[sipcore] Comment on draft-ietf-sipcore-refer-explicit-subscription-01
<marianne.mohali@orange.com> Sat, 14 March 2015 16:58 UTC
Return-Path: <marianne.mohali@orange.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 52DF81A0277 for <sipcore@ietfa.amsl.com>; Sat, 14 Mar 2015 09:58:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level:
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 cdVlQnDh9cCi for <sipcore@ietfa.amsl.com>; Sat, 14 Mar 2015 09:58:40 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76F661A026A for <sipcore@ietf.org>; Sat, 14 Mar 2015 09:58:39 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id D2AEB26425E; Sat, 14 Mar 2015 17:58:37 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 9E851238056; Sat, 14 Mar 2015 17:58:37 +0100 (CET)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0224.002; Sat, 14 Mar 2015 17:58:37 +0100
From: marianne.mohali@orange.com
To: Robert Sparks <rjsparks@nostrum.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] Comment on draft-ietf-sipcore-refer-explicit-subscription-01
Thread-Index: AdBed7/EO4fQAoUJRcSohVaf/WA0hw==
Date: Sat, 14 Mar 2015 16:58:36 +0000
Message-ID: <12455_1426352317_550468BD_12455_2010_1_8B970F90C584EA4E97D5BAAC9172DBB814318AE6@PEXCVZYM12.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.4]
Content-Type: multipart/alternative; boundary="_000_8B970F90C584EA4E97D5BAAC9172DBB814318AE6PEXCVZYM12corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/AfH4pFElsJ2R6QDngV2x5kXxvu4>
Subject: [sipcore] Comment on draft-ietf-sipcore-refer-explicit-subscription-01
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: Sat, 14 Mar 2015 16:58:43 -0000
Hello, I did a late review of draft-ietf-sipcore-refer-clarifications-03 and draft-ietf-sipcore-refer-explicit-subscription-01. I'm fine with those drafts but I just have one comment on draft-ietf-sipcore-refer-explicit-subscription-01 and I prefer to do it before its publication: On this draft it is clearly stated for the 'explicitsub' option tag that "The event server identified by the Refer-Events-At URI could receive SUBSCRIBE requests" In section 5.1 : For the 'nosub' option tag, even if it is stated that "no explicit subscription will be forthcoming", there is no explicit statement such as : A UA sending a REFER with the 'nosub' option tag MUST NOT send a SUBSCRIBE request for that dialog. Maybe you consider, this situation cannot appear as this UA will not receive the event server URI in the Refer-Event-At? In that case, I think it would be good to have the following statements: - in section 5.2: If the UA receives a 2xx-class response, it will not contain a Refer-Events-At header field. and - in section 5.3: An element that accepts a REFER request with 'nosub' in its Require header field MUST return a 200 response that MUST NOT contain a URI that could be used to subscribe to the refer event state associated with this REFER request. It is also possible that I missed something already mentioned in the draft. If not, I think a statement like that could reinforce the correct usage of the 'nosub' option tag. Sorry about this very late comment. Kind regards, Marianne Mohali _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- [sipcore] Comment on draft-ietf-sipcore-refer-exp… marianne.mohali
- Re: [sipcore] Comment on draft-ietf-sipcore-refer… Robert Sparks