1. BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute draft-pmohapat-idr-info-safi-02.txt Pradosh Mohapatra and Eric Rosen Cisco Systems IETF-69, July 26, 2007

2. The story so far Prior versions of this draft describe a BGP- based approach to signal encapsulation information between edge routers: –NLRI = –Defined a tunnel encapsulation attribute that has a TLV format (and sub-TLVs) to encode the encapsulation parameters. –Defined tunnel encapsulation format for L2TPv3 and GRE.

3. Changes from -00 version (based on comments) Renamed to “encap-SAFI” to better indicate intended usage. Use of encap-SAFI restricted to cases where AFI is either IPv4 or IPv6. NLRI simplified by removal of “distinguisher” field. Clarified that the NLRI is defined by a combination of (consistent with draft-ietf-idr-v4nlri-v6nh). Reworked the abstract and introduction sections to give clear explanation of when encap-SAFI is and is not useful.

4. Changes from -00 version (based on comments) Justification for use of encap-SAFI (rather than new attribute) given Justification for use of single SAFI covering multiple encapsulations, rather than one SAFI per encapsulation given. Clarification of processing by a BGP speaker that does not understand some sub-TLV. New “opaque extended community” defined: can be used in cases where encap-SAFI is not really needed (i.e. no encapsulation parameters to signal).

5. Next steps WG document? Referenced by softwires mesh framework, like draft-ietf-idr-v4nlri-v6nh.