IETF Logo Mail Archive

Re: [sipcore] draft-ietf-sipcore-subnot-etags: When to include SIP-Etag in NOTIFY?

Adam Roach <adam@nostrum.com> Wed, 07 April 2010 21:40 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4A0E3A6968 for <sipcore@core3.amsl.com>; Wed, 7 Apr 2010 14:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level:
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fb-sSvWGV4o4 for <sipcore@core3.amsl.com>; Wed, 7 Apr 2010 14:40:34 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id C31BF3A688D for <sipcore@ietf.org>; Wed, 7 Apr 2010 14:40:33 -0700 (PDT)
Received: from [172.16.3.231] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o37LePjj086845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Apr 2010 16:40:26 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BBCFBC9.1070204@nostrum.com>
Date: Wed, 07 Apr 2010 16:40:25 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <FF84A09F50A6DC48ACB6714F4666CC745E21C7CB1E@ESESSCMS0354.eemea.ericsson.se>, <D49EC598-C99E-4171-9DE9-E6737A0CCE0A@softarmor.com> <FF84A09F50A6DC48ACB6714F4666CC745E21B30A99@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC745E21B30A99@ESESSCMS0354.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] draft-ietf-sipcore-subnot-etags: When to include SIP-Etag in NOTIFY?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2010 21:40:34 -0000

On 4/7/10 4:31 PM, Christer Holmberg wrote:
> Hi,
>
>    
>>> So, the question is: is a subnot-etags compliant notifier required
>>> to insert the SIP-Etag in *every* NOT request, or only in the cases
>>> explicitly described in Section 6?
>>>        
>>
>> I believe the answer is "always".
>>
>> I also believe I just saw an Auth 48 request come out on this draft.
>> Anybody else got a bug to fix?
>>      
> In 3265bis we are aiming at getting rid of the 202 response. The subnot draft defines another one, 204, but I guess it doesn't matter since only endpoints supporting the draft are going to send and receive it.
>    

We're getting rid of 202 because it is vestigial, meaningless, and often 
implemented incorrectly.

subnot-etag's use of 204 is critical for proper functioning of its 
mechanism.

/a

v2.23.0 | Report a Bug | By Email