Re: draft-ietf-ptomaine-nopeer-01.txt

[Alex Zinin <zinin@psg.com>]

Randy,

> a - the whole purpose of this exercise is to create a well-known
>     community that operators treat as transitive

Let's not play the words. IANA allocation is done in protocol-specific
terms. Unlike BGP attributes, communities do not have the
well-know/optional characteristic. Transitivity is defined for
extended communities, not the regular ones. IANA and the potential
reader will need to ignore these words to avoid confusion.

> b - as there is no extended community (show me the rfc), the current
>     reference is not ambiguous.

When/if there is one, the document will be confusing. The draft
doesn't even have a ref to the doc defining the communities it talks
about.

Alex

> we have been 'round all this before!

> randy