RFC 7450 on Automatic Multicast Tunneling

rfc-editor@rfc-editor.org Wed, 18 February 2015 23: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 11C8F1A1BBD; Wed, 18 Feb 2015 15:02:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 nhJwx2rFYxDq; Wed, 18 Feb 2015 15:02:39 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id D00121A1BD7; Wed, 18 Feb 2015 15:02:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 12E09181D1F; Wed, 18 Feb 2015 15:02:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7450 on Automatic Multicast Tunneling
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150218230216.12E09181D1F@rfc-editor.org>
Date: Wed, 18 Feb 2015 15:02:16 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/d0N10tdQGQFFiK6UQOCzTOa8gmI>
Cc: mboned@ietf.org, 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: Wed, 18 Feb 2015 23:02:41 -0000

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

        
        RFC 7450

        Title:      Automatic Multicast Tunneling 
        Author:     G. Bumgardner
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2015
        Mailbox:    gbumgard@gmail.com
        Pages:      82
        Characters: 188711
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mboned-auto-multicast-18.txt

        URL:        https://www.rfc-editor.org/info/rfc7450

This document describes Automatic Multicast Tunneling (AMT), a
protocol for delivering multicast traffic from sources in a
multicast-enabled network to receivers that lack multicast
connectivity to the source network.  The protocol uses UDP
encapsulation and unicast replication to provide this functionality.

The AMT protocol is specifically designed to support rapid deployment
by requiring minimal changes to existing network infrastructure.

This document is a product of the MBONE Deployment Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  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