Re: [Insipid] Alignment with RFC 6665 in draft-ietf-insipid-session-id
Andrew Allen <aallen@blackberry.com> Thu, 26 March 2015 17:04 UTC
Return-Path: <aallen@blackberry.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7D81A03AB for <insipid@ietfa.amsl.com>; Thu, 26 Mar 2015 10:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 QifYkcnlv4XC for <insipid@ietfa.amsl.com>; Thu, 26 Mar 2015 10:04:15 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1381A88D6 for <insipid@ietf.org>; Thu, 26 Mar 2015 10:04:14 -0700 (PDT)
Received: from xct102cnc.rim.net ([10.65.161.202]) by mhs210cnc.rim.net with ESMTP/TLS/AES128-SHA; 26 Mar 2015 13:04:10 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT102CNC.rim.net ([fe80::2066:5d4f:8c45:af55%17]) with mapi id 14.03.0210.002; Thu, 26 Mar 2015 13:04:08 -0400
From: Andrew Allen <aallen@blackberry.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Alignment with RFC 6665 in draft-ietf-insipid-session-id
Thread-Index: AQHQZ+beaxdhN4PqnkS3yFmuhj0h5Q==
Date: Thu, 26 Mar 2015 17:04:07 +0000
Message-ID: <20150326170406.5955730.66546.18280@blackberry.com>
References: <949EF20990823C4C85C18D59AA11AD8B4A11D6A5@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B4A11D6A5@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_2015032617040659557306654618280blackberrycom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/k9pLizrQLJ6NNaIRQf_mIHjpz5E>
Cc: Adam Roach <adam@nostrum.com>
Subject: Re: [Insipid] Alignment with RFC 6665 in draft-ietf-insipid-session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2015 17:04:17 -0000
I would support 2) and 3) There should be clear text that the current 9.2 example is a legacy example where the remote target provided is not a GRUU and that the other case (currently 9.9) is the normal scenario. The legacy case should go at the end of the examples. Sent from my BlackBerry 10 smartphone. From: DRAGE, Keith (Keith) Sent: Thursday, March 26, 2015 12:01 To: insipid@ietf.org Cc: Adam Roach Subject: [Insipid] Alignment with RFC 6665 in draft-ietf-insipid-session-id (As WG chair) WG please address the following issue. We have a couple of examples showing REFER usage in this document (section 9.2 and section 9.2). RFC 6665 deprecates the usage of in-dialog REFER, so the only source for such usage would be interoperation with legacy systems. Section 9.2 (with the in-dialog usage) appears first. 1) Should section 9.2 be included in the document at all, because it is at variance with the normal operation specified in RFC 6665? 2) If section 9.2 does appear in the document, should we reverse the order of the examples? 3) If section 9.2 does appear in the document, should there be some extra text explaining the variance from RFC 6665, and if so what? Regards Keith _______________________________________________ insipid mailing list insipid@ietf.org https://www.ietf.org/mailman/listinfo/insipid
- [Insipid] Alignment with RFC 6665 in draft-ietf-i… DRAGE, Keith (Keith)
- Re: [Insipid] Alignment with RFC 6665 in draft-ie… Andrew Allen
- Re: [Insipid] Alignment with RFC 6665 in draft-ie… DRAGE, Keith (Keith)