
From nobody Sat Oct 18 03:32:09 2014
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 E8F821A1BA2 for <insipid@ietfa.amsl.com>; Sat, 18 Oct 2014 03:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Qi0R1fdvV0aL for <insipid@ietfa.amsl.com>; Sat, 18 Oct 2014 03:32:06 -0700 (PDT)
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 F39F71A1B9A for <insipid@ietf.org>; Sat, 18 Oct 2014 03:32:05 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 954A7BF82198 for <insipid@ietf.org>; Sat, 18 Oct 2014 10:32:00 +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 s9IAW2nH010247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <insipid@ietf.org>; Sat, 18 Oct 2014 12:32:02 +0200
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; Sat, 18 Oct 2014 12:32:02 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: Working group last call for draft-ietf-insipid-session-id-10
Thread-Index: Ac/qvkp4YeX1M6uVTyGkdH2Dq6Q5CA==
Date: Sat, 18 Oct 2014 10:32:01 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B261ADE@FR712WXCHMBA11.zeu.alcatel-lucent.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.41]
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/jt7agLqQLHmeFnu_uuom1YT57dM
Subject: [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: Sat, 18 Oct 2014 10:32:08 -0000

This is a WGLC for draft-ietf-insipid-session-id-10

https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/

Please review and provide comments both editorial and technical, preferably=
 to the list directly, by 1st of November 2014.

It is helpful if comments are given some form of grading, so we can quickly=
 identify the showstoppers from the pure editorial (and those inbetween).

If you have comments as a result of this review that you believe will need =
discussion in Honolulu to resolve, then please attempt to identify those co=
mments early, i.e. within the next few days.

Regards

Keith
Gonzalo

WG cochairs=


From nobody Sat Oct 18 04:15:15 2014
Return-Path: <mary.ietf.barnes@gmail.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 4E0A81A6F98 for <insipid@ietfa.amsl.com>; Sat, 18 Oct 2014 04:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 ejgK2K48i4H3 for <insipid@ietfa.amsl.com>; Sat, 18 Oct 2014 04:15:04 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40E081A6F9B for <insipid@ietf.org>; Sat, 18 Oct 2014 04:15:02 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id q1so1882136lam.36 for <insipid@ietf.org>; Sat, 18 Oct 2014 04:15:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=omYm4wpb9F5t/zzryb9z/wR50AMhJsM2KIj1rSX+3ks=; b=MZ+36uR1KE/aBfMZzJsAj7Ah8eUv1qx4iXngt2YjSEhwyhVkShJVW5Bx6e7354Wypm utFVcs0OosQWzUcjuFU2ulKDdAYFHXNpG//xFVlKlJLTLkKVXNwJdQQIxyHcNRf9xOvB GDaoVCnjMXtpF1LJh4funSyfY8vG/SwQF73Tvudp/+IbQXcHp3IhzDL6m6s/EP2vKpYx PGRS2hKyC6JS53YKii3sMsOGNSpNxKiKh8kVkhF7VGQDmU8RgYMeHR683+iAfOkkZiLL EaUu/+P206VQfMBCuWQZVWvXPoSRjc6uXZLt3/3qmP3ggtrXtmdDPMVRz0jHGYjsmT0e UxBg==
MIME-Version: 1.0
X-Received: by 10.112.85.138 with SMTP id h10mr14545119lbz.33.1413630900506; Sat, 18 Oct 2014 04:15:00 -0700 (PDT)
Received: by 10.25.42.136 with HTTP; Sat, 18 Oct 2014 04:15:00 -0700 (PDT)
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B261ADE@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <949EF20990823C4C85C18D59AA11AD8B261ADE@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Date: Sat, 18 Oct 2014 06:15:00 -0500
Message-ID: <CAHBDyN7fz0Scz7CD7gf4u26zR+wcwLmGKbWYpkAY9W-haOsJ9A@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=001a11347168ab14f60505b097f8
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/zzvle9-X6BEzhqd1zzq5V_RExI4
Cc: "insipid@ietf.org" <insipid@ietf.org>
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: Sat, 18 Oct 2014 11:15:07 -0000

--001a11347168ab14f60505b097f8
Content-Type: text/plain; charset=UTF-8

I think a 2 week WGLC, when one of the weeks is the week before the IETF
meeting draft deadline is a little short.  Most people are focused on
getting their own drafts updated and submitted prior to the draft cutoff
and most likely won't be looking for other drafts to read until after the
cutoff.

Regards,
Mary.

On Sat, Oct 18, 2014 at 5:32 AM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

> This is a WGLC for draft-ietf-insipid-session-id-10
>
> https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
>
> Please review and provide comments both editorial and technical,
> preferably to the list directly, by 1st of November 2014.
>
> It is helpful if comments are given some form of grading, so we can
> quickly identify the showstoppers from the pure editorial (and those
> inbetween).
>
> If you have comments as a result of this review that you believe will need
> discussion in Honolulu to resolve, then please attempt to identify those
> comments early, i.e. within the next few days.
>
> Regards
>
> Keith
> Gonzalo
>
> WG cochairs
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>

--001a11347168ab14f60505b097f8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think a 2 week WGLC, when one of the weeks is the week b=
efore the IETF meeting draft deadline is a little short.=C2=A0 Most people =
are focused on getting their own drafts updated and submitted prior to the =
draft cutoff and most likely won&#39;t be looking for other drafts to read =
until after the cutoff.=C2=A0<div><div><br></div><div>Regards,</div><div>Ma=
ry.</div></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sat, Oct 18, 2014 at 5:32 AM, DRAGE, Keith (Keith) <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:keith.drage@alcatel-lucent.com" target=3D"_blank">ke=
ith.drage@alcatel-lucent.com</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">This is a WGLC for draft-ietf-insipid-session-id-10<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/"=
 target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-insipid-sess=
ion-id/</a><br>
<br>
Please review and provide comments both editorial and technical, preferably=
 to the list directly, by 1st of November 2014.<br>
<br>
It is helpful if comments are given some form of grading, so we can quickly=
 identify the showstoppers from the pure editorial (and those inbetween).<b=
r>
<br>
If you have comments as a result of this review that you believe will need =
discussion in Honolulu to resolve, then please attempt to identify those co=
mments early, i.e. within the next few days.<br>
<br>
Regards<br>
<br>
Keith<br>
Gonzalo<br>
<br>
WG cochairs<br>
_______________________________________________<br>
insipid mailing list<br>
<a href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/insipid" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/insipid</a><br>
</blockquote></div><br></div>

--001a11347168ab14f60505b097f8--


From nobody Sat Oct 18 04:22:38 2014
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 0D4DB1A6F98 for <insipid@ietfa.amsl.com>; Sat, 18 Oct 2014 04:22:36 -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 7KSyzklULh4b for <insipid@ietfa.amsl.com>; Sat, 18 Oct 2014 04:22:33 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 6A14D1A6F84 for <insipid@ietf.org>; Sat, 18 Oct 2014 04:22:33 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id C348781A44269; Sat, 18 Oct 2014 11:22:28 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s9IBMV7D000546 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 18 Oct 2014 13:22:31 +0200
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; Sat, 18 Oct 2014 13:22:31 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [Insipid] Working group last call for draft-ietf-insipid-session-id-10
Thread-Index: AQHP6sTJrRn5kQ6zfk+F4mYre0qNyZw1tUDA
Date: Sat, 18 Oct 2014 11:22:30 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B261BB2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <949EF20990823C4C85C18D59AA11AD8B261ADE@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAHBDyN7fz0Scz7CD7gf4u26zR+wcwLmGKbWYpkAY9W-haOsJ9A@mail.gmail.com>
In-Reply-To: <CAHBDyN7fz0Scz7CD7gf4u26zR+wcwLmGKbWYpkAY9W-haOsJ9A@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.41]
Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B261BB2FR712WXCHMBA11zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/l6kXFvBSfWvi0y6Ftvswav030kI
Cc: "insipid@ietf.org" <insipid@ietf.org>
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: Sat, 18 Oct 2014 11:22:36 -0000

--_000_949EF20990823C4C85C18D59AA11AD8B261BB2FR712WXCHMBA11zeu_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Conversely the document has been already well reviewed by a number of membe=
rs of the working group, so I hope we are looking to catch the few people w=
ho might have missed it so far.

Having said that, and this always applies as far as I am concerned, if anyo=
ne is planning to review this, but needs more cycles, then they should send=
 a mail to the chairs indicating when they can complete by, and we will add=
ress it accordingly.

regards

Keith

________________________________
From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: 18 October 2014 12:15
To: DRAGE, Keith (Keith)
Cc: insipid@ietf.org
Subject: Re: [Insipid] Working group last call for draft-ietf-insipid-sessi=
on-id-10

I think a 2 week WGLC, when one of the weeks is the week before the IETF me=
eting draft deadline is a little short.  Most people are focused on getting=
 their own drafts updated and submitted prior to the draft cutoff and most =
likely won't be looking for other drafts to read until after the cutoff.

Regards,
Mary.

On Sat, Oct 18, 2014 at 5:32 AM, DRAGE, Keith (Keith) <keith.drage@alcatel-=
lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
This is a WGLC for draft-ietf-insipid-session-id-10

https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/

Please review and provide comments both editorial and technical, preferably=
 to the list directly, by 1st of November 2014.

It is helpful if comments are given some form of grading, so we can quickly=
 identify the showstoppers from the pure editorial (and those inbetween).

If you have comments as a result of this review that you believe will need =
discussion in Honolulu to resolve, then please attempt to identify those co=
mments early, i.e. within the next few days.

Regards

Keith
Gonzalo

WG cochairs
_______________________________________________
insipid mailing list
insipid@ietf.org<mailto:insipid@ietf.org>
https://www.ietf.org/mailman/listinfo/insipid


--_000_949EF20990823C4C85C18D59AA11AD8B261BB2FR712WXCHMBA11zeu_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta content=3D"MSHTML 6.00.2900.6550" name=3D"GENERATOR">
</head>
<body>
<div dir=3D"ltr" align=3D"left"><span class=3D"215341911-18102014"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Conversely the document has been =
already well reviewed by a number of members of the working group, so I hop=
e we are looking to catch the few people who
 might have missed it so far.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"215341911-18102014"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"215341911-18102014"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Having said that, and this always=
 applies as far as I am concerned, if anyone is planning to review this, bu=
t needs more cycles, then they should send a
 mail to the chairs indicating when they can complete by, and we will addre=
ss it accordingly.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"215341911-18102014"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"215341911-18102014"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">regards</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"215341911-18102014"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"215341911-18102014"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Keith</font></span></div>
<br>
<blockquote dir=3D"ltr" style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDE=
R-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Mary Barnes [mailto:mary.ietf=
.barnes@gmail.com]
<br>
<b>Sent:</b> 18 October 2014 12:15<br>
<b>To:</b> DRAGE, Keith (Keith)<br>
<b>Cc:</b> insipid@ietf.org<br>
<b>Subject:</b> Re: [Insipid] Working group last call for draft-ietf-insipi=
d-session-id-10<br>
</font><br>
</div>
<div></div>
<div dir=3D"ltr">I think a 2 week WGLC, when one of the weeks is the week b=
efore the IETF meeting draft deadline is a little short.&nbsp; Most people =
are focused on getting their own drafts updated and submitted prior to the =
draft cutoff and most likely won't be looking
 for other drafts to read until after the cutoff.&nbsp;
<div>
<div><br>
</div>
<div>Regards,</div>
<div>Mary.</div>
</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Sat, Oct 18, 2014 at 5:32 AM, DRAGE, Keith (K=
eith) <span dir=3D"ltr">
&lt;<a href=3D"mailto:keith.drage@alcatel-lucent.com" target=3D"_blank">kei=
th.drage@alcatel-lucent.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
This is a WGLC for draft-ietf-insipid-session-id-10<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/"=
 target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-insipid-sess=
ion-id/</a><br>
<br>
Please review and provide comments both editorial and technical, preferably=
 to the list directly, by 1st of November 2014.<br>
<br>
It is helpful if comments are given some form of grading, so we can quickly=
 identify the showstoppers from the pure editorial (and those inbetween).<b=
r>
<br>
If you have comments as a result of this review that you believe will need =
discussion in Honolulu to resolve, then please attempt to identify those co=
mments early, i.e. within the next few days.<br>
<br>
Regards<br>
<br>
Keith<br>
Gonzalo<br>
<br>
WG cochairs<br>
_______________________________________________<br>
insipid mailing list<br>
<a href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/insipid" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/insipid</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>

--_000_949EF20990823C4C85C18D59AA11AD8B261BB2FR712WXCHMBA11zeu_--


From nobody Tue Oct 21 07:48:55 2014
Return-Path: <gsalguei@cisco.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 2A50F1A86E7 for <insipid@ietfa.amsl.com>; Tue, 21 Oct 2014 07:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 XsiW9XQ0Qpwi for <insipid@ietfa.amsl.com>; Tue, 21 Oct 2014 07:48:48 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EEC91A6F6D for <insipid@ietf.org>; Tue, 21 Oct 2014 07:48:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1420; q=dns/txt; s=iport; t=1413902912; x=1415112512; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=Cd/KsLjt95GdmaLHhx51cH9G7W+5G2hZ3alnx8GQuj0=; b=C+RGoRUyHTfIqlmABs1gn0KYKxpKUnm75FNU38eGvXq3LpewKh4f2RBh 0iY+aJSvSwHhDxDcinBvKoaZ03RVVcr2FrPmCx9dVrF5Kf/DNEo1LnOmh pxxMii88YIUclBuXIFgXPnIJAwlisaiD0fXDne5vWD/Ho5c+RSlv3WWFS A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFADJxRlStJA2I/2dsb2JhbABcAYMNU1zMJIdNgRMWAXILhAk6PxIBPkInBA4giCQNw2oBAQEBAQEBAQEBAQEBAQEBAQEBAQETBJBRgzSBHgWSAYRGhxOBMINGihCHHIN3gjSBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,762,1406592000"; d="scan'208";a="88997465"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP; 21 Oct 2014 14:48:32 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s9LEmVOp009160 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Oct 2014 14:48:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Tue, 21 Oct 2014 09:48:31 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: INSIPID will not have a meeting at IETF91
Thread-Index: AQHP7T4UpIWM5d4IQ0C/N9NXg7Ofkg==
Date: Tue, 21 Oct 2014 14:48:31 +0000
Message-ID: <BA141347-E1EE-442C-9D8C-B5C8EA0AD8CC@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.250.177]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4FFF3B55A4867A479B7AA44F66200295@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/F9VCFo5bV7O1MpDlt-5LqcqEhvI
Cc: "insipid-chairs@tools.ietf.org" <insipid-chairs@tools.ietf.org>
Subject: [Insipid] INSIPID will not have a meeting at IETF91
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: Tue, 21 Oct 2014 14:48:51 -0000

Folks -

The INSIPID WG will not be meeting in Hawaii.  After discussion with the
authors there do not appear to be any open issues requiring F2F
discussion.=20

We are making good progress on the remaining documents. Below is a=20
status update on the remaining milestones:

- The Session-ID solutions document
(https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/) is in
WGLC after extensive WG review. The WGLC ends November 1st.  There was
a comment on the list that perhaps the proximity to the meeting might
impact folks' ability to devote review cycles to the document, so we can
certainly extend the WGLC period if that is deemed necessary. Please let
us know.

- The 'logme' requirement draft
(https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-reqs/) has
addressed all pending review feedback.  After the Hawaii meeting the
document shepherd will provide a final review in preparation for
WGLC.

- The 'logme' solutions draft
(https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-reqs/) is in
need of further review. The chairs ask the WG to please set aside some
time to provide review feedback on the document.  Additionally, to
accelerate this endeavor Peter Dawes will be explicitly requesting
specific individual to review the document to the list.


Please let the chairs know if you have issues with any of the above.

Thanks,

Gonzalo & Keith


From nobody Fri Oct 24 07:51:42 2014
Return-Path: <brett@broadsoft.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 914A51A0AF1 for <insipid@ietfa.amsl.com>; Fri, 24 Oct 2014 07:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.08
X-Spam-Level: 
X-Spam-Status: No, score=-0.08 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, 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 9kB5uk2diZdx for <insipid@ietfa.amsl.com>; Fri, 24 Oct 2014 07:51:38 -0700 (PDT)
Received: from mail-qc0-f174.google.com (mail-qc0-f174.google.com [209.85.216.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78A3F1A033B for <insipid@ietf.org>; Fri, 24 Oct 2014 07:51:38 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id i8so844421qcq.33 for <insipid@ietf.org>; Fri, 24 Oct 2014 07:51:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=UF9/VhGqhQj3HHZnQ4oKpAqTtideQc3R0Fb9XCKlU08=; b=BD6it+uY6bLsfIYWdMTx144POJARpH+znF7sn/OUyk9MMDOxSfc6eowuxaBf5EAkiX /40GMAtHaUefZQNzn2HLSjZYUN831DINo5tUG22gbnA70GRahp7obDq20zyNeO2JBrlC 114aQWk1mzMhGHnUqYt7VXz/aQGbaMDq4WVgfy7M77852TGO0oMQ28R/9o1u2W2c+QAT 8ZhDmosxElaKPEuheySsuGws1SPFmhv3XsrANbgLQXK9iYVurc1Kh+1Qq12+/4ZqArq7 0tqOQg29smpBOqjls3Ht7UR/d2HOEWBnzhmZR6SSe6JgkDqSFJERdzxWMkTwMNI713DT 0WUA==
X-Gm-Message-State: ALoCoQlk7cgfUZZEuR6pM+qmkTb8jowTj3CkafcPxi2Gw0nwAj7PuXd3yP6/leSicxhCGy8DqIAb
X-Received: by 10.224.152.5 with SMTP id e5mr6531784qaw.48.1414162297101; Fri, 24 Oct 2014 07:51:37 -0700 (PDT)
From: Brett Tate <brett@broadsoft.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac/vmfI0m5CgOzI/QEqXYEBMnGZAtA==
Date: Fri, 24 Oct 2014 10:51:33 -0400
Message-ID: <d643e9d97d38374d7dc5f53ee8281949@mail.gmail.com>
To: draft-ietf-insipid-session-id@tools.ietf.org, insipid@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/P6c1w8t197VBKVD5FIQOusJwWGs
Subject: [Insipid] draft-ietf-insipid-session-id-10: comments
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: Fri, 24 Oct 2014 14:51:40 -0000

Hi,

The following are a few comments concerning
draft-ietf-insipid-session-id-10.

Thanks,
Brett

------

Section 1 paragraph 4: "This procedures" should be "The procedures".

Section 6 paragraph 1: "be used the peer" should be "be used if the peer".

Section 7 paragraph 1: Since proxies cannot alter a Call-ID (without
becoming B2BUA), "proxies and" should potentially be removed from the
first sentence.

Section 7 paragraph 6: Concerning early dialogs, the CANCEL correlates to
the INVITE instead of a specific early dialog.  Thus the paragraph should
likely be reworded to always reflect the INVITE when CANCEL not traversing
a dialog.  For instance if received multiple 18x creating multiple early
dialogs and received Session-IDs {B1, A} and {B2, A}, the current
paragraph appears to recommend that the CANCEL include one of these within
the CANCEL.

Section 7 paragraph 7: Should potentially recommend what should occur when
B2BUA sends re-INVITE without SDP to obtain SDP to setup another session.
More specifically, should the re-INVITE contain a new 3PCC generated UUID?
The other options would be to resurrect the discarded UUID or use the
currently connected session's UUID.

Section 9.1: Concerning the SIP messages, the B2BUA appears to be a proxy.
Thus from a RFC 7092 perspective, I guess that it is a Proxy-B2BUA that
hasn't originated any requests.

Section 9.1: The F3 and F4 Via branch "z9hG4bKnashds8" should instead
reflect INVITE's Via branch.

Section 9.1: The F4 Contact or F5 Request-URI potentially need a different
ip-address (although maybe reflecting missing Record-Route without "lr").
F4 Contact reflects F3 Contact and doesn't match F5 Request-URI.

Section 9.1: Concerning F6, the B2BUA's Via header appears to be missing.
And existing Via should contain a received parameter.

Section 9.2: Should potentially clarify if the REFER is mid-dialog even if
section 9.9 is out-of-dialog REFER.

Section 9.3 bullet 2: I'm glad that the example isn't mandating sending a
request to update the Session-ID after transfer.  However you might want
to reword the last sentence since Alice won't remain "completely unaware"
of the transfer since Alice's device would notice the transfer caused
Session-ID modification when subsequent messaging occurs on the dialog.

Section 9.4 bullet 4: Potentially should clarify why this example is
quickly updating the Session-ID but section 9.3 example does not.

Section 9.8.1 figure 10: What should be the CANCEL session-id if Bob-1 had
sent two 18x creating two early dialogs with Session-IDs {B1x, A} and
{B1y, A}?

Section 10 paragraph 4: "following" should be "follow".

Section 10 paragraph 5: "rules for" should be "rules that".

Section 10 bullets: Some currently start upper case; others currently
start lower case.

Section 10 bullet 7: "include and" should be "include a"

Section 10 last bullet: Should potentially reword the bullet.  I'm not
sure if second sentence is indicating to ignore unknown parameters, remove
unknown parameters, or something else (like reiterating that the above
bullets do not apply to them).

Section 14.2 RFC5589: "RFC 5359" should be "RFC 5589".


From nobody Fri Oct 24 19:35:53 2014
Return-Path: <paulej@packetizer.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 828DC1A1A33 for <insipid@ietfa.amsl.com>; Fri, 24 Oct 2014 19:35:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.002
X-Spam-Level: 
X-Spam-Status: No, score=-1.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 oBhpuZtKIEG4 for <insipid@ietfa.amsl.com>; Fri, 24 Oct 2014 19:35:49 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3382E1A1ADD for <insipid@ietf.org>; Fri, 24 Oct 2014 19:35:49 -0700 (PDT)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s9P2ZkUs006803 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Oct 2014 22:35:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1414204547; bh=yTUxldLqPHdIj8QyHoZIyHzU8j83Yy3exunhUANuzds=; h=From:To:Subject:Date:Message-Id:In-Reply-To:Reply-To:Mime-Version: Content-Type:Content-Transfer-Encoding; b=IfIS5yLtb94xZ1SwsekUpGNXqAu2rEJRqj8Ke+XYK3Ah4jSrA85E9AnZg0Wkwq1zh GZBT7mWx4xlhHqVpKslbMGZ3YI3lSpPpwVUIoxRmdw6vRxbPmbeyv2zYi4ZZNcEnMK YCk+MOXsSErK2CzlVaoXlzTpxFoeJ6t+wK6uDBaU=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Brett Tate" <brett@broadsoft.com>, draft-ietf-insipid-session-id@tools.ietf.org, insipid@ietf.org
Date: Sat, 25 Oct 2014 02:36:05 +0000
Message-Id: <em20d0761c-6a62-43c5-90ec-2407be5915e4@sydney>
In-Reply-To: <d643e9d97d38374d7dc5f53ee8281949@mail.gmail.com>
User-Agent: eM_Client/6.0.21034.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/LxZ3pXqaqiyGWjqQ673n2M2luwg
Subject: Re: [Insipid] draft-ietf-insipid-session-id-10: comments
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
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: Sat, 25 Oct 2014 02:35:51 -0000

Brett,

Thanks for your feedback.  Please see my replies inline:

>Section 1 paragraph 4: "This procedures" should be "The procedures".
Fixed.

>Section 6 paragraph 1: "be used the peer" should be "be used if the=20
>peer".

Fixed.

>Section 7 paragraph 1: Since proxies cannot alter a Call-ID (without
>becoming B2BUA), "proxies and" should potentially be removed from the
>first sentence.

Good catch! Fixed.

>Section 7 paragraph 6: Concerning early dialogs, the CANCEL correlates=20
>to
>the INVITE instead of a specific early dialog. Thus the paragraph=20
>should
>likely be reworded to always reflect the INVITE when CANCEL not=20
>traversing
>a dialog. For instance if received multiple 18x creating multiple early
>dialogs and received Session-IDs {B1, A} and {B2, A}, the current
>paragraph appears to recommend that the CANCEL include one of these=20
>within
>the CANCEL.

I'm not entirely clear on what you're suggesting.  All the current=20
paragraph says is that if an intermediary sends a CANCEL and it doesn't=20
have the value B1, for example, it is to use {A, "null"} as the=20
Session-ID.


>Section 7 paragraph 7: Should potentially recommend what should occur=20
>when
>B2BUA sends re-INVITE without SDP to obtain SDP to setup another=20
>session.
>More specifically, should the re-INVITE contain a new 3PCC generated=20
>UUID?
>The other options would be to resurrect the discarded UUID or use the
>currently connected session's UUID.

What changes in the text are you proposing?  The temporary value would=20
persist until such time as a the 3PCC device learns what the actual UUID=
=20
values are for Alice or Bob.  If a re-INVITE is sent, the 3PCC device=20
would send either the same fabricated UUID to Bob if it does not know=20
Alice's UUID.  Or, it will send Alice's UUID if it knows it.


>Section 9.1: Concerning the SIP messages, the B2BUA appears to be a=20
>proxy.
>Thus from a RFC 7092 perspective, I guess that it is a Proxy-B2BUA that
>hasn't originated any requests.

B2BUAs don't have to originate requests.  This example (and all others=20
that use B2BUA) shows a classic B2BUA.  I don't think it will help to=20
make this clearer introducing a new type of device like "Proxy-B2BUA".


>Section 9.1: The F3 and F4 Via branch "z9hG4bKnashds8" should instead
>reflect INVITE's Via branch.

Fixed

>Section 9.1: The F4 Contact or F5 Request-URI potentially need a=20
>different
>ip-address (although maybe reflecting missing Record-Route without=20
>"lr").
>F4 Contact reflects F3 Contact and doesn't match F5 Request-URI.

I think you're saying that F4 needs to contain a Record-Route header. =20
Correct?
I've added "Record-Route: <sip:server10.biloxi.example.com;lr>"

I think the ACK from Alice to the B2BUA was also wrong.  I've changed=20
that to reflect Bob's address.  That is, the ACK should have:
ACK sip:bob@192.168.10.20 SIP/2.0


>Section 9.1: Concerning F6, the B2BUA's Via header appears to be=20
>missing.
>And existing Via should contain a received parameter.

Fixed (I think; please check the next draft I'll post for this all all=20
other corrections).


>Section 9.2: Should potentially clarify if the REFER is mid-dialog even=
=20
>if
>section 9.9 is out-of-dialog REFER.
OK.  Added a sentence in parentheses.

>  Section 9.3 bullet 2: I'm glad that the example isn't mandating=20
>sending a
>request to update the Session-ID after transfer. However you might want
>to reword the last sentence since Alice won't remain "completely=20
>unaware"
>of the transfer since Alice's device would notice the transfer caused
>Session-ID modification when subsequent messaging occurs on the dialog.

That is certainly true up to this point that Alice would be unaware of=20
the transfer, but you're right that she would become aware in the future=
=20
when she receives a message from Carol.  I tried to make that a little=20
clearer.

>Section 9.4 bullet 4: Potentially should clarify why this example is
>quickly updating the Session-ID but section 9.3 example does not.

I'm not sure what you are referring to here.  Nowhere do we purposely go=
=20
out of the way to update a Session-ID.  Those values are only updated=20
when there is otherwise a reason to send a message.


>Section 9.8.1 figure 10: What should be the CANCEL session-id if Bob-1=20
>had
>sent two 18x creating two early dialogs with Session-IDs {B1x, A} and
>{B1y, A}?

I don't fully understand your question.  However, if there is a single=20
call initiated from Alice to Bob-1, then there would only be {B1} at=20
Bob-1, not {B1x} and a {B1y}.  If you're asking about the case where=20
Alice made two separate calls to Bob-1, then Alice would be using two=20
separate {A1} and {A2} values.

>Section 10 paragraph 4: "following" should be "follow".

Fixed.

>Section 10 paragraph 5: "rules for" should be "rules that".

Fixed.


>Section 10 bullets: Some currently start upper case; others currently
>start lower case.

Fixed.


>Section 10 bullet 7: "include and" should be "include a"

Fixed.


>Section 10 last bullet: Should potentially reword the bullet. I'm not
>sure if second sentence is indicating to ignore unknown parameters,=20
>remove
>unknown parameters, or something else (like reiterating that the above
>bullets do not apply to them).

I tried to fix that.  Please let me know if this is clearer.


>
>Section 14.2 RFC5589: "RFC 5359" should be "RFC 5589".
Fixed it.

Thanks for the very thorough review.  This really helps!

Paul


From nobody Fri Oct 24 19:51:01 2014
Return-Path: <internet-drafts@ietf.org>
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 675511A1B1C; Fri, 24 Oct 2014 19:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 E86581nzhqxc; Fri, 24 Oct 2014 19:50:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 225091A1A8D; Fri, 24 Oct 2014 19:50:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141025025055.27477.9515.idtracker@ietfa.amsl.com>
Date: Fri, 24 Oct 2014 19:50:55 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/4Jfpa6BnvagCRSGbHKqC6eN3G10
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-11.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 25 Oct 2014 02:50:57 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the INtermediary-safe SIP session ID Working Group of the IETF.

        Title           : End-to-End Session Identification in IP-Based Multimedia Communication Networks
        Authors         : Paul E. Jones
                          James Polk
                          Gonzalo Salgueiro
                          Chris Pearce
	Filename        : draft-ietf-insipid-session-id-11.txt
	Pages           : 31
	Date            : 2014-10-24

Abstract:
   This document describes an end-to-end Session Identifier for use in
   IP-based multimedia communication systems that enables endpoints,
   intermediate devices, and management systems to identify a session
   end-to-end, associate multiple endpoints with a given multipoint
   conference, track communication sessions when they are redirected,
   and associate one or more media flows with a given communication
   session.

   This document also describes a backwards compatibility mechanism for
   an existing "in the wild" session identifier implementation that is
   sufficiently different from the procedures defined in this document.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-insipid-session-id-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-session-id-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Oct 25 09:25:05 2014
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 700C41A88EC for <insipid@ietfa.amsl.com>; Sat, 25 Oct 2014 09:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Vcfu5UzigwX0 for <insipid@ietfa.amsl.com>; Sat, 25 Oct 2014 09:24:58 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 087121A88FC for <insipid@ietf.org>; Sat, 25 Oct 2014 09:24:46 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 70C6C90E77300 for <insipid@ietf.org>; Sat, 25 Oct 2014 16:24:41 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s9PGOig7024620 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <insipid@ietf.org>; Sat, 25 Oct 2014 18:24:44 +0200
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; Sat, 25 Oct 2014 18:24:44 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Working group last call for draft-ietf-insipid-session-id-10
Thread-Index: Ac/qvkp4YeX1M6uVTyGkdH2Dq6Q5CAFcdyUA
Date: Sat, 25 Oct 2014 16:24:44 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B268902@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <949EF20990823C4C85C18D59AA11AD8B261ADE@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B261ADE@FR712WXCHMBA11.zeu.alcatel-lucent.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.38]
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/nMLRfJe4VVJsNnLPXM265_K5BpU
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: Sat, 25 Oct 2014 16:25:00 -0000

(as WG co-chair)

I normally prefer to have a single version during the advertised period of =
WGLC, however -11 has "escaped" my control.

Therefore please be aware that WGLC comments are now valid on both the -10 =
and -11 version. If you have reviewed -10, or are in the process of reviewi=
ng -10, then you can submit the comments without checking against, or rerev=
iewing, -11.

A reminder to comment by 1st November, and if you do intend to review but c=
annot meet this deadline, then please inform the chairs, with a date by whi=
ch you could review, and we will take appropriate steps to accommodate you.

Regards

Keith

> -----Original Message-----
> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of=20
> DRAGE, Keith (Keith)
> Sent: 18 October 2014 11:32
> To: insipid@ietf.org
> Subject: [Insipid] Working group last call for=20
> draft-ietf-insipid-session-id-10
>=20
> This is a WGLC for draft-ietf-insipid-session-id-10
>=20
> https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
>=20
> Please review and provide comments both editorial and=20
> technical, preferably to the list directly, by 1st of November 2014.
>=20
> It is helpful if comments are given some form of grading, so=20
> we can quickly identify the showstoppers from the pure=20
> editorial (and those inbetween).
>=20
> If you have comments as a result of this review that you=20
> believe will need discussion in Honolulu to resolve, then=20
> please attempt to identify those comments early, i.e. within=20
> the next few days.
>=20
> Regards
>=20
> Keith
> Gonzalo
>=20
> WG cochairs
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
> =


From nobody Mon Oct 27 09:27:22 2014
Return-Path: <brett@broadsoft.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 E6EFD1A0ABD for <insipid@ietfa.amsl.com>; Mon, 27 Oct 2014 09:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, 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 VJcIgDEexqEM for <insipid@ietfa.amsl.com>; Mon, 27 Oct 2014 09:27:17 -0700 (PDT)
Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E92871A07BC for <insipid@ietf.org>; Mon, 27 Oct 2014 09:27:15 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id z107so2377644qgd.12 for <insipid@ietf.org>; Mon, 27 Oct 2014 09:27:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:content-type; bh=oEO5iyXHHWfQp0c9EAL27f3sg0j7O+yDIJWxYTxg8nY=; b=OzadeLZg6ZMEs0Y4VOV95hGilFEpvDo/JgiDAaYxp3vHW0FxwfB0nCy3mryOx1EB2k I4LLaO30NpRcGfowlpQ2Wvnqrq2+90zT8ezd1zOLqiKVTrM+uYzKiIwsU9t8ZvtNNF6V xGQF2XM52SVOm4m/fMHB9AY5jaRd/2J1IHGzrhTcNLOSc+zNpbZa+59QtBSFgM/OCkbg SaSErbR3AsGNlWpW0e/DpZPsVT4hhRRW6EJIbAXlU18gMM8tA6Cj8SeUvu8q/6dYsS/6 Nyeb9PnwuYC8bXhR9kXbQBuaQyh/zz8ZT1qdmBpZ0z5sKjMIiGPnSkMGTj+PQqCZ/9xd hUmw==
X-Gm-Message-State: ALoCoQn06cxgniRjHbitGzQ1n/p0oQAPiP6rf0lz8Nkc/Vf2qVuxyC1MZnJ22Te6vyPO0NE+UaVv
X-Received: by 10.140.40.99 with SMTP id w90mr32455618qgw.18.1414427235112; Mon, 27 Oct 2014 09:27:15 -0700 (PDT)
From: Brett Tate <brett@broadsoft.com>
References: <d643e9d97d38374d7dc5f53ee8281949@mail.gmail.com> <em20d0761c-6a62-43c5-90ec-2407be5915e4@sydney>
In-Reply-To: <em20d0761c-6a62-43c5-90ec-2407be5915e4@sydney>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGbdhhKQ3DvBXA6l1QrPhU34HqbiZyszd5A
Date: Mon, 27 Oct 2014 12:27:14 -0400
Message-ID: <3649bab698adb60eecad5473bfb80d21@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>, draft-ietf-insipid-session-id@tools.ietf.org, insipid@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/tPQuXoywC0TZWl32TRk1WZ9OeRc
Subject: Re: [Insipid] draft-ietf-insipid-session-id-10: comments
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: Mon, 27 Oct 2014 16:27:20 -0000

Hi,

Thanks for the response; reply is inline.

> >Section 7 paragraph 6: Concerning early dialogs, the CANCEL correlates
> >to the INVITE instead of a specific early dialog. Thus the paragraph
> >should likely be reworded to always reflect the INVITE when CANCEL not
> >traversing a dialog. For instance if received multiple 18x creating
> >multiple early dialogs and received Session-IDs {B1, A} and {B2, A},
> >the current paragraph appears to recommend that the CANCEL include one
> >of these within the CANCEL.
>
> I'm not entirely clear on what you're suggesting.  All the current
> paragraph
> says is that if an intermediary sends a CANCEL and it doesn't have the
> value
> B1, for example, it is to use {A, "null"} as the Session-ID.

I'm indicating that a CANCEL should not reflect early dialog information; it
should reflect the INVITE.  Otherwise you'd be having to select a single
Session-ID from 1 of potentially many early dialogs to place within the
CANCEL (which isn't associated with a specific early dialog).  My comment is
similar to my Section 9.8.1 figure 10 comment.

Current text:

" A CANCEL request sent by an intermediary that has not received a UUID
   from the destination UA MUST construct a Session-ID header value
   exactly like the INVITE to that UA, with the known "local-uuid" value
   for the initiating UA and the null UUID as the "remote-uuid" value
   for the destination UA."

Suggested text: "A CANCEL request sent by an intermediary MUST construct a
Session-ID header value exactly like the INVITE's Session-ID."

Similar text should likely be added to section 6; for instance, maybe after
the next-to-last paragraph which indicates UAs MUST take care concerning
forking interaction.


> >Section 7 paragraph 7: Should potentially recommend what should occur
> >when B2BUA sends re-INVITE without SDP to obtain SDP to setup another
> >session.
> >More specifically, should the re-INVITE contain a new 3PCC generated
> >UUID?
> >The other options would be to resurrect the discarded UUID or use the
> >currently connected session's UUID.
>
> What changes in the text are you proposing?  The temporary value would
> persist until such time as a the 3PCC device learns what the actual UUID
> values are for Alice or Bob.  If a re-INVITE is sent, the 3PCC device
> would send
> either the same fabricated UUID to Bob if it does not know Alice's UUID.
> Or,
> it will send Alice's UUID if it knows it.

The 3PCC device can send a re-INVITE without SDP to Alice to connect Alice
to device X instead of Bob.  X's UUID would be within the Session-ID of
re-INVITE's ACK; however I'm currently not sure what UUID the draft is
recommending the 3PCC to place within re-INVITE.  Allowing the 3PCC device
to do whatever (or interpret however) it wants is okay with me; however I
thought the draft might want to clarify what should occur.

For instance, see RFC 3725 section 10.2 figure 13.  After the Controller
sends re-INVITE to place the Called Party (Bob) on hold, the Controller
sends re-INVITE (message 4) to connect Pre-Paid User (Alice)  to Media
Server (X).  I'm attempting to understand which UUIDs should go within
message 4's Session-ID.


> >Section 9.1: Concerning the SIP messages, the B2BUA appears to be a
> >proxy.
> >Thus from a RFC 7092 perspective, I guess that it is a Proxy-B2BUA that
> >hasn't originated any requests.
>
> B2BUAs don't have to originate requests.  This example (and all others
> that
> use B2BUA) shows a classic B2BUA.  I don't think it will help to make this
> clearer introducing a new type of device like "Proxy-B2BUA".

I was just commenting that the example looked like a proxy instead of a
B2BUA.  However if intentional, that is okay with me.


> >Section 9.1: The F4 Contact or F5 Request-URI potentially need a
> >different ip-address (although maybe reflecting missing Record-Route
> >without "lr").
> >F4 Contact reflects F3 Contact and doesn't match F5 Request-URI.
>
> I think you're saying that F4 needs to contain a Record-Route header.
> Correct?

Yes; unless Record-Route and Route were considered non-essential headers
(and the Request-URI was reflecting B2BUA's Record-Route entry which had no
lr).

Concerning draft-ietf-insipid-session-id-11... if Record-Route and Route are
considered essential, Record-Route should likely be added to F2 and F3; and
Route should likely be added to F5.


> >Section 9.1: Concerning F6, the B2BUA's Via header appears to be
> >missing.
> >And existing Via should contain a received parameter.
>
> Fixed (I think; please check the next draft I'll post for this all
> other corrections).

The fix looks okay to me.


> >Section 9.4 bullet 4: Potentially should clarify why this example is
> >quickly updating the Session-ID but section 9.3 example does not.
>
> I'm not sure what you are referring to here.  Nowhere do we purposely go
> out of the way to update a Session-ID.  Those values are only updated
> when there is otherwise a reason to send a message.

Figure 4 indicates "(to change the UUID to M')" within several locations
when sending re-INVITE.  Similarly section 8 has MUST statements which
appear to require the MCU to update the Session-ID.  Thus if the MCU didn't
otherwise have a need to send the re-INVITE, section 8 appears to require
sending re-INVITE to fix the Session-ID.


> >Section 9.8.1 figure 10: What should be the CANCEL session-id if Bob-1
> >had
> >sent two 18x creating two early dialogs with Session-IDs {B1x, A} and
> >{B1y, A}?
>
> I don't fully understand your question.  However, if there is a single
> call initiated from Alice to Bob-1, then there would only be {B1} at
> Bob-1, not {B1x} and a {B1y}.  If you're asking about the case where
> Alice made two separate calls to Bob-1, then Alice would be using two
> separate {A1} and {A2} values.

See my section 7 paragraph 6 comment.  If it helps, consider situation of
Alice having an outbound B2BUA which sends CANCEL while Bob's B2BUA is using
a simultaneous ringing service (instead of Call Forward No Answer service).
Should Alice's B2BUA include Session-ID {A, B1} or {A, B2} within the CANCEL
sent to Bob's B2BUA?

If I understand correctly, Figure 10 and section 7 paragraph 6 currently
imply that Alice's outbound B2BUA would send CANCEL with Session-ID {A, B1}
or Session-ID {A, B2} instead of Session-ID {A, N}.  I'm suggesting that
Figure 10 and section 7 paragraph 6 potentially be updated to indicate that
Session-ID {A, N} would be sent.


> >Section 10 last bullet: Should potentially reword the bullet. I'm not
> >sure if second sentence is indicating to ignore unknown parameters,
> >remove
> >unknown parameters, or something else (like reiterating that the above
> >bullets do not apply to them).
>
> I tried to fix that.  Please let me know if this is clearer.

Sounds okay to me.


From nobody Tue Oct 28 21:25:30 2014
Return-Path: <paulej@packetizer.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 DF2CA1A6F96 for <insipid@ietfa.amsl.com>; Tue, 28 Oct 2014 21:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.698
X-Spam-Level: *
X-Spam-Status: No, score=1.698 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 TnHLCWbGmrGm for <insipid@ietfa.amsl.com>; Tue, 28 Oct 2014 21:25:25 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 285871A6F63 for <insipid@ietf.org>; Tue, 28 Oct 2014 21:25:25 -0700 (PDT)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s9T4PMLp004058 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 Oct 2014 00:25:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1414556723; bh=DVLdeQGikOmDTeOft3PJIAqPDLh3bHn0e/Vx83WHjFY=; h=From:To:Subject:Date:Message-Id:In-Reply-To:Reply-To:Mime-Version: Content-Type:Content-Transfer-Encoding; b=AjrlCYmybipQuzuqTkEg0o0uy2o0OEhfu4p6NPBj8XMe3Ml2lKjszrv+TVhaETRME urKckH5KSuDqytnnPk9yLKwYdpfTvp3C3fOJwOMci2htcGthBAujn1kHNjQYnNi+8D dSjioHZHv4PtsXU50Mu7OPsA+cFMtuWHZRT0pekk=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Brett Tate" <brett@broadsoft.com>, draft-ietf-insipid-session-id@tools.ietf.org, insipid@ietf.org
Date: Wed, 29 Oct 2014 04:25:28 +0000
Message-Id: <emc5c807ce-4698-40f4-b8b2-1683d5418a09@sydney>
In-Reply-To: <3649bab698adb60eecad5473bfb80d21@mail.gmail.com>
User-Agent: eM_Client/6.0.21034.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/A7W9DYIQJ6dLIaFQSUqYTjwXKQI
Subject: Re: [Insipid] draft-ietf-insipid-session-id-10: comments
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
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: Wed, 29 Oct 2014 04:25:28 -0000

Brett,

Please see my comments below:


>Thanks for the response; reply is inline.
>
>>  >Section 7 paragraph 6: Concerning early dialogs, the CANCEL=20
>>correlates
>>  >to the INVITE instead of a specific early dialog. Thus the paragraph
>>  >should likely be reworded to always reflect the INVITE when CANCEL=20
>>not
>>  >traversing a dialog. For instance if received multiple 18x creating
>>  >multiple early dialogs and received Session-IDs {B1, A} and {B2, A},
>>  >the current paragraph appears to recommend that the CANCEL include=20
>>one
>>  >of these within the CANCEL.
>>
>>  I'm not entirely clear on what you're suggesting. All the current
>>  paragraph
>>  says is that if an intermediary sends a CANCEL and it doesn't have=20
>>the
>>  value
>>  B1, for example, it is to use {A, "null"} as the Session-ID.
>
>I'm indicating that a CANCEL should not reflect early dialog=20
>information; it
>should reflect the INVITE. Otherwise you'd be having to select a single
>Session-ID from 1 of potentially many early dialogs to place within the
>CANCEL (which isn't associated with a specific early dialog). My=20
>comment is
>similar to my Section 9.8.1 figure 10 comment.
>
>Current text:
>
>" A CANCEL request sent by an intermediary that has not received a UUID
>    from the destination UA MUST construct a Session-ID header value
>    exactly like the INVITE to that UA, with the known "local-uuid"=20
>value
>    for the initiating UA and the null UUID as the "remote-uuid" value
>    for the destination UA."
>
>Suggested text: "A CANCEL request sent by an intermediary MUST=20
>construct a
>Session-ID header value exactly like the INVITE's Session-ID."

OK, your text down below made this clearer for me.  I agree we should do=
=20
as you say.


>Similar text should likely be added to section 6; for instance, maybe=20
>after
>the next-to-last paragraph which indicates UAs MUST take care=20
>concerning
>forking interaction.

This is referring to Alice's behavior.  Basically, when she further=20
communicates with Bob-2, for example, she needs to ensure the Session-ID=
=20
header contain's Bob-2's UUID value.  I don't think we want to change=20
that.

In both of the above, I'm not trying to be contrary, by any means. If=20
folks don't think this is the right thing to do, I can change the text. =
=20
  But, it seems odd that we'd have different rules for how the Session-ID=
=20
is populated just because there is an early dialog and it definitely=20
does not fulfill that desire to be able to use it for debugging=20
messages.


>>  >Section 7 paragraph 7: Should potentially recommend what should=20
>>occur
>>  >when B2BUA sends re-INVITE without SDP to obtain SDP to setup=20
>>another
>>  >session.
>>  >More specifically, should the re-INVITE contain a new 3PCC generated
>>  >UUID?
>>  >The other options would be to resurrect the discarded UUID or use=20
>>the
>>  >currently connected session's UUID.
>>
>>  What changes in the text are you proposing? The temporary value would
>>  persist until such time as a the 3PCC device learns what the actual=20
>>UUID
>>  values are for Alice or Bob. If a re-INVITE is sent, the 3PCC device
>>  would send
>>  either the same fabricated UUID to Bob if it does not know Alice's=20
>>UUID.
>>  Or,
>>  it will send Alice's UUID if it knows it.
>
>The 3PCC device can send a re-INVITE without SDP to Alice to connect=20
>Alice
>to device X instead of Bob. X's UUID would be within the Session-ID of
>re-INVITE's ACK; however I'm currently not sure what UUID the draft is
>recommending the 3PCC to place within re-INVITE. Allowing the 3PCC=20
>device
>to do whatever (or interpret however) it wants is okay with me; however=
=20
>I
>thought the draft might want to clarify what should occur.
>
>For instance, see RFC 3725 section 10.2 figure 13. After the Controller
>sends re-INVITE to place the Called Party (Bob) on hold, the Controller
>sends re-INVITE (message 4) to connect Pre-Paid User (Alice) to Media
>Server (X). I'm attempting to understand which UUIDs should go within
>message 4's Session-ID.

Yeah, this is a good point and it's not stated in the draft.   The=20
benefit of using Bob's UUID is that the continuity is maintained.  If we=
=20
use a null UUID for the re-invite, then it's lost.  For message 6,=20
though, that INVITE should be {A,null}.  Message 7 would have {A,Y} (Y=20
=3D=3D Media Server).  Message 8 should have {A,Y}.  That's my opinion. =
 If=20
you agree, would you mind suggesting some words that effectively convey=20
that with brevity?


>>  >Section 9.1: The F4 Contact or F5 Request-URI potentially need a
>>  >different ip-address (although maybe reflecting missing Record-Route
>>  >without "lr").
>>  >F4 Contact reflects F3 Contact and doesn't match F5 Request-URI.
>>
>>  I think you're saying that F4 needs to contain a Record-Route header.
>>  Correct?
>
>Yes; unless Record-Route and Route were considered non-essential=20
>headers
>(and the Request-URI was reflecting B2BUA's Record-Route entry which=20
>had no
>lr).
>
>Concerning draft-ietf-insipid-session-id-11... if Record-Route and=20
>Route are
>considered essential, Record-Route should likely be added to F2 and F3;=
=20
>and
>Route should likely be added to F5.

F2, OK.  But F3 for Record-Route?  Does that message from Bob really=20
need Record-Route?  I appreciate it could be there, but is that=20
essential?

"Route:" in F5, ok.  What about F3 (since Record-Route is now added to=20
F2)?


>>  >Section 9.4 bullet 4: Potentially should clarify why this example is
>>  >quickly updating the Session-ID but section 9.3 example does not.
>>
>>  I'm not sure what you are referring to here. Nowhere do we purposely=
=20
>>go
>>  out of the way to update a Session-ID. Those values are only updated
>>  when there is otherwise a reason to send a message.
>
>Figure 4 indicates "(to change the UUID to M')" within several=20
>locations
>when sending re-INVITE. Similarly section 8 has MUST statements which
>appear to require the MCU to update the Session-ID. Thus if the MCU=20
>didn't
>otherwise have a need to send the re-INVITE, section 8 appears to=20
>require
>sending re-INVITE to fix the Session-ID.

OK, I see why that's not so clear.  The text to which you refer in=20
Figure 4 relates to the fact that the participant called into the MCU=20
and initially had a call with the IVR system.  Once the IVR system was=20
done, a re-INVITE is sent to put the participant to put them into the=20
conference.  That's what the "to change the UUID to M'" text means. =20
However, "to change the UUID" is not the primary motivation for sending=20
that re-INVITE.

We could just remove  the text "(to change the UUID to M')" or change it=
=20
to something else.  I'm not sure what we should change it to that will=20
not be a mile long.  Suggestions?


>>  >Section 9.8.1 figure 10: What should be the CANCEL session-id if=20
>>Bob-1
>>  >had
>>  >sent two 18x creating two early dialogs with Session-IDs {B1x, A}=20
>>and
>>  >{B1y, A}?
>>
>>  I don't fully understand your question. However, if there is a single
>>  call initiated from Alice to Bob-1, then there would only be {B1} at
>>  Bob-1, not {B1x} and a {B1y}. If you're asking about the case where
>>  Alice made two separate calls to Bob-1, then Alice would be using two
>>  separate {A1} and {A2} values.
>
>See my section 7 paragraph 6 comment. If it helps, consider situation=20
>of
>Alice having an outbound B2BUA which sends CANCEL while Bob's B2BUA is=20
>using
>a simultaneous ringing service (instead of Call Forward No Answer=20
>service).
>Should Alice's B2BUA include Session-ID {A, B1} or {A, B2} within the=20
>CANCEL
>sent to Bob's B2BUA?

This bit made it clearer for me.


>If I understand correctly, Figure 10 and section 7 paragraph 6=20
>currently
>imply that Alice's outbound B2BUA would send CANCEL with Session-ID {A,=
=20
>B1}
>or Session-ID {A, B2} instead of Session-ID {A, N}. I'm suggesting that
>Figure 10 and section 7 paragraph 6 potentially be updated to indicate=20
>that
>Session-ID {A, N} would be sent.

OK, I'm sold on this needed change.  We'll have all CANCEL's align with=20
INVITE messages.

Man, I really appreciate you finding these kinds of issues.

Paul

