Hmmmmmm not sure my Understanding of the lambda switching is what I’ve
called spatial switching that is lambda1 portA à
lambda1 portB what is not clear to me is how can be advertised an OEO
transponder that can only perform frequency switching lambda1 à lambda 2.
Adrian? Deb? Anyone else?
From: MEURIC Julien RD-CORE-LAN [mailto:email@example.com]
Sent: mercoledì 4 luglio 2007 18.47
To: Diego Caviglia (GA/ERI); firstname.lastname@example.org
Subject: RE: Switching Capability of Photonic Links with Transponder
believe we should refer to the Holly RFC 3945, chapter 1, verse 2:
"Lambda Switch Capable" interfaces "can operate at the level of an
*individual wavelength*" [or a "group of wavelengths"], meaning that
you manipulate values of wavelengths (as AU-4 numbers [or AU-4 ranges]
from an SDH portA to SDH portB), like in a ROADM;
"Fiber-Switch Capable" interfaces "can operate at the level of a single
or multiple *fibers*", meaning *spatial switching* where you don't
consider the type of signal that ports convey (could be anything like a
black and white signal, a wavelength, a WDM multiplex, some optical
packets...), like in a OOO PXC.
stick with strict terminolgy: lambda = wavelength = (speedOfLight /
if you need to do "frequency switching", then it is the so called
"lambda switching". :-)
this is my understanding, so if I'm wrong or if it's a vocabulary issue
because you find that terms are inappropriate, then we'd better ask
father Adrian and sister Deborah.
Diego Caviglia (GA/ERI) [mailto:email@example.com]
Actually not the PXC I had in mind is able to switch a single lambda I
didn't but the mux/demux In the picture sorry.
point I failed to illustrate is the ambiguity of the term "Lambda
Switch Capable" given that there two possible ways to switch a lambda.
first one is the spatial one: (Lambda1 portA) --> (Lambda1 portB)
this is the way an all optical switch works and this why there is the
lambda continuity constraint in photonic networks.
second one is the frequency switching: (Lambda1 portA) --> (Lambda2
portA) this switching can be done via a transponder (OEO) device.
course is possible to mix the two switching having (Lambda1 portA)
--> (Lambda2 portB)
impression is that the definition "Lambda Switch Capable" refers to the
spatial switching and thus I don't know how to model the fact that
after/before a photonic matrix I have a transponder.
hope I've made my question clearer.
MEURIC Julien RD-CORE-LAN [mailto:firstname.lastname@example.org]
martedì 3 luglio 2007 19.21
Diego Caviglia (GA/ERI); email@example.com
RE: Switching Capability of Photonic Links with Transponder
I understand correctly, your "lambda switch" by itself is a PXC that
only "Fiber-Switch Capable" interfaces. Then, you add
cards to it. So, correct me if I'm wrong (you or
else), but whether you do a lambda conversion inside a card or in
core matrix, this new interface on your global device is able to work
lambdas anyway [(lambda 1, port A) --> (lambda2, port B)]. As a
you need to advertise your most flexible capability, which is
you used "FSC", you wouldn't be able to control your "lambda
card, as LSPs are like lists of fibers and labels aren't
maybe I didn't get your actual issue.
Of Diego Caviglia (GA/ERI)
I've a doubt about how to model the following situation.
| | OEO |
| Lambda |-------+
| Switch |
node itself is able to cross connect only the Lambda while the
has a OEO transponder that is able to change the lambda
In this case there are two different 'switching capability'
spatial one that is performed by the switch (lambda 1, port A) -->
port B) and the frequency switching is done by the OEO
Witch kind of interface switching capability I have to
Line ON BBN
Global Product Center - Italy
Roma , Italy
+39 010 600 3736
+39 010 600 3493
+39 335 7181762
communication is confidential and intended solely for the
Any unauthorized review, use, disclosure or distribution
prohibited. If you believe this message has been sent to you in
please notify the sender by replying to this transmission and
the message without disclosing it. Thank you.
including attachments is susceptible to data corruption,
unauthorized amendment, tampering and viruses, and we only
and receive emails on the basis that we are not liable for any such
interception, amendment, tampering or viruses or any