
From keith.drage@alcatel-lucent.com  Fri Mar  1 10:14:06 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0169221F9010 for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 10:14:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.395
X-Spam-Level: 
X-Spam-Status: No, score=-107.395 tagged_above=-999 required=5 tests=[AWL=-1.146, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rdk4Jvz7SXnw for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 10:13:57 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by ietfa.amsl.com (Postfix) with ESMTP id 27A1A21F900E for <insipid@ietf.org>; Fri,  1 Mar 2013 10:13:56 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r21IDuua030250 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <insipid@ietf.org>; Fri, 1 Mar 2013 19:13:56 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Fri, 1 Mar 2013 19:13:56 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "insipid@ietf.org" <insipid@ietf.org>
Date: Fri, 1 Mar 2013 19:12:16 +0100
Thread-Topic: Call for working group adoption of identifier solution draft
Thread-Index: Ac4UlDroba7PV9ffSRu5+JxUGGPxMACE8KGg
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 18:14:06 -0000

(As WG cochair)

I know the call has only been out a couple of days, but so far there has be=
en absolute silence on this.=20

So this is to indicate that the chairs do need positive responses as well a=
s negative ones.=20

If we get no responses we'll just assume no one is interested, with the app=
ropriate consequences.

Keith

> -----Original Message-----
> From: DRAGE, Keith (Keith)
> Sent: 27 February 2013 02:44
> To: insipid@ietf.org
> Subject: Call for working group adoption of identifier solution draft
>=20
> (As working group cochair)
>=20
> This is a call for the adoption of the text of the draft
>=20
> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>=20
> as a working group draft to meet the milestone
>=20
> Specification of the new identifier sent to the IESG (PS)
>=20
> Please respond as to whether the draft is acceptable or not. You may also
> respond that certain parts are acceptable, or that parts are not
> acceptable (please be specific).
>=20
> This is currently the only text we have on the table to meet the mileston=
e
> and there seems to be some measure of convergence on this text at the
> Atlanta meeting.
>=20
> We will make a decision based on the responses received by Tuesday 12th
> March (i.e. Tuesday of the IETF meeting week).
>=20
> Regards
>=20
> Keith

From jmpolk@cisco.com  Fri Mar  1 10:33:25 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F76C21F93F5 for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 10:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.447
X-Spam-Level: 
X-Spam-Status: No, score=-110.447 tagged_above=-999 required=5 tests=[AWL=0.152, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id refk0MSWVB4H for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 10:33:24 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 8E96621F936D for <insipid@ietf.org>; Fri,  1 Mar 2013 10:33:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1772; q=dns/txt; s=iport; t=1362162804; x=1363372404; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=61pZGbRxAeTqykabZod3lwsx6Qy56Q58+XxEbUyx3g0=; b=HEWhGl7u+LBUMpEc1CEYG/ymdeZuL2qFBG/Nf6AAt7F89Ox2CpVJv7e5 UVTyHkkhugbZ3m2hEEku6GpN8jWtj1Ym5lzmjZpHKOk/H70BiKyBFyp8W kkQVb8EPBDUiDVA1TFoGPebBmhKWUSAkzQR529sZpfCoso6vgBf6LaZ/G Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAIDzMFGtJXG+/2dsb2JhbABEAcI7fxZzgh8BAQEEAQEBGhsCNAsMBAcEEQQBAQEJFRAPCg4oCAYTCRKHeAzBH41NgUULBwaCWWEDiGueQ4MngUs
X-IronPort-AV: E=Sophos;i="4.84,762,1355097600"; d="scan'208";a="182734572"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-2.cisco.com with ESMTP; 01 Mar 2013 18:33:23 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r21IXMXD006999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Mar 2013 18:33:22 GMT
Message-Id: <201303011833.r21IXMXD006999@rcdn-core2-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 01 Mar 2013 12:33:22 -0600
To: "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3. dc-m.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 18:33:25 -0000

I find this document meets the objectives of the milestone, with 
little or no changes of note necessary. Thus IMO the document has 
exceeded the bar to reach for WG adoption.

James

At 12:12 PM 3/1/2013, DRAGE, Keith (Keith) wrote:
>(As WG cochair)
>
>I know the call has only been out a couple of days, but so far there 
>has been absolute silence on this.
>
>So this is to indicate that the chairs do need positive responses as 
>well as negative ones.
>
>If we get no responses we'll just assume no one is interested, with 
>the appropriate consequences.
>
>Keith
>
> > -----Original Message-----
> > From: DRAGE, Keith (Keith)
> > Sent: 27 February 2013 02:44
> > To: insipid@ietf.org
> > Subject: Call for working group adoption of identifier solution draft
> >
> > (As working group cochair)
> >
> > This is a call for the adoption of the text of the draft
> >
> > http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
> >
> > as a working group draft to meet the milestone
> >
> > Specification of the new identifier sent to the IESG (PS)
> >
> > Please respond as to whether the draft is acceptable or not. You may also
> > respond that certain parts are acceptable, or that parts are not
> > acceptable (please be specific).
> >
> > This is currently the only text we have on the table to meet the milestone
> > and there seems to be some measure of convergence on this text at the
> > Atlanta meeting.
> >
> > We will make a decision based on the responses received by Tuesday 12th
> > March (i.e. Tuesday of the IETF meeting week).
> >
> > Regards
> >
> > Keith
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
>https://www.ietf.org/mailman/listinfo/insipid


From paulej@packetizer.com  Fri Mar  1 10:56:21 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17A221E803F for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 10:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vllvMEKaGcUe for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 10:56:21 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id D39D721E8037 for <insipid@ietf.org>; Fri,  1 Mar 2013 10:56:20 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r21IuEfw027813 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 1 Mar 2013 13:56:14 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362164174; bh=KzdYFsiuZ7YJJaRMFt3dAcjHwSwze+2e+rLWEPqhzzc=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=UfGyvzwEfIUhZRp2tMCkEcrBBM5zh+QwMOha134ket5ITF+0xM2Cpn+ADzBj9tXvD B+RTcJgohl0fQiiHIr+Igh0J77hLjyw7qdK807D3kgemXIVaDHinFIqjjtvCI64mtP RiuTpOQs8Yn0HJ2+3OTqVCgk/oJB+v4GbCpwdlgQ=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'James Polk'" <jmpolk@cisco.com>, <insipid@ietf.org>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <201303011833.r21IXMXD006999@rcdn-core2-3.cisco.com>
In-Reply-To: <201303011833.r21IXMXD006999@rcdn-core2-3.cisco.com>
Date: Fri, 1 Mar 2013 13:56:20 -0500
Message-ID: <00ec01ce16ae$767b5d80$63721880$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJuaSUV+NOtPvpM4naipBRn6dgJLAJlPMNPlz1ggsA=
Content-Language: en-us
Cc: "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 18:56:22 -0000

I assume it goes without saying that the co-authors are supportive.  I
certainly support the move.

Paul

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> Behalf Of James Polk
> Sent: Friday, March 01, 2013 1:33 PM
> To: insipid@ietf.org
> Cc: DRAGE, Keith (Keith)
> Subject: Re: [Insipid] Call for working group adoption of identifier
> solution draft
> 
> I find this document meets the objectives of the milestone, with little
> or no changes of note necessary. Thus IMO the document has exceeded the
> bar to reach for WG adoption.
> 
> James
> 
> At 12:12 PM 3/1/2013, DRAGE, Keith (Keith) wrote:
> >(As WG cochair)
> >
> >I know the call has only been out a couple of days, but so far there
> >has been absolute silence on this.
> >
> >So this is to indicate that the chairs do need positive responses as
> >well as negative ones.
> >
> >If we get no responses we'll just assume no one is interested, with the
> >appropriate consequences.
> >
> >Keith
> >
> > > -----Original Message-----
> > > From: DRAGE, Keith (Keith)
> > > Sent: 27 February 2013 02:44
> > > To: insipid@ietf.org
> > > Subject: Call for working group adoption of identifier solution
> > > draft
> > >
> > > (As working group cochair)
> > >
> > > This is a call for the adoption of the text of the draft
> > >
> > > http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
> > >
> > > as a working group draft to meet the milestone
> > >
> > > Specification of the new identifier sent to the IESG (PS)
> > >
> > > Please respond as to whether the draft is acceptable or not. You may
> > > also respond that certain parts are acceptable, or that parts are
> > > not acceptable (please be specific).
> > >
> > > This is currently the only text we have on the table to meet the
> > > milestone and there seems to be some measure of convergence on this
> > > text at the Atlanta meeting.
> > >
> > > We will make a decision based on the responses received by Tuesday
> > > 12th March (i.e. Tuesday of the IETF meeting week).
> > >
> > > Regards
> > >
> > > Keith
> >_______________________________________________
> >insipid mailing list
> >insipid@ietf.org
> >https://www.ietf.org/mailman/listinfo/insipid
> 
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From rjsparks@nostrum.com  Fri Mar  1 12:17:54 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDCA21E8053 for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 12:17:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.588
X-Spam-Level: 
X-Spam-Status: No, score=-101.588 tagged_above=-999 required=5 tests=[AWL=-0.962, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_46=1, OBFUSCATING_COMMENT=0.973, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrgP50Y6jrZO for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 12:17:52 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2B121F8BD4 for <insipid@ietf.org>; Fri,  1 Mar 2013 12:17:51 -0800 (PST)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r21KHnCg000987 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 1 Mar 2013 14:17:49 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <51310CEC.1070907@nostrum.com>
Date: Fri, 01 Mar 2013 14:17:48 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>
References: <055801cdeed9$8b441060$a1cc3120$@packetizer.com> <5F864ABC-E17F-44C9-8CDE-D6C5A32BF214@cisco.com> <92B7E61ADAC1BB4F941F943788C0882804728936@xmb-aln-x08.cisco.com> <50F07742.3030601@alum.mit.edu> <0a0e01ce10a7$875a0690$960e13b0$@packetizer.com> <512965C1.2090204@alum.mit.edu> <55fa36b1-465e-40e0-b875-90fb48f3fc13@email.android.com> <5129B6AD.6010306@alum.mit.edu> <fab2d64c-7f69-4575-a372-15d78237e667@email.android.com>
In-Reply-To: <fab2d64c-7f69-4575-a372-15d78237e667@email.android.com>
Content-Type: multipart/alternative; boundary="------------040400000502080705090606"
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: insipid@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [Insipid] Are we ready to LC on the requirements?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 20:17:54 -0000

This is a multi-part message in MIME format.
--------------040400000502080705090606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 2/24/13 8:38 AM, Paul E. Jones wrote:
> Paul,
>
> That still begs the question of "what language do we need to add or 
> change to make this clear?" In my mind, I know exactly what an 
> endpoint needs to do and what an SBC needs to do. But, I'll not say it 
> does not need more charity for those that do not have it clear in 
> their minds.
>
> But, perhaps being too close to the work, I'm having trouble seeing 
> where it is vague. Can you suggest text?
This is frustrating, for both of us probably. I've read the latest 
requirement document and it doesn't yet clearly
answer the questions I asked in the Atlanta meeting. I feel like I've 
asked them at several meetings before.
Can we stop that cycle of repeating the discussion by putting text in 
the document that directly answers each of these:

In a scenario where you only have one parallel forking SIP proxy, when 
an INVITE forks to two different
UAs and _both_ send 200 OKs, do you have one session or two? (This same 
question applies to early dialogs,
with or without early media, which is a _normal_ condition, not an race 
condition like multiple 200 OKs).

If you replace that with a _serial_ forking proxy, where you were in an 
early dialog with UA1, that got canceled
and then you ended up in an early dialog, and then a confirmed dialog 
with UA2, was that one session (with the
calling UA, UA1, and UA2 involved) or two sessions (one with the calling 
UA and UA1, the other with the calling
UA and UA2)?

If you replace that with a B2BUA that behaves similar to a serial 
forking proxy in that it only alerts one called thing
at a time, do you end up with one session or with two.

I don't see how the current document answers those questions. If I've 
missed that, please point to it and I'll see how
I can help make them more obvious.

Otherwise, can you please make the answers clear in the document, (not 
just in an email response).
>
> Paul
>
> ------------------------------------------------------------------------
> *From:* Paul Kyzivat <pkyzivat@alum.mit.edu>
> *Sent:* Sun Feb 24 01:43:57 EST 2013
> *To:* "Paul E. Jones" <paulej@packetizer.com>
> *Cc:* insipid@ietf.org
> *Subject:* Re: [Insipid] Are we ready to LC on the requirements?
>
> On 2/24/13 12:33 AM, Paul E. Jones wrote:
>
>     Paul, So what concept is vague? In terms of an H.323 device, I
>     would consider two terminals with users at each end to be a
>     communication session. I would consider a terminal and an MCU to
>     have a communication session. The collection of communication
>     sessions on an MCU to which one or more terrminals are a party is
>     a conference. And I would like to relate all those sessions by the
>     UUID the MCU uses in each of those sessions. That value could even
>     be the Conference ID in H.323. There are gateway devices that
>     connect to the PSTN that I would count as equal to a terminal.
>     But, there are gateway devices that bridge IP networks (SBCs) that
>     shoul! d just pass the UUIDs through. The difference between the
>     two really is whether it bridges an IPMC device to another or to
>     something else. There are call flows like the one you highlighted
>     in the threads where voice comes from one terminal and video from
>     another. That's an MCU, really. The session ID exists between
>     Alice and MCU (or PBX). The other devices Bob uses might share the
>     UUID of the MCU/PBX, but those are distinct communication sessions
>     like the typical MCU case. Yeah, such topologies do make it hard
>     to do debugging and the number of UUIDs makes it a pain, too, but
>     at least there is consistency in the assignments. So, it is
>     doable. So, how can we make progress here?
>
>
> We write some rules that any device that terminates more than one dialog
> can use to decide when one dialog should share a session-id with another
> dialog. The rules should get the "right" answer for all the use case!
>   s,
> and should be specific enough so that when applied to any device, no
> matter how weird, most reasonable people would agree with the answer.
> That way we can have a way of judging conformance to this specification.
>
> I realize this bridges the gap between what the requirements are
> responsible for and what the mechanism is responsible for. But the
> mechanism is about marking communications sessions, not defining them.
>
> OR I suppose the requirements could kick the can down the road, simply
> say that the mechanism must work for the specified use cases and itself
> must specify the algorithm for making the decision in other cases. But
> that just puts it off.
>
>   Thanks,
>   Paul K
>
>     Paul
>     ------------------------------------------------------------------------
>     *From:* Paul Kyzivat <pkyzivat@alum.mit.edu> *Sent:* Sat F! eb 23
>     19:58:41 EST 2013 *To:* "Paul E. Jones" <paulej@packetizer.com>
>     *Cc:* insipid@ietf.org *Subject:* Re: [Insipid] Are we ready to LC
>     on the requirements? On 2/21/13 9:51 PM, Paul E. Jones wrote:
>     Paul, I read your message, but was left unsure of exactly how we
>     could improve the definition over what we have already. If there
>     is something concrete that you can propose that would help lend to
>     clarity of the text, I'm definitely willing to put it in. I would
>     like to move the requirements along and the submission deadline is
>     Monday. Do you have text you would like to add before the
>     deadline? I'm traveling on business and have limited internet
>     access, and limited time, so I probably can't. In any case, ISTM
>     that the problem isn't that we don't have the right words. Rather,
>     we still don't have clear *concepts* that distinguish ! whatshould
>     be covered from what should not. We have some use cases, but lack
>     basic principles that can be applied to any case to determine if
>     it should be a communication session or not. It still seems to be
>     more in the realm of "I know one when I see it." If we had the
>     principles, then it would probably be straightforward to come up
>     with words. I don't yet see a suitable general principle here that
>     fits the use cases and seems to make sense. Thanks, Paul Paul
>     -----Original Message----- From: insipid-bounces@ietf.org
>     [mailto:insipid-bounces@ietf.org] On Behalf Of Paul Kyzivat Sent:
>     Friday, January 11, 2013 3:34 PM To: insipid@ietf.org Subject: Re:
>     [Insipid] Are we ready to LC on the requirements? (Sorry that this
>     is long. I don't know how to make it short.) Are we ready to LC? I
>     don't think so. Specifically I don't think we yet have an
>     unambiguous definition of what is being identified. This version
>     added some new text: In this document, the word "session" refers
>     to a "communication session" that may exist between two SIP user
>     agents and that may pass through one or more intermediary devices,
>     including B2BUAs or SIP proxies. A communication session consists
>     of one of more SIP transactions. A very simple communication
>     session may be a single out-of-dialog SIP transaction (e.g.,
>     MESSAGE/200). In the case of a SIP dialog, the SIP message
>     exchange includes a dialog creating INVITE transaction, and zero
>     of more subsequent SIP transactions within the same dialog (e.g.,
>     ACK, re-INVITE, BYE). Due to the existenc! e of middle boxes,
>     there may be multiple related SIP transactions or dialogs chained
>     together along the path from one end of the communication session
>     to the other. For example: A Middlebox B SIP trans1
>     -----------------> SIP trans 2 SIP dialog 1 <-------------- SIP
>     dialog 2 Figure 1 - Communication Session through a Middlebox In
>     such cases, the two SIP transactions or dialogs are part of a
>     single communication session. The term "end-to-end" in this
>     document means the communication session from the point of origin,
>     passing through any number of intermediaries, to the ultimate
>     point of termination. It is recognized that legacy devices may not
>     support the "end-to-end" session identifier, though an identifier
>     might be created by an intermediary when it is absent from the
>     session signaling. IMO this is a big improvement. But it still
>     isn't as prec! ise as I would like. What I find lacking in the
>     above is: o parsing the above, the properties of a communication
>     session are: - connects *two* UAs - optionally includes one or
>     more intermediary devices - one or more transactions - one
>     out-of-dialog transaction, OR a dialog including the dialog
>     establishing transaction and some transactions within the dialog.
>     - middle boxes may result in chaining dialogs or transactions.
>     Exactly how all these properties "plug together" fuzzy. I'm not at
>     all certain that all readers would reach the same conclusion about
>     which cases meet these criteria and which don't. o I'm also not
>     certain that these criteria match all the cases people expect, and
>     exclude all the cases people think should be excluded. - I think
>     people expect that a conference is *not* a single communications
>     session. But a conference with only two participants would! seem
>     to qualify according to all of the above criteria. So that
>     suggests that another criterion is needed to exclude that case. -
>     A topologically similar case to the conference is a click-to-dial
>     case where a web! server makes outward INVITEs to two UAs and
>     connects them. I think people believe this case *should* be a
>     communications session. - Another case is described in
>     http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html
>     and debated in the replies to that. Arguments are made for
>     different answers to what should get a common session id and what
>     should not. For this case I think we need to decide: . do we
>     mandate exactly how this should be treated? . or do we leave it to
>     the discretion of the B2BUA to decide? Either way we need to
>     decide what the criteria are that lead to the decision. o! IIRC
>     Hadriel suggested (in a meeting?) that where media originates and
>     terminates has something to do with this. That doesn't work all
>     the time (e.g. MESSAGE), but it might help in some cases. I think
>     he used this to just! ify that: - the Conference Bridge
>     Transcoding Model (RFC5369 section 3.2) is a single communications
>     session. - the 3PCC Transcoding Model (RFC5369 section 3.1) is
>     *not* a single communications session. (I'm not convinced - this
>     seems like a distinction without a difference.) Fundamentally we
>     should be able to classify all cases into: - those that *should*
>     be communications sessions, - those that *shouldn't* be
>     communication sessions, - those we don't care about - could be
>     either way. When we are done, we should be able to apply the
>     definition of communication session to any case. When applied to
>     the cases we explicitly care about it should deliver the an! swer
>     we expect. The more weird cases we care about, the more complex
>     and unintuitive the criteria will be. I suspect that the path we
>     are on will lead to complex criteria. (We can have a really crisp
>     de! finition of communications session if we don't care much about
>     which cases qualify.) One idea I considered is to define some new
>     terms that build on normal sip concepts but extend them to allow
>     B2BUA intermediaries where sip allows proxies. E.g. -
>     Transaction++ is either a sip transaction, or a series of sip
>     transactions linked by B2BUA intermediaries. - Dialog++ is either
>     a sip dialog, or a series of sip dialogs linked by B2BUA
>     intermediaries. Then would need to define the behavior of a B2BUA
>     intermediary. It needs to relay transactions from one "side" to
>     the other, preserving certain invariants (TBD). Presumably it can
>     also originate certain transactions, but there must be constraints
>     ! on what it can do. There must also be some rules on how media is
>     handled across one of these intermediaries. If that was done, then
>     a communication session could be defined as a Transaction++ for an
>     out-of-dialog request, or a Dialog++. But that makes the
>     definition of communication session the first priority and the
>     cases that happen to qualify as a communication session a
>     consequence. It probably won't match people's intuitive feelings
>     about what *should* be a communication session. So it might not
>     satisfy people. Thanks, Paul On 1/10/13 6:04 PM, Charles Eckel
>     (eckelcu) wrote: From my point of view, the draft looks good. The
>     changes incorporated in this updated version directly address this
>     open issue. Cheers, Charles -----Original Message----- From:
>     insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
>     Behalf Of Gonzalo Salgueiro (gsalguei) Sent: Thursday, January 10,
>     2013 12:39 PM To: Paul E. Jones Cc: insipid@ietf.org Subject: Re:
>     [Insipid] Are we ready to LC on the requirements? Thanks for
>     submitting this, Paul. The biggest open issue in regards to the
>     requirements document was to clearly define what it is we are
>     identifying (i.e., "communication session") within the scope of
>     this document and ensure that clearly defined language is used
>     consistently through! out the document. Prior to any consensus on
>     moving to WGLC, the chairs would appreciate hearing the group's
>     thoughts on where we are on this issue in the current version.
>     Cheers, Gonzalo & Keith On Jan 9, 2013, at 9:23 PM, Paul E. Jones
>     wrote: Folks, Dialog has been extremely light on the requirements
>     document. Do people feel generally OK with it as it is now? Can we
>     move on to the solution document now or are there other changes
>     needed in the requirements document? I just posted the -04 versi!
>     on with changes proposed on the list over the past month or so. Paul
>     ------------------------------------------------------------------------
>     insipid mailing list insipid@ietf.org
>     https://www.ietf.org/mailman/listinfo/insipid
>     ------------------------------------------------------------------------
>     insipid mailing list insipid@ietf.org
>     https://www.ietf.org/mailman/listinfo/insipid
>     ------------------------------------------------------------------------
>     insipid mailing list insipid@ietf.org
>     https://www.ietf.org/mailman/listinfo/insipid
>     ------------------------------------------------------------------------
>     insipid mailing list insipid@ietf.org
>     https://www.ietf.org/mailman/listinfo/insipid
>     ------------------------------------------------------------------------
>     insipid mailing list insipid@ietf.org
>     https://www.ietf.org/mailman/listinfo/insipid
>
>
>
>
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


--------------040400000502080705090606
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 2/24/13 8:38 AM, Paul E. Jones
      wrote:<br>
    </div>
    <blockquote
      cite="mid:fab2d64c-7f69-4575-a372-15d78237e667@email.android.com"
      type="cite">Paul,<br>
      <br>
      That still begs the question of "what language do we need to add
      or change to make this clear?" In my mind, I know exactly what an
      endpoint needs to do and what an SBC needs to do. But, I'll not
      say it does not need more charity for those that do not have it
      clear in their minds.<br>
      <br>
      But, perhaps being too close to the work, I'm having trouble
      seeing where it is vague. Can you suggest text?<br>
    </blockquote>
    This is frustrating, for both of us probably. I've read the latest
    requirement document and it doesn't yet clearly<br>
    answer the questions I asked in the Atlanta meeting. I feel like
    I've asked them at several meetings before.<br>
    Can we stop that cycle of repeating the discussion by putting text
    in the document that directly answers each of these:<br>
    <br>
    In a scenario where you only have one parallel forking SIP proxy,
    when an INVITE forks to two different<br>
    UAs and _both_ send 200 OKs, do you have one session or two? (This
    same question applies to early dialogs,<br>
    with or without early media, which is a _normal_ condition, not an
    race condition like multiple 200 OKs).<br>
    <br>
    If you replace that with a _serial_ forking proxy, where you were in
    an early dialog with UA1, that got canceled<br>
    and then you ended up in an early dialog, and then a confirmed
    dialog with UA2, was that one session (with the<br>
    calling UA, UA1, and UA2 involved) or two sessions (one with the
    calling UA and UA1, the other with the calling<br>
    UA and UA2)?<br>
    <br>
    If you replace that with a B2BUA that behaves similar to a serial
    forking proxy in that it only alerts one called thing<br>
    at a time, do you end up with one session or with two.<br>
    <br>
    I don't see how the current document answers those questions. If
    I've missed that, please point to it and I'll see how<br>
    I can help make them more obvious.<br>
    <br>
    Otherwise, can you please make the answers clear in the document,
    (not just in an email response).<br>
    <blockquote
      cite="mid:fab2d64c-7f69-4575-a372-15d78237e667@email.android.com"
      type="cite">
      <br>
      Paul<br>
      <br>
      <div
        style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;padding:3.0pt
        0in 0in 0in">
        <hr style="border:none;border-top:solid #B5C4DF 1.0pt">
        <b>From:</b> Paul Kyzivat <a class="moz-txt-link-rfc2396E" href="mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a><br>
        <b>Sent:</b> Sun Feb 24 01:43:57 EST 2013<br>
        <b>To:</b> "Paul E. Jones" <a class="moz-txt-link-rfc2396E" href="mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a><br>
        <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a><br>
        <b>Subject:</b> Re: [Insipid] Are we ready to LC on the
        requirements?<br>
      </div>
      <br>
      <pre style="white-space: pre-wrap; word-wrap:break-word; font-family: monospace; margin-top: 0px">On 2/24/13 12:33 AM, Paul E. Jones wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Paul,

So what concept is vague?

In terms of an H.323 device, I would consider two terminals with users
at each end to be a communication session. I would consider a terminal
and an MCU to have a communication session.

The collection of communication sessions on an MCU to which one or more
terrminals are a party is a conference. And I would like to relate all
those sessions by the UUID the MCU uses in each of those sessions. That
value could even be the Conference ID in H.323.

There are gateway devices that connect to the PSTN that I would count as
equal to a terminal. But, there are gateway devices that bridge IP
networks (SBCs) that shoul!
 d just
pass the UUIDs through. The difference
between the two really is whether it bridges an IPMC device to another
or to something else.

There are call flows like the one you highlighted in the threads where
voice comes from one terminal and video from another. That's an MCU,
really. The session ID exists between Alice and MCU (or PBX). The other
devices Bob uses might share the UUID of the MCU/PBX, but those are
distinct communication sessions like the typical MCU case. Yeah, such
topologies do make it hard to do debugging and the number of UUIDs makes
it a pain, too, but at least there is consistency in the assignments.
So, it is doable.

So, how can we make progress here?</blockquote>
We write some rules that any device that terminates more than one dialog 
can use to decide when one dialog should share a session-id with another 
dialog. The rules should get the "right" answer for all the use case!
 s, 
and should be specific enough so that when applied to any device, no 
matter how weird, most reasonable people would agree with the answer. 
That way we can have a way of judging conformance to this specification.

I realize this bridges the gap between what the requirements are 
responsible for and what the mechanism is responsible for. But the 
mechanism is about marking communications sessions, not defining them.

OR I suppose the requirements could kick the can down the road, simply 
say that the mechanism must work for the specified use cases and itself 
must specify the algorithm for making the decision in other cases. But 
that just puts it off.

 Thanks,
 Paul K

<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Paul



<hr>
*From:* Paul Kyzivat <a class="moz-txt-link-rfc2396E" href="mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a>
*Sent:* Sat F!
 eb 23
19:58:41 EST 2013
*To:* "Paul E. Jones" <a class="moz-txt-link-rfc2396E" href="mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a>
*Cc:* <a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
*Subject:* Re: [Insipid] Are we ready to LC on the requirements?

On 2/21/13 9:51 PM, Paul E. Jones wrote:

Paul,

I read your message, but was left unsure of exactly how we could
improve the
definition over what we have already.

If there is something concrete that you can propose that would help
lend to
clarity of the text, I'm definitely willing to put it in. I would
like to
move the requirements along and the submission deadline is Monday.
Do you
have text you would like to add before the deadline?


I'm traveling on business and have limited internet access, and limited
time, so I probably can't.

In any case, ISTM that the problem isn't that we don't have the right
words. Rather, we still don't have clear *concepts* that distinguish
!
what<!--
 br
/-->should be covered from what should not. We have some use cases, but
lack basic principles that can be applied to any case to determine if it
should be a communication session or not. It still seems to be more in
the realm of "I know one when I see it."

If we had the principles, then it would probably be straightforward to
come up with words.

I don't yet see a suitable general principle here that fits the use
cases and seems to make sense.

Thanks,
Paul

Paul

-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org</a>] On
Behalf Of Paul Kyzivat
Sent: Friday, January 11, 2013 3:34 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
Subject: Re: [Insipid] Are we ready to LC on the requirements?

(Sorry that this is long. I don't know how to make it short.)

Are we ready to LC? I don't think so. Specifically I don't think
we yet
have an
unambiguous definition of what is being identified.

This version added some new text:

In this document, the word "session" refers to a "communication
session" that may exist between two SIP user agents and that may
pass
through one or more intermediary devices, including B2BUAs or SIP
proxies. A communication session consists of one of more SIP
transactions. A very simple communication session may be a single
out-of-dialog SIP transaction (e.g., MESSAGE/200). In the case of a
SIP dialog, the SIP message exchange includes a dialog creating
INVITE transaction, and zero of more subsequent SIP transactions
within the same dialog (e.g., ACK, re-INVITE, BYE). Due to the
existenc! e of middle boxes, there may be multiple related SIP
transactions or dialogs chained together along the path from one end
of the communication session to the other. For example:

A Middlebox B
SIP trans1
-----------------&gt; SIP trans 2
SIP dialog 1 &lt;-------------- SIP dialog 2

Figure 1 - Communication Session through a Middlebox

In such cases, the two SIP transactions or dialogs are part of a
single communication session.

The term "end-to-end" in this document means the communication
session from the point of origin, passing through any number of
intermediaries, to the ultimate point of termination. It is
recognized that legacy devices may not support the "end-to-end"
session identifier, though an identifier might be created by an
intermediary when it is absent from the session signaling.

IMO this is a big improvement. But it still isn't as prec! ise
as I would
like. What I find lacking in the above is:

o parsing the above, the properties of a communication session are:
- connects *two* UAs
- optionally includes one or more intermediary devices
- one or more
transactions
- one out-of-dialog transaction,
OR a dialog including the dialog establishing transaction
and some transactions within the dialog.
- middle boxes may result in chaining dialogs or transactions.

Exactly how all these properties "plug together" fuzzy.
I'm not at all certain that all readers would reach
the same conclusion about which cases meet these criteria
and which don't.

o I'm also not certain that these criteria match all the cases
people expect, and exclude all the cases people think should
be excluded.

- I think people expect that a conference is *not* a single
communications session. But a conference with only two
participants would! seem to qualify according to all of the
above criteria. So that suggests that another criterion is
needed to exclude that case.

- A topologically similar case to the conference is a
click-to-dial case where a web!
  server
makes outward INVITEs
to two UAs and connects them. I think people believe this
case *should* be a communications session.

- Another case is described in
<a moz-do-not-send="true" href="http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html">http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html</a>
and debated in the replies to that. Arguments are made for
different answers to what should get a common session id and what
should not. For this case I think we need to decide:
. do we mandate exactly how this should be treated?
. or do we leave it to the discretion of the B2BUA to decide?

Either way we need to decide what the criteria are that lead
to the decision.

o! IIRC Hadriel suggested (in a meeting?) that where media
originates and terminates has something to do with this.
That doesn't work all the time (e.g. MESSAGE), but it might help
in some cases. I think he used this to just!
 ify
that:

- the Conference Bridge Transcoding Model (RFC5369 section 3.2)
is a single communications session.

- the 3PCC Transcoding Model (RFC5369 section 3.1) is *not*
a single communications session.

(I'm not convinced - this seems like a distinction without
a difference.)

Fundamentally we should be able to classify all cases into:
- those that *should* be communications sessions,
- those that *shouldn't* be communication sessions,
- those we don't care about - could be either way.

When we are done, we should be able to apply the definition of
communication session to any case. When applied to the cases we
explicitly care about it should deliver the an! swer we expect.

The more weird cases we care about, the more complex and
unintuitive the
criteria will be. I suspect that the path we are on will lead to
complex
criteria. (We can have a really crisp de!
 finition
of communications
session if we don't care much about which cases qualify.)

One idea I considered is to define some new terms that build on
normal
sip concepts but extend them to allow B2BUA intermediaries where sip
allows proxies. E.g.
- Transaction++ is either a sip transaction, or a series of sip
transactions linked by B2BUA intermediaries.

- Dialog++ is either a sip dialog, or a series of sip dialogs
linked by B2BUA intermediaries.

Then would need to define the behavior of a B2BUA intermediary.
It needs
to relay transactions from one "side" to the other, preserving
certain
invariants (TBD). Presumably it can also originate certain
transactions,
but there must be constraints ! on what it can do. There must
also be some
rules on how media is handled across one of these intermediaries.

If that was done, then a communication session could be defined as a
Transaction++ for an out-of-dialog request, or a Dialog++.

But that makes the definition of communication session the first
priority and the cases that happen to qualify as a communication
session
a consequence. It probably won't match people's intuitive
feelings about
what *should* be a communication session. So it might not
satisfy people.

Thanks,
Paul


On 1/10/13 6:04 PM, Charles Eckel (eckelcu) wrote:

>From my point of view, the draft looks good. The
changes incorporated

in this updated version directly address this open issue.

Cheers,
Charles

-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a>
[<a class="moz-txt-link-freetext" href="mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org</a>] On
Behalf Of Gonzalo Salgueiro (gsalguei)
Sent: Thursday, January 10, 2013 12:39 PM
To: Paul E. Jones
Cc: <a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
Subject: Re: [Insipid] Are we ready to LC on the
requirements?

Thanks for submitting this, Paul. The biggest open issue
in regards
to the requirements document was to clearly define what
it is we are
identifying (i.e., "communication session") within the
scope of this
document and ensure that clearly defined language is used
consistently through! out the document. Prior to any
consensus on
moving to WGLC, the chairs would appreciate hearing the
group's
thoughts on where we are on this issue in the current
version.

Cheers,

Gonzalo &amp; Keith



On Jan 9, 2013, at 9:23 PM, Paul E. Jones wrote:

Folks,

Dialog has been extremely light on the requirements
document. Do

people feel generally OK with it as it is now? Can we
move on to the
solution document now or are there other changes needed
in the
requirements document?

I just posted the -04 versi!
 on with
changes proposed
on the list over
the

past month or so.

Paul

<hr>

insipid mailing list
<a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a>


<hr>

insipid mailing list
<a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a>

<hr>

insipid mailing list
<a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a>



<hr>

insipid mailing list
<a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a>




<hr>

insipid mailing list
<a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a></blockquote>

</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
insipid mailing list
<a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040400000502080705090606--

From rjsparks@nostrum.com  Fri Mar  1 12:55:49 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 470B821F8820 for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 12:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYw2v048LK-I for <insipid@ietfa.amsl.com>; Fri,  1 Mar 2013 12:55:47 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id B698321F8815 for <insipid@ietf.org>; Fri,  1 Mar 2013 12:55:47 -0800 (PST)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r21Ktiek005229 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 1 Mar 2013 14:55:45 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <513115D0.5040108@nostrum.com>
Date: Fri, 01 Mar 2013 14:55:44 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>
References: <20130220214453.9775.21588.idtracker@ietfa.amsl.com> <081001ce0fbc$ecca1ce0$c65e56a0$@packetizer.com> <201302212314.r1LNEAvD021438@rcdn-core-5.cisco.com>
In-Reply-To: <201302212314.r1LNEAvD021438@rcdn-core-5.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: insipid@ietf.org
Subject: Re: [Insipid] FW: New Version Notification for draft-jones-insipid-session-id-02.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 20:55:49 -0000

> - Added a comment in the Security Cons section that this spec (or the 
> Session-ID itself) MUST NOT be used for billing, but the authors 
> failed to capture from Atlanta why that is a problem. Any help here 
> (from someone that has any memories of why this was desired - speak up 
> please!)
I think you added this because of a question I asked, and this was very 
much not the result I had expected. I think you should revert it - it's 
not a protocol requirement. At best, you could say that supporting 
billing systems is not a use case that is being considered in the design 
of a mechanism meeting these requirements. (If anybody disagrees with 
that, speak up).

The point was to figure out whether or not a 3rd party being able to 
guess these identifiers was important.

The requirements document should be clear on here - is there a 
requirement for them to be hard to guess? Is it important for them to be 
hard to spoof? Is it important to protect them from eavesdropping?

There was a brief conversation in the meeting about whether or not 
someone would be able to use knowledge of these things (either from 
guessing them, or eavesdropping on them) to do something "bad". Billing 
was pointed to as one attack surface for bad. It's not the only one. If 
these _ever_ get used for, e.g. admission policy (like Replaces does), 
then there are security considerations that need to be discussed.

RjS

From christer.holmberg@ericsson.com  Sat Mar  2 13:10:54 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E72421F858A for <insipid@ietfa.amsl.com>; Sat,  2 Mar 2013 13:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.246
X-Spam-Level: 
X-Spam-Status: No, score=-6.246 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYS7xByJn7TC for <insipid@ietfa.amsl.com>; Sat,  2 Mar 2013 13:10:53 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id BC97121F8598 for <insipid@ietf.org>; Sat,  2 Mar 2013 13:10:52 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-7b-51326adb64f6
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id AB.CB.10459.BDA62315; Sat,  2 Mar 2013 22:10:51 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.02.0318.004; Sat, 2 Mar 2013 22:10:50 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, insipid_ietf.org <insipid@ietf.org>
Thread-Topic: [Insipid] Call for working group adoption of identifier solution draft
Thread-Index: Ac4UlDroba7PV9ffSRu5+JxUGGPxMACE8KGgADibUVQ=
Date: Sat, 2 Mar 2013 21:10:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B10F6BE@ESESSMB209.ericsson.se>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B10F6BEESESSMB209ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvje7tLKNAg4YlJhbz7z9jsnjaeJbR gcmj9dleVo8lS34yBTBFcdmkpOZklqUW6dslcGXMurCQreCcTsWiH7tYGhhfqXYxcnJICJhI NKzsZ4KwxSQu3FvPBmILCRxilFgxRxLCXsQo0bY1oouRg4NNwEKi+582SFhEYC6jRP+dGBBb WCBUYuaJh0wgJSICYRLzvkhBlFhJHFr7nBXEZhFQkbj/7w/YdF4Bb4nLM+8xQkyPl7i6Zx8z iM0pkCDReX8BWA0j0DXfT60Bu4xZQFzi1pP5UFcKSCzZc54ZwhaVePn4HytETb7Eo0UzWCDm C0qcnPmEZQKj8Cwk7bOQlM1CUgYR15FYsPsTG4StLbFs4WtmGPvMgcdMyOILGNlXMbLnJmbm pJcbbmIERsfBLb91dzCeOidyiFGag0VJnDfM9UKAkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6p BkYmm6MzPheJ+1hknjoQGf1Cg+Xe9auXtNhlj2SdNHPb1FTSklfIckf4StrKCvVrC++9v9oo /e47N/f5vKjDLQqbz0WyBy1nuPpkTYlLzEtZA497Yh09rhYdhr6nmpcbOQqtbi2QfKZZHiH4 OmHqIysrfpet2s89zs7lEe6dnNVkoDq5p6DcVYmlOCPRUIu5qDgRAI/LH4tcAgAA
Subject: Re: [Insipid] Call for working group adoption of identifier	solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Mar 2013 21:10:54 -0000

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

Hi,

I support adoption of the draft.

Regards,

Christer



Sent from Windows using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: DRAGE, Keith (Keith) [keith.drage@alcatel-lucent.com]
To: DRAGE, Keith (Keith) [keith.drage@alcatel-lucent.com]; insipid@ietf.org=
 [insipid@ietf.org]
Subject: Re: [Insipid] Call for working group adoption of identifier soluti=
on draft
(As WG cochair)

I know the call has only been out a couple of days, but so far there has be=
en absolute silence on this.

So this is to indicate that the chairs do need positive responses as well a=
s negative ones.

If we get no responses we'll just assume no one is interested, with the app=
ropriate consequences.

Keith

> -----Original Message-----
> From: DRAGE, Keith (Keith)
> Sent: 27 February 2013 02:44
> To: insipid@ietf.org
> Subject: Call for working group adoption of identifier solution draft
>
> (As working group cochair)
>
> This is a call for the adoption of the text of the draft
>
> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>
> as a working group draft to meet the milestone
>
> Specification of the new identifier sent to the IESG (PS)
>
> Please respond as to whether the draft is acceptable or not. You may also
> respond that certain parts are acceptable, or that parts are not
> acceptable (please be specific).
>
> This is currently the only text we have on the table to meet the mileston=
e
> and there seems to be some measure of convergence on this text at the
> Atlanta meeting.
>
> We will make a decision based on the responses received by Tuesday 12th
> March (i.e. Tuesday of the IETF meeting week).
>
> Regards
>
> Keith
_______________________________________________
insipid mailing list
insipid@ietf.org
https://www.ietf.org/mailman/listinfo/insipid

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11p=
t; color:black">
<div><span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-s=
erif; font-size:11pt">Hi,</span></div>
<div>&nbsp;</div>
<div><font face=3D"Calibri">I support adoption of the draft.</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Regards,</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Christer</font></div>
<span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-serif;=
 font-size:11pt">
<div>&nbsp;</div>
<div><br>
<br>
Sent from <b><i>Windows</i></b> using <b style=3D"color:blue">TouchDown</b>=
 (www.nitrodesk.com)</div>
</span>
<div></div>
<br>
<span style=3D"color:black">-----Original Message-----<br>
<b>From:</b> DRAGE, Keith (Keith) [keith.drage@alcatel-lucent.com]<br>
<b>To:</b> DRAGE, Keith (Keith) [keith.drage@alcatel-lucent.com]; insipid@i=
etf.org [insipid@ietf.org]<br>
<b>Subject:</b> Re: [Insipid] Call for working group adoption of identifier=
 solution draft</span></div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">(As WG cochair)<br>
<br>
I know the call has only been out a couple of days, but so far there has be=
en absolute silence on this.
<br>
<br>
So this is to indicate that the chairs do need positive responses as well a=
s negative ones.
<br>
<br>
If we get no responses we'll just assume no one is interested, with the app=
ropriate consequences.<br>
<br>
Keith<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: DRAGE, Keith (Keith)<br>
&gt; Sent: 27 February 2013 02:44<br>
&gt; To: insipid@ietf.org<br>
&gt; Subject: Call for working group adoption of identifier solution draft<=
br>
&gt; <br>
&gt; (As working group cochair)<br>
&gt; <br>
&gt; This is a call for the adoption of the text of the draft<br>
&gt; <br>
&gt; <a href=3D"http://www.ietf.org/id/draft-jones-insipid-session-id-02.tx=
t">http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt</a><br>
&gt; <br>
&gt; as a working group draft to meet the milestone<br>
&gt; <br>
&gt; Specification of the new identifier sent to the IESG (PS)<br>
&gt; <br>
&gt; Please respond as to whether the draft is acceptable or not. You may a=
lso<br>
&gt; respond that certain parts are acceptable, or that parts are not<br>
&gt; acceptable (please be specific).<br>
&gt; <br>
&gt; This is currently the only text we have on the table to meet the miles=
tone<br>
&gt; and there seems to be some measure of convergence on this text at the<=
br>
&gt; Atlanta meeting.<br>
&gt; <br>
&gt; We will make a decision based on the responses received by Tuesday 12t=
h<br>
&gt; March (i.e. Tuesday of the IETF meeting week).<br>
&gt; <br>
&gt; Regards<br>
&gt; <br>
&gt; Keith<br>
_______________________________________________<br>
insipid mailing list<br>
insipid@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.=
org/mailman/listinfo/insipid</a><br>
</div>
</span></font>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B10F6BEESESSMB209ericsso_--

From paulej@packetizer.com  Mon Mar  4 06:27:46 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDF421F8826 for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 06:27:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ilUe0QfJL15W for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 06:27:38 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id AE3B721F8533 for <insipid@ietf.org>; Mon,  4 Mar 2013 06:27:34 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r24ERWJo030800 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 4 Mar 2013 09:27:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362407253; bh=Ii67RiopeRajq+tH4I3colYS0ehMWx0nAhvaC+HGlDI=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=BFngcMkkTobZKqaiDNsu+fRDNzJZw9k63zJt9ExCLjdI/nB0BvbBr9Pa8Sz3iaCA3 qtrEpGPXP5Ap5q5+fncgGJ8mk4+KRoWB/ZgU4Z3x82yvqtUj7+Yh8zNjuCWkgx2xFM /N2NvjDn+9n14ZJJza/Qu5FNyJF6EzKIqhnDhyt8=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Robert Sparks'" <rjsparks@nostrum.com>
References: <055801cdeed9$8b441060$a1cc3120$@packetizer.com>	<5F864ABC-E17F-44C9-8CDE-D6C5A32BF214@cisco.com>	<92B7E61ADAC1BB4F941F943788C0882804728936@xmb-aln-x08.cisco.com>	<50F07742.3030601@alum.mit.edu>	<0a0e01ce10a7$875a0690$960e13b0$@packetizer.com>	<512965C1.2090204@alum.mit.edu>	<55fa36b1-465e-40e0-b875-90fb48f3fc13@email.android.com>	<5129B6AD.6010306@alum.mit.edu>	<fab2d64c-7f69-4575-a372-15d78237e667@email.android.com> <51310CEC.1070907@nostrum.com>
In-Reply-To: <51310CEC.1070907@nostrum.com>
Date: Mon, 4 Mar 2013 09:27:44 -0500
Message-ID: <013401ce18e4$7061a2a0$5124e7e0$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0135_01CE18BA.87907CA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHTUbyWWA5m3crBY/au5zDaSqMbPQHgf0hnAhmddX0CpBjqowIxbGDRAeh2nkEBtHmmmAGjQg/hAfb7tOQDFd7KkZfyPm3g
Content-Language: en-us
Cc: insipid@ietf.org, 'Paul Kyzivat' <pkyzivat@alum.mit.edu>
Subject: Re: [Insipid] Are we ready to LC on the requirements?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 14:27:46 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0135_01CE18BA.87907CA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Robert,

 

We'll try to cover this in the meeting with slides and then incorporate in
slides subsequently.  I have an answer for each.  That said, please do allow
me to provide an answer below that we can discuss before then.

 

Paul

 

From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On Behalf
Of Robert Sparks
Sent: Friday, March 01, 2013 3:18 PM
To: Paul E. Jones
Cc: insipid@ietf.org; Paul Kyzivat
Subject: Re: [Insipid] Are we ready to LC on the requirements?

 

On 2/24/13 8:38 AM, Paul E. Jones wrote:

Paul,

That still begs the question of "what language do we need to add or change
to make this clear?" In my mind, I know exactly what an endpoint needs to do
and what an SBC needs to do. But, I'll not say it does not need more charity
for those that do not have it clear in their minds.

But, perhaps being too close to the work, I'm having trouble seeing where it
is vague. Can you suggest text?

This is frustrating, for both of us probably. I've read the latest
requirement document and it doesn't yet clearly
answer the questions I asked in the Atlanta meeting. I feel like I've asked
them at several meetings before.
Can we stop that cycle of repeating the discussion by putting text in the
document that directly answers each of these:

In a scenario where you only have one parallel forking SIP proxy, when an
INVITE forks to two different
UAs and _both_ send 200 OKs, do you have one session or two? (This same
question applies to early dialogs,
with or without early media, which is a _normal_ condition, not an race
condition like multiple 200 OKs).

 

PEJ: That would be two communication sessions, one between Alice to Bob-1
and one between Alice and Bob-2.  This is precisely why we use the approach
in our proposed solution.  The Session-ID is always comprised of the UUID
values from each "endpoint" (which would include MCUs, PSTN GWs, or 3PCC
session initiators).


If you replace that with a _serial_ forking proxy, where you were in an
early dialog with UA1, that got canceled
and then you ended up in an early dialog, and then a confirmed dialog with
UA2, was that one session (with the
calling UA, UA1, and UA2 involved) or two sessions (one with the calling UA
and UA1, the other with the calling
UA and UA2)?

 

PEJ: That would be two communication sessions.  Any time there is a
different UA on one end, that represents a distinct communication session.


If you replace that with a B2BUA that behaves similar to a serial forking
proxy in that it only alerts one called thing
at a time, do you end up with one session or with two.

 

PEJ: This is similar to the case where a fork is cancelled.  Alice is only
in one communication session and the SBC has to pick a UUID to return.
However, the UUID can change if the other device actually answers.  For that
matter, the SBC could even fabricate a temporary value, knowing there is a
50/50 change it will change, anyway.  What's important is the end result:
the "stable call".  Once the call is connected, there are just two devices,
Alice and some Bob.  And, if the Bob changes during call establishment, the
UUID value will change on that end.  That's perfectly fine.

 

Paul


I don't see how the current document answers those questions. If I've missed
that, please point to it and I'll see how
I can help make them more obvious.

Otherwise, can you please make the answers clear in the document, (not just
in an email response).




Paul

  _____  

From: Paul Kyzivat  <mailto:pkyzivat@alum.mit.edu> <pkyzivat@alum.mit.edu>
Sent: Sun Feb 24 01:43:57 EST 2013
To: "Paul E. Jones"  <mailto:paulej@packetizer.com> <paulej@packetizer.com>
Cc: insipid@ietf.org
Subject: Re: [Insipid] Are we ready to LC on the requirements?





On 2/24/13 12:33 AM, Paul E. Jones wrote:

Paul,
 
So what concept is vague?
 
In terms of an H.323 device, I would consider two terminals with users
at each end to be a communication session. I would consider a terminal
and an MCU to have a communication session.
 
The collection of communication sessions on an MCU to which one or more
terrminals are a party is a conference. And I would like to relate all
those sessions by the UUID the MCU uses in each of those sessions. That
value could even be the Conference ID in H.323.
 
There are gateway devices that connect to the PSTN that I would count as
equal to a terminal. But, there are gateway devices that bridge IP
networks (SBCs) that shoul!
 d just
pass the UUIDs through. The difference
between the two really is whether it bridges an IPMC device to another
or to something else.
 
There are call flows like the one you highlighted in the threads where
voice comes from one terminal and video from another. That's an MCU,
really. The session ID exists between Alice and MCU (or PBX). The other
devices Bob uses might share the UUID of the MCU/PBX, but those are
distinct communication sessions like the typical MCU case. Yeah, such
topologies do make it hard to do debugging and the number of UUIDs makes
it a pain, too, but at least there is consistency in the assignments.
So, it is doable.
 
So, how can we make progress here?

 
We write some rules that any device that terminates more than one dialog 
can use to decide when one dialog should share a session-id with another 
dialog. The rules should get the "right" answer for all the use case!
 s, 
and should be specific enough so that when applied to any device, no 
matter how weird, most reasonable people would agree with the answer. 
That way we can have a way of judging conformance to this specification.
 
I realize this bridges the gap between what the requirements are 
responsible for and what the mechanism is responsible for. But the 
mechanism is about marking communications sessions, not defining them.
 
OR I suppose the requirements could kick the can down the road, simply 
say that the mechanism must work for the specified use cases and itself 
must specify the algorithm for making the decision in other cases. But 
that just puts it off.
 
 Thanks,
 Paul K
 

Paul
 
 
 


  _____  

 
*From:* Paul Kyzivat  <mailto:pkyzivat@alum.mit.edu> <pkyzivat@alum.mit.edu>
*Sent:* Sat F!
 eb 23
19:58:41 EST 2013
*To:* "Paul E. Jones"  <mailto:paulej@packetizer.com>
<paulej@packetizer.com>
*Cc:* insipid@ietf.org
*Subject:* Re: [Insipid] Are we ready to LC on the requirements?
 
On 2/21/13 9:51 PM, Paul E. Jones wrote:
 
Paul,
 
I read your message, but was left unsure of exactly how we could
improve the
definition over what we have already.
 
If there is something concrete that you can propose that would help
lend to
clarity of the text, I'm definitely willing to put it in. I would
like to
move the requirements along and the submission deadline is Monday.
Do you
have text you would like to add before the deadline?
 
 
I'm traveling on business and have limited internet access, and limited
time, so I probably can't.
 
In any case, ISTM that the problem isn't that we don't have the right
words. Rather, we still don't have clear *concepts* that distinguish
!
whatshould be covered from what should not. We have some use cases, but
lack basic principles that can be applied to any case to determine if it
should be a communication session or not. It still seems to be more in
the realm of "I know one when I see it."
 
If we had the principles, then it would probably be straightforward to
come up with words.
 
I don't yet see a suitable general principle here that fits the use
cases and seems to make sense.
 
Thanks,
Paul
 
Paul
 
-----Original Message-----
From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
Behalf Of Paul Kyzivat
Sent: Friday, January 11, 2013 3:34 PM
To: insipid@ietf.org
Subject: Re: [Insipid] Are we ready to LC on the requirements?
 
(Sorry that this is long. I don't know how to make it short.)
 
Are we ready to LC? I don't think so. Specifically I don't think
we yet
have an
unambiguous definition of what is being identified.
 
This version added some new text:
 
In this document, the word "session" refers to a "communication
session" that may exist between two SIP user agents and that may
pass
through one or more intermediary devices, including B2BUAs or SIP
proxies. A communication session consists of one of more SIP
transactions. A very simple communication session may be a single
out-of-dialog SIP transaction (e.g., MESSAGE/200). In the case of a
SIP dialog, the SIP message exchange includes a dialog creating
INVITE transaction, and zero of more subsequent SIP transactions
within the same dialog (e.g., ACK, re-INVITE, BYE). Due to the
existenc! e of middle boxes, there may be multiple related SIP
transactions or dialogs chained together along the path from one end
of the communication session to the other. For example:
 
A Middlebox B
SIP trans1
-----------------> SIP trans 2
SIP dialog 1 <-------------- SIP dialog 2
 
Figure 1 - Communication Session through a Middlebox
 
In such cases, the two SIP transactions or dialogs are part of a
single communication session.
 
The term "end-to-end" in this document means the communication
session from the point of origin, passing through any number of
intermediaries, to the ultimate point of termination. It is
recognized that legacy devices may not support the "end-to-end"
session identifier, though an identifier might be created by an
intermediary when it is absent from the session signaling.
 
IMO this is a big improvement. But it still isn't as prec! ise
as I would
like. What I find lacking in the above is:
 
o parsing the above, the properties of a communication session are:
- connects *two* UAs
- optionally includes one or more intermediary devices
- one or more
transactions
- one out-of-dialog transaction,
OR a dialog including the dialog establishing transaction
and some transactions within the dialog.
- middle boxes may result in chaining dialogs or transactions.
 
Exactly how all these properties "plug together" fuzzy.
I'm not at all certain that all readers would reach
the same conclusion about which cases meet these criteria
and which don't.
 
o I'm also not certain that these criteria match all the cases
people expect, and exclude all the cases people think should
be excluded.
 
- I think people expect that a conference is *not* a single
communications session. But a conference with only two
participants would! seem to qualify according to all of the
above criteria. So that suggests that another criterion is
needed to exclude that case.
 
- A topologically similar case to the conference is a
click-to-dial case where a web!
  server
makes outward INVITEs
to two UAs and connects them. I think people believe this
case *should* be a communications session.
 
- Another case is described in
http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html
and debated in the replies to that. Arguments are made for
different answers to what should get a common session id and what
should not. For this case I think we need to decide:
. do we mandate exactly how this should be treated?
. or do we leave it to the discretion of the B2BUA to decide?
 
Either way we need to decide what the criteria are that lead
to the decision.
 
o! IIRC Hadriel suggested (in a meeting?) that where media
originates and terminates has something to do with this.
That doesn't work all the time (e.g. MESSAGE), but it might help
in some cases. I think he used this to just!
 ify
that:
 
- the Conference Bridge Transcoding Model (RFC5369 section 3.2)
is a single communications session.
 
- the 3PCC Transcoding Model (RFC5369 section 3.1) is *not*
a single communications session.
 
(I'm not convinced - this seems like a distinction without
a difference.)
 
Fundamentally we should be able to classify all cases into:
- those that *should* be communications sessions,
- those that *shouldn't* be communication sessions,
- those we don't care about - could be either way.
 
When we are done, we should be able to apply the definition of
communication session to any case. When applied to the cases we
explicitly care about it should deliver the an! swer we expect.
 
The more weird cases we care about, the more complex and
unintuitive the
criteria will be. I suspect that the path we are on will lead to
complex
criteria. (We can have a really crisp de!
 finition
of communications
session if we don't care much about which cases qualify.)
 
One idea I considered is to define some new terms that build on
normal
sip concepts but extend them to allow B2BUA intermediaries where sip
allows proxies. E.g.
- Transaction++ is either a sip transaction, or a series of sip
transactions linked by B2BUA intermediaries.
 
- Dialog++ is either a sip dialog, or a series of sip dialogs
linked by B2BUA intermediaries.
 
Then would need to define the behavior of a B2BUA intermediary.
It needs
to relay transactions from one "side" to the other, preserving
certain
invariants (TBD). Presumably it can also originate certain
transactions,
but there must be constraints ! on what it can do. There must
also be some
rules on how media is handled across one of these intermediaries.
 
If that was done, then a communication session could be defined as a
Transaction++ for an out-of-dialog request, or a Dialog++.
 
But that makes the definition of communication session the first
priority and the cases that happen to qualify as a communication
session
a consequence. It probably won't match people's intuitive
feelings about
what *should* be a communication session. So it might not
satisfy people.
 
Thanks,
Paul
 
 
On 1/10/13 6:04 PM, Charles Eckel (eckelcu) wrote:
 
>From my point of view, the draft looks good. The
changes incorporated
 
in this updated version directly address this open issue.
 
Cheers,
Charles
 
-----Original Message-----
From: insipid-bounces@ietf.org
[mailto:insipid-bounces@ietf.org] On
Behalf Of Gonzalo Salgueiro (gsalguei)
Sent: Thursday, January 10, 2013 12:39 PM
To: Paul E. Jones
Cc: insipid@ietf.org
Subject: Re: [Insipid] Are we ready to LC on the
requirements?
 
Thanks for submitting this, Paul. The biggest open issue
in regards
to the requirements document was to clearly define what
it is we are
identifying (i.e., "communication session") within the
scope of this
document and ensure that clearly defined language is used
consistently through! out the document. Prior to any
consensus on
moving to WGLC, the chairs would appreciate hearing the
group's
thoughts on where we are on this issue in the current
version.
 
Cheers,
 
Gonzalo & Keith
 
 
 
On Jan 9, 2013, at 9:23 PM, Paul E. Jones wrote:
 
Folks,
 
Dialog has been extremely light on the requirements
document. Do
 
people feel generally OK with it as it is now? Can we
move on to the
solution document now or are there other changes needed
in the
requirements document?
 
I just posted the -04 versi!
 on with
changes proposed
on the list over
the
 
past month or so.
 
Paul
 


  _____  

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


  _____  

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


  _____  

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


  _____  

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


  _____  

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

 
 






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

 


------=_NextPart_000_0135_01CE18BA.87907CA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Robert,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We&#8217;ll try to cover this in the meeting with slides and then =
incorporate in slides subsequently.&nbsp; I have an answer for =
each.&nbsp; That said, please do allow me to provide an answer below =
that we can discuss before then.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Paul<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] <b>On =
Behalf Of </b>Robert Sparks<br><b>Sent:</b> Friday, March 01, 2013 3:18 =
PM<br><b>To:</b> Paul E. Jones<br><b>Cc:</b> insipid@ietf.org; Paul =
Kyzivat<br><b>Subject:</b> Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On =
2/24/13 8:38 AM, Paul E. Jones wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>Paul,<br><br>That still begs the question of =
&quot;what language do we need to add or change to make this =
clear?&quot; In my mind, I know exactly what an endpoint needs to do and =
what an SBC needs to do. But, I'll not say it does not need more charity =
for those that do not have it clear in their minds.<br><br>But, perhaps =
being too close to the work, I'm having trouble seeing where it is =
vague. Can you suggest text?<o:p></o:p></p></blockquote><p =
class=3DMsoNormal>This is frustrating, for both of us probably. I've =
read the latest requirement document and it doesn't yet =
clearly<br>answer the questions I asked in the Atlanta meeting. I feel =
like I've asked them at several meetings before.<br>Can we stop that =
cycle of repeating the discussion by putting text in the document that =
directly answers each of these:<br><br>In a scenario where you only have =
one parallel forking SIP proxy, when an INVITE forks to two =
different<br>UAs and _both_ send 200 OKs, do you have one session or =
two? (This same question applies to early dialogs,<br>with or without =
early media, which is a _normal_ condition, not an race condition like =
multiple 200 OKs).<span style=3D'color:#1F497D'><o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>PEJ: That would be two communication sessions, one between Alice to =
Bob-1 and one between Alice and Bob-2.&nbsp; This is precisely why we =
use the approach in our proposed solution.&nbsp; The Session-ID is =
always comprised of the UUID values from each &#8220;endpoint&#8221; =
(which would include MCUs, PSTN GWs, or 3PCC session =
initiators).</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><br>If you replace that =
with a _serial_ forking proxy, where you were in an early dialog with =
UA1, that got canceled<br>and then you ended up in an early dialog, and =
then a confirmed dialog with UA2, was that one session (with =
the<br>calling UA, UA1, and UA2 involved) or two sessions (one with the =
calling UA and UA1, the other with the calling<br>UA and UA2)?<span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>PEJ: That would be two communication sessions.&nbsp; Any time there is =
a different UA on one end, that represents a distinct communication =
session.<o:p></o:p></span></p><p class=3DMsoNormal><br>If you replace =
that with a B2BUA that behaves similar to a serial forking proxy in that =
it only alerts one called thing<br>at a time, do you end up with one =
session or with two.<span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>PEJ: This is similar to the case where a fork is cancelled.&nbsp; Alice =
is only in one communication session and the SBC has to pick a UUID to =
return.&nbsp; However, the UUID can change if the other device actually =
answers.&nbsp; For that matter, the SBC could even fabricate a temporary =
value, knowing there is a 50/50 change it will change, anyway.&nbsp; =
What&#8217;s important is the end result: the &#8220;stable =
call&#8221;.&nbsp; Once the call is connected, there are just two =
devices, Alice and some Bob.&nbsp; And, if the Bob changes during call =
establishment, the UUID value will change on that end.&nbsp; =
That&#8217;s perfectly fine.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>Paul<o:p></o:p></span></p><p class=3DMsoNormal><br>I don't see how the =
current document answers those questions. If I've missed that, please =
point to it and I'll see how<br>I can help make them more =
obvious.<br><br>Otherwise, can you please make the answers clear in the =
document, (not just in an email response).<br><br><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>Paul<o:p></o:p></p><div><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><hr =
size=3D2 width=3D"100%" align=3Dcenter></span></div><p =
class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Paul Kyzivat <a =
href=3D"mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a><b=
r><b>Sent:</b> Sun Feb 24 01:43:57 EST 2013<br><b>To:</b> &quot;Paul E. =
Jones&quot; <a =
href=3D"mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a><b=
r><b>Cc:</b> <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><br><b>Subject:</b> =
Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></span></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><pre>On 2/24/13 12:33 AM, Paul =
E. Jones wrote:<o:p></o:p></pre><blockquote =
style=3D'border:none;border-left:solid #729FCF 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in;margin-bottom:6.0pt'><pre>Paul,<=
o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>So what concept is =
vague?<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>In terms of an =
H.323 device, I would consider two terminals with =
users<o:p></o:p></pre><pre>at each end to be a communication session. I =
would consider a terminal<o:p></o:p></pre><pre>and an MCU to have a =
communication =
session.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>The collection =
of communication sessions on an MCU to which one or =
more<o:p></o:p></pre><pre>terrminals are a party is a conference. And I =
would like to relate all<o:p></o:p></pre><pre>those sessions by the UUID =
the MCU uses in each of those sessions. That<o:p></o:p></pre><pre>value =
could even be the Conference ID in =
H.323.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>There are =
gateway devices that connect to the PSTN that I would count =
as<o:p></o:p></pre><pre>equal to a terminal. But, there are gateway =
devices that bridge IP<o:p></o:p></pre><pre>networks (SBCs) that =
shoul!<o:p></o:p></pre><pre> d just<o:p></o:p></pre><pre>pass the UUIDs =
through. The difference<o:p></o:p></pre><pre>between the two really is =
whether it bridges an IPMC device to another<o:p></o:p></pre><pre>or to =
something else.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>There =
are call flows like the one you highlighted in the threads =
where<o:p></o:p></pre><pre>voice comes from one terminal and video from =
another. That's an MCU,<o:p></o:p></pre><pre>really. The session ID =
exists between Alice and MCU (or PBX). The =
other<o:p></o:p></pre><pre>devices Bob uses might share the UUID of the =
MCU/PBX, but those are<o:p></o:p></pre><pre>distinct communication =
sessions like the typical MCU case. Yeah, =
such<o:p></o:p></pre><pre>topologies do make it hard to do debugging and =
the number of UUIDs makes<o:p></o:p></pre><pre>it a pain, too, but at =
least there is consistency in the assignments.<o:p></o:p></pre><pre>So, =
it is doable.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>So, how =
can we make progress =
here?<o:p></o:p></pre></blockquote><pre><o:p>&nbsp;</o:p></pre><pre>We =
write some rules that any device that terminates more than one dialog =
<o:p></o:p></pre><pre>can use to decide when one dialog should share a =
session-id with another <o:p></o:p></pre><pre>dialog. The rules should =
get the &quot;right&quot; answer for all the use =
case!<o:p></o:p></pre><pre> s, <o:p></o:p></pre><pre>and should be =
specific enough so that when applied to any device, no =
<o:p></o:p></pre><pre>matter how weird, most reasonable people would =
agree with the answer. <o:p></o:p></pre><pre>That way we can have a way =
of judging conformance to this =
specification.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I =
realize this bridges the gap between what the requirements are =
<o:p></o:p></pre><pre>responsible for and what the mechanism is =
responsible for. But the <o:p></o:p></pre><pre>mechanism is about =
marking communications sessions, not defining =
them.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>OR I suppose the =
requirements could kick the can down the road, simply =
<o:p></o:p></pre><pre>say that the mechanism must work for the specified =
use cases and itself <o:p></o:p></pre><pre>must specify the algorithm =
for making the decision in other cases. But <o:p></o:p></pre><pre>that =
just puts it off.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre> =
Thanks,<o:p></o:p></pre><pre> Paul =
K<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><blockquote =
style=3D'border:none;border-left:solid #729FCF 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in;margin-bottom:6.0pt'><pre>Paul<o=
:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><p=
re><o:p>&nbsp;</o:p></pre><pre style=3D'text-align:center'><hr size=3D2 =
width=3D"100%" =
align=3Dcenter></pre><pre><o:p>&nbsp;</o:p></pre><pre>*From:* Paul =
Kyzivat <a =
href=3D"mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a><o=
:p></o:p></pre><pre>*Sent:* Sat F!<o:p></o:p></pre><pre> eb =
23<o:p></o:p></pre><pre>19:58:41 EST 2013<o:p></o:p></pre><pre>*To:* =
&quot;Paul E. Jones&quot; <a =
href=3D"mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a><o=
:p></o:p></pre><pre>*Cc:* <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e>*Subject:* Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>On =
2/21/13 9:51 PM, Paul E. Jones =
wrote:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Paul,<o:p></o:p><=
/pre><pre><o:p>&nbsp;</o:p></pre><pre>I read your message, but was left =
unsure of exactly how we could<o:p></o:p></pre><pre>improve =
the<o:p></o:p></pre><pre>definition over what we have =
already.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>If there is =
something concrete that you can propose that would =
help<o:p></o:p></pre><pre>lend to<o:p></o:p></pre><pre>clarity of the =
text, I'm definitely willing to put it in. I =
would<o:p></o:p></pre><pre>like to<o:p></o:p></pre><pre>move the =
requirements along and the submission deadline is =
Monday.<o:p></o:p></pre><pre>Do you<o:p></o:p></pre><pre>have text you =
would like to add before the =
deadline?<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o=
:p></pre><pre>I'm traveling on business and have limited internet =
access, and limited<o:p></o:p></pre><pre>time, so I probably =
can't.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>In any case, =
ISTM that the problem isn't that we don't have the =
right<o:p></o:p></pre><pre>words. Rather, we still don't have clear =
*concepts* that =
distinguish<o:p></o:p></pre><pre>!<o:p></o:p></pre><pre>whatshould be =
covered from what should not. We have some use cases, =
but<o:p></o:p></pre><pre>lack basic principles that can be applied to =
any case to determine if it<o:p></o:p></pre><pre>should be a =
communication session or not. It still seems to be more =
in<o:p></o:p></pre><pre>the realm of &quot;I know one when I see =
it.&quot;<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>If we had the =
principles, then it would probably be straightforward =
to<o:p></o:p></pre><pre>come up with =
words.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I don't yet see =
a suitable general principle here that fits the =
use<o:p></o:p></pre><pre>cases and seems to make =
sense.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Thanks,<o:p></o:p=
></pre><pre>Paul<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Paul<o:=
p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: <a =
href=3D"mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a> =
[<a =
href=3D"mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org<=
/a>] On<o:p></o:p></pre><pre>Behalf Of Paul =
Kyzivat<o:p></o:p></pre><pre>Sent: Friday, January 11, 2013 3:34 =
PM<o:p></o:p></pre><pre>To: <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e>Subject: Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>(Sorry =
that this is long. I don't know how to make it =
short.)<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Are we ready to =
LC? I don't think so. Specifically I don't think<o:p></o:p></pre><pre>we =
yet<o:p></o:p></pre><pre>have an<o:p></o:p></pre><pre>unambiguous =
definition of what is being =
identified.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>This =
version added some new =
text:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>In this document, =
the word &quot;session&quot; refers to a =
&quot;communication<o:p></o:p></pre><pre>session&quot; that may exist =
between two SIP user agents and that =
may<o:p></o:p></pre><pre>pass<o:p></o:p></pre><pre>through one or more =
intermediary devices, including B2BUAs or =
SIP<o:p></o:p></pre><pre>proxies. A communication session consists of =
one of more SIP<o:p></o:p></pre><pre>transactions. A very simple =
communication session may be a single<o:p></o:p></pre><pre>out-of-dialog =
SIP transaction (e.g., MESSAGE/200). In the case of =
a<o:p></o:p></pre><pre>SIP dialog, the SIP message exchange includes a =
dialog creating<o:p></o:p></pre><pre>INVITE transaction, and zero of =
more subsequent SIP transactions<o:p></o:p></pre><pre>within the same =
dialog (e.g., ACK, re-INVITE, BYE). Due to =
the<o:p></o:p></pre><pre>existenc! e of middle boxes, there may be =
multiple related SIP<o:p></o:p></pre><pre>transactions or dialogs =
chained together along the path from one end<o:p></o:p></pre><pre>of the =
communication session to the other. For =
example:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>A Middlebox =
B<o:p></o:p></pre><pre>SIP =
trans1<o:p></o:p></pre><pre>-----------------&gt; SIP trans =
2<o:p></o:p></pre><pre>SIP dialog 1 &lt;-------------- SIP dialog =
2<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Figure 1 - =
Communication Session through a =
Middlebox<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>In such =
cases, the two SIP transactions or dialogs are part of =
a<o:p></o:p></pre><pre>single communication =
session.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>The term =
&quot;end-to-end&quot; in this document means the =
communication<o:p></o:p></pre><pre>session from the point of origin, =
passing through any number of<o:p></o:p></pre><pre>intermediaries, to =
the ultimate point of termination. It is<o:p></o:p></pre><pre>recognized =
that legacy devices may not support the =
&quot;end-to-end&quot;<o:p></o:p></pre><pre>session identifier, though =
an identifier might be created by an<o:p></o:p></pre><pre>intermediary =
when it is absent from the session =
signaling.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>IMO this is =
a big improvement. But it still isn't as prec! =
ise<o:p></o:p></pre><pre>as I would<o:p></o:p></pre><pre>like. What I =
find lacking in the above =
is:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>o parsing the =
above, the properties of a communication session =
are:<o:p></o:p></pre><pre>- connects *two* UAs<o:p></o:p></pre><pre>- =
optionally includes one or more intermediary =
devices<o:p></o:p></pre><pre>- one or =
more<o:p></o:p></pre><pre>transactions<o:p></o:p></pre><pre>- one =
out-of-dialog transaction,<o:p></o:p></pre><pre>OR a dialog including =
the dialog establishing transaction<o:p></o:p></pre><pre>and some =
transactions within the dialog.<o:p></o:p></pre><pre>- middle boxes may =
result in chaining dialogs or =
transactions.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Exactly =
how all these properties &quot;plug together&quot; =
fuzzy.<o:p></o:p></pre><pre>I'm not at all certain that all readers =
would reach<o:p></o:p></pre><pre>the same conclusion about which cases =
meet these criteria<o:p></o:p></pre><pre>and which =
don't.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>o I'm also not =
certain that these criteria match all the =
cases<o:p></o:p></pre><pre>people expect, and exclude all the cases =
people think should<o:p></o:p></pre><pre>be =
excluded.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>- I think =
people expect that a conference is *not* a =
single<o:p></o:p></pre><pre>communications session. But a conference =
with only two<o:p></o:p></pre><pre>participants would! seem to qualify =
according to all of the<o:p></o:p></pre><pre>above criteria. So that =
suggests that another criterion is<o:p></o:p></pre><pre>needed to =
exclude that case.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>- A =
topologically similar case to the conference is =
a<o:p></o:p></pre><pre>click-to-dial case where a =
web!<o:p></o:p></pre><pre>&nbsp; server<o:p></o:p></pre><pre>makes =
outward INVITEs<o:p></o:p></pre><pre>to two UAs and connects them. I =
think people believe this<o:p></o:p></pre><pre>case *should* be a =
communications =
session.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>- Another case =
is described in<o:p></o:p></pre><pre><a =
href=3D"http://www.ietf.org/mail-archive/web/insipid/current/msg00429.htm=
l">http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html</a>=
<o:p></o:p></pre><pre>and debated in the replies to that. Arguments are =
made for<o:p></o:p></pre><pre>different answers to what should get a =
common session id and what<o:p></o:p></pre><pre>should not. For this =
case I think we need to decide:<o:p></o:p></pre><pre>. do we mandate =
exactly how this should be treated?<o:p></o:p></pre><pre>. or do we =
leave it to the discretion of the B2BUA to =
decide?<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Either way we =
need to decide what the criteria are that lead<o:p></o:p></pre><pre>to =
the decision.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>o! IIRC =
Hadriel suggested (in a meeting?) that where =
media<o:p></o:p></pre><pre>originates and terminates has something to do =
with this.<o:p></o:p></pre><pre>That doesn't work all the time (e.g. =
MESSAGE), but it might help<o:p></o:p></pre><pre>in some cases. I think =
he used this to just!<o:p></o:p></pre><pre> =
ify<o:p></o:p></pre><pre>that:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pr=
e><pre>- the Conference Bridge Transcoding Model (RFC5369 section =
3.2)<o:p></o:p></pre><pre>is a single communications =
session.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>- the 3PCC =
Transcoding Model (RFC5369 section 3.1) is *not*<o:p></o:p></pre><pre>a =
single communications =
session.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>(I'm not =
convinced - this seems like a distinction without<o:p></o:p></pre><pre>a =
difference.)<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Fundamental=
ly we should be able to classify all cases into:<o:p></o:p></pre><pre>- =
those that *should* be communications sessions,<o:p></o:p></pre><pre>- =
those that *shouldn't* be communication sessions,<o:p></o:p></pre><pre>- =
those we don't care about - could be either =
way.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>When we are done, =
we should be able to apply the definition =
of<o:p></o:p></pre><pre>communication session to any case. When applied =
to the cases we<o:p></o:p></pre><pre>explicitly care about it should =
deliver the an! swer we =
expect.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>The more weird =
cases we care about, the more complex =
and<o:p></o:p></pre><pre>unintuitive the<o:p></o:p></pre><pre>criteria =
will be. I suspect that the path we are on will lead =
to<o:p></o:p></pre><pre>complex<o:p></o:p></pre><pre>criteria. (We can =
have a really crisp de!<o:p></o:p></pre><pre> =
finition<o:p></o:p></pre><pre>of =
communications<o:p></o:p></pre><pre>session if we don't care much about =
which cases =
qualify.)<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>One idea I =
considered is to define some new terms that build =
on<o:p></o:p></pre><pre>normal<o:p></o:p></pre><pre>sip concepts but =
extend them to allow B2BUA intermediaries where =
sip<o:p></o:p></pre><pre>allows proxies. E.g.<o:p></o:p></pre><pre>- =
Transaction++ is either a sip transaction, or a series of =
sip<o:p></o:p></pre><pre>transactions linked by B2BUA =
intermediaries.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>- =
Dialog++ is either a sip dialog, or a series of sip =
dialogs<o:p></o:p></pre><pre>linked by B2BUA =
intermediaries.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Then =
would need to define the behavior of a B2BUA =
intermediary.<o:p></o:p></pre><pre>It needs<o:p></o:p></pre><pre>to =
relay transactions from one &quot;side&quot; to the other, =
preserving<o:p></o:p></pre><pre>certain<o:p></o:p></pre><pre>invariants =
(TBD). Presumably it can also originate =
certain<o:p></o:p></pre><pre>transactions,<o:p></o:p></pre><pre>but =
there must be constraints ! on what it can do. There =
must<o:p></o:p></pre><pre>also be some<o:p></o:p></pre><pre>rules on how =
media is handled across one of these =
intermediaries.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>If that =
was done, then a communication session could be defined as =
a<o:p></o:p></pre><pre>Transaction++ for an out-of-dialog request, or a =
Dialog++.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>But that =
makes the definition of communication session the =
first<o:p></o:p></pre><pre>priority and the cases that happen to qualify =
as a communication<o:p></o:p></pre><pre>session<o:p></o:p></pre><pre>a =
consequence. It probably won't match people's =
intuitive<o:p></o:p></pre><pre>feelings about<o:p></o:p></pre><pre>what =
*should* be a communication session. So it might =
not<o:p></o:p></pre><pre>satisfy =
people.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Thanks,<o:p></o:=
p></pre><pre>Paul<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&=
nbsp;</o:p></pre><pre>On 1/10/13 6:04 PM, Charles Eckel (eckelcu) =
wrote:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>From my point of =
view, the draft looks good. The<o:p></o:p></pre><pre>changes =
incorporated<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>in this =
updated version directly address this open =
issue.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Cheers,<o:p></o:p=
></pre><pre>Charles<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>----=
-Original Message-----<o:p></o:p></pre><pre>From: <a =
href=3D"mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a><o:p=
></o:p></pre><pre>[<a =
href=3D"mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org<=
/a>] On<o:p></o:p></pre><pre>Behalf Of Gonzalo Salgueiro =
(gsalguei)<o:p></o:p></pre><pre>Sent: Thursday, January 10, 2013 12:39 =
PM<o:p></o:p></pre><pre>To: Paul E. Jones<o:p></o:p></pre><pre>Cc: <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e>Subject: Re: [Insipid] Are we ready to LC on =
the<o:p></o:p></pre><pre>requirements?<o:p></o:p></pre><pre><o:p>&nbsp;</=
o:p></pre><pre>Thanks for submitting this, Paul. The biggest open =
issue<o:p></o:p></pre><pre>in regards<o:p></o:p></pre><pre>to the =
requirements document was to clearly define what<o:p></o:p></pre><pre>it =
is we are<o:p></o:p></pre><pre>identifying (i.e., &quot;communication =
session&quot;) within the<o:p></o:p></pre><pre>scope of =
this<o:p></o:p></pre><pre>document and ensure that clearly defined =
language is used<o:p></o:p></pre><pre>consistently through! out the =
document. Prior to any<o:p></o:p></pre><pre>consensus =
on<o:p></o:p></pre><pre>moving to WGLC, the chairs would appreciate =
hearing the<o:p></o:p></pre><pre>group's<o:p></o:p></pre><pre>thoughts =
on where we are on this issue in the =
current<o:p></o:p></pre><pre>version.<o:p></o:p></pre><pre><o:p>&nbsp;</o=
:p></pre><pre>Cheers,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Go=
nzalo &amp; =
Keith<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p><=
/pre><pre><o:p>&nbsp;</o:p></pre><pre>On Jan 9, 2013, at 9:23 PM, Paul =
E. Jones =
wrote:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Folks,<o:p></o:p>=
</pre><pre><o:p>&nbsp;</o:p></pre><pre>Dialog has been extremely light =
on the requirements<o:p></o:p></pre><pre>document. =
Do<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>people feel =
generally OK with it as it is now? Can we<o:p></o:p></pre><pre>move on =
to the<o:p></o:p></pre><pre>solution document now or are there other =
changes needed<o:p></o:p></pre><pre>in =
the<o:p></o:p></pre><pre>requirements =
document?<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I just posted =
the -04 versi!<o:p></o:p></pre><pre> on =
with<o:p></o:p></pre><pre>changes proposed<o:p></o:p></pre><pre>on the =
list =
over<o:p></o:p></pre><pre>the<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre=
><pre>past month or =
so.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Paul<o:p></o:p></pre=
><pre><o:p>&nbsp;</o:p></pre><pre style=3D'text-align:center'><hr =
size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></p=
re><pre><o:p>&nbsp;</o:p></pre><pre style=3D'text-align:center'><hr =
size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></p=
re><pre style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></p=
re><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre =
style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></p=
re><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbs=
p;</o:p></pre><pre style=3D'text-align:center'><hr size=3D2 =
width=3D"100%" =
align=3Dcenter></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre></blockquote><pre><o:p>&n=
bsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><p =
class=3DMsoNormal><br><br><br><o:p></o:p></p><pre>_______________________=
________________________<o:p></o:p></pre><pre>insipid mailing =
list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0135_01CE18BA.87907CA0--


From rjsparks@nostrum.com  Mon Mar  4 07:10:39 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB02721F89B3 for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 07:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uaT0WbB7G-Zk for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 07:10:34 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D989721F898A for <insipid@ietf.org>; Mon,  4 Mar 2013 07:10:33 -0800 (PST)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r24FAUnx048698 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 4 Mar 2013 09:10:31 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <5134B967.2010509@nostrum.com>
Date: Mon, 04 Mar 2013 09:10:31 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>
References: <055801cdeed9$8b441060$a1cc3120$@packetizer.com>	<5F864ABC-E17F-44C9-8CDE-D6C5A32BF214@cisco.com>	<92B7E61ADAC1BB4F941F943788C0882804728936@xmb-aln-x08.cisco.com>	<50F07742.3030601@alum.mit.edu>	<0a0e01ce10a7$875a0690$960e13b0$@packetizer.com>	<512965C1.2090204@alum.mit.edu>	<55fa36b1-465e-40e0-b875-90fb48f3fc13@email.android.com>	<5129B6AD.6010306@alum.mit.edu>	<fab2d64c-7f69-4575-a372-15d78237e667@email.android.com> <51310CEC.1070907@nostrum.com> <013401ce18e4$7061a2a0$5124e7e0$@packetizer.com>
In-Reply-To: <013401ce18e4$7061a2a0$5124e7e0$@packetizer.com>
Content-Type: multipart/alternative; boundary="------------040803070409090305010401"
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: insipid@ietf.org, 'Paul Kyzivat' <pkyzivat@alum.mit.edu>
Subject: Re: [Insipid] Are we ready to LC on the requirements?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 15:10:39 -0000

This is a multi-part message in MIME format.
--------------040803070409090305010401
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 3/4/13 8:27 AM, Paul E. Jones wrote:
>
> Robert,
>
> We'll try to cover this in the meeting with slides and then 
> incorporate in slides subsequently.  I have an answer for each.  That 
> said, please do allow me to provide an answer below that we can 
> discuss before then.
>
> Paul
>
> *From:*insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] *On 
> Behalf Of *Robert Sparks
> *Sent:* Friday, March 01, 2013 3:18 PM
> *To:* Paul E. Jones
> *Cc:* insipid@ietf.org; Paul Kyzivat
> *Subject:* Re: [Insipid] Are we ready to LC on the requirements?
>
> On 2/24/13 8:38 AM, Paul E. Jones wrote:
>
>     Paul,
>
>     That still begs the question of "what language do we need to add
>     or change to make this clear?" In my mind, I know exactly what an
>     endpoint needs to do and what an SBC needs to do. But, I'll not
>     say it does not need more charity for those that do not have it
>     clear in their minds.
>
>     But, perhaps being too close to the work, I'm having trouble
>     seeing where it is vague. Can you suggest text?
>
> This is frustrating, for both of us probably. I've read the latest 
> requirement document and it doesn't yet clearly
> answer the questions I asked in the Atlanta meeting. I feel like I've 
> asked them at several meetings before.
> Can we stop that cycle of repeating the discussion by putting text in 
> the document that directly answers each of these:
>
> In a scenario where you only have one parallel forking SIP proxy, when 
> an INVITE forks to two different
> UAs and _both_ send 200 OKs, do you have one session or two? (This 
> same question applies to early dialogs,
> with or without early media, which is a _normal_ condition, not an 
> race condition like multiple 200 OKs).
>
> PEJ: That would be two communication sessions, one between Alice to 
> Bob-1 and one between Alice and Bob-2.  This is precisely why we use 
> the approach in our proposed solution.  The Session-ID is always 
> comprised of the UUID values from each "endpoint" (which would include 
> MCUs, PSTN GWs, or 3PCC session initiators).
>
>
> If you replace that with a _serial_ forking proxy, where you were in 
> an early dialog with UA1, that got canceled
> and then you ended up in an early dialog, and then a confirmed dialog 
> with UA2, was that one session (with the
> calling UA, UA1, and UA2 involved) or two sessions (one with the 
> calling UA and UA1, the other with the calling
> UA and UA2)?
>
> PEJ: That would be two communication sessions.  Any time there is a 
> different UA on one end, that represents a distinct communication session.
>
>
> If you replace that with a B2BUA that behaves similar to a serial 
> forking proxy in that it only alerts one called thing
> at a time, do you end up with one session or with two.
>
> PEJ: This is similar to the case where a fork is cancelled. Alice is 
> only in one communication session and the SBC has to pick a UUID to 
> return.  However, the UUID can change if the other device actually 
> answers.  For that matter, the SBC could even fabricate a temporary 
> value, knowing there is a 50/50 change it will change, anyway.  What's 
> important is the end result: the "stable call".  Once the call is 
> connected, there are just two devices, Alice and some Bob.  And, if 
> the Bob changes during call establishment, the UUID value will change 
> on that end. That's perfectly fine.
>
I had to read this several times to make sure, but I think the end 
result is that you said "two" (or perhaps even three) here, but if you 
were looking at whole set of messages between the three UAs involved, 
you would never try to identify them all with a single session 
identifier. Did I hear you correctly?

> Paul
>
>
> I don't see how the current document answers those questions. If I've 
> missed that, please point to it and I'll see how
> I can help make them more obvious.
>
> Otherwise, can you please make the answers clear in the document, (not 
> just in an email response).
>
>
> Paul
>
> ------------------------------------------------------------------------
>
> *From:*Paul Kyzivat <pkyzivat@alum.mit.edu> <mailto:pkyzivat@alum.mit.edu>
> *Sent:* Sun Feb 24 01:43:57 EST 2013
> *To:* "Paul E. Jones" <paulej@packetizer.com> 
> <mailto:paulej@packetizer.com>
> *Cc:* insipid@ietf.org <mailto:insipid@ietf.org>
> *Subject:* Re: [Insipid] Are we ready to LC on the requirements?
>
>
>
> On 2/24/13 12:33 AM, Paul E. Jones wrote:
>
>     Paul,
>
>       
>
>     So what concept is vague?
>
>       
>
>     In terms of an H.323 device, I would consider two terminals with users
>
>     at each end to be a communication session. I would consider a terminal
>
>     and an MCU to have a communication session.
>
>       
>
>     The collection of communication sessions on an MCU to which one or more
>
>     terrminals are a party is a conference. And I would like to relate all
>
>     those sessions by the UUID the MCU uses in each of those sessions. That
>
>     value could even be the Conference ID in H.323.
>
>       
>
>     There are gateway devices that connect to the PSTN that I would count as
>
>     equal to a terminal. But, there are gateway devices that bridge IP
>
>     networks (SBCs) that shoul!
>
>       d just
>
>     pass the UUIDs through. The difference
>
>     between the two really is whether it bridges an IPMC device to another
>
>     or to something else.
>
>       
>
>     There are call flows like the one you highlighted in the threads where
>
>     voice comes from one terminal and video from another. That's an MCU,
>
>     really. The session ID exists between Alice and MCU (or PBX). The other
>
>     devices Bob uses might share the UUID of the MCU/PBX, but those are
>
>     distinct communication sessions like the typical MCU case. Yeah, such
>
>     topologies do make it hard to do debugging and the number of UUIDs makes
>
>     it a pain, too, but at least there is consistency in the assignments.
>
>     So, it is doable.
>
>       
>
>     So, how can we make progress here?
>
>   
> We write some rules that any device that terminates more than one dialog
> can use to decide when one dialog should share a session-id with another
> dialog. The rules should get the "right" answer for all the use case!
>   s,
> and should be specific enough so that when applied to any device, no
> matter how weird, most reasonable people would agree with the answer.
> That way we can have a way of judging conformance to this specification.
>   
> I realize this bridges the gap between what the requirements are
> responsible for and what the mechanism is responsible for. But the
> mechanism is about marking communications sessions, not defining them.
>   
> OR I suppose the requirements could kick the can down the road, simply
> say that the mechanism must work for the specified use cases and itself
> must specify the algorithm for making the decision in other cases. But
> that just puts it off.
>   
>   Thanks,
>   Paul K
>   
>
>     Paul
>
>       
>
>       
>
>       
>
>     ------------------------------------------------------------------------
>
>       
>
>     *From:* Paul Kyzivat<pkyzivat@alum.mit.edu>  <mailto:pkyzivat@alum.mit.edu>
>
>     *Sent:* Sat F!
>
>       eb 23
>
>     19:58:41 EST 2013
>
>     *To:* "Paul E. Jones"<paulej@packetizer.com>  <mailto:paulej@packetizer.com>
>
>     *Cc:*insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     *Subject:* Re: [Insipid] Are we ready to LC on the requirements?
>
>       
>
>     On 2/21/13 9:51 PM, Paul E. Jones wrote:
>
>       
>
>     Paul,
>
>       
>
>     I read your message, but was left unsure of exactly how we could
>
>     improve the
>
>     definition over what we have already.
>
>       
>
>     If there is something concrete that you can propose that would help
>
>     lend to
>
>     clarity of the text, I'm definitely willing to put it in. I would
>
>     like to
>
>     move the requirements along and the submission deadline is Monday.
>
>     Do you
>
>     have text you would like to add before the deadline?
>
>       
>
>       
>
>     I'm traveling on business and have limited internet access, and limited
>
>     time, so I probably can't.
>
>       
>
>     In any case, ISTM that the problem isn't that we don't have the right
>
>     words. Rather, we still don't have clear *concepts* that distinguish
>
>     !
>
>     whatshould be covered from what should not. We have some use cases, but
>
>     lack basic principles that can be applied to any case to determine if it
>
>     should be a communication session or not. It still seems to be more in
>
>     the realm of "I know one when I see it."
>
>       
>
>     If we had the principles, then it would probably be straightforward to
>
>     come up with words.
>
>       
>
>     I don't yet see a suitable general principle here that fits the use
>
>     cases and seems to make sense.
>
>       
>
>     Thanks,
>
>     Paul
>
>       
>
>     Paul
>
>       
>
>     -----Original Message-----
>
>     From:insipid-bounces@ietf.org  <mailto:insipid-bounces@ietf.org>  [mailto:insipid-bounces@ietf.org] On
>
>     Behalf Of Paul Kyzivat
>
>     Sent: Friday, January 11, 2013 3:34 PM
>
>     To:insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     Subject: Re: [Insipid] Are we ready to LC on the requirements?
>
>       
>
>     (Sorry that this is long. I don't know how to make it short.)
>
>       
>
>     Are we ready to LC? I don't think so. Specifically I don't think
>
>     we yet
>
>     have an
>
>     unambiguous definition of what is being identified.
>
>       
>
>     This version added some new text:
>
>       
>
>     In this document, the word "session" refers to a "communication
>
>     session" that may exist between two SIP user agents and that may
>
>     pass
>
>     through one or more intermediary devices, including B2BUAs or SIP
>
>     proxies. A communication session consists of one of more SIP
>
>     transactions. A very simple communication session may be a single
>
>     out-of-dialog SIP transaction (e.g., MESSAGE/200). In the case of a
>
>     SIP dialog, the SIP message exchange includes a dialog creating
>
>     INVITE transaction, and zero of more subsequent SIP transactions
>
>     within the same dialog (e.g., ACK, re-INVITE, BYE). Due to the
>
>     existenc! e of middle boxes, there may be multiple related SIP
>
>     transactions or dialogs chained together along the path from one end
>
>     of the communication session to the other. For example:
>
>       
>
>     A Middlebox B
>
>     SIP trans1
>
>     -----------------> SIP trans 2
>
>     SIP dialog 1 <-------------- SIP dialog 2
>
>       
>
>     Figure 1 - Communication Session through a Middlebox
>
>       
>
>     In such cases, the two SIP transactions or dialogs are part of a
>
>     single communication session.
>
>       
>
>     The term "end-to-end" in this document means the communication
>
>     session from the point of origin, passing through any number of
>
>     intermediaries, to the ultimate point of termination. It is
>
>     recognized that legacy devices may not support the "end-to-end"
>
>     session identifier, though an identifier might be created by an
>
>     intermediary when it is absent from the session signaling.
>
>       
>
>     IMO this is a big improvement. But it still isn't as prec! ise
>
>     as I would
>
>     like. What I find lacking in the above is:
>
>       
>
>     o parsing the above, the properties of a communication session are:
>
>     - connects *two* UAs
>
>     - optionally includes one or more intermediary devices
>
>     - one or more
>
>     transactions
>
>     - one out-of-dialog transaction,
>
>     OR a dialog including the dialog establishing transaction
>
>     and some transactions within the dialog.
>
>     - middle boxes may result in chaining dialogs or transactions.
>
>       
>
>     Exactly how all these properties "plug together" fuzzy.
>
>     I'm not at all certain that all readers would reach
>
>     the same conclusion about which cases meet these criteria
>
>     and which don't.
>
>       
>
>     o I'm also not certain that these criteria match all the cases
>
>     people expect, and exclude all the cases people think should
>
>     be excluded.
>
>       
>
>     - I think people expect that a conference is *not* a single
>
>     communications session. But a conference with only two
>
>     participants would! seem to qualify according to all of the
>
>     above criteria. So that suggests that another criterion is
>
>     needed to exclude that case.
>
>       
>
>     - A topologically similar case to the conference is a
>
>     click-to-dial case where a web!
>
>        server
>
>     makes outward INVITEs
>
>     to two UAs and connects them. I think people believe this
>
>     case *should* be a communications session.
>
>       
>
>     - Another case is described in
>
>     http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html
>
>     and debated in the replies to that. Arguments are made for
>
>     different answers to what should get a common session id and what
>
>     should not. For this case I think we need to decide:
>
>     . do we mandate exactly how this should be treated?
>
>     . or do we leave it to the discretion of the B2BUA to decide?
>
>       
>
>     Either way we need to decide what the criteria are that lead
>
>     to the decision.
>
>       
>
>     o! IIRC Hadriel suggested (in a meeting?) that where media
>
>     originates and terminates has something to do with this.
>
>     That doesn't work all the time (e.g. MESSAGE), but it might help
>
>     in some cases. I think he used this to just!
>
>       ify
>
>     that:
>
>       
>
>     - the Conference Bridge Transcoding Model (RFC5369 section 3.2)
>
>     is a single communications session.
>
>       
>
>     - the 3PCC Transcoding Model (RFC5369 section 3.1) is *not*
>
>     a single communications session.
>
>       
>
>     (I'm not convinced - this seems like a distinction without
>
>     a difference.)
>
>       
>
>     Fundamentally we should be able to classify all cases into:
>
>     - those that *should* be communications sessions,
>
>     - those that *shouldn't* be communication sessions,
>
>     - those we don't care about - could be either way.
>
>       
>
>     When we are done, we should be able to apply the definition of
>
>     communication session to any case. When applied to the cases we
>
>     explicitly care about it should deliver the an! swer we expect.
>
>       
>
>     The more weird cases we care about, the more complex and
>
>     unintuitive the
>
>     criteria will be. I suspect that the path we are on will lead to
>
>     complex
>
>     criteria. (We can have a really crisp de!
>
>       finition
>
>     of communications
>
>     session if we don't care much about which cases qualify.)
>
>       
>
>     One idea I considered is to define some new terms that build on
>
>     normal
>
>     sip concepts but extend them to allow B2BUA intermediaries where sip
>
>     allows proxies. E.g.
>
>     - Transaction++ is either a sip transaction, or a series of sip
>
>     transactions linked by B2BUA intermediaries.
>
>       
>
>     - Dialog++ is either a sip dialog, or a series of sip dialogs
>
>     linked by B2BUA intermediaries.
>
>       
>
>     Then would need to define the behavior of a B2BUA intermediary.
>
>     It needs
>
>     to relay transactions from one "side" to the other, preserving
>
>     certain
>
>     invariants (TBD). Presumably it can also originate certain
>
>     transactions,
>
>     but there must be constraints ! on what it can do. There must
>
>     also be some
>
>     rules on how media is handled across one of these intermediaries.
>
>       
>
>     If that was done, then a communication session could be defined as a
>
>     Transaction++ for an out-of-dialog request, or a Dialog++.
>
>       
>
>     But that makes the definition of communication session the first
>
>     priority and the cases that happen to qualify as a communication
>
>     session
>
>     a consequence. It probably won't match people's intuitive
>
>     feelings about
>
>     what *should* be a communication session. So it might not
>
>     satisfy people.
>
>       
>
>     Thanks,
>
>     Paul
>
>       
>
>       
>
>     On 1/10/13 6:04 PM, Charles Eckel (eckelcu) wrote:
>
>       
>
>      From my point of view, the draft looks good. The
>
>     changes incorporated
>
>       
>
>     in this updated version directly address this open issue.
>
>       
>
>     Cheers,
>
>     Charles
>
>       
>
>     -----Original Message-----
>
>     From:insipid-bounces@ietf.org  <mailto:insipid-bounces@ietf.org>
>
>     [mailto:insipid-bounces@ietf.org] On
>
>     Behalf Of Gonzalo Salgueiro (gsalguei)
>
>     Sent: Thursday, January 10, 2013 12:39 PM
>
>     To: Paul E. Jones
>
>     Cc:insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     Subject: Re: [Insipid] Are we ready to LC on the
>
>     requirements?
>
>       
>
>     Thanks for submitting this, Paul. The biggest open issue
>
>     in regards
>
>     to the requirements document was to clearly define what
>
>     it is we are
>
>     identifying (i.e., "communication session") within the
>
>     scope of this
>
>     document and ensure that clearly defined language is used
>
>     consistently through! out the document. Prior to any
>
>     consensus on
>
>     moving to WGLC, the chairs would appreciate hearing the
>
>     group's
>
>     thoughts on where we are on this issue in the current
>
>     version.
>
>       
>
>     Cheers,
>
>       
>
>     Gonzalo & Keith
>
>       
>
>       
>
>       
>
>     On Jan 9, 2013, at 9:23 PM, Paul E. Jones wrote:
>
>       
>
>     Folks,
>
>       
>
>     Dialog has been extremely light on the requirements
>
>     document. Do
>
>       
>
>     people feel generally OK with it as it is now? Can we
>
>     move on to the
>
>     solution document now or are there other changes needed
>
>     in the
>
>     requirements document?
>
>       
>
>     I just posted the -04 versi!
>
>       on with
>
>     changes proposed
>
>     on the list over
>
>     the
>
>       
>
>     past month or so.
>
>       
>
>     Paul
>
>       
>
>     ------------------------------------------------------------------------
>
>       
>
>       
>
>     insipid mailing list
>
>     insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/insipid
>
>       
>
>       
>
>     ------------------------------------------------------------------------
>
>       
>
>       
>
>     insipid mailing list
>
>     insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/insipid
>
>       
>
>     ------------------------------------------------------------------------
>
>       
>
>       
>
>     insipid mailing list
>
>     insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/insipid
>
>       
>
>       
>
>       
>
>     ------------------------------------------------------------------------
>
>       
>
>       
>
>     insipid mailing list
>
>     insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/insipid
>
>       
>
>       
>
>       
>
>       
>
>     ------------------------------------------------------------------------
>
>       
>
>       
>
>     insipid mailing list
>
>     insipid@ietf.org  <mailto:insipid@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/insipid
>
>   
>   
>
>
>
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org  <mailto:insipid@ietf.org>
> https://www.ietf.org/mailman/listinfo/insipid
>


--------------040803070409090305010401
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/4/13 8:27 AM, Paul E. Jones wrote:<br>
    </div>
    <blockquote
      cite="mid:013401ce18e4$7061a2a0$5124e7e0$@packetizer.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Robert,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We&#8217;ll
            try to cover this in the meeting with slides and then
            incorporate in slides subsequently.&nbsp; I have an answer for
            each.&nbsp; That said, please do allow me to provide an answer
            below that we can discuss before then.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Paul<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                  <a class="moz-txt-link-abbreviated" href="mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a>
                  [<a class="moz-txt-link-freetext" href="mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org</a>] <b>On Behalf Of </b>Robert
                  Sparks<br>
                  <b>Sent:</b> Friday, March 01, 2013 3:18 PM<br>
                  <b>To:</b> Paul E. Jones<br>
                  <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>; Paul Kyzivat<br>
                  <b>Subject:</b> Re: [Insipid] Are we ready to LC on
                  the requirements?<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <div>
            <p class="MsoNormal">On 2/24/13 8:38 AM, Paul E. Jones
              wrote:<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal">Paul,<br>
              <br>
              That still begs the question of "what language do we need
              to add or change to make this clear?" In my mind, I know
              exactly what an endpoint needs to do and what an SBC needs
              to do. But, I'll not say it does not need more charity for
              those that do not have it clear in their minds.<br>
              <br>
              But, perhaps being too close to the work, I'm having
              trouble seeing where it is vague. Can you suggest text?<o:p></o:p></p>
          </blockquote>
          <p class="MsoNormal">This is frustrating, for both of us
            probably. I've read the latest requirement document and it
            doesn't yet clearly<br>
            answer the questions I asked in the Atlanta meeting. I feel
            like I've asked them at several meetings before.<br>
            Can we stop that cycle of repeating the discussion by
            putting text in the document that directly answers each of
            these:<br>
            <br>
            In a scenario where you only have one parallel forking SIP
            proxy, when an INVITE forks to two different<br>
            UAs and _both_ send 200 OKs, do you have one session or two?
            (This same question applies to early dialogs,<br>
            with or without early media, which is a _normal_ condition,
            not an race condition like multiple 200 OKs).<span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:green">PEJ:
              That would be two communication sessions, one between
              Alice to Bob-1 and one between Alice and Bob-2.&nbsp; This is
              precisely why we use the approach in our proposed
              solution.&nbsp; The Session-ID is always comprised of the UUID
              values from each &#8220;endpoint&#8221; (which would include MCUs,
              PSTN GWs, or 3PCC session initiators).</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><br>
            If you replace that with a _serial_ forking proxy, where you
            were in an early dialog with UA1, that got canceled<br>
            and then you ended up in an early dialog, and then a
            confirmed dialog with UA2, was that one session (with the<br>
            calling UA, UA1, and UA2 involved) or two sessions (one with
            the calling UA and UA1, the other with the calling<br>
            UA and UA2)?<span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:green">PEJ:
              That would be two communication sessions.&nbsp; Any time there
              is a different UA on one end, that represents a distinct
              communication session.<o:p></o:p></span></p>
          <p class="MsoNormal"><br>
            If you replace that with a B2BUA that behaves similar to a
            serial forking proxy in that it only alerts one called thing<br>
            at a time, do you end up with one session or with two.<span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:green">PEJ:
              This is similar to the case where a fork is cancelled.&nbsp;
              Alice is only in one communication session and the SBC has
              to pick a UUID to return.&nbsp; However, the UUID can change if
              the other device actually answers.&nbsp; For that matter, the
              SBC could even fabricate a temporary value, knowing there
              is a 50/50 change it will change, anyway.&nbsp; What&#8217;s
              important is the end result: the &#8220;stable call&#8221;.&nbsp; Once the
              call is connected, there are just two devices, Alice and
              some Bob.&nbsp; And, if the Bob changes during call
              establishment, the UUID value will change on that end.&nbsp;
              That&#8217;s perfectly fine.</span></p>
        </div>
      </div>
    </blockquote>
    I had to read this several times to make sure, but I think the end
    result is that you said "two" (or perhaps even three) here, but if
    you were looking at whole set of messages between the three UAs
    involved, you would never try to identify them all with a single
    session identifier. Did I hear you correctly?<br>
    <br>
    <blockquote
      cite="mid:013401ce18e4$7061a2a0$5124e7e0$@packetizer.com"
      type="cite">
      <div class="WordSection1">
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:green"><o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:green"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:green">Paul<o:p></o:p></span></p>
          <p class="MsoNormal"><br>
            I don't see how the current document answers those
            questions. If I've missed that, please point to it and I'll
            see how<br>
            I can help make them more obvious.<br>
            <br>
            Otherwise, can you please make the answers clear in the
            document, (not just in an email response).<br>
            <br>
            <o:p></o:p></p>
          <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
            Paul<o:p></o:p></p>
          <div>
            <div class="MsoNormal" style="text-align:center"
              align="center"><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                <hr align="center" size="2" width="100%"></span></div>
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                Paul Kyzivat <a moz-do-not-send="true"
                  href="mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a><br>
                <b>Sent:</b> Sun Feb 24 01:43:57 EST 2013<br>
                <b>To:</b> "Paul E. Jones" <a moz-do-not-send="true"
                  href="mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a><br>
                <b>Cc:</b> <a moz-do-not-send="true"
                  href="mailto:insipid@ietf.org">insipid@ietf.org</a><br>
                <b>Subject:</b> Re: [Insipid] Are we ready to LC on the
                requirements?<o:p></o:p></span></p>
          </div>
          <p class="MsoNormal"><br>
            <br>
            <o:p></o:p></p>
          <pre>On 2/24/13 12:33 AM, Paul E. Jones wrote:<o:p></o:p></pre>
          <blockquote style="border:none;border-left:solid #729FCF
            1.0pt;padding:0in 0in 0in
            6.0pt;margin-left:4.8pt;margin-right:0in;margin-bottom:6.0pt">
            <pre>Paul,<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>So what concept is vague?<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>In terms of an H.323 device, I would consider two terminals with users<o:p></o:p></pre>
            <pre>at each end to be a communication session. I would consider a terminal<o:p></o:p></pre>
            <pre>and an MCU to have a communication session.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>The collection of communication sessions on an MCU to which one or more<o:p></o:p></pre>
            <pre>terrminals are a party is a conference. And I would like to relate all<o:p></o:p></pre>
            <pre>those sessions by the UUID the MCU uses in each of those sessions. That<o:p></o:p></pre>
            <pre>value could even be the Conference ID in H.323.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>There are gateway devices that connect to the PSTN that I would count as<o:p></o:p></pre>
            <pre>equal to a terminal. But, there are gateway devices that bridge IP<o:p></o:p></pre>
            <pre>networks (SBCs) that shoul!<o:p></o:p></pre>
            <pre> d just<o:p></o:p></pre>
            <pre>pass the UUIDs through. The difference<o:p></o:p></pre>
            <pre>between the two really is whether it bridges an IPMC device to another<o:p></o:p></pre>
            <pre>or to something else.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>There are call flows like the one you highlighted in the threads where<o:p></o:p></pre>
            <pre>voice comes from one terminal and video from another. That's an MCU,<o:p></o:p></pre>
            <pre>really. The session ID exists between Alice and MCU (or PBX). The other<o:p></o:p></pre>
            <pre>devices Bob uses might share the UUID of the MCU/PBX, but those are<o:p></o:p></pre>
            <pre>distinct communication sessions like the typical MCU case. Yeah, such<o:p></o:p></pre>
            <pre>topologies do make it hard to do debugging and the number of UUIDs makes<o:p></o:p></pre>
            <pre>it a pain, too, but at least there is consistency in the assignments.<o:p></o:p></pre>
            <pre>So, it is doable.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>So, how can we make progress here?<o:p></o:p></pre>
          </blockquote>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre>We write some rules that any device that terminates more than one dialog <o:p></o:p></pre>
          <pre>can use to decide when one dialog should share a session-id with another <o:p></o:p></pre>
          <pre>dialog. The rules should get the "right" answer for all the use case!<o:p></o:p></pre>
          <pre> s, <o:p></o:p></pre>
          <pre>and should be specific enough so that when applied to any device, no <o:p></o:p></pre>
          <pre>matter how weird, most reasonable people would agree with the answer. <o:p></o:p></pre>
          <pre>That way we can have a way of judging conformance to this specification.<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre>I realize this bridges the gap between what the requirements are <o:p></o:p></pre>
          <pre>responsible for and what the mechanism is responsible for. But the <o:p></o:p></pre>
          <pre>mechanism is about marking communications sessions, not defining them.<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre>OR I suppose the requirements could kick the can down the road, simply <o:p></o:p></pre>
          <pre>say that the mechanism must work for the specified use cases and itself <o:p></o:p></pre>
          <pre>must specify the algorithm for making the decision in other cases. But <o:p></o:p></pre>
          <pre>that just puts it off.<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre> Thanks,<o:p></o:p></pre>
          <pre> Paul K<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <blockquote style="border:none;border-left:solid #729FCF
            1.0pt;padding:0in 0in 0in
            6.0pt;margin-left:4.8pt;margin-right:0in;margin-bottom:6.0pt">
            <pre>Paul<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre style="text-align:center"><hr align="center" size="2" width="100%"></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>*From:* Paul Kyzivat <a moz-do-not-send="true" href="mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a><o:p></o:p></pre>
            <pre>*Sent:* Sat F!<o:p></o:p></pre>
            <pre> eb 23<o:p></o:p></pre>
            <pre>19:58:41 EST 2013<o:p></o:p></pre>
            <pre>*To:* "Paul E. Jones" <a moz-do-not-send="true" href="mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a><o:p></o:p></pre>
            <pre>*Cc:* <a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre>*Subject:* Re: [Insipid] Are we ready to LC on the requirements?<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>On 2/21/13 9:51 PM, Paul E. Jones wrote:<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Paul,<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>I read your message, but was left unsure of exactly how we could<o:p></o:p></pre>
            <pre>improve the<o:p></o:p></pre>
            <pre>definition over what we have already.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>If there is something concrete that you can propose that would help<o:p></o:p></pre>
            <pre>lend to<o:p></o:p></pre>
            <pre>clarity of the text, I'm definitely willing to put it in. I would<o:p></o:p></pre>
            <pre>like to<o:p></o:p></pre>
            <pre>move the requirements along and the submission deadline is Monday.<o:p></o:p></pre>
            <pre>Do you<o:p></o:p></pre>
            <pre>have text you would like to add before the deadline?<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>I'm traveling on business and have limited internet access, and limited<o:p></o:p></pre>
            <pre>time, so I probably can't.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>In any case, ISTM that the problem isn't that we don't have the right<o:p></o:p></pre>
            <pre>words. Rather, we still don't have clear *concepts* that distinguish<o:p></o:p></pre>
            <pre>!<o:p></o:p></pre>
            <pre>whatshould be covered from what should not. We have some use cases, but<o:p></o:p></pre>
            <pre>lack basic principles that can be applied to any case to determine if it<o:p></o:p></pre>
            <pre>should be a communication session or not. It still seems to be more in<o:p></o:p></pre>
            <pre>the realm of "I know one when I see it."<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>If we had the principles, then it would probably be straightforward to<o:p></o:p></pre>
            <pre>come up with words.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>I don't yet see a suitable general principle here that fits the use<o:p></o:p></pre>
            <pre>cases and seems to make sense.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Thanks,<o:p></o:p></pre>
            <pre>Paul<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Paul<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>-----Original Message-----<o:p></o:p></pre>
            <pre>From: <a moz-do-not-send="true" href="mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a> [<a moz-do-not-send="true" href="mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org</a>] On<o:p></o:p></pre>
            <pre>Behalf Of Paul Kyzivat<o:p></o:p></pre>
            <pre>Sent: Friday, January 11, 2013 3:34 PM<o:p></o:p></pre>
            <pre>To: <a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre>Subject: Re: [Insipid] Are we ready to LC on the requirements?<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>(Sorry that this is long. I don't know how to make it short.)<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Are we ready to LC? I don't think so. Specifically I don't think<o:p></o:p></pre>
            <pre>we yet<o:p></o:p></pre>
            <pre>have an<o:p></o:p></pre>
            <pre>unambiguous definition of what is being identified.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>This version added some new text:<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>In this document, the word "session" refers to a "communication<o:p></o:p></pre>
            <pre>session" that may exist between two SIP user agents and that may<o:p></o:p></pre>
            <pre>pass<o:p></o:p></pre>
            <pre>through one or more intermediary devices, including B2BUAs or SIP<o:p></o:p></pre>
            <pre>proxies. A communication session consists of one of more SIP<o:p></o:p></pre>
            <pre>transactions. A very simple communication session may be a single<o:p></o:p></pre>
            <pre>out-of-dialog SIP transaction (e.g., MESSAGE/200). In the case of a<o:p></o:p></pre>
            <pre>SIP dialog, the SIP message exchange includes a dialog creating<o:p></o:p></pre>
            <pre>INVITE transaction, and zero of more subsequent SIP transactions<o:p></o:p></pre>
            <pre>within the same dialog (e.g., ACK, re-INVITE, BYE). Due to the<o:p></o:p></pre>
            <pre>existenc! e of middle boxes, there may be multiple related SIP<o:p></o:p></pre>
            <pre>transactions or dialogs chained together along the path from one end<o:p></o:p></pre>
            <pre>of the communication session to the other. For example:<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>A Middlebox B<o:p></o:p></pre>
            <pre>SIP trans1<o:p></o:p></pre>
            <pre>-----------------&gt; SIP trans 2<o:p></o:p></pre>
            <pre>SIP dialog 1 &lt;-------------- SIP dialog 2<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Figure 1 - Communication Session through a Middlebox<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>In such cases, the two SIP transactions or dialogs are part of a<o:p></o:p></pre>
            <pre>single communication session.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>The term "end-to-end" in this document means the communication<o:p></o:p></pre>
            <pre>session from the point of origin, passing through any number of<o:p></o:p></pre>
            <pre>intermediaries, to the ultimate point of termination. It is<o:p></o:p></pre>
            <pre>recognized that legacy devices may not support the "end-to-end"<o:p></o:p></pre>
            <pre>session identifier, though an identifier might be created by an<o:p></o:p></pre>
            <pre>intermediary when it is absent from the session signaling.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>IMO this is a big improvement. But it still isn't as prec! ise<o:p></o:p></pre>
            <pre>as I would<o:p></o:p></pre>
            <pre>like. What I find lacking in the above is:<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>o parsing the above, the properties of a communication session are:<o:p></o:p></pre>
            <pre>- connects *two* UAs<o:p></o:p></pre>
            <pre>- optionally includes one or more intermediary devices<o:p></o:p></pre>
            <pre>- one or more<o:p></o:p></pre>
            <pre>transactions<o:p></o:p></pre>
            <pre>- one out-of-dialog transaction,<o:p></o:p></pre>
            <pre>OR a dialog including the dialog establishing transaction<o:p></o:p></pre>
            <pre>and some transactions within the dialog.<o:p></o:p></pre>
            <pre>- middle boxes may result in chaining dialogs or transactions.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Exactly how all these properties "plug together" fuzzy.<o:p></o:p></pre>
            <pre>I'm not at all certain that all readers would reach<o:p></o:p></pre>
            <pre>the same conclusion about which cases meet these criteria<o:p></o:p></pre>
            <pre>and which don't.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>o I'm also not certain that these criteria match all the cases<o:p></o:p></pre>
            <pre>people expect, and exclude all the cases people think should<o:p></o:p></pre>
            <pre>be excluded.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>- I think people expect that a conference is *not* a single<o:p></o:p></pre>
            <pre>communications session. But a conference with only two<o:p></o:p></pre>
            <pre>participants would! seem to qualify according to all of the<o:p></o:p></pre>
            <pre>above criteria. So that suggests that another criterion is<o:p></o:p></pre>
            <pre>needed to exclude that case.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>- A topologically similar case to the conference is a<o:p></o:p></pre>
            <pre>click-to-dial case where a web!<o:p></o:p></pre>
            <pre>&nbsp; server<o:p></o:p></pre>
            <pre>makes outward INVITEs<o:p></o:p></pre>
            <pre>to two UAs and connects them. I think people believe this<o:p></o:p></pre>
            <pre>case *should* be a communications session.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>- Another case is described in<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html">http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html</a><o:p></o:p></pre>
            <pre>and debated in the replies to that. Arguments are made for<o:p></o:p></pre>
            <pre>different answers to what should get a common session id and what<o:p></o:p></pre>
            <pre>should not. For this case I think we need to decide:<o:p></o:p></pre>
            <pre>. do we mandate exactly how this should be treated?<o:p></o:p></pre>
            <pre>. or do we leave it to the discretion of the B2BUA to decide?<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Either way we need to decide what the criteria are that lead<o:p></o:p></pre>
            <pre>to the decision.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>o! IIRC Hadriel suggested (in a meeting?) that where media<o:p></o:p></pre>
            <pre>originates and terminates has something to do with this.<o:p></o:p></pre>
            <pre>That doesn't work all the time (e.g. MESSAGE), but it might help<o:p></o:p></pre>
            <pre>in some cases. I think he used this to just!<o:p></o:p></pre>
            <pre> ify<o:p></o:p></pre>
            <pre>that:<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>- the Conference Bridge Transcoding Model (RFC5369 section 3.2)<o:p></o:p></pre>
            <pre>is a single communications session.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>- the 3PCC Transcoding Model (RFC5369 section 3.1) is *not*<o:p></o:p></pre>
            <pre>a single communications session.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>(I'm not convinced - this seems like a distinction without<o:p></o:p></pre>
            <pre>a difference.)<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Fundamentally we should be able to classify all cases into:<o:p></o:p></pre>
            <pre>- those that *should* be communications sessions,<o:p></o:p></pre>
            <pre>- those that *shouldn't* be communication sessions,<o:p></o:p></pre>
            <pre>- those we don't care about - could be either way.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>When we are done, we should be able to apply the definition of<o:p></o:p></pre>
            <pre>communication session to any case. When applied to the cases we<o:p></o:p></pre>
            <pre>explicitly care about it should deliver the an! swer we expect.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>The more weird cases we care about, the more complex and<o:p></o:p></pre>
            <pre>unintuitive the<o:p></o:p></pre>
            <pre>criteria will be. I suspect that the path we are on will lead to<o:p></o:p></pre>
            <pre>complex<o:p></o:p></pre>
            <pre>criteria. (We can have a really crisp de!<o:p></o:p></pre>
            <pre> finition<o:p></o:p></pre>
            <pre>of communications<o:p></o:p></pre>
            <pre>session if we don't care much about which cases qualify.)<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>One idea I considered is to define some new terms that build on<o:p></o:p></pre>
            <pre>normal<o:p></o:p></pre>
            <pre>sip concepts but extend them to allow B2BUA intermediaries where sip<o:p></o:p></pre>
            <pre>allows proxies. E.g.<o:p></o:p></pre>
            <pre>- Transaction++ is either a sip transaction, or a series of sip<o:p></o:p></pre>
            <pre>transactions linked by B2BUA intermediaries.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>- Dialog++ is either a sip dialog, or a series of sip dialogs<o:p></o:p></pre>
            <pre>linked by B2BUA intermediaries.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Then would need to define the behavior of a B2BUA intermediary.<o:p></o:p></pre>
            <pre>It needs<o:p></o:p></pre>
            <pre>to relay transactions from one "side" to the other, preserving<o:p></o:p></pre>
            <pre>certain<o:p></o:p></pre>
            <pre>invariants (TBD). Presumably it can also originate certain<o:p></o:p></pre>
            <pre>transactions,<o:p></o:p></pre>
            <pre>but there must be constraints ! on what it can do. There must<o:p></o:p></pre>
            <pre>also be some<o:p></o:p></pre>
            <pre>rules on how media is handled across one of these intermediaries.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>If that was done, then a communication session could be defined as a<o:p></o:p></pre>
            <pre>Transaction++ for an out-of-dialog request, or a Dialog++.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>But that makes the definition of communication session the first<o:p></o:p></pre>
            <pre>priority and the cases that happen to qualify as a communication<o:p></o:p></pre>
            <pre>session<o:p></o:p></pre>
            <pre>a consequence. It probably won't match people's intuitive<o:p></o:p></pre>
            <pre>feelings about<o:p></o:p></pre>
            <pre>what *should* be a communication session. So it might not<o:p></o:p></pre>
            <pre>satisfy people.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Thanks,<o:p></o:p></pre>
            <pre>Paul<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>On 1/10/13 6:04 PM, Charles Eckel (eckelcu) wrote:<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>From my point of view, the draft looks good. The<o:p></o:p></pre>
            <pre>changes incorporated<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>in this updated version directly address this open issue.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Cheers,<o:p></o:p></pre>
            <pre>Charles<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>-----Original Message-----<o:p></o:p></pre>
            <pre>From: <a moz-do-not-send="true" href="mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a><o:p></o:p></pre>
            <pre>[<a moz-do-not-send="true" href="mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org</a>] On<o:p></o:p></pre>
            <pre>Behalf Of Gonzalo Salgueiro (gsalguei)<o:p></o:p></pre>
            <pre>Sent: Thursday, January 10, 2013 12:39 PM<o:p></o:p></pre>
            <pre>To: Paul E. Jones<o:p></o:p></pre>
            <pre>Cc: <a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre>Subject: Re: [Insipid] Are we ready to LC on the<o:p></o:p></pre>
            <pre>requirements?<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Thanks for submitting this, Paul. The biggest open issue<o:p></o:p></pre>
            <pre>in regards<o:p></o:p></pre>
            <pre>to the requirements document was to clearly define what<o:p></o:p></pre>
            <pre>it is we are<o:p></o:p></pre>
            <pre>identifying (i.e., "communication session") within the<o:p></o:p></pre>
            <pre>scope of this<o:p></o:p></pre>
            <pre>document and ensure that clearly defined language is used<o:p></o:p></pre>
            <pre>consistently through! out the document. Prior to any<o:p></o:p></pre>
            <pre>consensus on<o:p></o:p></pre>
            <pre>moving to WGLC, the chairs would appreciate hearing the<o:p></o:p></pre>
            <pre>group's<o:p></o:p></pre>
            <pre>thoughts on where we are on this issue in the current<o:p></o:p></pre>
            <pre>version.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Cheers,<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Gonzalo &amp; Keith<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>On Jan 9, 2013, at 9:23 PM, Paul E. Jones wrote:<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Folks,<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Dialog has been extremely light on the requirements<o:p></o:p></pre>
            <pre>document. Do<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>people feel generally OK with it as it is now? Can we<o:p></o:p></pre>
            <pre>move on to the<o:p></o:p></pre>
            <pre>solution document now or are there other changes needed<o:p></o:p></pre>
            <pre>in the<o:p></o:p></pre>
            <pre>requirements document?<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>I just posted the -04 versi!<o:p></o:p></pre>
            <pre> on with<o:p></o:p></pre>
            <pre>changes proposed<o:p></o:p></pre>
            <pre>on the list over<o:p></o:p></pre>
            <pre>the<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>past month or so.<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>Paul<o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre style="text-align:center"><hr align="center" size="2" width="100%"></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>insipid mailing list<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a><o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre style="text-align:center"><hr align="center" size="2" width="100%"></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>insipid mailing list<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a><o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre style="text-align:center"><hr align="center" size="2" width="100%"></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>insipid mailing list<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a><o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre style="text-align:center"><hr align="center" size="2" width="100%"></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>insipid mailing list<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a><o:p></o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre style="text-align:center"><hr align="center" size="2" width="100%"></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre><o:p>&nbsp;</o:p></pre>
            <pre>insipid mailing list<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a><o:p></o:p></pre>
          </blockquote>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <p class="MsoNormal"><br>
            <br>
            <br>
            <o:p></o:p></p>
          <pre>_______________________________________________<o:p></o:p></pre>
          <pre>insipid mailing list<o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a><o:p></o:p></pre>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------040803070409090305010401--

From paulej@packetizer.com  Mon Mar  4 07:43:56 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D285521F8558 for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 07:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v7Hh5YoXKz2A for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 07:43:47 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 7DAA921F8A84 for <insipid@ietf.org>; Mon,  4 Mar 2013 07:43:47 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r24FhjwC004630 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 4 Mar 2013 10:43:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362411826; bh=NHm5YtUwad/nmdrbworxf0wXsRsGFvzDr004KGQOyeU=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=Z4kaDMqACIiGdd+hTTjdvvvg7zWdadMEVv9GSCuq8n4ERzlDs6Km2Pb/Ya6gw0dpg LB5pDalzead/VjKYRHHM03Ci1bNHm2dyx/7n9+2dUxCJEMJY9ZyzO0CxYUGKXkpEQw QC3rOLM3StWF1xgLSCT5Bp0dOIY5ijeaPlTQJwmU=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Robert Sparks'" <rjsparks@nostrum.com>
References: <055801cdeed9$8b441060$a1cc3120$@packetizer.com>	<5F864ABC-E17F-44C9-8CDE-D6C5A32BF214@cisco.com>	<92B7E61ADAC1BB4F941F943788C0882804728936@xmb-aln-x08.cisco.com>	<50F07742.3030601@alum.mit.edu>	<0a0e01ce10a7$875a0690$960e13b0$@packetizer.com>	<512965C1.2090204@alum.mit.edu>	<55fa36b1-465e-40e0-b875-90fb48f3fc13@email.android.com>	<5129B6AD.6010306@alum.mit.edu>	<fab2d64c-7f69-4575-a372-15d78237e667@email.android.com> <51310CEC.1070907@nostrum.com> <013401ce18e4$7061a2a0$5124e7e0$@packetizer.com> <5134B967.2010509@nostrum.com>
In-Reply-To: <5134B967.2010509@nostrum.com>
Date: Mon, 4 Mar 2013 10:43:58 -0500
Message-ID: <018c01ce18ef$1611aab0$42350010$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_018D_01CE18C5.2D400F80"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHTUbyWWA5m3crBY/au5zDaSqMbPQHgf0hnAhmddX0CpBjqowIxbGDRAeh2nkEBtHmmmAGjQg/hAfb7tOQDFd7KkQKK0rjmAvtw0qGXxhwy8A==
Content-Language: en-us
Cc: insipid@ietf.org, 'Paul Kyzivat' <pkyzivat@alum.mit.edu>
Subject: Re: [Insipid] Are we ready to LC on the requirements?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 15:43:56 -0000

This is a multipart message in MIME format.

------=_NextPart_000_018D_01CE18C5.2D400F80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Robert,

 

Comments down below:

 

From: Robert Sparks [mailto:rjsparks@nostrum.com] 
Sent: Monday, March 04, 2013 10:11 AM
To: Paul E. Jones
Cc: insipid@ietf.org; 'Paul Kyzivat'
Subject: Re: [Insipid] Are we ready to LC on the requirements?

 

On 3/4/13 8:27 AM, Paul E. Jones wrote:

Robert,

 

We'll try to cover this in the meeting with slides and then incorporate in
slides subsequently.  I have an answer for each.  That said, please do allow
me to provide an answer below that we can discuss before then.

 

PEJ: meant to say "document" above.

 

Paul

 

From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On Behalf
Of Robert Sparks
Sent: Friday, March 01, 2013 3:18 PM
To: Paul E. Jones
Cc: insipid@ietf.org; Paul Kyzivat
Subject: Re: [Insipid] Are we ready to LC on the requirements?

 

On 2/24/13 8:38 AM, Paul E. Jones wrote:

Paul,

That still begs the question of "what language do we need to add or change
to make this clear?" In my mind, I know exactly what an endpoint needs to do
and what an SBC needs to do. But, I'll not say it does not need more charity
for those that do not have it clear in their minds.

But, perhaps being too close to the work, I'm having trouble seeing where it
is vague. Can you suggest text?

This is frustrating, for both of us probably. I've read the latest
requirement document and it doesn't yet clearly
answer the questions I asked in the Atlanta meeting. I feel like I've asked
them at several meetings before.
Can we stop that cycle of repeating the discussion by putting text in the
document that directly answers each of these:

In a scenario where you only have one parallel forking SIP proxy, when an
INVITE forks to two different
UAs and _both_ send 200 OKs, do you have one session or two? (This same
question applies to early dialogs,
with or without early media, which is a _normal_ condition, not an race
condition like multiple 200 OKs).

 

PEJ: That would be two communication sessions, one between Alice to Bob-1
and one between Alice and Bob-2.  This is precisely why we use the approach
in our proposed solution.  The Session-ID is always comprised of the UUID
values from each "endpoint" (which would include MCUs, PSTN GWs, or 3PCC
session initiators).


If you replace that with a _serial_ forking proxy, where you were in an
early dialog with UA1, that got canceled
and then you ended up in an early dialog, and then a confirmed dialog with
UA2, was that one session (with the
calling UA, UA1, and UA2 involved) or two sessions (one with the calling UA
and UA1, the other with the calling
UA and UA2)?

 

PEJ: That would be two communication sessions.  Any time there is a
different UA on one end, that represents a distinct communication session.


If you replace that with a B2BUA that behaves similar to a serial forking
proxy in that it only alerts one called thing
at a time, do you end up with one session or with two.

 

PEJ: This is similar to the case where a fork is cancelled.  Alice is only
in one communication session and the SBC has to pick a UUID to return.
However, the UUID can change if the other device actually answers.  For that
matter, the SBC could even fabricate a temporary value, knowing there is a
50/50 change it will change, anyway.  What's important is the end result:
the "stable call".  Once the call is connected, there are just two devices,
Alice and some Bob.  And, if the Bob changes during call establishment, the
UUID value will change on that end.  That's perfectly fine.

I had to read this several times to make sure, but I think the end result is
that you said "two" (or perhaps even three) here, but if you were looking at
whole set of messages between the three UAs involved, you would never try to
identify them all with a single session identifier. Did I hear you
correctly?



PEJ: Alice sends an INVITE and gets back a single 180, even if the B2BUA
gets 10 180s, right?  In that case, there are 10 Bobs ringing and there
would be 10 communication sessions {Alice, Bob-1}, {Alice, Bob-2}, ..
However, only the SBC sees those.  That's because the SBC is not forwarding
all messages to Alice.  The SBC is going to forward something to Alice.
Would this be Bob-1 or some UUID fabricated by the SBC?  Does not really
matter, since the remote end is allowed to change.  So, the SBC could send a
UUID such that Alice has {Alice, SBC}, but then when Bob-5 sends a 200,
Alice updates her Session-ID to be { Alice, Bob-5 }.  Because session
establishment works like this, we need something that is flexible enough to
accommodate.  That's the reason we propose to use two UUIID values.  Each
UUID identifies a particular physical or logical endpoint in a session.  The
set of two UUIDs define the communication session comprised of those two
endpoints.

 

Paul

 





 

Paul


I don't see how the current document answers those questions. If I've missed
that, please point to it and I'll see how
I can help make them more obvious.

Otherwise, can you please make the answers clear in the document, (not just
in an email response).





Paul

  _____  

From: Paul Kyzivat  <mailto:pkyzivat@alum.mit.edu> <pkyzivat@alum.mit.edu>
Sent: Sun Feb 24 01:43:57 EST 2013
To: "Paul E. Jones"  <mailto:paulej@packetizer.com> <paulej@packetizer.com>
Cc: insipid@ietf.org
Subject: Re: [Insipid] Are we ready to LC on the requirements?






On 2/24/13 12:33 AM, Paul E. Jones wrote:

Paul,
 
So what concept is vague?
 
In terms of an H.323 device, I would consider two terminals with users
at each end to be a communication session. I would consider a terminal
and an MCU to have a communication session.
 
The collection of communication sessions on an MCU to which one or more
terrminals are a party is a conference. And I would like to relate all
those sessions by the UUID the MCU uses in each of those sessions. That
value could even be the Conference ID in H.323.
 
There are gateway devices that connect to the PSTN that I would count as
equal to a terminal. But, there are gateway devices that bridge IP
networks (SBCs) that shoul!
 d just
pass the UUIDs through. The difference
between the two really is whether it bridges an IPMC device to another
or to something else.
 
There are call flows like the one you highlighted in the threads where
voice comes from one terminal and video from another. That's an MCU,
really. The session ID exists between Alice and MCU (or PBX). The other
devices Bob uses might share the UUID of the MCU/PBX, but those are
distinct communication sessions like the typical MCU case. Yeah, such
topologies do make it hard to do debugging and the number of UUIDs makes
it a pain, too, but at least there is consistency in the assignments.
So, it is doable.
 
So, how can we make progress here?

 
We write some rules that any device that terminates more than one dialog 
can use to decide when one dialog should share a session-id with another 
dialog. The rules should get the "right" answer for all the use case!
 s, 
and should be specific enough so that when applied to any device, no 
matter how weird, most reasonable people would agree with the answer. 
That way we can have a way of judging conformance to this specification.
 
I realize this bridges the gap between what the requirements are 
responsible for and what the mechanism is responsible for. But the 
mechanism is about marking communications sessions, not defining them.
 
OR I suppose the requirements could kick the can down the road, simply 
say that the mechanism must work for the specified use cases and itself 
must specify the algorithm for making the decision in other cases. But 
that just puts it off.
 
 Thanks,
 Paul K
 

Paul
 
 
 


  _____  

 
*From:* Paul Kyzivat  <mailto:pkyzivat@alum.mit.edu> <pkyzivat@alum.mit.edu>
*Sent:* Sat F!
 eb 23
19:58:41 EST 2013
*To:* "Paul E. Jones"  <mailto:paulej@packetizer.com>
<paulej@packetizer.com>
*Cc:* insipid@ietf.org
*Subject:* Re: [Insipid] Are we ready to LC on the requirements?
 
On 2/21/13 9:51 PM, Paul E. Jones wrote:
 
Paul,
 
I read your message, but was left unsure of exactly how we could
improve the
definition over what we have already.
 
If there is something concrete that you can propose that would help
lend to
clarity of the text, I'm definitely willing to put it in. I would
like to
move the requirements along and the submission deadline is Monday.
Do you
have text you would like to add before the deadline?
 
 
I'm traveling on business and have limited internet access, and limited
time, so I probably can't.
 
In any case, ISTM that the problem isn't that we don't have the right
words. Rather, we still don't have clear *concepts* that distinguish
!
whatshould be covered from what should not. We have some use cases, but
lack basic principles that can be applied to any case to determine if it
should be a communication session or not. It still seems to be more in
the realm of "I know one when I see it."
 
If we had the principles, then it would probably be straightforward to
come up with words.
 
I don't yet see a suitable general principle here that fits the use
cases and seems to make sense.
 
Thanks,
Paul
 
Paul
 
-----Original Message-----
From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
Behalf Of Paul Kyzivat
Sent: Friday, January 11, 2013 3:34 PM
To: insipid@ietf.org
Subject: Re: [Insipid] Are we ready to LC on the requirements?
 
(Sorry that this is long. I don't know how to make it short.)
 
Are we ready to LC? I don't think so. Specifically I don't think
we yet
have an
unambiguous definition of what is being identified.
 
This version added some new text:
 
In this document, the word "session" refers to a "communication
session" that may exist between two SIP user agents and that may
pass
through one or more intermediary devices, including B2BUAs or SIP
proxies. A communication session consists of one of more SIP
transactions. A very simple communication session may be a single
out-of-dialog SIP transaction (e.g., MESSAGE/200). In the case of a
SIP dialog, the SIP message exchange includes a dialog creating
INVITE transaction, and zero of more subsequent SIP transactions
within the same dialog (e.g., ACK, re-INVITE, BYE). Due to the
existenc! e of middle boxes, there may be multiple related SIP
transactions or dialogs chained together along the path from one end
of the communication session to the other. For example:
 
A Middlebox B
SIP trans1
-----------------> SIP trans 2
SIP dialog 1 <-------------- SIP dialog 2
 
Figure 1 - Communication Session through a Middlebox
 
In such cases, the two SIP transactions or dialogs are part of a
single communication session.
 
The term "end-to-end" in this document means the communication
session from the point of origin, passing through any number of
intermediaries, to the ultimate point of termination. It is
recognized that legacy devices may not support the "end-to-end"
session identifier, though an identifier might be created by an
intermediary when it is absent from the session signaling.
 
IMO this is a big improvement. But it still isn't as prec! ise
as I would
like. What I find lacking in the above is:
 
o parsing the above, the properties of a communication session are:
- connects *two* UAs
- optionally includes one or more intermediary devices
- one or more
transactions
- one out-of-dialog transaction,
OR a dialog including the dialog establishing transaction
and some transactions within the dialog.
- middle boxes may result in chaining dialogs or transactions.
 
Exactly how all these properties "plug together" fuzzy.
I'm not at all certain that all readers would reach
the same conclusion about which cases meet these criteria
and which don't.
 
o I'm also not certain that these criteria match all the cases
people expect, and exclude all the cases people think should
be excluded.
 
- I think people expect that a conference is *not* a single
communications session. But a conference with only two
participants would! seem to qualify according to all of the
above criteria. So that suggests that another criterion is
needed to exclude that case.
 
- A topologically similar case to the conference is a
click-to-dial case where a web!
  server
makes outward INVITEs
to two UAs and connects them. I think people believe this
case *should* be a communications session.
 
- Another case is described in
http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html
and debated in the replies to that. Arguments are made for
different answers to what should get a common session id and what
should not. For this case I think we need to decide:
. do we mandate exactly how this should be treated?
. or do we leave it to the discretion of the B2BUA to decide?
 
Either way we need to decide what the criteria are that lead
to the decision.
 
o! IIRC Hadriel suggested (in a meeting?) that where media
originates and terminates has something to do with this.
That doesn't work all the time (e.g. MESSAGE), but it might help
in some cases. I think he used this to just!
 ify
that:
 
- the Conference Bridge Transcoding Model (RFC5369 section 3.2)
is a single communications session.
 
- the 3PCC Transcoding Model (RFC5369 section 3.1) is *not*
a single communications session.
 
(I'm not convinced - this seems like a distinction without
a difference.)
 
Fundamentally we should be able to classify all cases into:
- those that *should* be communications sessions,
- those that *shouldn't* be communication sessions,
- those we don't care about - could be either way.
 
When we are done, we should be able to apply the definition of
communication session to any case. When applied to the cases we
explicitly care about it should deliver the an! swer we expect.
 
The more weird cases we care about, the more complex and
unintuitive the
criteria will be. I suspect that the path we are on will lead to
complex
criteria. (We can have a really crisp de!
 finition
of communications
session if we don't care much about which cases qualify.)
 
One idea I considered is to define some new terms that build on
normal
sip concepts but extend them to allow B2BUA intermediaries where sip
allows proxies. E.g.
- Transaction++ is either a sip transaction, or a series of sip
transactions linked by B2BUA intermediaries.
 
- Dialog++ is either a sip dialog, or a series of sip dialogs
linked by B2BUA intermediaries.
 
Then would need to define the behavior of a B2BUA intermediary.
It needs
to relay transactions from one "side" to the other, preserving
certain
invariants (TBD). Presumably it can also originate certain
transactions,
but there must be constraints ! on what it can do. There must
also be some
rules on how media is handled across one of these intermediaries.
 
If that was done, then a communication session could be defined as a
Transaction++ for an out-of-dialog request, or a Dialog++.
 
But that makes the definition of communication session the first
priority and the cases that happen to qualify as a communication
session
a consequence. It probably won't match people's intuitive
feelings about
what *should* be a communication session. So it might not
satisfy people.
 
Thanks,
Paul
 
 
On 1/10/13 6:04 PM, Charles Eckel (eckelcu) wrote:
 
>From my point of view, the draft looks good. The
changes incorporated
 
in this updated version directly address this open issue.
 
Cheers,
Charles
 
-----Original Message-----
From: insipid-bounces@ietf.org
[mailto:insipid-bounces@ietf.org] On
Behalf Of Gonzalo Salgueiro (gsalguei)
Sent: Thursday, January 10, 2013 12:39 PM
To: Paul E. Jones
Cc: insipid@ietf.org
Subject: Re: [Insipid] Are we ready to LC on the
requirements?
 
Thanks for submitting this, Paul. The biggest open issue
in regards
to the requirements document was to clearly define what
it is we are
identifying (i.e., "communication session") within the
scope of this
document and ensure that clearly defined language is used
consistently through! out the document. Prior to any
consensus on
moving to WGLC, the chairs would appreciate hearing the
group's
thoughts on where we are on this issue in the current
version.
 
Cheers,
 
Gonzalo & Keith
 
 
 
On Jan 9, 2013, at 9:23 PM, Paul E. Jones wrote:
 
Folks,
 
Dialog has been extremely light on the requirements
document. Do
 
people feel generally OK with it as it is now? Can we
move on to the
solution document now or are there other changes needed
in the
requirements document?
 
I just posted the -04 versi!
 on with
changes proposed
on the list over
the
 
past month or so.
 
Paul
 


  _____  

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


  _____  

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


  _____  

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


  _____  

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


  _____  

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

 
 







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

 

 


------=_NextPart_000_018D_01CE18C5.2D400F80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Robert,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Comments down </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C=
0'>below</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#C0000=
0'>:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> Robert Sparks [mailto:rjsparks@nostrum.com] <br><b>Sent:</b> =
Monday, March 04, 2013 10:11 AM<br><b>To:</b> Paul E. =
Jones<br><b>Cc:</b> insipid@ietf.org; 'Paul Kyzivat'<br><b>Subject:</b> =
Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On =
3/4/13 8:27 AM, Paul E. Jones wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Robert,</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We&#8217;ll try to cover this in the meeting with slides and then =
incorporate in <u>slides</u> subsequently.&nbsp; I have an answer for =
each.&nbsp; That said, please do allow me to provide an answer below =
that we can discuss before then.</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C=
0'>PEJ: meant to say &#8220;document&#8221; =
above.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Paul</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> <a =
href=3D"mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a> =
[<a =
href=3D"mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org<=
/a>] <b>On Behalf Of </b>Robert Sparks<br><b>Sent:</b> Friday, March 01, =
2013 3:18 PM<br><b>To:</b> Paul E. Jones<br><b>Cc:</b> <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a>; Paul =
Kyzivat<br><b>Subject:</b> Re: [Insipid] Are we ready to LC on the =
requirements?</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal>On =
2/24/13 8:38 AM, Paul E. Jones wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>Paul,<br><br>That still begs the question of =
&quot;what language do we need to add or change to make this =
clear?&quot; In my mind, I know exactly what an endpoint needs to do and =
what an SBC needs to do. But, I'll not say it does not need more charity =
for those that do not have it clear in their minds.<br><br>But, perhaps =
being too close to the work, I'm having trouble seeing where it is =
vague. Can you suggest text?<o:p></o:p></p></blockquote><p =
class=3DMsoNormal>This is frustrating, for both of us probably. I've =
read the latest requirement document and it doesn't yet =
clearly<br>answer the questions I asked in the Atlanta meeting. I feel =
like I've asked them at several meetings before.<br>Can we stop that =
cycle of repeating the discussion by putting text in the document that =
directly answers each of these:<br><br>In a scenario where you only have =
one parallel forking SIP proxy, when an INVITE forks to two =
different<br>UAs and _both_ send 200 OKs, do you have one session or =
two? (This same question applies to early dialogs,<br>with or without =
early media, which is a _normal_ condition, not an race condition like =
multiple 200 OKs).<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>PEJ: That would be two communication sessions, one between Alice to =
Bob-1 and one between Alice and Bob-2.&nbsp; This is precisely why we =
use the approach in our proposed solution.&nbsp; The Session-ID is =
always comprised of the UUID values from each &#8220;endpoint&#8221; =
(which would include MCUs, PSTN GWs, or 3PCC session =
initiators).</span><o:p></o:p></p><p class=3DMsoNormal><br>If you =
replace that with a _serial_ forking proxy, where you were in an early =
dialog with UA1, that got canceled<br>and then you ended up in an early =
dialog, and then a confirmed dialog with UA2, was that one session (with =
the<br>calling UA, UA1, and UA2 involved) or two sessions (one with the =
calling UA and UA1, the other with the calling<br>UA and =
UA2)?<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>PEJ: That would be two communication sessions.&nbsp; Any time there is =
a different UA on one end, that represents a distinct communication =
session.</span><o:p></o:p></p><p class=3DMsoNormal><br>If you replace =
that with a B2BUA that behaves similar to a serial forking proxy in that =
it only alerts one called thing<br>at a time, do you end up with one =
session or with two.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>PEJ: This is similar to the case where a fork is cancelled.&nbsp; Alice =
is only in one communication session and the SBC has to pick a UUID to =
return.&nbsp; However, the UUID can change if the other device actually =
answers.&nbsp; For that matter, the SBC could even fabricate a temporary =
value, knowing there is a 50/50 change it will change, anyway.&nbsp; =
What&#8217;s important is the end result: the &#8220;stable =
call&#8221;.&nbsp; Once the call is connected, there are just two =
devices, Alice and some Bob.&nbsp; And, if the Bob changes during call =
establishment, the UUID value will change on that end.&nbsp; =
That&#8217;s perfectly fine.</span><o:p></o:p></p></div></blockquote><p =
class=3DMsoNormal>I had to read this several times to make sure, but I =
think the end result is that you said &quot;two&quot; (or perhaps even =
three) here, but if you were looking at whole set of messages between =
the three UAs involved, you would never try to identify them all with a =
single session identifier. Did I hear you correctly?<br><br><span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C=
0'>PEJ: Alice sends an INVITE and gets back a single 180, even if the =
B2BUA gets 10 180s, right?&nbsp; In that case, there are 10 Bobs ringing =
and there would be 10 communication sessions {Alice, Bob-1}, {Alice, =
Bob-2}, &#8230;.&nbsp; However, only the SBC sees those.&nbsp; =
That&#8217;s because the SBC is not forwarding all messages to =
Alice.&nbsp; The SBC is going to forward <i>something</i> to =
Alice.&nbsp; Would this be Bob-1 or some UUID fabricated by the SBC? =
&nbsp;Does not really matter, since the remote end is allowed to change. =
&nbsp;So, the SBC could send a UUID such that Alice has {Alice, SBC}, =
but then when Bob-5 sends a 200, Alice updates her Session-ID to be { =
Alice, Bob-5 }.&nbsp; Because session establishment works like this, we =
need something that is flexible enough to accommodate.&nbsp; =
That&#8217;s the reason we propose to use two UUIID values. &nbsp;Each =
UUID identifies a particular physical or logical endpoint in a =
session.&nbsp; The set of two UUIDs define the communication session =
comprised of those two endpoints.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C=
0'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C=
0'>Paul<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>Paul</span><o:p></o:p></p><p class=3DMsoNormal><br>I don't see how the =
current document answers those questions. If I've missed that, please =
point to it and I'll see how<br>I can help make them more =
obvious.<br><br>Otherwise, can you please make the answers clear in the =
document, (not just in an email response).<br><br><br><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>Paul<o:p></o:p></p><div><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><hr =
size=3D2 width=3D"100%" align=3Dcenter></span></div><p =
class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Paul Kyzivat <a =
href=3D"mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a><b=
r><b>Sent:</b> Sun Feb 24 01:43:57 EST 2013<br><b>To:</b> &quot;Paul E. =
Jones&quot; <a =
href=3D"mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a><b=
r><b>Cc:</b> <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><br><b>Subject:</b> =
Re: [Insipid] Are we ready to LC on the =
requirements?</span><o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><br><o:p></o:p></p><pre>On 2/24/13 12:33 AM, =
Paul E. Jones wrote:<o:p></o:p></pre><blockquote =
style=3D'border:none;border-left:solid #729FCF 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:6=
.0pt'><pre>Paul,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>So =
what concept is =
vague?<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>In terms of an =
H.323 device, I would consider two terminals with =
users<o:p></o:p></pre><pre>at each end to be a communication session. I =
would consider a terminal<o:p></o:p></pre><pre>and an MCU to have a =
communication =
session.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>The collection =
of communication sessions on an MCU to which one or =
more<o:p></o:p></pre><pre>terrminals are a party is a conference. And I =
would like to relate all<o:p></o:p></pre><pre>those sessions by the UUID =
the MCU uses in each of those sessions. That<o:p></o:p></pre><pre>value =
could even be the Conference ID in =
H.323.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>There are =
gateway devices that connect to the PSTN that I would count =
as<o:p></o:p></pre><pre>equal to a terminal. But, there are gateway =
devices that bridge IP<o:p></o:p></pre><pre>networks (SBCs) that =
shoul!<o:p></o:p></pre><pre> d just<o:p></o:p></pre><pre>pass the UUIDs =
through. The difference<o:p></o:p></pre><pre>between the two really is =
whether it bridges an IPMC device to another<o:p></o:p></pre><pre>or to =
something else.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>There =
are call flows like the one you highlighted in the threads =
where<o:p></o:p></pre><pre>voice comes from one terminal and video from =
another. That's an MCU,<o:p></o:p></pre><pre>really. The session ID =
exists between Alice and MCU (or PBX). The =
other<o:p></o:p></pre><pre>devices Bob uses might share the UUID of the =
MCU/PBX, but those are<o:p></o:p></pre><pre>distinct communication =
sessions like the typical MCU case. Yeah, =
such<o:p></o:p></pre><pre>topologies do make it hard to do debugging and =
the number of UUIDs makes<o:p></o:p></pre><pre>it a pain, too, but at =
least there is consistency in the assignments.<o:p></o:p></pre><pre>So, =
it is doable.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>So, how =
can we make progress =
here?<o:p></o:p></pre></blockquote><pre>&nbsp;<o:p></o:p></pre><pre>We =
write some rules that any device that terminates more than one dialog =
<o:p></o:p></pre><pre>can use to decide when one dialog should share a =
session-id with another <o:p></o:p></pre><pre>dialog. The rules should =
get the &quot;right&quot; answer for all the use =
case!<o:p></o:p></pre><pre> s, <o:p></o:p></pre><pre>and should be =
specific enough so that when applied to any device, no =
<o:p></o:p></pre><pre>matter how weird, most reasonable people would =
agree with the answer. <o:p></o:p></pre><pre>That way we can have a way =
of judging conformance to this =
specification.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I =
realize this bridges the gap between what the requirements are =
<o:p></o:p></pre><pre>responsible for and what the mechanism is =
responsible for. But the <o:p></o:p></pre><pre>mechanism is about =
marking communications sessions, not defining =
them.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>OR I suppose the =
requirements could kick the can down the road, simply =
<o:p></o:p></pre><pre>say that the mechanism must work for the specified =
use cases and itself <o:p></o:p></pre><pre>must specify the algorithm =
for making the decision in other cases. But <o:p></o:p></pre><pre>that =
just puts it off.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre> =
Thanks,<o:p></o:p></pre><pre> Paul =
K<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><blockquote =
style=3D'border:none;border-left:solid #729FCF 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:6=
.0pt'><pre>Paul<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o=
:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre =
style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre>&nbsp;<o:p></o:p></pre><pre>*From:* Paul =
Kyzivat <a =
href=3D"mailto:pkyzivat@alum.mit.edu">&lt;pkyzivat@alum.mit.edu&gt;</a><o=
:p></o:p></pre><pre>*Sent:* Sat F!<o:p></o:p></pre><pre> eb =
23<o:p></o:p></pre><pre>19:58:41 EST 2013<o:p></o:p></pre><pre>*To:* =
&quot;Paul E. Jones&quot; <a =
href=3D"mailto:paulej@packetizer.com">&lt;paulej@packetizer.com&gt;</a><o=
:p></o:p></pre><pre>*Cc:* <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e>*Subject:* Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>On =
2/21/13 9:51 PM, Paul E. Jones =
wrote:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Paul,<o:p></o:p><=
/pre><pre>&nbsp;<o:p></o:p></pre><pre>I read your message, but was left =
unsure of exactly how we could<o:p></o:p></pre><pre>improve =
the<o:p></o:p></pre><pre>definition over what we have =
already.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>If there is =
something concrete that you can propose that would =
help<o:p></o:p></pre><pre>lend to<o:p></o:p></pre><pre>clarity of the =
text, I'm definitely willing to put it in. I =
would<o:p></o:p></pre><pre>like to<o:p></o:p></pre><pre>move the =
requirements along and the submission deadline is =
Monday.<o:p></o:p></pre><pre>Do you<o:p></o:p></pre><pre>have text you =
would like to add before the =
deadline?<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o=
:p></pre><pre>I'm traveling on business and have limited internet =
access, and limited<o:p></o:p></pre><pre>time, so I probably =
can't.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>In any case, =
ISTM that the problem isn't that we don't have the =
right<o:p></o:p></pre><pre>words. Rather, we still don't have clear =
*concepts* that =
distinguish<o:p></o:p></pre><pre>!<o:p></o:p></pre><pre>whatshould be =
covered from what should not. We have some use cases, =
but<o:p></o:p></pre><pre>lack basic principles that can be applied to =
any case to determine if it<o:p></o:p></pre><pre>should be a =
communication session or not. It still seems to be more =
in<o:p></o:p></pre><pre>the realm of &quot;I know one when I see =
it.&quot;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>If we had the =
principles, then it would probably be straightforward =
to<o:p></o:p></pre><pre>come up with =
words.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I don't yet see =
a suitable general principle here that fits the =
use<o:p></o:p></pre><pre>cases and seems to make =
sense.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Thanks,<o:p></o:p=
></pre><pre>Paul<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Paul<o:=
p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: <a =
href=3D"mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a> =
[<a =
href=3D"mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org<=
/a>] On<o:p></o:p></pre><pre>Behalf Of Paul =
Kyzivat<o:p></o:p></pre><pre>Sent: Friday, January 11, 2013 3:34 =
PM<o:p></o:p></pre><pre>To: <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e>Subject: Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>(Sorry =
that this is long. I don't know how to make it =
short.)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Are we ready to =
LC? I don't think so. Specifically I don't think<o:p></o:p></pre><pre>we =
yet<o:p></o:p></pre><pre>have an<o:p></o:p></pre><pre>unambiguous =
definition of what is being =
identified.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>This =
version added some new =
text:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>In this document, =
the word &quot;session&quot; refers to a =
&quot;communication<o:p></o:p></pre><pre>session&quot; that may exist =
between two SIP user agents and that =
may<o:p></o:p></pre><pre>pass<o:p></o:p></pre><pre>through one or more =
intermediary devices, including B2BUAs or =
SIP<o:p></o:p></pre><pre>proxies. A communication session consists of =
one of more SIP<o:p></o:p></pre><pre>transactions. A very simple =
communication session may be a single<o:p></o:p></pre><pre>out-of-dialog =
SIP transaction (e.g., MESSAGE/200). In the case of =
a<o:p></o:p></pre><pre>SIP dialog, the SIP message exchange includes a =
dialog creating<o:p></o:p></pre><pre>INVITE transaction, and zero of =
more subsequent SIP transactions<o:p></o:p></pre><pre>within the same =
dialog (e.g., ACK, re-INVITE, BYE). Due to =
the<o:p></o:p></pre><pre>existenc! e of middle boxes, there may be =
multiple related SIP<o:p></o:p></pre><pre>transactions or dialogs =
chained together along the path from one end<o:p></o:p></pre><pre>of the =
communication session to the other. For =
example:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>A Middlebox =
B<o:p></o:p></pre><pre>SIP =
trans1<o:p></o:p></pre><pre>-----------------&gt; SIP trans =
2<o:p></o:p></pre><pre>SIP dialog 1 &lt;-------------- SIP dialog =
2<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Figure 1 - =
Communication Session through a =
Middlebox<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>In such =
cases, the two SIP transactions or dialogs are part of =
a<o:p></o:p></pre><pre>single communication =
session.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>The term =
&quot;end-to-end&quot; in this document means the =
communication<o:p></o:p></pre><pre>session from the point of origin, =
passing through any number of<o:p></o:p></pre><pre>intermediaries, to =
the ultimate point of termination. It is<o:p></o:p></pre><pre>recognized =
that legacy devices may not support the =
&quot;end-to-end&quot;<o:p></o:p></pre><pre>session identifier, though =
an identifier might be created by an<o:p></o:p></pre><pre>intermediary =
when it is absent from the session =
signaling.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>IMO this is =
a big improvement. But it still isn't as prec! =
ise<o:p></o:p></pre><pre>as I would<o:p></o:p></pre><pre>like. What I =
find lacking in the above =
is:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>o parsing the =
above, the properties of a communication session =
are:<o:p></o:p></pre><pre>- connects *two* UAs<o:p></o:p></pre><pre>- =
optionally includes one or more intermediary =
devices<o:p></o:p></pre><pre>- one or =
more<o:p></o:p></pre><pre>transactions<o:p></o:p></pre><pre>- one =
out-of-dialog transaction,<o:p></o:p></pre><pre>OR a dialog including =
the dialog establishing transaction<o:p></o:p></pre><pre>and some =
transactions within the dialog.<o:p></o:p></pre><pre>- middle boxes may =
result in chaining dialogs or =
transactions.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Exactly =
how all these properties &quot;plug together&quot; =
fuzzy.<o:p></o:p></pre><pre>I'm not at all certain that all readers =
would reach<o:p></o:p></pre><pre>the same conclusion about which cases =
meet these criteria<o:p></o:p></pre><pre>and which =
don't.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>o I'm also not =
certain that these criteria match all the =
cases<o:p></o:p></pre><pre>people expect, and exclude all the cases =
people think should<o:p></o:p></pre><pre>be =
excluded.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>- I think =
people expect that a conference is *not* a =
single<o:p></o:p></pre><pre>communications session. But a conference =
with only two<o:p></o:p></pre><pre>participants would! seem to qualify =
according to all of the<o:p></o:p></pre><pre>above criteria. So that =
suggests that another criterion is<o:p></o:p></pre><pre>needed to =
exclude that case.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>- A =
topologically similar case to the conference is =
a<o:p></o:p></pre><pre>click-to-dial case where a =
web!<o:p></o:p></pre><pre>&nbsp; server<o:p></o:p></pre><pre>makes =
outward INVITEs<o:p></o:p></pre><pre>to two UAs and connects them. I =
think people believe this<o:p></o:p></pre><pre>case *should* be a =
communications =
session.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>- Another case =
is described in<o:p></o:p></pre><pre><a =
href=3D"http://www.ietf.org/mail-archive/web/insipid/current/msg00429.htm=
l">http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html</a>=
<o:p></o:p></pre><pre>and debated in the replies to that. Arguments are =
made for<o:p></o:p></pre><pre>different answers to what should get a =
common session id and what<o:p></o:p></pre><pre>should not. For this =
case I think we need to decide:<o:p></o:p></pre><pre>. do we mandate =
exactly how this should be treated?<o:p></o:p></pre><pre>. or do we =
leave it to the discretion of the B2BUA to =
decide?<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Either way we =
need to decide what the criteria are that lead<o:p></o:p></pre><pre>to =
the decision.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>o! IIRC =
Hadriel suggested (in a meeting?) that where =
media<o:p></o:p></pre><pre>originates and terminates has something to do =
with this.<o:p></o:p></pre><pre>That doesn't work all the time (e.g. =
MESSAGE), but it might help<o:p></o:p></pre><pre>in some cases. I think =
he used this to just!<o:p></o:p></pre><pre> =
ify<o:p></o:p></pre><pre>that:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pr=
e><pre>- the Conference Bridge Transcoding Model (RFC5369 section =
3.2)<o:p></o:p></pre><pre>is a single communications =
session.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>- the 3PCC =
Transcoding Model (RFC5369 section 3.1) is *not*<o:p></o:p></pre><pre>a =
single communications =
session.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>(I'm not =
convinced - this seems like a distinction without<o:p></o:p></pre><pre>a =
difference.)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Fundamental=
ly we should be able to classify all cases into:<o:p></o:p></pre><pre>- =
those that *should* be communications sessions,<o:p></o:p></pre><pre>- =
those that *shouldn't* be communication sessions,<o:p></o:p></pre><pre>- =
those we don't care about - could be either =
way.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>When we are done, =
we should be able to apply the definition =
of<o:p></o:p></pre><pre>communication session to any case. When applied =
to the cases we<o:p></o:p></pre><pre>explicitly care about it should =
deliver the an! swer we =
expect.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>The more weird =
cases we care about, the more complex =
and<o:p></o:p></pre><pre>unintuitive the<o:p></o:p></pre><pre>criteria =
will be. I suspect that the path we are on will lead =
to<o:p></o:p></pre><pre>complex<o:p></o:p></pre><pre>criteria. (We can =
have a really crisp de!<o:p></o:p></pre><pre> =
finition<o:p></o:p></pre><pre>of =
communications<o:p></o:p></pre><pre>session if we don't care much about =
which cases =
qualify.)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>One idea I =
considered is to define some new terms that build =
on<o:p></o:p></pre><pre>normal<o:p></o:p></pre><pre>sip concepts but =
extend them to allow B2BUA intermediaries where =
sip<o:p></o:p></pre><pre>allows proxies. E.g.<o:p></o:p></pre><pre>- =
Transaction++ is either a sip transaction, or a series of =
sip<o:p></o:p></pre><pre>transactions linked by B2BUA =
intermediaries.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>- =
Dialog++ is either a sip dialog, or a series of sip =
dialogs<o:p></o:p></pre><pre>linked by B2BUA =
intermediaries.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Then =
would need to define the behavior of a B2BUA =
intermediary.<o:p></o:p></pre><pre>It needs<o:p></o:p></pre><pre>to =
relay transactions from one &quot;side&quot; to the other, =
preserving<o:p></o:p></pre><pre>certain<o:p></o:p></pre><pre>invariants =
(TBD). Presumably it can also originate =
certain<o:p></o:p></pre><pre>transactions,<o:p></o:p></pre><pre>but =
there must be constraints ! on what it can do. There =
must<o:p></o:p></pre><pre>also be some<o:p></o:p></pre><pre>rules on how =
media is handled across one of these =
intermediaries.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>If that =
was done, then a communication session could be defined as =
a<o:p></o:p></pre><pre>Transaction++ for an out-of-dialog request, or a =
Dialog++.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>But that =
makes the definition of communication session the =
first<o:p></o:p></pre><pre>priority and the cases that happen to qualify =
as a communication<o:p></o:p></pre><pre>session<o:p></o:p></pre><pre>a =
consequence. It probably won't match people's =
intuitive<o:p></o:p></pre><pre>feelings about<o:p></o:p></pre><pre>what =
*should* be a communication session. So it might =
not<o:p></o:p></pre><pre>satisfy =
people.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Thanks,<o:p></o:=
p></pre><pre>Paul<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;=
<o:p></o:p></pre><pre>On 1/10/13 6:04 PM, Charles Eckel (eckelcu) =
wrote:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>From my point of =
view, the draft looks good. The<o:p></o:p></pre><pre>changes =
incorporated<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>in this =
updated version directly address this open =
issue.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Cheers,<o:p></o:p=
></pre><pre>Charles<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>----=
-Original Message-----<o:p></o:p></pre><pre>From: <a =
href=3D"mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a><o:p=
></o:p></pre><pre>[<a =
href=3D"mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org<=
/a>] On<o:p></o:p></pre><pre>Behalf Of Gonzalo Salgueiro =
(gsalguei)<o:p></o:p></pre><pre>Sent: Thursday, January 10, 2013 12:39 =
PM<o:p></o:p></pre><pre>To: Paul E. Jones<o:p></o:p></pre><pre>Cc: <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e>Subject: Re: [Insipid] Are we ready to LC on =
the<o:p></o:p></pre><pre>requirements?<o:p></o:p></pre><pre>&nbsp;<o:p></=
o:p></pre><pre>Thanks for submitting this, Paul. The biggest open =
issue<o:p></o:p></pre><pre>in regards<o:p></o:p></pre><pre>to the =
requirements document was to clearly define what<o:p></o:p></pre><pre>it =
is we are<o:p></o:p></pre><pre>identifying (i.e., &quot;communication =
session&quot;) within the<o:p></o:p></pre><pre>scope of =
this<o:p></o:p></pre><pre>document and ensure that clearly defined =
language is used<o:p></o:p></pre><pre>consistently through! out the =
document. Prior to any<o:p></o:p></pre><pre>consensus =
on<o:p></o:p></pre><pre>moving to WGLC, the chairs would appreciate =
hearing the<o:p></o:p></pre><pre>group's<o:p></o:p></pre><pre>thoughts =
on where we are on this issue in the =
current<o:p></o:p></pre><pre>version.<o:p></o:p></pre><pre>&nbsp;<o:p></o=
:p></pre><pre>Cheers,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Go=
nzalo &amp; =
Keith<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p><=
/pre><pre>&nbsp;<o:p></o:p></pre><pre>On Jan 9, 2013, at 9:23 PM, Paul =
E. Jones =
wrote:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Folks,<o:p></o:p>=
</pre><pre>&nbsp;<o:p></o:p></pre><pre>Dialog has been extremely light =
on the requirements<o:p></o:p></pre><pre>document. =
Do<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>people feel =
generally OK with it as it is now? Can we<o:p></o:p></pre><pre>move on =
to the<o:p></o:p></pre><pre>solution document now or are there other =
changes needed<o:p></o:p></pre><pre>in =
the<o:p></o:p></pre><pre>requirements =
document?<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I just posted =
the -04 versi!<o:p></o:p></pre><pre> on =
with<o:p></o:p></pre><pre>changes proposed<o:p></o:p></pre><pre>on the =
list =
over<o:p></o:p></pre><pre>the<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre=
><pre>past month or =
so.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Paul<o:p></o:p></pre=
><pre>&nbsp;<o:p></o:p></pre><pre style=3D'text-align:center'><hr =
size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></p=
re><pre>&nbsp;<o:p></o:p></pre><pre style=3D'text-align:center'><hr =
size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></p=
re><pre style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></p=
re><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre =
style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></p=
re><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:=
p></o:p></pre><pre style=3D'text-align:center'><hr size=3D2 =
width=3D"100%" =
align=3Dcenter></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></=
pre><pre>insipid mailing list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre></blockquote><pre>&nbsp;<=
o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><p =
class=3DMsoNormal><br><br><br><br><o:p></o:p></p><pre>___________________=
____________________________<o:p></o:p></pre><pre>insipid mailing =
list<o:p></o:p></pre><pre><a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><o:p></o:p></pre><pr=
e><a =
href=3D"https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.o=
rg/mailman/listinfo/insipid</a><o:p></o:p></pre><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_018D_01CE18C5.2D400F80--


From rjsparks@nostrum.com  Mon Mar  4 08:07:26 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2BE21F8A3D for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 08:07:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7zNt18detgl for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 08:07:24 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 944A221F8CA1 for <insipid@ietf.org>; Mon,  4 Mar 2013 08:07:23 -0800 (PST)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r24G7MZG055064 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 4 Mar 2013 10:07:22 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <5134C6B9.70508@nostrum.com>
Date: Mon, 04 Mar 2013 10:07:21 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>
References: <055801cdeed9$8b441060$a1cc3120$@packetizer.com>	<5F864ABC-E17F-44C9-8CDE-D6C5A32BF214@cisco.com>	<92B7E61ADAC1BB4F941F943788C0882804728936@xmb-aln-x08.cisco.com>	<50F07742.3030601@alum.mit.edu>	<0a0e01ce10a7$875a0690$960e13b0$@packetizer.com>	<512965C1.2090204@alum.mit.edu>	<55fa36b1-465e-40e0-b875-90fb48f3fc13@email.android.com>	<5129B6AD.6010306@alum.mit.edu>	<fab2d64c-7f69-4575-a372-15d78237e667@email.android.com> <51310CEC.1070907@nostrum.com> <013401ce18e4$7061a2a0$5124e7e0$@packetizer.com> <5134B967.2010509@nostrum.com> <018c01ce18ef$1611aab0$42350010$@packetizer.com>
In-Reply-To: <018c01ce18ef$1611aab0$42350010$@packetizer.com>
Content-Type: multipart/alternative; boundary="------------090207030307040600040008"
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: insipid@ietf.org, 'Paul Kyzivat' <pkyzivat@alum.mit.edu>
Subject: Re: [Insipid] Are we ready to LC on the requirements?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 16:07:26 -0000

This is a multi-part message in MIME format.
--------------090207030307040600040008
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Trimming a bit.

On 3/4/13 9:43 AM, Paul E. Jones wrote:
> *From:* Robert Sparks [mailto:rjsparks@nostrum.com]
>
> On 3/4/13 8:27 AM, Paul E. Jones wrote:
>
>     If you replace that with a B2BUA that behaves similar to a serial
>     forking proxy in that it only alerts one called thing
>
>     at a time, do you end up with one session or with two.
>
>     PEJ: This is similar to the case where a fork is cancelled.  Alice
>     is only in one communication session and the SBC has to pick a
>     UUID to return.  However, the UUID can change if the other device
>     actually answers.  For that matter, the SBC could even fabricate a
>     temporary value, knowing there is a 50/50 change it will change,
>     anyway.  What's important is the end result: the "stable call". 
>     Once the call is connected, there are just two devices, Alice and
>     some Bob.  And, if the Bob changes during call establishment, the
>     UUID value will change on that end.  That's perfectly fine.
>
> I had to read this several times to make sure, but I think the end 
> result is that you said "two" (or perhaps even three) here, but if you 
> were looking at whole set of messages between the three UAs involved, 
> you would never try to identify them all with a single session 
> identifier. Did I hear you correctly?
>
> PEJ: Alice sends an INVITE and gets back a single 180, even if the 
> B2BUA gets 10 180s, right?  In that case, there are 10 Bobs ringing 
> and there would be 10 communication sessions {Alice, Bob-1}, {Alice, 
> Bob-2}, ....  However, only the SBC sees those.  That's because the 
> SBC is not forwarding all messages to Alice.  The SBC is going to 
> forward /something/ to Alice.  Would this be Bob-1 or some UUID 
> fabricated by the SBC?  Does not really matter, since the remote end 
> is allowed to change.  So, the SBC could send a UUID such that Alice 
> has {Alice, SBC}, but then when Bob-5 sends a 200, Alice updates her 
> Session-ID to be { Alice, Bob-5 }. Because session establishment works 
> like this, we need something that is flexible enough to accommodate.  
> That's the reason we propose to use two UUIID values.  Each UUID 
> identifies a particular physical or logical endpoint in a session.  
> The set of two UUIDs define the communication session comprised of 
> those two endpoints.
>
>
You probably aren't doing this on purpose, but it feels like you are 
trying to avoid answering my direct questions.

I would be a lot more comfortable that we're not talking past each other 
if you had said clearly "yes" or "no" above
(and then launched into an explanation if you needed to). I think you 
said "yes", and then explained more about
why "perhaps even three" might be the case. Would you confirm that?

And specifically, you agree that "If you were looking at the whole set 
of messages between the three UAs involved, you would never try to 
identify them all with a single session identifier."?

If you aren't comfortable just saying yes to both of those things, we 
need to discuss more about why. If you are, then we can move on to the 
next step of working that into a description of what this identifier is 
identifying.

RjS



--------------090207030307040600040008
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Trimming a bit.<br>
      <br>
      On 3/4/13 9:43 AM, Paul E. Jones wrote:<br>
    </div>
    <blockquote
      cite="mid:018c01ce18ef$1611aab0$42350010$@packetizer.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b>
        Robert Sparks [<a class="moz-txt-link-freetext" href="mailto:rjsparks@nostrum.com">mailto:rjsparks@nostrum.com</a>] <br>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoNormal">On 3/4/13 8:27 AM, Paul E. Jones wrote:<o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">If
            you replace that with a B2BUA that behaves similar to a
            serial forking proxy in that it only alerts one called thing<br>
            <div style="border:none;border-left:solid blue
              1.5pt;padding:0in 0in 0in 4.0pt">
              <p class="MsoNormal">at a time, do you end up with one
                session or with two.<o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:green">PEJ:
                  This is similar to the case where a fork is
                  cancelled.&nbsp; Alice is only in one communication session
                  and the SBC has to pick a UUID to return.&nbsp; However,
                  the UUID can change if the other device actually
                  answers.&nbsp; For that matter, the SBC could even
                  fabricate a temporary value, knowing there is a 50/50
                  change it will change, anyway.&nbsp; What&#8217;s important is
                  the end result: the &#8220;stable call&#8221;.&nbsp; Once the call is
                  connected, there are just two devices, Alice and some
                  Bob.&nbsp; And, if the Bob changes during call
                  establishment, the UUID value will change on that
                  end.&nbsp; That&#8217;s perfectly fine.</span><o:p></o:p></p>
            </div>
          </blockquote>
          <p class="MsoNormal">I had to read this several times to make
            sure, but I think the end result is that you said "two" (or
            perhaps even three) here, but if you were looking at whole
            set of messages between the three UAs involved, you would
            never try to identify them all with a single session
            identifier. Did I hear you correctly?<br>
            <br>
            <span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#0070C0">PEJ:
              Alice sends an INVITE and gets back a single 180, even if
              the B2BUA gets 10 180s, right?&nbsp; In that case, there are 10
              Bobs ringing and there would be 10 communication sessions
              {Alice, Bob-1}, {Alice, Bob-2}, &#8230;.&nbsp; However, only the SBC
              sees those.&nbsp; That&#8217;s because the SBC is not forwarding all
              messages to Alice.&nbsp; The SBC is going to forward <i>something</i>
              to Alice.&nbsp; Would this be Bob-1 or some UUID fabricated by
              the SBC? &nbsp;Does not really matter, since the remote end is
              allowed to change. &nbsp;So, the SBC could send a UUID such
              that Alice has {Alice, SBC}, but then when Bob-5 sends a
              200, Alice updates her Session-ID to be { Alice, Bob-5 }.&nbsp;
              Because session establishment works like this, we need
              something that is flexible enough to accommodate.&nbsp; That&#8217;s
              the reason we propose to use two UUIID values. &nbsp;Each UUID
              identifies a particular physical or logical endpoint in a
              session.&nbsp; The set of two UUIDs define the communication
              session comprised of those two endpoints.<o:p></o:p></span></p>
          <br>
        </div>
      </div>
    </blockquote>
    You probably aren't doing this on purpose, but it feels like you are
    trying to avoid answering my direct questions.<br>
    <br>
    I would be a lot more comfortable that we're not talking past each
    other if you had said clearly "yes" or "no" above <br>
    (and then launched into an explanation if you needed to). I think
    you said "yes", and then explained more about <br>
    why "perhaps even three" might be the case. Would you confirm that?<br>
    <br>
    And specifically, you agree that "If you were looking at the whole
    set of messages between the three UAs involved, you would never try
    to identify them all with a single session identifier."?<br>
    <br>
    If you aren't comfortable just saying yes to both of those things,
    we need to discuss more about why. If you are, then we can move on
    to the next step of working that into a description of what this
    identifier is identifying.<br>
    <br>
    RjS<br>
    <br>
    <br>
  </body>
</html>

--------------090207030307040600040008--

From paulej@packetizer.com  Mon Mar  4 08:38:00 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 438F621F8CA6 for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 08:38:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLlzkiecH-4F for <insipid@ietfa.amsl.com>; Mon,  4 Mar 2013 08:37:56 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id DD23821F8C82 for <insipid@ietf.org>; Mon,  4 Mar 2013 08:37:55 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r24GbsVP007309 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 4 Mar 2013 11:37:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362415074; bh=K3dyuDU7hlk4sGANfjZHJYlDDscb8Ji2XIzgb2aeWio=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=K0cpw8o1iLitf1Gmqsalh8R9CYhpVJCOr0WLqLp5Y9L5hmCE5FZY7DZzcW132ZLoS SGdSwB2+g/jtu3M3jcw8DNybWVE2YRmNcc5oNehwRzVCkOeb80fLoaEGmnTtTJ7+40 QP0pCA8kd1u1VWc99bc10Is/53mWQxlqNhr5keCU=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Robert Sparks'" <rjsparks@nostrum.com>
References: <055801cdeed9$8b441060$a1cc3120$@packetizer.com>	<5F864ABC-E17F-44C9-8CDE-D6C5A32BF214@cisco.com>	<92B7E61ADAC1BB4F941F943788C0882804728936@xmb-aln-x08.cisco.com>	<50F07742.3030601@alum.mit.edu>	<0a0e01ce10a7$875a0690$960e13b0$@packetizer.com>	<512965C1.2090204@alum.mit.edu>	<55fa36b1-465e-40e0-b875-90fb48f3fc13@email.android.com>	<5129B6AD.6010306@alum.mit.edu>	<fab2d64c-7f69-4575-a372-15d78237e667@email.android.com> <51310CEC.1070907@nostrum.com> <013401ce18e4$7061a2a0$5124e7e0$@packetizer.com> <5134B967.2010509@nostrum.com> <018c01ce18ef$1611aab0$42350010$@packetizer.com> <5134C6B9.70508@nostrum.com>
In-Reply-To: <5134C6B9.70508@nostrum.com>
Date: Mon, 4 Mar 2013 11:38:06 -0500
Message-ID: <01bc01ce18f6$a65569c0$f3003d40$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BD_01CE18CC.BD804C20"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHTUbyWWA5m3crBY/au5zDaSqMbPQHgf0hnAhmddX0CpBjqowIxbGDRAeh2nkEBtHmmmAGjQg/hAfb7tOQDFd7KkQKK0rjmAvtw0qEBL9ZzIwF/GV5xl7C3NtA=
Content-Language: en-us
Cc: insipid@ietf.org, 'Paul Kyzivat' <pkyzivat@alum.mit.edu>
Subject: Re: [Insipid] Are we ready to LC on the requirements?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 16:38:00 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01BD_01CE18CC.BD804C20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Robert,

 

Comments below:

 

From: Robert Sparks [mailto:rjsparks@nostrum.com] 
Sent: Monday, March 04, 2013 11:07 AM
To: Paul E. Jones
Cc: insipid@ietf.org; 'Paul Kyzivat'
Subject: Re: [Insipid] Are we ready to LC on the requirements?

 

Trimming a bit.

On 3/4/13 9:43 AM, Paul E. Jones wrote:

From: Robert Sparks [mailto:rjsparks@nostrum.com] 

On 3/4/13 8:27 AM, Paul E. Jones wrote:

If you replace that with a B2BUA that behaves similar to a serial forking
proxy in that it only alerts one called thing

at a time, do you end up with one session or with two.

 

PEJ: This is similar to the case where a fork is cancelled.  Alice is only
in one communication session and the SBC has to pick a UUID to return.
However, the UUID can change if the other device actually answers.  For that
matter, the SBC could even fabricate a temporary value, knowing there is a
50/50 change it will change, anyway.  What's important is the end result:
the "stable call".  Once the call is connected, there are just two devices,
Alice and some Bob.  And, if the Bob changes during call establishment, the
UUID value will change on that end.  That's perfectly fine.

I had to read this several times to make sure, but I think the end result is
that you said "two" (or perhaps even three) here, but if you were looking at
whole set of messages between the three UAs involved, you would never try to
identify them all with a single session identifier. Did I hear you
correctly?




PEJ: Alice sends an INVITE and gets back a single 180, even if the B2BUA
gets 10 180s, right?  In that case, there are 10 Bobs ringing and there
would be 10 communication sessions {Alice, Bob-1}, {Alice, Bob-2}, ..
However, only the SBC sees those.  That's because the SBC is not forwarding
all messages to Alice.  The SBC is going to forward something to Alice.
Would this be Bob-1 or some UUID fabricated by the SBC?  Does not really
matter, since the remote end is allowed to change.  So, the SBC could send a
UUID such that Alice has {Alice, SBC}, but then when Bob-5 sends a 200,
Alice updates her Session-ID to be { Alice, Bob-5 }.  Because session
establishment works like this, we need something that is flexible enough to
accommodate.  That's the reason we propose to use two UUIID values.  Each
UUID identifies a particular physical or logical endpoint in a session.  The
set of two UUIDs define the communication session comprised of those two
endpoints.

 

You probably aren't doing this on purpose, but it feels like you are trying
to avoid answering my direct questions.

I would be a lot more comfortable that we're not talking past each other if
you had said clearly "yes" or "no" above 
(and then launched into an explanation if you needed to). I think you said
"yes", and then explained more about 
why "perhaps even three" might be the case. Would you confirm that?

PEJ: Yes :-) I apologize for adding more text, but I got the impression you
were still unsure and I'm willing to explain all day.

And specifically, you agree that "If you were looking at the whole set of
messages between the three UAs involved, you would never try to identify
them all with a single session identifier."?

PEJ: Correct.  (Optional-to-read elaboration: Alice would use the same UUID
between her and the two Bobs.  However, each Bob would use a distinct UUID
and therefore the Session-IDs would be different between Alice and Bob-1 as
compared to Alice and Bob-2.)

Paul

If you aren't comfortable just saying yes to both of those things, we need
to discuss more about why. If you are, then we can move on to the next step
of working that into a description of what this identifier is identifying.

RjS




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Robert,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Comments </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#4F622=
8;mso-style-textfill-fill-color:#4F6228;mso-style-textfill-fill-alpha:100=
.0%'><span style=3D'color:windowtext'>below</span></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> Robert Sparks [mailto:rjsparks@nostrum.com] <br><b>Sent:</b> =
Monday, March 04, 2013 11:07 AM<br><b>To:</b> Paul E. =
Jones<br><b>Cc:</b> insipid@ietf.org; 'Paul Kyzivat'<br><b>Subject:</b> =
Re: [Insipid] Are we ready to LC on the =
requirements?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Trimming a bit.<br><br>On 3/4/13 9:43 AM, Paul E. =
Jones wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b> Robert Sparks [<a =
href=3D"mailto:rjsparks@nostrum.com">mailto:rjsparks@nostrum.com</a>] =
<o:p></o:p></p><div style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt'><p class=3DMsoNormal>On 3/4/13 8:27 AM, =
Paul E. Jones wrote:<o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>If =
you replace that with a B2BUA that behaves similar to a serial forking =
proxy in that it only alerts one called thing<o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><p class=3DMsoNormal>at a time, do you end up with one session or =
with two.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:green'=
>PEJ: This is similar to the case where a fork is cancelled.&nbsp; Alice =
is only in one communication session and the SBC has to pick a UUID to =
return.&nbsp; However, the UUID can change if the other device actually =
answers.&nbsp; For that matter, the SBC could even fabricate a temporary =
value, knowing there is a 50/50 change it will change, anyway.&nbsp; =
What&#8217;s important is the end result: the &#8220;stable =
call&#8221;.&nbsp; Once the call is connected, there are just two =
devices, Alice and some Bob.&nbsp; And, if the Bob changes during call =
establishment, the UUID value will change on that end.&nbsp; =
That&#8217;s perfectly fine.</span><o:p></o:p></p></div></blockquote><p =
class=3DMsoNormal>I had to read this several times to make sure, but I =
think the end result is that you said &quot;two&quot; (or perhaps even =
three) here, but if you were looking at whole set of messages between =
the three UAs involved, you would never try to identify them all with a =
single session identifier. Did I hear you =
correctly?<br><br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C=
0'>PEJ: Alice sends an INVITE and gets back a single 180, even if the =
B2BUA gets 10 180s, right?&nbsp; In that case, there are 10 Bobs ringing =
and there would be 10 communication sessions {Alice, Bob-1}, {Alice, =
Bob-2}, &#8230;.&nbsp; However, only the SBC sees those.&nbsp; =
That&#8217;s because the SBC is not forwarding all messages to =
Alice.&nbsp; The SBC is going to forward <i>something</i> to =
Alice.&nbsp; Would this be Bob-1 or some UUID fabricated by the SBC? =
&nbsp;Does not really matter, since the remote end is allowed to change. =
&nbsp;So, the SBC could send a UUID such that Alice has {Alice, SBC}, =
but then when Bob-5 sends a 200, Alice updates her Session-ID to be { =
Alice, Bob-5 }.&nbsp; Because session establishment works like this, we =
need something that is flexible enough to accommodate.&nbsp; =
That&#8217;s the reason we propose to use two UUIID values. &nbsp;Each =
UUID identifies a particular physical or logical endpoint in a =
session.&nbsp; The set of two UUIDs define the communication session =
comprised of those two endpoints.</span><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></blockquote><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>You probably aren't =
doing this on purpose, but it feels like you are trying to avoid =
answering my direct questions.<br><br>I would be a lot more comfortable =
that we're not talking past each other if you had said clearly =
&quot;yes&quot; or &quot;no&quot; above <br>(and then launched into an =
explanation if you needed to). I think you said &quot;yes&quot;, and =
then explained more about <br>why &quot;perhaps even three&quot; might =
be the case. Would you confirm that?<span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#4F622=
8;mso-style-textfill-fill-color:#4F6228;mso-style-textfill-fill-alpha:100=
.0%'><span style=3D'color:windowtext'>PEJ: Yes :-) I apologize for =
adding more text, but I got the impression you were still unsure and =
I&#8217;m willing to explain all day.</span></span><br><br>And =
specifically, you agree that &quot;If you were looking at the whole set =
of messages between the three UAs involved, you would never try to =
identify them all with a single session identifier.&quot;?<span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#4F622=
8;mso-style-textfill-fill-color:#4F6228;mso-style-textfill-fill-alpha:100=
.0%'><span style=3D'color:windowtext'>PEJ: Correct.&nbsp; =
(Optional-to-read elaboration: Alice would use the same UUID between her =
and the two Bobs.&nbsp; However, each Bob would use a distinct UUID and =
therefore the Session-IDs would be different between Alice and Bob-1 as =
compared to Alice and Bob-2.)<o:p></o:p></span></span></p><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#4F622=
8;mso-style-textfill-fill-color:#4F6228;mso-style-textfill-fill-alpha:100=
.0%'><span =
style=3D'color:windowtext'>Paul<o:p></o:p></span></span></p><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>If you aren't =
comfortable just saying yes to both of those things, we need to discuss =
more about why. If you are, then we can move on to the next step of =
working that into a description of what this identifier is =
identifying.<br><br>RjS<br><br><o:p></o:p></p></div></div></body></html>
------=_NextPart_000_01BD_01CE18CC.BD804C20--


From eckelcu@cisco.com  Tue Mar  5 09:35:53 2013
Return-Path: <eckelcu@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE3C321F8698 for <insipid@ietfa.amsl.com>; Tue,  5 Mar 2013 09:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1xH83+K25KY for <insipid@ietfa.amsl.com>; Tue,  5 Mar 2013 09:35:53 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 2235321F8645 for <insipid@ietf.org>; Tue,  5 Mar 2013 09:35:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1371; q=dns/txt; s=iport; t=1362504953; x=1363714553; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=TScfql7GO9gvNdEULxv6XjXDmlDEUNpj9Pb7eZcTldM=; b=CCg2ftzZXPSWJIt7BlUYAwBGIE0dX2CUcG3gi/RgFNlNyqddrEPEIleF 1SO7ojqNxc5mPZXwSGESthNweNmVhV/hl4mC5QRjHWeUAJC1FwMQiQ1eB bvp2kH2ajyYCaLUc37uLWvZFjwa5kpMC4Ual2PyRXG/sg0prxB9peGqYp M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFADcsNlGtJV2d/2dsb2JhbABFAcRtgWgWc4IpAQEBBAEBARodNBcEAgEIEQQBAQsUCQcnCxQJCAEBBAESCAESh3cBDKxSkBKOXCYSBoJZYQOnOIMIgic
X-IronPort-AV: E=Sophos;i="4.84,788,1355097600"; d="scan'208";a="184044404"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 05 Mar 2013 17:35:52 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r25HZqvr003437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Mar 2013 17:35:52 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.144]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.02.0318.004; Tue, 5 Mar 2013 11:35:52 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Call for working group adoption of identifier solution	draft
Thread-Index: Ac4UlDroba7PV9ffSRu5+JxUGGPxMAFM4cFg
Date: Tue, 5 Mar 2013 17:35:52 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828047C7110@xmb-aln-x08.cisco.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.63]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Insipid] Call for working group adoption of identifier solution	draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 17:35:53 -0000

I suppose the adoption of this draft toward addressing the corresponding mi=
lestone.

Cheers,
Charles

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> Behalf Of DRAGE, Keith (Keith)
> Sent: Tuesday, February 26, 2013 6:44 PM
> To: insipid@ietf.org
> Subject: [Insipid] Call for working group adoption of identifier solution=
 draft
>=20
> (As working group cochair)
>=20
> This is a call for the adoption of the text of the draft
>=20
> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>=20
> as a working group draft to meet the milestone
>=20
> Specification of the new identifier sent to the IESG (PS)
>=20
> Please respond as to whether the draft is acceptable or not. You may also
> respond that certain parts are acceptable, or that parts are not acceptab=
le
> (please be specific).
>=20
> This is currently the only text we have on the table to meet the mileston=
e
> and there seems to be some measure of convergence on this text at the
> Atlanta meeting.
>=20
> We will make a decision based on the responses received by Tuesday 12th
> March (i.e. Tuesday of the IETF meeting week).
>=20
> Regards
>=20
> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid

From salvatore.loreto@ericsson.com  Tue Mar  5 09:38:32 2013
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F461F0D12 for <insipid@ietfa.amsl.com>; Tue,  5 Mar 2013 09:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.248
X-Spam-Level: 
X-Spam-Status: No, score=-106.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6bHiFiJ73tI for <insipid@ietfa.amsl.com>; Tue,  5 Mar 2013 09:38:31 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 360391F0D10 for <insipid@ietf.org>; Tue,  5 Mar 2013 09:38:31 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-53-51362d961996
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 92.D2.10459.69D26315; Tue,  5 Mar 2013 18:38:30 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.279.1; Tue, 5 Mar 2013 18:38:29 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 8BEA12AFD	for <insipid@ietf.org>; Tue,  5 Mar 2013 19:38:29 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id DA68A54649	for <insipid@ietf.org>; Tue,  5 Mar 2013 19:38:26 +0200 (EET)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 69EB75453E	for <insipid@ietf.org>; Tue,  5 Mar 2013 19:38:26 +0200 (EET)
Message-ID: <51362D94.801@ericsson.com>
Date: Tue, 5 Mar 2013 18:38:28 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: insipid@ietf.org
References: <EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------060600070804090303060509"
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBLMWRmVeSWpSXmKPExsUyM+Jvje40XbNAg1d3RC3m33/G5MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujPnTrrIWLJOo2H9iFmMD4w/hLkZODgkBE4lDx4+yQ9hiEhfu rWfrYuTiEBI4yShx4MkNKGc9o8T7E13sEM5FRok132AyRxglVnycywzhnGWU+Dn9MRPIMF4B dYm7nxezgNgsAioSS2c8A4uzCZhJPH+4hRnEFhVIlvj36AgjRL2gxMmZT8DqRQREJH7fnQJ2 lLBAqMT9vmNg9UIC8RI3G9vBajgFEiQ2XpwO1MvBwSwQJrFlZzLED2oSV89tgirXkug928k0 gVF4FpINsxA6QMLMArYSF+ZcZ4Gw5SW2v53DDGHrSlz4PwVFfAEj2ypG9tzEzJz0csNNjMDQ P7jlt+4OxlPnRA4xSnOwKInzhrleCBASSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAmBIS4D57 WZZI0rWpp6Pn+k9oiXP9r+CulGjTZ/wwxn9e8JScvitrS1V8f6ZN7JA1Nb1aHNXGwFm8lVPR 3CJwkWzYt3/pkyeExzSFiG+Z8KS6Z7X+hRsxazV6dohwGk23LwsU+nCzwqtxj0aNUqXBERY7 4xn3/nxwmB++saxe7av017XvNTcqsRRnJBpqMRcVJwIA0UWXxUsCAAA=
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 17:38:32 -0000

--------------060600070804090303060509
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

I support the adoption of the draft

cheers
Salvatore

On 2/27/13 3:43 AM, DRAGE, Keith (Keith) wrote:
> (As working group cochair)
>
> This is a call for the adoption of the text of the draft
>
> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>
> as a working group draft to meet the milestone
>
> Specification of the new identifier sent to the IESG (PS)
>
> Please respond as to whether the draft is acceptable or not. You may also respond that certain parts are acceptable, or that parts are not acceptable (please be specific).
>
> This is currently the only text we have on the table to meet the milestone and there seems to be some measure of convergence on this text at the Atlanta meeting.
>
> We will make a decision based on the responses received by Tuesday 12th March (i.e. Tuesday of the IETF meeting week).
>
> Regards
>
> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid



--------------060600070804090303060509
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><font face="Calibri">I support the
        adoption of the draft<br>
        <br>
        cheers<br>
        Salvatore<br>
      </font><br>
      On 2/27/13 3:43 AM, DRAGE, Keith (Keith) wrote:<br>
    </div>
    <blockquote
cite="mid:EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com"
      type="cite">
      <pre wrap="">(As working group cochair)

This is a call for the adoption of the text of the draft

<a class="moz-txt-link-freetext" href="http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt">http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt</a> 

as a working group draft to meet the milestone

Specification of the new identifier sent to the IESG (PS)

Please respond as to whether the draft is acceptable or not. You may also respond that certain parts are acceptable, or that parts are not acceptable (please be specific).

This is currently the only text we have on the table to meet the milestone and there seems to be some measure of convergence on this text at the Atlanta meeting.

We will make a decision based on the responses received by Tuesday 12th March (i.e. Tuesday of the IETF meeting week).

Regards

Keith
_______________________________________________
insipid mailing list
<a class="moz-txt-link-abbreviated" href="mailto:insipid@ietf.org">insipid@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a>
</pre>
    </blockquote>
    <br>
    <br>
  </body>
</html>

--------------060600070804090303060509--

From laura.liess.dt@googlemail.com  Wed Mar  6 03:53:41 2013
Return-Path: <laura.liess.dt@googlemail.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35FC821F88B1 for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 03:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dbSBIM8epjX for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 03:53:40 -0800 (PST)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4653921F888B for <insipid@ietf.org>; Wed,  6 Mar 2013 03:53:40 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id r6so7875711wey.19 for <insipid@ietf.org>; Wed, 06 Mar 2013 03:53:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=PmNGXBr12IqDebCK3Ik0Z5+NqqrXoh2/SRkCGkDUUPk=; b=T0yMpkwBwZTzTTwDDWh0yfdzcJ8hqZBtGLHOYJmlsq98MNE1RpBoYZJjs8Cwm78Hs8 2YLIIFZaf0xzuqQJGcxJiZcDkT8ipY6aiznqV6GJXmJNfVxJkCJPxZ2n9i3cVWHG9U9Z X5nvEdOriqPIa5NYNkdKuH2fEPSk5tIJuTWr28OKbSxAoqqMYPxk5lkWTAkEWW4QrB2D wJHd/IRZTlA3SgK5BXxkLt9XJVJYmhynvBraB2lit/ZliTIf2wwYiXQ4K87q2ssEYdrB 4cWaj8U9QD3O07JM9nakgrjmzrTPX+YSfboMk+PveWcCbh94mIdJY136PCSsgrrtBgna yb+Q==
MIME-Version: 1.0
X-Received: by 10.180.183.193 with SMTP id eo1mr25214300wic.19.1362570818114;  Wed, 06 Mar 2013 03:53:38 -0800 (PST)
Received: by 10.180.90.207 with HTTP; Wed, 6 Mar 2013 03:53:38 -0800 (PST)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Wed, 6 Mar 2013 12:53:38 +0100
Message-ID: <CACWXZj0K+marrTxBB4RhfYZU392kARkf0rsbAnReKtECDbKTWQ@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=001a11c241ce985c0204d7403d28
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 06 Mar 2013 11:53:42 -0000

--001a11c241ce985c0204d7403d28
Content-Type: text/plain; charset=ISO-8859-1

I am interested in the adoption of the draft.

Thani you
Laura

2013/2/27 DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com>

> (As working group cochair)
>
> This is a call for the adoption of the text of the draft
>
> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>
> as a working group draft to meet the milestone
>
> Specification of the new identifier sent to the IESG (PS)
>
> Please respond as to whether the draft is acceptable or not. You may also
> respond that certain parts are acceptable, or that parts are not acceptable
> (please be specific).
>
> This is currently the only text we have on the table to meet the milestone
> and there seems to be some measure of convergence on this text at the
> Atlanta meeting.
>
> We will make a decision based on the responses received by Tuesday 12th
> March (i.e. Tuesday of the IETF meeting week).
>
> Regards
>
> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>

--001a11c241ce985c0204d7403d28
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I am interested in the adoption of the draft. <br><br>Thani you<br>Laura <b=
r><br><div class=3D"gmail_quote">2013/2/27 DRAGE, Keith (Keith) <span dir=
=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-lucent.com" target=3D"_b=
lank">keith.drage@alcatel-lucent.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">(As working group cochair)<br>
<br>
This is a call for the adoption of the text of the draft<br>
<br>
<a href=3D"http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt" ta=
rget=3D"_blank">http://www.ietf.org/id/draft-jones-insipid-session-id-02.tx=
t</a><br>
<br>
as a working group draft to meet the milestone<br>
<br>
Specification of the new identifier sent to the IESG (PS)<br>
<br>
Please respond as to whether the draft is acceptable or not. You may also r=
espond that certain parts are acceptable, or that parts are not acceptable =
(please be specific).<br>
<br>
This is currently the only text we have on the table to meet the milestone =
and there seems to be some measure of convergence on this text at the Atlan=
ta meeting.<br>
<br>
We will make a decision based on the responses received by Tuesday 12th Mar=
ch (i.e. Tuesday of the IETF meeting week).<br>
<br>
Regards<br>
<br>
Keith<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>

--001a11c241ce985c0204d7403d28--

From gsalguei@cisco.com  Wed Mar  6 07:40:17 2013
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0951721F8BEA for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 07:40:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZWOm1OZCd5Jv for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 07:40:16 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 23BED21F8BE4 for <insipid@ietf.org>; Wed,  6 Mar 2013 07:40:16 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r26FeE1T007727 for <insipid@ietf.org>; Wed, 6 Mar 2013 10:40:14 -0500 (EST)
Received: from dhcp-10-150-54-128.cisco.com (dhcp-10-150-54-128.cisco.com [10.150.54.128]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r26FeEAb027888 for <insipid@ietf.org>; Wed, 6 Mar 2013 10:40:14 -0500 (EST)
From: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E159D850-5F02-4D25-AB9C-D0DFBBA50FF2"
Date: Wed, 6 Mar 2013 10:40:13 -0500
References: <mailman.189.1362577071.3430.insipid@ietf.org>
To: "insipid@ietf.org" <insipid@ietf.org>
Message-Id: <C1999DCC-3F55-4FA0-8AAE-EBB3610FF87A@cisco.com>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [Insipid] Fwd: Uncaught bounce notification
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 06 Mar 2013 15:40:17 -0000

--Apple-Mail=_E159D850-5F02-4D25-AB9C-D0DFBBA50FF2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Forwarding Roland's email supporting adoption.

Gonzalo

Begin forwarded message:

> From: mailman-bounces@ietf.org
> Subject: Uncaught bounce notification
> Date: March 6, 2013 8:37:51 AM EST
> To: insipid-owner@ietf.org
>=20
> The attached message was received as a bounce, but either the bounce
> format was not recognized, or no member addresses could be extracted
> from it.  This mailing list has been configured to send all
> unrecognized bounce messages to the list administrator(s).
>=20
> For more information see:
> https://www.ietf.org/mailman/admin/insipid/bounce
>=20
>=20
> From: <R.Jesske@telekom.de>
> Subject: AW: [Insipid] Call for working group adoption of identifier =
solution draft
> Date: March 6, 2013 8:37:43 AM EST
> To: <keith.drage@alcatel-lucent.com>, <insipid-bounces@ietf.org>
>=20
>=20
> Hi Keith,
> I vote for adoption.
>=20
> Best Regards
>=20
> Roland
>=20
>> -----Urspr=FCngliche Nachricht-----
>> Von: insipid-bounces@ietf.org
>> [mailto:insipid-bounces@ietf.org] Im Auftrag von DRAGE, Keith (Keith)
>> Gesendet: Freitag, 1. M=E4rz 2013 19:12
>> An: DRAGE, Keith (Keith); insipid@ietf.org
>> Betreff: Re: [Insipid] Call for working group adoption of
>> identifier solution draft
>>=20
>> (As WG cochair)
>>=20
>> I know the call has only been out a couple of days, but so
>> far there has been absolute silence on this.
>>=20
>> So this is to indicate that the chairs do need positive
>> responses as well as negative ones.
>>=20
>> If we get no responses we'll just assume no one is
>> interested, with the appropriate consequences.
>>=20
>> Keith
>>=20
>>> -----Original Message-----
>>> From: DRAGE, Keith (Keith)
>>> Sent: 27 February 2013 02:44
>>> To: insipid@ietf.org
>>> Subject: Call for working group adoption of identifier
>> solution draft
>>>=20
>>> (As working group cochair)
>>>=20
>>> This is a call for the adoption of the text of the draft
>>>=20
>>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>>>=20
>>> as a working group draft to meet the milestone
>>>=20
>>> Specification of the new identifier sent to the IESG (PS)
>>>=20
>>> Please respond as to whether the draft is acceptable or
>> not. You may
>>> also respond that certain parts are acceptable, or that
>> parts are not
>>> acceptable (please be specific).
>>>=20
>>> This is currently the only text we have on the table to meet the
>>> milestone and there seems to be some measure of convergence on this
>>> text at the Atlanta meeting.
>>>=20
>>> We will make a decision based on the responses received by Tuesday
>>> 12th March (i.e. Tuesday of the IETF meeting week).
>>>=20
>>> Regards
>>>=20
>>> Keith
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>>=20
>=20
>=20


--Apple-Mail=_E159D850-5F02-4D25-AB9C-D0DFBBA50FF2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Forwarding Roland's email supporting =
adoption.</div><div><br></div><div>Gonzalo</div><div><br><div>Begin =
forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:mailman-bounces@ietf.org">mailman-bounces@ietf.org</a><br><=
/span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>Subject: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><b>Uncaught bounce =
notification</b><br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>Date: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">March 6, 2013 8:37:51 AM EST<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:insipid-owner@ietf.org">insipid-owner@ietf.org</a><br></spa=
n></div><br>The attached message was received as a bounce, but either =
the bounce<br>format was not recognized, or no member addresses could be =
extracted<br>from it. &nbsp;This mailing list has been configured to =
send all<br>unrecognized bounce messages to the list =
administrator(s).<br><br>For more information see:<br><a =
href=3D"https://www.ietf.org/mailman/admin/insipid/bounce">https://www.iet=
f.org/mailman/admin/insipid/bounce</a><br><br><br><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(127, 127, 127, 1.0);"><b>From: =
</b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">&lt;R.Jesske@telekom.de&gt;<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(127, 127, 127, 1.0);"><b>Subject: =
</b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><b>AW: [Insipid] Call for working group adoption of =
identifier solution draft</b><br></span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(127, 127, =
127, 1.0);"><b>Date: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">March 6, 2013 8:37:43 AM EST<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(127, 127, 127, 1.0);"><b>To: =
</b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">&lt;keith.drage@alcatel-lucent.com&gt;, =
&lt;insipid-bounces@ietf.org&gt;<br></span></div><br><br>Hi Keith,<br>I =
vote for adoption.<br><br>Best Regards<br><br>Roland<br><br><blockquote =
type=3D"cite">-----Urspr=FCngliche Nachricht-----<br>Von: =
insipid-bounces@ietf.org<br>[mailto:insipid-bounces@ietf.org] Im Auftrag =
von DRAGE, Keith (Keith)<br>Gesendet: Freitag, 1. M=E4rz 2013 =
19:12<br>An: DRAGE, Keith (Keith); insipid@ietf.org<br>Betreff: Re: =
[Insipid] Call for working group adoption of<br>identifier solution =
draft<br><br>(As WG cochair)<br><br>I know the call has only been out a =
couple of days, but so<br>far there has been absolute silence on =
this.<br><br>So this is to indicate that the chairs do need =
positive<br>responses as well as negative ones.<br><br>If we get no =
responses we'll just assume no one is<br>interested, with the =
appropriate consequences.<br><br>Keith<br><br><blockquote =
type=3D"cite">-----Original Message-----<br>From: DRAGE, Keith =
(Keith)<br>Sent: 27 February 2013 02:44<br>To: =
insipid@ietf.org<br>Subject: Call for working group adoption of =
identifier<br></blockquote>solution draft<br><blockquote =
type=3D"cite"><br>(As working group cochair)<br><br>This is a call for =
the adoption of the text of the =
draft<br><br>http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt<=
br><br>as a working group draft to meet the =
milestone<br><br>Specification of the new identifier sent to the IESG =
(PS)<br><br>Please respond as to whether the draft is acceptable =
or<br></blockquote>not. You may<br><blockquote type=3D"cite">also =
respond that certain parts are acceptable, or that<br></blockquote>parts =
are not<br><blockquote type=3D"cite">acceptable (please be =
specific).<br><br>This is currently the only text we have on the table =
to meet the<br>milestone and there seems to be some measure of =
convergence on this<br>text at the Atlanta meeting.<br><br>We will make =
a decision based on the responses received by Tuesday<br>12th March =
(i.e. Tuesday of the IETF meeting =
week).<br><br>Regards<br><br>Keith<br></blockquote>_______________________=
________________________<br>insipid mailing =
list<br>insipid@ietf.org<br>https://www.ietf.org/mailman/listinfo/insipid<=
br><br></blockquote><br><br></blockquote></div><br></body></html>=

--Apple-Mail=_E159D850-5F02-4D25-AB9C-D0DFBBA50FF2--

From muthu.arul@gmail.com  Wed Mar  6 07:50:39 2013
Return-Path: <muthu.arul@gmail.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF76621F8AF0 for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 07:50:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o2xwiDcc9F9q for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 07:50:38 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE5821F8AC3 for <insipid@ietf.org>; Wed,  6 Mar 2013 07:50:37 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id x8so8285733wey.6 for <insipid@ietf.org>; Wed, 06 Mar 2013 07:50:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=70t4Z4IPvmAItOFwMw85BJdMDOnHgsNcYO399QoBn3w=; b=iPLWtLxta8L4xmgissqHUG2WbaJkfNVGzz9cuZ0Ibor6oPkcLft37HwObo+w7WqddI hNplLW+Mmnj6/faNrAZj0Nn6/I3HGUiANS85UtyUurW4jIjV+MEtW3zcNQNxRtHprabZ OY/siRgL0CHL8RANTXrYGqY9QOcKIr3+r7ovfmJplAHZGZOExhPgZhiI5YrazEOrUMsS znzagLYjxWFVLx4Rm3tbs7cs/9VZ2Vr9Bw7cZqkivhNSVluFY3271eG3yAevWBPOKh78 r2eBdNUNWQlPm9UX/OlYtWwKZBq6H73gwQP+CLcqHZvab7l5Fe5JPS11D8wsxpTauQvS iPjw==
MIME-Version: 1.0
X-Received: by 10.180.93.234 with SMTP id cx10mr27213755wib.34.1362585037126;  Wed, 06 Mar 2013 07:50:37 -0800 (PST)
Received: by 10.180.102.198 with HTTP; Wed, 6 Mar 2013 07:50:37 -0800 (PST)
In-Reply-To: <CACWXZj0K+marrTxBB4RhfYZU392kARkf0rsbAnReKtECDbKTWQ@mail.gmail.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210701F2443@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <CACWXZj0K+marrTxBB4RhfYZU392kARkf0rsbAnReKtECDbKTWQ@mail.gmail.com>
Date: Wed, 6 Mar 2013 21:20:37 +0530
Message-ID: <CAKz0y8ycLRMnUiEzF+8AnRzZv=j7O5yfNSNGWepf+8M5XmY1Rg@mail.gmail.com>
From: Muthu Arul <muthu.arul@gmail.com>
To: Laura Liess <laura.liess.dt@googlemail.com>
Content-Type: multipart/alternative; boundary=f46d04388e171d42f804d7438d85
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 06 Mar 2013 15:50:39 -0000

--f46d04388e171d42f804d7438d85
Content-Type: text/plain; charset=ISO-8859-1

+1

Muthu

On Wed, Mar 6, 2013 at 5:23 PM, Laura Liess
<laura.liess.dt@googlemail.com>wrote:

> I am interested in the adoption of the draft.
>
> Thani you
> Laura
>
> 2013/2/27 DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com>
>
> (As working group cochair)
>>
>> This is a call for the adoption of the text of the draft
>>
>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>>
>> as a working group draft to meet the milestone
>>
>> Specification of the new identifier sent to the IESG (PS)
>>
>> Please respond as to whether the draft is acceptable or not. You may also
>> respond that certain parts are acceptable, or that parts are not acceptable
>> (please be specific).
>>
>> This is currently the only text we have on the table to meet the
>> milestone and there seems to be some measure of convergence on this text at
>> the Atlanta meeting.
>>
>> We will make a decision based on the responses received by Tuesday 12th
>> March (i.e. Tuesday of the IETF meeting week).
>>
>> Regards
>>
>> Keith
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>>
>
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>
>

--f46d04388e171d42f804d7438d85
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1<div><br></div><div>Muthu<br><br><div class=3D"gmail_quote">On Wed, Mar 6=
, 2013 at 5:23 PM, Laura Liess <span dir=3D"ltr">&lt;<a href=3D"mailto:laur=
a.liess.dt@googlemail.com" target=3D"_blank">laura.liess.dt@googlemail.com<=
/a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I am interested in the adoption of the draft=
. <br><br>Thani you<br>Laura <br><br><div class=3D"gmail_quote">2013/2/27 D=
RAGE, Keith (Keith) <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alc=
atel-lucent.com" target=3D"_blank">keith.drage@alcatel-lucent.com</a>&gt;</=
span><div>
<div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">(As working group cochair)<br>
<br>
This is a call for the adoption of the text of the draft<br>
<br>
<a href=3D"http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt" ta=
rget=3D"_blank">http://www.ietf.org/id/draft-jones-insipid-session-id-02.tx=
t</a><br>
<br>
as a working group draft to meet the milestone<br>
<br>
Specification of the new identifier sent to the IESG (PS)<br>
<br>
Please respond as to whether the draft is acceptable or not. You may also r=
espond that certain parts are acceptable, or that parts are not acceptable =
(please be specific).<br>
<br>
This is currently the only text we have on the table to meet the milestone =
and there seems to be some measure of convergence on this text at the Atlan=
ta meeting.<br>
<br>
We will make a decision based on the responses received by Tuesday 12th Mar=
ch (i.e. Tuesday of the IETF meeting week).<br>
<br>
Regards<br>
<br>
Keith<br>
_______________________________________________<br>
insipid mailing list<br>
<a href=3D"mailto:insipid@ietf.org" target=3D"_blank">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></div></div><br>
<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>
<br></blockquote></div><br></div>

--f46d04388e171d42f804d7438d85--

From keith.drage@alcatel-lucent.com  Wed Mar  6 18:33:33 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEA0011E809C for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 18:33:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sKkfmzCv-tOj for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 18:33:32 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 64EE521F8525 for <insipid@ietf.org>; Wed,  6 Mar 2013 18:33:29 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r272XSFi006381 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <insipid@ietf.org>; Thu, 7 Mar 2013 03:33:28 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 7 Mar 2013 03:33:28 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Date: Thu, 7 Mar 2013 03:33:25 +0100
Thread-Topic: Comment on draft-jones-insipid-session-id-02
Thread-Index: Ac4a3CUiEkhr+iQLT0iSTtaftvZu1w==
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE2107163BDB0@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Subject: [Insipid] Comment on draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 02:33:33 -0000

In doing a quick read through of the above document, I identified that the =
IANA registration requirements need to register the header field parameters=
 as well as the header field itself.

I suspect that will end up being a registration of "remote" as I think loca=
l-uuid is a value of the header field rather than a parameter. I am however=
 open to correction on this aspect.

Assuming that people agree the ABNF in section 5 is the way forward, I don'=
t see this aspect being contentious.

Regards

Keith

From keith.drage@alcatel-lucent.com  Wed Mar  6 18:35:34 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9CED11E809C for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 18:35:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bgVE51yl3wxk for <insipid@ietfa.amsl.com>; Wed,  6 Mar 2013 18:35:34 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id E954121F8525 for <insipid@ietf.org>; Wed,  6 Mar 2013 18:35:33 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r272ZS6e017058 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <insipid@ietf.org>; Thu, 7 Mar 2013 03:35:31 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Thu, 7 Mar 2013 03:35:30 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Date: Thu, 7 Mar 2013 03:35:25 +0100
Thread-Topic: Referencing error in draft-ietf-insipid-session-id-reqts-05
Thread-Index: Ac4a3GxJfyKU2rSgTl2xDPAHpeQRHw==
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE2107163BDB1@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: [Insipid] Referencing error in draft-ietf-insipid-session-id-reqts-05
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 02:35:34 -0000

In section 4.1 of the above document there is the text "All Requirements in=
 Section 4". I believe this should be "All Requirements in Section 5".

Regards

Keith

From pkyzivat@alum.mit.edu  Thu Mar  7 15:21:07 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D40D21F852B for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 15:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.242
X-Spam-Level: 
X-Spam-Status: No, score=-0.242 tagged_above=-999 required=5 tests=[AWL=0.195,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxPVuM0z0p5C for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 15:21:06 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 6238E21F851F for <insipid@ietf.org>; Thu,  7 Mar 2013 15:21:06 -0800 (PST)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta03.westchester.pa.mail.comcast.net with comcast id 8dV71l0061GhbT853nM5uE; Thu, 07 Mar 2013 23:21:05 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta07.westchester.pa.mail.comcast.net with comcast id 8nM51l00e3ZTu2S3TnM5ES; Thu, 07 Mar 2013 23:21:05 +0000
Message-ID: <513920E0.7020609@alum.mit.edu>
Date: Fri, 08 Mar 2013 07:21:04 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: "insipid@ietf.org" <insipid@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1362698465; bh=B50BTcktD0Qqc+VZKCSzhzMMsjlo5nr+XOCdI2xV/E8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Gy5ieCz3AQGhiU/84IRzUsjuRYvKvVWm5NQXCdVNXsFAiifdJkN7g4kvNc+wUhVVi jrvu9iTXUPTA/0xJEUTXZH/3VpNItvAx+rDd0WedLESgSia9LH8aQe7d0rfHivBl01 l/AVZmFMeolBu0a4XkrdiqGxROngIg5qf97WK3qejUjk9PjsqUGWnh4gir+qv/39sr 48F7LbWnxAQ/NZnWVfCADFDoId1ygBAJaZjFH8Zo7Iiq3g2jvM3qeFNkcl/LW3tRaJ KPn+4fW9DncN2rlKUxFuzhCru4d3ZCelz/HMAEl/wnsbLpgZI1kTQ8oyS35sexls6I 1dpuQnnpnq28w==
Subject: [Insipid] Review of draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 23:21:07 -0000

I just reviewed the latest version. Here are some things I noted:

Formatting:

There is *something* wrong with this draft, but I'm not certain what. 
Both the idnits tool and the diff tool fail on it.

http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-jones-insipid-session-id-02.txt

http://tools.ietf.org/rfcdiff?url2=draft-jones-insipid-session-id-02.txt

Because of this I couldn't tell what was different since the prior 
version and just reviewed this one from scratch.

Syntax:

It is common practice to permit hex to be expressed in either lower or 
upper case, such as:

    sess-uuid = 32(HEXDIG) ; HEXDIG defined in 5234

Section 6:

    It should be noted that messages received by a UA might contain a
    "remote" parameter that does match the UAs UUID.  This might happen
    as a result of service interactions by intermediaries and MUST NOT be
    regarded as an error.

ISTM that this *is* an error, but not one that should be considered 
fatal. It might suggest some investigation to find out what is going on 
to cause it. The key behaviors are that this should not affect what the 
local id for this node and not cause an error.

    An endpoint MUST assume that the UUID value of the peer UA MAY change
    at any time due to service interactions.  However, once an UA
    allocates a UUID value for a communication session, the UA MUST NOT
    change that UUID value for the duration of the session, including
    when communication attempts are retried due to receipt of 4xx
    messages, when the session is redirected in response to a 3xx
    message, or when a session is transferred via a REFER message [6].

If I understand the intent, there is another case that should preserve 
the local uuid: a successful INVITE/Replaces.

Section 7:

    Intermediaries that wish to utilize the Session-ID MAY extract the
    UUID header-values from any SIP message.  Alternatively,
    intermediaries MAY observe the first UUID value in the Session-ID
    header for messages sent in each direction and use those values to
    locally construct the Session Identifier.

The portion of section 6 mentioned earlier says that one may receive a 
message with a remote part that doesn't match the one known locally, and 
that it should be ignored rather than replacing the local one.

If the same thing is observed in an intermediary, this paragraph says 
its ok to either ignore the changed one and stick with what was known, 
or else replace it. The particular choice will affect other nodes.

Section 9.2:

An ACK is shown after the REFER. That is wrong.

Section 9.6:

This example shows some unique behavior. But this behavior is not 
mentioned in the normative section 5 & 6. I don't think these examples 
are normative. So something is missing if you want these to be valid.

	Thanks,
	Paul

From paulej@packetizer.com  Thu Mar  7 20:49:33 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D74FC21F86A8 for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 20:49:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7RcrbQz8fXzJ for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 20:49:33 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 36E9721F86A1 for <insipid@ietf.org>; Thu,  7 Mar 2013 20:49:33 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r284nTuR022006 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Mar 2013 23:49:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362718169; bh=yWSzVfx8gCcnhpZN3zYNlT5X8IZCHQxzKx0hN/V5giA=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=fGU7VGCOT3fjuYefLdVf7Kk7lL1rkI6vyBXinMZ9BV7rizvQJtTJX92d5XWdQzM+F Hev8xccBJzN826uE73fESgJCk4BMkMbjgF/6IOCFZrLJHoeOlHnTnJTezm6ceCaI1O YJAQUv6LgU5uNk1Z1oJHr0p6DT5bgd0xlJ/zSRDA=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, <insipid@ietf.org>
References: <EDC0A1AE77C57744B664A310A0B23AE2107163BDB0@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE2107163BDB0@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Thu, 7 Mar 2013 23:49:43 -0500
Message-ID: <003001ce1bb8$59fda2d0$0df8e870$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDwB7EWOjm/P6GElvq6niEembGxAJpXYIQQ
Content-Language: en-us
Subject: Re: [Insipid] Comment on draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 04:49:34 -0000

Keith,

Indeed.  Here's what we need to add, I think:

+------------------+----------------+-------------------+-----------+
| Header Field     | Parameter Name | Predefined Values | Reference |
+------------------+----------------+-------------------+-----------+
| Session-ID       | remote         | No                | [RFCXXXX] |
+------------------+----------------+-------------------+-----------+

Paul

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> Behalf Of DRAGE, Keith (Keith)
> Sent: Wednesday, March 06, 2013 9:33 PM
> To: insipid@ietf.org
> Subject: [Insipid] Comment on draft-jones-insipid-session-id-02
> 
> In doing a quick read through of the above document, I identified that
> the IANA registration requirements need to register the header field
> parameters as well as the header field itself.
> 
> I suspect that will end up being a registration of "remote" as I think
> local-uuid is a value of the header field rather than a parameter. I am
> however open to correction on this aspect.
> 
> Assuming that people agree the ABNF in section 5 is the way forward, I
> don't see this aspect being contentious.
> 
> Regards
> 
> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From paulej@packetizer.com  Thu Mar  7 20:50:44 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A794621F86C5 for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 20:50:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cTw0VitfK5zN for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 20:50:44 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD8221F86C9 for <insipid@ietf.org>; Thu,  7 Mar 2013 20:50:43 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r284ofro022081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Mar 2013 23:50:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362718242; bh=66/xUX6XdWYlu+TYQagru8rs8rmJNAh4uisaYSq25W8=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=FolA8PjpJyXQ/cIUNMEtf0/7UBkMRhDvbtVk7jHO0zv82OxEugHQ88cr5hz/KmF1I 5Nwq/GlzBeQHQer4MSv5GZxgSS6BDaq0H9O+8ZFGEI6WmPApn2+7Esz7Cg9VIV4HnO XromhuuZSMz5Ohm+h0HeP7FJd2jBPEkMOmIHXNgQ=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'DRAGE, Keith \(Keith\)'" <keith.drage@alcatel-lucent.com>, <insipid@ietf.org>
References: <EDC0A1AE77C57744B664A310A0B23AE2107163BDB1@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE2107163BDB1@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Thu, 7 Mar 2013 23:50:55 -0500
Message-ID: <003201ce1bb8$8512fe70$8f38fb50$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLw2jbWp28I00PD0F2GEmTCuteptpZVvJAg
Content-Language: en-us
Subject: Re: [Insipid] Referencing error in	draft-ietf-insipid-session-id-reqts-05
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 04:50:44 -0000

Changed.

Thanks!

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> Behalf Of DRAGE, Keith (Keith)
> Sent: Wednesday, March 06, 2013 9:35 PM
> To: insipid@ietf.org
> Subject: [Insipid] Referencing error in draft-ietf-insipid-session-id-
> reqts-05
> 
> In section 4.1 of the above document there is the text "All Requirements
> in Section 4". I believe this should be "All Requirements in Section 5".
> 
> Regards
> 
> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From paulej@packetizer.com  Thu Mar  7 21:52:48 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D42B11E80A3 for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 21:52:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aAYtRst6n1xJ for <insipid@ietfa.amsl.com>; Thu,  7 Mar 2013 21:52:47 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 6216311E809C for <insipid@ietf.org>; Thu,  7 Mar 2013 21:52:47 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r285qjpo024862 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Mar 2013 00:52:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362721966; bh=lOZLtruUaWbURSFLkAbC9JzPE5BKZl25BsLfKn1Fz0Y=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=pwVF8SvcT5qrgTbJ6iLA6vr6y4ewvx6upQJ63ObUe9Q+nDm4t8eG9pjNitYI1m+VP 4tgbOHOUSXTM6JKNe+Gla+akTbc4jebIMiiCw9qmywy3RRZ2ntC2sn03wVqmEbd/ig OSVCK4XNnly2IaaYr3V1IANBtQc0vYJjQJ8a6N10=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>, <insipid@ietf.org>
References: <513920E0.7020609@alum.mit.edu>
In-Reply-To: <513920E0.7020609@alum.mit.edu>
Date: Fri, 8 Mar 2013 00:52:59 -0500
Message-ID: <004301ce1bc1$30fb0b80$92f12280$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHVssP/eJH6ffGxuuSwYKVaIXeWR5iMD8Sw
Content-Language: en-us
Subject: Re: [Insipid] Review of draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 05:52:48 -0000

Paul,

> Formatting:
> 
> There is *something* wrong with this draft, but I'm not certain what.
> Both the idnits tool and the diff tool fail on it.

We saw that, too.  I also tried using Microsoft Word to do a diff on the
.docx version of these files and it hung on me.  I think there are ghosts in
the machines that do not want a diff produced of this text.
 
> Syntax:
> 
> It is common practice to permit hex to be expressed in either lower or
> upper case, such as:
> 
>     sess-uuid = 32(HEXDIG) ; HEXDIG defined in 5234

If I'm reading RFC 5234 correctly, HEXDIG is defined to use only uppercase.
Am I misreading that?

Anyway, what do we want here?  Upper, lower, or either?  I don't really have
a preference.
 
> Section 6:
> 
>     It should be noted that messages received by a UA might contain a
>     "remote" parameter that does match the UAs UUID.  This might happen
>     as a result of service interactions by intermediaries and MUST NOT
> be
>     regarded as an error.
> 
> ISTM that this *is* an error, but not one that should be considered
> fatal. It might suggest some investigation to find out what is going on
> to cause it. The key behaviors are that this should not affect what the
> local id for this node and not cause an error.

How about this:

    It should be noted that messages received by a UA might contain a
    "remote" parameter that does match the UAs UUID.  This might happen
    as a result of service interactions by intermediaries and MUST NOT
    negatively affect the communication session.  However, the UA may
    log this event for the purposes of troubleshooting.

>     An endpoint MUST assume that the UUID value of the peer UA MAY
> change
>     at any time due to service interactions.  However, once an UA
>     allocates a UUID value for a communication session, the UA MUST NOT
>     change that UUID value for the duration of the session, including
>     when communication attempts are retried due to receipt of 4xx
>     messages, when the session is redirected in response to a 3xx
>     message, or when a session is transferred via a REFER message [6].
> 
> If I understand the intent, there is another case that should preserve
> the local uuid: a successful INVITE/Replaces.

Yes; I will add that.
 
> Section 7:
> 
>     Intermediaries that wish to utilize the Session-ID MAY extract the
>     UUID header-values from any SIP message.  Alternatively,
>     intermediaries MAY observe the first UUID value in the Session-ID
>     header for messages sent in each direction and use those values to
>     locally construct the Session Identifier.
> 
> The portion of section 6 mentioned earlier says that one may receive a
> message with a remote part that doesn't match the one known locally, and
> that it should be ignored rather than replacing the local one.

Section 6 talks about what Alice would do if Bob sent her a "remote" value
that did not match her UUID.  She should ignore it, by and large.  The
intermediaries would not be privy to the knowledge Alice has.  As far as
they are concerned, the "remote" value from Bob is the correct one, so I can
appreciate that they would us it.  However, Alice will generate a reply to
Bob and she would insert her UUID in that reply. So, the intermediary will
learn what Alice's UUID is.  The intermediary should just assume it changed
again.

> If the same thing is observed in an intermediary, this paragraph says
> its ok to either ignore the changed one and stick with what was known,
> or else replace it. The particular choice will affect other nodes.

Given the above explanation, do you think we need to change the text?  I'm
not sure what to add, but will take input.
 
> Section 9.2:
> 
> An ACK is shown after the REFER. That is wrong.

Deleted.

> Section 9.6:
> 
> This example shows some unique behavior. But this behavior is not
> mentioned in the normative section 5 & 6. I don't think these examples
> are normative. So something is missing if you want these to be valid.

We need to talk about this one.  James has this planned for discussion next
week.  I'll wait to do something here.

Thanks!
Paul



From pkyzivat@alum.mit.edu  Fri Mar  8 07:28:09 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA30421F8751 for <insipid@ietfa.amsl.com>; Fri,  8 Mar 2013 07:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.252
X-Spam-Level: 
X-Spam-Status: No, score=-0.252 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1049nKeP51EX for <insipid@ietfa.amsl.com>; Fri,  8 Mar 2013 07:28:08 -0800 (PST)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 6B66621F85C3 for <insipid@ietf.org>; Fri,  8 Mar 2013 07:28:08 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta15.westchester.pa.mail.comcast.net with comcast id 90eZ1l0031uE5Es5F3U8TN; Fri, 08 Mar 2013 15:28:08 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta16.westchester.pa.mail.comcast.net with comcast id 93U71l00c3ZTu2S3c3U7Ai; Fri, 08 Mar 2013 15:28:08 +0000
Message-ID: <513A0387.8030907@alum.mit.edu>
Date: Fri, 08 Mar 2013 23:28:07 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>
References: <513920E0.7020609@alum.mit.edu> <004301ce1bc1$30fb0b80$92f12280$@packetizer.com>
In-Reply-To: <004301ce1bc1$30fb0b80$92f12280$@packetizer.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1362756488; bh=/vcuOYDpouUnTEI3xZbc+Mzol4br+32XOi6cJAN+Qcg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=NGxl8YwaENlCzPNGTa24Cg1B3MpIj8XqKSP4NFc5VMJZsLA0Y++/BEnfczqmZNGEE GJF2KDKmOY6eYAyp5Q0sMer8cJgo8G1sXsIxnrHqO3G2VaPbHfHqPoU625qoYoGrzu 7y3Oa7A4+gbNBV+EhCGgMHdsc3X1a+gFkueyfFGi8s2U/Y3UduI1JMGeQsjAyrdBvb QEt4ODZpMKWcZH87o3SatPorOw330XSek4mxRUxODoA/aLRhWtq2K3a2F4RpzGNTE0 j1wzBycswtoS0MDBDwhqjLX5ki08dA63ygdqU2QiR0DPqXsdemJn5WpbK7Qf4sVD9b h08HuxA3PvuAQ==
Cc: insipid@ietf.org
Subject: Re: [Insipid] Review of draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 15:28:09 -0000

On 3/8/13 1:52 PM, Paul E. Jones wrote:
> Paul,
>
>> Formatting:
>>
>> There is *something* wrong with this draft, but I'm not certain what.
>> Both the idnits tool and the diff tool fail on it.
>
> We saw that, too.  I also tried using Microsoft Word to do a diff on the
> .docx version of these files and it hung on me.  I think there are ghosts in
> the machines that do not want a diff produced of this text.

I don't have a solution for you, but you need to find a solution. 
Ultimately the draft must pass idnits. I suspect the the problem is some 
artifact of using MSWord to format the draft. You could convert over to 
using xml2rfc for this.

>> Syntax:
>>
>> It is common practice to permit hex to be expressed in either lower or
>> upper case, such as:
>>
>>      sess-uuid = 32(HEXDIG) ; HEXDIG defined in 5234
>
> If I'm reading RFC 5234 correctly, HEXDIG is defined to use only uppercase.
> Am I misreading that?

People often get confused by this. In ABNF "A" matches both 'A' and 'a'. 
So HEXDIG matches both upper and lower case hex digits.

> Anyway, what do we want here?  Upper, lower, or either?  I don't really have
> a preference.

Common practice in most places I am aware of is to allow either.

>> Section 6:
>>
>>      It should be noted that messages received by a UA might contain a
>>      "remote" parameter that does match the UAs UUID.  This might happen
>>      as a result of service interactions by intermediaries and MUST NOT
>> be
>>      regarded as an error.
>>
>> ISTM that this *is* an error, but not one that should be considered
>> fatal. It might suggest some investigation to find out what is going on
>> to cause it. The key behaviors are that this should not affect what the
>> local id for this node and not cause an error.
>
> How about this:
>
>      It should be noted that messages received by a UA might contain a
>      "remote" parameter that does match the UAs UUID.  This might happen
>      as a result of service interactions by intermediaries and MUST NOT
>      negatively affect the communication session.  However, the UA may
>      log this event for the purposes of troubleshooting.

WFM

>>      An endpoint MUST assume that the UUID value of the peer UA MAY
>> change
>>      at any time due to service interactions.  However, once an UA
>>      allocates a UUID value for a communication session, the UA MUST NOT
>>      change that UUID value for the duration of the session, including
>>      when communication attempts are retried due to receipt of 4xx
>>      messages, when the session is redirected in response to a 3xx
>>      message, or when a session is transferred via a REFER message [6].
>>
>> If I understand the intent, there is another case that should preserve
>> the local uuid: a successful INVITE/Replaces.
>
> Yes; I will add that.
>
>> Section 7:
>>
>>      Intermediaries that wish to utilize the Session-ID MAY extract the
>>      UUID header-values from any SIP message.  Alternatively,
>>      intermediaries MAY observe the first UUID value in the Session-ID
>>      header for messages sent in each direction and use those values to
>>      locally construct the Session Identifier.
>>
>> The portion of section 6 mentioned earlier says that one may receive a
>> message with a remote part that doesn't match the one known locally, and
>> that it should be ignored rather than replacing the local one.
>
> Section 6 talks about what Alice would do if Bob sent her a "remote" value
> that did not match her UUID.  She should ignore it, by and large.  The
> intermediaries would not be privy to the knowledge Alice has.  As far as
> they are concerned, the "remote" value from Bob is the correct one, so I can
> appreciate that they would us it.  However, Alice will generate a reply to
> Bob and she would insert her UUID in that reply. So, the intermediary will
> learn what Alice's UUID is.  The intermediary should just assume it changed
> again.
>
>> If the same thing is observed in an intermediary, this paragraph says
>> its ok to either ignore the changed one and stick with what was known,
>> or else replace it. The particular choice will affect other nodes.
>
> Given the above explanation, do you think we need to change the text?  I'm
> not sure what to add, but will take input.

I don't know. ISTM that consistency is valuable here - so either always 
use the first value seen or always use the most recent one. Always using 
the first value seen requires the intermediary to be stateful about 
this, so it might be undesirable.

Or perhaps an intermediary that *assigns* the initial value should be 
expected to remember it and behave like an endpoint, while one that did 
not assign the value should just take what comes.

>> Section 9.2:
>>
>> An ACK is shown after the REFER. That is wrong.
>
> Deleted.
>
>> Section 9.6:
>>
>> This example shows some unique behavior. But this behavior is not
>> mentioned in the normative section 5 & 6. I don't think these examples
>> are normative. So something is missing if you want these to be valid.
>
> We need to talk about this one.  James has this planned for discussion next
> week.  I'll wait to do something here.

OK - I can wait if the draft is simply incomplete in this regard. But 
eventually we really need normative specification of expected behavior.

	Thanks,
	Paul


From paulej@packetizer.com  Fri Mar  8 09:01:10 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB9521F8698 for <insipid@ietfa.amsl.com>; Fri,  8 Mar 2013 09:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVBkCnXR8wJd for <insipid@ietfa.amsl.com>; Fri,  8 Mar 2013 09:01:04 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id D3DA121F87D5 for <insipid@ietf.org>; Fri,  8 Mar 2013 09:00:53 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r28H0qHg026155 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Mar 2013 12:00:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1362762053; bh=W6IBvqt6zbrzMqBVHU4NGylib4fL/eMswAx6miTam2s=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=togfiUAozvCeQ1iJE96AaT4TfXGtMT/GLz7j0WhFWevCUZOScR1KvJfOnTJDYQXtQ 9SP/SgOrlyd347fsu2IhNRsTVZRvPk+3OGUESOtYqAm+jqKrQib6t+FpQ6EvLgWQFo Z+RmFkVqY2F2aKbkkIcLyF1slBXac40MmHsBo7eQ=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>
References: <513920E0.7020609@alum.mit.edu> <004301ce1bc1$30fb0b80$92f12280$@packetizer.com> <513A0387.8030907@alum.mit.edu>
In-Reply-To: <513A0387.8030907@alum.mit.edu>
Date: Fri, 8 Mar 2013 12:01:07 -0500
Message-ID: <00cc01ce1c1e$87071cf0$951556d0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHVssP/eJH6ffGxuuSwYKVaIXeWRwJfZDMgAPynhSSYcfHGgA==
Content-Language: en-us
Cc: insipid@ietf.org
Subject: Re: [Insipid] Review of draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 17:01:10 -0000

Paul,

> > We saw that, too.  I also tried using Microsoft Word to do a diff on
> > the .docx version of these files and it hung on me.  I think there are
> > ghosts in the machines that do not want a diff produced of this text.
> 
> I don't have a solution for you, but you need to find a solution.
> Ultimately the draft must pass idnits. I suspect the the problem is some
> artifact of using MSWord to format the draft. You could convert over to
> using xml2rfc for this.

It appears to be functional now.
 
> >> Syntax:
> >>
> >> It is common practice to permit hex to be expressed in either lower
> >> or upper case, such as:
> >>
> >>      sess-uuid = 32(HEXDIG) ; HEXDIG defined in 5234
> >
> > If I'm reading RFC 5234 correctly, HEXDIG is defined to use only
> uppercase.
> > Am I misreading that?
> 
> People often get confused by this. In ABNF "A" matches both 'A' and 'a'.
> So HEXDIG matches both upper and lower case hex digits.

OK.  I changed the production as you suggested.
 
> > Section 6 talks about what Alice would do if Bob sent her a "remote"
> > value that did not match her UUID.  She should ignore it, by and
> > large.  The intermediaries would not be privy to the knowledge Alice
> > has.  As far as they are concerned, the "remote" value from Bob is the
> > correct one, so I can appreciate that they would us it.  However,
> > Alice will generate a reply to Bob and she would insert her UUID in
> > that reply. So, the intermediary will learn what Alice's UUID is.  The
> > intermediary should just assume it changed again.
> >
> >> If the same thing is observed in an intermediary, this paragraph says
> >> its ok to either ignore the changed one and stick with what was
> >> known, or else replace it. The particular choice will affect other
> nodes.
> >
> > Given the above explanation, do you think we need to change the text?
> > I'm not sure what to add, but will take input.
> 
> I don't know. ISTM that consistency is valuable here - so either always
> use the first value seen or always use the most recent one. Always using
> the first value seen requires the intermediary to be stateful about this,
> so it might be undesirable.

The intent was that devices would always use the most recent value seen.
State should not necessarily be maintained for these values, though I can
appreciate why some devices might want to maintain state (e.g., to highlight
endpoint changes when logging call signaling messages).
 
> Or perhaps an intermediary that *assigns* the initial value should be
> expected to remember it and behave like an endpoint, while one that did
> not assign the value should just take what comes.

It would have to keep up with it when initiating the session, like it keeps
up with other parts of the SIP signaling.

This stuff gets into Section 7.  Is there something not covered or should be
changed?

Paul



From keith.drage@alcatel-lucent.com  Sun Mar 10 19:51:05 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23FBD21F8794 for <insipid@ietfa.amsl.com>; Sun, 10 Mar 2013 19:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nTxV0Te+nfQs for <insipid@ietfa.amsl.com>; Sun, 10 Mar 2013 19:51:02 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7E7E121F8429 for <insipid@ietf.org>; Sun, 10 Mar 2013 19:51:00 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r2B2ouuj006093 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 11 Mar 2013 03:50:57 +0100
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 11 Mar 2013 03:50:56 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 11 Mar 2013 03:50:56 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Review of draft-jones-insipid-session-id-02
Thread-Index: Ac4binnt6m2qI3nhRG+L9WQ2XVl2IQCeEYFg
Date: Mon, 11 Mar 2013 02:50:56 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8BFBEF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <513920E0.7020609@alum.mit.edu>
In-Reply-To: <513920E0.7020609@alum.mit.edu>
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
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: Re: [Insipid] Review of draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 02:51:05 -0000

Paul K.,

In respect of the WG call to adopt solution text, does your comment against=
 9.6 mean either, we should omit 9.6 from the WG adopted text (with a subse=
quent proposal to the list to provide the procedures and examples together)=
, or we should put an open issue statement in either section 5 or 6 to indi=
cate this needs to be completed?

Regards

Keith

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On Behal=
f
> Of Paul Kyzivat
> Sent: 07 March 2013 23:21
> To: insipid@ietf.org
> Subject: [Insipid] Review of draft-jones-insipid-session-id-02
>=20
> I just reviewed the latest version. Here are some things I noted:
>=20
> Formatting:
>=20
> There is *something* wrong with this draft, but I'm not certain what.
> Both the idnits tool and the diff tool fail on it.
>=20
> http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-jones-
> insipid-session-id-02.txt
>=20
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-jones-insipid-session-id-02.tx=
t
>=20
> Because of this I couldn't tell what was different since the prior
> version and just reviewed this one from scratch.
>=20
> Syntax:
>=20
> It is common practice to permit hex to be expressed in either lower or
> upper case, such as:
>=20
>     sess-uuid =3D 32(HEXDIG) ; HEXDIG defined in 5234
>=20
> Section 6:
>=20
>     It should be noted that messages received by a UA might contain a
>     "remote" parameter that does match the UAs UUID.  This might happen
>     as a result of service interactions by intermediaries and MUST NOT be
>     regarded as an error.
>=20
> ISTM that this *is* an error, but not one that should be considered
> fatal. It might suggest some investigation to find out what is going on
> to cause it. The key behaviors are that this should not affect what the
> local id for this node and not cause an error.
>=20
>     An endpoint MUST assume that the UUID value of the peer UA MAY change
>     at any time due to service interactions.  However, once an UA
>     allocates a UUID value for a communication session, the UA MUST NOT
>     change that UUID value for the duration of the session, including
>     when communication attempts are retried due to receipt of 4xx
>     messages, when the session is redirected in response to a 3xx
>     message, or when a session is transferred via a REFER message [6].
>=20
> If I understand the intent, there is another case that should preserve
> the local uuid: a successful INVITE/Replaces.
>=20
> Section 7:
>=20
>     Intermediaries that wish to utilize the Session-ID MAY extract the
>     UUID header-values from any SIP message.  Alternatively,
>     intermediaries MAY observe the first UUID value in the Session-ID
>     header for messages sent in each direction and use those values to
>     locally construct the Session Identifier.
>=20
> The portion of section 6 mentioned earlier says that one may receive a
> message with a remote part that doesn't match the one known locally, and
> that it should be ignored rather than replacing the local one.
>=20
> If the same thing is observed in an intermediary, this paragraph says
> its ok to either ignore the changed one and stick with what was known,
> or else replace it. The particular choice will affect other nodes.
>=20
> Section 9.2:
>=20
> An ACK is shown after the REFER. That is wrong.
>=20
> Section 9.6:
>=20
> This example shows some unique behavior. But this behavior is not
> mentioned in the normative section 5 & 6. I don't think these examples
> are normative. So something is missing if you want these to be valid.
>=20
> 	Thanks,
> 	Paul
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid

From keith.drage@alcatel-lucent.com  Sun Mar 10 19:54:17 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48A4C21F85ED for <insipid@ietfa.amsl.com>; Sun, 10 Mar 2013 19:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JwLoMEHZyH2 for <insipid@ietfa.amsl.com>; Sun, 10 Mar 2013 19:54:16 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 80AF121F859B for <insipid@ietf.org>; Sun, 10 Mar 2013 19:54:16 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r2B2sFZn006757 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <insipid@ietf.org>; Mon, 11 Mar 2013 03:54:15 +0100
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (135.120.45.64) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 11 Mar 2013 03:54:15 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Mon, 11 Mar 2013 03:54:15 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: Call for working group adoption of identifier solution draft
Thread-Index: Ac4UlDroba7PV9ffSRu5+JxUGGPxMACE8KGgAdbfH2A=
Date: Mon, 11 Mar 2013 02:54:14 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8BFC0C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.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
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 02:54:17 -0000

(As WG cochair)

It would be nice to see a few more responses to this call (either way) befo=
re the deadline on Tuesday this week.

If you are interested in the INSIPID work, and have not looked at the draft=
 and responded, then please do so.

Regards

Keith

> -----Original Message-----
> From: DRAGE, Keith (Keith)
> Sent: 01 March 2013 18:12
> To: DRAGE, Keith (Keith); insipid@ietf.org
> Subject: RE: Call for working group adoption of identifier solution draft
>=20
> (As WG cochair)
>=20
> I know the call has only been out a couple of days, but so far there has
> been absolute silence on this.
>=20
> So this is to indicate that the chairs do need positive responses as well
> as negative ones.
>=20
> If we get no responses we'll just assume no one is interested, with the
> appropriate consequences.
>=20
> Keith
>=20
> > -----Original Message-----
> > From: DRAGE, Keith (Keith)
> > Sent: 27 February 2013 02:44
> > To: insipid@ietf.org
> > Subject: Call for working group adoption of identifier solution draft
> >
> > (As working group cochair)
> >
> > This is a call for the adoption of the text of the draft
> >
> > http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
> >
> > as a working group draft to meet the milestone
> >
> > Specification of the new identifier sent to the IESG (PS)
> >
> > Please respond as to whether the draft is acceptable or not. You may
> also
> > respond that certain parts are acceptable, or that parts are not
> > acceptable (please be specific).
> >
> > This is currently the only text we have on the table to meet the
> milestone
> > and there seems to be some measure of convergence on this text at the
> > Atlanta meeting.
> >
> > We will make a decision based on the responses received by Tuesday 12th
> > March (i.e. Tuesday of the IETF meeting week).
> >
> > Regards
> >
> > Keith

From pkyzivat@alum.mit.edu  Sun Mar 10 19:57:39 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD8121F87F5 for <insipid@ietfa.amsl.com>; Sun, 10 Mar 2013 19:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.313
X-Spam-Level: 
X-Spam-Status: No, score=0.313 tagged_above=-999 required=5 tests=[AWL=0.750,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4MK9xrUK8Om for <insipid@ietfa.amsl.com>; Sun, 10 Mar 2013 19:57:38 -0700 (PDT)
Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:56]) by ietfa.amsl.com (Postfix) with ESMTP id 6E2C721F87AA for <insipid@ietf.org>; Sun, 10 Mar 2013 19:57:38 -0700 (PDT)
Received: from omta10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by qmta06.emeryville.ca.mail.comcast.net with comcast id A2v91l0030cQ2SLA62xeJf; Mon, 11 Mar 2013 02:57:38 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([IPv6:2001:df8:0:128:1d9f:4522:3569:ca14]) by omta10.emeryville.ca.mail.comcast.net with comcast id A2xc1l00a4B9e0B8W2xdMV; Mon, 11 Mar 2013 02:57:37 +0000
Message-ID: <513D4820.5090608@alum.mit.edu>
Date: Mon, 11 Mar 2013 10:57:36 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <513920E0.7020609@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8BFBEF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8BFBEF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1362970658; bh=Zncb8fHtkrnelfBeaboOdUKymoW4vVZBNosSiEHd9cw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=HJuOjX9Tj7Hl0Cz19Y2v/ns9/e5s1lvz+cyS5SfoTNy4X9gW53WH2mdAROvmX8Qle omdE8M2kD92sFQzIzJAY1f162PGFemnkYlQidahzVFhn6WSulfzK3I4Cj+eSLNxra3 zTSJalRHEH32qYnerOdw5CFIREILD+u9HEFsfc+hF6fJobf5b6zd5A5Ga0n5tAYkHH UjAZKCMsA0pVx9/E8e1Oihzh/GcQacRJLHHIPVSnUAAt8E+SgEDMzoeh+Y3Tws8oCT BzqKOszZsKs3lmPND/HJYRUunLVxYqmtBcmMZ/9BVaTkLoiq2PufUgXu77Mnv3TMsA k8oUlJC8WsjjA==
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Review of draft-jones-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 02:57:39 -0000

On 3/11/13 10:50 AM, DRAGE, Keith (Keith) wrote:
> Paul K.,
>
> In respect of the WG call to adopt solution text, does your comment against 9.6 mean either, we should omit 9.6 from the WG adopted text (with a subsequent proposal to the list to provide the procedures and examples together), or we should put an open issue statement in either section 5 or 6 to indicate this needs to be completed?

IMO it would be sufficient to open an issue that this needs to be defined.

	Thanks,
	Paul

> Regards
>
> Keith
>
>> -----Original Message-----
>> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On Behalf
>> Of Paul Kyzivat
>> Sent: 07 March 2013 23:21
>> To: insipid@ietf.org
>> Subject: [Insipid] Review of draft-jones-insipid-session-id-02
>>
>> I just reviewed the latest version. Here are some things I noted:
>>
>> Formatting:
>>
>> There is *something* wrong with this draft, but I'm not certain what.
>> Both the idnits tool and the diff tool fail on it.
>>
>> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-jones-
>> insipid-session-id-02.txt
>>
>> http://tools.ietf.org/rfcdiff?url2=draft-jones-insipid-session-id-02.txt
>>
>> Because of this I couldn't tell what was different since the prior
>> version and just reviewed this one from scratch.
>>
>> Syntax:
>>
>> It is common practice to permit hex to be expressed in either lower or
>> upper case, such as:
>>
>>      sess-uuid = 32(HEXDIG) ; HEXDIG defined in 5234
>>
>> Section 6:
>>
>>      It should be noted that messages received by a UA might contain a
>>      "remote" parameter that does match the UAs UUID.  This might happen
>>      as a result of service interactions by intermediaries and MUST NOT be
>>      regarded as an error.
>>
>> ISTM that this *is* an error, but not one that should be considered
>> fatal. It might suggest some investigation to find out what is going on
>> to cause it. The key behaviors are that this should not affect what the
>> local id for this node and not cause an error.
>>
>>      An endpoint MUST assume that the UUID value of the peer UA MAY change
>>      at any time due to service interactions.  However, once an UA
>>      allocates a UUID value for a communication session, the UA MUST NOT
>>      change that UUID value for the duration of the session, including
>>      when communication attempts are retried due to receipt of 4xx
>>      messages, when the session is redirected in response to a 3xx
>>      message, or when a session is transferred via a REFER message [6].
>>
>> If I understand the intent, there is another case that should preserve
>> the local uuid: a successful INVITE/Replaces.
>>
>> Section 7:
>>
>>      Intermediaries that wish to utilize the Session-ID MAY extract the
>>      UUID header-values from any SIP message.  Alternatively,
>>      intermediaries MAY observe the first UUID value in the Session-ID
>>      header for messages sent in each direction and use those values to
>>      locally construct the Session Identifier.
>>
>> The portion of section 6 mentioned earlier says that one may receive a
>> message with a remote part that doesn't match the one known locally, and
>> that it should be ignored rather than replacing the local one.
>>
>> If the same thing is observed in an intermediary, this paragraph says
>> its ok to either ignore the changed one and stick with what was known,
>> or else replace it. The particular choice will affect other nodes.
>>
>> Section 9.2:
>>
>> An ACK is shown after the REFER. That is wrong.
>>
>> Section 9.6:
>>
>> This example shows some unique behavior. But this behavior is not
>> mentioned in the normative section 5 & 6. I don't think these examples
>> are normative. So something is missing if you want these to be valid.
>>
>> 	Thanks,
>> 	Paul
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>


From btv1==782186899c1==HKaplan@acmepacket.com  Mon Mar 11 11:11:17 2013
Return-Path: <btv1==782186899c1==HKaplan@acmepacket.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5547D11E81CE for <insipid@ietfa.amsl.com>; Mon, 11 Mar 2013 11:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdNL7whreBcW for <insipid@ietfa.amsl.com>; Mon, 11 Mar 2013 11:11:16 -0700 (PDT)
Received: from mx1.acmepacket.com (mx1.acmepacket.com [216.41.24.33]) by ietfa.amsl.com (Postfix) with ESMTP id 1232211E81C3 for <insipid@ietf.org>; Mon, 11 Mar 2013 11:11:16 -0700 (PDT)
X-ASG-Debug-ID: 1363025474-03fc200f25438ac0001-Waf2p9
Received: from Mail1.acmepacket.com (mail1.acmepacket.com [10.0.0.21]) by mx1.acmepacket.com with ESMTP id cbNOcxQTWLbKAzEG (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Mon, 11 Mar 2013 14:11:14 -0400 (EDT)
X-Barracuda-Envelope-From: HKaplan@acmepacket.com
Received: from MAIL2.acmepacket.com ([169.254.2.222]) by Mail1.acmepacket.com ([169.254.1.130]) with mapi id 14.02.0283.003; Mon, 11 Mar 2013 14:11:14 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Thread-Topic: [Insipid] Call for working group adoption of identifier solution draft
X-ASG-Orig-Subj: Re: [Insipid] Call for working group adoption of identifier solution draft
Thread-Index: AQHOHoPQmzghxzyb/kiuilFWvjHtTw==
Date: Mon, 11 Mar 2013 18:11:12 +0000
Message-ID: <7351F35E-19AB-4815-A2D3-1994FDFED2C6@acmepacket.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8BFC0C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8BFC0C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9A7C91386F433640A2B042A3F98CD0AA@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: mail1.acmepacket.com[10.0.0.21]
X-Barracuda-Start-Time: 1363025474
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://spam.acmepacket.com:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at acmepacket.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=BSF_SC0_MISMATCH_TO
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.124915 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO    Envelope rcpt doesn't match header
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Call for working group adoption of identifier	solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 18:11:44 -0000

Well if you need more input...
I was going to ask if it's possible to postpone the deadline for WG adoptio=
n to fall *after* the INSIPID WG session on Wednesday?

But as I understand it, it doesn't really matter - all you're talking about=
 is adopting the draft as a WG document.  After that point it can still cha=
nge anyway, even changing some things significantly, right?

So since there's no proposed alternative document for a solution, I am also=
 in favor of adopting this document as a WG document.

-hadriel


On Mar 10, 2013, at 10:54 PM, "DRAGE, Keith (Keith)" <keith.drage@alcatel-l=
ucent.com> wrote:

> (As WG cochair)
>=20
> It would be nice to see a few more responses to this call (either way) be=
fore the deadline on Tuesday this week.
>=20
> If you are interested in the INSIPID work, and have not looked at the dra=
ft and responded, then please do so.
>=20
> Regards
>=20
> Keith
>=20
>> -----Original Message-----
>> From: DRAGE, Keith (Keith)
>> Sent: 01 March 2013 18:12
>> To: DRAGE, Keith (Keith); insipid@ietf.org
>> Subject: RE: Call for working group adoption of identifier solution draf=
t
>>=20
>> (As WG cochair)
>>=20
>> I know the call has only been out a couple of days, but so far there has
>> been absolute silence on this.
>>=20
>> So this is to indicate that the chairs do need positive responses as wel=
l
>> as negative ones.
>>=20
>> If we get no responses we'll just assume no one is interested, with the
>> appropriate consequences.
>>=20
>> Keith
>>=20
>>> -----Original Message-----
>>> From: DRAGE, Keith (Keith)
>>> Sent: 27 February 2013 02:44
>>> To: insipid@ietf.org
>>> Subject: Call for working group adoption of identifier solution draft
>>>=20
>>> (As working group cochair)
>>>=20
>>> This is a call for the adoption of the text of the draft
>>>=20
>>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>>>=20
>>> as a working group draft to meet the milestone
>>>=20
>>> Specification of the new identifier sent to the IESG (PS)
>>>=20
>>> Please respond as to whether the draft is acceptable or not. You may
>> also
>>> respond that certain parts are acceptable, or that parts are not
>>> acceptable (please be specific).
>>>=20
>>> This is currently the only text we have on the table to meet the
>> milestone
>>> and there seems to be some measure of convergence on this text at the
>>> Atlanta meeting.
>>>=20
>>> We will make a decision based on the responses received by Tuesday 12th
>>> March (i.e. Tuesday of the IETF meeting week).
>>>=20
>>> Regards
>>>=20
>>> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From gsalguei@cisco.com  Mon Mar 11 12:15:54 2013
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C19E11E818A for <insipid@ietfa.amsl.com>; Mon, 11 Mar 2013 12:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lvsre4OiSF6K for <insipid@ietfa.amsl.com>; Mon, 11 Mar 2013 12:15:54 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id DA06F11E80E2 for <insipid@ietf.org>; Mon, 11 Mar 2013 12:15:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3344; q=dns/txt; s=iport; t=1363029353; x=1364238953; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=RKMtlOXig57DU8JjUI5e3YIpR9P4Ob7/XXBjl57JSoY=; b=YuuXV16Xa33bKP7nnVYI4cjd83jNKDcIOsTFmx0zz0fyrEYBQG4EmzoF wVFWUUrXGFnbNstJ8T9jHioTnVQny7s0qbLYnMxp7XyskCQ5BTCNDa0Gt O39YvQdQcCevPED4xix+nGZ1rjfJHWB25wSQoEGlmhulWC4lI1CyMNLtw s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAJAsPlGtJXG8/2dsb2JhbABDAcRlgV8WdIIpAQEBAwEBAQEaHTQLBQcEAgEIDgMEAQEBHhAnCx0IAgQOBQkSh3IGDL8ojlsIIAsHBoJZYQOWVZB1gwo
X-IronPort-AV: E=Sophos;i="4.84,825,1355097600"; d="scan'208";a="186204235"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 11 Mar 2013 19:15:53 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2BJFrVJ005629 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 Mar 2013 19:15:53 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Mon, 11 Mar 2013 14:15:53 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Thread-Topic: [Insipid] Call for working group adoption of	identifier solution draft
Thread-Index: AQHOHoPoP611A7mWwk2+hAHzY0PLAJig3KpZ
Date: Mon, 11 Mar 2013 19:15:52 +0000
Message-ID: <5F353312-B548-4268-8EA5-7419F67C4256@cisco.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8BFC0C@FR712WXCHMBA11.zeu.alcatel-lucent.com>, <7351F35E-19AB-4815-A2D3-1994FDFED2C6@acmepacket.com>
In-Reply-To: <7351F35E-19AB-4815-A2D3-1994FDFED2C6@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Call for working group adoption of	identifier	solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 19:15:54 -0000

Yeah, you're right.  This is not finalized text, rather is simply adopting =
initial text that the WG supports as a starting point for the work.  We can=
 certainly add/remove/change based on WG consensus.

Gonzalo

On Mar 11, 2013, at 2:11 PM, "Hadriel Kaplan" <HKaplan@acmepacket.com> wrot=
e:

> Well if you need more input...
> I was going to ask if it's possible to postpone the deadline for WG adopt=
ion to fall *after* the INSIPID WG session on Wednesday?
>=20
> But as I understand it, it doesn't really matter - all you're talking abo=
ut is adopting the draft as a WG document.  After that point it can still c=
hange anyway, even changing some things significantly, right?
>=20
> So since there's no proposed alternative document for a solution, I am al=
so in favor of adopting this document as a WG document.
>=20
> -hadriel
>=20
>=20
> On Mar 10, 2013, at 10:54 PM, "DRAGE, Keith (Keith)" <keith.drage@alcatel=
-lucent.com> wrote:
>=20
>> (As WG cochair)
>>=20
>> It would be nice to see a few more responses to this call (either way) b=
efore the deadline on Tuesday this week.
>>=20
>> If you are interested in the INSIPID work, and have not looked at the dr=
aft and responded, then please do so.
>>=20
>> Regards
>>=20
>> Keith
>>=20
>>> -----Original Message-----
>>> From: DRAGE, Keith (Keith)
>>> Sent: 01 March 2013 18:12
>>> To: DRAGE, Keith (Keith); insipid@ietf.org
>>> Subject: RE: Call for working group adoption of identifier solution dra=
ft
>>>=20
>>> (As WG cochair)
>>>=20
>>> I know the call has only been out a couple of days, but so far there ha=
s
>>> been absolute silence on this.
>>>=20
>>> So this is to indicate that the chairs do need positive responses as we=
ll
>>> as negative ones.
>>>=20
>>> If we get no responses we'll just assume no one is interested, with the
>>> appropriate consequences.
>>>=20
>>> Keith
>>>=20
>>>> -----Original Message-----
>>>> From: DRAGE, Keith (Keith)
>>>> Sent: 27 February 2013 02:44
>>>> To: insipid@ietf.org
>>>> Subject: Call for working group adoption of identifier solution draft
>>>>=20
>>>> (As working group cochair)
>>>>=20
>>>> This is a call for the adoption of the text of the draft
>>>>=20
>>>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>>>>=20
>>>> as a working group draft to meet the milestone
>>>>=20
>>>> Specification of the new identifier sent to the IESG (PS)
>>>>=20
>>>> Please respond as to whether the draft is acceptable or not. You may
>>> also
>>>> respond that certain parts are acceptable, or that parts are not
>>>> acceptable (please be specific).
>>>>=20
>>>> This is currently the only text we have on the table to meet the
>>> milestone
>>>> and there seems to be some measure of convergence on this text at the
>>>> Atlanta meeting.
>>>>=20
>>>> We will make a decision based on the responses received by Tuesday 12t=
h
>>>> March (i.e. Tuesday of the IETF meeting week).
>>>>=20
>>>> Regards
>>>>=20
>>>> Keith
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>=20

From keith.drage@alcatel-lucent.com  Mon Mar 11 15:27:09 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 310D521F8E83 for <insipid@ietfa.amsl.com>; Mon, 11 Mar 2013 15:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnUWhIwL7zA0 for <insipid@ietfa.amsl.com>; Mon, 11 Mar 2013 15:27:08 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 52B1421F8DF0 for <insipid@ietf.org>; Mon, 11 Mar 2013 15:27:08 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r2BMR3NU016723 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 11 Mar 2013 23:27:03 +0100
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 11 Mar 2013 23:27:02 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 11 Mar 2013 23:27:02 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>, Hadriel Kaplan <HKaplan@acmepacket.com>
Thread-Topic: [Insipid] Call for working group adoption of	identifier solution draft
Thread-Index: AQHOHozccdcVHpxQP0as0/+525/zWpihEUaA
Date: Mon, 11 Mar 2013 22:27:02 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B011242@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8BFC0C@FR712WXCHMBA11.zeu.alcatel-lucent.com>, <7351F35E-19AB-4815-A2D3-1994FDFED2C6@acmepacket.com> <5F353312-B548-4268-8EA5-7419F67C4256@cisco.com>
In-Reply-To: <5F353312-B548-4268-8EA5-7419F67C4256@cisco.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
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Call for working group adoption of	identifier	solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 22:27:09 -0000

Correct.

The normal process of IETF commenting on adopted text applies. Therefore if=
 you say yes, all you are saying is that the text you support takes us forw=
ard in the process of creating an RFC. If you believe the answer is that it=
 does not, then answer no to all or part of the text.

Keith

> -----Original Message-----
> From: Gonzalo Salgueiro (gsalguei) [mailto:gsalguei@cisco.com]
> Sent: 11 March 2013 19:16
> To: Hadriel Kaplan
> Cc: DRAGE, Keith (Keith); insipid@ietf.org
> Subject: Re: [Insipid] Call for working group adoption of identifier
> solution draft
>=20
> Yeah, you're right.  This is not finalized text, rather is simply adoptin=
g
> initial text that the WG supports as a starting point for the work.  We
> can certainly add/remove/change based on WG consensus.
>=20
> Gonzalo
>=20
> On Mar 11, 2013, at 2:11 PM, "Hadriel Kaplan" <HKaplan@acmepacket.com>
> wrote:
>=20
> > Well if you need more input...
> > I was going to ask if it's possible to postpone the deadline for WG
> adoption to fall *after* the INSIPID WG session on Wednesday?
> >
> > But as I understand it, it doesn't really matter - all you're talking
> about is adopting the draft as a WG document.  After that point it can
> still change anyway, even changing some things significantly, right?
> >
> > So since there's no proposed alternative document for a solution, I am
> also in favor of adopting this document as a WG document.
> >
> > -hadriel
> >
> >
> > On Mar 10, 2013, at 10:54 PM, "DRAGE, Keith (Keith)"
> <keith.drage@alcatel-lucent.com> wrote:
> >
> >> (As WG cochair)
> >>
> >> It would be nice to see a few more responses to this call (either way)
> before the deadline on Tuesday this week.
> >>
> >> If you are interested in the INSIPID work, and have not looked at the
> draft and responded, then please do so.
> >>
> >> Regards
> >>
> >> Keith
> >>
> >>> -----Original Message-----
> >>> From: DRAGE, Keith (Keith)
> >>> Sent: 01 March 2013 18:12
> >>> To: DRAGE, Keith (Keith); insipid@ietf.org
> >>> Subject: RE: Call for working group adoption of identifier solution
> draft
> >>>
> >>> (As WG cochair)
> >>>
> >>> I know the call has only been out a couple of days, but so far there
> has
> >>> been absolute silence on this.
> >>>
> >>> So this is to indicate that the chairs do need positive responses as
> well
> >>> as negative ones.
> >>>
> >>> If we get no responses we'll just assume no one is interested, with
> the
> >>> appropriate consequences.
> >>>
> >>> Keith
> >>>
> >>>> -----Original Message-----
> >>>> From: DRAGE, Keith (Keith)
> >>>> Sent: 27 February 2013 02:44
> >>>> To: insipid@ietf.org
> >>>> Subject: Call for working group adoption of identifier solution draf=
t
> >>>>
> >>>> (As working group cochair)
> >>>>
> >>>> This is a call for the adoption of the text of the draft
> >>>>
> >>>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
> >>>>
> >>>> as a working group draft to meet the milestone
> >>>>
> >>>> Specification of the new identifier sent to the IESG (PS)
> >>>>
> >>>> Please respond as to whether the draft is acceptable or not. You may
> >>> also
> >>>> respond that certain parts are acceptable, or that parts are not
> >>>> acceptable (please be specific).
> >>>>
> >>>> This is currently the only text we have on the table to meet the
> >>> milestone
> >>>> and there seems to be some measure of convergence on this text at th=
e
> >>>> Atlanta meeting.
> >>>>
> >>>> We will make a decision based on the responses received by Tuesday
> 12th
> >>>> March (i.e. Tuesday of the IETF meeting week).
> >>>>
> >>>> Regards
> >>>>
> >>>> Keith
> >> _______________________________________________
> >> insipid mailing list
> >> insipid@ietf.org
> >> https://www.ietf.org/mailman/listinfo/insipid
> >
> > _______________________________________________
> > insipid mailing list
> > insipid@ietf.org
> > https://www.ietf.org/mailman/listinfo/insipid
> >

From paulej@packetizer.com  Tue Mar 12 08:04:58 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F43521F85B8 for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 08:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level: 
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[AWL=0.668,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lZlJCVIF25AK for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 08:04:57 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 183E121F85B2 for <insipid@ietf.org>; Tue, 12 Mar 2013 08:04:57 -0700 (PDT)
Received: from [130.129.20.212] (dhcp-14d4.meeting.ietf.org [130.129.20.212]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2CF4sEL013181 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <insipid@ietf.org>; Tue, 12 Mar 2013 11:04:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1363100696; bh=6mm9Bc45Qur5V7QGSSMPAAVl4Hft+sQo+yfP9aUXH58=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=bP6WHom6XAq5nob7IHL0VsND5Kkc/2FHD/tsZMPRZtc28EH6HkH0gTsA+QzFYRrR3 429iCTPulY+llgRn3yGauTYrSRW+JOb4kSmCYFHhJAHuVTkO6fyVuA/i1qNbFuO9D6 sD627XmFhrj30M1B+3nczbGU9cIOh1MoepWW2Kz4=
Message-ID: <513F4426.8070405@packetizer.com>
Date: Tue, 12 Mar 2013 11:05:10 -0400
From: "Paul E. Jones" <paulej@packetizer.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: insipid@ietf.org
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8BFC0C@FR712WXCHMBA11.zeu.alcatel-lucent.com>, <7351F35E-19AB-4815-A2D3-1994FDFED2C6@acmepacket.com> <5F353312-B548-4268-8EA5-7419F67C4256@cisco.com> <949EF20990823C4C85C18D59AA11AD8B011242@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B011242@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Insipid] Call for working group adoption of	identifier	solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 15:04:58 -0000

Keith, Gonzalo,

Shall I post the -00 WG draft with just the editorial things Keith 
raised now and then publish -01 after further dialog?

Paul

On 3/11/2013 6:27 PM, DRAGE, Keith (Keith) wrote:
> Correct.
>
> The normal process of IETF commenting on adopted text applies. Therefore if you say yes, all you are saying is that the text you support takes us forward in the process of creating an RFC. If you believe the answer is that it does not, then answer no to all or part of the text.
>
> Keith
>
>> -----Original Message-----
>> From: Gonzalo Salgueiro (gsalguei) [mailto:gsalguei@cisco.com]
>> Sent: 11 March 2013 19:16
>> To: Hadriel Kaplan
>> Cc: DRAGE, Keith (Keith); insipid@ietf.org
>> Subject: Re: [Insipid] Call for working group adoption of identifier
>> solution draft
>>
>> Yeah, you're right.  This is not finalized text, rather is simply adopting
>> initial text that the WG supports as a starting point for the work.  We
>> can certainly add/remove/change based on WG consensus.
>>
>> Gonzalo
>>
>> On Mar 11, 2013, at 2:11 PM, "Hadriel Kaplan" <HKaplan@acmepacket.com>
>> wrote:
>>
>>> Well if you need more input...
>>> I was going to ask if it's possible to postpone the deadline for WG
>> adoption to fall *after* the INSIPID WG session on Wednesday?
>>> But as I understand it, it doesn't really matter - all you're talking
>> about is adopting the draft as a WG document.  After that point it can
>> still change anyway, even changing some things significantly, right?
>>> So since there's no proposed alternative document for a solution, I am
>> also in favor of adopting this document as a WG document.
>>> -hadriel
>>>
>>>
>>> On Mar 10, 2013, at 10:54 PM, "DRAGE, Keith (Keith)"
>> <keith.drage@alcatel-lucent.com> wrote:
>>>> (As WG cochair)
>>>>
>>>> It would be nice to see a few more responses to this call (either way)
>> before the deadline on Tuesday this week.
>>>> If you are interested in the INSIPID work, and have not looked at the
>> draft and responded, then please do so.
>>>> Regards
>>>>
>>>> Keith
>>>>
>>>>> -----Original Message-----
>>>>> From: DRAGE, Keith (Keith)
>>>>> Sent: 01 March 2013 18:12
>>>>> To: DRAGE, Keith (Keith); insipid@ietf.org
>>>>> Subject: RE: Call for working group adoption of identifier solution
>> draft
>>>>> (As WG cochair)
>>>>>
>>>>> I know the call has only been out a couple of days, but so far there
>> has
>>>>> been absolute silence on this.
>>>>>
>>>>> So this is to indicate that the chairs do need positive responses as
>> well
>>>>> as negative ones.
>>>>>
>>>>> If we get no responses we'll just assume no one is interested, with
>> the
>>>>> appropriate consequences.
>>>>>
>>>>> Keith
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: DRAGE, Keith (Keith)
>>>>>> Sent: 27 February 2013 02:44
>>>>>> To: insipid@ietf.org
>>>>>> Subject: Call for working group adoption of identifier solution draft
>>>>>>
>>>>>> (As working group cochair)
>>>>>>
>>>>>> This is a call for the adoption of the text of the draft
>>>>>>
>>>>>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>>>>>>
>>>>>> as a working group draft to meet the milestone
>>>>>>
>>>>>> Specification of the new identifier sent to the IESG (PS)
>>>>>>
>>>>>> Please respond as to whether the draft is acceptable or not. You may
>>>>> also
>>>>>> respond that certain parts are acceptable, or that parts are not
>>>>>> acceptable (please be specific).
>>>>>>
>>>>>> This is currently the only text we have on the table to meet the
>>>>> milestone
>>>>>> and there seems to be some measure of convergence on this text at the
>>>>>> Atlanta meeting.
>>>>>>
>>>>>> We will make a decision based on the responses received by Tuesday
>> 12th
>>>>>> March (i.e. Tuesday of the IETF meeting week).
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Keith
>>>> _______________________________________________
>>>> insipid mailing list
>>>> insipid@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/insipid
>>> _______________________________________________
>>> insipid mailing list
>>> insipid@ietf.org
>>> https://www.ietf.org/mailman/listinfo/insipid
>>>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From keith.drage@alcatel-lucent.com  Tue Mar 12 08:06:29 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD65221F89FB for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 08:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MTwetQs0aIJW for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 08:06:29 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id E3E2A21F89E9 for <insipid@ietf.org>; Tue, 12 Mar 2013 08:06:28 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r2CF6I7S027874 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 12 Mar 2013 16:06:25 +0100
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 12 Mar 2013 16:06:23 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 12 Mar 2013 16:06:22 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Paul E. Jones" <paulej@packetizer.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Call for working group adoption of	identifier solution draft
Thread-Index: AQHOHzL9cdcVHpxQP0as0/+525/zWpiiJ8Yg
Date: Tue, 12 Mar 2013 15:06:22 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B011AD7@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8BFC0C@FR712WXCHMBA11.zeu.alcatel-lucent.com>, <7351F35E-19AB-4815-A2D3-1994FDFED2C6@acmepacket.com> <5F353312-B548-4268-8EA5-7419F67C4256@cisco.com> <949EF20990823C4C85C18D59AA11AD8B011242@FR712WXCHMBA11.zeu.alcatel-lucent.com> <513F4426.8070405@packetizer.com>
In-Reply-To: <513F4426.8070405@packetizer.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
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: Re: [Insipid] Call for working group adoption of	identifier	solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 15:06:30 -0000

Something like that but will send you a real mail at lunchtime - taking ses=
sion notes at the moment.

Keith

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On Behal=
f
> Of Paul E. Jones
> Sent: 12 March 2013 15:05
> To: insipid@ietf.org
> Subject: Re: [Insipid] Call for working group adoption of identifier
> solution draft
>=20
> Keith, Gonzalo,
>=20
> Shall I post the -00 WG draft with just the editorial things Keith
> raised now and then publish -01 after further dialog?
>=20
> Paul
>=20
> On 3/11/2013 6:27 PM, DRAGE, Keith (Keith) wrote:
> > Correct.
> >
> > The normal process of IETF commenting on adopted text applies. Therefor=
e
> if you say yes, all you are saying is that the text you support takes us
> forward in the process of creating an RFC. If you believe the answer is
> that it does not, then answer no to all or part of the text.
> >
> > Keith
> >
> >> -----Original Message-----
> >> From: Gonzalo Salgueiro (gsalguei) [mailto:gsalguei@cisco.com]
> >> Sent: 11 March 2013 19:16
> >> To: Hadriel Kaplan
> >> Cc: DRAGE, Keith (Keith); insipid@ietf.org
> >> Subject: Re: [Insipid] Call for working group adoption of identifier
> >> solution draft
> >>
> >> Yeah, you're right.  This is not finalized text, rather is simply
> adopting
> >> initial text that the WG supports as a starting point for the work.  W=
e
> >> can certainly add/remove/change based on WG consensus.
> >>
> >> Gonzalo
> >>
> >> On Mar 11, 2013, at 2:11 PM, "Hadriel Kaplan" <HKaplan@acmepacket.com>
> >> wrote:
> >>
> >>> Well if you need more input...
> >>> I was going to ask if it's possible to postpone the deadline for WG
> >> adoption to fall *after* the INSIPID WG session on Wednesday?
> >>> But as I understand it, it doesn't really matter - all you're talking
> >> about is adopting the draft as a WG document.  After that point it can
> >> still change anyway, even changing some things significantly, right?
> >>> So since there's no proposed alternative document for a solution, I a=
m
> >> also in favor of adopting this document as a WG document.
> >>> -hadriel
> >>>
> >>>
> >>> On Mar 10, 2013, at 10:54 PM, "DRAGE, Keith (Keith)"
> >> <keith.drage@alcatel-lucent.com> wrote:
> >>>> (As WG cochair)
> >>>>
> >>>> It would be nice to see a few more responses to this call (either
> way)
> >> before the deadline on Tuesday this week.
> >>>> If you are interested in the INSIPID work, and have not looked at th=
e
> >> draft and responded, then please do so.
> >>>> Regards
> >>>>
> >>>> Keith
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: DRAGE, Keith (Keith)
> >>>>> Sent: 01 March 2013 18:12
> >>>>> To: DRAGE, Keith (Keith); insipid@ietf.org
> >>>>> Subject: RE: Call for working group adoption of identifier solution
> >> draft
> >>>>> (As WG cochair)
> >>>>>
> >>>>> I know the call has only been out a couple of days, but so far ther=
e
> >> has
> >>>>> been absolute silence on this.
> >>>>>
> >>>>> So this is to indicate that the chairs do need positive responses a=
s
> >> well
> >>>>> as negative ones.
> >>>>>
> >>>>> If we get no responses we'll just assume no one is interested, with
> >> the
> >>>>> appropriate consequences.
> >>>>>
> >>>>> Keith
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: DRAGE, Keith (Keith)
> >>>>>> Sent: 27 February 2013 02:44
> >>>>>> To: insipid@ietf.org
> >>>>>> Subject: Call for working group adoption of identifier solution
> draft
> >>>>>>
> >>>>>> (As working group cochair)
> >>>>>>
> >>>>>> This is a call for the adoption of the text of the draft
> >>>>>>
> >>>>>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
> >>>>>>
> >>>>>> as a working group draft to meet the milestone
> >>>>>>
> >>>>>> Specification of the new identifier sent to the IESG (PS)
> >>>>>>
> >>>>>> Please respond as to whether the draft is acceptable or not. You
> may
> >>>>> also
> >>>>>> respond that certain parts are acceptable, or that parts are not
> >>>>>> acceptable (please be specific).
> >>>>>>
> >>>>>> This is currently the only text we have on the table to meet the
> >>>>> milestone
> >>>>>> and there seems to be some measure of convergence on this text at
> the
> >>>>>> Atlanta meeting.
> >>>>>>
> >>>>>> We will make a decision based on the responses received by Tuesday
> >> 12th
> >>>>>> March (i.e. Tuesday of the IETF meeting week).
> >>>>>>
> >>>>>> Regards
> >>>>>>
> >>>>>> Keith
> >>>> _______________________________________________
> >>>> insipid mailing list
> >>>> insipid@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/insipid
> >>> _______________________________________________
> >>> insipid mailing list
> >>> insipid@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/insipid
> >>>
> > _______________________________________________
> > insipid mailing list
> > insipid@ietf.org
> > https://www.ietf.org/mailman/listinfo/insipid
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid

From keith.drage@alcatel-lucent.com  Tue Mar 12 09:05:40 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFF911E80FA for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 09:05:40 -0700 (PDT)
X-Quarantine-ID: <OzYWAtXwcvk8>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...79FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>\n 
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzYWAtXwcvk8 for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 09:05:39 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 23C3411E80E8 for <insipid@ietf.org>; Tue, 12 Mar 2013 09:05:38 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r2CG5BvO012154 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <insipid@ietf.org>; Tue, 12 Mar 2013 17:05:37 +0100
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 12 Mar 2013 17:05:32 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 12 Mar 2013 17:05:30 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: Call for working group adoption of identifier solution draft
Thread-Index: Ac4UlDroba7PV9ffSRu5+JxUGGPxMACE8KGgAdbfH2AATcny0A==
Date: Tue, 12 Mar 2013 16:05:29 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B012255@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.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
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 16:05:40 -0000

(As WG cochair)

I'd like to declare working group consensus to adopt the current text of ht=
tp://www.ietf.org/id/draft-jones-insipid-session-id-02.txt as a working gro=
up draft, and I have asked Paul Jones to issue a working group draft of thi=
s.

All the major protagonists have explicitly spoken, and the chairs have rece=
ived no objections.

There have been some editorial changes identified in the discussion, and I =
have asked Paul to include these, but I have asked that technical changes a=
lready posted on the list are held to the next version, which we should see=
 shortly after the meeting, incorporating also any agreements we make from =
the face-to-face discussion (subject to no objections on list).

So the basis of discussion on Wednesday will be technically the same whethe=
r you are looking at the latest author draft or the new working group draft=
.

Keith

> -----Original Message-----
> From: DRAGE, Keith (Keith)
> Sent: 11 March 2013 02:54
> To: insipid@ietf.org
> Subject: RE: Call for working group adoption of identifier solution draft
>=20
> (As WG cochair)
>=20
> It would be nice to see a few more responses to this call (either way)
> before the deadline on Tuesday this week.
>=20
> If you are interested in the INSIPID work, and have not looked at the
> draft and responded, then please do so.
>=20
> Regards
>=20
> Keith
>=20
> > -----Original Message-----
> > From: DRAGE, Keith (Keith)
> > Sent: 01 March 2013 18:12
> > To: DRAGE, Keith (Keith); insipid@ietf.org
> > Subject: RE: Call for working group adoption of identifier solution
> draft
> >
> > (As WG cochair)
> >
> > I know the call has only been out a couple of days, but so far there ha=
s
> > been absolute silence on this.
> >
> > So this is to indicate that the chairs do need positive responses as
> well
> > as negative ones.
> >
> > If we get no responses we'll just assume no one is interested, with the
> > appropriate consequences.
> >
> > Keith
> >
> > > -----Original Message-----
> > > From: DRAGE, Keith (Keith)
> > > Sent: 27 February 2013 02:44
> > > To: insipid@ietf.org
> > > Subject: Call for working group adoption of identifier solution draft
> > >
> > > (As working group cochair)
> > >
> > > This is a call for the adoption of the text of the draft
> > >
> > > http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
> > >
> > > as a working group draft to meet the milestone
> > >
> > > Specification of the new identifier sent to the IESG (PS)
> > >
> > > Please respond as to whether the draft is acceptable or not. You may
> > also
> > > respond that certain parts are acceptable, or that parts are not
> > > acceptable (please be specific).
> > >
> > > This is currently the only text we have on the table to meet the
> > milestone
> > > and there seems to be some measure of convergence on this text at the
> > > Atlanta meeting.
> > >
> > > We will make a decision based on the responses received by Tuesday
> 12th
> > > March (i.e. Tuesday of the IETF meeting week).
> > >
> > > Regards
> > >
> > > Keith

From keith.drage@alcatel-lucent.com  Tue Mar 12 10:07:52 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AEAA11E80E2 for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 10:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPFsMoayGFh8 for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 10:07:51 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE6B11E80E1 for <insipid@ietf.org>; Tue, 12 Mar 2013 10:07:51 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r2CH7mpH015222 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <insipid@ietf.org>; Tue, 12 Mar 2013 18:07:48 +0100
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 12 Mar 2013 18:07:47 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 12 Mar 2013 18:07:47 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: Call for slides for Wednesdays meeting
Thread-Index: Ac4fRB3URB0vHIiSSGSGMcWjE/Hlkg==
Date: Tue, 12 Mar 2013 17:07:46 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0123E0@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
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: [Insipid] Call for slides for Wednesdays meeting
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 17:07:52 -0000

If possible could I request that you send slides to the chairs, preferably =
by last thing tonight (Tuesday), and at the latest by first thing tomorrow =
morning (Wednesday).

This gives the chairs a chance to get the slides on the meeting materials s=
ite, and allows remote participants to gain access prior to the start of th=
e meeting.

Keith

From internet-drafts@ietf.org  Tue Mar 12 10:20:48 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00F6721F8A5F; Tue, 12 Mar 2013 10:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x1uROckcJr-c; Tue, 12 Mar 2013 10:20:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C00C21F8697; Tue, 12 Mar 2013 10:20:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
Message-ID: <20130312172047.13581.56151.idtracker@ietfa.amsl.com>
Date: Tue, 12 Mar 2013 10:20:47 -0700
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-00.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 17:20:48 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 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
	Author(s)       : Paul E. Jones
                          Chris Pearce
                          James Polk
                          Gonzalo Salgueiro
	Filename        : draft-ietf-insipid-session-id-00.txt
	Pages           : 20
	Date            : 2013-03-12

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.


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-00


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


From paulej@packetizer.com  Tue Mar 12 10:24:00 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E57F1F0C74 for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 10:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.154
X-Spam-Level: 
X-Spam-Status: No, score=-2.154 tagged_above=-999 required=5 tests=[AWL=0.445,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKv-f4YNr5pA for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 10:23:58 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 94B7F1F0C6D for <insipid@ietf.org>; Tue, 12 Mar 2013 10:23:58 -0700 (PDT)
Received: from [130.129.20.212] (dhcp-14d4.meeting.ietf.org [130.129.20.212]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2CHNpxv020502 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 12 Mar 2013 13:23:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1363109036; bh=4oRvOSJm4oWJ7by80IVa2kwG6uLUKwxQPihv77/HdPM=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=O+JRFbJU28Q4hp2hnFjyin8xr1prWmqMMYuR/1LSwXEKU7pA8JPBo1U0iG+vSofzP 1otLIOMTuW1jVG4B0HFOvRHCU5MwOgEhRkp4Ds9GDNBHOnvYVQgl7YO+2msBtPD4GE PMeHIcII3DFBxlJxIVQ5XRzSxJtORVBnSPeLtXc4=
Message-ID: <513F64B5.6000806@packetizer.com>
Date: Tue, 12 Mar 2013 13:24:05 -0400
From: "Paul E. Jones" <paulej@packetizer.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE210702679FD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8B012255@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B012255@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Call for working group adoption of identifier solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 17:24:00 -0000

I posted the -00 draft.  I have the -01 text prepared already, but it 
may get revised further following this meeting, of course.  I'll send 
out the list of proposed technical changes to the list following the 
meeting.  Perhaps late this week or early next week.

Paul

On 3/12/2013 12:05 PM, DRAGE, Keith (Keith) wrote:
> (As WG cochair)
>
> I'd like to declare working group consensus to adopt the current text of http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt as a working group draft, and I have asked Paul Jones to issue a working group draft of this.
>
> All the major protagonists have explicitly spoken, and the chairs have received no objections.
>
> There have been some editorial changes identified in the discussion, and I have asked Paul to include these, but I have asked that technical changes already posted on the list are held to the next version, which we should see shortly after the meeting, incorporating also any agreements we make from the face-to-face discussion (subject to no objections on list).
>
> So the basis of discussion on Wednesday will be technically the same whether you are looking at the latest author draft or the new working group draft.
>
> Keith
>
>> -----Original Message-----
>> From: DRAGE, Keith (Keith)
>> Sent: 11 March 2013 02:54
>> To: insipid@ietf.org
>> Subject: RE: Call for working group adoption of identifier solution draft
>>
>> (As WG cochair)
>>
>> It would be nice to see a few more responses to this call (either way)
>> before the deadline on Tuesday this week.
>>
>> If you are interested in the INSIPID work, and have not looked at the
>> draft and responded, then please do so.
>>
>> Regards
>>
>> Keith
>>
>>> -----Original Message-----
>>> From: DRAGE, Keith (Keith)
>>> Sent: 01 March 2013 18:12
>>> To: DRAGE, Keith (Keith); insipid@ietf.org
>>> Subject: RE: Call for working group adoption of identifier solution
>> draft
>>> (As WG cochair)
>>>
>>> I know the call has only been out a couple of days, but so far there has
>>> been absolute silence on this.
>>>
>>> So this is to indicate that the chairs do need positive responses as
>> well
>>> as negative ones.
>>>
>>> If we get no responses we'll just assume no one is interested, with the
>>> appropriate consequences.
>>>
>>> Keith
>>>
>>>> -----Original Message-----
>>>> From: DRAGE, Keith (Keith)
>>>> Sent: 27 February 2013 02:44
>>>> To: insipid@ietf.org
>>>> Subject: Call for working group adoption of identifier solution draft
>>>>
>>>> (As working group cochair)
>>>>
>>>> This is a call for the adoption of the text of the draft
>>>>
>>>> http://www.ietf.org/id/draft-jones-insipid-session-id-02.txt
>>>>
>>>> as a working group draft to meet the milestone
>>>>
>>>> Specification of the new identifier sent to the IESG (PS)
>>>>
>>>> Please respond as to whether the draft is acceptable or not. You may
>>> also
>>>> respond that certain parts are acceptable, or that parts are not
>>>> acceptable (please be specific).
>>>>
>>>> This is currently the only text we have on the table to meet the
>>> milestone
>>>> and there seems to be some measure of convergence on this text at the
>>>> Atlanta meeting.
>>>>
>>>> We will make a decision based on the responses received by Tuesday
>> 12th
>>>> March (i.e. Tuesday of the IETF meeting week).
>>>>
>>>> Regards
>>>>
>>>> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From laura.liess.dt@googlemail.com  Tue Mar 12 14:21:14 2013
Return-Path: <laura.liess.dt@googlemail.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A787D11E80BA for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 14:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzDCaHeB71ON for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 14:21:13 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 2DBB721F8B6B for <insipid@ietf.org>; Tue, 12 Mar 2013 14:21:12 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id fj20so362837lab.6 for <insipid@ietf.org>; Tue, 12 Mar 2013 14:21:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=YvghqiRx8fDpa85ClsvVZxtOZxmxAoxrGM5D+Vgu8kU=; b=AM3id9IUr+DIDDTRgGgkqPJeNQ6a2RN0WWZhUaRPkcfDPT4TuI4SvZcff6LZizSUnd CaEjkzEs0GGvrHHmk70dd5bTybSft8WvQqcH8ve+W/NqzakvkCLWRms/R6w7Jv92k/lT 7Gv6Ms05CMmWyG5CJR18FuQKuLz/z5ht9oVzJSE4PCDodf9HXOzNSEOAzjscfqnt76mU CdBxHNzSe/gH5Kso957j8YwyYXdv2dc4btAWBh9e1NMvnLsTB5Yudfyu4pgVp11Uu08g LGGx51tiy1Pz+60uJqJFbDfLmWHp+ZnoWnv36S6/DZC452g7PKMV3hEueNJqaLi3d4Dp 6VLQ==
MIME-Version: 1.0
X-Received: by 10.152.125.239 with SMTP id mt15mr15369206lab.26.1363123272080;  Tue, 12 Mar 2013 14:21:12 -0700 (PDT)
Received: by 10.114.95.99 with HTTP; Tue, 12 Mar 2013 14:21:11 -0700 (PDT)
Date: Tue, 12 Mar 2013 22:21:11 +0100
Message-ID: <CACWXZj1kBdPqABYNYR+YuwW38HUeGFEKSfg1Wc-T_5qoGfD43A@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: Paul Jones <paulej@packetizer.com>
Content-Type: multipart/alternative; boundary=f46d04426b666ae19104d7c0de66
Cc: insipid@ietf.org
Subject: [Insipid] The value of the "local-uuid" to be inserted by SBCs
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 21:21:14 -0000

--f46d04426b666ae19104d7c0de66
Content-Type: text/plain; charset=ISO-8859-1

Paul,

I have a comment concerning folowing text in Section 7:


 If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a "local-uuid" value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a "remote" value that identifies the
   receiving UA, it MUST insert that value if also inserting the "local-
   uuid" value.

IMO the value of the of the local-uuid must be the hashed call-ID of
the incomming call leg.
Otherwise there is not possible for an external  monitoring device to
correlate both legs of a call  in case of a failure
of the receiving device ( the receiving device drops the call).

Thank you
Laura



2013/3/12 <internet-drafts@ietf.org>

>
> 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
>         Author(s)       : Paul E. Jones
>                           Chris Pearce
>                           James Polk
>                           Gonzalo Salgueiro
>         Filename        : draft-ietf-insipid-session-id-00.txt
>         Pages           : 20
>         Date            : 2013-03-12
>
> 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.
>
>
> 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-00
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>

--f46d04426b666ae19104d7c0de66
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<pre><span style=3D"font-family:arial narrow,sans-serif"><font><font>Paul<f=
ont>,<br></font></font></font></span></pre><pre><span style=3D"font-family:=
arial narrow,sans-serif"><font><font><font>I have a comment concerning folo=
wing text in Section 7:</font></font></font></span><br>
</pre><pre style=3D"margin-left:40px"><span style=3D"font-family:arial narr=
ow,sans-serif"></span></pre><pre style=3D"margin-left:80px"><span style=3D"=
font-family:arial narrow,sans-serif"><font><br> <font>If a SIP message havi=
ng no Session-ID header is received by an
   intermediary, the intermediary MAY assign a &quot;local-uuid&quot; value=
 to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a &quot;remote&quot; value that identifies the
   receiving UA, it MUST insert that value if also inserting the &quot;loca=
l-
   uuid&quot; value.<br></font></font></span></pre><pre><span style=3D"font=
-family:arial narrow,sans-serif"><font>IMO <font>the value of the of the lo=
cal-uu<font>id</font></font> must be the hashed call-ID <font>of the incomm=
ing call leg. <br>
Otherwise the<font>re is not possible for an external </font> monitoring de=
vice to correlate both legs of a call  in case of a failure<br><font>of the=
 receiving device ( the receiving device drops the call). <br><br><font>Tha=
nk you<br>
<font>Laura</font><br></font></font></font></font></span></pre><div style=
=3D"margin-left:40px"><span style=3D"font-family:arial narrow,sans-serif"><=
/span><br><span style=3D"font-family:arial narrow,sans-serif"></span></div>=
<br>
<div class=3D"gmail_quote">2013/3/12  <span dir=3D"ltr">&lt;<a href=3D"mail=
to:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>=
&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the INtermediary-safe SIP session ID Workin=
g Group of the IETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : End-to-End Session Identificati=
on in IP-Based Multimedia Communication Networks<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Paul E. Jones<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Chris Pearce<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 James Polk<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Gonzalo Salgueiro<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-insipid-session-id-00.=
txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 20<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-03-12<br>
<br>
Abstract:<br>
=A0 =A0This document describes an end-to-end Session Identifier for use in<=
br>
=A0 =A0IP-based Multimedia Communication systems that enables endpoints,<br=
>
=A0 =A0intermediate devices, and management systems to identify a session<b=
r>
=A0 =A0end-to-end, associate multiple endpoints with a given multipoint<br>
=A0 =A0conference, track communication sessions when they are redirected,<b=
r>
=A0 =A0and associate one or more media flows with a given communication<br>
=A0 =A0session.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<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-sessi=
on-id</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-insipid-session-id-00" tar=
get=3D"_blank">http://tools.ietf.org/html/draft-ietf-insipid-session-id-00<=
/a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
insipid mailing list<br>
<a href=3D"mailto:insipid@ietf.org" target=3D"_blank">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>

--f46d04426b666ae19104d7c0de66--

From paulej@packetizer.com  Tue Mar 12 14:49:41 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC8921F89FC for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 14:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[AWL=-0.334, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_HEAD=1.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uLyHANKEyFiN for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 14:49:40 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8CD21F89CB for <insipid@ietf.org>; Tue, 12 Mar 2013 14:49:37 -0700 (PDT)
Received: from dhcp-15f5.meeting.ietf.org (dhcp-15f5.meeting.ietf.org [130.129.21.245]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2CLnYxU002287 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 12 Mar 2013 17:49:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1363124975; bh=Ou6tJySJuNLz2/WZSNp+k06P1qwKszR5Pn3ag7ZTXFc=; h=In-Reply-To:References:MIME-Version:Content-Type:Subject:From: Date:To:CC:Message-ID; b=oBxs6SppqwguxcyqeVrN3XLHbROlN/EV/5t1IyjPUtR92CaRlq763BKWjhki+O7S4 1yevBmkJD+40NZ69Wb+R+3h2OMCvRMVExSiAA1yifNCmYSNzuU1EbIsE5dky8UWde9 XSpfruyPm85gpiefZ4QdHKl6VckeNjOmlMR/tIMs=
User-Agent: K-9 Mail for Android
In-Reply-To: <CACWXZj1kBdPqABYNYR+YuwW38HUeGFEKSfg1Wc-T_5qoGfD43A@mail.gmail.com>
References: <CACWXZj1kBdPqABYNYR+YuwW38HUeGFEKSfg1Wc-T_5qoGfD43A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----GFD2BYXSKWFX5V53PABHPQ0JTEUT14"
From: "Paul E. Jones" <paulej@packetizer.com>
Date: Tue, 12 Mar 2013 17:49:32 -0400
To: Laura Liess <laura.liess.dt@googlemail.com>
Message-ID: <ac3e2963-f838-48e4-9a9c-f74f7b6e5408@email.android.com>
Cc: insipid@ietf.org
Subject: Re: [Insipid] The value of the "local-uuid" to be inserted by SBCs
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 21:49:41 -0000

------GFD2BYXSKWFX5V53PABHPQ0JTEUT14
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

Laura,

That would be a good idea. RFC 4122 allows for an SHA-1 hash to be used, for example. If we reserved that UUID type for this scenario, we could also tell the value was fabricated by a middle box. Other versions (like v4 - random values) could be used by endpoints that generate their own values.

We need to define the exact usage of UUIDs, of course. I like your idea.

Paul


-------- Original Message --------
From: Laura Liess <laura.liess.dt@googlemail.com>
Sent: Tue Mar 12 17:21:11 EDT 2013
To: Paul Jones <paulej@packetizer.com>
Cc: insipid@ietf.org
Subject: The value of the "local-uuid" to be inserted by SBCs

Paul,

I have a comment concerning folowing text in Section 7:


 If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a "local-uuid" value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a "remote" value that identifies the
   receiving UA, it MUST insert that value if also inserting the "local-
   uuid" value.

IMO the value of the of the local-uuid must be the hashed call-ID of
the incomming call leg.
Otherwise there is not possible for an external  monitoring device to
correlate both legs of a call  in case of a failure
of the receiving device ( the receiving device drops the call).

Thank you
Laura



2013/3/12 <internet-drafts@ietf.org>

>
> 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
>         Author(s)       : Paul E. Jones
>                           Chris Pearce
>                           James Polk
>                           Gonzalo Salgueiro
>         Filename        : draft-ietf-insipid-session-id-00.txt
>         Pages           : 20
>         Date            : 2013-03-12
>
> 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.
>
>
> 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-00
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>

------GFD2BYXSKWFX5V53PABHPQ0JTEUT14
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head/><body><html><head></head><body>Laura,<br>
<br>
That would be a good idea. RFC 4122 allows for an SHA-1 hash to be used, for example. If we reserved that UUID type for this scenario, we could also tell the value was fabricated by a middle box. Other versions (like v4 - random values) could be used by endpoints that generate their own values.<br>
<br>
We need to define the exact usage of UUIDs, of course. I like your idea.<br>
<br>
Paul<br><br><div style='font-size:10.0pt;font-family:"Tahoma","sans-serif";padding:3.0pt 0in 0in 0in'>
<hr style='border:none;border-top:solid #B5C4DF 1.0pt'>
<b>From:</b> Laura Liess &lt;laura.liess.dt@googlemail.com&gt;<br>
<b>Sent:</b> Tue Mar 12 17:21:11 EDT 2013<br>
<b>To:</b> Paul Jones &lt;paulej@packetizer.com&gt;<br>
<b>Cc:</b> insipid@ietf.org<br>
<b>Subject:</b> The value of the &quot;local-uuid&quot; to be inserted by SBCs<br>
</div>
<br>
<pre><span style="font-family:arial narrow,sans-serif"><font><font>Paul<font>,<br /></font></font></font></span></pre><pre><span style="font-family:arial narrow,sans-serif"><font><font><font>I have a comment concerning folowing text in Section 7:</font></font></font></span><br />
</pre><pre style="margin-left:40px"><span style="font-family:arial narrow,sans-serif"></span></pre><pre style="margin-left:80px"><span style="font-family:arial narrow,sans-serif"><font><br /> <font>If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a &quot;local-uuid&quot; value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a &quot;remote&quot; value that identifies the
   receiving UA, it MUST insert that value if also inserting the &quot;local-
   uuid&quot; value.<br /></font></font></span></pre><pre><span style="font-family:arial narrow,sans-serif"><font>IMO <font>the value of the of the local-uu<font>id</font></font> must be the hashed call-ID <font>of the incomming call leg. <br />
Otherwise the<font>re is not possible for an external </font> monitoring device to correlate both legs of a call  in case of a failure<br /><font>of the receiving device ( the receiving device drops the call). <br /><br /><font>Thank you<br />
<font>Laura</font><br /></font></font></font></font></span></pre><div style="margin-left:40px"><span style="font-family:arial narrow,sans-serif"></span><br /><span style="font-family:arial narrow,sans-serif"></span></div><br />
<div class="gmail_quote">2013/3/12  <span dir="ltr">&lt;<a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a>&gt;</span><br />
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br />
A New Internet-Draft is available from the on-line Internet-Drafts directories.<br />
 This draft is a work item of the INtermediary-safe SIP session ID Working Group of the IETF.<br />
<br />
        Title           : End-to-End Session Identification in IP-Based Multimedia Communication Networks<br />
        Author(s)       : Paul E. Jones<br />
                          Chris Pearce<br />
                          James Polk<br />
                          Gonzalo Salgueiro<br />
        Filename        : draft-ietf-insipid-session-id-00.txt<br />
        Pages           : 20<br />
        Date            : 2013-03-12<br />
<br />
Abstract:<br />
   This document describes an end-to-end Session Identifier for use in<br />
   IP-based Multimedia Communication systems that enables endpoints,<br />
   intermediate devices, and management systems to identify a session<br />
   end-to-end, associate multiple endpoints with a given multipoint<br />
   conference, track communication sessions when they are redirected,<br />
   and associate one or more media flows with a given communication<br />
   session.<br />
<br />
<br />
The IETF datatracker status page for this draft is:<br />
<a href="https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id</a><br />
<br />
There&#39;s also a htmlized version available at:<br />
<a href="http://tools.ietf.org/html/draft-ietf-insipid-session-id-00" target="_blank">http://tools.ietf.org/html/draft-ietf-insipid-session-id-00</a><br />
<br />
<br />
Internet-Drafts are also available by anonymous FTP at:<br />
<a href="ftp://ftp.ietf.org/internet-drafts/" target="_blank">ftp://ftp.ietf.org/internet-drafts/</a><br />
<br />
_______________________________________________<br />
insipid mailing list<br />
<a href="mailto:insipid@ietf.org" target="_blank">insipid@ietf.org</a><br />
<a href="https://www.ietf.org/mailman/listinfo/insipid" target="_blank">https://www.ietf.org/mailman/listinfo/insipid</a><br />
</blockquote></div><br />
</body></html></body></html>
------GFD2BYXSKWFX5V53PABHPQ0JTEUT14--


From gsalguei@cisco.com  Tue Mar 12 22:17:01 2013
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8206B21F8DC1 for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 22:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKXYuTAZ0ict for <insipid@ietfa.amsl.com>; Tue, 12 Mar 2013 22:17:00 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id A021921F8DC0 for <insipid@ietf.org>; Tue, 12 Mar 2013 22:17:00 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r2D5H0g6019306 for <insipid@ietf.org>; Wed, 13 Mar 2013 01:17:00 -0400 (EDT)
Received: from rtp-vpn5-1507.cisco.com (rtp-vpn5-1507.cisco.com [10.82.237.232]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r2D5GuEL027105 for <insipid@ietf.org>; Wed, 13 Mar 2013 01:16:59 -0400 (EDT)
From: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <193A747F-41C7-4E06-9F25-559E1962FBE5@cisco.com>
Date: Wed, 13 Mar 2013 01:16:54 -0400
To: "insipid@ietf.org" <insipid@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [Insipid] INSIPID Meeting Materials Uploaded
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Mar 2013 05:17:01 -0000

INSIPID WG - 

The slides for the INSIPID meeting tomorrow have been posted.

Gonzalo & Keith


From btv1==784b8d51794==HKaplan@acmepacket.com  Wed Mar 13 13:36:27 2013
Return-Path: <btv1==784b8d51794==HKaplan@acmepacket.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE08721F8D5B for <insipid@ietfa.amsl.com>; Wed, 13 Mar 2013 13:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.522
X-Spam-Level: 
X-Spam-Status: No, score=-3.522 tagged_above=-999 required=5 tests=[AWL=1.077,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtw9jnkw4dnR for <insipid@ietfa.amsl.com>; Wed, 13 Mar 2013 13:36:26 -0700 (PDT)
Received: from mx2.acmepacket.com (mx2.acmepacket.com [216.41.24.99]) by ietfa.amsl.com (Postfix) with ESMTP id BE47C21F8ABC for <insipid@ietf.org>; Wed, 13 Mar 2013 13:36:26 -0700 (PDT)
X-ASG-Debug-ID: 1363206985-03fc217260f3fcc0001-Waf2p9
Received: from Mail1.acmepacket.com (mail1.acmepacket.com [10.0.0.21]) by mx2.acmepacket.com with ESMTP id oE2ss3PMAzR3Jj9M (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for <insipid@ietf.org>; Wed, 13 Mar 2013 16:36:25 -0400 (EDT)
X-Barracuda-Envelope-From: HKaplan@acmepacket.com
Received: from MAIL2.acmepacket.com ([169.254.2.222]) by Mail1.acmepacket.com ([169.254.1.130]) with mapi id 14.02.0283.003; Wed, 13 Mar 2013 16:36:25 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: publishing draft-kaplan session-id as historic
X-ASG-Orig-Subj: publishing draft-kaplan session-id as historic
Thread-Index: AQHOICpux5bkfvRMbE+xoibi4zwbMA==
Date: Wed, 13 Mar 2013 20:36:24 +0000
Message-ID: <A4783B9E-AEED-454A-8530-6E5C3BEAC047@acmepacket.com>
References: <7F2072F1E0DE894DA4B517B93C6A05853408683664@ESESSCMS0356.eemea.ericsson.se> <EEDB748C-2DAC-4B8A-BB94-6D6DE37CEB1C@acmepacket.com>
In-Reply-To: <EEDB748C-2DAC-4B8A-BB94-6D6DE37CEB1C@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <62BCB99AF7469F4D8D405CBDFF10EDBF@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: mail1.acmepacket.com[10.0.0.21]
X-Barracuda-Start-Time: 1363206985
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://216.41.24.99:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at acmepacket.com
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.125115 Rule breakdown below pts rule name              description ---- ---------------------- --------------------------------------------------
Subject: [Insipid] publishing draft-kaplan session-id as historic
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Mar 2013 20:36:57 -0000

>From today's meeting action I took... below was the email.
The difference between draft-kaplan-dispatch-session-id-03 and 02 can be se=
en here:

http://tools.ietf.org/rfcdiff?url2=3Ddraft-kaplan-dispatch-session-id-03.tx=
t

It did not change the ABNF nor protocol rules.  Therefore I propose to subm=
it 03 as independent submission to the RFC Editor, for 'Historic' status.  =
Or 'Epic' status if they have that. :)

-hadriel


On Aug 17, 2012, at 1:47 PM, Hadriel Kaplan <HKaplan@acmepacket.com> wrote:

>=20
> When we talked about this in Vancouver I was thinking there wouldn't be a=
ny problem going to/from UUID syntax, because going to/from UUIDs in H.323 =
was talked about a long, long time ago for session-id.  But I forgot about =
the bug in the draft-kaplan ABNF...
>=20
> Since version 01 of draft-kaplan-sip-session-id in 2008, which later beca=
me draft-kaplan-dispatch-session-id, the rules for generating the session-i=
d always made it lower-case *hex* characters.  I.e., the g-z range wasn't a=
ctually possible.  The ABNF for it didn't get fixed until draft-kaplan-disp=
atch-session-id-01 in April 2010, but that also dropped it to 16 characters=
 of hex because the algorithm changed, and then 3 months later reverted bac=
k to 32 characters and the correct ABNF.
>=20
> So that begs the question of *which* version of draft-kaplan we want to b=
e backwards compatible with.  Since draft-kaplan-dispatch-session-id-01 onl=
y existed for 3 months, I think we can ignore that one.  And since everythi=
ng else only used hex characters, except the initial 00-draft which itself =
only existed for 4 months, I think we can ignore that one too.
>=20
> Therefore, as far as I can tell we shouldn't have a problem converting dr=
aft-kaplan session-ids to/from UUIDs for H.323/whatever.
>=20
> -hadriel
>=20
>=20
> On Aug 14, 2012, at 4:27 PM, Christer Holmberg wrote:
>=20
>> Hi,
>>=20
>> In Vancouver, I expressed a wish to make the INSIPID mechanism backward =
compatible with the draft-kaplan-session-id one, the reason being that it h=
as been around for a relatively long time, and has been implemented and dep=
loyed.
>>=20
>> I compared the suggested draft-jones solution with the draft-kaplan solu=
tion, and I think there are ways to achieve backward compability.
>>=20
>>=20
>> --------------
>>=20
>>=20
>> FIRST, looking purely at the ABNF syntax:
>>=20
>> The jones ABNF is:
>>=20
>>=20
>> Session-ID-UUID =3D "Session-ID-UUID" HCOLON UUID
>>=20
>>=20
>>=20
>> The kaplan ABNF is:
>>=20
>>=20
>>=20
>> Session-ID           =3D  "Session-ID" HCOLON sess-id
>>=20
>>                          *( SEMI generic-param )
>>=20
>> sess-id              =3D  32(DIGIT / %x61-7A)  ; 32 chars of [0-9a-z]
>>=20
>>=20
>>=20
>>=20
>>=20
>> Now, assuming 32 chars is enough to carry ONE UUID, jones applications c=
ould put the SECOND UUID in a header field parameter (generic-param), rathe=
r than combining it with the received UUID.
>>=20
>>=20
>>=20
>> Of course, the first UUDI (carried in sess-id) can only contains charact=
ers 0-9 and a-z.
>>=20
>>=20
>>=20
>> A UUID can contain characters 0-9 and a-f and A-F.
>>=20
>>=20
>>=20
>> So, a jones entity would have to be prepared to receive g-z.
>>=20
>>=20
>>=20
>> And, as kaplan entity is not prepared to receive capital A-F, a jones en=
tity would have to only use small letters. But, that should not be a proble=
m, afaik, as they have the same meaning as far as UUID is concerned.
>>=20
>>=20
>>=20
>> --------------
>>=20
>>=20
>>=20
>> SECOND, looking at it would work functionwise:
>>=20
>>=20
>>=20
>> There are two main alternatives:
>>=20
>>=20
>>=20
>>=20
>>=20
>> 1. Second UUID is added even when one entity is kaplan compliant
>>=20
>> 2. Second UUID is not added when one entity is kaplan compliant
>>=20
>>=20
>>=20
>>=20
>>=20
>> Alternative 1:
>>=20
>>=20
>>=20
>> When a kaplan entity inserts the first UUID (I use that as a general ter=
m, eventhough a kaplan entity does not use UUIDs), one must assume that it =
is prepared to receive a response from a jones entity which has added the s=
econd UUID into the header field parameter.
>>=20
>>=20
>>=20
>> When a jones entity inserts the first UUID, one must assume that it is p=
repared to receive a response from a kaplan entity where the second UUID ha=
s *not* been added.
>>=20
>>=20
>>=20
>>=20
>>=20
>> Alternative 2:
>>=20
>>=20
>>=20
>> When a kaplan entity inserts the first UUID, the jones entity detects (u=
sing some identify-a-kaplan-entity mechanism) that it comes from a kaplan e=
ntity, so it does not insert a seoncd UUID in the first place.
>>=20
>>=20
>>=20
>> As in alternative 1, when a jones entity inserts the first UUID, it has =
to be prepared to receive a response where the second UUID has not been add=
ed (the identify-a-kaplan-entity mechanism might also inform the jones enti=
ty that the response comes from a kaplan entity.
>>=20
>>=20
>>=20
>>=20
>>=20
>> --------------
>>=20
>>=20
>>=20
>> Now, there will of course be cases, where two UUIDs are required, that w=
on't work. But, kaplan entities would be able to use the session-id for wha=
tever they've used it so far.
>>=20
>>=20
>>=20
>>=20
>>=20
>> Regards,
>>=20
>>=20
>>=20
>> Christer
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From rjsparks@nostrum.com  Wed Mar 13 14:04:48 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59ED121F870F for <insipid@ietfa.amsl.com>; Wed, 13 Mar 2013 14:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.6
X-Spam-Level: 
X-Spam-Status: No, score=-103.6 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVjVa8zntWAP for <insipid@ietfa.amsl.com>; Wed, 13 Mar 2013 14:04:47 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4F05421F8706 for <insipid@ietf.org>; Wed, 13 Mar 2013 14:04:47 -0700 (PDT)
Received: from dhcp-5232.meeting.ietf.org (dhcp-5232.meeting.ietf.org [130.129.82.50]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r2DL4k8X075390 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <insipid@ietf.org>; Wed, 13 Mar 2013 16:04:46 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5140E9ED.5060206@nostrum.com>
Date: Wed, 13 Mar 2013 17:04:45 -0400
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: insipid@ietf.org
References: <7F2072F1E0DE894DA4B517B93C6A05853408683664@ESESSCMS0356.eemea.ericsson.se> <EEDB748C-2DAC-4B8A-BB94-6D6DE37CEB1C@acmepacket.com> <A4783B9E-AEED-454A-8530-6E5C3BEAC047@acmepacket.com>
In-Reply-To: <A4783B9E-AEED-454A-8530-6E5C3BEAC047@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 130.129.82.50 is authenticated by a trusted mechanism)
Subject: Re: [Insipid] publishing draft-kaplan session-id as historic
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Mar 2013 21:04:48 -0000

On 3/13/13 4:36 PM, Hadriel Kaplan wrote:
>  From today's meeting action I took... below was the email.
> The difference between draft-kaplan-dispatch-session-id-03 and 02 can be seen here:
>
> http://tools.ietf.org/rfcdiff?url2=draft-kaplan-dispatch-session-id-03.txt
>
> It did not change the ABNF nor protocol rules.  Therefore I propose to submit 03 as independent submission to the RFC Editor, for 'Historic' status.  Or 'Epic' status if they have that. :)
It wouldn't be -03 as is - there needs to be an editing pass explaining 
this document's this is a proprietary something that may be in the wild. 
The text should be touched to make it an exposition (This is what you 
would have seen) vs a specification (this is what you should do).

RjS

>
> -hadriel
>
>
> On Aug 17, 2012, at 1:47 PM, Hadriel Kaplan <HKaplan@acmepacket.com> wrote:
>
>> When we talked about this in Vancouver I was thinking there wouldn't be any problem going to/from UUID syntax, because going to/from UUIDs in H.323 was talked about a long, long time ago for session-id.  But I forgot about the bug in the draft-kaplan ABNF...
>>
>> Since version 01 of draft-kaplan-sip-session-id in 2008, which later became draft-kaplan-dispatch-session-id, the rules for generating the session-id always made it lower-case *hex* characters.  I.e., the g-z range wasn't actually possible.  The ABNF for it didn't get fixed until draft-kaplan-dispatch-session-id-01 in April 2010, but that also dropped it to 16 characters of hex because the algorithm changed, and then 3 months later reverted back to 32 characters and the correct ABNF.
>>
>> So that begs the question of *which* version of draft-kaplan we want to be backwards compatible with.  Since draft-kaplan-dispatch-session-id-01 only existed for 3 months, I think we can ignore that one.  And since everything else only used hex characters, except the initial 00-draft which itself only existed for 4 months, I think we can ignore that one too.
>>
>> Therefore, as far as I can tell we shouldn't have a problem converting draft-kaplan session-ids to/from UUIDs for H.323/whatever.
>>
>> -hadriel
>>
>>
>> On Aug 14, 2012, at 4:27 PM, Christer Holmberg wrote:
>>
>>> Hi,
>>>
>>> In Vancouver, I expressed a wish to make the INSIPID mechanism backward compatible with the draft-kaplan-session-id one, the reason being that it has been around for a relatively long time, and has been implemented and deployed.
>>>
>>> I compared the suggested draft-jones solution with the draft-kaplan solution, and I think there are ways to achieve backward compability.
>>>
>>>
>>> --------------
>>>
>>>
>>> FIRST, looking purely at the ABNF syntax:
>>>
>>> The jones ABNF is:
>>>
>>>
>>> Session-ID-UUID = "Session-ID-UUID" HCOLON UUID
>>>
>>>
>>>
>>> The kaplan ABNF is:
>>>
>>>
>>>
>>> Session-ID           =  "Session-ID" HCOLON sess-id
>>>
>>>                           *( SEMI generic-param )
>>>
>>> sess-id              =  32(DIGIT / %x61-7A)  ; 32 chars of [0-9a-z]
>>>
>>>
>>>
>>>
>>>
>>> Now, assuming 32 chars is enough to carry ONE UUID, jones applications could put the SECOND UUID in a header field parameter (generic-param), rather than combining it with the received UUID.
>>>
>>>
>>>
>>> Of course, the first UUDI (carried in sess-id) can only contains characters 0-9 and a-z.
>>>
>>>
>>>
>>> A UUID can contain characters 0-9 and a-f and A-F.
>>>
>>>
>>>
>>> So, a jones entity would have to be prepared to receive g-z.
>>>
>>>
>>>
>>> And, as kaplan entity is not prepared to receive capital A-F, a jones entity would have to only use small letters. But, that should not be a problem, afaik, as they have the same meaning as far as UUID is concerned.
>>>
>>>
>>>
>>> --------------
>>>
>>>
>>>
>>> SECOND, looking at it would work functionwise:
>>>
>>>
>>>
>>> There are two main alternatives:
>>>
>>>
>>>
>>>
>>>
>>> 1. Second UUID is added even when one entity is kaplan compliant
>>>
>>> 2. Second UUID is not added when one entity is kaplan compliant
>>>
>>>
>>>
>>>
>>>
>>> Alternative 1:
>>>
>>>
>>>
>>> When a kaplan entity inserts the first UUID (I use that as a general term, eventhough a kaplan entity does not use UUIDs), one must assume that it is prepared to receive a response from a jones entity which has added the second UUID into the header field parameter.
>>>
>>>
>>>
>>> When a jones entity inserts the first UUID, one must assume that it is prepared to receive a response from a kaplan entity where the second UUID has *not* been added.
>>>
>>>
>>>
>>>
>>>
>>> Alternative 2:
>>>
>>>
>>>
>>> When a kaplan entity inserts the first UUID, the jones entity detects (using some identify-a-kaplan-entity mechanism) that it comes from a kaplan entity, so it does not insert a seoncd UUID in the first place.
>>>
>>>
>>>
>>> As in alternative 1, when a jones entity inserts the first UUID, it has to be prepared to receive a response where the second UUID has not been added (the identify-a-kaplan-entity mechanism might also inform the jones entity that the response comes from a kaplan entity.
>>>
>>>
>>>
>>>
>>>
>>> --------------
>>>
>>>
>>>
>>> Now, there will of course be cases, where two UUIDs are required, that won't work. But, kaplan entities would be able to use the session-id for whatever they've used it so far.
>>>
>>>
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>
>>> Christer
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> insipid mailing list
>>> insipid@ietf.org
>>> https://www.ietf.org/mailman/listinfo/insipid
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From btv1==784b8d51794==HKaplan@acmepacket.com  Wed Mar 13 15:43:48 2013
Return-Path: <btv1==784b8d51794==HKaplan@acmepacket.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56CD221F86C2 for <insipid@ietfa.amsl.com>; Wed, 13 Mar 2013 15:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.614
X-Spam-Level: 
X-Spam-Status: No, score=-3.614 tagged_above=-999 required=5 tests=[AWL=0.985,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgNyojXFs9Iu for <insipid@ietfa.amsl.com>; Wed, 13 Mar 2013 15:43:46 -0700 (PDT)
Received: from mx1.acmepacket.com (mx1.acmepacket.com [216.41.24.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7EBBE21F8614 for <insipid@ietf.org>; Wed, 13 Mar 2013 15:43:46 -0700 (PDT)
X-ASG-Debug-ID: 1363214625-03fc200f25558490001-Waf2p9
Received: from Mail1.acmepacket.com (mail1.acmepacket.com [10.0.0.21]) by mx1.acmepacket.com with ESMTP id NYUwZpoTNcNFFezN (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Wed, 13 Mar 2013 18:43:45 -0400 (EDT)
X-Barracuda-Envelope-From: HKaplan@acmepacket.com
Received: from MAIL2.acmepacket.com ([169.254.2.222]) by Mail1.acmepacket.com ([169.254.1.130]) with mapi id 14.02.0283.003; Wed, 13 Mar 2013 18:43:45 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [Insipid] publishing draft-kaplan session-id as historic
X-ASG-Orig-Subj: Re: [Insipid] publishing draft-kaplan session-id as historic
Thread-Index: AQHOIDw3D/Lw37+nlUOfmGw4zhPOkg==
Date: Wed, 13 Mar 2013 22:43:44 +0000
Message-ID: <919553E8-D8AB-4B56-A68D-1AF46A5B72C3@acmepacket.com>
References: <7F2072F1E0DE894DA4B517B93C6A05853408683664@ESESSCMS0356.eemea.ericsson.se> <EEDB748C-2DAC-4B8A-BB94-6D6DE37CEB1C@acmepacket.com> <A4783B9E-AEED-454A-8530-6E5C3BEAC047@acmepacket.com> <5140E9ED.5060206@nostrum.com>
In-Reply-To: <5140E9ED.5060206@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F102B93868E1554FBF2F26F47BF12AE8@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: mail1.acmepacket.com[10.0.0.21]
X-Barracuda-Start-Time: 1363214625
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://spam.acmepacket.com:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at acmepacket.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.125123 Rule breakdown below pts rule name              description ---- ---------------------- --------------------------------------------------
Cc: "<insipid@ietf.org>" <insipid@ietf.org>
Subject: Re: [Insipid] publishing draft-kaplan session-id as historic
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Mar 2013 22:43:48 -0000

Yes sorry I should have been clearer - I realize I'll have to edit the doc =
to actually submit, I just meant using 03 as the version vs. 02 or 01 or wh=
atever.

-hadriel


On Mar 13, 2013, at 5:04 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> On 3/13/13 4:36 PM, Hadriel Kaplan wrote:
>> From today's meeting action I took... below was the email.
>> The difference between draft-kaplan-dispatch-session-id-03 and 02 can be=
 seen here:
>>=20
>> http://tools.ietf.org/rfcdiff?url2=3Ddraft-kaplan-dispatch-session-id-03=
.txt
>>=20
>> It did not change the ABNF nor protocol rules.  Therefore I propose to s=
ubmit 03 as independent submission to the RFC Editor, for 'Historic' status=
.  Or 'Epic' status if they have that. :)
> It wouldn't be -03 as is - there needs to be an editing pass explaining t=
his document's this is a proprietary something that may be in the wild. The=
 text should be touched to make it an exposition (This is what you would ha=
ve seen) vs a specification (this is what you should do).
>=20
> RjS
>=20
>>=20
>> -hadriel
>>=20
>>=20
>> On Aug 17, 2012, at 1:47 PM, Hadriel Kaplan <HKaplan@acmepacket.com> wro=
te:
>>=20
>>> When we talked about this in Vancouver I was thinking there wouldn't be=
 any problem going to/from UUID syntax, because going to/from UUIDs in H.32=
3 was talked about a long, long time ago for session-id.  But I forgot abou=
t the bug in the draft-kaplan ABNF...
>>>=20
>>> Since version 01 of draft-kaplan-sip-session-id in 2008, which later be=
came draft-kaplan-dispatch-session-id, the rules for generating the session=
-id always made it lower-case *hex* characters.  I.e., the g-z range wasn't=
 actually possible.  The ABNF for it didn't get fixed until draft-kaplan-di=
spatch-session-id-01 in April 2010, but that also dropped it to 16 characte=
rs of hex because the algorithm changed, and then 3 months later reverted b=
ack to 32 characters and the correct ABNF.
>>>=20
>>> So that begs the question of *which* version of draft-kaplan we want to=
 be backwards compatible with.  Since draft-kaplan-dispatch-session-id-01 o=
nly existed for 3 months, I think we can ignore that one.  And since everyt=
hing else only used hex characters, except the initial 00-draft which itsel=
f only existed for 4 months, I think we can ignore that one too.
>>>=20
>>> Therefore, as far as I can tell we shouldn't have a problem converting =
draft-kaplan session-ids to/from UUIDs for H.323/whatever.
>>>=20
>>> -hadriel
>>>=20
>>>=20
>>> On Aug 14, 2012, at 4:27 PM, Christer Holmberg wrote:
>>>=20
>>>> Hi,
>>>>=20
>>>> In Vancouver, I expressed a wish to make the INSIPID mechanism backwar=
d compatible with the draft-kaplan-session-id one, the reason being that it=
 has been around for a relatively long time, and has been implemented and d=
eployed.
>>>>=20
>>>> I compared the suggested draft-jones solution with the draft-kaplan so=
lution, and I think there are ways to achieve backward compability.
>>>>=20
>>>>=20
>>>> --------------
>>>>=20
>>>>=20
>>>> FIRST, looking purely at the ABNF syntax:
>>>>=20
>>>> The jones ABNF is:
>>>>=20
>>>>=20
>>>> Session-ID-UUID =3D "Session-ID-UUID" HCOLON UUID
>>>>=20
>>>>=20
>>>>=20
>>>> The kaplan ABNF is:
>>>>=20
>>>>=20
>>>>=20
>>>> Session-ID           =3D  "Session-ID" HCOLON sess-id
>>>>=20
>>>>                          *( SEMI generic-param )
>>>>=20
>>>> sess-id              =3D  32(DIGIT / %x61-7A)  ; 32 chars of [0-9a-z]
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Now, assuming 32 chars is enough to carry ONE UUID, jones applications=
 could put the SECOND UUID in a header field parameter (generic-param), rat=
her than combining it with the received UUID.
>>>>=20
>>>>=20
>>>>=20
>>>> Of course, the first UUDI (carried in sess-id) can only contains chara=
cters 0-9 and a-z.
>>>>=20
>>>>=20
>>>>=20
>>>> A UUID can contain characters 0-9 and a-f and A-F.
>>>>=20
>>>>=20
>>>>=20
>>>> So, a jones entity would have to be prepared to receive g-z.
>>>>=20
>>>>=20
>>>>=20
>>>> And, as kaplan entity is not prepared to receive capital A-F, a jones =
entity would have to only use small letters. But, that should not be a prob=
lem, afaik, as they have the same meaning as far as UUID is concerned.
>>>>=20
>>>>=20
>>>>=20
>>>> --------------
>>>>=20
>>>>=20
>>>>=20
>>>> SECOND, looking at it would work functionwise:
>>>>=20
>>>>=20
>>>>=20
>>>> There are two main alternatives:
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> 1. Second UUID is added even when one entity is kaplan compliant
>>>>=20
>>>> 2. Second UUID is not added when one entity is kaplan compliant
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Alternative 1:
>>>>=20
>>>>=20
>>>>=20
>>>> When a kaplan entity inserts the first UUID (I use that as a general t=
erm, eventhough a kaplan entity does not use UUIDs), one must assume that i=
t is prepared to receive a response from a jones entity which has added the=
 second UUID into the header field parameter.
>>>>=20
>>>>=20
>>>>=20
>>>> When a jones entity inserts the first UUID, one must assume that it is=
 prepared to receive a response from a kaplan entity where the second UUID =
has *not* been added.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Alternative 2:
>>>>=20
>>>>=20
>>>>=20
>>>> When a kaplan entity inserts the first UUID, the jones entity detects =
(using some identify-a-kaplan-entity mechanism) that it comes from a kaplan=
 entity, so it does not insert a seoncd UUID in the first place.
>>>>=20
>>>>=20
>>>>=20
>>>> As in alternative 1, when a jones entity inserts the first UUID, it ha=
s to be prepared to receive a response where the second UUID has not been a=
dded (the identify-a-kaplan-entity mechanism might also inform the jones en=
tity that the response comes from a kaplan entity.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> --------------
>>>>=20
>>>>=20
>>>>=20
>>>> Now, there will of course be cases, where two UUIDs are required, that=
 won't work. But, kaplan entities would be able to use the session-id for w=
hatever they've used it so far.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Regards,
>>>>=20
>>>>=20
>>>>=20
>>>> Christer
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> insipid mailing list
>>>> insipid@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/insipid
>>> _______________________________________________
>>> insipid mailing list
>>> insipid@ietf.org
>>> https://www.ietf.org/mailman/listinfo/insipid
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From paulej@packetizer.com  Thu Mar 21 18:52:18 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A34E21F872E for <insipid@ietfa.amsl.com>; Thu, 21 Mar 2013 18:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dApzT2kUxK3 for <insipid@ietfa.amsl.com>; Thu, 21 Mar 2013 18:52:17 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1E021F8B4C for <insipid@ietf.org>; Thu, 21 Mar 2013 18:52:14 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2M1qAYw004468 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <insipid@ietf.org>; Thu, 21 Mar 2013 21:52:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1363917132; bh=RUT18m74Fx6LGm7CewE/oyHk04qfbrkd4+tbficF3ok=; h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=gU0qo4HS87yUenWJwIDTd6X7alv9Ig0LNT9aHG6KZziH/hUQjvq3bqYibJxXFSuS7 wLf7R4JpXNzqlUov/eZx4qZA0Gs//MXctuVqXzLs7q5WOrw+jvQ4q9hV7Tm/mztIIz I2Tf8KWRR3ZetFScmfnGcBD/CMSbIT/0FJzou+l8=
From: "Paul E. Jones" <paulej@packetizer.com>
To: <insipid@ietf.org>
Date: Thu, 21 Mar 2013 21:52:29 -0400
Message-ID: <010001ce269f$ea74ecf0$bf5ec6d0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4mnvJjxiazr5YcTESPM1noEOMsOg==
Content-Language: en-us
Subject: [Insipid] Technical changes for the draft-ietf-insipid-session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Mar 2013 01:52:18 -0000

Folks,

The technical changes I have for the solution document include changes as
shown below:

Section 6

OLD
It should be noted that messages received by a UA might contain a "remote"
parameter that does match the UAs UUID.  This might happen as a result of
service interactions by intermediaries and MUST NOT be regarded as an error.

NEW
It should be noted that messages received by a UA might contain a "remote"
parameter that does match the UAs UUID.  This might happen as a result of
service interactions by intermediaries and MUST NOT negatively affect the
communication session.  However, the UA may log this event for the purposes
of troubleshooting.


OLD
... the UA MUST NOT change that UUID value for the duration of the session,
including when communication attempts are retried due to receipt of 4xx
messages, when the session is redirected in response to a 3xx message, or
when a session is transferred via a REFER message [7].

NEW
... the UA MUST NOT change that UUID value for the duration of the session,
including when communication attempts are retried due to receipt of 4xx
messages, when the session is redirected in response to a 3xx message, when
a session is transferred via a REFER message [8], or when a SIP dialog is
replace via an INVITE with Replaces [7].


There was discussion of changing the "sess-uuid" production, but I believe
it was decided in the meeting to leave it as it is in -00.

Was it decided to remove Section 9.6 or any other text?

Paul



From paulej@packetizer.com  Thu Mar 21 20:14:23 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 332D321F8E6E for <insipid@ietfa.amsl.com>; Thu, 21 Mar 2013 20:14:23 -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=[AWL=-0.646,  BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_HEAD=1.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DVBco3SkahNH for <insipid@ietfa.amsl.com>; Thu, 21 Mar 2013 20:14:22 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 4EDB321F81FF for <insipid@ietf.org>; Thu, 21 Mar 2013 20:14:22 -0700 (PDT)
Received: from dyn-157.arid.us (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2M3EF1Z008683 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <insipid@ietf.org>; Thu, 21 Mar 2013 23:14:17 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1363922061; bh=khDgceLsxB5oSKiHjy/BitlMo6JuMGenk5RcC05+a8s=; h=MIME-Version:Content-Type:Subject:From:Date:To:Message-ID; b=JlDvj/uHbcE39DY0tsPfPRN0PeIJ9OVXnSDiIFt+fk1aqSfYdCTs8Wxhb+7w4nJ6a GW3rxXvnkvCofy8HnMbbCu8QtYavOqbsdqQabuvNqcPT06Kodjcifq/WPpS/TwYF07 KTcqyg29IYVtElP/uBhjIkteaozNMWnx4Way4Gxc=
User-Agent: K-9 Mail for Android
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----K552ZZMX88OO4052CWZ44E3FSGRGTN"
From: "Paul E. Jones" <paulej@packetizer.com>
Date: Thu, 21 Mar 2013 23:14:14 -0400
To: insipid@ietf.org
Message-ID: <06b2139a-662a-489d-b24b-a84b26185b34@email.android.com>
Subject: [Insipid] Fwd: The value of the "local-uuid" to be inserted by SBCs
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Mar 2013 03:14:23 -0000

------K552ZZMX88OO4052CWZ44E3FSGRGTN
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

Folks,

In addition to the two other items, there is this suggestion from Laura. I think it's reasonable, but I've not written the text, yet.

Do others have only on this?

Paul


-------- Original Message --------
From: Laura Liess <laura.liess.dt@googlemail.com>
Sent: Tue Mar 12 17:21:11 EDT 2013
To: Paul Jones <paulej@packetizer.com>
Cc: insipid@ietf.org
Subject: The value of the "local-uuid" to be inserted by SBCs

Paul,

I have a comment concerning folowing text in Section 7:


 If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a "local-uuid" value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a "remote" value that identifies the
   receiving UA, it MUST insert that value if also inserting the "local-
   uuid" value.

IMO the value of the of the local-uuid must be the hashed call-ID of
the incomming call leg.
Otherwise there is not possible for an external  monitoring device to
correlate both legs of a call  in case of a failure
of the receiving device ( the receiving device drops the call).

Thank you
Laura



2013/3/12 <internet-drafts@ietf.org>

>
> 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
>         Author(s)       : Paul E. Jones
>                           Chris Pearce
>                           James Polk
>                           Gonzalo Salgueiro
>         Filename        : draft-ietf-insipid-session-id-00.txt
>         Pages           : 20
>         Date            : 2013-03-12
>
> 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.
>
>
> 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-00
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>

------K552ZZMX88OO4052CWZ44E3FSGRGTN
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head/><body><html><head/><body>Folks,<br>
<br>
In addition to the two other items, there is this suggestion from Laura. I think it&#39;s reasonable, but I&#39;ve not written the text, yet.<br>
<br>
Do others have only on this?<br>
<br>
Paul<br><br><div style='font-size:10.0pt;font-family:"Tahoma","sans-serif";padding:3.0pt 0in 0in 0in'>
<hr style='border:none;border-top:solid #B5C4DF 1.0pt'>
<b>From:</b> Laura Liess &lt;laura.liess.dt@googlemail.com&gt;<br>
<b>Sent:</b> Tue Mar 12 17:21:11 EDT 2013<br>
<b>To:</b> Paul Jones &lt;paulej@packetizer.com&gt;<br>
<b>Cc:</b> insipid@ietf.org<br>
<b>Subject:</b> The value of the &quot;local-uuid&quot; to be inserted by SBCs<br>
</div>
<br>
<pre><span style="font-family:arial narrow,sans-serif"><font><font>Paul<font>,<br></font></font></font></span></pre><pre><span style="font-family:arial narrow,sans-serif"><font><font><font>I have a comment concerning folowing text in Section 7:</font></font></font></span><br>
</pre><pre style="margin-left:40px"><span style="font-family:arial narrow,sans-serif"></span></pre><pre style="margin-left:80px"><span style="font-family:arial narrow,sans-serif"><font><br> <font>If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a &quot;local-uuid&quot; value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a &quot;remote&quot; value that identifies the
   receiving UA, it MUST insert that value if also inserting the &quot;local-
   uuid&quot; value.<br></font></font></span></pre><pre><span style="font-family:arial narrow,sans-serif"><font>IMO <font>the value of the of the local-uu<font>id</font></font> must be the hashed call-ID <font>of the incomming call leg. <br>
Otherwise the<font>re is not possible for an external </font> monitoring device to correlate both legs of a call  in case of a failure<br><font>of the receiving device ( the receiving device drops the call). <br><br><font>Thank you<br>
<font>Laura</font><br></font></font></font></font></span></pre><div style="margin-left:40px"><span style="font-family:arial narrow,sans-serif"></span><br><span style="font-family:arial narrow,sans-serif"></span></div><br>
<div class="gmail_quote">2013/3/12  <span dir="ltr">&lt;<a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a>&gt;</span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts directories.<br>
 This draft is a work item of the INtermediary-safe SIP session ID Working Group of the IETF.<br>
<br>
        Title           : End-to-End Session Identification in IP-Based Multimedia Communication Networks<br>
        Author(s)       : Paul E. Jones<br>
                          Chris Pearce<br>
                          James Polk<br>
                          Gonzalo Salgueiro<br>
        Filename        : draft-ietf-insipid-session-id-00.txt<br>
        Pages           : 20<br>
        Date            : 2013-03-12<br>
<br>
Abstract:<br>
   This document describes an end-to-end Session Identifier for use in<br>
   IP-based Multimedia Communication systems that enables endpoints,<br>
   intermediate devices, and management systems to identify a session<br>
   end-to-end, associate multiple endpoints with a given multipoint<br>
   conference, track communication sessions when they are redirected,<br>
   and associate one or more media flows with a given communication<br>
   session.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href="https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href="http://tools.ietf.org/html/draft-ietf-insipid-session-id-00" target="_blank">http://tools.ietf.org/html/draft-ietf-insipid-session-id-00</a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href="ftp://ftp.ietf.org/internet-drafts/" target="_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
insipid mailing list<br>
<a href="mailto:insipid@ietf.org" target="_blank">insipid@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/insipid" target="_blank">https://www.ietf.org/mailman/listinfo/insipid</a><br>
</blockquote></div><br>
</body></html></body></html>
------K552ZZMX88OO4052CWZ44E3FSGRGTN--


From paulej@packetizer.com  Thu Mar 21 21:13:25 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F290821F8B45 for <insipid@ietfa.amsl.com>; Thu, 21 Mar 2013 21:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.867
X-Spam-Level: 
X-Spam-Status: No, score=-1.867 tagged_above=-999 required=5 tests=[AWL=-0.603, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_HEAD=1.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iORulE-azR8O for <insipid@ietfa.amsl.com>; Thu, 21 Mar 2013 21:13:24 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9E821F8B20 for <insipid@ietf.org>; Thu, 21 Mar 2013 21:13:23 -0700 (PDT)
Received: from dyn-170.arid.us (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2M4DM1O011929 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <insipid@ietf.org>; Fri, 22 Mar 2013 00:13:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1363925603; bh=NSVX4q0s9nJkgQLuDZQ86HBSsDb8P8Ra1FcpFMOAu0A=; h=In-Reply-To:References:MIME-Version:Content-Type:Subject:From: Date:To:Message-ID; b=i3/bsM+d/OPHralRq+5oXxCirw90wzgLR62fXxjygbjAYoQ/j/R8YWLFEx73oFBmF Eb/85fLn06CQqHwKozPRHOYAglvqHeabsAGlcLzdpzW/4EHfCBf/hw3MqxqoRI5U+P wzwyztiGakVAqnPo/Xo1NA6fROD3+aMP7hDwYKdM=
User-Agent: Kaiten Mail
In-Reply-To: <06b2139a-662a-489d-b24b-a84b26185b34@email.android.com>
References: <06b2139a-662a-489d-b24b-a84b26185b34@email.android.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----I4TQO9SJBOAVW20ZMRIACCMC21PT1A"
From: "Paul E. Jones" <paulej@packetizer.com>
Date: Fri, 22 Mar 2013 00:13:17 -0400
To: insipid@ietf.org
Message-ID: <c332aa51-db32-4961-ba7f-899fd44dfd18@email.android.com>
Subject: Re: [Insipid] Fwd: The value of the "local-uuid" to be inserted by SBCs
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Mar 2013 04:13:25 -0000

------I4TQO9SJBOAVW20ZMRIACCMC21PT1A
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

That would be "do others have an opinion on this?"

Paul


-------- Original Message --------
From: "Paul E. Jones" <paulej@packetizer.com>
Sent: Thu Mar 21 23:14:14 EDT 2013
To: insipid@ietf.org
Subject: [Insipid] Fwd: The value of the "local-uuid" to be inserted by SBCs

Folks,

In addition to the two other items, there is this suggestion from Laura. I think it's reasonable, but I've not written the text, yet.

Do others have only on this?

Paul


-------- Original Message --------
From: Laura Liess <laura.liess.dt@googlemail.com>
Sent: Tue Mar 12 17:21:11 EDT 2013
To: Paul Jones <paulej@packetizer.com>
Cc: insipid@ietf.org
Subject: The value of the "local-uuid" to be inserted by SBCs

Paul,

I have a comment concerning folowing text in Section 7:


 If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a "local-uuid" value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a "remote" value that identifies the
   receiving UA, it MUST insert that value if also inserting the "local-
   uuid" value.

IMO the value of the of the local-uuid must be the hashed call-ID of
the incomming call leg.
Otherwise there is not possible for an external  monitoring device to
correlate both legs of a call  in case of a failure
of the receiving device ( the receiving device drops the call).

Thank you
Laura



2013/3/12 <internet-drafts@ietf.org>

>
> 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
>         Author(s)       : Paul E. Jones
>                           Chris Pearce
>                           James Polk
>                           Gonzalo Salgueiro
>         Filename        : draft-ietf-insipid-session-id-00.txt
>         Pages           : 20
>         Date            : 2013-03-12
>
> 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.
>
>
> 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-00
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>


------------------------------------------------------------------------

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

------I4TQO9SJBOAVW20ZMRIACCMC21PT1A
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head/><body><html><head></head><body><p dir="ltr">That would be "do others have an opinion on this?"</p>
<p dir="ltr">Paul</p>
<br><br><div style='font-size:10.0pt;font-family:"Tahoma","sans-serif";padding:3.0pt 0in 0in 0in'>
<hr style='border:none;border-top:solid #B5C4DF 1.0pt'>
<b>From:</b> &quot;Paul E. Jones&quot; &lt;paulej@packetizer.com&gt;<br>
<b>Sent:</b> Thu Mar 21 23:14:14 EDT 2013<br>
<b>To:</b> insipid@ietf.org<br>
<b>Subject:</b> [Insipid] Fwd: The value of the &quot;local-uuid&quot; to be inserted by SBCs<br>
</div>
<br>
Folks,<br />
<br />
In addition to the two other items, there is this suggestion from Laura. I think it&#39;s reasonable, but I&#39;ve not written the text, yet.<br />
<br />
Do others have only on this?<br />
<br />
Paul<br /><br /><div style="font-size:10.0pt;font-family:"Tahoma","sans-serif";padding:3.0pt 0in 0in 0in">
<hr style="border:none;border-top:solid #B5C4DF 1.0pt" />
<b>From:</b> Laura Liess &lt;laura.liess.dt@googlemail.com&gt;<br />
<b>Sent:</b> Tue Mar 12 17:21:11 EDT 2013<br />
<b>To:</b> Paul Jones &lt;paulej@packetizer.com&gt;<br />
<b>Cc:</b> insipid@ietf.org<br />
<b>Subject:</b> The value of the &quot;local-uuid&quot; to be inserted by SBCs<br />
</div>
<br />
<pre><span style="font-family:arial narrow,sans-serif"><font><font>Paul<font>,<br /></font></font></font></span></pre><pre><span style="font-family:arial narrow,sans-serif"><font><font><font>I have a comment concerning folowing text in Section 7:</font></font></font></span><br />
</pre><pre style="margin-left:40px"><span style="font-family:arial narrow,sans-serif"></span></pre><pre style="margin-left:80px"><span style="font-family:arial narrow,sans-serif"><font><br /> <font>If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a &quot;local-uuid&quot; value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a &quot;remote&quot; value that identifies the
   receiving UA, it MUST insert that value if also inserting the &quot;local-
   uuid&quot; value.<br /></font></font></span></pre><pre><span style="font-family:arial narrow,sans-serif"><font>IMO <font>the value of the of the local-uu<font>id</font></font> must be the hashed call-ID <font>of the incomming call leg. <br />
Otherwise the<font>re is not possible for an external </font> monitoring device to correlate both legs of a call  in case of a failure<br /><font>of the receiving device ( the receiving device drops the call). <br /><br /><font>Thank you<br />
<font>Laura</font><br /></font></font></font></font></span></pre><div style="margin-left:40px"><span style="font-family:arial narrow,sans-serif"></span><br /><span style="font-family:arial narrow,sans-serif"></span></div><br />
<div class="gmail_quote">2013/3/12  <span dir="ltr">&lt;<a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a>&gt;</span><br />
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br />
A New Internet-Draft is available from the on-line Internet-Drafts directories.<br />
 This draft is a work item of the INtermediary-safe SIP session ID Working Group of the IETF.<br />
<br />
        Title           : End-to-End Session Identification in IP-Based Multimedia Communication Networks<br />
        Author(s)       : Paul E. Jones<br />
                          Chris Pearce<br />
                          James Polk<br />
                          Gonzalo Salgueiro<br />
        Filename        : draft-ietf-insipid-session-id-00.txt<br />
        Pages           : 20<br />
        Date            : 2013-03-12<br />
<br />
Abstract:<br />
   This document describes an end-to-end Session Identifier for use in<br />
   IP-based Multimedia Communication systems that enables endpoints,<br />
   intermediate devices, and management systems to identify a session<br />
   end-to-end, associate multiple endpoints with a given multipoint<br />
   conference, track communication sessions when they are redirected,<br />
   and associate one or more media flows with a given communication<br />
   session.<br />
<br />
<br />
The IETF datatracker status page for this draft is:<br />
<a href="https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id</a><br />
<br />
There&#39;s also a htmlized version available at:<br />
<a href="http://tools.ietf.org/html/draft-ietf-insipid-session-id-00" target="_blank">http://tools.ietf.org/html/draft-ietf-insipid-session-id-00</a><br />
<br />
<br />
Internet-Drafts are also available by anonymous FTP at:<br />
<a href="ftp://ftp.ietf.org/internet-drafts/" target="_blank">ftp://ftp.ietf.org/internet-drafts/</a><br />
<br />
_______________________________________________<br />
insipid mailing list<br />
<a href="mailto:insipid@ietf.org" target="_blank">insipid@ietf.org</a><br />
<a href="https://www.ietf.org/mailman/listinfo/insipid" target="_blank">https://www.ietf.org/mailman/listinfo/insipid</a><br />
</blockquote></div><br />
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre style="white-space: pre-wrap; word-wrap:break-word; font-family: monospace; margin-top: 0px"><hr /><br />insipid mailing list<br />insipid@ietf.org<br /><a href="https://www.ietf.org/mailman/listinfo/insipid">https://www.ietf.org/mailman/listinfo/insipid</a><br /></pre></body></html></body></html>
------I4TQO9SJBOAVW20ZMRIACCMC21PT1A--


From eckelcu@cisco.com  Fri Mar 22 12:53:33 2013
Return-Path: <eckelcu@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2130521F9198 for <insipid@ietfa.amsl.com>; Fri, 22 Mar 2013 12:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BrRUUjeJtdXA for <insipid@ietfa.amsl.com>; Fri, 22 Mar 2013 12:53:32 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 372EE21F9196 for <insipid@ietf.org>; Fri, 22 Mar 2013 12:53:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2232; q=dns/txt; s=iport; t=1363982012; x=1365191612; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=9iWnUwmwPGHv9bX8pvYsDA4N2+EVr+XbG101ramqX2g=; b=cKDnqTZPKAM18BRqk+ywlqEqoQ4Tkwf4juAB1PQIQHWaMhIsm4wd34bq vMmCIHz4v0AOJzC05JN3er23UDOPr6upHMAdK59qo/8z8SddAAExQsgl7 Kk1Uj0Vn8tzOUQL40JRhmbbJ8ubRCDiJxOREKTQN0OoKZfUIay0A7NkjP Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAHK1TFGtJV2b/2dsb2JhbABDxVWBZRZ0giQBAQEDAQEBASQTNBcEAgEIEQQBAQsUCQcnCxQJCAEBBAEJCQgTh3MFAQzCDgSOYSYSBoJZYQOnaIMKgig
X-IronPort-AV: E=Sophos;i="4.84,893,1355097600"; d="scan'208";a="190530809"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP; 22 Mar 2013 19:53:31 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2MJrVDo021908 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Mar 2013 19:53:31 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.144]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Fri, 22 Mar 2013 14:53:21 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul E. Jones" <paulej@packetizer.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Technical changes for the draft-ietf-insipid-session-id
Thread-Index: Ac4mnvJjxiazr5YcTESPM1noEOMsOgAl6Rrw
Date: Fri, 22 Mar 2013 19:53:20 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828047DB646@xmb-aln-x08.cisco.com>
References: <010001ce269f$ea74ecf0$bf5ec6d0$@packetizer.com>
In-Reply-To: <010001ce269f$ea74ecf0$bf5ec6d0$@packetizer.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.50]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Insipid] Technical changes for the draft-ietf-insipid-session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Mar 2013 19:53:33 -0000

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> Behalf Of Paul E. Jones
> Sent: Thursday, March 21, 2013 6:52 PM
> To: insipid@ietf.org
> Subject: [Insipid] Technical changes for the draft-ietf-insipid-session-i=
d
>=20
> Folks,
>=20
> The technical changes I have for the solution document include changes as
> shown below:
>=20
> Section 6
>=20
> OLD
> It should be noted that messages received by a UA might contain a "remote=
"
> parameter that does match the UAs UUID.  This might happen as a result of
> service interactions by intermediaries and MUST NOT be regarded as an
> error.
>=20
> NEW
> It should be noted that messages received by a UA might contain a "remote=
"
> parameter that does match the UAs UUID.  This might happen as a result of
> service interactions by intermediaries and MUST NOT negatively affect the
> communication session.  However, the UA may log this event for the
> purposes
> of troubleshooting.

Looks good, except I think you mean "does NOT match" instead of "does match=
".
=20
>=20
> OLD
> ... the UA MUST NOT change that UUID value for the duration of the sessio=
n,
> including when communication attempts are retried due to receipt of 4xx
> messages, when the session is redirected in response to a 3xx message, or
> when a session is transferred via a REFER message [7].
>=20
> NEW
> ... the UA MUST NOT change that UUID value for the duration of the sessio=
n,
> including when communication attempts are retried due to receipt of 4xx
> messages, when the session is redirected in response to a 3xx message,
> when
> a session is transferred via a REFER message [8], or when a SIP dialog is
> replace via an INVITE with Replaces [7].

Fine, but "replace" -> "replaced"

Cheers,
Charles

>=20
>=20
> There was discussion of changing the "sess-uuid" production, but I believ=
e
> it was decided in the meeting to leave it as it is in -00.
>=20
> Was it decided to remove Section 9.6 or any other text?
>=20
> Paul
>=20
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid

From paulej@packetizer.com  Sat Mar 23 12:09:11 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D70121F8BB7 for <insipid@ietfa.amsl.com>; Sat, 23 Mar 2013 12:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJNO8zzbAGPV for <insipid@ietfa.amsl.com>; Sat, 23 Mar 2013 12:09:10 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 52E7521F8BB6 for <insipid@ietf.org>; Sat, 23 Mar 2013 12:09:08 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2NJ95WE011220 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 23 Mar 2013 15:09:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1364065745; bh=kFghWwpTedueWO4aePbC21xOcAxJORHqOfflnxzS6TA=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=WD3l7FRrX1dSKSx8S/oMB7138yTiMiZEOlDfhql4Lk9dY2Dv7AllD05a3A2CpMUdB 952CZuYBwQYO54JtoBFosDXSXwI2DLYjcas8ct7tU39b8fL+u8eoLlIG6LEryEdolb j/0n7GuIyYYm5K/aUkvNIQtH9GANemYYdNp+j0NI=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Charles Eckel \(eckelcu\)'" <eckelcu@cisco.com>, <insipid@ietf.org>
References: <010001ce269f$ea74ecf0$bf5ec6d0$@packetizer.com> <92B7E61ADAC1BB4F941F943788C08828047DB646@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828047DB646@xmb-aln-x08.cisco.com>
Date: Sat, 23 Mar 2013 15:09:28 -0400
Message-ID: <03ca01ce27f9$f1102470$d3306d50$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGefFjjTlGgVjIDUpqP5b+w+6DQTAGMDvpcmQaaQwA=
Content-Language: en-us
Subject: Re: [Insipid] Technical changes for the draft-ietf-insipid-session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Mar 2013 19:09:11 -0000

Charles,

> > Section 6
> >
> > OLD
> > It should be noted that messages received by a UA might contain a
> "remote"
> > parameter that does match the UAs UUID.  This might happen as a result
> > of service interactions by intermediaries and MUST NOT be regarded as
> > an error.
> >
> > NEW
> > It should be noted that messages received by a UA might contain a
> "remote"
> > parameter that does match the UAs UUID.  This might happen as a result
> > of service interactions by intermediaries and MUST NOT negatively
> > affect the communication session.  However, the UA may log this event
> > for the purposes of troubleshooting.
> 
> Looks good, except I think you mean "does NOT match" instead of "does
> match".

Thanks for catching that!
 
> > OLD
> > ... the UA MUST NOT change that UUID value for the duration of the
> > session, including when communication attempts are retried due to
> > receipt of 4xx messages, when the session is redirected in response to
> > a 3xx message, or when a session is transferred via a REFER message
> [7].
> >
> > NEW
> > ... the UA MUST NOT change that UUID value for the duration of the
> > session, including when communication attempts are retried due to
> > receipt of 4xx messages, when the session is redirected in response to
> > a 3xx message, when a session is transferred via a REFER message [8],
> > or when a SIP dialog is replace via an INVITE with Replaces [7].
> 
> Fine, but "replace" -> "replaced"

Thanks, again! :-)

I corrected both errors in my draft.

Paul



From brett@broadsoft.com  Wed Mar 27 08:01:19 2013
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A75E21F91C5 for <insipid@ietfa.amsl.com>; Wed, 27 Mar 2013 08:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6SD6RsqU1md for <insipid@ietfa.amsl.com>; Wed, 27 Mar 2013 08:01:18 -0700 (PDT)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.21]) by ietfa.amsl.com (Postfix) with ESMTP id C24DA21F91BC for <insipid@ietf.org>; Wed, 27 Mar 2013 08:01:18 -0700 (PDT)
Received: from CASUMHUB04.citservers.local (172.16.98.225) by smtpedge.partnerhosted.com (172.16.98.247) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 27 Mar 2013 08:03:33 -0700
Received: from MBX07.citservers.local ([fe80::d9a5:240b:376a:aeb6]) by CASUMHUB04.citservers.local ([::1]) with mapi id 14.02.0247.003; Wed, 27 Mar 2013 08:03:33 -0700
From: Brett Tate <brett@broadsoft.com>
To: "Paul E. Jones" <paulej@packetizer.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Fwd: The value of the "local-uuid" to be inserted by SBCs
Thread-Index: AQHOJrQCqsH7HGd0SUSfsQKdXiEbRZi5nOCA
Date: Wed, 27 Mar 2013 15:03:32 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B88196A5165@MBX07.citservers.local>
References: <06b2139a-662a-489d-b24b-a84b26185b34@email.android.com> <c332aa51-db32-4961-ba7f-899fd44dfd18@email.android.com>
In-Reply-To: <c332aa51-db32-4961-ba7f-899fd44dfd18@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.98.77]
Content-Type: multipart/alternative; boundary="_000_576A8B541C219D4E9CEB1DF8C19C7B88196A5165MBX07citservers_"
MIME-Version: 1.0
Subject: Re: [Insipid] Fwd: The value of the "local-uuid" to be inserted by	SBCs
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 27 Mar 2013 15:01:19 -0000

--_000_576A8B541C219D4E9CEB1DF8C19C7B88196A5165MBX07citservers_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhlIHN1Z2dlc3Rpb24gc291bmRzIG9rYXkgdG8gbWU7IGhvd2V2ZXIgdGhlIHJlcXVlc3QgY2Fu
IGZvcmsgYW5kIENhbGwtSUQgY2hhbmdlIHByaW9yIHRvIHRoZSBTZXNzaW9uLUlEIGJlaW5nIGFk
ZGVkLiAgVGh1cyBldmVuIHRob3VnaCB0aGVyZSBtaWdodCBub3QgYmUgYSBiZXR0ZXIgc29sdXRp
b24sIHRoZSBzdWdnZXN0aW9uIGRvZXMgbm90IGNvbXBsZXRlbHkgcmVzb2x2ZSB0aGUgY29ycmVs
YXRpb24gcHJvYmxlbS4NCg0KSWYgdGhlcmUgYXJlIHN0aWxsIHZlbmRvcnMgd2hvIHJldXNlIENh
bGwtSUQgZm9yIGNvcnJlbGF0aW9uIG9yIG90aGVyIHJlYXNvbnMsIGl0IG1pZ2h0IGNhdXNlIHRo
ZSBpbnRlcm1lZGlhcnkgdG8gYWRkIHRoZSBzYW1lIGxvY2FsLXV1aWQgd2hlbiBpdCBwb3RlbnRp
YWxseSBpc27igJl0IGRlc2lyYWJsZS4NCg0KDQpGcm9tOiBpbnNpcGlkLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzppbnNpcGlkLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBQYXVsIEUu
IEpvbmVzDQpTZW50OiBGcmlkYXksIE1hcmNoIDIyLCAyMDEzIDEyOjEzIEFNDQpUbzogaW5zaXBp
ZEBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtJbnNpcGlkXSBGd2Q6IFRoZSB2YWx1ZSBvZiB0aGUg
ImxvY2FsLXV1aWQiIHRvIGJlIGluc2VydGVkIGJ5IFNCQ3MNCg0KDQpUaGF0IHdvdWxkIGJlICJk
byBvdGhlcnMgaGF2ZSBhbiBvcGluaW9uIG9uIHRoaXM/Ig0KDQpQYXVsDQoNCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiAiUGF1bCBFLiBKb25lcyIgPHBhdWxlakBwYWNr
ZXRpemVyLmNvbTxtYWlsdG86cGF1bGVqQHBhY2tldGl6ZXIuY29tPj4NClNlbnQ6IFRodSBNYXIg
MjEgMjM6MTQ6MTQgRURUIDIwMTMNClRvOiBpbnNpcGlkQGlldGYub3JnPG1haWx0bzppbnNpcGlk
QGlldGYub3JnPg0KU3ViamVjdDogW0luc2lwaWRdIEZ3ZDogVGhlIHZhbHVlIG9mIHRoZSAibG9j
YWwtdXVpZCIgdG8gYmUgaW5zZXJ0ZWQgYnkgU0JDcw0KDQpGb2xrcywNCg0KSW4gYWRkaXRpb24g
dG8gdGhlIHR3byBvdGhlciBpdGVtcywgdGhlcmUgaXMgdGhpcyBzdWdnZXN0aW9uIGZyb20gTGF1
cmEuIEkgdGhpbmsgaXQncyByZWFzb25hYmxlLCBidXQgSSd2ZSBub3Qgd3JpdHRlbiB0aGUgdGV4
dCwgeWV0Lg0KDQpEbyBvdGhlcnMgaGF2ZSBvbmx5IG9uIHRoaXM/DQoNClBhdWwNCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBMYXVyYSBMaWVzcyA8bGF1cmEubGllc3Mu
ZHRAZ29vZ2xlbWFpbC5jb208bWFpbHRvOmxhdXJhLmxpZXNzLmR0QGdvb2dsZW1haWwuY29tPj4N
ClNlbnQ6IFR1ZSBNYXIgMTIgMTc6MjE6MTEgRURUIDIwMTMNClRvOiBQYXVsIEpvbmVzIDxwYXVs
ZWpAcGFja2V0aXplci5jb208bWFpbHRvOnBhdWxlakBwYWNrZXRpemVyLmNvbT4+DQpDYzogaW5z
aXBpZEBpZXRmLm9yZzxtYWlsdG86aW5zaXBpZEBpZXRmLm9yZz4NClN1YmplY3Q6IFRoZSB2YWx1
ZSBvZiB0aGUgImxvY2FsLXV1aWQiIHRvIGJlIGluc2VydGVkIGJ5IFNCQ3MNCg0KDQpQYXVsLA0K
DQpJIGhhdmUgYSBjb21tZW50IGNvbmNlcm5pbmcgZm9sb3dpbmcgdGV4dCBpbiBTZWN0aW9uIDc6
DQoNCg0KIElmIGEgU0lQIG1lc3NhZ2UgaGF2aW5nIG5vIFNlc3Npb24tSUQgaGVhZGVyIGlzIHJl
Y2VpdmVkIGJ5IGFuDQoNCiAgIGludGVybWVkaWFyeSwgdGhlIGludGVybWVkaWFyeSBNQVkgYXNz
aWduIGEgImxvY2FsLXV1aWQiIHZhbHVlIHRvDQoNCiAgIHJlcHJlc2VudCB0aGUgc2VuZGluZyBl
bmRwb2ludCBhbmQgaW5zZXJ0IHRoYXQgdmFsdWUgaW50byBhbGwNCg0KICAgc2lnbmFsaW5nIG1l
c3NhZ2VzIG9uIGJlaGFsZiBvZiB0aGUgc2VuZGluZyBlbmRwb2ludC4gIElmIHRoZQ0KDQogICBp
bnRlcm1lZGlhcnkgaXMgYXdhcmUgb2YgYSAicmVtb3RlIiB2YWx1ZSB0aGF0IGlkZW50aWZpZXMg
dGhlDQoNCiAgIHJlY2VpdmluZyBVQSwgaXQgTVVTVCBpbnNlcnQgdGhhdCB2YWx1ZSBpZiBhbHNv
IGluc2VydGluZyB0aGUgImxvY2FsLQ0KDQogICB1dWlkIiB2YWx1ZS4NCg0KSU1PIHRoZSB2YWx1
ZSBvZiB0aGUgb2YgdGhlIGxvY2FsLXV1aWQgbXVzdCBiZSB0aGUgaGFzaGVkIGNhbGwtSUQgb2Yg
dGhlIGluY29tbWluZyBjYWxsIGxlZy4NCg0KDQpPdGhlcndpc2UgdGhlcmUgaXMgbm90IHBvc3Np
YmxlIGZvciBhbiBleHRlcm5hbCAgbW9uaXRvcmluZyBkZXZpY2UgdG8gY29ycmVsYXRlIGJvdGgg
bGVncyBvZiBhIGNhbGwgIGluIGNhc2Ugb2YgYSBmYWlsdXJlDQpvZiB0aGUgcmVjZWl2aW5nIGRl
dmljZSAoIHRoZSByZWNlaXZpbmcgZGV2aWNlIGRyb3BzIHRoZSBjYWxsKS4NCg0KVGhhbmsgeW91
DQoNCg0KTGF1cmENCg0KDQo=

--_000_576A8B541C219D4E9CEB1DF8C19C7B88196A5165MBX07citservers_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VGFob21hOw0K
CXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6Q29uc29sYXM7DQoJcGFub3NlLTE6MiAxMSA2IDkgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQXJpYWwgTmFycm93IjsNCglwYW5vc2UtMToyIDExIDYgNiAyIDIg
MiAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05v
cm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw
dDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJz
ZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRl
ZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
Y29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0
OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi
O30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwg
UHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpzcGFu
LkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRl
ZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwg
UHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseTpDb25zb2xhczt9DQpzcGFuLkVtYWlsU3R5bGUy
MA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNv
LXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3Jk
U2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGlu
IDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9z
dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk
aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl
ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9o
ZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRp
diBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGUgc3VnZ2VzdGlvbiBzb3VuZHMgb2th
eSB0byBtZTsgaG93ZXZlciB0aGUgcmVxdWVzdCBjYW4gZm9yayBhbmQgQ2FsbC1JRCBjaGFuZ2Ug
cHJpb3IgdG8gdGhlIFNlc3Npb24tSUQgYmVpbmcgYWRkZWQuJm5ic3A7IFRodXMgZXZlbiB0aG91
Z2ggdGhlcmUgbWlnaHQgbm90IGJlDQogYSBiZXR0ZXIgc29sdXRpb24sIHRoZSBzdWdnZXN0aW9u
IGRvZXMgbm90IGNvbXBsZXRlbHkgcmVzb2x2ZSB0aGUgY29ycmVsYXRpb24gcHJvYmxlbS4mbmJz
cDsNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+SWYgdGhlcmUgYXJlIHN0aWxsIHZlbmRvcnMgd2hvIHJldXNlIENhbGwt
SUQgZm9yIGNvcnJlbGF0aW9uIG9yIG90aGVyIHJlYXNvbnMsIGl0IG1pZ2h0IGNhdXNlIHRoZSBp
bnRlcm1lZGlhcnkgdG8gYWRkIHRoZSBzYW1lIGxvY2FsLXV1aWQgd2hlbiBpdCBwb3RlbnRpYWxs
eQ0KIGlzbuKAmXQgZGVzaXJhYmxlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVw
dDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGlu
IDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gaW5zaXBpZC1i
b3VuY2VzQGlldGYub3JnIFttYWlsdG86aW5zaXBpZC1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24g
QmVoYWxmIE9mIDwvYj5QYXVsIEUuIEpvbmVzPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgTWFy
Y2ggMjIsIDIwMTMgMTI6MTMgQU08YnI+DQo8Yj5Ubzo8L2I+IGluc2lwaWRAaWV0Zi5vcmc8YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtJbnNpcGlkXSBGd2Q6IFRoZSB2YWx1ZSBvZiB0aGUgJnF1
b3Q7bG9jYWwtdXVpZCZxdW90OyB0byBiZSBpbnNlcnRlZCBieSBTQkNzPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHA+VGhhdCB3b3VsZCBiZSAmcXVvdDtkbyBvdGhlcnMgaGF2ZSBhbiBvcGlu
aW9uIG9uIHRoaXM/JnF1b3Q7PG86cD48L286cD48L3A+DQo8cD5QYXVsPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXYgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImNl
bnRlciIgc3R5bGU9InRleHQtYWxpZ246Y2VudGVyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+DQo8aHIgc2l6ZT0iMiIgd2lkdGg9IjEwMCUiIGFsaWduPSJjZW50ZXIiPg0KPC9zcGFuPjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+ICZxdW90O1BhdWwg
RS4gSm9uZXMmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpwYXVsZWpAcGFja2V0aXplci5jb20i
PnBhdWxlakBwYWNrZXRpemVyLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+U2VudDo8L2I+IFRodSBNYXIg
MjEgMjM6MTQ6MTQgRURUIDIwMTM8YnI+DQo8Yj5Ubzo8L2I+IDxhIGhyZWY9Im1haWx0bzppbnNp
cGlkQGlldGYub3JnIj5pbnNpcGlkQGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9iPiBb
SW5zaXBpZF0gRndkOiBUaGUgdmFsdWUgb2YgdGhlICZxdW90O2xvY2FsLXV1aWQmcXVvdDsgdG8g
YmUgaW5zZXJ0ZWQgYnkgU0JDczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48YnI+DQpGb2xrcyw8
YnI+DQo8YnI+DQpJbiBhZGRpdGlvbiB0byB0aGUgdHdvIG90aGVyIGl0ZW1zLCB0aGVyZSBpcyB0
aGlzIHN1Z2dlc3Rpb24gZnJvbSBMYXVyYS4gSSB0aGluayBpdCdzIHJlYXNvbmFibGUsIGJ1dCBJ
J3ZlIG5vdCB3cml0dGVuIHRoZSB0ZXh0LCB5ZXQuPGJyPg0KPGJyPg0KRG8gb3RoZXJzIGhhdmUg
b25seSBvbiB0aGlzPzxicj4NCjxicj4NClBhdWw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2
IGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJ0ZXh0LWFsaWduOmNlbnRl
ciI+DQo8aHIgc2l6ZT0iMiIgd2lkdGg9IjEwMCUiIGFsaWduPSJjZW50ZXIiPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gTGF1cmEgTGllc3MgJmx0OzxhIGhyZWY9
Im1haWx0bzpsYXVyYS5saWVzcy5kdEBnb29nbGVtYWlsLmNvbSI+bGF1cmEubGllc3MuZHRAZ29v
Z2xlbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPlNlbnQ6PC9iPiBUdWUgTWFyIDEyIDE3OjIxOjEx
IEVEVCAyMDEzPGJyPg0KPGI+VG86PC9iPiBQYXVsIEpvbmVzICZsdDs8YSBocmVmPSJtYWlsdG86
cGF1bGVqQHBhY2tldGl6ZXIuY29tIj5wYXVsZWpAcGFja2V0aXplci5jb208L2E+Jmd0Ozxicj4N
CjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmluc2lwaWRAaWV0Zi5vcmciPmluc2lwaWRAaWV0
Zi5vcmc8L2E+PGJyPg0KPGI+U3ViamVjdDo8L2I+IFRoZSB2YWx1ZSBvZiB0aGUgJnF1b3Q7bG9j
YWwtdXVpZCZxdW90OyB0byBiZSBpbnNlcnRlZCBieSBTQkNzPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHByZT48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwgTmFycm93JnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPlBhdWwsPC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCBOYXJyb3cmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+SSBoYXZlIGEgY29tbWVudCBjb25jZXJuaW5nIGZvbG93aW5nIHRleHQgaW4gU2Vj
dGlvbiA3Ojwvc3Bhbj48YnI+PGJyPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJtYXJn
aW4tbGVmdDo2MC4wcHQiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCBOYXJy
b3cmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPiBJZiBhIFNJUCBtZXNzYWdlIGhh
dmluZyBubyBTZXNzaW9uLUlEIGhlYWRlciBpcyByZWNlaXZlZCBieSBhbjxvOnA+PC9vOnA+PC9z
cGFuPjwvcHJlPg0KPHByZSBzdHlsZT0ibWFyZ2luLWxlZnQ6NjAuMHB0Ij48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwgTmFycm93JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPiZuYnNwOyZuYnNwOyBpbnRlcm1lZGlhcnksIHRoZSBpbnRlcm1lZGlhcnkgTUFZIGFzc2ln
biBhICZxdW90O2xvY2FsLXV1aWQmcXVvdDsgdmFsdWUgdG88bzpwPjwvbzpwPjwvc3Bhbj48L3By
ZT4NCjxwcmUgc3R5bGU9Im1hcmdpbi1sZWZ0OjYwLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsIE5hcnJvdyZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJz
cDsmbmJzcDsgcmVwcmVzZW50IHRoZSBzZW5kaW5nIGVuZHBvaW50IGFuZCBpbnNlcnQgdGhhdCB2
YWx1ZSBpbnRvIGFsbDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZSBzdHlsZT0ibWFyZ2lu
LWxlZnQ6NjAuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwgTmFycm93
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOyZuYnNwOyBzaWduYWxpbmcgbWVz
c2FnZXMgb24gYmVoYWxmIG9mIHRoZSBzZW5kaW5nIGVuZHBvaW50LiZuYnNwOyBJZiB0aGU8bzpw
PjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmUgc3R5bGU9Im1hcmdpbi1sZWZ0OjYwLjBwdCI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsIE5hcnJvdyZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij4mbmJzcDsmbmJzcDsgaW50ZXJtZWRpYXJ5IGlzIGF3YXJlIG9mIGEgJnF1
b3Q7cmVtb3RlJnF1b3Q7IHZhbHVlIHRoYXQgaWRlbnRpZmllcyB0aGU8bzpwPjwvbzpwPjwvc3Bh
bj48L3ByZT4NCjxwcmUgc3R5bGU9Im1hcmdpbi1sZWZ0OjYwLjBwdCI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsIE5hcnJvdyZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij4mbmJzcDsmbmJzcDsgcmVjZWl2aW5nIFVBLCBpdCBNVVNUIGluc2VydCB0aGF0IHZhbHVlIGlm
IGFsc28gaW5zZXJ0aW5nIHRoZSAmcXVvdDtsb2NhbC08bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4N
CjxwcmUgc3R5bGU9Im1hcmdpbi1sZWZ0OjYwLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsIE5hcnJvdyZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDsm
bmJzcDsgdXVpZCZxdW90OyB2YWx1ZS48L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsIE5hcnJvdyZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij5JTU8gdGhlIHZhbHVlIG9mIHRoZSBvZiB0aGUgbG9jYWwtdXVpZCBtdXN0
IGJlIHRoZSBoYXNoZWQgY2FsbC1JRCBvZiB0aGUgaW5jb21taW5nIGNhbGwgbGVnLiA8YnI+PGJy
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwgTmFycm93JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPk90aGVyd2lz
ZSB0aGVyZSBpcyBub3QgcG9zc2libGUgZm9yIGFuIGV4dGVybmFsJm5ic3A7IG1vbml0b3Jpbmcg
ZGV2aWNlIHRvIGNvcnJlbGF0ZSBib3RoIGxlZ3Mgb2YgYSBjYWxsJm5ic3A7IGluIGNhc2Ugb2Yg
YSBmYWlsdXJlPGJyPm9mIHRoZSByZWNlaXZpbmcgZGV2aWNlICggdGhlIHJlY2VpdmluZyBkZXZp
Y2UgZHJvcHMgdGhlIGNhbGwpLiA8YnI+PGJyPlRoYW5rIHlvdTxicj48YnI+PG86cD48L286cD48
L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCBO
YXJyb3cmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+TGF1cmE8L3NwYW4+PG86cD48L286
cD48L3ByZT4NCjxwcmU+PG86cD4mbmJzcDs8L286cD48L3ByZT4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_576A8B541C219D4E9CEB1DF8C19C7B88196A5165MBX07citservers_--

From paulej@packetizer.com  Wed Mar 27 08:41:29 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE8321F91E7 for <insipid@ietfa.amsl.com>; Wed, 27 Mar 2013 08:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QV2ZVR4R8bYA for <insipid@ietfa.amsl.com>; Wed, 27 Mar 2013 08:41:28 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 7A26D21F91D4 for <insipid@ietf.org>; Wed, 27 Mar 2013 08:41:28 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2RFfHls028310 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Mar 2013 11:41:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1364398878; bh=JnptRTFqpaGemaMlPLC0MZpucUePq5ug8yo9/PLDcWI=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=r2fGto6y7N+UW3IA7BlHtqehpqCLRxm4OVUYudBRLdQGXBku+d2M6NxRQuvWvoBGh WSnRcIk8hyC1vXo9GLfgc5wcYliRptwxIz9RLhsqTFnMSU9Zjp8aEcuyRtICiwuki9 Gqz0ms/ZZy2eEe1J9BBOdjCtBbTpjgsa5xU+KYfA=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Brett Tate'" <brett@broadsoft.com>, <insipid@ietf.org>
References: <06b2139a-662a-489d-b24b-a84b26185b34@email.android.com>	<c332aa51-db32-4961-ba7f-899fd44dfd18@email.android.com> <576A8B541C219D4E9CEB1DF8C19C7B88196A5165@MBX07.citservers.local>
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B88196A5165@MBX07.citservers.local>
Date: Wed, 27 Mar 2013 11:41:39 -0400
Message-ID: <01f301ce2b01$92ff0030$b8fd0090$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01F4_01CE2AE0.0BEE71A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMWFLFVyjfpET6lx0EyZxzZbSJ/qwFibi/+AaWtuROWEZcLwA==
Content-Language: en-us
Subject: Re: [Insipid] Fwd: The value of the "local-uuid" to be inserted	by	SBCs
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 27 Mar 2013 15:41:29 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01F4_01CE2AE0.0BEE71A0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Brett,

=20

Yeah, you=E2=80=99re right.  The only suggestion I could give people in =
that case is that if they rely on the Session-ID header, they need to =
ensure it gets consistently applied.  Either the endpoints need to =
generate it or some intermediary needs to insert it.  Some aspects, the =
network admin can control.  But, if one is just monitoring a network and =
expecting consistent usage without putting effort in to ensure =
consistent usage, results will be disappointing.

=20

Paul

=20

From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On =
Behalf Of Brett Tate
Sent: Wednesday, March 27, 2013 11:04 AM
To: Paul E. Jones; insipid@ietf.org
Subject: Re: [Insipid] Fwd: The value of the "local-uuid" to be inserted =
by SBCs

=20

The suggestion sounds okay to me; however the request can fork and =
Call-ID change prior to the Session-ID being added.  Thus even though =
there might not be a better solution, the suggestion does not completely =
resolve the correlation problem. =20

=20

If there are still vendors who reuse Call-ID for correlation or other =
reasons, it might cause the intermediary to add the same local-uuid when =
it potentially isn=E2=80=99t desirable.

=20

=20

From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On =
Behalf Of Paul E. Jones
Sent: Friday, March 22, 2013 12:13 AM
To: insipid@ietf.org
Subject: Re: [Insipid] Fwd: The value of the "local-uuid" to be inserted =
by SBCs

=20

That would be "do others have an opinion on this?"

Paul

=20

  _____ =20

From: "Paul E. Jones" <paulej@packetizer.com>
Sent: Thu Mar 21 23:14:14 EDT 2013
To: insipid@ietf.org
Subject: [Insipid] Fwd: The value of the "local-uuid" to be inserted by =
SBCs


Folks,

In addition to the two other items, there is this suggestion from Laura. =
I think it's reasonable, but I've not written the text, yet.

Do others have only on this?

Paul

  _____ =20

From: Laura Liess <laura.liess.dt@googlemail.com>
Sent: Tue Mar 12 17:21:11 EDT 2013
To: Paul Jones <paulej@packetizer.com>
Cc: insipid@ietf.org
Subject: The value of the "local-uuid" to be inserted by SBCs

=20

Paul,
I have a comment concerning folowing text in Section 7:

 If a SIP message having no Session-ID header is received by an
   intermediary, the intermediary MAY assign a "local-uuid" value to
   represent the sending endpoint and insert that value into all
   signaling messages on behalf of the sending endpoint.  If the
   intermediary is aware of a "remote" value that identifies the
   receiving UA, it MUST insert that value if also inserting the "local-
   uuid" value.
IMO the value of the of the local-uuid must be the hashed call-ID of the =
incomming call leg.=20
Otherwise there is not possible for an external  monitoring device to =
correlate both legs of a call  in case of a failure
of the receiving device ( the receiving device drops the call).=20

Thank you
Laura
=20

------=_NextPart_000_01F4_01CE2AE0.0BEE71A0
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Arial Narrow";
	panose-1:2 11 6 6 2 2 2 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Brett,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Yeah, you=E2=80=99re right.=C2=A0 The only suggestion I could give =
people in that case is that if they rely on the Session-ID header, they =
need to ensure it gets consistently applied.=C2=A0 Either the endpoints =
need to generate it or some intermediary needs to insert it.=C2=A0 Some =
aspects, the network admin can control.=C2=A0 But, if one is just =
monitoring a network and expecting consistent usage without putting =
effort in to ensure consistent usage, results will be =
disappointing.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Paul<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] <b>On Behalf =
Of </b>Brett Tate<br><b>Sent:</b> Wednesday, March 27, 2013 11:04 =
AM<br><b>To:</b> Paul E. Jones; insipid@ietf.org<br><b>Subject:</b> Re: =
[Insipid] Fwd: The value of the &quot;local-uuid&quot; to be inserted by =
SBCs<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The suggestion sounds okay to me; however the request can fork and =
Call-ID change prior to the Session-ID being added.&nbsp; Thus even =
though there might not be a better solution, the suggestion does not =
completely resolve the correlation problem.&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If there are still vendors who reuse Call-ID for correlation or other =
reasons, it might cause the intermediary to add the same local-uuid when =
it potentially isn=E2=80=99t desirable.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:insipid-bounces@ietf.org">insipid-bounces@ietf.org</a> =
[<a =
href=3D"mailto:insipid-bounces@ietf.org">mailto:insipid-bounces@ietf.org<=
/a>] <b>On Behalf Of </b>Paul E. Jones<br><b>Sent:</b> Friday, March 22, =
2013 12:13 AM<br><b>To:</b> <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><br><b>Subject:</b> =
Re: [Insipid] Fwd: The value of the &quot;local-uuid&quot; to be =
inserted by SBCs<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p>That would be &quot;do others =
have an opinion on this?&quot;<o:p></o:p></p><p>Paul<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><hr =
size=3D2 width=3D"100%" align=3Dcenter></span></div><p =
class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
&quot;Paul E. Jones&quot; &lt;<a =
href=3D"mailto:paulej@packetizer.com">paulej@packetizer.com</a>&gt;<br><b=
>Sent:</b> Thu Mar 21 23:14:14 EDT 2013<br><b>To:</b> <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><br><b>Subject:</b> =
[Insipid] Fwd: The value of the &quot;local-uuid&quot; to be inserted by =
SBCs<o:p></o:p></span></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>Folks,<br><br>In addition to the two =
other items, there is this suggestion from Laura. I think it's =
reasonable, but I've not written the text, yet.<br><br>Do others have =
only on this?<br><br>Paul<o:p></o:p></p><div><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></div><p class=3DMsoNormal><b>From:</b> Laura Liess =
&lt;<a =
href=3D"mailto:laura.liess.dt@googlemail.com">laura.liess.dt@googlemail.c=
om</a>&gt;<br><b>Sent:</b> Tue Mar 12 17:21:11 EDT 2013<br><b>To:</b> =
Paul Jones &lt;<a =
href=3D"mailto:paulej@packetizer.com">paulej@packetizer.com</a>&gt;<br><b=
>Cc:</b> <a =
href=3D"mailto:insipid@ietf.org">insipid@ietf.org</a><br><b>Subject:</b> =
The value of the &quot;local-uuid&quot; to be inserted by =
SBCs<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><pre><span =
style=3D'font-family:"Arial =
Narrow","sans-serif"'>Paul,</span><o:p></o:p></pre><pre =
style=3D'margin-bottom:12.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>I have a comment concerning folowing text in =
Section 7:</span><o:p></o:p></pre><pre =
style=3D'margin-left:60.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'><br> If a SIP message having no Session-ID header =
is received by an<o:p></o:p></span></pre><pre =
style=3D'margin-left:60.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>&nbsp;&nbsp; intermediary, the intermediary MAY =
assign a &quot;local-uuid&quot; value to<o:p></o:p></span></pre><pre =
style=3D'margin-left:60.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>&nbsp;&nbsp; represent the sending endpoint and =
insert that value into all<o:p></o:p></span></pre><pre =
style=3D'margin-left:60.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>&nbsp;&nbsp; signaling messages on behalf of the =
sending endpoint.&nbsp; If the<o:p></o:p></span></pre><pre =
style=3D'margin-left:60.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>&nbsp;&nbsp; intermediary is aware of a =
&quot;remote&quot; value that identifies the<o:p></o:p></span></pre><pre =
style=3D'margin-left:60.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>&nbsp;&nbsp; receiving UA, it MUST insert that =
value if also inserting the &quot;local-<o:p></o:p></span></pre><pre =
style=3D'margin-left:60.0pt'><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>&nbsp;&nbsp; uuid&quot; =
value.</span><o:p></o:p></pre><pre style=3D'margin-bottom:12.0pt'><span =
style=3D'font-family:"Arial Narrow","sans-serif"'>IMO the value of the =
of the local-uuid must be the hashed call-ID of the incomming call leg. =
<o:p></o:p></span></pre><pre style=3D'margin-bottom:12.0pt'><span =
style=3D'font-family:"Arial Narrow","sans-serif"'>Otherwise there is not =
possible for an external&nbsp; monitoring device to correlate both legs =
of a call&nbsp; in case of a failure<br>of the receiving device ( the =
receiving device drops the call). <br><br>Thank =
you<o:p></o:p></span></pre><pre><span style=3D'font-family:"Arial =
Narrow","sans-serif"'>Laura</span><o:p></o:p></pre><pre><o:p>&nbsp;</o:p>=
</pre></div></div></div></body></html>
------=_NextPart_000_01F4_01CE2AE0.0BEE71A0--


From gsalguei@cisco.com  Thu Mar 28 20:00:07 2013
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B5AC21F90CC for <insipid@ietfa.amsl.com>; Thu, 28 Mar 2013 20:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GISh646z+o3z for <insipid@ietfa.amsl.com>; Thu, 28 Mar 2013 20:00:06 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id C4E4021F90AF for <insipid@ietf.org>; Thu, 28 Mar 2013 20:00:06 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r2T306Xm027668 for <insipid@ietf.org>; Thu, 28 Mar 2013 23:00:06 -0400 (EDT)
Received: from rtp-vpn3-847.cisco.com (rtp-vpn3-847.cisco.com [10.82.219.83]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r2T305LI000919 for <insipid@ietf.org>; Thu, 28 Mar 2013 23:00:06 -0400 (EDT)
From: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <F822CDD6-4859-424A-8DEC-1509BDE786AF@cisco.com>
Date: Thu, 28 Mar 2013 23:00:05 -0400
To: "insipid@ietf.org" <insipid@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Subject: [Insipid] INSIPID WG IETF86 Minutes
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 03:00:07 -0000

WG,

Here is the draft version of the minutes for the INSIPID session of IETF
86. Many thanks to Charles Eckel and Andrew Allen for taking notes.

http://www.ietf.org/proceedings/86/minutes/minutes-86-insipid

Please review and provide feedback.=20

Also, please take special note of the Action items:

- Action Item: Paul Jones to produce new text for the Terminology =
section that defines a 'Communication Session' in such a way that it =
answers Robert's three scenarios. Robert Sparks agrees to review and =
provide alternative text, if necessary [In Progress]
- Action Item: James Polk to produce text for the Security =
Considerations section that provides some details on spoofing and =
interception of the Session ID.  To be hashed out on list prior to =
updating draft.
- Action Item: Hadriel Kaplan to confirm appropriate version of =
draft-kaplan-session-id [Done]
- Action Item: Hadriel Kaplan to proceed working with ADs to sponsor =
publication of the appropriate version of the Kaplan draft as Historic
- Action Item: Paul Kyzivat to initiate discussion on the list about =
whether (and how) we consider cascading conference bridge call flow =
(Section 9.6)=20
- Action Item: James Polk to initiate discussion on the list about how =
we handle disaggregated media call flow raised by Brett Tate
- Action Item: Hadriel Kaplan to raise on list the backwards =
compatibility request to keep value and remote value in the same order =
(i.e. swapping of value and param not required)
- Action Item: Keith Drage to take to list discussion of whether further =
virtual interims are required to make progress in a timely fashion

Cheers,

Gonzalo & Keith



From brett@broadsoft.com  Fri Mar 29 08:07:56 2013
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6F1521F943F for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 08:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9u9WTSifdcxE for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 08:07:56 -0700 (PDT)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.21]) by ietfa.amsl.com (Postfix) with ESMTP id 57CC621F943C for <insipid@ietf.org>; Fri, 29 Mar 2013 08:07:56 -0700 (PDT)
Received: from CASUMHUB03.citservers.local (172.16.98.219) by smtpedge.partnerhosted.com (172.16.98.247) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 29 Mar 2013 08:10:13 -0700
Received: from MBX07.citservers.local ([fe80::d9a5:240b:376a:aeb6]) by CASUMHUB03.citservers.local ([::1]) with mapi id 14.02.0247.003; Fri, 29 Mar 2013 08:10:12 -0700
From: Brett Tate <brett@broadsoft.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: disaggregated media
Thread-Index: Ac4sjy+oatrlt+cmTc+nRJgRqMlXmA==
Date: Fri, 29 Mar 2013 15:10:11 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B88196A55B2@MBX07.citservers.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.98.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Insipid] disaggregated media
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 15:07:57 -0000

Hi,

Concerning slides-86-insipid-5.pdf's "Disaggregated Media" slide, I thought=
 that I'd mention that the call flow is a variant of the one that I origina=
lly sent.  I mention it mainly because the variant appears more like a conf=
erence since it relays media and doesn't accommodate end-to-end ACK; althou=
gh, I'm not sure if that'd change anyone's opinion on the topic.

http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html

Since there was some debate concerning if Session-ID values should be more =
like the slide or the above email, I thought that I'd mention that a common=
 scenario is that INVITE to "Bob's computer" is quickly declined or cancell=
ed after "Bob's phone" answers the INVITE.  That is one of the reasons why =
the Session-ID values mentioned within the above email might be more approp=
riate.  However if the Session-ID values of the slide is preferred, should =
"M" continue to be part of the Session-ID (i.e. instead of switching to be =
"A" and "Bp") when "Bob's computer" is not part of the answered call?

Thanks,
Brett

This email is intended solely for the person or entity to which it is addre=
ssed and may contain confidential and/or privileged information. If you are=
 not the intended recipient and have received this email in error, please n=
otify BroadSoft, Inc. immediately by replying to this message, and destroy =
all copies of this message, along with any attachment, prior to reading, di=
stributing or copying it.

From brett@broadsoft.com  Fri Mar 29 09:32:05 2013
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA4F21F9409 for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 09:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIduWD4pwXmV for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 09:32:03 -0700 (PDT)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.204]) by ietfa.amsl.com (Postfix) with ESMTP id C6A6A21F9407 for <insipid@ietf.org>; Fri, 29 Mar 2013 09:32:03 -0700 (PDT)
Received: from CASUMHUB04.citservers.local (172.16.98.225) by Xedge02.citservers.local (172.16.98.248) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 29 Mar 2013 09:34:20 -0700
Received: from MBX07.citservers.local ([fe80::d9a5:240b:376a:aeb6]) by CASUMHUB04.citservers.local ([::1]) with mapi id 14.02.0247.003; Fri, 29 Mar 2013 09:34:20 -0700
From: Brett Tate <brett@broadsoft.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: disaggregated media: call origination
Thread-Index: Ac4smvCDkRVJESN5T7qqv8kqRFB4yQ==
Date: Fri, 29 Mar 2013 16:34:19 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B88196A55D1@MBX07.citservers.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.98.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Insipid] disaggregated media: call origination
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 16:32:05 -0000

Hi,

As I mentioned within the November 13 email, there is a similar disaggregat=
ed media call flow when Bobs-phone originates a call to Alice.  Bobs-comput=
er is pulled into the call setup so both audio and video can be offered to =
Alice.

Based upon prior feedback and the slide presented at IETF 86, some within i=
nsipid prefer the B2BUA to assign Session-ID like a conferencing server (ev=
en though it doesn't send/receive media) during disaggregated media situati=
ons.  Thus I assume some prefer the B2BUA to not allow the session-ID value=
s to go end-to-end within the following call flow.  I think that the follow=
ing indicates their preference.  Hopefully the picture doesn't get too corr=
upted.

Session-ID
----  Alice        B2BUA    Bobs-phone Bobs-computer
 {Bp}   |            |<---INVITE--|          |
 {M}    |            |---INVITE------------->|
 {Bc,M} |            |<--200 OK--------------|
 {M,Bc} |            |---ACK---------------->|
 {M}    |<---INVITE--|            |          |
 {A,M}  |---200 OK-->|            |          |
 {M,Bp} |            |---200 OK-->|          |
 {Bp,M} |            |<---ACK-----|          |
 {M,A}  |<-----ACK---|            |          |
 {M,A   |<-reINVITE--|            |          |
 {A,M}  |---200 OK-->|            |          |
 {M,Bp} |            |-reINVITE-->|          |
 {M,Bc} |            |-reINVITE------------->|
 {Bp,M} |            |<--200 OK---|          |
 {Bc,M} |            |<--200 OK--------------|
 {M,A}  |<-----ACK---|            |          |
 {M,Bp} |            |---ACK----->|          |
 {M,Bc} |            |---ACK---------------->|


Please reply if you have an opinion on the topic.

Thanks,
Brett

This email is intended solely for the person or entity to which it is addre=
ssed and may contain confidential and/or privileged information. If you are=
 not the intended recipient and have received this email in error, please n=
otify BroadSoft, Inc. immediately by replying to this message, and destroy =
all copies of this message, along with any attachment, prior to reading, di=
stributing or copying it.

From jmpolk@cisco.com  Fri Mar 29 10:39:21 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E98721F939B for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 10:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DhvWZphna1u for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 10:39:20 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 563F821F93FD for <insipid@ietf.org>; Fri, 29 Mar 2013 10:39:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3206; q=dns/txt; s=iport; t=1364578760; x=1365788360; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=NT23lDiA967+Vcm+gJ4Lh76I8jM++j9OqN2KxP9DhP8=; b=WvsBWHv46JVl/BnLaoV5EXykDkJ+NdLr72eyMNWXW9RH4wXIW/u5jDgP OEQXyMQ7G0wlv2cCYbjcIaj3i9ejI0q3LvbYpurNct2Vt3+fe/WXEadu0 z6mgtfqeSAiJh+XFKPb8waAE6CQK0hX1DU68ftqbuhNHL1MdaVWE3FtML I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAHXQVVGtJV2c/2dsb2JhbABDgzq/KIEKFnSCHwEBAQQBAQE1Ai4GGwcEGAkVEA8KDjAGARIJiAsMwACNZQoGgTmDQAOIep58gykegS4EBRc
X-IronPort-AV: E=Sophos;i="4.87,374,1363132800"; d="scan'208";a="192980095"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 29 Mar 2013 17:39:20 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2THdJgL011982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Mar 2013 17:39:19 GMT
Message-Id: <201303291739.r2THdJgL011982@rcdn-core-5.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 29 Mar 2013 12:38:29 -0500
To: Brett Tate <brett@broadsoft.com>, "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B88196A55B2@MBX07.citservers. local>
References: <576A8B541C219D4E9CEB1DF8C19C7B88196A55B2@MBX07.citservers.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: Re: [Insipid] disaggregated media
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 17:39:21 -0000

At 10:10 AM 3/29/2013, Brett Tate wrote:
>Hi,
>
>Concerning slides-86-insipid-5.pdf's "Disaggregated Media" slide, I 
>thought that I'd mention that the call flow is a variant of the one 
>that I originally sent.  I mention it mainly because the variant 
>appears more like a conference since it relays media and doesn't 
>accommodate end-to-end ACK; although, I'm not sure if that'd change 
>anyone's opinion on the topic.
>
>http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html
>
>Since there was some debate concerning if Session-ID values should 
>be more like the slide or the above email, I thought that I'd 
>mention that a common scenario is that INVITE to "Bob's computer" is 
>quickly declined or cancelled after "Bob's phone" answers the INVITE.

Brett - If this INVITE to Bob's computer is CANCELled (such as in the 
case of concurrent forking), then the SIP state engine for that UA 
would become "inactive" and would no longer be part of any active 
call, therefore wouldn't this defeat the purpose of originally having 
the intent of only the video being sent and displayed on Bob's 
computer? i.e., wouldn't the only active part of the call be from 
Alice to Bob's phone (in audio only mode)?

>That is one of the reasons why the Session-ID values mentioned 
>within the above email might be more appropriate.  However if the 
>Session-ID values of the slide is preferred,

I don't know if the slide was preferred, but I answered your email 
with a diagram on Jan 11th (the final message on the thread) and no 
one said I was wrong, so that's what I built the slide upon.

>should "M" continue to be part of the Session-ID (i.e. instead of 
>switching to be "A" and "Bp") when "Bob's computer" is not part of 
>the answered call?

That was one of the open questions to the room. If a conference call, 
I'd say yes. If not a conference, I'd say you have some special 
handling within the B2BUA that does the SDP splitting and some in the 
room wanted no special handling rules regardless the entity type - 
something I wasn't a fan of, BTW. I just believe one needs to clearly 
describe the scenario so everyone codes every entity the same way for 
every special case. I agree with limiting the number of special 
cases, but we're burying our heads in the sand if we think we can 
contain vendors from doing special one-offs, and customers from 
asking for one-offs. If we hope to be successful as a WG, we need to 
address the obvious one-offs in a uniform way IMO. That does NOT mean 
every one-off, just limited set of obvious ones.

James


>Thanks,
>Brett
>
>This email is intended solely for the person or entity to which it 
>is addressed and may contain confidential and/or privileged 
>information. If you are not the intended recipient and have received 
>this email in error, please notify BroadSoft, Inc. immediately by 
>replying to this message, and destroy all copies of this message, 
>along with any attachment, prior to reading, distributing or copying it.
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
>https://www.ietf.org/mailman/listinfo/insipid


From jmpolk@cisco.com  Fri Mar 29 10:47:19 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46FCF21F92F6 for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 10:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gFi-xPYe3hXP for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 10:47:18 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 064EA21F8EFC for <insipid@ietf.org>; Fri, 29 Mar 2013 10:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3024; q=dns/txt; s=iport; t=1364579238; x=1365788838; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=RPm3ZmyxvdrZNcWkRoe5FdkW4c1ayei6Ithe1ZCVwe4=; b=dYCjn2pHOwGpFCD9T+o76wZo3uCwXmseYxo9AL+68j9Y8+mafzyl6u/d ixHcvNkhnrVXjLYXiztBcv64v8FuFZgqec/icken7MHqL6ZzgkDpA1BjN ztmh8HL28XdW2vY9tK3F3tZRDl0snHDAHs+bdBuyYk2sgkTR7/4QClthn w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFADvTVVGtJXG8/2dsb2JhbABDgzq/KIEKFnSCHwEBAQQBAQEkEQI0GwcEGAkVEA8KDjAGARKIFAy/fASNZYFJg0ADiHqefIMpHoE3
X-IronPort-AV: E=Sophos;i="4.87,374,1363132800"; d="scan'208";a="189990535"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-9.cisco.com with ESMTP; 29 Mar 2013 17:47:17 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2THlHFO006920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Mar 2013 17:47:17 GMT
Message-Id: <201303291747.r2THlHFO006920@rcdn-core2-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 29 Mar 2013 12:46:26 -0500
To: Brett Tate <brett@broadsoft.com>, "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B88196A55D1@MBX07.citservers. local>
References: <576A8B541C219D4E9CEB1DF8C19C7B88196A55D1@MBX07.citservers.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: Re: [Insipid] disaggregated media: call origination
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 17:47:19 -0000

At 11:34 AM 3/29/2013, Brett Tate wrote:
>Hi,
>
>As I mentioned within the November 13 email, there is a similar 
>disaggregated media call flow when Bobs-phone originates a call to 
>Alice.  Bobs-computer is pulled into the call setup so both audio 
>and video can be offered to Alice.

How in SIP is this done without sending Bob's computer an INVITE?


>Based upon prior feedback and the slide presented at IETF 86, some 
>within insipid prefer the B2BUA to assign Session-ID like a 
>conferencing server (even though it doesn't send/receive media) 
>during disaggregated media situations.  Thus I assume some prefer 
>the B2BUA to not allow the session-ID values to go end-to-end within 
>the following call flow.

To me, it's not a question of allowing the session-UUIDs to go 
end-to-end, it's a question of you have 3 UAs involved, so you have 3 
UUIDs for a 2 UUID field value. How exactly is that reconciled, is 
what I want to know?

>I think that the following indicates their preference.

I have not ever seen anyone describe (let alone display) any call 
flow originating from Bob's side, so if "they" have a preference, 
"they" are keeping it to themselves  ;-)

But I agree that if we're going to show an example from Alice's side 
for Disaggregated Media, we need to include one from Bob's side as well.

James

>Hopefully the picture doesn't get too corrupted.
>
>Session-ID
>----  Alice        B2BUA    Bobs-phone Bobs-computer
>  {Bp}   |            |<---INVITE--|          |
>  {M}    |            |---INVITE------------->|
>  {Bc,M} |            |<--200 OK--------------|
>  {M,Bc} |            |---ACK---------------->|
>  {M}    |<---INVITE--|            |          |
>  {A,M}  |---200 OK-->|            |          |
>  {M,Bp} |            |---200 OK-->|          |
>  {Bp,M} |            |<---ACK-----|          |
>  {M,A}  |<-----ACK---|            |          |
>  {M,A   |<-reINVITE--|            |          |
>  {A,M}  |---200 OK-->|            |          |
>  {M,Bp} |            |-reINVITE-->|          |
>  {M,Bc} |            |-reINVITE------------->|
>  {Bp,M} |            |<--200 OK---|          |
>  {Bc,M} |            |<--200 OK--------------|
>  {M,A}  |<-----ACK---|            |          |
>  {M,Bp} |            |---ACK----->|          |
>  {M,Bc} |            |---ACK---------------->|
>
>
>Please reply if you have an opinion on the topic.
>
>Thanks,
>Brett
>
>This email is intended solely for the person or entity to which it 
>is addressed and may contain confidential and/or privileged 
>information. If you are not the intended recipient and have received 
>this email in error, please notify BroadSoft, Inc. immediately by 
>replying to this message, and destroy all copies of this message, 
>along with any attachment, prior to reading, distributing or copying it.
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
>https://www.ietf.org/mailman/listinfo/insipid


From brett@broadsoft.com  Fri Mar 29 13:00:05 2013
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0EF821F842D for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 13:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G6WzJYzpvSso for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 13:00:03 -0700 (PDT)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.21]) by ietfa.amsl.com (Postfix) with ESMTP id 98D3221F842B for <insipid@ietf.org>; Fri, 29 Mar 2013 13:00:03 -0700 (PDT)
Received: from CASUMHUB03.citservers.local (172.16.98.219) by smtpedge.partnerhosted.com (172.16.98.247) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 29 Mar 2013 13:02:20 -0700
Received: from MBX07.citservers.local ([fe80::d9a5:240b:376a:aeb6]) by CASUMHUB03.citservers.local ([::1]) with mapi id 14.02.0247.003; Fri, 29 Mar 2013 13:02:20 -0700
From: Brett Tate <brett@broadsoft.com>
To: James Polk <jmpolk@cisco.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] disaggregated media: call origination
Thread-Index: AQHOLKXJgNfoekD+QUGLGyLwNeFOcZi9Cu6g
Date: Fri, 29 Mar 2013 20:02:19 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B88196A5629@MBX07.citservers.local>
References: <576A8B541C219D4E9CEB1DF8C19C7B88196A55D1@MBX07.citservers.local> <201303291747.r2THlHFO006920@rcdn-core2-1.cisco.com>
In-Reply-To: <201303291747.r2THlHFO006920@rcdn-core2-1.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.98.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Insipid] disaggregated media: call origination
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 20:00:05 -0000

> >As I mentioned within the November 13 email, there is a similar
> >disaggregated media call flow when Bobs-phone originates a call to
> >Alice.  Bobs-computer is pulled into the call setup so both audio
> >and video can be offered to Alice.
>=20
> How in SIP is this done without sending Bob's computer an INVITE?

As the diagram shows, an INVITE is sent to Bob's computer.  The B2BUA is pr=
oviding a call originating service for Bob.  Thus it sent an INVITE to Bob'=
s computer to attempt to obtain a video offer.

> >Based upon prior feedback and the slide presented at IETF 86, some
> >within insipid prefer the B2BUA to assign Session-ID like a
> >conferencing server (even though it doesn't send/receive media)
> >during disaggregated media situations.  Thus I assume some prefer
> >the B2BUA to not allow the session-ID values to go end-to-end within
> >the following call flow.
>=20
> To me, it's not a question of allowing the session-UUIDs to go
> end-to-end, it's a question of you have 3 UAs involved, so you have 3
> UUIDs for a 2 UUID field value. How exactly is that reconciled, is
> what I want to know?

I'd like to know that also. :)  I mentioned end-to-end because of REQ3; thu=
s, it is just a matter of deciding how best to ignore that requirement.

 REQ3: The solution must require that the identifier, if present, pass
 unchanged through SIP B2BUAs or other intermediaries.

> >I think that the following indicates their preference.
>=20
> I have not ever seen anyone describe (let alone display) any call
> flow originating from Bob's side, so if "they" have a preference,
> "they" are keeping it to themselves  ;-)

My apologies if I was being overly presumptuous.  I was extrapolating the s=
lides and prior comments associated with "disaggregated media" call termina=
tion to also apply to "disaggregated media" call origination.

> But I agree that if we're going to show an example from Alice's side
> for Disaggregated Media, we need to include one from Bob's side as
> well.
>=20
> James
>=20
> >Hopefully the picture doesn't get too corrupted.
> >
> >Session-ID
> >----  Alice        B2BUA    Bobs-phone Bobs-computer
> >  {Bp}   |            |<---INVITE--|          |
> >  {M}    |            |---INVITE------------->|
> >  {Bc,M} |            |<--200 OK--------------|
> >  {M,Bc} |            |---ACK---------------->|
> >  {M}    |<---INVITE--|            |          |
> >  {A,M}  |---200 OK-->|            |          |
> >  {M,Bp} |            |---200 OK-->|          |
> >  {Bp,M} |            |<---ACK-----|          |
> >  {M,A}  |<-----ACK---|            |          |
> >  {M,A   |<-reINVITE--|            |          |
> >  {A,M}  |---200 OK-->|            |          |
> >  {M,Bp} |            |-reINVITE-->|          |
> >  {M,Bc} |            |-reINVITE------------->|
> >  {Bp,M} |            |<--200 OK---|          |
> >  {Bc,M} |            |<--200 OK--------------|
> >  {M,A}  |<-----ACK---|            |          |
> >  {M,Bp} |            |---ACK----->|          |
> >  {M,Bc} |            |---ACK---------------->|
> >
> >
> >Please reply if you have an opinion on the topic.


From brett@broadsoft.com  Fri Mar 29 13:20:36 2013
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60CC121F8BFD for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 13:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ie-IzWu0ulnw for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 13:20:34 -0700 (PDT)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.21]) by ietfa.amsl.com (Postfix) with ESMTP id E1B3B21F8BF6 for <insipid@ietf.org>; Fri, 29 Mar 2013 13:20:32 -0700 (PDT)
Received: from CASUMHUB03.citservers.local (172.16.98.219) by smtpedge.partnerhosted.com (172.16.98.247) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 29 Mar 2013 13:22:50 -0700
Received: from MBX07.citservers.local ([fe80::d9a5:240b:376a:aeb6]) by CASUMHUB03.citservers.local ([::1]) with mapi id 14.02.0247.003; Fri, 29 Mar 2013 13:22:50 -0700
From: Brett Tate <brett@broadsoft.com>
To: James Polk <jmpolk@cisco.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] disaggregated media
Thread-Index: AQHOLKSqS3qMuTqTBUyImtYBWHBu1Zi8+g8g
Date: Fri, 29 Mar 2013 20:22:50 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B88196A5637@MBX07.citservers.local>
References: <576A8B541C219D4E9CEB1DF8C19C7B88196A55B2@MBX07.citservers.local> <201303291739.r2THdJgL011982@rcdn-core-5.cisco.com>
In-Reply-To: <201303291739.r2THdJgL011982@rcdn-core-5.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.98.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Insipid] disaggregated media
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 20:20:36 -0000

Thanks for the response.  Reply is inline.

> >Concerning slides-86-insipid-5.pdf's "Disaggregated Media" slide, I
> >thought that I'd mention that the call flow is a variant of the one
> >that I originally sent.  I mention it mainly because the variant
> >appears more like a conference since it relays media and doesn't
> >accommodate end-to-end ACK; although, I'm not sure if that'd change
> >anyone's opinion on the topic.
> >
> >http://www.ietf.org/mail-archive/web/insipid/current/msg00429.html
> >
> >Since there was some debate concerning if Session-ID values should
> >be more like the slide or the above email, I thought that I'd
> >mention that a common scenario is that INVITE to "Bob's computer" is
> >quickly declined or cancelled after "Bob's phone" answers the INVITE.
>=20
> Brett - If this INVITE to Bob's computer is CANCELled (such as in the
> case of concurrent forking), then the SIP state engine for that UA
> would become "inactive" and would no longer be part of any active
> call, therefore wouldn't this defeat the purpose of originally having
> the intent of only the video being sent and displayed on Bob's
> computer?=20

The service allows the called party (Bob) to decide to answer audio only (i=
.e. phone) or both audio/video (i.e. phone and computer).

> i.e., wouldn't the only active part of the call be from
> Alice to Bob's phone (in audio only mode)?

Yes; since Bob decided not to answer video.

> >That is one of the reasons why the Session-ID values mentioned
> >within the above email might be more appropriate.  However if the
> >Session-ID values of the slide is preferred,
>=20
> I don't know if the slide was preferred, but I answered your email
> with a diagram on Jan 11th (the final message on the thread) and no
> one said I was wrong, so that's what I built the slide upon.

My impression from the 1/15 email was that the authors and working group we=
re still thinking about it.

http://www.ietf.org/mail-archive/web/insipid/current/msg00457.html=20

The slide doesn't appear to indicate your reply (at least the snippet shown=
 below); however the slide does reflect the response from Paul Jones and Pa=
ul Kyzivat.  I currently don't have a strong preference.

"However,
 - from the B2BUA to Bob's phone, the Session-ID should be (A,Bp)
and
 - from the B2BUA to Bob's computer, the Session-ID should be (A,Bc)"


> >should "M" continue to be part of the Session-ID (i.e. instead of
> >switching to be "A" and "Bp") when "Bob's computer" is not part of
> >the answered call?
>=20
> That was one of the open questions to the room. If a conference call,
> I'd say yes. If not a conference, I'd say you have some special
> handling within the B2BUA that does the SDP splitting and some in the
> room wanted no special handling rules regardless the entity type -
> something I wasn't a fan of, BTW. I just believe one needs to clearly
> describe the scenario so everyone codes every entity the same way for
> every special case. I agree with limiting the number of special
> cases, but we're burying our heads in the sand if we think we can
> contain vendors from doing special one-offs, and customers from
> asking for one-offs. If we hope to be successful as a WG, we need to
> address the obvious one-offs in a uniform way IMO. That does NOT mean
> every one-off, just limited set of obvious ones.


From eckelcu@cisco.com  Fri Mar 29 13:22:42 2013
Return-Path: <eckelcu@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02CDD21F8C2C for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 13:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gLSATDjP8PMI for <insipid@ietfa.amsl.com>; Fri, 29 Mar 2013 13:22:39 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 071B321F8C1A for <insipid@ietf.org>; Fri, 29 Mar 2013 13:22:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4114; q=dns/txt; s=iport; t=1364588559; x=1365798159; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=LBaoXDmrkMqXcEs3vjpQojQoLzmAj3o12/pcGbedlUw=; b=dpoJvoDXNPMMChN8x6FafidfonOXwuxxsbsIAhgyu1V1SsS9Efm1lkJN 9RdoOe7d3eKNTmKyS0oYT3Zrlqj47gOjvjHVR5pl7Gih2YySRyTVOXZ8E mcROLvngLk/4w5UU41wvChrZCfeTXZkDqvRuE1q2cBBudEW3iVx1+idIm E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAIv3VVGtJV2a/2dsb2JhbABDgzq/KYEKFnSCHwEBAQQBAQEkEzQXBAIBCBEEAQELFAkHJwsUCQgBAQQBEggTh3gBDL97BI1lgREmEgaCWWEDp3aDC4FzNQ
X-IronPort-AV: E=Sophos;i="4.87,374,1363132800"; d="scan'208";a="190028913"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 29 Mar 2013 20:22:38 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2TKMcYE026362 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 29 Mar 2013 20:22:38 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.144]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Fri, 29 Mar 2013 15:22:37 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Brett Tate <brett@broadsoft.com>, "James Polk (jmpolk)" <jmpolk@cisco.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] disaggregated media: call origination
Thread-Index: Ac4smvCDkRVJESN5T7qqv8kqRFB4yQACobgsAA8wsIAACgwnMA==
Date: Fri, 29 Mar 2013 20:22:37 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828047DF088@xmb-aln-x08.cisco.com>
References: <576A8B541C219D4E9CEB1DF8C19C7B88196A55D1@MBX07.citservers.local> <201303291747.r2THlHFO006920@rcdn-core2-1.cisco.com> <576A8B541C219D4E9CEB1DF8C19C7B88196A5629@MBX07.citservers.local>
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B88196A5629@MBX07.citservers.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.50]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Insipid] disaggregated media: call origination
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Mar 2013 20:22:42 -0000

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> Behalf Of Brett Tate
> Sent: Friday, March 29, 2013 1:02 PM
> To: James Polk (jmpolk); insipid@ietf.org
> Subject: Re: [Insipid] disaggregated media: call origination
>=20
> > >As I mentioned within the November 13 email, there is a similar
> > >disaggregated media call flow when Bobs-phone originates a call to
> > >Alice.  Bobs-computer is pulled into the call setup so both audio
> > >and video can be offered to Alice.
> >
> > How in SIP is this done without sending Bob's computer an INVITE?
>=20
> As the diagram shows, an INVITE is sent to Bob's computer.  The B2BUA is
> providing a call originating service for Bob.  Thus it sent an INVITE to =
Bob's
> computer to attempt to obtain a video offer.
>=20
> > >Based upon prior feedback and the slide presented at IETF 86, some
> > >within insipid prefer the B2BUA to assign Session-ID like a
> > >conferencing server (even though it doesn't send/receive media)
> > >during disaggregated media situations.  Thus I assume some prefer
> > >the B2BUA to not allow the session-ID values to go end-to-end within
> > >the following call flow.
> >
> > To me, it's not a question of allowing the session-UUIDs to go
> > end-to-end, it's a question of you have 3 UAs involved, so you have 3
> > UUIDs for a 2 UUID field value. How exactly is that reconciled, is
> > what I want to know?
>=20
> I'd like to know that also. :)  I mentioned end-to-end because of REQ3; t=
hus,
> it is just a matter of deciding how best to ignore that requirement.
>=20
>  REQ3: The solution must require that the identifier, if present, pass
>  unchanged through SIP B2BUAs or other intermediaries.

Perhaps this requirement needs be to expanded a bit to differentiate betwee=
n proxies and B2BUA. For a proxy, in think the existing wording of Req 3 is=
 fine. For a B2BUA, the requirement needs to be changed to state that 'M', =
in this example, remains unchanged rather than the entire identifier remain=
s unchanged.

Cheers,
Charles
=20
> > >I think that the following indicates their preference.
> >
> > I have not ever seen anyone describe (let alone display) any call
> > flow originating from Bob's side, so if "they" have a preference,
> > "they" are keeping it to themselves  ;-)
>=20
> My apologies if I was being overly presumptuous.  I was extrapolating the
> slides and prior comments associated with "disaggregated media" call
> termination to also apply to "disaggregated media" call origination.
>=20
> > But I agree that if we're going to show an example from Alice's side
> > for Disaggregated Media, we need to include one from Bob's side as
> > well.
> >
> > James
> >
> > >Hopefully the picture doesn't get too corrupted.
> > >
> > >Session-ID
> > >----  Alice        B2BUA    Bobs-phone Bobs-computer
> > >  {Bp}   |            |<---INVITE--|          |
> > >  {M}    |            |---INVITE------------->|
> > >  {Bc,M} |            |<--200 OK--------------|
> > >  {M,Bc} |            |---ACK---------------->|
> > >  {M}    |<---INVITE--|            |          |
> > >  {A,M}  |---200 OK-->|            |          |
> > >  {M,Bp} |            |---200 OK-->|          |
> > >  {Bp,M} |            |<---ACK-----|          |
> > >  {M,A}  |<-----ACK---|            |          |
> > >  {M,A   |<-reINVITE--|            |          |
> > >  {A,M}  |---200 OK-->|            |          |
> > >  {M,Bp} |            |-reINVITE-->|          |
> > >  {M,Bc} |            |-reINVITE------------->|
> > >  {Bp,M} |            |<--200 OK---|          |
> > >  {Bc,M} |            |<--200 OK--------------|
> > >  {M,A}  |<-----ACK---|            |          |
> > >  {M,Bp} |            |---ACK----->|          |
> > >  {M,Bc} |            |---ACK---------------->|
> > >
> > >
> > >Please reply if you have an opinion on the topic.
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid

From jmpolk@cisco.com  Sun Mar 31 12:53:41 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E04021F87C5 for <insipid@ietfa.amsl.com>; Sun, 31 Mar 2013 12:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108
X-Spam-Level: 
X-Spam-Status: No, score=-108 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XiEjg9kKoVUY for <insipid@ietfa.amsl.com>; Sun, 31 Mar 2013 12:53:40 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8D01E21F87A4 for <insipid@ietf.org>; Sun, 31 Mar 2013 12:53:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4948; q=dns/txt; s=iport; t=1364759620; x=1365969220; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=G8zMEY6cHHqZ3mbzyeqn6zG0DhhKp/ffJExxKYQMgPk=; b=gn8owNBr3Cp0VlHBVI5c+r7gZ4Wrq0t1pF0CG2P3HtjJ4CbnV8w9dzjE vwtSwaULBmilVUJUTtu3zPobtzeYd1XCSPzy4npd2Dk1u33pWUFMYOx8y yt7GSBAePSnVJcC2OnPTbeG2iH8beEhm35uOa9VjlicGBkgow+vEn6omv s=;
X-IronPort-AV: E=Sophos;i="4.87,383,1363132800"; d="scan'208";a="193385620"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-8.cisco.com with ESMTP; 31 Mar 2013 19:53:40 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2VJrdGo009354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Mar 2013 19:53:40 GMT
Message-Id: <201303311953.r2VJrdGo009354@rcdn-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 31 Mar 2013 14:52:44 -0500
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Brett Tate <brett@broadsoft.com>, "James Polk (jmpolk)" <jmpolk@cisco.com>, "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828047DF088@xmb-aln-x08.cisco .com>
References: <576A8B541C219D4E9CEB1DF8C19C7B88196A55D1@MBX07.citservers.local> <201303291747.r2THlHFO006920@rcdn-core2-1.cisco.com> <576A8B541C219D4E9CEB1DF8C19C7B88196A5629@MBX07.citservers.local> <92B7E61ADAC1BB4F941F943788C08828047DF088@xmb-aln-x08.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: Re: [Insipid] disaggregated media: call origination
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 31 Mar 2013 19:53:41 -0000

At 03:22 PM 3/29/2013, Charles Eckel (eckelcu) wrote:
> > -----Original Message-----
> > From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> > Behalf Of Brett Tate
> > Sent: Friday, March 29, 2013 1:02 PM
> > To: James Polk (jmpolk); insipid@ietf.org
> > Subject: Re: [Insipid] disaggregated media: call origination
> >
> > > >As I mentioned within the November 13 email, there is a similar
> > > >disaggregated media call flow when Bobs-phone originates a call to
> > > >Alice.  Bobs-computer is pulled into the call setup so both audio
> > > >and video can be offered to Alice.
> > >
> > > How in SIP is this done without sending Bob's computer an INVITE?
> >
> > As the diagram shows, an INVITE is sent to Bob's computer.  The B2BUA is
> > providing a call originating service for Bob.  Thus it sent an 
> INVITE to Bob's
> > computer to attempt to obtain a video offer.
> >
> > > >Based upon prior feedback and the slide presented at IETF 86, some
> > > >within insipid prefer the B2BUA to assign Session-ID like a
> > > >conferencing server (even though it doesn't send/receive media)
> > > >during disaggregated media situations.  Thus I assume some prefer
> > > >the B2BUA to not allow the session-ID values to go end-to-end within
> > > >the following call flow.
> > >
> > > To me, it's not a question of allowing the session-UUIDs to go
> > > end-to-end, it's a question of you have 3 UAs involved, so you have 3
> > > UUIDs for a 2 UUID field value. How exactly is that reconciled, is
> > > what I want to know?
> >
> > I'd like to know that also. :)  I mentioned end-to-end because of 
> REQ3; thus,
> > it is just a matter of deciding how best to ignore that requirement.
> >
> >  REQ3: The solution must require that the identifier, if present, pass
> >  unchanged through SIP B2BUAs or other intermediaries.
>
>Perhaps this requirement needs be to expanded a bit to differentiate 
>between proxies and B2BUA. For a proxy, in think the existing 
>wording of Req 3 is fine. For a B2BUA, the requirement needs to be 
>changed to state that 'M', in this example, remains unchanged rather 
>than the entire identifier remains unchanged.

I see what you're saying, but the tricky think is here we want any 
SIP intermediary to pass a received Session-ID header-value unchanged 
through the intermediary, and yet allow B2BUA's that are part of any 
forking or call origination to swap one UUID for another. The best 
example of this is in the solution doc, the 3PCC example. That is not 
the only example of where this will need to occur, but it's a good 
one to point at. If you or everyone agrees (roughly ;-), the wording 
of REQ3 gets more delicate, and longer. I'm not opposed to that 
outcome, just would like to see offered text from someone(s)...

James


>Cheers,
>Charles
>
> > > >I think that the following indicates their preference.
> > >
> > > I have not ever seen anyone describe (let alone display) any call
> > > flow originating from Bob's side, so if "they" have a preference,
> > > "they" are keeping it to themselves  ;-)
> >
> > My apologies if I was being overly presumptuous.  I was extrapolating the
> > slides and prior comments associated with "disaggregated media" call
> > termination to also apply to "disaggregated media" call origination.
> >
> > > But I agree that if we're going to show an example from Alice's side
> > > for Disaggregated Media, we need to include one from Bob's side as
> > > well.
> > >
> > > James
> > >
> > > >Hopefully the picture doesn't get too corrupted.
> > > >
> > > >Session-ID
> > > >----  Alice        B2BUA    Bobs-phone Bobs-computer
> > > >  {Bp}   |            |<---INVITE--|          |
> > > >  {M}    |            |---INVITE------------->|
> > > >  {Bc,M} |            |<--200 OK--------------|
> > > >  {M,Bc} |            |---ACK---------------->|
> > > >  {M}    |<---INVITE--|            |          |
> > > >  {A,M}  |---200 OK-->|            |          |
> > > >  {M,Bp} |            |---200 OK-->|          |
> > > >  {Bp,M} |            |<---ACK-----|          |
> > > >  {M,A}  |<-----ACK---|            |          |
> > > >  {M,A   |<-reINVITE--|            |          |
> > > >  {A,M}  |---200 OK-->|            |          |
> > > >  {M,Bp} |            |-reINVITE-->|          |
> > > >  {M,Bc} |            |-reINVITE------------->|
> > > >  {Bp,M} |            |<--200 OK---|          |
> > > >  {Bc,M} |            |<--200 OK--------------|
> > > >  {M,A}  |<-----ACK---|            |          |
> > > >  {M,Bp} |            |---ACK----->|          |
> > > >  {M,Bc} |            |---ACK---------------->|
> > > >
> > > >
> > > >Please reply if you have an opinion on the topic.
> >
> > _______________________________________________
> > insipid mailing list
> > insipid@ietf.org
> > https://www.ietf.org/mailman/listinfo/insipid

