Re: [EFM] OAM loop back / echo server function
Your discussions only emphasize that P802.3ah/EFM is only a part of what is
needed as a full service offering for a service provider's Ethernet To The
Subscriber product offering.
A limited amount of this discussion is appropriate for this forum. However,
the scope of this project is limited. It would probably be worthwhile to
set up a different forum on how to build a complete Ethernet To The
Subscriber. That would be a more appropriate forum for doing the larger
architecture and determining what standards work in other committees is
needed to complete the solution.
At 08:29 AM 8/31/01 -0600, Charles Cook wrote:
>As a carrier, I concur with your thoughts including your comment that
>an access solution for residential users is a "bad idea".
>Carlos Ribeiro wrote:
> > At 17:29 30/08/01 +0100, Bob Barrett wrote:
> > >Remote loop back of Ethernet packets / 802.3 frames is a really bad idea.
> > >No mater how well intentioned it will go wrong sometimes and when it does
> > >it is really bad news.
> > I also was late on this discussion, but I have the same opinion. In
> > general, thinking as a service provider perspective, each and every user
> > should have a logically protected circuit to the
> > headend/olt/switch/whatever. Any chance of having packets exchanged
> > directly between the users opens a wide door for exploits (or even
> > unintentional) problems. In this sense, I believe that EFM should allow
> > - direct broadcast on the downstream, limited by VLAN, where the service
> > provider can control what packets get broadcasted;
> > - direct point-to-point communication upstream between the ONU and the OLT.
> > For some specific applications, bridging may be a simple solution for the
> > direct communication between the endpoints. As an access solution for
> > residential users, it is a bad idea.
> > Carlos Ribeiro
> > CTBC Telecom