RFC 9081 on Interoperation between Multicast Virtual Private Network (MVPN) and Multicast Source Directory Protocol (MSDP) Source-Active Routes

rfc-editor@rfc-editor.org Fri, 23 July 2021 05:03 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 (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DB4C33A1CBD; Thu, 22 Jul 2021 22:03:27 -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 qotAZsY9wpsO; Thu, 22 Jul 2021 22:03:22 -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 775BB3A1CB8; Thu, 22 Jul 2021 22:03:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B1B38F4077E; Thu, 22 Jul 2021 22:03:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwODEgb24gSW50ZXJvcGVyYXRpb24gYmV0d2VlbiBNdWx0aWNhc3QgVmlydHVhbCBQcml2YXRlIE5ldHdvcmsgKE1WUE4pIGFuZCBNdWx0aWNhc3QgU291cmNlIERpcmVjdG9yeSBQcm90b2NvbCAoTVNEUCkgU291cmNlLUFjdGl2ZSBSb3V0ZXM=?=
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, bess@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210723050308.B1B38F4077E@rfc-editor.org>
Date: Thu, 22 Jul 2021 22:03:08 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/S8PO_s66JwbP8YC4kk8sVSnjtd4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 23 Jul 2021 05:03:28 -0000

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

        RFC 9081

        Title:      Interoperation between Multicast Virtual Private 
                    Network (MVPN) and Multicast Source Directory 
                    Protocol (MSDP) Source-Active Routes 
        Author:     Z. Zhang,
                    L. Giuliano
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2021
        Mailbox:    zzhang@juniper.net,
        Pages:      6
        Updates:    RFC 6514

        I-D Tag:    draft-ietf-bess-mvpn-msdp-sa-interoperation-08.txt

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

        DOI:        10.17487/RFC9081

This document specifies the procedures for interoperation between
Multicast Virtual Private Network (MVPN) Source-Active (SA) routes
and customer Multicast Source Discovery Protocol (MSDP) SA routes,
which is useful for MVPN provider networks offering services to
customers with an existing MSDP infrastructure. Without the
procedures described in this document, VPN-specific MSDP sessions are
required among the Provider Edge (PE) routers that are customer MSDP
peers. This document updates RFC 6514.

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

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