RE: [EFM-Copper] RE: [EFM] Official Nickname for our standard?
Scott,
This is a good question and it goes beyond the copper track.
The 802 group is known as "LAN/MAN Standards Committee".
Yet 802.3ah defines a network which is neither LAN nor
MAN... The name we choose will be used not only in our
standard, but will find its way into marketing and research
literature.
Traditionally networks were classified by their geographical
span: Local Area Networks (LANs), Metropolitan Area Networks
(MANs), or Wide Area Networks (WANs). Following this
ideology, we would call our network something like
"Neighborhood Area Network" (NAN).
Alternatively we may emphasize the network purpose and call
it "Access Network" or "$ub$criber Access Network". In my
opinion "Access Network" is not descriptive enough, and as
you mentioned the abbreviation for "$ub$criber Access
Network" clashes with "Storage Area Networks".
The name "Storage Area Network" makes very little sense as
it combines purpose (storage) and area. Surprisingly, the
name caught on. By this analogy we may call our network
"Access Area Network (AAN)" or "$ub$criber Access Area
Network (SAAN)".
Are there any other suggestions?
Long live the IEEE 802 LAN/MAN/SAAN(?) Standards Committee!
Cheers,
Glen
> -----Original Message-----
> From: owner-stds-802-3-efm@majordomo.ieee.org
> [mailto:owner-stds-802-3-efm@majordomo.ieee.org] On Behalf
> Of Hugh Barrass
> Sent: Sunday, May 25, 2003 7:32 AM
> To: John.Egan@infineon.com
> Cc: stds-802-3-efm@ieee.org; stds-802-3-efm-
> copper@ieee.org
> Subject: Re: [EFM-Copper] RE: [EFM] Official Nickname for
> our standard?
>
>
> John,
>
> ... because "EFM" does not appear in either the PAR or
> anywhere in the draft. We haven't adopted EFM as an
> "official" name for anything.
>
> Scott,
>
> One possibility might be 10P"reg name" and 2B"reg name" -
> with registers applicable to both being 10P/2B"reg name" -
> that is fairly short and unique.
>
> Alternatively SA"reg name" (by dropping the N, we avoid
> confusion with the storage version).
>
> Hugh.
>
>
> John.Egan@infineon.com wrote:
>
> > Why not use EFMC?
> >
> > -----Original Message-----
> > From: Scott Simon [mailto:scottprops@speakeasy.net]
> > Sent: Friday, May 23, 2003 1:59 PM
> > To: stds-802-3-efm@ieee.org; stds-802-3-efm-
> copper@ieee.org
> > Subject: [EFM] Official Nickname for our standard?
> >
> > Hey All,
> >
> > Here's another question. Do we have an official
> nickname for our standard? For example, 10GBASE-X
> registers in Clause 45 are called "10G <register name>".
> >
> > Do we have something like "EFM <register name"?
> "10PASS-TS/2BASE-TL <register name>" seems a little
> lengthy. Maybe we just live with the long winded version,
> but is there a good alternative?
> >
> > As far as I remember, we are discouraged from using EFM
> in the draft. What about these suggestions:
> >
> > SAN -- $ub$criber access network? (a good joke against
> our storage colleagues)
> > SuNe -- $ub$criber network?
> > SAP -- $ub$criber access PHY?
> >
> > What does everyone think?
> >
> > I have a comment to put something in front of the
> 10PASS-TS/2BASE-TL registers, I'll just use the long
> winded version if no one has a better idea.
> >
> > -=Scott