Re: [Idr] I-D Action: draft-ietf-idr-large-community-05.txt

[t.petch <[e-mail]>]

Job

a minor administrative point; the RFC Editor commonly imposes a
constraint of five names on the first page, and this list has now grown
to six.  A common practice is to have just one name on the front, that
of the pen-holder, and list the others at the back, differentiating, at
the back, between those who have made a major contribution and those who
have not.  Cutting out one from six may be more problematic:-(

Tom Petch


--- Original Message -----
From: "Job Snijders" <[e-mail]>
To: <[e-mail]>
Sent: Wednesday, October 26, 2016 8:18 PM


> Dear Working Group,
>
> ChangeLog:
>
>     o New Early IANA Allocation!
>     o Reduce ambiguity, UINT_MAX -> UINT16_MAX (John Heasley)
>     o Remove empty attribute error handling sentence, thus default to
7606 (David Freedman, Jeff, Jakob)
>
> In a twisted turn of events, this effort has ended up with BGP Path
> Attribute value 32 - very befitting if you look at the very problem
> we're trying to solve :-)
>
> Kind regards,
>
> Job
>
>
> On Wed, Oct 26, 2016 at 12:10:46PM -0700, [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 of the IETF.
> >
> >         Title           : Large BGP Communities
> >         Authors         : Jakob Heitz
> >                           Job Snijders
> >                           Keyur Patel
> >                           Ignas Bagdonas
> >                           Adam Simpson
> >                           Nick Hilliard
> > Filename        : draft-ietf-idr-large-community-05.txt
> > Pages           : 9
> > Date            : 2016-10-26
> >
> > Abstract:
> >    This document describes the Large BGP Communities attribute, an
> >    extension to BGP-4.  This attribute provides a mechanism to
signal
> >    opaque information within separate namespaces to aid in routing
> >    management.  The attribute is suitable for use in four-octet
ASNs.
> >
> >