Re: [Idr] [Editorial Errata Reported] RFC8092 (4962)

[Job Snijders <[e-mail]>]

On Thu, Mar 09, 2017 at 07:21:56AM -0800, RFC Errata System wrote:
> The following errata report has been submitted for RFC8092, "BGP Large
> Communities Attribute".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=8092&eid=4962
> 
> --------------------------------------
> Type: Editorial
> 
> Section: 3
> 
> Original Text
> -------------
>    Duplicate BGP Large Community values MUST NOT be transmitted. A
>    receiving speaker MUST silently remove redundant BGP Large
>    Community values from a BGP Large Community attribute.
> 
> Corrected Text
> --------------
>    Duplicate BGP Large Community values MUST NOT be transmitted. A
>    receiving speaker MUST silently remove redundant BGP Large
>    Community values from a BGP Large Communities attribute.

I suggest to reject this errata. The name of the BGP Path Attribute is
singular, namely "LARGE_COMMUNITY" (see IANA's "Border Gateway Protocol
(BGP) Parameters" registry for "BGP Path Attributes")

There somewhat is a lack of semantic precision on when to use
"community" and when to use "communities", but there is no other
commonly accepted jargon for what we're talking about in IETF creole
language. In this sense RFC 8092 was aligned with RFC 1997. Sorry for
the confusion, but we didn't see a way around it.

If you are an implementer, feel free to reach out to me off list, I'd be
happy to help clarify, confirm your understanding of the specification
and perhaps help with interop testing.

Kind regards,

Job