IETF Logo Mail Archive

Re: [Insipid] Working group last call for draft-ietf-insipid-session-id-10

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Thu, 06 November 2014 20:43 UTC

Return-Path: <keith.drage@alcatel-lucent.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 717EE1A6F2D for <insipid@ietfa.amsl.com>; Thu, 6 Nov 2014 12:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.494
X-Spam-Level:
X-Spam-Status: No, score=-7.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594] 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 YyGCFqzcYiJA for <insipid@ietfa.amsl.com>; Thu, 6 Nov 2014 12:43:12 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6B701A1BB0 for <insipid@ietf.org>; Thu, 6 Nov 2014 12:43:11 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 0867E323A8697; Thu, 6 Nov 2014 20:43:05 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id sA6Kh89J023574 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 6 Nov 2014 21:43:08 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.25]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Thu, 6 Nov 2014 21:43:08 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Brett Tate <brett@broadsoft.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Working group last call for draft-ietf-insipid-session-id-10
Thread-Index: Ac/6AXJ7QpsEiybpQCeWT5uCLiGAmAAAIkbQ
Date: Thu, 06 Nov 2014 20:43:07 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B272A7A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <d1d0daf674d86e0f34bd3363d4045af8@mail.gmail.com>
In-Reply-To: <d1d0daf674d86e0f34bd3363d4045af8@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/yOozGv-YHnCDIebKDIHFfr8hPDs
Subject: Re: [Insipid] Working group last call for draft-ietf-insipid-session-id-10
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, 06 Nov 2014 20:43:14 -0000

Yes, I am expecting an update sometime after the window reopens on Monday. But I would like to get this closed off.

I would encourage others to join the discussion of this one open point.

Keith

> -----Original Message-----
> From: Brett Tate [mailto:brett@broadsoft.com] 
> Sent: 06 November 2014 20:40
> To: DRAGE, Keith (Keith); insipid@ietf.org
> Subject: RE: [Insipid] Working group last call for 
> draft-ietf-insipid-session-id-10
> 
> Hi,
> 
> I'd actually like to see the draft be updated based upon the 
> current WGLC comments and the WGLC be continued.
> 
> As indicated within the following post and the following 
> offline comment, I currently don't think that the draft 
> adequately addresses CANCEL.  This includes when caller 
> cancels a forking fan-out.
> 
> http://www.ietf.org/mail-archive/web/insipid/current/msg00962.html
> 
> "However, seeing the section 9.8.1 figure 10 modification 
> highlights additional interesting things concerning the 
> CANCEL-while-forking call flow such as the CANCEL's 200 
> response and INVITE's 487 response.
> 
> Some B2BUAs act like a proxy, you might want to white board 
> exactly how you expect compliant proxies (or proxy B2BUAs) to 
> behave when the caller cancels.
> 
> Similarly, some B2BUAs will send 487 immediately instead of 
> waiting for a final responses from the cancelled branches.  
> You might want to white board exactly how you expect 
> compliant B2BUAs (which behave this way) to behave when the 
> caller cancels.
> 
> Similarly, both of the above can occur after 100 response (no 
> 101-199 responses).  You might want to white board exactly 
> how you expect a compliant proxy/B2BUA to behave."
> 
> Thanks,
> Brett
> 
> -------
> 
> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of 
> DRAGE, Keith
> (Keith)
> Sent: Thursday, November 06, 2014 2:57 PM
> To: insipid@ietf.org
> Subject: [Insipid] Working group last call for 
> draft-ietf-insipid-session-id-10
> 
> (as WG cochair)
> 
> We have now passed the deadline for comments.
> 
> The chairs believe the document has been well reviewed and 
> will now proceed with the publication request writeup.
> 
> If you do still have comments out there that are yet to be 
> submitted, then please contact the chairs to at least 
> indicate they are coming, and we will make appropriate 
> arrangements to handle them.
> 
> Regards
> 
> Keith
> 
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>

v2.23.0 | Report a Bug | By Email