[MBONED] RFC 8487 on Mtrace Version 2: Traceroute Facility for IP Multicast

rfc-editor@rfc-editor.org Mon, 29 October 2018 05:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6AAD5128D0C; Sun, 28 Oct 2018 22:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mofZvU83jvYL; Sun, 28 Oct 2018 22:17:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ECF0130DC3; Sun, 28 Oct 2018 22:17:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 08FD6B81021; Sun, 28 Oct 2018 22:16:54 -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: <20181029051654.08FD6B81021@rfc-editor.org>
Date: Sun, 28 Oct 2018 22:16:54 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Kzud9sUfVRIbSHudp6Rr4O_YLpM>
Subject: [MBONED] =?utf-8?q?RFC_8487_on_Mtrace_Version_2=3A_Traceroute_Fa?= =?utf-8?q?cility_for_IP_Multicast?=
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: Mon, 29 Oct 2018 05:17:03 -0000

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

        RFC 8487

        Title:      Mtrace Version 2: Traceroute Facility 
                    for IP Multicast 
        Author:     H. Asaeda,
                    K. Meyer,
                    W. Lee. Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2018
        Mailbox:    asaeda@nict.go.jp, 
        Pages:      41
        Characters: 96547
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mboned-mtrace-v2-26.txt

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

        DOI:        10.17487/RFC8487

This document describes the IP multicast traceroute facility, named
Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
requires special implementations on the part of routers.  This
specification describes the required functionality in multicast
routers, as well as how an Mtrace2 client invokes a Query and
receives a Reply.

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

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