
From Peter.Dawes@vodafone.com  Wed Feb  5 07:45:16 2014
Return-Path: <Peter.Dawes@vodafone.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DBD71A019D for <insipid@ietfa.amsl.com>; Wed,  5 Feb 2014 07:45:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yCSRwL4qof8K for <insipid@ietfa.amsl.com>; Wed,  5 Feb 2014 07:45:12 -0800 (PST)
Received: from mailout07.vodafone.com (mailout07.vodafone.com [195.232.224.76]) by ietfa.amsl.com (Postfix) with ESMTP id 528D31A01DA for <insipid@ietf.org>; Wed,  5 Feb 2014 07:45:12 -0800 (PST)
Received: from mailint07.vodafone.com (localhost [127.0.0.1]) by mailout07.vodafone.com (Postfix) with ESMTP id 0F84B221AB4 for <insipid@ietf.org>; Wed,  5 Feb 2014 16:45:10 +0100 (CET)
Received: from VOEXC02W.internal.vodafone.com (voexc02w.dc-ratingen.de [145.230.101.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint07.vodafone.com (Postfix) with ESMTPS id 01F6B2214C2; Wed,  5 Feb 2014 16:45:10 +0100 (CET)
Received: from VOEXC14W.internal.vodafone.com (145.230.101.16) by VOEXC02W.internal.vodafone.com (145.230.101.22) with Microsoft SMTP Server (TLS) id 14.3.146.2; Wed, 5 Feb 2014 16:45:09 +0100
Received: from VOEXM31W.internal.vodafone.com ([169.254.7.56]) by voexc14w.internal.vodafone.com ([145.230.101.16]) with mapi id 14.03.0146.002; Wed, 5 Feb 2014 16:45:09 +0100
From: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
Thread-Index: Ac8S4EdE5CU+hhHLR+GO87oHorGijQAF//+ZAAIkjeABOfRl8AAZOl4AAo2vTvA=
Date: Wed, 5 Feb 2014 15:45:08 +0000
Message-ID: <4A4F136CBD0E0D44AE1EDE36C4CD9D997395E62D@VOEXM31W.internal.vodafone.com>
References: <4A4F136CBD0E0D44AE1EDE36C4CD9D997394ABE4@VOEXM31W.internal.vodafone.com> <201401162019.s0GKJQHH012866@rcdn-core2-3.cisco.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D997394AD08@VOEXM31W.internal.vodafone.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D997394C66D@VOEXM31W.internal.vodafone.com> <52E13F82.10701@alum.mit.edu>
In-Reply-To: <52E13F82.10701@alum.mit.edu>
Accept-Language: en-GB, 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
Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 15:45:16 -0000

Hello Paul,
Thanks for reviewing the draft. In http://www.ietf.org/id/draft-dawes-insip=
id-logme-solutions-00.txt I have tried to leave all of the text about sendi=
ng logged information to a server as descriptive because the related requir=
ement is not currently in the requirements draft. (was REQ9: A log-me marke=
r may include a locator of the server that collects logs.  This locator is =
known as the diagnostic server identifier and may be an address of a server=
.  A SIP entity can use the diagnostic server identifier to send collected =
logs to the diagnostic server.) Therefore the solutions draft does not desc=
ribe the protocol details of sending logs or the related security. Three al=
ternative next steps are possible (1) REQ 9 or similar gets re-instated and=
 I define log sending and security (2) a requirement is agreed that SIP ent=
ities send some kind of flag to a debug server to indicate that they have a=
 log to collect (3) collection of logs is left outside the scope of log-me.

To me it would seem that (1) is possible to specify, for example regarding =
your questions:
[And how do they discover where to send it, and what protocol to use to do =
so?] the server address could be carried along with the logme marker. The p=
rotocol could be mandated as e-mail (mailto:)
[How do the servers establish trust in this destination when sending logs? =
Is 6.2.2 the whole story? (That doesn't seem very practical.)] Maybe a simp=
le way is to have a white list of domain names on the sending entity
[Since you have said the logs are to be encrypted, *how* are they encrypted=
 so that the server can decode and others cannot?] I imagine that many meth=
ods are possible e.g. TLS or some kind of public key encryption but I would=
 need to consult experts on the best way to do it.

Do you think (1) is possible to specify, or does transmitting logs securely=
 and to the right destination pose too many problems?

Regards,
Peter


-----Original Message-----
From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: 23 January 2014 16:13
To: insipid@ietf.org
Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88

Some questions about this draft:

Solution A:

    User agents and SIP proxies may send logged information to a debug
    server.

And how do they discover where to send it, and what protocol to use to do s=
o?

Solution B:

    Call-Info: mailto:"SIP logging"<siplogs@d1.foocorp.com>;
               purpose=3D"debug"

Is the use of a mailto URL normative, or just an example?

How do the servers establish trust in this destination when sending logs? I=
s 6.2.2 the whole story? (That doesn't seem very practical.)

Since you have said the logs are to be encrypted, *how* are they encrypted =
so that the server can decode and others cannot?

How should the log be formatted within the mail? How is the test case name =
included in the mailed log?

Solution C:

As with solution A, how is the log sent?

	Thanks,
	Paul


On 1/22/14 10:38 PM, Dawes, Peter, Vodafone Group wrote:
> Hello All,
> I have submitted the draft below which describes a solution to the log me=
 requirements and gives a few specific protocol options (the ones that were=
 in clause 7 of the requirements draft reviewed in Vancouver) that could be=
 used to code a log-me marker.

>
> http://www.ietf.org/id/draft-dawes-insipid-logme-solutions-00.txt
>
> This draft has more protocol description than was previously in the requi=
rements draft and tries to give a complete picture of what user agents and =
SIP proxies need to do to provide log-me marking. It would be good if I cou=
ld present this solutions draft at IETF#89 for insipid to discuss.
>
> Rgds,
> Peter
>
>
> -----Original Message-----
> From: Dawes, Peter, Vodafone Group
> Sent: 17 January 2014 05:22
> To: 'James Polk'
> Cc: DRAGE, Keith (Keith) (keith.drage@alcatel-lucent.com);=20
> insipid@ietf.org; Gonzalo Salgueiro (gsalguei@cisco.com)
> Subject: RE: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>
> Thanks James, now submitted as draft-dawes-insipid-logme-reqs-00:
>
> http://datatracker.ietf.org/doc/draft-dawes-insipid-logme-reqs/
>
> Peter
>
> -----Original Message-----
> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of James=20
> Polk
> Sent: 16 January 2014 20:19
> To: Dawes, Peter, Vodafone Group
> Cc: DRAGE, Keith (Keith) (keith.drage@alcatel-lucent.com);=20
> insipid@ietf.org; Gonzalo Salgueiro (gsalguei@cisco.com)
> Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>
> Peter
>
> To be blunt, if you seriously want this draft to be considered for INSIPI=
D WG adoption you need to put "-insipid-" in the filename, and stop putting=
 "-dispatch-" in the filename.
>
> Linking the drafts is simple work for the chairs to do, if that's your co=
ncern.
>
> James
>
> At 11:31 AM 1/16/2014, Dawes, Peter, Vodafone Group wrote:
>> Hello All,
>> Following up from IETF#88 I have uploaded a revised logme=20
>> requirements draft (version -04).
>>
>> https://datatracker.ietf.org/doc/draft-dawes-dispatch-logme-reqs/
>>
>> As per the comments in Vancouver, version -04 does not include REQ9=20
>> regarding a logging server address and the related sub-clause 6.2.2.
>> Also, clause 7 on potential solutions has been removed. These=20
>> requirements seem to be stable now.
>>
>> I will upload a related solutions draft by the end of next week=20
>> (Friday
>> 24) at the latest and I hope we can discuss solution options here on=20
>> the list and then later on at IETF#89 at the beginning of March.
>>
>> Regards,
>> Peter
>> _______________________________________________
>> 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

From paulej@packetizer.com  Wed Feb  5 09:23:24 2014
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4071C1A014B for <insipid@ietfa.amsl.com>; Wed,  5 Feb 2014 09:23:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I_ubjD0hlM_z for <insipid@ietfa.amsl.com>; Wed,  5 Feb 2014 09:23:22 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 915251A00F7 for <insipid@ietf.org>; Wed,  5 Feb 2014 09:23:21 -0800 (PST)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s15HNKnd023839 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Feb 2014 12:23:20 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1391621000; bh=IKV/SiXtbmB8xChOXxwk83YzZTK70/vaktQlbyKP2BY=; h=From:To:Subject:Date:Content-Transfer-Encoding:Content-Type: In-Reply-To:Message-Id:Mime-Version:Reply-To; b=PFJUvoRLw+je4xQ1zTQ6G5rKUPG3eR9HXppXYeeKLyIwv3TjbiWSWSEDB1sD9qa9V iDyI4hvljWLlQnRY8fZBCcurKiYhcJoxu+Kv+QAak2vtJzCA/6bLlqsnAkpVMivZqP tsBVLRSQkNchcf+NPcUmOjVzNoWuHwYCF844QzIg=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Paul E. Jones" <paulej@packetizer.com>, insipid@ietf.org
Date: Wed, 05 Feb 2014 17:23:27 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
In-Reply-To: <em3db05562-6c09-46c6-bf6f-74bb468b6c14@sydney>
Message-Id: <emfa601a7b-633f-4e93-9ce7-dd2648a3de26@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/6.0.19861.0
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-04.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 17:23:24 -0000

Folks,

Any comments on this draft?  If there is general agreement with the=20
backward-compatibility text, we'll then address the other comments=20
received and try to get another draft before the upcoming meeting.

Paul

------ Original Message ------
From: "Paul E. Jones" <paulej@packetizer.com>
To: insipid@ietf.org
Sent: 1/24/2014 11:07:47 PM
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-04.txt

>Folks,
>
>This document was updated to try to address the backward-compatibility=20
>requests made during the last IETF meeting. James took the lead on=20
>revising the text to align with what he believes is the request from=20
>the group.
>
>We still have email messages with comments from Paul K., Keith, and=20
>Brett that have not been reflected in this text. We also need to work=20
>on the security considerations and there may be other matters of a more=
=20
>general nature. However, it was decided to first focus on the call=20
>flows and interworking with the Kaplan draft.
>
>Please review this version and provide feedback, particularly on the=20
>areas of focus, but any comment is welcome, of course.
>
>Cheers!
>Paul
>
>------ Original Message ------
>From: internet-drafts@ietf.org
>To: i-d-announce@ietf.org
>Cc: insipid@ietf.org
>Sent: 1/24/2014 11:02:21 PM
>Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-04.txt
>
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts=20
>>directories.
>>  This draft is a work item of the INtermediary-safe SIP session ID=20
>>Working Group of the IETF.
>>
>>         Title : End-to-End Session Identification in IP-Based=20
>>Multimedia Communication Networks
>>         Authors : Paul E. Jones
>>                           Chris Pearce
>>                           James Polk
>>                           Gonzalo Salgueiro
>>  Filename : draft-ietf-insipid-session-id-04.txt
>>  Pages : 27
>>  Date : 2014-01-24
>>
>>Abstract:
>>    This document describes an end-to-end Session Identifier for use in
>>    IP-based Multimedia Communication systems that enables endpoints,
>>    intermediate devices, and management systems to identify a session
>>    end-to-end, associate multiple endpoints with a given multipoint
>>    conference, track communication sessions when they are redirected,
>>    and associate one or more media flows with a given communication
>>    session.
>>
>>    This document also describes a backwards compatibility mechanism=20
>>for
>>    an existing "in the wild" implementation that is both sufficiently
>>    different than the standard solution and whose implementation will
>>    likely not be updated ever by some vendors.
>>
>>
>>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-04
>>
>>A diff from the previous version is available at:
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-insipid-session-id-04
>>
>>
>>Please note that it may take a couple of minutes from the time of=20
>>submission
>>until the htmlized version and diff are available at tools.ietf.org.
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>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 pkyzivat@alum.mit.edu  Wed Feb  5 10:08:12 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2EA1A0150 for <insipid@ietfa.amsl.com>; Wed,  5 Feb 2014 10:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OjXtD9xi5l8x for <insipid@ietfa.amsl.com>; Wed,  5 Feb 2014 10:08:09 -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 961DC1A0124 for <insipid@ietf.org>; Wed,  5 Feb 2014 10:08:09 -0800 (PST)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta15.westchester.pa.mail.comcast.net with comcast id NgyQ1n0061wpRvQ5Fi88E4; Wed, 05 Feb 2014 18:08:08 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta18.westchester.pa.mail.comcast.net with comcast id Ni881n00P3ZTu2S3ei88Xo; Wed, 05 Feb 2014 18:08:08 +0000
Message-ID: <52F27E08.3090904@alum.mit.edu>
Date: Wed, 05 Feb 2014 13:08:08 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>,  "insipid@ietf.org" <insipid@ietf.org>
References: <4A4F136CBD0E0D44AE1EDE36C4CD9D997394ABE4@VOEXM31W.internal.vodafone.com> <201401162019.s0GKJQHH012866@rcdn-core2-3.cisco.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D997394AD08@VOEXM31W.internal.vodafone.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D997394C66D@VOEXM31W.internal.vodafone.com> <52E13F82.10701@alum.mit.edu> <4A4F136CBD0E0D44AE1EDE36C4CD9D997395E62D@VOEXM31W.internal.vodafone.com>
In-Reply-To: <4A4F136CBD0E0D44AE1EDE36C4CD9D997395E62D@VOEXM31W.internal.vodafone.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=1391623688; bh=9tDF54Q4h97eYs9KcnrVFG4o6b2owwRVodht0vkCKxY=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=FSAV/jn/tTD0gNIHqbWmg/h23XwmEiid/aYeRpBC31RgNB4qBW4jMhSEzkQBKuq7w 5Dxak4+0P3IeGIgKWA+CA+cchfVwLrkQ8F3KT1JiP7YOfer9ddBw3R401/RLjEyUI8 VWRpZuQHSWudH7OUZvXjHs1fPKgT+nCP6wKyzsrUuoY4sQSNIveTZna/04DxJlsDZQ QgHmaMOEQasfS+wwKU1i7x05HV7TRY+IyoruvxW4l0UdXLQSyLwry1KmKeYfAe59kK Zq9VYFbZ8YERn8sdJOJyeHvgiixzLFVdaOTaD4BaLeQCmVbl4Jxt3BjUYt3SkXjfdn SmmRSY9XLHfig==
Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:08:12 -0000

On 2/5/14 10:45 AM, Dawes, Peter, Vodafone Group wrote:
> Hello Paul,
> Thanks for reviewing the draft. In http://www.ietf.org/id/draft-dawes-insipid-logme-solutions-00.txt

I have tried to leave all of the text about sending logged information 
to a server as descriptive because the related requirement is not 
currently in the requirements draft.

(was REQ9: A log-me marker may include a locator of the server that 
collects logs.  This locator is known as the diagnostic server 
identifier and may be an address of a server.  A SIP entity can use the 
diagnostic server identifier to send collected logs to the diagnostic 
server.)

Therefore the solutions draft does not describe the protocol details of 
sending logs or the related security. Three alternative next steps are 
possible

(1) REQ 9 or similar gets re-instated and I define log sending and security

(2) a requirement is agreed that SIP entities send some kind of flag to 
a debug server to indicate that they have a log to collect

(3) collection of logs is left outside the scope of log-me.
>
> To me it would seem that (1) is possible to specify, for example regarding your questions:
> [And how do they discover where to send it, and what protocol to use to do so?] the server address could be carried along with the logme marker. The protocol could be mandated as e-mail (mailto:)
> [How do the servers establish trust in this destination when sending logs? Is 6.2.2 the whole story? (That doesn't seem very practical.)] Maybe a simple way is to have a white list of domain names on the sending entity
> [Since you have said the logs are to be encrypted, *how* are they encrypted so that the server can decode and others cannot?] I imagine that many methods are possible e.g. TLS or some kind of public key encryption but I would need to consult experts on the best way to do it.
>
> Do you think (1) is possible to specify, or does transmitting logs securely and to the right destination pose too many problems?

I don't see much difference between (1) and (2) from a standardization 
perspective. (2) still requires sending *something*, so you still need 
to specify a protocol. It just decomposes the problem into two steps. I 
think you would still need to specify both of those.

It would certainly be simpler to do *nothing* about transmitting or 
accessing the logs. I don't know if that meets your needs.

If you need to do something, it is certainly possible to define. It will 
be more work - I think substantially more.

You might consider publishing something without this, but with an 
extensibility hook that allows you to then do more work for the log 
transmission.

But I am fundamentally opposed to defining a parameter for this without 
specifying any semantics for the identifier.

	Thanks,
	Paul

> Regards,
> Peter
>
>
> -----Original Message-----
> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 23 January 2014 16:13
> To: insipid@ietf.org
> Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>
> Some questions about this draft:
>
> Solution A:
>
>      User agents and SIP proxies may send logged information to a debug
>      server.
>
> And how do they discover where to send it, and what protocol to use to do so?
>
> Solution B:
>
>      Call-Info: mailto:"SIP logging"<siplogs@d1.foocorp.com>;
>                 purpose="debug"
>
> Is the use of a mailto URL normative, or just an example?
>
> How do the servers establish trust in this destination when sending logs? Is 6.2.2 the whole story? (That doesn't seem very practical.)
>
> Since you have said the logs are to be encrypted, *how* are they encrypted so that the server can decode and others cannot?
>
> How should the log be formatted within the mail? How is the test case name included in the mailed log?
>
> Solution C:
>
> As with solution A, how is the log sent?
>
> 	Thanks,
> 	Paul
>
>
> On 1/22/14 10:38 PM, Dawes, Peter, Vodafone Group wrote:
>> Hello All,
>> I have submitted the draft below which describes a solution to the log me requirements and gives a few specific protocol options (the ones that were in clause 7 of the requirements draft reviewed in Vancouver) that could be used to code a log-me marker.
>
>>
>> http://www.ietf.org/id/draft-dawes-insipid-logme-solutions-00.txt
>>
>> This draft has more protocol description than was previously in the requirements draft and tries to give a complete picture of what user agents and SIP proxies need to do to provide log-me marking. It would be good if I could present this solutions draft at IETF#89 for insipid to discuss.
>>
>> Rgds,
>> Peter
>>
>>
>> -----Original Message-----
>> From: Dawes, Peter, Vodafone Group
>> Sent: 17 January 2014 05:22
>> To: 'James Polk'
>> Cc: DRAGE, Keith (Keith) (keith.drage@alcatel-lucent.com);
>> insipid@ietf.org; Gonzalo Salgueiro (gsalguei@cisco.com)
>> Subject: RE: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>>
>> Thanks James, now submitted as draft-dawes-insipid-logme-reqs-00:
>>
>> http://datatracker.ietf.org/doc/draft-dawes-insipid-logme-reqs/
>>
>> Peter
>>
>> -----Original Message-----
>> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of James
>> Polk
>> Sent: 16 January 2014 20:19
>> To: Dawes, Peter, Vodafone Group
>> Cc: DRAGE, Keith (Keith) (keith.drage@alcatel-lucent.com);
>> insipid@ietf.org; Gonzalo Salgueiro (gsalguei@cisco.com)
>> Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>>
>> Peter
>>
>> To be blunt, if you seriously want this draft to be considered for INSIPID WG adoption you need to put "-insipid-" in the filename, and stop putting "-dispatch-" in the filename.
>>
>> Linking the drafts is simple work for the chairs to do, if that's your concern.
>>
>> James
>>
>> At 11:31 AM 1/16/2014, Dawes, Peter, Vodafone Group wrote:
>>> Hello All,
>>> Following up from IETF#88 I have uploaded a revised logme
>>> requirements draft (version -04).
>>>
>>> https://datatracker.ietf.org/doc/draft-dawes-dispatch-logme-reqs/
>>>
>>> As per the comments in Vancouver, version -04 does not include REQ9
>>> regarding a logging server address and the related sub-clause 6.2.2.
>>> Also, clause 7 on potential solutions has been removed. These
>>> requirements seem to be stable now.
>>>
>>> I will upload a related solutions draft by the end of next week
>>> (Friday
>>> 24) at the latest and I hope we can discuss solution options here on
>>> the list and then later on at IETF#89 at the beginning of March.
>>>
>>> Regards,
>>> Peter
>>> _______________________________________________
>>> 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
>


From internet-drafts@ietf.org  Fri Feb  7 14:59:43 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E1811AD791; Fri,  7 Feb 2014 14:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H12BT8USNBFe; Fri,  7 Feb 2014 14:59:42 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E68B81AD67C; Fri,  7 Feb 2014 14:59:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140207225941.8270.46034.idtracker@ietfa.amsl.com>
Date: Fri, 07 Feb 2014 14:59:41 -0800
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-reqts-10.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 22:59:43 -0000

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

        Title           : Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks
        Authors         : Paul E. Jones
                          Gonzalo Salgueiro
                          James Polk
                          Laura Liess
                          Hadriel Kaplan
	Filename        : draft-ietf-insipid-session-id-reqts-10.txt
	Pages           : 12
	Date            : 2014-02-07

Abstract:
   This document specifies the requirements for an end-to-end session
   identifier in IP-based multimedia communication networks.  This
   identifier would enable endpoints, intermediate devices, and
   management and monitoring systems to identify a session end-to-end
   across multiple SIP devices, hops, and administrative domains.


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

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

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


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

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


From internet-drafts@ietf.org  Sat Feb  8 10:14:07 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 958AE1A0548; Sat,  8 Feb 2014 10:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwsPNoEI5Q1S; Sat,  8 Feb 2014 10:14:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C631A0025; Sat,  8 Feb 2014 10:14:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140208181406.2196.73061.idtracker@ietfa.amsl.com>
Date: Sat, 08 Feb 2014 10:14:06 -0800
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-reqts-11.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Feb 2014 18:14:07 -0000

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

        Title           : Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks
        Authors         : Paul E. Jones
                          Gonzalo Salgueiro
                          James Polk
                          Laura Liess
                          Hadriel Kaplan
	Filename        : draft-ietf-insipid-session-id-reqts-11.txt
	Pages           : 12
	Date            : 2014-02-08

Abstract:
   This document specifies the requirements for an end-to-end session
   identifier in IP-based multimedia communication networks.  This
   identifier would enable endpoints, intermediate devices, and
   management and monitoring systems to identify a session end-to-end
   across multiple SIP devices, hops, and administrative domains.


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

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

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


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

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


From iesg-secretary@ietf.org  Mon Feb 10 12:28:31 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F19C41A01FD; Mon, 10 Feb 2014 12:28:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mivUL7HIt3C3; Mon, 10 Feb 2014 12:28:29 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3FC21A047C; Mon, 10 Feb 2014 12:28:26 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140210202826.7491.50738.idtracker@ietfa.amsl.com>
Date: Mon, 10 Feb 2014 12:28:26 -0800
Cc: insipid mailing list <insipid@ietf.org>, insipid chair <insipid-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Insipid] Document Action: 'Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks' to Informational RFC (draft-ietf-insipid-session-id-reqts-11.txt)
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 20:28:31 -0000

The IESG has approved the following document:
- 'Requirements for an End-to-End Session Identification in IP-Based
   Multimedia Communication Networks'
  (draft-ietf-insipid-session-id-reqts-11.txt) as Informational RFC

This document is the product of the INtermediary-safe SIP session ID
Working Group.

The IESG contact persons are Richard Barnes and Gonzalo Camarillo.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-insipid-session-id-reqts/




Technical Summary:

This document specifies the requirements for an end-to-end session identifier in IP-based multimedia communication networks.  This identifier would enable endpoints, intermediate devices, and management and monitoring systems to identify a session end-to-end across multiple SIP devices, hops, and administrative domains.


Working Group Summary:

The document has achieved working group consensus. 

One particular issue was on how much terminology to define in this document, and section 3 has been substantially worked upon within the working group.

There also has been significant discussion on the scoping of the work, and its applicability to more complex scenarios. In accordance with the charter, the work has been kept to the simpler scenarios, and the applicability to the more complex scenarios will be limited to whatever works as a result.


Document Quality:

There are no implementations as this is a requirements document. The working group is currently working on a solutions document in draft-ietf-insipid-session-id.


Personnel:

Keith Drage is the document shepherd. Richard Barnes is the responsible area director.


From Peter.Dawes@vodafone.com  Tue Feb 11 02:05:03 2014
Return-Path: <Peter.Dawes@vodafone.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029B71A07D0 for <insipid@ietfa.amsl.com>; Tue, 11 Feb 2014 02:05:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9KYJoiVNv7WP for <insipid@ietfa.amsl.com>; Tue, 11 Feb 2014 02:04:59 -0800 (PST)
Received: from mailout09.vodafone.com (mailout09.vodafone.com [195.232.224.78]) by ietfa.amsl.com (Postfix) with ESMTP id 1194E1A07E0 for <insipid@ietf.org>; Tue, 11 Feb 2014 02:04:59 -0800 (PST)
Received: from mailint09.vodafone.com (localhost [127.0.0.1]) by mailout09.vodafone.com (Postfix) with ESMTP id 3A0F0E1A77 for <insipid@ietf.org>; Tue, 11 Feb 2014 11:04:51 +0100 (CET)
Received: from VOEXC06W.internal.vodafone.com (voexc06w.dc-ratingen.de [145.230.101.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint09.vodafone.com (Postfix) with ESMTPS id 255E4E1A75; Tue, 11 Feb 2014 11:04:51 +0100 (CET)
Received: from VOEXC21W.internal.vodafone.com (145.230.103.126) by VOEXC06W.internal.vodafone.com (145.230.101.26) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 11 Feb 2014 11:04:50 +0100
Received: from VOEXM31W.internal.vodafone.com ([169.254.7.123]) by VOEXC21W.internal.vodafone.com ([145.230.103.126]) with mapi id 14.03.0146.002; Tue, 11 Feb 2014 11:04:49 +0100
From: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
Thread-Index: Ac8S4EdE5CU+hhHLR+GO87oHorGijQAF//+ZAAIkjeABOfRl8AAZOl4AAo2vTvAABCFmAAEenRhw
Date: Tue, 11 Feb 2014 10:04:49 +0000
Message-ID: <4A4F136CBD0E0D44AE1EDE36C4CD9D997397E9C4@VOEXM31W.internal.vodafone.com>
References: <4A4F136CBD0E0D44AE1EDE36C4CD9D997394ABE4@VOEXM31W.internal.vodafone.com> <201401162019.s0GKJQHH012866@rcdn-core2-3.cisco.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D997394AD08@VOEXM31W.internal.vodafone.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D997394C66D@VOEXM31W.internal.vodafone.com> <52E13F82.10701@alum.mit.edu> <4A4F136CBD0E0D44AE1EDE36C4CD9D997395E62D@VOEXM31W.internal.vodafone.com> <52F27E08.3090904@alum.mit.edu>
In-Reply-To: <52F27E08.3090904@alum.mit.edu>
Accept-Language: en-GB, de-DE, 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
Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2014 10:05:03 -0000

Hello Paul,
Thanks for the guidance. For my needs, it is not essential to specify how t=
o transmit or access logs. I will revise http://www.ietf.org/id/draft-dawes=
-insipid-logme-solutions-00.txt and take out text about sending logs to a s=
erver that was left in the example solutions.=20

Regards,
Peter

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]=20
Sent: 05 February 2014 18:08
To: Dawes, Peter, Vodafone Group; insipid@ietf.org
Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88

On 2/5/14 10:45 AM, Dawes, Peter, Vodafone Group wrote:
> Hello Paul,
> Thanks for reviewing the draft. In=20
> http://www.ietf.org/id/draft-dawes-insipid-logme-solutions-00.txt

I have tried to leave all of the text about sending logged information to a=
 server as descriptive because the related requirement is not currently in =
the requirements draft.

(was REQ9: A log-me marker may include a locator of the server that collect=
s logs.  This locator is known as the diagnostic server identifier and may =
be an address of a server.  A SIP entity can use the diagnostic server iden=
tifier to send collected logs to the diagnostic
server.)

Therefore the solutions draft does not describe the protocol details of sen=
ding logs or the related security. Three alternative next steps are possibl=
e

(1) REQ 9 or similar gets re-instated and I define log sending and security

(2) a requirement is agreed that SIP entities send some kind of flag to a d=
ebug server to indicate that they have a log to collect

(3) collection of logs is left outside the scope of log-me.
>
> To me it would seem that (1) is possible to specify, for example regardin=
g your questions:
> [And how do they discover where to send it, and what protocol to use=20
> to do so?] the server address could be carried along with the logme=20
> marker. The protocol could be mandated as e-mail (mailto:) [How do the se=
rvers establish trust in this destination when sending logs? Is 6.2.2 the w=
hole story? (That doesn't seem very practical.)] Maybe a simple way is to h=
ave a white list of domain names on the sending entity [Since you have said=
 the logs are to be encrypted, *how* are they encrypted so that the server =
can decode and others cannot?] I imagine that many methods are possible e.g=
. TLS or some kind of public key encryption but I would need to consult exp=
erts on the best way to do it.
>
> Do you think (1) is possible to specify, or does transmitting logs secure=
ly and to the right destination pose too many problems?

I don't see much difference between (1) and (2) from a standardization pers=
pective. (2) still requires sending *something*, so you still need to speci=
fy a protocol. It just decomposes the problem into two steps. I think you w=
ould still need to specify both of those.

It would certainly be simpler to do *nothing* about transmitting or accessi=
ng the logs. I don't know if that meets your needs.

If you need to do something, it is certainly possible to define. It will be=
 more work - I think substantially more.

You might consider publishing something without this, but with an extensibi=
lity hook that allows you to then do more work for the log transmission.

But I am fundamentally opposed to defining a parameter for this without spe=
cifying any semantics for the identifier.

	Thanks,
	Paul

> Regards,
> Peter
>
>
> -----Original Message-----
> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of Paul=20
> Kyzivat
> Sent: 23 January 2014 16:13
> To: insipid@ietf.org
> Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>
> Some questions about this draft:
>
> Solution A:
>
>      User agents and SIP proxies may send logged information to a debug
>      server.
>
> And how do they discover where to send it, and what protocol to use to do=
 so?
>
> Solution B:
>
>      Call-Info: mailto:"SIP logging"<siplogs@d1.foocorp.com>;
>                 purpose=3D"debug"
>
> Is the use of a mailto URL normative, or just an example?
>
> How do the servers establish trust in this destination when sending=20
> logs? Is 6.2.2 the whole story? (That doesn't seem very practical.)
>
> Since you have said the logs are to be encrypted, *how* are they encrypte=
d so that the server can decode and others cannot?
>
> How should the log be formatted within the mail? How is the test case nam=
e included in the mailed log?
>
> Solution C:
>
> As with solution A, how is the log sent?
>
> 	Thanks,
> 	Paul
>
>
> On 1/22/14 10:38 PM, Dawes, Peter, Vodafone Group wrote:
>> Hello All,
>> I have submitted the draft below which describes a solution to the log m=
e requirements and gives a few specific protocol options (the ones that wer=
e in clause 7 of the requirements draft reviewed in Vancouver) that could b=
e used to code a log-me marker.
>
>>
>> http://www.ietf.org/id/draft-dawes-insipid-logme-solutions-00.txt
>>
>> This draft has more protocol description than was previously in the requ=
irements draft and tries to give a complete picture of what user agents and=
 SIP proxies need to do to provide log-me marking. It would be good if I co=
uld present this solutions draft at IETF#89 for insipid to discuss.
>>
>> Rgds,
>> Peter
>>
>>
>> -----Original Message-----
>> From: Dawes, Peter, Vodafone Group
>> Sent: 17 January 2014 05:22
>> To: 'James Polk'
>> Cc: DRAGE, Keith (Keith) (keith.drage@alcatel-lucent.com);=20
>> insipid@ietf.org; Gonzalo Salgueiro (gsalguei@cisco.com)
>> Subject: RE: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>>
>> Thanks James, now submitted as draft-dawes-insipid-logme-reqs-00:
>>
>> http://datatracker.ietf.org/doc/draft-dawes-insipid-logme-reqs/
>>
>> Peter
>>
>> -----Original Message-----
>> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of James=20
>> Polk
>> Sent: 16 January 2014 20:19
>> To: Dawes, Peter, Vodafone Group
>> Cc: DRAGE, Keith (Keith) (keith.drage@alcatel-lucent.com);=20
>> insipid@ietf.org; Gonzalo Salgueiro (gsalguei@cisco.com)
>> Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
>>
>> Peter
>>
>> To be blunt, if you seriously want this draft to be considered for INSIP=
ID WG adoption you need to put "-insipid-" in the filename, and stop puttin=
g "-dispatch-" in the filename.
>>
>> Linking the drafts is simple work for the chairs to do, if that's your c=
oncern.
>>
>> James
>>
>> At 11:31 AM 1/16/2014, Dawes, Peter, Vodafone Group wrote:
>>> Hello All,
>>> Following up from IETF#88 I have uploaded a revised logme=20
>>> requirements draft (version -04).
>>>
>>> https://datatracker.ietf.org/doc/draft-dawes-dispatch-logme-reqs/
>>>
>>> As per the comments in Vancouver, version -04 does not include REQ9=20
>>> regarding a logging server address and the related sub-clause 6.2.2.
>>> Also, clause 7 on potential solutions has been removed. These=20
>>> requirements seem to be stable now.
>>>
>>> I will upload a related solutions draft by the end of next week=20
>>> (Friday
>>> 24) at the latest and I hope we can discuss solution options here on=20
>>> the list and then later on at IETF#89 at the beginning of March.
>>>
>>> Regards,
>>> Peter
>>> _______________________________________________
>>> 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
>


From gsalguei@cisco.com  Tue Feb 11 17:07:24 2014
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B70ED1A0311 for <insipid@ietfa.amsl.com>; Tue, 11 Feb 2014 17:07:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86Lm8bicy4JW for <insipid@ietfa.amsl.com>; Tue, 11 Feb 2014 17:07:23 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id 243F31A03CC for <insipid@ietf.org>; Tue, 11 Feb 2014 17:07:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=856; q=dns/txt; s=iport; t=1392167242; x=1393376842; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=u+HDAqkvQ0XbZKgmMZL1KENo8KsEPVjs/ZtnsOuXjEk=; b=eecbTozj+S6Ow/xCtLQbNhyLkePJV5OQ8uMPtBxriNnMDi9EsrferWfe j9bS3vjAoAtijjIyiaNnYGq4bVOymQPcKSeuUsWQe0mesLr+cgQX2fioO xNGQlL8gWuwX19FObniVlPIAPlD9ZmHgJU6UEFM+Gn/YLA0WJPz5S/g2b U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFADzI+lKtJV2d/2dsb2JhbABagwyBD78agRYWdIIsOjQLEgE+QicEDiCHasoVF455gyuBFASYKpIggy2CKg
X-IronPort-AV: E=Sophos;i="4.95,829,1384300800"; d="scan'208";a="19730871"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP; 12 Feb 2014 01:07:22 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s1C17M2F027719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 12 Feb 2014 01:07:22 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.213]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Tue, 11 Feb 2014 19:07:22 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: Adoption of draft-dawes-insipid-logme-reqs-00 as WG item
Thread-Index: AQHPJ47INTDT2N5PdkGJ5qj8U99meQ==
Date: Wed, 12 Feb 2014 01:07:22 +0000
Message-ID: <C56C2B30-2F67-4C41-92AC-1C51EDF40E7C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.235.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F1E2AF32D0A97547936C536B6F7EB59A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "insipid-chairs@tools.ietf.org" <insipid-chairs@tools.ietf.org>
Subject: [Insipid] Adoption of draft-dawes-insipid-logme-reqs-00 as WG item
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 01:07:24 -0000

Greetings -


Requirements for marking SIP sessions for logging is one of our recently ad=
ded milestones.  We currently have draft-dawes-insipid-logme-reqs specifyin=
g this.

This draft has been presented at the meeting and discussed on the mailing l=
ist.  There was consensus in Vancouver to adopt this draft as a WG document=
 to satisfy this milestone. Consensus was conditional on removing all solut=
ion elements from the requirements document and removing REQ #9.  The chair=
s believe this has been done.=20

Based on the above, we would like to propose moving forward with adoption o=
f draft-dawes-insipid-logme-reqs-00 as a WG item for the above milestone. =
=20

If you have any comments or concerns with the above, please let us know no =
later than February 28, 2014.

Thanks,

-- Gonzalo & Keith (INSIPID co-chairs)





From paulej@packetizer.com  Wed Feb 12 13:54:57 2014
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2875A1A0009 for <insipid@ietfa.amsl.com>; Wed, 12 Feb 2014 13:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.359
X-Spam-Level: 
X-Spam-Status: No, score=0.359 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vOVkf5oGx3m for <insipid@ietfa.amsl.com>; Wed, 12 Feb 2014 13:54:54 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id C4ECA1A0007 for <insipid@ietf.org>; Wed, 12 Feb 2014 13:54:54 -0800 (PST)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s1CLsq29027463 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 12 Feb 2014 16:54:53 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1392242093; bh=VqW2gDO25qFSobq+7mRuL9URSZUEpcneqYCCqlaIP44=; h=From:To:Subject:Date:Content-Transfer-Encoding:Content-Type: In-Reply-To:Message-Id:Mime-Version:Reply-To; b=NhbaNZp4MbMFkTUl4Wfn548KdWidkQqCsC9BdmQr6eks5Exxsztovd1xmaLtlBQ0V O6WGbJW7J7/eNBJBDHO6wZpEDaLPBSPMQombKjGORCnYsdsJCfc06Z9Cxe+OsQ9opE HiiENUE6uOjP6mh2/3j8pOLW8RsxCXfAACmN5Mgg=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
Date: Wed, 12 Feb 2014 21:55:00 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
In-Reply-To: <52701C91.2030200@alum.mit.edu>
Message-Id: <emf407e21c-5018-4eba-9ad4-8bdecc6daa4b@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/6.0.19861.0
Subject: Re: [Insipid] comments on draft-ietf-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 21:54:57 -0000

Paul,

Finally getting back to your comments.  We held off on most of these=20
comments until we made traction on the backward-compatibility stuff. =20
Actually, some issues do appear to be resolved, but I didn't positively=20
acknowledge.

Comments below...


>Section 6:
>
>    The exception to including the UUID of the transmitting entity
>    mentioned above is in the case of provisional responses that occur
>    before the destination UA has generated its UUID. The 100 (Trying)
>    response and the 181 (Call Forwarding) response are examples of such
>    provisional responses. In these cases, the sending intermediary
>    places the one known UUID in the remote-uuid field, and leaves the
>    "local-uuid" blank. This placement is always where a UA expects to
>    receive its UUID value in SIP responses.
>
>The above calls for a syntactically incorrect header field. If you want=
=20
>to allow the local-uuid to be omitted then the syntax needs to be=20
>updated. Or else specify that the local-uuid must be set to the NULL=20
>value.

This one I think is now addressed via use of the "null" UUID in the -04=20
draft.  You'll see the same in the forthcoming -05.


>
>    For any purpose the UA has for the Session Identifier, it MUST=20
>assume
>    that the Session Identifier is {A,B} where "A" is the UUID value of
>    this endpoint (i.e., "local-uuid") and "B" is the UUID value of the
>    peer endpoint (i.e., "remote-uuid"), taken from the most recently
>    received message within this session. Note that when comparing
>    Session Identifiers for equivalence, the identifier {A,B} is equal=20
>to
>    the set {B,A}.
>
>s/the set/the identifier/

Corrected.


>The last paragraph of Section 6 says:
>
>    Cascading MCUs all utilize the same UUID value ("local-uuid" portion
>    of the Session-ID header-value) for all participants of the cascaded
>    conference. An MCU conveys the UUID value to utilize via the "local-
>    uuid" portion of the Session-ID header-value in an INVITE to a=20
>second
>    MCU.
>
>Then Section 8 says more about MCUs. But there is nothing normative. If=
=20
>you want to say anything about this then I think it would be better to=20
>make it normative, even if it is optional to use.

We made some changes to Section 6 and Section 8.  When the -05 is=20
published, please consider what further changes we should make.


>Is the intent that when a conference focus (MCU-2) receives an INVITE,=20
>and the caller (MCU-1) indicates isFocus, that MCU-2 SHOULD adopt the=20
>uuid received in that INVITE as its own for the duration of that=20
>dialog?

Yes.


>Section 9.1:
>
>The general operation description makes a distinction between "the=20
>originating transmitter" and "UA-Alice". These seem to be the same. Is=20
>there a point to the distinction?

These are the same.  I'll change it to UA-Alice, since the rest of the=20
text appears to refer to UA-Alice and UA-Bob.


>Section 9.2:
>
>      o UA-Bob reINVITEs Alice to call Carol, using a REFER transaction,
>        as described in [RFC3515]. UA-Alice is initially put on hold,
>        then told in the REFER who to contact with a new INVITE, in this
>        case UA-Carol. This Alice-to-Carol dialog will have a new Call-
>        ID, therefore it requires a new Session-ID header-value. The
>        wrinkle here is we can, and will, use Alice's UUID from her
>        existing dialog with Bob in the new INVITE to Carol.
>
>The phrasing above is misleading. I suggest:
>
>s/reINVITEs/requests/

Changed.


>  Section 9.3:
>
>      o Bob sends a reINVITE to Alice (with the Session-ID "local-uuid"
>        =3D Bob's UUID and "remote-uuid" =3D Alice's UUID), informing her=
 to
>        transfer her existing call to Carol.
>
>I've mentioned this before...
>
>There is nothing standard that you can put in a reINVITE that will tell=
=20
>the receiver to transfer the call. I'm inclined to suggest you just=20
>drop this example. But if you want it, then you must explain what magic=
=20
>you are assuming that triggers the transfer.

You're entirely correct, but it's also common for PBX systems to perform=
=20
call transfers "behind the scenes".  I'll put in an editor's note=20
capturing your point and asking for guidance.  This can be discussed via=
=20
email or during the meeting in London.  One argument might be that if we=
=20
remove it, it does no harm because endpoints don't even know they are=20
being transferred, therefore they would have no reason to change the=20
UUID.  Thus, we could safely remove the text. Another argument might be=20
that having this helps to answer any questions that arise related to=20
such situations.


>Section 9.6:
>
>I presume that after the initial INVITE from MCU-1 to MCU-2 that MCU-2=20
>SHOULD use M' as its local UUID. If so, why doesn't it use M' as its=20
>own in the response to that invite, resulting in {M',M'}?

M' refers to the MCU's UUID.  It sends that to each of the conference=20
participants.  It also sends that to each of the MCUs with which it=20
wants to bring into a cascaded conference.  However, it's not clear=20
which message you are suggesting should be {M',M'}.  The session=20
established between the MCU-1 and MCU-2 would not use {M',M'}, if that's=
=20
what you're asking.  The sessions established between MCUs are still=20
distinct sessions and the session IDs need to be distinct.  MCU-2 and=20
MCU-3 are supposed to use M' with participants that join the conference.


>The examples also don't go far enough to show the effect they want. For=
=20
>this you should show two callers calling in, to two different MCUs and=20
>both getting M' back.

We have a new 9.6.1 that shows this example.  I'm not sure if that=20
should be its own sub-section just appended to 9.6.  Thoughts?


>Section 9.9:
>
>The "(Target-Dialog:Carol)" must be wrong since there is no dialog with=
=20
>Carol at that point. I think what you want is "(Refer-To:Carol)". There=
=20
>will be a Target-Dialog, but it isn't especially interesting here. If=20
>you want to mention it, then you might call it=20
>"(Target-Dialog:Bob-Alice)".

I think "Refer-To: Carol" is the right thing here.


>  Is there a reason for using X & Y rather than reusing B & A? E.g.:
>
>          {B} |--REFER------------>|(Refer-To:Carol) |
>         {A,B} |<-202 Accepted------| |
>                      | | |
>         {A,B} |<NOTIFY {100 Trying}| |
>         {B,A} |-200 OK------------>| |
>
>ISTM this is at least as justified as an MCU using the same uuid for=20
>all the dialogs in the same conference.

Yeah, one might make that argument.  The issue with this one was that it=
=20
was OOD.  If we want that OOD exchange to be considered a part of the=20
same session, then we would re-use {A,B}.  However, I think the thought=20
here was that the OOD REFER case is a whole other call and that means a=20
whole other session.  Bob could have used {B} as the UUID, but re-using=20
{A} (thus {A,B}) is different from the conference case, since we lose=20
the uniqueness of the two sessions.

I think we need to decide whether that OOD REFER should be considered=20
the same or a different session.

Paul


From paulej@packetizer.com  Wed Feb 12 14:06:56 2014
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5441A0018 for <insipid@ietfa.amsl.com>; Wed, 12 Feb 2014 14:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.54
X-Spam-Level: 
X-Spam-Status: No, score=-1.54 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91FsnEoCuTdq for <insipid@ietfa.amsl.com>; Wed, 12 Feb 2014 14:06:55 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id DF1D61A000F for <insipid@ietf.org>; Wed, 12 Feb 2014 14:06:54 -0800 (PST)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s1CM6qUv028184 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 12 Feb 2014 17:06:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1392242813; bh=a+go5iIDvKynphV64NbuUxNiA5E21VpCrrqz0zDPEFA=; h=From:To:Subject:Date:Content-Transfer-Encoding:Content-Type: In-Reply-To:Message-Id:Mime-Version:Reply-To; b=nh8zvR9mEtLoQqgKjph+hKALzBri372KRSeHdPQlhpAGJzi0fFDkfsAUFTtpDOtmz RzCQ3Uwmh+AYuSchgqAq9l+rL6aF2tMFFxjWi4DC0xm52UJdUDAkFS3KTZLBLpLGq9 wmAsb7TTddtDklR9Fr0dbe02L1FDff2FDWaapD+o=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Brett Tate" <brett@broadsoft.com>, "draft-ietf-insipid-session-id@tools.ietf.org" <draft-ietf-insipid-session-id@tools.ietf.org>, "insipid@ietf.org" <insipid@ietf.org>
Date: Wed, 12 Feb 2014 22:06:59 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B881A06EF56@MBX08.citservers.local>
Message-Id: <em09aae09b-d5f3-40f4-8f08-c7f191185caf@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/6.0.19861.0
Subject: Re: [Insipid] draft-ietf-insipid-session-id-02: exception for 181
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 22:06:57 -0000

Brett,

The 100 and 180 are just examples.  I think the behavior by=20
intermediaries should be the same for all provisional responses.  This=20
text has changed a bit.  When -05 comes out, feel free to comment=20
further.

Paul

------ Original Message ------
From: "Brett Tate" <brett@broadsoft.com>
To: "draft-ietf-insipid-session-id@tools.ietf.org"=20
<draft-ietf-insipid-session-id@tools.ietf.org>; "insipid@ietf.org"=20
<insipid@ietf.org>
Sent: 1/3/2014 3:05:17 PM
Subject: [Insipid] draft-ietf-insipid-session-id-02: exception for 181

>Hi,
>
>Concerning draft-ietf-insipid-session-id-02 sections 6 and 9.8, I'm not=
=20
>sure that I understand the rule which allows an intermediary to avoid=20
>creating UUID for Session-ID when sending a non-100 provisional=20
>response.
>
>"The exception to including the UUID of the transmitting entity
>  mentioned above is in the case of provisional responses that occur
>  before the destination UA has generated its UUID. The 100 (Trying)
>  response and the 181 (Call Forwarding) response are examples of such
>  provisional responses. In these cases, the sending intermediary
>  places the one known UUID in the remote-uuid field, and leaves the
>  "local-uuid" blank. This placement is always where a UA expects to
>  receive its UUID value in SIP responses."
>
>The 181 with To tag creates a new dialog (at least per RFC 5359). What=20
>makes the 181 special? For instance, there are services enabled on some=
=20
>intermediaries which generate 180 or 183 to accommodate longer delays=20
>(or to play announcements) before actually receiving a 18x from the=20
>target. It sounds like the exception also applies to 180 and 183 within=
=20
>this situation.
>
>If it matters, the draft snippet does not use normative statements to=20
>indicate how the "sending intermediary" MAY, SHOULD, or MUST behave.
>
>Thanks,
>Brett
>
>This email is intended solely for the person or entity to which it is=20
>addressed and may contain confidential and/or privileged information.=20
>If you are not the intended recipient and have received this email in=20
>error, please notify BroadSoft, Inc. immediately by replying to this=20
>message, and destroy all copies of this message, along with any=20
>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  Wed Feb 12 23:40:26 2014
Return-Path: <jmpolk@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B0D1A0147 for <insipid@ietfa.amsl.com>; Wed, 12 Feb 2014 23:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.049
X-Spam-Level: 
X-Spam-Status: No, score=-15.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2B5YubwgHPQ for <insipid@ietfa.amsl.com>; Wed, 12 Feb 2014 23:40:23 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 99E081A0141 for <insipid@ietf.org>; Wed, 12 Feb 2014 23:40:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3563; q=dns/txt; s=iport; t=1392277223; x=1393486823; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=pT5axQ6F7mcASkIuo7Kl6vfOVbc6vWgT+Penk8aaqas=; b=i37cJ6p3sntYWLgW3Ly8fdLajRswp/OjrMX7yrPraphPRdfjmLEEnMBr sY1TlAkNIfQ3moPqjqTPdROaMactQ/sS67m+BI4U5oGsdGgkI6zj4vdZc qltqegT1epsetnYAGVW8sSKVW5sq8zSgXpUwxojKpGq7+Lc834ye5a5bE 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAI92/FKrRDoJ/2dsb2JhbABZgwo4v0dPgRUWdIIlAQEBBAEBATUCNBcEBwQRBAEBAQkVEA8KDigIBgESiAQOyDMTBI4XEQFLDAaEMgSJSKEEg0wdgTU
X-IronPort-AV: E=Sophos;i="4.95,837,1384300800"; d="scan'208";a="103048872"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 13 Feb 2014 07:40:22 +0000
Received: from jmpolk-WS.cisco.com (sjc-vpn5-753.cisco.com [10.21.90.241]) (authenticated bits=0) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1D7e2Wt009163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Feb 2014 07:40:19 GMT
Message-Id: <201402130740.s1D7e2Wt009163@mtv-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 13 Feb 2014 01:40:01 -0600
To: "Paul E. Jones" <paulej@packetizer.com>, Brett Tate <brett@broadsoft.com>,  "draft-ietf-insipid-session-id@tools.ietf.org" <draft-ietf-insipid-session-id@tools.ietf.org>,  "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <em09aae09b-d5f3-40f4-8f08-c7f191185caf@sydney>
References: <576A8B541C219D4E9CEB1DF8C19C7B881A06EF56@MBX08.citservers.local> <em09aae09b-d5f3-40f4-8f08-c7f191185caf@sydney>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: Re: [Insipid] draft-ietf-insipid-session-id-02: exception for  181
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 07:40:26 -0000

Brett

I had a specific set of use-cases in mind when I wrote that text. I 
didn't give the same treatment for all provisional responses because 
there are two types of provisional responses (from a Session_ID point of view:

-  those that haven't reached any non-B2BUA SIP intermediary
(180 or 183)

and

- those that aren't expected to have reached a destination (100 and 181).

A 180 and 183 are generally expected to have reached the ultimate 
UAS, therefore have the expectation to have replaced the null UUID 
out for "their " UUID. Neither the 100 or 181 are expected to have 
anything other than a null second UUID.

With that in mind, did the text cover this point adequately enough, 
or we authors put in (somewhere) this explanation so implementors 
don't get confused down the road?

oh yeah, do you agree with this explanation?

James

At 04:06 PM 2/12/2014, Paul E. Jones wrote:
>Brett,
>
>The 100 and 180 are just examples.  I think the behavior by 
>intermediaries should be the same for all provisional 
>responses.  This text has changed a bit.  When -05 comes out, feel 
>free to comment further.
>
>Paul
>
>------ Original Message ------
>From: "Brett Tate" <brett@broadsoft.com>
>To: "draft-ietf-insipid-session-id@tools.ietf.org" 
><draft-ietf-insipid-session-id@tools.ietf.org>; "insipid@ietf.org" 
><insipid@ietf.org>
>Sent: 1/3/2014 3:05:17 PM
>Subject: [Insipid] draft-ietf-insipid-session-id-02: exception for 181
>
>>Hi,
>>
>>Concerning draft-ietf-insipid-session-id-02 sections 6 and 9.8, I'm 
>>not sure that I understand the rule which allows an intermediary to 
>>avoid creating UUID for Session-ID when sending a non-100 provisional response.
>>
>>"The exception to including the UUID of the transmitting entity
>>  mentioned above is in the case of provisional responses that occur
>>  before the destination UA has generated its UUID. The 100 (Trying)
>>  response and the 181 (Call Forwarding) response are examples of such
>>  provisional responses. In these cases, the sending intermediary
>>  places the one known UUID in the remote-uuid field, and leaves the
>>  "local-uuid" blank. This placement is always where a UA expects to
>>  receive its UUID value in SIP responses."
>>
>>The 181 with To tag creates a new dialog (at least per RFC 5359). 
>>What makes the 181 special? For instance, there are services 
>>enabled on some intermediaries which generate 180 or 183 to 
>>accommodate longer delays (or to play announcements) before 
>>actually receiving a 18x from the target. It sounds like the 
>>exception also applies to 180 and 183 within this situation.
>>
>>If it matters, the draft snippet does not use normative statements 
>>to indicate how the "sending intermediary" MAY, SHOULD, or MUST behave.
>>
>>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
>
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
>https://www.ietf.org/mailman/listinfo/insipid


From jmpolk@cisco.com  Thu Feb 13 00:17:21 2014
Return-Path: <jmpolk@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77C701A0113 for <insipid@ietfa.amsl.com>; Thu, 13 Feb 2014 00:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.049
X-Spam-Level: 
X-Spam-Status: No, score=-15.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyMOVrNSwXY9 for <insipid@ietfa.amsl.com>; Thu, 13 Feb 2014 00:17:19 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 490771A016D for <insipid@ietf.org>; Thu, 13 Feb 2014 00:17:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4651; q=dns/txt; s=iport; t=1392279438; x=1393489038; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=p9Lv4z8NTqy7qZM29TYARN5NOfK8IbaJOyjRm4mfh/0=; b=bxUDxZVaaPMuHldIAoei0WMpcpHlUGYd9TzLodMS7ynIZwiOrQTu8Wku 6DzNEADfUv9PmItD37e15UpgIWXcCeDv5ZY3JMYRj+kkIezSfpNixHrSd qS4XsnHm0nXZDmxAquLnooxbKs3aWmcAEVO3I6ScWsyoC8+DC2PJXuE54 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAJN+/FKrRDoG/2dsb2JhbABPCg6CfDi/SU+BFRZ0giUBAQEDAQEBASQRAi4GGwcEGAkVEA8KDjAGAQkJh30HDsgSEwSOFwYIAwFXhDgEiUihBIJuXh2BNQ
X-IronPort-AV: E=Sophos;i="4.95,837,1384300800"; d="scan'208";a="102348369"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 13 Feb 2014 08:17:17 +0000
Received: from jmpolk-WS.cisco.com (sjc-vpn5-753.cisco.com [10.21.90.241]) (authenticated bits=0) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1D8HHPI025915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Feb 2014 08:17:17 GMT
Message-Id: <201402130817.s1D8HHPI025915@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 13 Feb 2014 02:17:16 -0600
To: "Paul E. Jones" <paulej@packetizer.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <emf407e21c-5018-4eba-9ad4-8bdecc6daa4b@sydney>
References: <52701C91.2030200@alum.mit.edu> <emf407e21c-5018-4eba-9ad4-8bdecc6daa4b@sydney>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: Re: [Insipid] comments on draft-ietf-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 08:17:21 -0000

Paul and Paul

I'll remove the q&a that I agree with, leaving only the points that 
need further context or correction.

At 03:55 PM 2/12/2014, Paul E. Jones wrote:
>Paul,
>
>Finally getting back to your comments.  We held off on most of these 
>comments until we made traction on the backward-compatibility stuff.
>Actually, some issues do appear to be resolved, but I didn't 
>positively acknowledge.
>
>Comments below...
>

<snip>


>>  Section 9.3:
>>
>>      o Bob sends a reINVITE to Alice (with the Session-ID "local-uuid"
>>        = Bob's UUID and "remote-uuid" = Alice's UUID), informing her to
>>        transfer her existing call to Carol.
>>
>>I've mentioned this before...
>>
>>There is nothing standard that you can put in a reINVITE that will 
>>tell the receiver to transfer the call.

I'll add that you're correct too, and that this above bullet should 
have been separated into (at least) two bullets for each step. I knew 
what I wanted to explain, and just cut the text down *too* much. This 
mistake is on me.

Of course the REFER request "...tell(s) the receiver to transfer the call. "

I'll just split out the one bullet the necessary, but concise, 
bullets to explain what we mean.

>>I'm inclined to suggest you just drop this example. But if you want 
>>it, then you must explain what magic you are assuming that triggers 
>>the transfer.
>
>You're entirely correct, but it's also common for PBX systems to 
>perform call transfers "behind the scenes".  I'll put in an editor's 
>note capturing your point and asking for guidance.  This can be 
>discussed via email or during the meeting in London.  One argument 
>might be that if we remove it, it does no harm because endpoints 
>don't even know they are being transferred, therefore they would 
>have no reason to change the UUID.  Thus, we could safely remove the 
>text. Another argument might be that having this helps to answer any 
>questions that arise related to such situations.
>
>
>>Section 9.6:
>>
>>I presume that after the initial INVITE from MCU-1 to MCU-2 that 
>>MCU-2 SHOULD use M' as its local UUID. If so, why doesn't it use M' 
>>as its own in the response to that invite, resulting in {M',M'}?
>
>M' refers to the MCU's UUID.

If I may inject - M' is the UUID for this conference. Another 
conference involving this combination - or another combination - of 
MCUs would have a different UUID (say, M'', or M*)... which would be 
distributed by another series of  INVITE transactions. As the draft says

"...A conference bridge, or MCU, needs a way to identify itself when 
contacting another MCU. RFC 4579 [RFC4579] defines the 'isfocus' 
Contact: header parameter just for this purpose. "

in the first paragraph of section 9.6.

>It sends that to each of the conference participants.  It also sends 
>that to each of the MCUs with which it wants to bring into a 
>cascaded conference.  However, it's not clear which message you are 
>suggesting should be {M',M'}.  The session established between the 
>MCU-1 and MCU-2 would not use {M',M'}, if that's what you're 
>asking.  The sessions established between MCUs are still distinct 
>sessions and the session IDs need to be distinct.  MCU-2 and MCU-3 
>are supposed to use M' with participants that join the conference.




>>  Is there a reason for using X & Y rather than reusing B & A? E.g.:
>>
>>          {B} |--REFER------------>|(Refer-To:Carol) |
>>         {A,B} |<-202 Accepted------| |
>>                      | | |
>>         {A,B} |<NOTIFY {100 Trying}| |
>>         {B,A} |-200 OK------------>| |
>>
>>ISTM this is at least as justified as an MCU using the same uuid 
>>for all the dialogs in the same conference.
>
>Yeah, one might make that argument.  The issue with this one was 
>that it was OOD.  If we want that OOD exchange to be considered a 
>part of the same session, then we would re-use {A,B}.  However, I 
>think the thought here was that the OOD REFER case is a whole other 
>call and that means a whole other session.  Bob could have used {B} 
>as the UUID, but re-using {A} (thus {A,B}) is different from the 
>conference case, since we lose the uniqueness of the two sessions.
>
>I think we need to decide whether that OOD REFER should be 
>considered the same or a different session.

I'll take input from those that know SIP better than me on this one 
(Robert, Keith, Paul K, others...)...

James


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


From nobody Thu Feb 13 11:47:08 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B721A043E for <insipid@ietfa.amsl.com>; Thu, 13 Feb 2014 11:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6ZczLeiTHRH for <insipid@ietfa.amsl.com>; Thu, 13 Feb 2014 11:47:02 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7761A043C for <insipid@ietf.org>; Thu, 13 Feb 2014 11:47:02 -0800 (PST)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta12.westchester.pa.mail.comcast.net with comcast id Rrko1n0051wpRvQ5Cvn1rC; Thu, 13 Feb 2014 19:47:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta18.westchester.pa.mail.comcast.net with comcast id Rvn01n0073ZTu2S3evn0We; Thu, 13 Feb 2014 19:47:00 +0000
Message-ID: <52FD2134.8040100@alum.mit.edu>
Date: Thu, 13 Feb 2014 14:47:00 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>, "Paul E. Jones" <paulej@packetizer.com>, "insipid@ietf.org" <insipid@ietf.org>
References: <52701C91.2030200@alum.mit.edu> <emf407e21c-5018-4eba-9ad4-8bdecc6daa4b@sydney> <201402130817.s1D8HHPI025915@mtv-core-1.cisco.com>
In-Reply-To: <201402130817.s1D8HHPI025915@mtv-core-1.cisco.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=1392320821; bh=LksH0ifVMbzv3gw8Km6cjWMS5vL8xI4MNnVaCKMrD04=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=S4ZjvODu7II3uPrcGFnSx6+7AqZI8xnDcodk3a9pjTIFwcrkiemwHnC3RaaokGaHP qpp2QkkNZfr3qB7CG12v+Nkj3Qg6G4obVow6i8GqIkbCmdh/vLEFB2SD563Ld4v3uD 9b1Y2sz7PX5AXg5dYGhtV7+7Z9rQU3ziQQbGmij3S2+9OS4+DPbjvn8HJtRVsGQS/s e+7fUsfki1uIgnNh9q0pnLZnUGjVhrFcnCduo9658jXF07OB8yB20o8fkfN14VwFKO BJu5pjEP6j4qqC4g1tRHC+MqBMV4//fozYQMsBdPH+CcqGPefCQ3px1RmYplwZV90R B+d/yBJQpoVDQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/DLu8hm02v5hMEjYiDiOoaTViLB8
Subject: Re: [Insipid] comments on draft-ietf-insipid-session-id-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 19:47:04 -0000

On 2/13/14 3:17 AM, James Polk wrote:
> Paul and Paul
>
> I'll remove the q&a that I agree with, leaving only the points that need
> further context or correction.

Its been awhile, and hard to get my head back into this.
And its hard to figure out which things below are my own comments.
But I'll comment as best I can.

> At 03:55 PM 2/12/2014, Paul E. Jones wrote:
>> Paul,
>>
>> Finally getting back to your comments.  We held off on most of these
>> comments until we made traction on the backward-compatibility stuff.
>> Actually, some issues do appear to be resolved, but I didn't
>> positively acknowledge.
>>
>> Comments below...
>>
>
> <snip>
>
>
>>>  Section 9.3:
>>>
>>>      o Bob sends a reINVITE to Alice (with the Session-ID "local-uuid"
>>>        = Bob's UUID and "remote-uuid" = Alice's UUID), informing her to
>>>        transfer her existing call to Carol.
>>>
>>> I've mentioned this before...
>>>
>>> There is nothing standard that you can put in a reINVITE that will
>>> tell the receiver to transfer the call.
>
> I'll add that you're correct too, and that this above bullet should have
> been separated into (at least) two bullets for each step. I knew what I
> wanted to explain, and just cut the text down *too* much. This mistake
> is on me.
>
> Of course the REFER request "...tell(s) the receiver to transfer the
> call. "
>
> I'll just split out the one bullet the necessary, but concise, bullets
> to explain what we mean.

OK. I'll wait to see what you come up with.

>>> I'm inclined to suggest you just drop this example. But if you want
>>> it, then you must explain what magic you are assuming that triggers
>>> the transfer.
>>
>> You're entirely correct, but it's also common for PBX systems to
>> perform call transfers "behind the scenes".  I'll put in an editor's
>> note capturing your point and asking for guidance.  This can be
>> discussed via email or during the meeting in London.  One argument
>> might be that if we remove it, it does no harm because endpoints don't
>> even know they are being transferred, therefore they would have no
>> reason to change the UUID.  Thus, we could safely remove the text.
>> Another argument might be that having this helps to answer any
>> questions that arise related to such situations.
>>
>>
>>> Section 9.6:
>>>
>>> I presume that after the initial INVITE from MCU-1 to MCU-2 that
>>> MCU-2 SHOULD use M' as its local UUID. If so, why doesn't it use M'
>>> as its own in the response to that invite, resulting in {M',M'}?
>>
>> M' refers to the MCU's UUID.

So? The whole point is so that in figure 8 MCU-3 will identify itself as 
M' to Robert. So why shouldn't MCU-3 and MCU-2 identify themselves as M' 
to MCU-1.

I'm looking for some rationale and logic for when and why the MCU uses a 
unique UUID of its own and when it uses one it was given.

> If I may inject - M' is the UUID for this conference. Another conference
> involving this combination - or another combination - of MCUs would have
> a different UUID (say, M'', or M*)... which would be distributed by
> another series of  INVITE transactions. As the draft says

Sure. This is simple if each MCU has a unique URI that identifies the 
conference. (E.g. sip:confN@mcu1.com, sip:confN@mcu2.com, ...)

Then the MCU always knows what conference it is dealing with and can use 
the proper UUID.

> "...A conference bridge, or MCU, needs a way to identify itself when
> contacting another MCU. RFC 4579 [RFC4579] defines the 'isfocus'
> Contact: header parameter just for this purpose. "
>
> in the first paragraph of section 9.6.
>
>> It sends that to each of the conference participants.  It also sends
>> that to each of the MCUs with which it wants to bring into a cascaded
>> conference.  However, it's not clear which message you are suggesting
>> should be {M',M'}.  The session established between the MCU-1 and
>> MCU-2 would not use {M',M'}, if that's what you're asking.

Why not? Presumably that session is used to share media between the 
MCUs, which is legitimately part of the conference.

>> The
>> sessions established between MCUs are still distinct sessions and the
>> session IDs need to be distinct.  MCU-2 and MCU-3 are supposed to use
>> M' with participants that join the conference.

You seem to have some clear vision of how these are used that guides the 
way you are specifying this. But AFAICT you haven't explained that 
vision, and clearly I don't share it. So your choices seem entirely 
arbitrary to me.

>>>  Is there a reason for using X & Y rather than reusing B & A? E.g.:
>>>
>>>          {B} |--REFER------------>|(Refer-To:Carol) |
>>>         {A,B} |<-202 Accepted------| |
>>>                      | | |
>>>         {A,B} |<NOTIFY {100 Trying}| |
>>>         {B,A} |-200 OK------------>| |
>>>
>>> ISTM this is at least as justified as an MCU using the same uuid for
>>> all the dialogs in the same conference.
>>
>> Yeah, one might make that argument.  The issue with this one was that
>> it was OOD.  If we want that OOD exchange to be considered a part of
>> the same session, then we would re-use {A,B}.  However, I think the
>> thought here was that the OOD REFER case is a whole other call and
>> that means a whole other session.  Bob could have used {B} as the
>> UUID, but re-using {A} (thus {A,B}) is different from the conference
>> case, since we lose the uniqueness of the two sessions.
>>
>> I think we need to decide whether that OOD REFER should be considered
>> the same or a different session.

> I'll take input from those that know SIP better than me on this one
> (Robert, Keith, Paul K, others...)...

This isn't a question that existing sip specs have an answer to. The 
"session" being defined here is a new abstract concept, built on 
existing concepts such as dialogs, UAs, B2BUAs. This was my issue with 
the whole notion of session-id.

It seems that these are *choices*. It isn't clear to me if they are 
choices that we should make in this document, or if these are choices 
that implementers should make on a case by case basis.

If these are to be left as implementer choices, then I think this draft 
should call these out as choices, say that it is up to the implementer 
to make them, and explain the sorts of criteria that are relevant to the 
choice.

	Thanks,
	Paul

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


From nobody Thu Feb 13 21:17:30 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDEC1A00EC; Thu, 13 Feb 2014 21:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QM7Nk4alxWIX; Thu, 13 Feb 2014 21:17:22 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5801A00BF; Thu, 13 Feb 2014 21:17:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140214051722.25282.67767.idtracker@ietfa.amsl.com>
Date: Thu, 13 Feb 2014 21:17:22 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/txiwO5eQQePyCLChCEEAJ8FQ9cA
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-05.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 05:17:24 -0000

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

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

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

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


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

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

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


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

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


From nobody Fri Feb 14 08:31:00 2014
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A52C51A02D9 for <insipid@ietfa.amsl.com>; Fri, 14 Feb 2014 08:30:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wgWy5CfHLClX for <insipid@ietfa.amsl.com>; Fri, 14 Feb 2014 08:30:52 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 04D7C1A02A3 for <insipid@ietf.org>; Fri, 14 Feb 2014 08:30:49 -0800 (PST)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s1EGUmbY028792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <insipid@ietf.org>; Fri, 14 Feb 2014 11:30:48 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1392395448; bh=bYSZ2Hk1+e8Fyf02atnAihoCfBhea9F6yhliKuFQHKg=; h=From:To:Subject:Date:Content-Type:Message-Id:Mime-Version: Reply-To; b=eeNknUo/NDIPMlK96mgh5IXbSP/+HUwLaJuOw/u9PVeLOyEQGY8vGOKA7Md9Yx8hb oni8vB67wdxCYwdE7IqIep4abA61qG0OFtemDU9O6+IyXoRhCM2PZZZydQjmJLkjFR AeNSuKmc8TZX2U0qmziAnvmKaTEgnXhj93L98Fa0=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Date: Fri, 14 Feb 2014 16:30:59 +0000
Content-Type: multipart/alternative; boundary="------=_MB664DD253-F21F-4D98-B1A5-CDD47E9CD1A1"
Message-Id: <em0604de17-0f00-436b-ae36-80265dd5901e@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/6.0.19861.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/epiX1cm0zokN4R6qmGMf-bMV0mQ
Subject: [Insipid] New draft posted: draft-ietf-insipid-session-id-05
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 16:30:55 -0000

--------=_MB664DD253-F21F-4D98-B1A5-CDD47E9CD1A1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8

Folks,

You might have seen the announcement for the -05 draft.  Here are the=20
highlights:
Building upon the -04 draft, which was mainly focused on=20
backward-compatibilityWe made a number of editorial changes to try to=20
improve the clarityWe refer to the requirements document for definitions=
=20
of "session identifier" and "communication session"Corrected a few=20
errors in the calls flows, including where we did not mention the null=20
UUID; it's always present now when the remote uuid is not know, etc.We=20
simplified the ABNF slightly, though kept two productions with the same=20
RHS since we refer to those by name throughout the documentWe tried to=20
more cleanly separate endpoint behavior (defined in section 6) from=20
intermediary behavior (section 7)We moved MCU-related material from=20
section 6 to section 8 (which is about MCUs)We inserted three editor's=20
notes that call for discussionSection 9.3 - Transfer through=20
re-inviteSection 9.9 - OOD REFER questionSection 11 - Security=20
considerations needs more material
Please have a look at the new draft and provide comments via the list,=20
if possible.  We will have some discussion time during the meeting to=20
discuss issues, but there is not much time.

Cheers!
Paul

--------=_MB664DD253-F21F-4D98-B1A5-CDD47E9CD1A1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=utf-8

<HTML><HEAD>
<STYLE id=3DeMClientCss>
blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px;=
 padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px;=
 padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; paddin=
g-top: 0px; }
.plain pre, .plain tt { font-family: monospace; font-size: 100%; font-weigh=
t: normal; font-style: normal; }
body {font-family: Calibri;font-size: 11pt;}
.plain pre, .plain tt {font-family: Calibri;font-size: 11pt;}</STYLE>
</HEAD>
<BODY>
<DIV>Folks,</DIV>
<DIV>&nbsp;</DIV>
<DIV>You might have seen the announcement for the -05 draft.&nbsp; Here =
are the highlights:</DIV>
<UL>
<LI>Building upon the -04 draft, which was mainly focused on backward-compa=
tibility</LI>
<LI>We made a number of editorial changes to try to improve the clarity</LI=
>
<LI>We refer to the requirements document for definitions of "session ident=
ifier" and "communication session"</LI>
<LI>Corrected a few errors in the calls flows, including&nbsp;where we did=
 not mention the null UUID; it's always present now when the remote uuid=
 is not know, etc.</LI>
<LI>We simplified the ABNF slightly, though kept two productions with the=
 same RHS since we refer to those by name throughout the document</LI>
<LI>We tried to more cleanly separate endpoint behavior (defined in section=
 6) from intermediary behavior (section 7)</LI>
<LI>We moved MCU-related material from section 6 to section 8 (which is =
about MCUs)</LI>
<LI>We inserted three editor's notes that call for discussion</LI>
<UL>
<LI>Section 9.3 - Transfer through re-invite</LI>
<LI>Section 9.9 - OOD REFER question</LI>
<LI>Section 11 - Security considerations needs more material</LI></UL></UL>
<DIV>Please have a look at the new draft and provide comments via the list,=
 if possible.&nbsp; We will have some discussion time during the meeting=
 to discuss issues, but there is not much time.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Cheers!</DIV>
<DIV>Paul</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>
--------=_MB664DD253-F21F-4D98-B1A5-CDD47E9CD1A1--


From nobody Mon Feb 17 22:08:46 2014
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880561A060B for <insipid@ietfa.amsl.com>; Mon, 17 Feb 2014 22:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0lZF8jXQb8L for <insipid@ietfa.amsl.com>; Mon, 17 Feb 2014 22:08:37 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id F27621A05F7 for <insipid@ietf.org>; Mon, 17 Feb 2014 22:08:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=415; q=dns/txt; s=iport; t=1392703714; x=1393913314; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=fG33GHf934djhCc1dORLb8X3IL+l074UuFQCYxRPg48=; b=HI1IS864IfO5h1O3PEt380sgjwz58J34gEN76etZk+IAxEUiQBe3pMBh XJMrMfs16uqVOO+W2fazUze3AJ1E7oQFQjjyk+uFHjAS4W61qBr4GYttZ 7eA6pWjaZ2p/ggIHN8i6tAo/42Fa1/ESHxOY0R95t+5HYVAynjzagHvip k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFANv3AlOtJV2d/2dsb2JhbABZgwY4V79QgRMWdIIsOj8SAT5CFBMEDgUJh3wNyxAXjwGDK4EUBJgskiODLYIq
X-IronPort-AV: E=Sophos;i="4.97,500,1389744000"; d="scan'208";a="21183462"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP; 18 Feb 2014 06:08:34 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s1I68YXM005385 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Feb 2014 06:08:34 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.169]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Tue, 18 Feb 2014 00:08:33 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: IETF89 INSIPID Draft Agenda Posted
Thread-Index: AQHPLG/ao1uGEubXuUWMBtQAL5+qFw==
Date: Tue, 18 Feb 2014 06:08:33 +0000
Message-ID: <46C73497-9CCA-4567-A691-70096474D76C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.132.52]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CB9521D353149849A0DAA9CEE5D09BC0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/ZHI9zfDeeiamETGiJjdD9_SZD70
Cc: "insipid-chairs@tools.ietf.org" <insipid-chairs@tools.ietf.org>
Subject: [Insipid] IETF89 INSIPID Draft Agenda Posted
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 06:08:39 -0000

Hi -=20

We have posted the draft agenda for INSIPID here: http://www.ietf.org/proce=
edings/89/agenda/agenda-89-insipid

Please send the chairs (insipid-chairs@tools.ietf.org)any comments or reque=
sts for changes/additions before Monday February 24th (when the revised WG =
agendas are due).

Authors:  We require your slides by EOD on Monday, March 3.

Thanks,=20

Gonzalo & Keith
(as co-chairs)=


From nobody Mon Feb 17 23:15:00 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E86D1A0437 for <insipid@ietfa.amsl.com>; Mon, 17 Feb 2014 23:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NTSD5c6EqgUx for <insipid@ietfa.amsl.com>; Mon, 17 Feb 2014 23:13:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 76D5B1A05DD for <insipid@ietf.org>; Mon, 17 Feb 2014 23:13:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: insipid@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140218071331.19002.86869.idtracker@ietfa.amsl.com>
Date: Mon, 17 Feb 2014 23:13:31 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/vxRRrq_OxJyCWZDtHD25U32chCo
X-Mailman-Approved-At: Mon, 17 Feb 2014 23:14:59 -0800
Subject: [Insipid] Milestones changed for insipid WG
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 07:13:34 -0000

Changed milestone "Requirements and use cases for new identifier sent
to IESG (Informational)", set due date to March 2014 from November
2013.

Changed milestone "Specification of the new identifier sent to the
IESG (Proposed Standard)", set due date to August 2014 from April
2014.

Changed milestone "Requirements for marking SIP sessions for logging
to IESG (Informational)", set due date to September 2014 from June
2014.

Changed milestone "Protocol for marking SIP sessions for logging to
IESG (Proposed Standard)", set due date to December 2014 from November
2014.

URL: http://datatracker.ietf.org/wg/insipid/charter/


From nobody Thu Feb 20 14:06:18 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349B71A0213 for <insipid@ietfa.amsl.com>; Thu, 20 Feb 2014 14:05:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtQvsV4ErU-R for <insipid@ietfa.amsl.com>; Thu, 20 Feb 2014 14:05:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF8961A02F2 for <insipid@ietf.org>; Thu, 20 Feb 2014 14:05:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: insipid@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140220220545.3190.18716.idtracker@ietfa.amsl.com>
Date: Thu, 20 Feb 2014 14:05:45 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/2pXBT8pOfUBwylrvGx8Oertvq54
X-Mailman-Approved-At: Thu, 20 Feb 2014 14:06:16 -0800
Subject: [Insipid] Milestones changed for insipid WG
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 22:05:53 -0000

Changed milestone "Requirements and use cases for new identifier sent
to IESG (Informational)", resolved as "Done".

URL: http://datatracker.ietf.org/wg/insipid/charter/


From nobody Mon Feb 24 20:52:00 2014
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE1A1A02D5 for <insipid@ietfa.amsl.com>; Mon, 24 Feb 2014 20:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O09zHm1Lr3mS for <insipid@ietfa.amsl.com>; Mon, 24 Feb 2014 20:51:57 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 653AE1A028F for <insipid@ietf.org>; Mon, 24 Feb 2014 20:51:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=704; q=dns/txt; s=iport; t=1393303916; x=1394513516; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+s+ne1nlW47OC3rNhf/+bQ3NzgWwi/aRNNi/N1G/Z7k=; b=DRXM6qI4s1ynZnnDRL0GhE1V4rTzbq4GR5Y5rrHPePvi38x3GvBMtD0n vq1p+wknNk40ENRdU9vq5+gs+eXJFYaJQPhLFiFwfFaMrG6te3IqnMGJv ji3bAZF1ntgp3mvdiGT0Ng4J4EfrkiKlHnEvhY6F8iArIYyRvWsCk1rfU E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAFAgDFOtJV2b/2dsb2JhbABYgwY7V8FLgRgWdIIlAQEBAwE6PwULAgEINhAyFBECBA4FCYd0CA3GYBeOMTMHgySBFASYNJIngy2CKg
X-IronPort-AV: E=Sophos;i="4.97,538,1389744000"; d="scan'208";a="22927400"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-4.cisco.com with ESMTP; 25 Feb 2014 04:51:56 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1P4puik015857 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 25 Feb 2014 04:51:56 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.99]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Mon, 24 Feb 2014 22:51:56 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: IETF89 INSIPID Draft Agenda Posted
Thread-Index: AQHPLG/ao1uGEubXuUWMBtQAL5+qF5rF1lKA
Date: Tue, 25 Feb 2014 04:51:55 +0000
Message-ID: <DB0B650D-6FF7-4A0C-A1D8-9E8D4A59E914@cisco.com>
References: <46C73497-9CCA-4567-A691-70096474D76C@cisco.com>
In-Reply-To: <46C73497-9CCA-4567-A691-70096474D76C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.132.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4883C132FC8A8848B6D7BCE24931EF99@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/wVe-tg-uWJlv86vvXvAwdAmy4NI
Cc: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>, "James Polk \(jmpolk\)" <jmpolk@cisco.com>
Subject: Re: [Insipid] IETF89 INSIPID Draft Agenda Posted
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 04:51:59 -0000

Updated agenda has been uploaded.

Authors: Please note that we require your slides by EOD on Monday, March 3.

Thanks!

Gonzalo & Keith
(as co-chairs)


On Feb 18, 2014, at 1:08 AM, Gonzalo Salgueiro (gsalguei) <gsalguei@cisco.c=
om> wrote:

> Hi -=20
>=20
> We have posted the draft agenda for INSIPID here: http://www.ietf.org/pro=
ceedings/89/agenda/agenda-89-insipid
>=20
> Please send the chairs (insipid-chairs@tools.ietf.org)any comments or req=
uests for changes/additions before Monday February 24th (when the revised W=
G agendas are due).
>=20
> Authors:  We require your slides by EOD on Monday, March 3.
>=20
> Thanks,=20
>=20
> Gonzalo & Keith
> (as co-chairs)


From nobody Thu Feb 27 04:13:41 2014
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80A001A0241 for <insipid@ietfa.amsl.com>; Thu, 27 Feb 2014 04:13:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.721
X-Spam-Level: 
X-Spam-Status: No, score=0.721 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQUDaMSwXlRV for <insipid@ietfa.amsl.com>; Thu, 27 Feb 2014 04:13:38 -0800 (PST)
Received: from mail-vc0-f173.google.com (mail-vc0-f173.google.com [209.85.220.173]) by ietfa.amsl.com (Postfix) with ESMTP id F3FE91A01E9 for <insipid@ietf.org>; Thu, 27 Feb 2014 04:13:35 -0800 (PST)
Received: by mail-vc0-f173.google.com with SMTP id ld13so2359549vcb.18 for <insipid@ietf.org>; Thu, 27 Feb 2014 04:13:34 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:content-type; bh=v2EQXZO+dRUxj4VqOerp9Q7dE2CKpgHadzTACkwbmxc=; b=NNlRb1CUqW7daI56tcP07iUEaHuhuDD2xTZM90e4gbfjlhQq/0c49Jxdph4G1hZusY 1SLTsW3TP7n6K1Ck1BhiiwOar7Jc0dRWyqD2cRlN4WwNbIvLW+yu7rNRCabQqfDfOfaw IeGmTvn/V5NzcyukcZ+b9oO6WaxvR2vEX0ulsN6sA51LTjqrggYTSxgga1m5I2H8kDic fQAJOCololwBFH/XxyjuM4YxLHHmGn+yVUCSn/QSQVbtHqq6ckWNOGJ/whkz6UCDvcHM SEazfJcjhkaDH3MFCYPaZQtYs1MtFyyuQfXVTjrg7H8CCkvzFiS4ysyuDJ3oWv8UFRNm ZCQg==
X-Gm-Message-State: ALoCoQn83RL/sFhH+MeA1GPU/6yelLI8jP7CDDOGs0+SE13ibeXyuAf34eEtY6R266pD15ePFtBuGvs5czLkuN7acPgKSIbjkQ==
X-Received: by 10.221.39.138 with SMTP id tm10mr10536641vcb.7.1393503214310; Thu, 27 Feb 2014 04:13:34 -0800 (PST)
From: Brett Tate <brett@broadsoft.com>
References: <576A8B541C219D4E9CEB1DF8C19C7B881A06EF56@MBX08.citservers.local> <em09aae09b-d5f3-40f4-8f08-c7f191185caf@sydney> <201402130740.s1D7e2Wt009163@mtv-core-4.cisco.com>
In-Reply-To: <201402130740.s1D7e2Wt009163@mtv-core-4.cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac8ojtrly7gSIDRvQHKVDGA7LgccpQLHoZmw
Date: Thu, 27 Feb 2014 07:13:33 -0500
Message-ID: <3b3e85287d34712a1bc882a2c8632f8b@mail.gmail.com>
To: James Polk <jmpolk@cisco.com>, draft-ietf-insipid-session-id@tools.ietf.org, insipid@ietf.org
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/ksf52TWysbInlhGrNVI75xIO1bw
Subject: Re: [Insipid] draft-ietf-insipid-session-id-02: exception for 181
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 12:13:40 -0000

Hi James,

Draft-ietf-insipid-session-id-05 section 7 indicates the following.

"When intermediaries transmit provisional responses, such as 100
 (Trying) or the 181 (Call Forwarding), and when the UUID of the
 destination UA is unknown, the sending intermediary MUST place the
 one known UUID in the "remote-uuid" field and set the "local-uuid"
 field to the null UUID value."

Based upon the snippet, I'd assume that the B2BUA must also insert the
null UUID value if they generate 180 or 183 responses.  If you don't want
that behavior, the draft should clarify why it applies to 181 but not 180
and 183.

If I understand your response correctly, the reason is because
intermediaries typically don't generate 180 and 183 responses and
destinations typically don't generate 181 (before forwarding elsewhere).
I'm not sure if that is a good reason for the different behavior;
similarly I'm not sure why there should be different behavior.

Thanks,
Brett

> -----Original Message-----
> From: James Polk [mailto:jmpolk@cisco.com]
> Sent: Thursday, February 13, 2014 2:40 AM
> To: Paul E. Jones; Brett Tate; draft-ietf-insipid-session-
> id@tools.ietf.org; insipid@ietf.org
> Subject: Re: [Insipid] draft-ietf-insipid-session-id-02: exception for
> 181
>
> Brett
>
> I had a specific set of use-cases in mind when I wrote that text. I
> didn't give the same treatment for all provisional responses because
> there are two types of provisional responses (from a Session_ID point
> of view:
>
> -  those that haven't reached any non-B2BUA SIP intermediary
> (180 or 183)
>
> and
>
> - those that aren't expected to have reached a destination (100 and
> 181).
>
> A 180 and 183 are generally expected to have reached the ultimate
> UAS, therefore have the expectation to have replaced the null UUID
> out for "their " UUID. Neither the 100 or 181 are expected to have
> anything other than a null second UUID.
>
> With that in mind, did the text cover this point adequately enough,
> or we authors put in (somewhere) this explanation so implementors
> don't get confused down the road?
>
> oh yeah, do you agree with this explanation?
>
> James
>
> At 04:06 PM 2/12/2014, Paul E. Jones wrote:
> >Brett,
> >
> >The 100 and 180 are just examples.  I think the behavior by
> >intermediaries should be the same for all provisional
> >responses.  This text has changed a bit.  When -05 comes out, feel
> >free to comment further.
> >
> >Paul
> >
> >------ Original Message ------
> >From: "Brett Tate" <brett@broadsoft.com>
> >To: "draft-ietf-insipid-session-id@tools.ietf.org"
> ><draft-ietf-insipid-session-id@tools.ietf.org>; "insipid@ietf.org"
> ><insipid@ietf.org>
> >Sent: 1/3/2014 3:05:17 PM
> >Subject: [Insipid] draft-ietf-insipid-session-id-02: exception for 181
> >
> >>Hi,
> >>
> >>Concerning draft-ietf-insipid-session-id-02 sections 6 and 9.8, I'm
> >>not sure that I understand the rule which allows an intermediary to
> >>avoid creating UUID for Session-ID when sending a non-100 provisional
> response.
> >>
> >>"The exception to including the UUID of the transmitting entity
> >>  mentioned above is in the case of provisional responses that occur
> >>  before the destination UA has generated its UUID. The 100 (Trying)
> >>  response and the 181 (Call Forwarding) response are examples of
> such
> >>  provisional responses. In these cases, the sending intermediary
> >>  places the one known UUID in the remote-uuid field, and leaves the
> >>  "local-uuid" blank. This placement is always where a UA expects to
> >>  receive its UUID value in SIP responses."
> >>
> >>The 181 with To tag creates a new dialog (at least per RFC 5359).
> >>What makes the 181 special? For instance, there are services
> >>enabled on some intermediaries which generate 180 or 183 to
> >>accommodate longer delays (or to play announcements) before
> >>actually receiving a 18x from the target. It sounds like the
> >>exception also applies to 180 and 183 within this situation.
> >>
> >>If it matters, the draft snippet does not use normative statements
> >>to indicate how the "sending intermediary" MAY, SHOULD, or MUST
> behave.
> >>
> >>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.


From nobody Fri Feb 28 19:36:35 2014
Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B40F51A0410 for <insipid@ietfa.amsl.com>; Fri, 28 Feb 2014 19:36:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.047
X-Spam-Level: 
X-Spam-Status: No, score=-10.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uDjbHDR0ko1B for <insipid@ietfa.amsl.com>; Fri, 28 Feb 2014 19:36:32 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 2940B1A040C for <insipid@ietf.org>; Fri, 28 Feb 2014 19:36:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4235; q=dns/txt; s=iport; t=1393644990; x=1394854590; h=from:to:cc:subject:date:message-id:references: mime-version; bh=yHKGyQgu0c084SebziUkN6/ZvpxCWowR9GIA1ZxLoyE=; b=ltxxu1zzzvT/199IgQSqZHARVnd0bQisZ/I1o1aNl9KVQX6GlFiu5dtm 9nzZVA96vbF5PhciZoO3AQvjVrQO/fYE7FjFE5k3VyixX4nKz+jGKvC3t MRb8YUo1unDZpiwmRDRXuzBp0d+Cbcz+Ig/eH1oCedrLpOSgSi4El8Gi0 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnwGAF9VEVOtJXG8/2dsb2JhbABZgwY7V4QhvCtPgREWdIImAQEEAQEBGlELEAIBCAQ7BycLFBECBA4FG4deDctcEwSOUQSDKoEUBJg6kiuDLYIq
X-IronPort-AV: E=Sophos; i="4.97,566,1389744000"; d="scan'208,217"; a="24130377"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by alln-iport-4.cisco.com with ESMTP; 01 Mar 2014 03:36:29 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s213aTHB004572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 1 Mar 2014 03:36:29 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.98]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0123.003; Fri, 28 Feb 2014 21:36:29 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Adoption of draft-dawes-insipid-logme-reqs-00 as WG item
Thread-Index: AQHPJ47INTDT2N5PdkGJ5qj8U99meQ==
Date: Sat, 1 Mar 2014 03:36:29 +0000
Message-ID: <2C7E07CC-85AB-4653-A20F-9ED73A41CF59@cisco.com>
References: <C56C2B30-2F67-4C41-92AC-1C51EDF40E7C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.132.51]
Content-Type: multipart/alternative; boundary="_000_2C7E07CC85AB4653A20F9ED73A41CF59ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/UbugRrH9gAc65mQDBlIK1KFIEtQ
Cc: "insipid-chairs@tools.ietf.org" <insipid-chairs@tools.ietf.org>
Subject: Re: [Insipid] Adoption of draft-dawes-insipid-logme-reqs-00 as WG item
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Mar 2014 03:36:33 -0000

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

This working group call for adoption has completed.

The WG has accepted this draft:

draft-dawes-insipid-logme-reqs-00<https://datatracker.ietf.org/doc/draft-da=
wes-insipid-logme-reqs/>

After the I-D moratorium is lifted (on March 3rd), will the author please s=
ubmit this as:

draft-ietf-insipid-logme-reqs-00


Thanks,

-- Gonzalo & Keith (INSIPID co-chairs)


On Feb 11, 2014, at 8:07 PM, Gonzalo Salgueiro (gsalguei) <gsalguei@cisco.c=
om<mailto:gsalguei@cisco.com>> wrote:

Greetings -


Requirements for marking SIP sessions for logging is one of our recently ad=
ded milestones.  We currently have draft-dawes-insipid-logme-reqs specifyin=
g this.

This draft has been presented at the meeting and discussed on the mailing l=
ist.  There was consensus in Vancouver to adopt this draft as a WG document=
 to satisfy this milestone. Consensus was conditional on removing all solut=
ion elements from the requirements document and removing REQ #9.  The chair=
s believe this has been done.

Based on the above, we would like to propose moving forward with adoption o=
f draft-dawes-insipid-logme-reqs-00 as a WG item for the above milestone.

If you have any comments or concerns with the above, please let us know no =
later than February 28, 2014.

Thanks,

-- Gonzalo & Keith (INSIPID co-chairs)




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


--_000_2C7E07CC85AB4653A20F9ED73A41CF59ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <38552ACA3E155841A1C2C8401F4E4218@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div>This working group call for adoption has completed. &nbsp;</div>
<div><br>
</div>
<div>The WG has accepted this draft:&nbsp;</div>
<div><br>
</div>
<div><a href=3D"https://datatracker.ietf.org/doc/draft-dawes-insipid-logme-=
reqs/">draft-dawes-insipid-logme-reqs-00</a></div>
<div><br>
</div>
<div>After the I-D moratorium is lifted (on March 3rd), will the author ple=
ase submit this as:</div>
<div>&nbsp;</div>
<div>draft-ietf-insipid-logme-reqs-00</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>Thanks,<br>
<br>
-- Gonzalo &amp; Keith (INSIPID co-chairs)</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Feb 11, 2014, at 8:07 PM, Gonzalo Salgueiro (gsalguei) &lt;<a href=3D"ma=
ilto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; wrote:<br>
<br>
<blockquote type=3D"cite">Greetings -<br>
<br>
<br>
Requirements for marking SIP sessions for logging is one of our recently ad=
ded milestones. &nbsp;We currently have draft-dawes-insipid-logme-reqs&nbsp=
;specifying this.<br>
<br>
This draft has been presented at the meeting and discussed on the mailing l=
ist. &nbsp;There was consensus in Vancouver to adopt this draft as a WG&nbs=
p;document to satisfy this milestone. Consensus was conditional on removing=
 all solution elements from the requirements
 document and removing REQ #9.&nbsp;&nbsp;The chairs believe this has been =
done.&nbsp;<br>
<br>
Based on the above, we would like to propose moving forward with adoption o=
f draft-dawes-insipid-logme-reqs-00 as a WG item for the above&nbsp;milesto=
ne. &nbsp;<br>
<br>
If you have any comments or concerns with the above, please let us know no =
later than February 28, 2014.<br>
<br>
Thanks,<br>
<br>
-- Gonzalo &amp; Keith (INSIPID co-chairs)<br>
<br>
<br>
<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">https://www.ietf.=
org/mailman/listinfo/insipid</a><br>
</blockquote>
<br>
</body>
</html>

--_000_2C7E07CC85AB4653A20F9ED73A41CF59ciscocom_--

