Hi,

Just a question: does this rescope affect chapter 8 (Overlap with
connection reuse) of the keep draft
(http://users.piuha.net/cholmber/drafts/draft-holmberg-sip-keep-03.txt)?


Regards,

Christer

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Dean Willis
Sent: Monday, March 02, 2009 10:04 PM
To: SIP WG
Cc: Cullen Jennings; Keith Drage
Subject: [Sip] Connection Reuse draft to focus on TLS connections


We intend to slightly rescope the Connection Reuse draft:

http://tools.ietf.org/id/draft-ietf-sip-connect-reuse-12.txt

Based on input from our ADs, the WG chairs and the editor of the have
agreed to eliminate the part of the draft that discusses the
implementation of reusing non-TLS connections. The stage for this is set
in the abstract of the current draft, from which I quote:

> From the security perspective, it is bad practice to reuse a single 
> connection for the TCP or SCTP transport between two peers, and this 
> document provides specific insights into why this is the case. As a 
> remedy, it suggests using two TCP connections (or two SCTP 
> associations), each opened pro-actively towards the recipient by the 
> sender.


We may  discuss at a later date the idea of developing a draft for
connection reuse in the absence of TLS.

I'm really not expecting anybody to object strongly to this approach,
but am bringing this to the list to avoid surprises down the road. If
you have major issues with doing it this way, please bring them up now.

--
Dean Willis (as chair, ten years and counting . . .)


_______________________________________________
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
_______________________________________________
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

Reply via email to