RFC 7355 on Indicating WebSocket Protocol as a Transport in the Session Initiation Protocol (SIP) Common Log Format (CLF)

rfc-editor@rfc-editor.org Tue, 23 September 2014 20:02 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 715331A1BCB for <ietf-announce@ietfa.amsl.com>; Tue, 23 Sep 2014 13:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.688
X-Spam-Level:
X-Spam-Status: No, score=-102.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, 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 bjdsZMOgdv-Q for <ietf-announce@ietfa.amsl.com>; Tue, 23 Sep 2014 13:02:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5B48E1A88C2 for <ietf-announce@ietf.org>; Tue, 23 Sep 2014 13:01:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B2244180015; Tue, 23 Sep 2014 13:01:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7355 on Indicating WebSocket Protocol as a Transport in the Session Initiation Protocol (SIP) Common Log Format (CLF)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140923200135.B2244180015@rfc-editor.org>
Date: Tue, 23 Sep 2014 13:01:35 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/8u56Jp_yQZQ-b3Eso8aN5uiu7ds
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: Tue, 23 Sep 2014 20:02:17 -0000

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

        
        RFC 7355

        Title:      Indicating WebSocket Protocol as a Transport
                    in the Session Initiation Protocol (SIP)
                    Common Log Format (CLF) 
        Author:     G. Salgueiro, V. Pascual,
                    A. Roman, S. Garcia
        Status:     Informational
        Stream:     IETF
        Date:       September 2014
        Mailbox:    gsalguei@cisco.com, 
                    victor.pascual@quobis.com, 
                    anton.roman@quobis.com,
                    sergio.garcia@quobis.com
        Pages:      9
        Characters: 16180
        Updates:    RFC 6873

        I-D Tag:    draft-salgueiro-dispatch-websocket-sipclf-02.txt

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

RFC 7118 specifies a WebSocket subprotocol as a reliable real-time
transport mechanism between Session Initiation Protocol (SIP)
entities to enable usage of SIP in web-oriented deployments.  This
document updates the SIP Common Log Format (CLF), defined in RFC
6873, with a new "Transport Flag" for such SIP WebSocket transport.


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