Date: Fri, 29 Mar 2024 15:51:38 +0000 (UTC) Message-ID: <571033519.8212.1711727498262@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8211_1316076640.1711727498261" ------=_Part_8211_1316076640.1711727498261 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
NTAC Peering working Group
11/20/07
In attendance: Jeff Bartig, Cort Buffington, Matt Davy, Leo Donnelly, Li= nda Roos, Steve Wallace
Agenda
1. Agenda bash
2. Mailing list for working group
3. Updates from Internet2 on CPS
4. Suggestions for a Periodic/quarterly Internet2 CPS Technical Update
5. Discuss suggestion of migrating commercial IPv6 peers to CPS
6. Internet2 IPv6 transit
1. Mailing list for working group
Linda has requested that a mailing list for the group be created by Intern=
et2. She will send a notification to the entire NTAC list and will ask anyo=
ne interested to request a subscription.
2. Updates from Internet2 on CPS
Since the last NTAC meeting, five new peers and 4500 new routes have been =
added. In addition, capacity to existing peers has been increased. The serv=
ice continues to grow.
Both Indiana and NOX have started to see 50% or more commodity traffic use=
the peering service. Steve has indicated that he will create a reasonable =
way to share information regarding the peers with this group.
3. Suggestions for a Periodic/quarterly Internet2 CPS Technical Update
Jeff asked for input on what the group would like to see in a technical up=
date from Internet2. The group indicated that they would like to have an up=
date on:
=E2=80=A2 Traffic loads
=E2=80=A2 Traffic balances
=E2=80=A2 Updates on new peers
=E2=80=A2 Traffic on backbone links=E2=80=94capacity planning
Additionally, the members of the group were asked to provide information r=
egarding local CPS configurations perhaps including a logical picture of ho=
w they are connected. Steve will work with Linda for target dates for quart=
erly updates during regularly scheduled calls.
4. Discuss suggestion of migrating commercial IPv6 peers to CPS
At the last NTAC meeting, Steve indicated that Internet2 would like to mov=
e IPv6 peers to CPS. The group reviewed a proposal provided by Steven Walla=
ce. Discussion ensued regarding this topic. In an email, Dave Farmer recomm=
ended that the connector migration to provider-independent IPv6 prefixes no=
t be tied to the commercial v6 migration to CPS. The group agreed to delive=
r both messages to connectors at the same time when it makes sense. The gro=
up recommended that the NOC work to make testing points available to both V=
RFs.
Additionally, the group agreed that Steve will create a letter to be del= ivered with the updated proposal to the IPv6 working group. The IPv6 workin= g group will be asked to indicate their desired level of involvement in thi= s issue. Steve will copy the peering working group on the communication.
5. Internet2 IPv6 transit
Jeff indicated that Internet2 is providing IPv6 transit through the R&=
E VRF and he asked if transit will be moved to CPS VRF. Matt Davy indicated=
that this makes the most sense. Moving IPv6 transit into the CPS VRF expan=
ds the possible locations and providers Internet2 could use for transit to =
include all of the CPS peering locations. Moving IPv6 transit to the CPS VR=
F may also encourage connectors to make the transition to peering with the =
CPS VRF for IPv6 commercial peering on a reasonable schedule. Matt Davy ind=
icated that this information needs to be added to the document. Steve will =
add this to the document and send an updated version to the group.
6. Other business
Steve indicated that there has been confusion, at least in Europe, about w=
hat CPS is. Steve talked to some European colleagues at the last member mee=
ting and when they understood that CPS is not transit, they were interested=
and there may be an opportunity to do something with Europe with respect t=
o v6 peering internationally. The group endorsed Steve pursuing these discu=
ssions. If anything develops, Steve will bring it back to the group for inp=
ut and assistance in developing the service.