RE: [Sip] RFC 3261 supported header in 1xx responses

"Arunachalam Venkatraman \(arunvenk\)" <arunvenk@cisco.com> Sat, 19 November 2005 01:04 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EdH9X-00076H-T6; Fri, 18 Nov 2005 20:04:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EdH9W-000768-4J for sip@megatron.ietf.org; Fri, 18 Nov 2005 20:04:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25833 for <sip@ietf.org>; Fri, 18 Nov 2005 20:03:50 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EdHRR-0002P3-Vc for sip@ietf.org; Fri, 18 Nov 2005 20:22:59 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 18 Nov 2005 17:04:15 -0800
X-IronPort-AV: i="3.97,348,1125903600"; d="scan'208"; a="232301154:sNHT34814996"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jAJ14DeS026607; Fri, 18 Nov 2005 17:04:13 -0800 (PST)
Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 18 Nov 2005 17:04:13 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
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] RFC 3261 supported header in 1xx responses
Date: Fri, 18 Nov 2005 17:04:07 -0800
Message-ID: <75B2A84D9323BC4CA3977CF378CE75EBCA41C8@xmb-sjc-21e.amer.cisco.com>
Thread-Topic: [Sip] RFC 3261 supported header in 1xx responses
Thread-Index: AcXsmYLYTvywZ/7nS8y6rjCv+YbMcgACwABg
From: "Arunachalam Venkatraman (arunvenk)" <arunvenk@cisco.com>
To: "Jonathan Rosenberg (jdrosen)" <jdrosen@cisco.com>, Brett Tate <brett@broadsoft.com>
X-OriginalArrivalTime: 19 Nov 2005 01:04:13.0199 (UTC) FILETIME=[27D581F0:01C5ECA5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable
Cc: sip-ietf <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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Can a proxy add Supported? Is this disallowed?
If proxy may do so, the Supported cannot be interpreted as UAS
capabilities, even if the 1xx is reliable (consider INVITE with
Require:100rel).

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Jonathan Rosenberg (jdrosen)
Sent: Friday, November 18, 2005 5:39 PM
To: Brett Tate
Cc: sip-ietf
Subject: Re: [Sip] RFC 3261 supported header in 1xx responses

It makes sense to include them in a dialog forming response. A normal
1xx is not dialog forming. My suspicion (though I didn't check if this
was true) is that it went away when 100rel moved out of 3261. It can't
hurt to send them, of course, but it would be ignored unless its
reliable.

-Jonathan R.

Brett Tate wrote:

> Within early versions of draft-ietf-sip-rfc2543bis, the Supported 
> header could be expected within 1xx responses.  However within
> draft-ietf-sip-rfc2543bis-06 it was removed and remains so within RFC
3261.
> Is there a reason why it is undesirable to indicate supported 
> extensions within a 1xx?  Or was it just an oversight when changing 
> the "Summary of header fields" table to indicate 2xx instead of all
responses?
> 
> 
> 
> 
> _______________________________________________
> 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
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
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