RFC 7329 on A Session Identifier for the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Thu, 21 August 2014 01:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 383691A0099 for <ietf-announce@ietfa.amsl.com>; Wed, 20 Aug 2014 18:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.57
X-Spam-Level:
X-Spam-Status: No, score=-107.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 PZXTeZmRSSv8 for <ietf-announce@ietfa.amsl.com>; Wed, 20 Aug 2014 18:39:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 242B91A00B8 for <ietf-announce@ietf.org>; Wed, 20 Aug 2014 18:39:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D105D180483; Wed, 20 Aug 2014 18:38:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7329 on A Session Identifier for the Session Initiation Protocol (SIP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140821013857.D105D180483@rfc-editor.org>
Date: Wed, 20 Aug 2014 18:38:57 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/9JSgipx_VaosLF_c49v_JlHj1CM
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2014 01:39:04 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7329

        Title:      A Session Identifier for the 
                    Session Initiation Protocol (SIP) 
        Author:     H. Kaplan
        Status:     Informational
        Stream:     IETF
        Date:       August 2014
        Mailbox:    hadrielk@yahoo.com
        Pages:      17
        Characters: 39057
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-kaplan-insipid-session-id-04.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7329.txt

There is a need for having a globally unique session identifier for
the same SIP session that can be consistently maintained across
SIP Proxies, Back-to-Back User Agents (B2BUAs), and other SIP
middleboxes, for the purpose of troubleshooting.  This document
proposes a new SIP header to carry such a value: Session-ID.

The mechanism defined in this document has been widely deployed, and
is being followed in a backward-compatible fashion for a new Standards
Track document produced by the INSIPID Working Group.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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/rfc.html

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