[bess] RFC 7902 on Registry and Extensions for P-Multicast Service Interface Tunnel Attribute Flags

rfc-editor@rfc-editor.org Thu, 09 June 2016 01:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1348412D8ED; Wed, 8 Jun 2016 18:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.628
X-Spam-Level:
X-Spam-Status: No, score=-105.628 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 wqfn59e1ef_s; Wed, 8 Jun 2016 18:40:32 -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 EF2AC12D8F2; Wed, 8 Jun 2016 18:40:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9EB63B80B28; Wed, 8 Jun 2016 18:40:10 -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
Message-Id: <20160609014010.9EB63B80B28@rfc-editor.org>
Date: Wed, 08 Jun 2016 18:40:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/HVYCZeh_R6h2w-pXHe9uaXIXd2U>
Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org
Subject: [bess] RFC 7902 on Registry and Extensions for P-Multicast Service Interface Tunnel Attribute Flags
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2016 01:40:37 -0000

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

        
        RFC 7902

        Title:      Registry and Extensions for P-Multicast 
                    Service Interface Tunnel Attribute Flags 
        Author:     E. Rosen, T. Morin
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2016
        Mailbox:    erosen@juniper.net, 
                    thomas.morin@orange.com
        Pages:      7
        Characters: 14332
        Updates:    RFC 6514

        I-D Tag:    draft-ietf-bess-pta-flags-03.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7902

The BGP-based control procedures for Multicast Virtual Private
Networks (MVPNs) make use of a BGP attribute known as the
"P-Multicast Service Interface (PMSI) Tunnel" attribute.  The
attribute contains a one-octet "Flags" field.  The purpose of this
document is to establish an IANA registry for the assignment of the
bits in this field.  Since the "Flags" field contains only eight
bits, this document also defines a new BGP Extended Community,
"Additional PMSI Tunnel Attribute Flags", that can be used to carry
additional flags for the "P-Multicast Service Interface (PMSI)
Tunnel" attribute.  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
  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