NTAC Peering Working Group

[Michael H Lambert <>]

My apologies, Matt.  I obviously didn't have the output from our Brocade 
parsed quite right.  Although they could probably have spent more effort in 
sane formatting of that output...

Michael

> On 2 May 2018, at 15:19, Matt Mullins 
> <>
>  wrote:
> 
> Hi Michael,
> 
> 11537:66 - Learned from rtsw.sunn
> 11537:226 - Learned from rtsw.star
> 11537:238 - Learned from rtsw.minn
> 11537:251 - Learned from rtsw.paix
> 11537:2502 - Internal use for International/federal routes
> 
> The ones below we do not see in our configurations:
> 
> 11537:2
> 11537:9
> 11537:20
> 11537:25
> 11537:50
> 11537:200
> 11537:550
> 
> 
> I will get the NOC BGP Community page updated with the known communities.  
> Jeff and I have been discussing a new BGP community strategy that we hope 
> will standardize the communities a bit more between Internet2’s different 
> networks.
> 
> Thank you,
> 
> Matt Mullins
> Team Lead - Internet2 Network Infrastructure
> GlobalNOC at Indiana University
> 
> 317-278-6622
> 
>> On May 1, 2018, at 1:53 PM, Michael H Lambert 
>> <>
>>  wrote:
>> 
>> In working with Brad on the community tagging document we talked about on 
>> the last call, I thought I would take a look at the communities we are 
>> actually seeing.  I've only done R&E so far.  The following are not 
>> documented on the NOC BGP Communities web page:
>> 
>> 11537:2
>> 11537:9
>> 11537:20
>> 11537:25
>> 11537:50
>> 11537:66
>> 11537:200
>> 11537:226
>> 11537:238
>> 11537:251
>> 11537:550
>> 11537:2502
>> 
>> Could someone who can do so please update that web page with definitions 
>> of these values?
>> 
>> Thanks,
>> 
>> Michael
>> 
>

Attachment: signature.asc
Description: Message signed with OpenPGP