Re: [j-nsp] T640

From: Michael Damkot (damkot@pop.net)
Date: Tue Apr 23 2002 - 14:52:34 EDT


Just out of curiosity, is there a big need for 768 speed? I was just
wondering, I don't know of anyone scrambling right now to add more OC-192
lines to their network, so is there a large need for OC-768?

----------------------------------
Michael Damkot
mike@damkot.net
mike-pager@damkot.net
703-628-1205
888-561-8872
----------------------------------

> From: "Martin, Christian" <cmartin@gnilink.net>
> Date: Tue, 23 Apr 2002 14:47:04 -0400
> To: "'Aviva Garrett'" <aviva@juniper.net>, Neil Stirling
> <neil.stirling@nortelnetworks.com>
> Cc: "'juniper-nsp@puck.nether.net'" <juniper-nsp@puck.nether.net>
> Subject: RE: [j-nsp] T640
> Resent-From: juniper-nsp@puck.nether.net
> Resent-Date: Tue, 23 Apr 2002 14:50:01 -0400
>
> When the technology exists! Long-haul OC-768 is likely 2 years away. PMD
> is a major issue that needs an economic resolution. OC-768 VSR can be done
> sooner. Then again, with link-bundling, you can have 768 on your M160 right
> now!
>
> chris
>
>
>> Neil,
>>
>> The support is possible, but I can't comment on any timeframes.
>>
>> Thanks,
>> ..Aviva
>>
>
>>> Aviva,
>>>
>>> I suppose with 40gbps per slot this will open up the STM-256/OC-768
>>> range - but any ideas when ?
>>>
>>> Neil.
>>>
>>> -----Original Message-----
>>> From: Aviva Garrett [mailto:aviva@juniper.net]
>>> Sent: 23 April 2002 17:58
>>> To: Martin, Christian
>>> Cc: 'juniper-nsp@puck.nether.net'; aviva@juniper.net
>>> Subject: Re: [j-nsp] T640
>>>
>>>
>>> In message
>>> <94B9091E1149D411A45C00508BACEB35015F2DE6@entmail.gnilink.com>you
>>> wri
>>> te:
>>>> Well, it's here.
>>>
>>> Not just another guitar @:-)
>>>
>>>>
>>>> Gibson is has been announced...
>>>>
>>>> http://www.juniper.net/news/features/core/
>>>>
>>>
>>> Somewhere on the midplane, you'll see something that looks like the
>>> acoustic guitar at
>>>
>>> http://www.gibson.com/
>>>
>>> ..Aviva
>>>
>>>
>>> ------_=_NextPart_001_01C1EAF1.AEF40E54
>>> Content-Type: text/html
>>> Content-Transfer-Encoding: quoted-printable
>>>
>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
>>> <HTML>
>>> <HEAD>
>>> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>>> charset=3Dus-ascii"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange
>>> Server version = 5.5.2655.35">
>>> <TITLE>RE: [j-nsp] T640 </TITLE>
>>> </HEAD>
>>> <BODY>
>>>
>>> <P><FONT SIZE=3D2>Aviva,</FONT>
>>> </P>
>>>
>>> <P><FONT SIZE=3D2>I suppose with 40gbps per slot this will
>> open up the
>>> = STM-256/OC-768 range - but any ideas when ?</FONT> </P>
>>>
>>> <P><FONT SIZE=3D2>Neil.</FONT>
>>> </P>
>>>
>>> <P><FONT SIZE=3D2>-----Original Message-----</FONT>
>>> <BR><FONT SIZE=3D2>From: Aviva Garrett [<A =
>>>
>> HREF=3D"mailto:aviva@juniper.net">mailto:aviva@juniper.net</A>]</FONT>
>>> <BR><FONT SIZE=3D2>Sent: 23 April 2002 17:58</FONT>
>>> <BR><FONT SIZE=3D2>To: Martin, Christian</FONT>
>>> <BR><FONT SIZE=3D2>Cc: 'juniper-nsp@puck.nether.net'; =
>>> aviva@juniper.net</FONT> <BR><FONT SIZE=3D2>Subject: Re:
>> [j-nsp] T640
>>> </FONT> </P>
>>> <BR>
>>>
>>> <P><FONT SIZE=3D2>In message =
>>>
>> &lt;94B9091E1149D411A45C00508BACEB35015F2DE6@entmail.gnilink.com&gt;yo
>>> u = wri</FONT> <BR><FONT SIZE=3D2>te:</FONT>
>>> <BR><FONT SIZE=3D2>&gt; Well, it's here.</FONT>
>>> </P>
>>>
>>> <P><FONT SIZE=3D2>Not just another guitar @:-)</FONT>
>>> </P>
>>>
>>> <P><FONT SIZE=3D2>&gt; </FONT>
>>> <BR><FONT SIZE=3D2>&gt; Gibson is has been announced...</FONT>
>>> <BR><FONT SIZE=3D2>&gt; </FONT> <BR><FONT SIZE=3D2>&gt; <A =
>>> HREF=3D"http://www.juniper.net/news/features/core/" =
>>>
>> TARGET=3D"_blank">http://www.juniper.net/news/features/core/></FONT>
>>> <BR><FONT SIZE=3D2>&gt; </FONT>
>>> </P>
>>>
>>> <P><FONT SIZE=3D2>Somewhere on the midplane, you'll see
>> something that
>>> = looks like the</FONT> <BR><FONT SIZE=3D2>acoustic guitar at </FONT>
>>> </P>
>>>
>>> <P><FONT SIZE=3D2>&nbsp; <A HREF=3D"
http://www.gibson.com/" =
>>> TARGET=3D"_blank">http://www.gibson.com/></FONT>
>>> </P>
>>>
>>> <P><FONT SIZE=3D2>..Aviva</FONT>
>>> </P>
>>>
>>> </BODY>
>>> </HTML>
>>> ------_=_NextPart_001_01C1EAF1.AEF40E54--
>>>
>>
>
>



This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:35 EDT