Re: [mpls] Working Group adoption call for draft-decraene-idr-next-hop-capability-03

Dear authors,

Some of the language sounds similar to that in draft-ietf-idr-tunnel-encaps.
Did you consider augmenting tunnel-encaps in order to signal EL by
adding a new sub-TLV ? It is a transitive attribute but it has a
Remote Endpoint sub-TLV to bind the capability to the specific nexthop.
(It may require a new "tunnel type" to represent plain MPLS nexthops.)

This would avoid the need to upgrade all the BGP speakers between egress
and ingress. tunnel-encaps also has a Color sub-TLV that can be useful,
for example, when using recursive resoltion, to select a subset of overlay
prefixes that would actually use EL for forwarding.

That said, some nitpicks:
- dependant==>dependent; infact it can be totally avoided and just
call it "Nexthop capabilites"
- that said, it would be better to avoid reusing the term "Capabilities"
for this
attribute though I understand you are trying to draw a parallel with
session capabilities

thanks--shyam

On Thu, May 18, 2017 at 9:32 AM, John G. Scudder <jgs@juniper.net> wrote:

> Hi All,
>
> IDR working group adoption has been requested for
> draft-decraene-idr-next-hop-capability-03. Please send your comments to
> the IDR mailing list before June 2, 2017. Please remember that we need
> affirmative support in order to adopt the draft, so don't be shy.
>
> draft datatracker page: https://datatracker.ietf.org/
> doc/draft-decraene-idr-next-hop-capability/
> slides from IETF-98: https://www.ietf.org/proceedings/98/slides/slides-
> 98-idr-08-bgp-next-hop-dependent-capabilities-00.pdf
>
> Since in part this draft specifies a replacement for the Entropy Label
> Capability Attribute (ELCA) that was defined by the MPLS WG in RFC 6790 and
> deprecated by RFC 7447, I have cc'd the MPLS WG mailing list. Since the
> proposed new attribute is a generic container with the ELCA replacement
> just the first application, the current draft is targeted to IDR and not
> MPLS (this was discussed during IETF-93).
>
> Thanks,
>
> --John
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>