Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [EFM] OAM loop back / echo server function



Roy-

At 06:32 PM 9/4/01 -0500, Roy Bynum wrote:
Geoff,

There will need to be some physical layer command functionality in order to  provide management functions that are not data traffic invasive.  That is one of the requirements of the OAM.  If it is not done within the EFM physical layer, then the service will only be "best effort" and not the high margin services that will be required to pay for the infrastructure deployment of EFM.

Thank you,
Roy Bynum
WorldCom

That is your opinion.
Such a "additional signal channel" has not yet been agreed to and adopted by consensus at this point and remains a controversial issue. It is also contrary to the traditional architecture of Ethernet.

I decline to take its existence as a given at this point, in fact I would oppose such a proposal.

Geoff


At 03:38 PM 9/4/01 -0700, Geoff Thompson wrote:
Roy-

I'm not sure that I understand what you mean.

You seem to be making some assumptions about what constitutes "OAM overhead" that I do not.

What I meant was that tying the transmit data stream directly to the receive data stream at the physical level is a bad idea when you are part of a live network. Since we don't have the concept of turning circuits up and down that means it  is a bad idea all of the time.

That has nothing to do with any "Loopback Protocol" which might reflect a payload back at a transmitting entity inside valid Ethernet packets.

Geoff

At 03:12 PM 9/4/01 -0500, Roy Bynum wrote:
Geoff,

What about a "loop back" within the OAM overhead?  That would be able to function regardless of the Ethernet traffic and network.  It may not be what some people are wanting, but it is better than nothing.

Thank you,
Roy Bynum