RE: [EFM-OAM] RE: [EFM] Re: Loopback and BERT
Bob,
I was thinking again about what you said, but in a different context. All
of the transmission systems chip sets are getting very inexpensive, not
just the BERT chips. The high bandwidth multiplexing chips are getting
very inexpensive as well. This would allow not only your BERT test but
multiple MAC/PCS ports to be multiplexed together as a real time streaming
bit signal. The upper layer encoding, including the 100Mb encoding could
be multiplexed without any changes to any of the clauses, except for the
management elements clause, and adding a new one for the OAM. Not only is
this inexpensive, it might be very easy to do from a documentation
standpoint.
Thank you,
Roy Bynum
At 11:52 PM 2/25/2002 +0000, Bob Barrett wrote:
>Roy
>
>The honest answer is I don't know enough about GE conformance tests to say
>one way or the other. I'll have one of my people look at this and make a
>comment later. It looks like a reasonable plan to me, and, as you suggested
>it, I would assume that it will meet the service provider requirements.
>
>Thanks
>
>Bob
>
>-----Original Message-----
>From: owner-stds-802-3-efm@majordomo.ieee.org
>[mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of Roy Bynum
>Sent: 25 February 2002 01:50
>To: bob.barrett@fiberintheloop.com; stds-802-3-efm@ieee.org;
>stds-802-3-efm-oam@ieee.org
>Cc: owner-stds-802-3-efm-p2mp@majordomo.ieee.org;
>owner-stds-802-3-efm-p2p@majordomo.ieee.org
>Subject: Re: [EFM-OAM] RE: [EFM] Re: Loopback and BERT
>
>
>
>Bob,
>
>Wouldn't be easier to just use the conformance test pattern that is already
>in the GbE PCS? The test pattern can be continuously repeated for the
>duration of the test. Invalid code sets can be introduced to verify that
>the remote PCS will detect the errors. Additional OAM physical layer bit
>error detection information can be used to detect the errors that might
>turn one valid code set into another valid code set. This can be done by
>inserting a bit flip in one of the valid code sets of the conformance
>pattern such that it becomes a different valid code set, but not correct
>the bit error detection information that would be in the OAM. This does
>not require any new chips to be introduced to the PHY. It leverages the
>existing PCS as much as possible.
>
>Thank you,
>Roy Bynum
>
>At 01:35 AM 2/25/2002 +0000, Bob Barrett wrote:
>
> >Roy
> >
> >Correct. The introduction of errors comes from the BERT engine at the POP
> >end, and potentially from the BERT engine in the CPE, if the implementer
> >chooses to support that in the CPE. The inexpensive BERT chips support all
> >of that 'stuff', and one of the BERT chip vendors does a pretty good job on
> >10/100 PHY/MAC chips too, so I would hope that they would support this
> >direction.
> >
> >Thanks
> >
> >Bob
> >
> >-----Original Message-----
> >From: owner-stds-802-3-efm@majordomo.ieee.org
> >[mailto:owner-stds-802-3-efm@majordomo.ieee.org]On Behalf Of Roy Bynum
> >Sent: 24 February 2002 22:07
> >To: bob.barrett@fiberintheloop.com; stds-802-3-efm@ieee.org;
> >stds-802-3-efm-oam@ieee.org
> >Cc: owner-stds-802-3-efm-p2mp@majordomo.ieee.org;
> >owner-stds-802-3-efm-p2p@majordomo.ieee.org
> >Subject: RE: [EFM] Re: Loopback and BERT
> >
> >
> >
> >Bob,
> >
> >One function that was always part of BERT testing when I was working in
> >field operations was the deliberate introduction of errors in the encoded
> >data stream to be sure that the customer premise equipment was properly
> >able to detect errors. This is part of the originating conformance
> >testing, and part of the conformance testing that was done after a
> >repair. I do not think that your "loop back plug" would qualify for that
> >level of conformance BERT testing.
> >
> >Thank you,
> >Roy Bynum
> >
> >At 08:55 PM 2/24/2002 +0000, Bob Barrett wrote:
> >
> > >Dear all
> > >
> > >Rather than put up a presentation on this at the March meeting I have
> > >written a white paper expressing what I think are the key issues (and the
> > >key reasons and benefits) of including loopback and BERT functions in the
> > >EFM subscriber access standard. It can be found at:
> > >
> > >http://www.rjbarrett.net/rb020225.pdf
> > >
> > >or from a link at www.rjbarrett.net
> > >
> > >I have written this as an individual, and not included references to my
> > >company or products, and I have put it on my personal web site.
>Inevitably
> >I
> > >do mirror my views into the technolgy that my company produces, as do
>most
> > >of we equipment vendors.
> > >
> > >By putting this paper up for discussion now I hope to reach the broad
> > >audience of all EFM streams and stimulate debate in advance of the March
> > >meeting, to help us to reach consensus.
> > >
> > >Thanks
> > >
> > >Bob Barrett