[MBONED] RFC 8777 on DNS Reverse IP Automatic Multicast Tunneling (AMT) Discovery
rfc-editor@rfc-editor.org Fri, 24 April 2020 16:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCC2D3A0E60; Fri, 24 Apr 2020 09:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 pm4LaqlAdJBd; Fri, 24 Apr 2020 09:00:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 565EA3A0E22; Fri, 24 Apr 2020 09:00:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E4D86F406C4; Fri, 24 Apr 2020 08:59:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mboned@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200424155958.E4D86F406C4@rfc-editor.org>
Date: Fri, 24 Apr 2020 08:59:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/FYdPGk9PzwuWKWlWwif9NsHjZ-o>
Subject: [MBONED] RFC 8777 on DNS Reverse IP Automatic Multicast Tunneling (AMT) Discovery
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2020 16:00:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8777
Title: DNS Reverse IP Automatic Multicast
Tunneling (AMT) Discovery
Author: J. Holland
Status: Standards Track
Stream: IETF
Date: April 2020
Mailbox: jakeholland.net@gmail.com
Pages: 33
Updates: RFC 7450
I-D Tag: draft-ietf-mboned-driad-amt-discovery-13.txt
URL: https://www.rfc-editor.org/info/rfc8777
DOI: 10.17487/RFC8777
This document updates RFC 7450, "Automatic Multicast Tunneling" (or
AMT), by modifying the relay discovery process. A new DNS resource
record named AMTRELAY is defined for publishing AMT relays for
source-specific multicast channels. The reverse IP DNS zone for a
multicast sender's IP address is configured to use AMTRELAY resource
records to advertise a set of AMT relays that can receive and forward
multicast traffic from that sender over an AMT tunnel. Other
extensions and clarifications to the relay discovery process are also
defined.
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/retrieve/bulk
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