RE: [Sip] RFC 3261 supported header in 1xx responses
ramakrishna.adukuri@wipro.com Tue, 22 November 2005 12:54 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 1EeXfC-0000P8-9S; Tue, 22 Nov 2005 07:54:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeXfA-0000Oh-OZ for sip@megatron.ietf.org; Tue, 22 Nov 2005 07:54:20 -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 HAA13296 for <sip@ietf.org>; Tue, 22 Nov 2005 07:53:41 -0500 (EST)
From: ramakrishna.adukuri@wipro.com
Received: from wip-ec-wd.wipro.com ([203.91.193.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EeXxl-0001NS-QI for sip@ietf.org; Tue, 22 Nov 2005 08:13:37 -0500
Received: from wip-ec-wd.wipro.com (localhost.wipro.com [127.0.0.1]) by localhost (Postfix) with ESMTP id E73EF2062E for <sip@ietf.org>; Tue, 22 Nov 2005 18:10:49 +0530 (IST)
Received: from blr-ec-bh01.wipro.com (blr-ec-bh01.wipro.com [10.201.50.91]) by wip-ec-wd.wipro.com (Postfix) with ESMTP id CC8B12063D for <sip@ietf.org>; Tue, 22 Nov 2005 18:10:49 +0530 (IST)
Received: from BLR-EC-MBX04.wipro.com ([10.201.50.165]) by blr-ec-bh01.wipro.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Nov 2005 18:23:52 +0530
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: Tue, 22 Nov 2005 18:23:50 +0530
Message-ID: <D6DA3A176076B2408E53467FC0B0056B01D8879F@BLR-EC-MBX04.wipro.com>
Thread-Topic: [Sip] RFC 3261 supported header in 1xx responses
Thread-Index: AcXurPBqxASv71SbS2i9BgXUE1D2lwAsySBA
To: jdrosen@cisco.com, arunvenk@cisco.com
X-OriginalArrivalTime: 22 Nov 2005 12:53:52.0603 (UTC) FILETIME=[CA6032B0:01C5EF63]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: quoted-printable
Cc: sip@ietf.org, brett@broadsoft.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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
Is this different for 'Require', because in the case of session timers proxy can add a 'Require' to request/response depending on UAC/UAS not supporting session timers. -Ramakrishna -----Original Message----- From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Jonathan Rosenberg Sent: Monday, November 21, 2005 8:30 PM To: Arunachalam Venkatraman (arunvenk) Cc: sip-ietf; Brett Tate Subject: Re: [Sip] RFC 3261 supported header in 1xx responses If a proxy genreates the 1xx itself, it is effectively acting as a UAS, in which case insertion of Supported is fine. This won't confuse a UAC since any 1xx generated by the proxy itself will have different tags from a 2xx or other responses generated by the actual UA, and thus represent a different (early) dialog. A proxy cannot insert or modify a Supported header in a response that passes by it (i.e., one for which it is proxying). -Jonathan R. Arunachalam Venkatraman (arunvenk) wrote: > 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
- [Sip] RFC 3261 supported header in 1xx responses Brett Tate
- Re: [Sip] RFC 3261 supported header in 1xx respon… Jonathan Rosenberg
- RE: [Sip] RFC 3261 supported header in 1xx respon… Arunachalam Venkatraman (arunvenk)
- Re: [Sip] RFC 3261 supported header in 1xx respon… Jonathan Rosenberg
- RE: [Sip] RFC 3261 supported header in 1xx respon… ramakrishna.adukuri
- Re: [Sip] RFC 3261 supported header in 1xx respon… Jonathan Rosenberg