[Insipid] Fwd: [rfc-dist] RFC 7329 on A Session Identifier for the Session Initiation Protocol (SIP)

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Thu, 21 August 2014 05:02 UTC

Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C24851A701D for <insipid@ietfa.amsl.com>; Wed, 20 Aug 2014 22:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.169
X-Spam-Level:
X-Spam-Status: No, score=-15.169 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 0Zqx34ryu1wV for <insipid@ietfa.amsl.com>; Wed, 20 Aug 2014 22:02:31 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 846061A7013 for <insipid@ietf.org>; Wed, 20 Aug 2014 22:02:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2605; q=dns/txt; s=iport; t=1408597351; x=1409806951; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=ZjkL5V5rZUwarF0wU6Nf77gsYnDFUx7TWVYZSmXPTP0=; b=bEtw4rDKqHkEZIeNeii0C450FqR5GM6n+8FL7Kep9GEjVr0i25sWEF5S VS0sV+8vTW2C8TpdlL8ElPk8CkUsAd0C44HbHzU1UDFyF9tIVD0cU84/l x4bC39ghyom2ZxSvTtZAvQCXEOfTi+7PtRG9RTfAVNVl7y4V1NOQ/f3Sr g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FACZ89VOtJV2Q/2dsb2JhbABagw1TVwSyFporCodZgRAWd4QDAQEBAwEBAQE3FCAQCwIBGQMBAg0SECcKARMIAggCBBMUBwIEiA0DCQgNwU4XjB2BAoFaVQuDKYEdBYUEBYwchCaEcIIJjAqCS4Y1gheBRmwBgQ45gQcBAQE
X-IronPort-AV: E=Sophos;i="5.01,906,1400025600"; d="scan'208";a="71070900"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-6.cisco.com with ESMTP; 21 Aug 2014 05:02:25 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s7L52PpV020540 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <insipid@ietf.org>; Thu, 21 Aug 2014 05:02:25 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.173]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Thu, 21 Aug 2014 00:02:25 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [rfc-dist] RFC 7329 on A Session Identifier for the Session Initiation Protocol (SIP)
Thread-Index: AQHPvODL38UXnlc9HEi1XM9+iJBs+A==
Date: Thu, 21 Aug 2014 05:02:24 +0000
Message-ID: <CCFA3FDB-4445-458C-83E2-34E56EA57BD1@cisco.com>
References: <20140821013857.D105D180483@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.132.53]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7B92E338B6B40942962874F0D772D914@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/BvroxyL0_vo15ul7ETK7Kn5adf4
Subject: [Insipid] Fwd: [rfc-dist] RFC 7329 on A Session Identifier for the Session Initiation Protocol (SIP)
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 21 Aug 2014 05:02:34 -0000

FYI

Begin forwarded message:

> From: <rfc-editor@rfc-editor.org>
> Subject: [rfc-dist] RFC 7329 on A Session Identifier for the Session Initiation Protocol (SIP)
> Date: August 20, 2014 at 9:38:57 PM EDT
> To: <ietf-announce@ietf.org>, <rfc-dist@rfc-editor.org>
> Cc: <drafts-update-ref@iana.org>, <rfc-editor@rfc-editor.org>
> 
> 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
> 
> 
> _______________________________________________
> rfc-dist mailing list
> rfc-dist@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-dist
> http://www.rfc-editor.org