Re: [sipcore] Last Call: <draft-ietf-sipcore-6665-clarification-00.txt> (A clarification on the use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework) to Proposed Standard

Ivo Sedlacek <ivo.sedlacek@ericsson.com> Thu, 04 June 2015 07:40 UTC

Return-Path: <ivo.sedlacek@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD3B1ACD53; Thu, 4 Jun 2015 00:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ww_Al6iPGex8; Thu, 4 Jun 2015 00:40:03 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D70301ACE71; Thu, 4 Jun 2015 00:39:59 -0700 (PDT)
X-AuditID: c1b4fb3a-f79ec6d000006dc0-af-557000cd9ed8
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.125]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 35.8F.28096.DC000755; Thu, 4 Jun 2015 09:39:58 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.137]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0210.002; Thu, 4 Jun 2015 09:39:57 +0200
From: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Thread-Topic: [sipcore] Last Call: <draft-ietf-sipcore-6665-clarification-00.txt> (A clarification on the use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework) to Proposed Standard
Thread-Index: AQHQnlAMFDKoxxFcN0S4yuB7gC29TJ2b9TCA
Date: Thu, 04 Jun 2015 07:39:57 +0000
Message-ID: <39B5E4D390E9BD4890E2B31079006101128CB7D1@ESESSMB301.ericsson.se>
References: <20150603225255.28317.78722.idtracker@ietfa.amsl.com>
In-Reply-To: <20150603225255.28317.78722.idtracker@ietfa.amsl.com>
Accept-Language: en-US, cs-CZ
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvre45hoJQg/VruSzunZnOZvFs43wW i68/NrE5MHssWfKTKYAxissmJTUnsyy1SN8ugSvj31GVgmPCFe3d3ewNjLsFuhg5OSQETCTW XN3FDGGLSVy4t56ti5GLQ0jgKKPE1acfGCGcxYwSJ26dAatiE9CTmLjlCCuILSLgLfF52SKw OLOApsSjnXuZQBqEBX4zSsxo7wNzRAT+MEqs/X+MCaLDSOL+ow1ANgcHi4CKxPaj4SBhXgFf ic4Nt9hAwkICjhL/5riDhDkFnCR2LP7ECGIzCshKXP3TywixS1zi1pP5TBBXC0gs2XMe6gNR iZeP/7FC2IoSV6cvZ4Ko15N4dmoWC4StLbFs4WtmiLWCEidnPmGZwCg2C8nYWUhaZiFpmYWk ZQEjyypG0eLU4uLcdCMjvdSizOTi4vw8vbzUkk2MwPg5uOW31Q7Gg88dDzEKcDAq8fAmvMwP FWJNLCuuzD3EKM3BoiTOO2NzXqiQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGxn6m/bemLY+d K3CMR8NH+dqkjfKvG5h+H3d+VcmRlea0lKnln+xJmX1zk+O/JR2Kfmpg+6+V0Wd9xOI3OdyS 2f+v6Ohtk8kJnHSF+7Ybs3H7jX5WW+VpMy832nv4ycyZGa5uXCqw/dRujdBjLBvWM6fvtXrg +XTJ3/5TK+8rvmljKhNi41rBosRSnJFoqMVcVJwIAG/uaTSAAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/IBFdDjSS7xlBji2bMrQNG3qzbTc>
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-6665-clarification-00.txt> (A clarification on the use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework) to Proposed Standard
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 04 Jun 2015 07:40:05 -0000

Hello,

COMMENT:
=======================================
The draft http://tools.ietf.org/html/draft-ietf-sipcore-6665-clarification-00 uses inconsistent terminology. It uses "subscription requests (implicit or explicit)" and "request that might create a subscription to the associated dialog" and both seem to be the same. It would be better to use one term only.
=======================================

Kind regards

Ivo Sedlacek

-----Original Message-----
From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of The IESG
Sent: 4. června 2015 0:53
To: IETF-Announce
Cc: sipcore@ietf.org
Subject: [sipcore] Last Call: <draft-ietf-sipcore-6665-clarification-00.txt> (A clarification on the use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework) to Proposed Standard


The IESG has received a request from the Session Initiation Protocol Core WG (sipcore) to consider the following document:
- 'A clarification on the use of Globally Routable User Agent URIs
   (GRUUs) in the Session Initiation Protocol (SIP) Event Notification
   Framework'
  <draft-ietf-sipcore-6665-clarification-00.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-06-17. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting.

Abstract


   Experience since the publication of the most recent SIP Events
   framework has shown that there is room for interpretation around the
   use of Globally Routable User Agent URIs in that specification.  This
   document clarifies the intended behavior.

   This document updates RFC 6665.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sipcore-6665-clarification/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-sipcore-6665-clarification/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore