RE: [EFM] OAM - Faye's seven points
Network management traffic can also benefit from exponential back-off, a
little bit like the Realt Time Streaming Control Protcocol (RTCP of
RTSP), does gather stats, but is intelligent about not saturating the
link.
I stress that in-band management is the only sure way of ensuring that
the information gets propagated in a non-discriminatory manner to
multiple service providers. It is possible that you will need to
multicast this information to different service providers. Think of the
situation where two ISPs want to diagnose a common CPE with two Ethernet
ports, providing IP Telephone service on one port and IP Video on
another port.
LLC traffic will amount to little more than noise on a customer
dedicated GigE P2P link.
-=Francois=-
-----Original Message-----
From: owner-stds-802-3-efm@majordomo.ieee.org
[mailto:owner-stds-802-3-efm@majordomo.ieee.org] On Behalf Of Matt
Squire
Sent: September 20, 2001 8:17 PM
To: stds-802-3-efm
Subject: Re: [EFM] OAM - Faye's seven points
Both OAM and data traffic travel over the same medium. No matter how we
slice it, OAM traffic does reduce the bandwidth available to the user.
One way to cap that effect is to use a dedicated side-band with a
limited bandwidth. An alternate way to cap the effect is to
police/shape the OAM traffic at a layer above. A third alternative is
to use something like a slow protocol which is limited to 5 frames/sec.
Roy Bynum wrote:
>
> Harry,
>
> I think that Faye is correct. If the OAM is "frame" based, then it
> will share the same bandwidth with the customer traffic. Only if the
> OAM is "side band" will it not share the same bandwidth as the
> customer traffic.
>
> Thank you,
> Roy Bynum
>
> At 02:31 PM 9/20/01 -0700, Harry Hvostov wrote:
>
> >Faye,
> >
> >What I meant was that the OAM control frames would not be forwarded
> >outside the ePON network.
> >
> >Harry