Protocol Action: 'Automatic Multicast Tunneling' to Proposed Standard (draft-ietf-mboned-auto-multicast-18.txt)

The IESG <iesg-secretary@ietf.org> Mon, 08 December 2014 17:27 UTC

Return-Path: <iesg-secretary@ietf.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 579C21ACC83; Mon, 8 Dec 2014 09:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 GHoKLgSSmsVv; Mon, 8 Dec 2014 09:27:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A03AA1ACCE0; Mon, 8 Dec 2014 09:27:40 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Automatic Multicast Tunneling' to Proposed Standard (draft-ietf-mboned-auto-multicast-18.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141208172740.22046.66338.idtracker@ietfa.amsl.com>
Date: Mon, 08 Dec 2014 09:27:40 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/B7ke6LFE3DjAarpVrnrRstXRFGE
Cc: mboned mailing list <mboned@ietf.org>, mboned chair <mboned-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Dec 2014 17:27:45 -0000

The IESG has approved the following document:
- 'Automatic Multicast Tunneling'
  (draft-ietf-mboned-auto-multicast-18.txt) as Proposed Standard

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

The IESG contact persons are Joel Jaeggli and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/




Technical Summary 

  The advantages and benefits provided by multicast technologies are 
  well known.  There are a number of application areas that are ideal 
  candidates for the use of multicast, including media broadcasting, 
  video conferencing, collaboration, real-time data feeds, data 
  replication, and software updates.  Unfortunately, many of these 
  applications lack multicast connectivity to networks that carry 
  traffic generated by multicast sources.  The reasons for the lack of 
  connectivity vary, but are primarily the result of service provider 
  policies and network limitations. 

  Automatic Multicast Tunneling (AMT) is a protocol that uses UDP-based 
  encapsulation to overcome the aforementioned lack of multicast 
  connectivity.  AMT enables sites, hosts or applications that do not 
  have native multicast access to a network with multicast connectivity 
  to a source, to request and receive SSM [RFC4607] and ASM [RFC1112] 
  traffic from a network that does provide multicast connectivity to 
  that source. 

Working Group Summary 

 This document has received strong support from the working group and no
 major controversies existed prior to the arriving at the IESG with 
 this document.

 Subsequent to the previous IESG review, efforts have been made to address IESG  
 discuss issues, deal with IANA concerns and spin up new work associated with  
 congestion guidance for multicast applications.

Document Quality 

  A number of AMT implementations exist today and significant deployment
  experience has been documented.  This document has received thorough
  review from the working group, and many have contributed to this effort
  over the last 11+ years.  In particular, Dave Thaler, Tom Pusateri,
  Thomas Morin and Greg Bumgardner deserve credit for most of the
  authorship of this document, and Bob Sayko, Doug Nortz and their
  colleagues at ATT deserve credit for extremely thorough review of the
  document.

Personnel 

  Lenny Giuliano is the Document Shepherd, Joel Jaeggli is the 
  Responsible Area Director. 

RFC Editor Note

OLD> Gateway support for the Teardown message is OPTIONAL but RECOMMENDED.
NEW> Gateway support for the Teardown message is RECOMMENDED.

Please move the reference to [RFC1321]  from the NORMATIVE reference section to the INFORMATIVE reference section.