Date: Fri, 29 Mar 2024 07:17:07 +0000 (UTC) Message-ID: <1349140883.7607.1711696627767@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7606_217581400.1711696627765" ------=_Part_7606_217581400.1711696627765 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
NTAC Peering
10/20/09
In attendance: Jeff Bartig, Brian Cort, Bob Collie, David Crowe, Cas=
D'Angelo, Akbar Kara, Lonnie Leger, Caren Litvanyi, Darrell Newcomb, Dave =
Reese, Chris Robb, Linda Roos, Steve Wallace, Matt Zekauskas
Agenda
1. Update from Internet2 on peering
2. Discussion re: Proposed Architecture for a Combined C=
PS and TR Service
Action Items:
Jeff will send a note to the mailing list asking for feedback on the Peeri=
ng Architecture document.
Meeting Notes
1. Update from Internet2 on peering
Caren Litvanyi mentioned that there is now light between the CPS and TR ro=
uters in DC. She also mentioned that there is work on obtaining a ris=
er and cross connect with Akamai in NY. Chris Robb mentioned that the=
next set of 10GE waves between Houston and LA and between Houston and KC h=
ave been lit. Chris encouraged those on the call to investigate the A=
rbor Network presentation at NANOG:http://nanog.org/meetings/nanog47/abstracts.php?pt=3DMTQ1MyZuYW5vZz=
Q3&nm=3Dnanog47
2. Discussion re: Proposed Architecture for a Combined C=
PS and TR Service
The CPS/TR Combined Architecture document is the result of meeting held in=
September in Indy. Those attending incleded Darrell Newcomb, Dave Re=
ese, Caren Litvanyi, Matt Davy, Jeff Bartig, Rob Vietzke, Steve Wallace and=
Chris Robb. Jeff asked those on the call for feedback on the documen=
t. Jeff reviewed the following points from the CIC TAC (sent via emai=
l to the NTAC peering list on 10/20/09):
The CIC TAC expresses a str=
ong desire that the openness and transparency associated with the Internet2=
CPS service be continued in a consolidated service. There is concern=
about the perceived lack of transparency with TransitRail (no publicly acc=
essible data, graphs, router proxy). As the networks are combined, th=
is lack of access to information will need to be reversed. There is a=
lso a strong desire that there be a method for the community to help direct=
the peering strategy, like there has been with CPS.IPv6 support w=
as not mentioned in the architecture document. While CPS has good IPv=
6 connectivity today, TransitRail does not. If we will be migrating t=
o the TransitRail ASN, it will need to establish equivalent IPv6 peering be=
fore the CPS (AS11537) commercial IPv6 peers are shutdown. IPv6 suppo=
rt is seen as an absolute requirement. Many CPS participants rely on CPS fo=
r either primary or backup global IPv6 transit.{_}The CIC TAC looks fo=
rward to seeing the complete consolidation proposal that includes budget an=
d governance details._Dave Reese mentioned that some of the points raised b=
y the CIC had been addressed in an earlier document. He mentioned tha=
t the same tools that have been used for CPS will be used for the combined =
services. The earlier document also mentioned a strong commitment to =
IPv6. Transparency is important to the project. Steve encourage=
d Dave Reese to provide an email response to the CIC. There were inqu=
iries regarding a budget for the combined service and Dave indicated that c=
reating a budget is difficult because the combined budget would include gro=
wth and previous budgets for each of the services were static. To dea=
l with this, a static budget was created for the combined services to allow=
comparison to the static budgets for the individual services. As the=
project progresses, the peering working group will be involved in budget b=
ecause that budget will include future growth of the combined service and i=
nput from the peering working group is needed to predict the rate of growth=
.
Steve Wallace mentioned that the group that created draft architecture wou=
ld like to have feedback from the NTAC peering working group as well as the=
entire NTAC this week. Jeff will send a note to the NTAC mailing list aski=
ng for feedback. The group is seeking feedback on this question: does=
this document encompass the technical architecture for the combined servic=
e?
After receiving endorsement of the document, the next step will be for Dav=
e Reese and Rob Vietzke to ask their organizations for a letter of commitme=
nt on the combined service. Work will also continue on the budget for=
the service.