
Subsequence Address Family Identifiers (SAFI) - per [RFC-ietf-idr-rfc2858bis-10.txt]

(last updated 2006-11-02)

As specified in this document, the MPL_REACH_NLRI and MP_UNREACH_NLRI
attributes contain the Subsequence Address Family Identifier (SAFI)
field. The IANA will maintain and register values for the SAFI namespace 
as follows.  

Registration Procedures: 
4 - 63:    Standards Action or Early Allocation policy
64 - 127:  First Come First Served
128 - 240: Some recognized assignments below, others Reserved
241 - 254: Private Use (not to be assigned)

Value    Description                                     Reference
-----    -----------                                     ---------
0        Reserved			                 [RFC-ietf-idr-rfc2858bis-10.txt]

1        Network Layer Reachability Information used     [RFC-ietf-idr-rfc2858bis-10.txt]
         for unicast forwarding	

2        Network Layer Reachability Information used     [RFC-ietf-idr-rfc2858bis-10.txt] 
         for mulitcast forwarding
	
3        Reserved                                        [RFC-ietf-idr-rfc2858bis-10.txt]

4        Network Layer Reachability Information (NLRI)   [RFC3107]
         with MPLS Labels

5-63     Unassigned (Standards Action or Early Allocation)

64       Tunnel SAFI                                    [Nalawade]

65       Virtual Private LAN Service (VPLS)             [draft-ietf-l2vpn-vpls-bgp]

66       BGP MDT SAFI                                   [Nalawade]

67       BGP 4over6 SAFI                                     [Cui]

68       BGP 6over4 SAFI                                     [Cui]

69-127   Unassigned (FCFS)

128      MPLS-labeled VPN address                        [RFC4364]

129      Multicast for BGP/MPLS IP Virtual Private       [RFC2547]
         Networks (VPNs)

130-131  Reserved                                       [RFC-ietf-idr-rfc2858bis-10.txt]

132      Route Target constrains                        [draft-ietf-l3vpn-rt-constrain]

133      Dissemination of flow specification rules      [draft-marques-idr-flow-spec]

134      Dissemination of flow specification rules      [draft-marques-idr-flow-spec]

135-139  Reserved                                       [RFC-ietf-idr-rfc2858bis-10.txt]

140      VPN auto-discovery                             [draft-ietf-l3vpn-bgpvpn-auto]

141-240  Reserved                                       [RFC-ietf-idr-rfc2858bis-10.txt]

241-254  Private Use                                    [RFC-ietf-idr-rfc2858bis-10.txt]

255      Reserved                                       [RFC-ietf-idr-rfc2858bis-10.txt]


References
----------
[RFC2547]  E. Rosen and Y. Rekhter, "BGP/MPLS VPNs", RFC 2547, March 1999.

[RFC3107]  Y. Rekhter and E. Rosen, "Carrying Label Information in 
           BGP-4", RFC 3107, May 2001.

[RFC4364]  E. Rosen and Y. Rekhter, "BGP/MPLS IP VPNs", RFC 4364, February 2006.

[RFC-ietf-idr-rfc2858bis-10.txt]
           T. Bates, R. Chandra, D. Katz and Y. Rekhter, "Multiprotocol 
           Extensions for BGP-4", RFC XXXX, Month Year.

[RFC-ietf-l3vpn-rt-constrain] 
           P. Marques, R. Bonica, L. Fang, L. Martini, R. Raszuk, K. Patel
           and J. Guichard, "Constrained VPN Route Distribution", RFC XXXX,
           Month Year.

[RFC-ietf-l2vpn-vpls-bgp-08.txt] 
           K. Kompella and Y. Rekhter, "Virtual Private LAN Service 
           (VPLS) Using BGP for Auto-discovery and Signaling", RFC XXXX,
           Month Year.

[draft-ietf-l3vpn-bgpvpn-auto]  Work-in-Progress

[draft-marques-idr-flow-spec]   Work-in-Progress


People
------
[Bates] Tony Bates, <tbates@cisco.com>, July 2000. 

[Cui]  Yong Cui, <cuiyong@tsinghua.edu.cn>, 15 August 2006, 20 September 2006.

[Nalawade]  Gargi Nalawade, <gargi@cisco.com>, January 2004. 
           (draft-nalawade-kapoor-tunnel-safi-01.txt)  
           (draft-nalawade-idr-mdt-safi-00.txt), February 2004.

(created July 2000)

[] 



