End-to-End Session Identification in IP-Based Multimedia Communication Networks
draft-ietf-insipid-session-id-27

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: ben@nostrum.com, insipid-chairs@ietf.org, draft-ietf-insipid-session-id@ietf.org, insipid@ietf.org, christer.holmberg@ericsson.com, "The IESG" <iesg@ietf.org>, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'End-to-End Session Identification in IP-Based Multimedia Communication Networks' to Proposed Standard (draft-ietf-insipid-session-id-27.txt)

The IESG has approved the following document:
- 'End-to-End Session Identification in IP-Based Multimedia Communication
   Networks'
  (draft-ietf-insipid-session-id-27.txt) as Proposed Standard

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

The IESG contact persons are Alexey Melnikov, Ben Campbell and Alissa
Cooper.

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

Ballot Text

Technical Summary

        The 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.

Working Group Summary

       The work on the document took a relatively long time in the WG. The reason 
       was not so much related to controversies, or different opinions, but more related 
       to the cycles the authors and contributors were able to put on the work.
       There is a consensus in the INSIPID WG to publish the document as an RFC.

Document Quality

       A number of vendors have indicated that they have implemented, or intend to 
       implement, the document. Individuals representing the implementers were also 
       involved in the work on the document.
      
       The document is also referenced by 3GPP, and support is required for certain IMS 
       use-cases and functions.

Personnel

      Document Shepherd: Christer Holmberg 
      Responsible Area Director: Ben Campbell

RFC Editor Note