Re: [Idr] I-D Action: draft-ietf-idr-tunnel-encaps-00.txt

[Lou Berger <[e-mail]>]

Authors/WG,
    Now that we have a WG draft on this topic, I'd like to propose that
this draft deprecate the Encap SAFI and obsolete/replace RFC5512. 

I'm not sure if anyone else has implemented Encap SAFI, but we have and
found it to be much more complex and limiting than just using the Encap
Attribute ala the new draft.

Also, I can propose specific text changes needed if the Authors wish,
but I suspect they can handle this themselves!

Thanks,
Lou

On 8/19/2015 2:59 PM, [e-mail] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Inter-Domain Routing Working Group of the IETF.
>
>         Title           : Using the BGP Tunnel Encapsulation Attribute without the BGP Encapsulation SAFI
>         Authors         : Eric C. Rosen
>                           Keyur Patel
>                           Gunter Van de Velde
> 	Filename        : draft-ietf-idr-tunnel-encaps-00.txt
> 	Pages           : 29
> 	Date            : 2015-08-19
>
> Abstract:
>    RFC 5512 defines a BGP Path Attribute known as the "Tunnel
>    Encapsulation Attribute".  This attribute allows one to specify a set
>    of tunnels.  For each such tunnel, the attribute can provide
>    additional information used to create a tunnel and the corresponding
>    encapsulation header, and can also provide information that aids in
>    choosing whether a particular packet is to be sent through a
>    particular tunnel.  RFC 5512 states that the attribute is only
>    carried in BGP UPDATEs that have the "Encapsulation Subsequent
>    Address Family (Encapsulation SAFI)".  This document updates RFC 5512
>    by deprecating the Encapsulation SAFI (which has never been used),and
>    by specifying semantics for the attribute when it is carried in
>    UPDATEs of certain other SAFIs.  This document also extends the
>    attribute by enabling it to carry additional information needed to
>    create the encapsulation headers additional tunnel types not
>    mentioned in RFC 5512.  Finally, this document also extends the
>    attribute by allowing it to specify a remote tunnel endpoint address
>    for each tunnel.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-tunnel-encaps/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-idr-tunnel-encaps-00
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>