RFC 5245 on Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols

rfc-editor@rfc-editor.org Thu, 29 April 2010 23:35 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CD8F3A69E8; Thu, 29 Apr 2010 16:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.074
X-Spam-Level:
X-Spam-Status: No, score=-1.074 tagged_above=-999 required=5 tests=[AWL=-0.933, BAYES_20=-0.74, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-22sv9bdxwj; Thu, 29 Apr 2010 16:35:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 9AF113A6951; Thu, 29 Apr 2010 16:35:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A66BCE065C; Thu, 29 Apr 2010 16:35:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5245 on Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
From: rfc-editor@rfc-editor.org
Message-Id: <20100429233544.A66BCE065C@rfc-editor.org>
Date: Thu, 29 Apr 2010 16:35:44 -0700
Cc: mmusic@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 29 Apr 2010 23:35:58 -0000

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

        
        RFC 5245

        Title:      Interactive Connectivity Establishment (ICE): A 
                    Protocol for Network Address Translator (NAT) 
                    Traversal for Offer/Answer Protocols 
        Author:     J. Rosenberg
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2010
        Mailbox:    jdrosen@jdrosen.net
        Pages:      117
        Characters: 285120
        Obsoletes:  RFC4091, RFC4092

        I-D Tag:    draft-ietf-mmusic-ice-19.txt

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

This document describes a protocol for Network Address Translator
(NAT) traversal for UDP-based multimedia sessions established with
the offer/answer model.  This protocol is called Interactive
Connectivity Establishment (ICE).  ICE makes use of the Session
Traversal Utilities for NAT (STUN) protocol and its extension,
Traversal Using Relay NAT (TURN).  ICE can be used by any protocol
utilizing the offer/answer model, such as the Session Initiation
Protocol (SIP).  [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