Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt

"Ben Campbell" <ben@nostrum.com> Mon, 27 June 2016 21:57 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A806312D8C2 for <insipid@ietfa.amsl.com>; Mon, 27 Jun 2016 14:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 5LWXqVFkJee8 for <insipid@ietfa.amsl.com>; Mon, 27 Jun 2016 14:57:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07F2D12D993 for <insipid@ietf.org>; Mon, 27 Jun 2016 14:57:25 -0700 (PDT)
Received: from [10.0.1.4] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u5RLvKWn093728 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 27 Jun 2016 16:57:20 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.4]
From: "Ben Campbell" <ben@nostrum.com>
To: "Paul Giralt" <pgiralt@cisco.com>
Date: Mon, 27 Jun 2016 16:57:25 -0500
Message-ID: <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com>
In-Reply-To: <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com> <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/1TQkoe_TLKkVz6CF9rVfxhlKInM>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2016 21:57:28 -0000

Hi Paul,

That version mostly addresses my concerns. I have a couple of comments 
about the updated section 12:

- The text states that, since the session-IDs must not contain device or 
user identifying information, they have no privacy considerations. That 
sort of statement is a bit of a red flag during IESG review. In 
particular, it would be good to also say something about the use of a 
session-ID as a persistent identifier to correlate across session. As it 
is, 4.2 says they generate a new, previously unused UUID. Is there any 
normative text about reusing the UUID for more than one "session"? (Not 
counting the text about transfers, etc.).

- The statement that session-id "MUST NOT be used for billing purposes" 
will probably draw objections. I suggest that be changed ot "is not 
appropriate for billing purposes." (Not really new text, but the 
revisions drew my attention to it.)

Thanks!

Ben.

On 24 Jun 2016, at 10:48, Paul Giralt (pgiralt) wrote:

> Ben,
>
> I’m hoping this version of the draft addresses your concerns. Please 
> let me know your thoughts on the latest changes.
>
> Thanks,
> -Paul
>
>> On Jun 24, 2016, at 12:37 AM, internet-drafts@ietf.org wrote:
>>
>>
>> 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 of 
>> the IETF.
>>
>>        Title           : End-to-End Session Identification in 
>> IP-Based Multimedia Communication Networks
>>        Authors         : Paul E. Jones
>>                          Gonzalo Salgueiro
>>                          Chris Pearce
>>                          Paul Giralt
>> 	Filename        : draft-ietf-insipid-session-id-23.txt
>> 	Pages           : 40
>> 	Date            : 2016-06-23
>>
>> Abstract:
>>   This document describes an end-to-end Session Identifier for use in
>>   IP-based multimedia communication systems that enables endpoints,
>>   intermediary 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.  While the identifier is intended to work across multiple
>>   protocols, this document describes its usage in SIP.
>>
>>   This document also describes a backwards compatibility mechanism 
>> for
>>   an existing session identifier implementation (RFC 7329) that is
>>   sufficiently different from the procedures defined in this 
>> document.
>>
>>   This document obsoletes RFC 7329.
>>
>>
>> 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:
>> https://tools.ietf.org/html/draft-ietf-insipid-session-id-23
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-session-id-23
>>
>>
>> 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/
>>
>> _______________________________________________
>> 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