[Insipid] RFC 7989 on End-to-End Session Identification in IP-Based Multimedia Communication Networks
rfc-editor@rfc-editor.org Thu, 20 October 2016 00:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 87E68129862; Wed, 19 Oct 2016 17:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.033
X-Spam-Level:
X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 aXY3D-qSkddK; Wed, 19 Oct 2016 17:18:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 859E212986D; Wed, 19 Oct 2016 17:17:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2465BB80164; Wed, 19 Oct 2016 17:17:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161020001730.2465BB80164@rfc-editor.org>
Date: Wed, 19 Oct 2016 17:17:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/36Nj4wiIdresbdkcprSCiZp1gUc>
Cc: drafts-update-ref@iana.org, insipid@ietf.org, rfc-editor@rfc-editor.org
Subject: [Insipid] RFC 7989 on End-to-End Session Identification in IP-Based Multimedia Communication Networks
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: Thu, 20 Oct 2016 00:18:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7989
Title: End-to-End Session Identification in IP-Based
Multimedia Communication Networks
Author: P. Jones, G. Salgueiro,
C. Pearce, P. Giralt
Status: Standards Track
Stream: IETF
Date: October 2016
Mailbox: paulej@packetizer.com,
gsalguei@cisco.com,
chrep@cisco.com,
pgiralt@cisco.com
Pages: 45
Characters: 103241
Obsoletes: RFC 7329
I-D Tag: draft-ietf-insipid-session-id-27.txt
URL: https://www.rfc-editor.org/info/rfc7989
DOI: http://dx.doi.org/10.17487/RFC7989
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 the Session
Initiation Protocol (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.
This document is a product of the INtermediary-safe SIP session ID Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC