Re: [Speermint] Fwd: [splices] RFC 6271 on Requirements for SIP-BasedSession Peering

"Mike Hammer (hmmr)" <hmmr@cisco.com> Wed, 29 June 2011 13:56 UTC

Return-Path: <hmmr@cisco.com>
X-Original-To: speermint@ietfa.amsl.com
Delivered-To: speermint@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 389D111E8075 for <speermint@ietfa.amsl.com>; Wed, 29 Jun 2011 06:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gFUen9AAqPK for <speermint@ietfa.amsl.com>; Wed, 29 Jun 2011 06:56:56 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id 3E08C228011 for <speermint@ietf.org>; Wed, 29 Jun 2011 06:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=hmmr@cisco.com; l=3022; q=dns/txt; s=iport; t=1309355816; x=1310565416; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=XuTIzG9MhcF0g8d8NDT9bgNF/BB++DCGli0Kjft4xBY=; b=Ws4ocgJlQOT4yN1ZQmrf06Tygx4p+hf1KXcAThiWDYN7xi5CdGdEkltr Z3FI2Fo63bEtDIcE33yDhxUrqUI+yS6CQf41TI4HZMXZ0sYMk3FV3qC5x D5GkqfWZzuy2xf9hXSWQv2ltPVhqqRGPwgCCVj+dZj+9PAEUAVyU6Vd7f E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBANIuC06tJV2a/2dsb2JhbABSmCKPOnerA54XhjAEhzaPX4tK
X-IronPort-AV: E=Sophos;i="4.65,443,1304294400"; d="scan'208";a="388471300"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by sj-iport-2.cisco.com with ESMTP; 29 Jun 2011 13:56:55 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p5TDutno014254; Wed, 29 Jun 2011 13:56:55 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 29 Jun 2011 08:56:54 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Jun 2011 08:56:53 -0500
Message-ID: <C4064AF1C9EC1F40868C033DB94958C704E63309@XMB-RCD-111.cisco.com>
In-Reply-To: <4E0AE0C5.7030904@ericsson.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Speermint] Fwd: [splices] RFC 6271 on Requirements for SIP-BasedSession Peering
Thread-Index: Acw2NbRlACFurK5fTV6wkHurzodDrQALqaSA
References: <4E0AE0C5.7030904@ericsson.com>
From: "Mike Hammer (hmmr)" <hmmr@cisco.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, speermint@ietf.org
X-OriginalArrivalTime: 29 Jun 2011 13:56:54.0906 (UTC) FILETIME=[679095A0:01CC3664]
Subject: Re: [Speermint] Fwd: [splices] RFC 6271 on Requirements for SIP-BasedSession Peering
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2011 13:56:57 -0000

Congratulations on completing this!  Finally.

Mike


-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On
Behalf Of Gonzalo Camarillo
Sent: Wednesday, June 29, 2011 4:22 AM
To: speermint@ietf.org
Subject: [Speermint] Fwd: [splices] RFC 6271 on Requirements for
SIP-BasedSession Peering

FYI. The email below went to the SPLICES mailing list for some reason.

Cheers,

Gonzalo

-------- Original Message --------
Subject: [splices] RFC 6271 on Requirements for SIP-Based Session
Peering
Date: Wed, 29 Jun 2011 00:35:20 +0200
From: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org <ietf-announce@ietf.org>,
rfc-dist@rfc-editor.org <rfc-dist@rfc-editor.org>
CC: splices@ietf.org <splices@ietf.org>, rfc-editor@rfc-editor.org
<rfc-editor@rfc-editor.org>


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


        RFC 6271

        Title:      Requirements for SIP-Based Session Peering
        Author:     J-F. Mule
        Status:     Informational
        Stream:     IETF
        Date:       June 2011
        Mailbox:    jf.mule@cablelabs.com
        Pages:      23
        Characters: 54492
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-speermint-requirements-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6271.txt

This memo captures protocol requirements to enable session peering of
voice, presence, instant messaging, and other types of multimedia
traffic.  This informational document is intended to link the various
use cases described for session peering to protocol solutions.  This
document is not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the Session PEERing for Multimedia
INTerconnect Working Group of the IETF.


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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see
http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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


_______________________________________________
splices mailing list
splices@ietf.org
https://www.ietf.org/mailman/listinfo/splices

_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint