IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 07 April 2010 12:59 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 2E14A3A68A2 for <sipcore@core3.amsl.com>; Wed, 7 Apr 2010 05:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.273
X-Spam-Level:
X-Spam-Status: No, score=-5.273 tagged_above=-999 required=5 tests=[AWL=1.325, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 YmkTXTOOrwZv for <sipcore@core3.amsl.com>; Wed, 7 Apr 2010 05:59:25 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 2997B3A688A for <sipcore@ietf.org>; Wed, 7 Apr 2010 05:59:24 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-59-4bbc81a804ef
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id F2.3F.23532.8A18CBB4; Wed, 7 Apr 2010 14:59:21 +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 14:59:20 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Wed, 07 Apr 2010 14:59:20 +0200
Thread-Topic: draft-ietf-sipcore-subnot-etags: When to include SIP-Etag in NOTIFY?
Thread-Index: AcrWUiOv5A1GPfg7RHuYv7tpmrzlKA==
Message-ID: <FF84A09F50A6DC48ACB6714F4666CC745E21C7CB1E@ESESSCMS0354.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_FF84A09F50A6DC48ACB6714F4666CC745E21C7CB1EESESSCMS0354e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [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 12:59:26 -0000

Hi,

When looking deeper into draft-ietf-sipcore-subnot-etags, we also found the following issue/question:

Figure1/Step 3 and Figure 3/Step 3 suggest that the subnot-etags compliant notifier includes the SIP-Etag in the NOT request even if the associated SUB request did not contain Suppress-If-Match. The overview text in section 3 also seems to indicate that SIP-Etag is inserted in every NOT, but that is also informative text only.

However, Section 6 only contains normative text about inclusion of the SIP-Etag in the following situations:

1. The NOT request is generated upon SIP SUB with condition (section 6.2); and

2. The NOT request is generated with state differential (section 6.4)

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?

Regards,

Christer

v2.23.0 | Report a Bug | By Email