RE: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues

"Francois Audet" <audet@nortel.com> Thu, 26 April 2007 21:50 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhBqm-00018o-8v; Thu, 26 Apr 2007 17:50:04 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HhBql-00018T-Cz for sip-confirm+ok@megatron.ietf.org; Thu, 26 Apr 2007 17:50:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhBql-00017N-1p for sip@ietf.org; Thu, 26 Apr 2007 17:50:03 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhBqj-0005Eh-Oj for sip@ietf.org; Thu, 26 Apr 2007 17:50:03 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l3QLnxn15385 for <sip@ietf.org>; Thu, 26 Apr 2007 21:49:59 GMT
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues
Date: Thu, 26 Apr 2007 16:49:55 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1032AB49@zrc2hxm0.corp.nortel.com>
In-Reply-To: <46311E22.3040307@alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues
Thread-Index: AceITKHKQDS6I9MVRFC4PEpGZp7+VwAABiFQ
References: <1ECE0EB50388174790F9694F77522CCF100DE550@zrc2hxm0.corp.nortel.com> <70B32427-9693-4423-AB86-7C926A479F85@cisco.com> <1ECE0EB50388174790F9694F77522CCF1028B59B@zrc2hxm0.corp.nortel.com> <462F613C.2050502@sipstation.com> <1ECE0EB50388174790F9694F77522CCF10329CA3@zrc2hxm0.corp.nortel.com> <17968.16340.800200.535818@tutpro.com> <1ECE0EB50388174790F9694F77522CCF1032A3C9@zrc2hxm0.corp.nortel.com> <17968.58739.220882.733487@tutpro.com> <1ECE0EB50388174790F9694F77522CCF1032A6D8@zrc2hxm0.corp.nortel.com> <17968.61648.893419.784702@tutpro.com> <05650EF6-4740-4F00-97AF-AA180402AC1E@softarmor.com> <1ECE0EB50388174790F9694F77522CCF1032AAEF@zrc2hxm0.corp.nortel.com> <46311E22.3040307@alcatel-lucent.com>
From: Francois Audet <audet@nortel.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Yes, that draft is wrong and needs to be fixed. 

The correct behavior is 1/

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com] 
> Sent: Thursday, April 26, 2007 14:48
> To: Audet, Francois (SC100:3055)
> Cc: sip@ietf.org
> Subject: Re: [Sip] draft-ietf-sip-sips-03.txt: Closing of 
> Opened issues
> 
> Francois Audet wrote:
> > VIA already supports SCTP, TLS-SCTP. And the draft provides the 
> > references to RFC 4168 that defines it.
> 
> We've had this conversation before.
> 
> That is all well and fine for Vias (responses), but what 
> about requests triggered by a R-URI?
> 
> > DTLS is defined in
> > http://tools.ietf.org/wg/sip/draft-jennings-sip-dtls-03.txt.
> 
> dtls-03 says that a SIP URI to be sent over DTLS should look 
> like the following:
> 
>     sip:alice@example.com;transport=dtls-udp
> 
> Two questions:
>    1/ should it not be "sips" scheme here?
>    2/ If we are endorsing "transport=dtls-udp" in a SIP URI, then
>       saying that you should not put "transport=tls" in a SIP URI
>       seems silly. (Note that I personally do not like how
>       implementations have continued to use "transport=tls"
>       despite rfc3261 deprecating this.  But questions will arise
>       in the future that why are we allowing "transport=dtls-udp"
>       and not "transport=tls"?)
> 
> Thanks,
> 
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
> WWW:   http://www.alcatel-lucent.com/bell-labs
> 


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip