Skip to Content.
Sympa Menu

ntacpeering - Re: Connector <-> TR-CPS paths with respect to AL2S/L3 Architecture discussions

Subject: NTAC Peering Working Group

List archive

Re: Connector <-> TR-CPS paths with respect to AL2S/L3 Architecture discussions


Chronological Thread 
  • From: David Pokorney <>
  • To: Darrell Newcomb <>
  • Cc: , Shel Waggener <>, Dave Pokorney <>
  • Subject: Re: Connector <-> TR-CPS paths with respect to AL2S/L3 Architecture discussions
  • Date: Tue, 21 May 2013 12:52:28 -0400
  • Authentication-results: sfpop-ironport03.merit.edu; dkim=neutral (message not signed) header.i=none

Head's up, on a conference call this morning I asked Shel Waggener to ask
both NTAC and AOAC to formally propose how the various Net+ services may be
delivered to a connector. It is clear that there is no single method that
all RONs want to see the Net+ routes.

thanks, -dave

On May 21, 2013, at 12:45 PM, Darrell Newcomb wrote:

> Regarding the following agenda topic for today's 4pm Eastern Peering and
> Routing WG meeting:
> On May 21, 2013, at 9:16 AM, Dale Finkelson wrote:
>> 3. Continued discussion of Connector <-> TR-CPS paths with respect to L3
>> Architecture discussions.
>>
>
>
> Following up on last month's discussion and seeking, if agreeable, the
> endorsement of this group around the Strawman Connector AL2S <> TR-CPS
> Exchange point site connections. That outlines additional links which
> together will provide some headroom overall and provide a minimal latency
> from Connector to Exchange point equipment. Latency is especially a factor
> for the few cases around Dallas where an AL2S access point would add
> latency above that currently experienced.
>
> Attached is an update to the spreadsheet outlining links from current
> Internet2 community aggregation points into Exchange Point facilities. The
> row #13 describes the working strawman from our discussion last month.
>
> Look forward to discussing,
> -Darrell Newcomb
> 714-220-3445
>
>
>
>
> For some additional background, the drawing attached to email with the
> following headers, could be of some use:
> From: Darrell Newcomb
> <>
> Subject: Re: Agenda for 4:00 EDT call
> Date: April 16, 2013 12:32:19 PM PDT
> To:
>
>
>
> Regarding details in the spreadsheet: The usage figures are better defined,
> contexualized for this purpose, and reference URL for supporting data noted
> in column M. As discussed last month, the peak short-term utilization on
> the single Seattle link was an outlier, though it happened at a time and in
> a place where additional capacity was projected to be needed. I believe
> the facts as presented better contextualize that, but still do support the
> notion that action on capacity in this area is still prudent.
>
>
>
> <TR-CPS - Internet2 Aggregation interconnects.xlsx>




Archive powered by MHonArc 2.6.16.

Top of Page