[rfc-dist] RFC 8534 on Explicit Tracking with Wildcard Routes in Multicast VPN

rfc-editor@rfc-editor.org Wed, 20 February 2019 06:57 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40EE41294FA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 19 Feb 2019 22:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable 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 LymgCtlThcIA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 19 Feb 2019 22:57:53 -0800 (PST)
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 A6AC212426A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 19 Feb 2019 22:57:53 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AC95DB80415; Tue, 19 Feb 2019 22:57:37 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id B2607B803CA; Tue, 19 Feb 2019 22:57:35 -0800 (PST)
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
Message-Id: <20190220065735.B2607B803CA@rfc-editor.org>
Date: Tue, 19 Feb 2019 22:57:35 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8534_on_Explicit_Tracking_with_Wildcard?= =?utf-8?q?_Routes_in_Multicast_VPN?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8534

        Title:      Explicit Tracking with Wildcard Routes 
                    in Multicast VPN 
        Author:     A. Dolganow, 
                    J. Kotalwar,
                    E. Rosen, Ed.,
                    Z. Zhang
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2019
        Mailbox:    andrew.dolganow@nokia.com, 
                    jayant.kotalwar@nokia.com, 
                    erosen52@gmail.com,
                    zzhang@juniper.net
        Pages:      21
        Characters: 49896
        Updates:    RFC 6514, RFC 6625, RFC 7524, RFC 7582, RFC 7900

        I-D Tag:    draft-ietf-bess-mvpn-expl-track-13.txt

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

        DOI:        10.17487/RFC8534

The base Multicast VPN (MVPN) specifications (RFCs 6513 and 6514)
provide procedures to allow a multicast ingress node to invoke
"explicit tracking" for a multicast flow or set of flows, thus
learning the egress nodes for that flow or set of flows.  However,
the specifications are not completely clear about how the explicit
tracking procedures work in certain scenarios.  This document
provides the necessary clarifications.  It also specifies a new,
optimized explicit-tracking procedure.  This new procedure allows an
ingress node, by sending a single message, to request explicit
tracking of each of a set of flows, where the set of flows is
specified using a wildcard mechanism.  This document updates RFCs
6514, 6625, 7524, 7582, and 7900.

This document is a product of the BGP Enabled Services 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org