IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 07 April 2010 21:33 UTC

Return-Path: <christer.holmberg@ericsson.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 4D0603A6956 for <sipcore@core3.amsl.com>; Wed, 7 Apr 2010 14:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.305
X-Spam-Level:
X-Spam-Status: No, score=-3.305 tagged_above=-999 required=5 tests=[AWL=-0.706, 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 Zy4JZbxEPYz9 for <sipcore@core3.amsl.com>; Wed, 7 Apr 2010 14:33:32 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 4DDFF3A68EF for <sipcore@ietf.org>; Wed, 7 Apr 2010 14:33:32 -0700 (PDT)
X-AuditID: c1b4fb39-b7b85ae000005cbc-38-4bbcfa281a69
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id A6.BF.23740.82AFCBB4; Wed, 7 Apr 2010 23:33:28 +0200 (CEST)
Received: from ESESSCMS0354.eemea.ericsson.se ([169.254.2.223]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Wed, 7 Apr 2010 23:33:28 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Dean Willis <dean.willis@softarmor.com>
Date: Wed, 07 Apr 2010 23:31:46 +0200
Thread-Topic: [sipcore] draft-ietf-sipcore-subnot-etags: When to include SIP-Etag in NOTIFY?
Thread-Index: AcrWmFVsOZpzRExQSBO+RnWw2pkuVQAAWReB
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745E21B30A99@ESESSCMS0354.eemea.ericsson.se>
References: <FF84A09F50A6DC48ACB6714F4666CC745E21C7CB1E@ESESSCMS0354.eemea.ericsson.se>, <D49EC598-C99E-4171-9DE9-E6737A0CCE0A@softarmor.com>
In-Reply-To: <D49EC598-C99E-4171-9DE9-E6737A0CCE0A@softarmor.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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:33:33 -0000

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.

Regards,

Christer

v2.23.0 | Report a Bug | By Email