Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-acceptown-community-01.txt

["Pradosh Mohapatra (pmohapat)" <pmohapat at cisco.com>]

| Robert -
| 
| In the L3VPN WG I asked a question on your use of well-known 
| BGP communities in this draft (as it is related to the IANA 
| BGP Well- Known Communities reservation procedures discussed 
| in IDR).  The question was "how do you know when the 
| community is well-known throughout the internet or service 
| provider network?" You answer was "it is off by default and 
| you have to configure it to be on, therefore the operator 
| knows what they are doing." That is a fine answer but, you 
| are using this as a reserved codepoint vs the semantics of 
| well-known communities (in which if a router receives the 
| well-known community whether configured or not, action is taken).  
| Does anyone care about the change of semantics and a router 
| will not pay attention to the community without configuration?

Going by the rule that well-known communities have global
significance & should be implemented by any community-attribute-
aware BGP speaker, I would agree to your earlier proposal that
split the reserved space and have some set of communities that
are either IANA allocated or FCFS allocated... and just call
the new ones reserved communities (*not* well-known). That also 
aligns with the fact that all BGP attributes defined later 
(than 1771) become optional by definition ;-)

- Pradosh

| 
| Thanks
| 
| -DWard
_______________________________________________
Idr mailing list
Idr at ietf.org
https://www.ietf.org/mailman/listinfo/idr