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

Cullen Jennings <fluffy@cisco.com> Sat, 28 April 2007 22:10 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 1Hhv7h-0006j8-JO; Sat, 28 Apr 2007 18:10:33 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hhv7g-0006j2-6l for sip-confirm+ok@megatron.ietf.org; Sat, 28 Apr 2007 18:10:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hhv7f-0006iu-TU for sip@ietf.org; Sat, 28 Apr 2007 18:10:31 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hhv7e-0007H1-IL for sip@ietf.org; Sat, 28 Apr 2007 18:10:31 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-5.cisco.com with ESMTP; 28 Apr 2007 15:10:30 -0700
X-IronPort-AV: i="4.14,465,1170662400"; d="scan'208"; a="416713872:sNHT49671224"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l3SMAUJA002793; Sat, 28 Apr 2007 15:10:30 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82]) by sj-core-3.cisco.com (8.12.10/8.12.6) with SMTP id l3SMAOA9029959; Sat, 28 Apr 2007 22:10:25 GMT
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1032AB49@zrc2hxm0.corp.nortel.com>
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> <1ECE0EB50388174790F9694F77522CCF1032AB49@zrc2hxm0.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <F7873361-B01E-4811-AD57-D30B93F57124@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues
Date: Sat, 28 Apr 2007 15:09:50 -0700
To: SIP <sip@ietf.org>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2235; t=1177798230; x=1178662230; c=relaxed/simple; s=sjdkim8002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-sips-03.txt=3A=20Closing=20of= 20Opened=20issues |Sender:=20; bh=bYEDzAhkAmJ0ryKvYzOp4YlVKFNrO9Blp3m/nRFnGbE=; b=kA1uMdjg5KGrK4/F1W1acXTgtOmwQGm0aPSblYlkOC2HtHfp6nPSxBMBUl6uvva8CKJy+7ZM ueFd4nQjpFJZeJU9PS2fO3Wr3Dpiyp1Z+LO2974d2L1T+PniPaAw2ceA;
Authentication-Results: sj-dkim-8; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim8002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: Francois Audet <audet@nortel.com>
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

Francois pointed out this draft was wrong to me a long time ago -  
Nagendra and I agree with him. We just had not got around to fixing it.

Cullen <with my individual hat on>


On Apr 26, 2007, at 2:49 PM, Francois Audet wrote:

> 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


_______________________________________________
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