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

It is long overdue.... Congrats!

On 6/29/11 9:56 AM, "Mike Hammer (hmmr)" <hmmr@cisco.com> wrote:

>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
>_______________________________________________
>Speermint mailing list
>Speermint@ietf.org
>https://www.ietf.org/mailman/listinfo/speermint