IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points

IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points Huawei Technologies



        loa@mail01.huawei.com



    
     Cisco Systems
     
      swallow@cisco.com
     
    

    



    


      
      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.



  
  
    
    
     
      In 'BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs'
      , an optional transitive BGP attribute called the
      "P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute" is 
      specified. This BGP attribute uses an octet field to specify the PMSI
      tunnel type.  RFC 6514 allocates the values 0-7. 
     
     
     
       There is now a need to make further code point allocations from
      this name space.  In particular, "Inter-Area P2MP Segmented LSPs"
       needs to make such
      an allocation. However, the RFC did not create an
      IANA registry for these code points.
     
    
     
      This document creates a new IANA registry called "P-Multicast
      Service Interface Tunnel (PMSI Tunnel) Tunnel Types" for these
      code points.  The registry is created in the "Border Gateway
      Protocol (BGP) Parameters" registry.
     
     
     
      Creating this registry is an update of RFC 6514 .
     
    
     
      
    
    
    
     This document simply creates an IANA registry from a table in RFC
     6514.  Thus, there are no security concerns.
    
    
    

     
    
    
    
     IANA has created a new registry called "P-Multicast Service 
      Interface Tunnel (PMSI Tunnel) Tunnel Types" in the "Border Gateway 
      Protocol (BGP) Parameters" registry.
    
    
    
     The allocation policy for values 0x00 to 0xFA is IETF Review 
     .  Values
     0xFB to 0xFE are experimental and are not to be assigned. 0xFF is
     reserved, the status of 0xFF may only be changed through Standards
     Action .
    
    
    
    
    The initial registry should appear as:
    
    
      
         
    
    
    
        


    
  

  
 
    





Guidelines for Writing an IANA Considerations Section in RFCs






Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).</t><t> In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.</t><t> This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.













BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs










This document describes the BGP encodings and procedures for exchanging the information elements required by Multicast in MPLS/BGP IP VPNs, as specified in RFC 6513. [STANDARDS-TRACK]






    

    







Inter-Area P2MP Segmented LSPs


    



    




This document describes procedures for building inter-area point-to- multipoint (P2MP) segmented service LSPs by partitioning such LSPs into intra-area segments and using BGP as the inter-area routing and label distribution protocol. Within each IGP area the intra-area segments are either carried over intra-area P2MP LSPs, using P2MP LSP hierarchy, or instantiated using ingress replication.  The intra-area P2MP LSPs may be signaled using P2MP RSVP-TE or P2MP mLDP. If ingress replication is used within an IGP area, then (multipoint-to-point) LDP LSPs or (point-to-point) RSVP-TE LSPs may be used in the IGP area. The applications/services that use such inter-area service LSPs may be BGP Multicast VPN, VPLS multicast, or global table multicast over MPLS.








    

    
      
      The authors want to thank Adrian Farrel for unwavering support and our 
      L3VPN, MPLS, and IDR co-chairs for swift processing of this document.