Subject: RFC 7385 on IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points

From: [email-masked]
Date: Fri, 10 Oct 2014 13:46:39 -0700 (PDT)

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

        RFC 7385

        Title:      IANA Registry for P-Multicast Service 
                    Interface (PMSI) Tunnel Type Code Points 
        Author:     L. Andersson, G. Swallow
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2014
        Mailbox:    [email-masked], 
                    [email-masked]
        Pages:      4
        Characters: 6690
        Updates:    RFC6514

        I-D Tag:    draft-ietf-l3vpn-pmsi-registry-07.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7385.txt

RFC 6514 created a space of Tunnel Type code points for a new BGP
attribute called the "P-Multicast Service Interface Tunnel 
(PMSI Tunnel) attribute".  However, the RFC did not create a corresponding
IANA registry.

There now is need to make further code point allocations from this
name space.  This document serves to update RFC 6514 in that it
creates an IANA registry for that purpose.

This document is a product of the Layer 3 Virtual Private Networks 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/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC