RFC 6336 on IANA Registry for Interactive Connectivity Establishment (ICE) Options

rfc-editor@rfc-editor.org Tue, 19 July 2011 23:48 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A8611E80A3; Tue, 19 Jul 2011 16:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level:
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=0.978, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 36oFDELUn1MX; Tue, 19 Jul 2011 16:48:17 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [64.170.98.47]) by ietfa.amsl.com (Postfix) with ESMTP id F3D6B11E80A2; Tue, 19 Jul 2011 16:48:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E022A98C520; Tue, 19 Jul 2011 16:48:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6336 on IANA Registry for Interactive Connectivity Establishment (ICE) Options
From: rfc-editor@rfc-editor.org
Message-Id: <20110719234816.E022A98C520@rfc-editor.org>
Date: Tue, 19 Jul 2011 16:48:16 -0700
Cc: mmusic@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 19 Jul 2011 23:48:18 -0000

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

        
        RFC 6336

        Title:      IANA Registry for Interactive Connectivity 
                    Establishment (ICE) Options 
        Author:     M. Westerlund, C. Perkins
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2011
        Mailbox:    magnus.westerlund@ericsson.com, 
                    csp@csperkins.org
        Pages:      5
        Characters: 8228
        Updates:    RFC5245

        I-D Tag:    draft-ietf-mmusic-ice-options-registry-02.txt

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

It has been identified that "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) Traversal for
Offer/Answer Protocols" (RFC 5245) is missing a registry for ICE
options.  This document defines this missing IANA registry and
updates RFC 5245.  [STANDARDS-TRACK]

This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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