Re: [IPsec] regarding draft-ietf-ipsecme-tcp-encaps

On 4/25/2017 8:46 PM, Yoav Nir wrote: > ... >>> While it is the default port for HTTPS, that protocol can run on any >>> port depending on the value in origin (RFC 6454). >> >> Yes, any protocol can run on any port number (as per above), as long >> as the endpoints agree. But that's not what

Re: [IPsec] regarding draft-ietf-ipsecme-tcp-encaps

Hi, Tommy, On 4/25/2017 8:34 PM, Tommy Pauly wrote: > I suggest that we can: > > - Clarify the text in section 2 (configuration) to say that the > default port is TCP 4500, and that implementations may communicate > other port options out of band as configuration. This is done for UDP > as well.

Re: [IPsec] regarding draft-ietf-ipsecme-tcp-encaps

> On 26 Apr 2017, at 0:15, Joe Touch wrote: > > First, correcting the subject line (sorry - that looks like an erroneous > paste on my part). > > Also below... > > On 4/25/2017 1:59 PM, Yoav Nir wrote: >> Hi, Joe >> >> I haven’t been involved with this draft, but I don’t

Re: [IPsec] regarding draft-ietf-ipsecme-tcp-encaps

> On Apr 25, 2017, at 2:15 PM, Joe Touch wrote: > > First, correcting the subject line (sorry - that looks like an erroneous > paste on my part). > > Also below... > > On 4/25/2017 1:59 PM, Yoav Nir wrote: >> Hi, Joe >> >> I haven’t been involved with this draft, but I don’t

[IPsec] regarding draft-ietf-ipsecme-tcp-encaps

First, correcting the subject line (sorry - that looks like an erroneous paste on my part). Also below... On 4/25/2017 1:59 PM, Yoav Nir wrote: > Hi, Joe > > I haven’t been involved with this draft, but I don’t believe that last > statement is correct: > >> On 25 Apr 2017, at 23:03, Joe Touch