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

"Paul E. Jones" <paulej@packetizer.com> Sat, 07 March 2015 06:17 UTC

From: "Paul E. Jones" <paulej@packetizer.com>
To: internet-drafts@ietf.org
Date: Sat, 07 Mar 2015 06:18:43 +0000
Message-Id: <em72baebe6-5a37-4bc8-b966-8b0d61220ab5@sydney>
In-Reply-To: <20150307061623.25688.2311.idtracker@ietfa.amsl.com>
User-Agent: eM_Client/6.0.21372.0
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/E1Ax1-5b1SYwdswiOexAY3u6A8M>
Cc: insipid@ietf.org
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-14.txt
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>

Folks,

I went ahead and posted an "official" -14 version that we can discuss.  
This should be considered as opposed to the document I referenced in the 
email yesterday.

Paul

------ Original Message ------
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: insipid@ietf.org
Sent: 3/7/2015 1:16:23 AM
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-14.txt

>
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>  This draft is a work item of the INtermediary-safe SIP session ID 
>Working Group of the IETF.
>
>         Title : End-to-End Session Identification in IP-Based 
>Multimedia Communication Networks
>         Authors : Paul E. Jones
>                           James Polk
>                           Gonzalo Salgueiro
>                           Chris Pearce
>  Filename : draft-ietf-insipid-session-id-14.txt
>  Pages : 33
>  Date : 2015-03-06
>
>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 (RFC 7329) 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-14
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-session-id-14
>
>
>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] I-D Action: draft-ietf-insipid-session-… internet-drafts
Re: [Insipid] I-D Action: draft-ietf-insipid-sess… Paul E. Jones