Re: [HSSG] fault signalling
I am in favor of having at least some flavor of line status signaling, at
least remote fault. It has proved very useful in other 802.3 optical standards.
But please tell me how the following terms (currently undefined in 802.3)
are in scope for this project:
ADM (unless you mean some device that goes between two (or more)
At 07:15 AM 10/2/2007 , Gary Nicholl (gnicholl) wrote:
>I would certainly support something like this. This would be very useful
>when connecting the client interface on a DWDM transponder to a 100GE
>interface on a router/switch/ADM. It might be as simple as defining
>another 'ordered code set' for fault signaling, so we would now have a
>total of three codes:
>The lack of such a feature at 10GE is one of the (very few) reasons that
>OC192 interfaces continue to be used for this kind of interconnect.
> > -----Original Message-----
> > From: Mikael Abrahamsson [mailto:swmike@SWM.PP.SE]
> > Sent: Monday, September 17, 2007 4:44 PM
> > To: STDS-802-3-HSSG@LISTSERV.IEEE.ORG
> > Subject: [HSSG] fault signalling
> > Hello.
> > I am very interested in having new HSSG standard implement
> > some kind of signalling equivalent to AIS, RDI etc which is
> > present in SONET/SDH and which is very useful for
> > fault-finding i WAN/DWDM applications where regenerators or
> > transponders are used to indicate where the fault might be.
> > Is it too early in the process to start discussing this?
> > Since symbol and bit encoding is being discussed. I am under
> > the impression that one could use non-data symbols out of
> > 64b/66b to handle some of the signalling, thus I wanted to
> > ask this early on in case this is the proper time, or if it
> > should be done later.
> > I have quite a few ideas about what could be included, even
> > if it's said to be optional to include (I don't know how this
> > is usually done).
> > I am willing to try to put together a more structured list of
> > suggestions if it's deemed appropriate at this time.
> > --
> > Mikael Abrahamsson email: firstname.lastname@example.org