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

"Ben Campbell" <ben@nostrum.com> Wed, 13 July 2016 22:27 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 E4F7612D939 for <insipid@ietfa.amsl.com>; Wed, 13 Jul 2016 15:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level:
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] 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 ylM0QWAhnoBr for <insipid@ietfa.amsl.com>; Wed, 13 Jul 2016 15:27:06 -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 3DED012D92D for <insipid@ietf.org>; Wed, 13 Jul 2016 15:27:06 -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 u6DMR1s2050730 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 13 Jul 2016 17:27:01 -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: Wed, 13 Jul 2016 17:27:00 -0500
Message-ID: <C21F8D82-7E8C-490D-ADE5-B80B90A50A0A@nostrum.com>
In-Reply-To: <5BF95E68-1D12-405E-9E0E-9FEF095B29CA@cisco.com>
References: <20160629233734.30463.86831.idtracker@ietfa.amsl.com> <5BF95E68-1D12-405E-9E0E-9FEF095B29CA@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/Eq1OSSIaQW0i8hMxRsTWA-UyvpE>
Cc: insipid@ietf.org
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-24.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: Wed, 13 Jul 2016 22:27:08 -0000

I think this one is ready for IETF last call. I will start that shortly. 
The last call will run an extra week, due to the fact it will cross an 
IETF meeting week.

Thanks!

Ben.

On 29 Jun 2016, at 18:44, Paul Giralt wrote:

> Ben / INSIPID WG,
>
> I believe this latest draft addresses all outstanding feedback. Please 
> let me know if any other changes are need before moving to the next 
> step in the process.
>
> Thanks,
> -Paul
>
>
>> On Jun 29, 2016, at 7:37 PM, 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-24.txt
>> 	Pages           : 41
>> 	Date            : 2016-06-29
>>
>> 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-24
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-session-id-24
>>
>>
>> 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