(As WG chair)

Here we have a document that has been floating around for a while. We
had a WGLC on it back on 26th October 2005 to complete 18th November
2005. After that we got buried in outbound, and sort of lost direction.

At the last IETF meeting, we agreed to rescope this and as a result
decided there support in progressing the document. You can find the
record of that discussion in the proceedings for IETF#69. This draft
reflects those WG decisions. 

We would therefore like to renew the WGLC, and solicit comments by close
of business on Tuesday 6th November on draft-ietf-sip-connect-reuse-08.

Normal rules apply. Comments to the sip mailing list and authors. Please
clearly identify the nature of your comment (editorial, minor technical,
major). Please clearly identify the text to which your comment relates.

Note that of the normative references, domain-certs is in progress as a
WG item, and we should see a first draft of the WG text in the next few
days.

Regards

Keith



> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, October 17, 2007 1:15 AM
> To: [EMAIL PROTECTED]
> Cc: [email protected]
> Subject: [Sip] I-D ACTION:draft-ietf-sip-connect-reuse-08.txt 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Session Initiation Protocol 
> Working Group of the IETF.
> 
>       Title           : Connection Reuse in the Session Initiation 
>                           Protocol (SIP)
>       Author(s)       : R. Mahy, et al.
>       Filename        : draft-ietf-sip-connect-reuse-08.txt
>       Pages           : 21
>       Date            : 2007-10-16
>       
> This document enables a pair of communicating proxies to reuse a
>    congestion-controlled connection between themselves for sending
>    requests in the forward and backwards direction.  Because the
>    connection is essentially aliased for requests going in 
> the backwards
>    direction, reuse should be predicated upon both the communicating
>    endpoints authenticating themselves using X.509 
> certificates through
>    TLS.  For this reason, we only consider connection reuse 
> for TLS over
>    TCP and TLS over SCTP.  A single connection cannot be 
> reused for the
>    TCP or SCTP transport between two peers, and this document provides
>    insight 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.  Finally, 
> this document
>    also provides guidelines on connection reuse and virtual 
> SIP servers
>    and the interaction of connection reuse and DNS SRV lookups in SIP.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sip-connect-reu
> se-08.txt
> 
> To remove yourself from the I-D Announcement list, send a 
> message to [EMAIL PROTECTED] with the word 
> unsubscribe in the body of the message. 
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> Internet-Drafts are also available by anonymous FTP. Login 
> with the username "anonymous" and a password of your e-mail 
> address. After logging in, type "cd internet-drafts" and then 
> "get draft-ietf-sip-connect-reuse-08.txt".
> 
> A list of Internet-Drafts directories can be found in 
> http://www.ietf.org/shadow.html or 
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>       [EMAIL PROTECTED]
> In the body type:
>       "FILE /internet-drafts/draft-ietf-sip-connect-reuse-08.txt".
>       
> NOTE: The mail server at ietf.org can return the document in
>       MIME-encoded form by using the "mpack" utility.  To use this
>       feature, insert the command "ENCODING mime" before the "FILE"
>       command.  To decode the response(s), you will need "munpack" or
>       a MIME-compliant mail reader.  Different MIME-compliant 
> mail readers
>       exhibit different behavior, especially when dealing with
>       "multipart" MIME messages (i.e. documents which have been split
>       up into multiple messages), so check your local documentation on
>       how to manipulate these messages.
> 
> Below is the data which will enable a MIME compliant mail 
> reader implementation to automatically retrieve the ASCII 
> version of the Internet-Draft.
> 


_______________________________________________
Sip mailing list  https://www1.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