NTAC Peering Working Group

["Schmiedt, Dan" <>]

   

1. Agenda Bash

1. There was no agenda bashing.

Update on peering and I2PX

1. Progress on moving Net+ peers out of the R&E table

1. US-West AWS routes have been moved out of R&E table.
2. Fallout – one institution with just R&E had traffic switch to paid traffic.  Fixed by turning up I2PX but only for AWS routes, filtered on the I2 side.  Similar fix could be done by any I2PX peer with appropriate community strings on peering.
3. New POP in Newark, 165 Halsey – replacing 111 8^th – now completely operational.  Connects back to primary NY POP (32 AoA).  Reaching out to peers to move them to 165 Halsey.  Hopefully more success to report by next month.  Several peers looking to increase capacity during move.

Network Weather Update – Trends and Coming Events

1. Traffic seems to down, likely due to spring break.

Internet2 Network Updates

1. Working on Kentik for netflow analysis, moving from Nokia Deepfield with good progress.

1. Now working on portal capability to give others a portal view (regional network, connectors, some campuses).
2. Would be filtered to give view of just the appropriate traffic.

All routers moved to IPFIX from Netflow 9.In coming weeks, will be splitting v4 and v6 to separate iBGP meshes.  Due to issue with Kentik getting next hops correctly because of incorrect Cisco implementation that used most significant bits instead of least significant bits.  May also resolve some v6 traceroutes across the network.Route reports previously distributed by Steve Wallace. 

1. See: https://console.internet2.edu/
2. Click on RE and I2PX – Debug routing problems
3. Please report any issues/anomalies.

Optical: OFCNet conference is coming up soon.  Will be lighting up first terabit plus waves on Cienna Wavelogic 6e – hope to take terabit to show floor.  JoAnne learned that they can peer with convention center.Optical SIG forming – goal to start meeting in mid-April.LOSA2 – router replacements.  Will be installing NCS 57D2 routers to do per vlan shaping so can offer directconnect/expressroute services in Los Angeles.  Replacing 8202 peering routers. Campus border route policy best practices

1. No updates.

Community peering needs and issues

1. Farmer: Wasabi traffic appears to be incoming via Zayo?

1. I2 peers with Wasabi in Ashburn and LA.  May have added another region.  Farmer to send prefixes to Bartig to investigate.

Any other business?

1. Schmiedt: one large university failed to pay MERIT invoice and IRR records were suspended.  Issue was corrected quickly with MERIT, but Tier-1 ISPs (eg, LUMEN) update prefix filters on their own schedule and will be difficult to get to do a manual update.  This is a cliff that others would do well to avoid.  Recommend others review state of IRR/billing contacts.

1. Discussion of how much longer ISPs will pay attention to RADb and other sources other than ARIN/regional Internet registry.  Unclear.
2. Suggestion to have one ISP that does not depend on IRR.  Downstream ISPs will still likely be impacted, but this might give some connectivity in the event of an unexpected billing failure.
3. Noted that these invoices are typically small ($3-400) and are thereby easier to miss than the big invoices, especially when looking for major recurring missing bills.