Re: Connection Reuse draft to focus on TLS connections

Hadriel Kaplan wrote:
> One should note it's not applicable to just "TLS" - it's only
> applicable to mutual-TLS.  I don't mean to sound negative, but really
> you might as well limit it's applicability to IPv6 as well at this
> rate.  :(
> 
> Can this draft at least remove the statement in section 8.1 that the
> client SHOULD NOT add an alias parameter to TCP/SCTP transports?

Hadriel: I have had discussions with the AD on TCP/SCTP connection
reuse and their impact on the current TLS connection reuse draft.
The AD is of the opinion that it will be hard to progress
the current connect-reuse draft in IESG while allowing TCP/SCTP
connection reuse in the big-I Internet.

Obviously, the fact remains that people will use TCP connection
reuse, whether or not this draft prohibits it or not.  The
question boils down to how to best move *this* work ahead
(i.e., TLS connection reuse), and then deal with TCP connection
reuse.

The best way forward is to excise any text relating to TCP/SCTP
connection reuse, and focus this draft on TLS only (the original
motivation for the draft.)  This allows us to get the TLS
connect-reuse draft out (it has been pending now for four
arduous, laborious, suspenseful, pondering, brutal, intemperate,
and exacting years.)

In parallel, right after the -00 deadline for IETF 74 is over,
I will put out a new draft on TCP/SCTP connection reuse that
allows reuse for these transports when certain assumptions
are met.  I have been assured by the AD that a milestone can
be quickly added to SIP/DISPATCH/SIPCORE WG to allow the new
work to progress expeditiously.

Is that a workable solution for you?  Please let me know.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip