Re: [Idr] Support for 4-byte generic communities in BGP

I strongly agree that support for 4-octet AS numbers in extended
communities is a problem which needs to be solved.

Here are some comments on the draft:

Add a reference to [RFC4360].

Only 2 bytes for the Local Administrator field seems very restrictive.

Do we need a capability (for capability negotiation) for this? (Just
because a speaker supports 4-octet AS numbers does not necessarily
imply it supports 4-octet AS numbers in extended communities).

Do we need rules on what to do when a NEW speaker sends an UPDATE with
a 4-octet extended community to an OLD speaker (similar to section
4.2.2. of [RFC4893])?

It seems relatively straightforward to include all relevant
information in this draft and remove the references to
[I-D.ietf-l3vpn-as4octet-ext-community
<http://tools.ietf.org/html/draft-dhrao-idr-4octet-extcomm-generic-subtype-00#ref-I-D.ietf-l3vpn-as4octet-ext-community>]
(this makes it a "stand-alone" draft).

On Thu, Nov 20, 2008 at 7:51 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:

> On Tue, Nov 18, 2008 at 01:50:10PM -0500, Jeffrey Haas wrote:
> > Given the (typical) lack of response in the mail list, I'd like to
> > request a room poll for this at the upcoming IDR session.  Since the
> > feature is straight forward, I don't believe we need to take the time to
> > give a presentation.
>
> It would appear a presentation would have been helpful.  While we have
> gotten an additional few people noting support on the mailing list, the
> lack of familiarity with the draft seems to be at issue.
>
> I'd like to encourage all of IDR to take a quick look at
> draft-dhrao-idr-4octet-extcomm-generic-subtype and indicate support or
> lack of support for this document.  We currently do not have a 4-byte AS
> equivalent standard community and this is going to be an increasingly
> large issue for operators as we deploy 4 byte ASes.
>
> Per the IDR session, we do not have enough visible support to adopt this
> draft.  I find that honestly shocking.
>
> Don't make me go rattling on mailing lists like NANOG for support. :-)
>
> -- Jeff
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>