Date: Tue, 2 Jun 1998 09:31:11 -0700
To: Ken Freeman <freeman@ciocc.arc.nasa.gov>,
From: "David A. Guevara" <dguevara@mail.arc.nasa.gov>
Subject: Re: Access jsimpson from 169.154.161.0 network...
Bill --
Any feedback on what Ken has requested. I would like to get the peering
set up between NREN and your HPCC-ESS router ASAP. Ken's approach seems
to be the simplest to implement.
-- david
At 12:02 PM -0700 5/29/98, Ken Freeman wrote:
>Bill:
>
>We are thinking of re-using the configuration for the Rendering
>experiment:
>
> We would like to use VPI/VCI=0,101 to go from the NREN
> Switch to the HPCC_ESS switch.
>
> Also, can we get an address in your address space
> (198.119.1.x) for configuration on our router.
>
> We want to configure a point-to-multipoint sub-interface
> on the NREN router and extablish a BGP session with
> your router.
>
> ken/steve
>
>On Fri, 29 May 1998, Bill Fink wrote:
>
>> > Bill,
>> > This is my mistake, The chicago switch is owned and managed by
>> > Sprint and it does not point to our arp server. Therefore there is no
>> > SVC support currently form SPRINT. They are planning to provide this
>> > service sometime soon.
>>
>> Steve,
>>
>> Just to be clear, use of an ATMARP server and support of SVCs are
>> two different things. If they support SVCs, we can just hardcode
>> the IP to ATM NSAP address mapping on our routers, like I did on
>> my end. If they don't support SVCs, I guess the next best option
>> is a UNI smart PVC to the switch closest to the Chicago NGIX NREN
>> router that does support SVCs, concatenated with a PVC to complete
>> the rest of the path (and change to using an SVC once they support
>> that service). Which case is it, so we can proceed accordingly?
>>
>> -Thanks
>>
>> -Bill
>>