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

Re: [802SEC] IEEE P802.3bj draft PAR and 5 Criteria - Physical Layer specifications and Management parameters for 100 Gb/s operation over Backplanes and Copper Cables



David-

All true.
But included in the conclusion was that there would inevitably be some from which we should stay away.
I believe that bj was the example cited.

Geoff

On 305//11 2:09 PM, Law, David wrote:
Hi Tony,

As far as I'm aware there isn't a list of proscribed suffixes. I believe that Bob Grow brought up a proposal to have a list of proscribed suffixes a few years back at the SASB level - but the proposal wasn't accepted. I seem to remember - and Bob please correct me if I'm wrong - one of the reasons was that what would be 'proscribed' would be dependant on language and being 'international' the list of proscribed suffixes could end up being huge.

Best regards,
   David
________________________________________

From: tonyjeffree@googlemail.com [mailto:tonyjeffree@googlemail.com] On Behalf Of Tony Jeffree
Sent: 30 May 2011 20:55
To: Law, David
Cc: STDS-802-SEC@listserv.ieee.org
Subject: Re: [802SEC] IEEE P802.3bj draft PAR and 5 Criteria - Physical Layer specifications and Management parameters for 100 Gb/s operation over Backplanes and Copper Cables

David
I thought "bj" was on the list of proscribed suffixes...
Regards,
Tony
On 30 May 2011 20:22, "Law, David"<dlaw@hp.com>  wrote:
Dear EC members,

In support of subclause 12.2 'LMSC Approval' of the LMSC Operations Manual (30 day rule) please find below the required information in respect to the IEEE P802.3bj Physical Layer specifications and Management parameters for 100 Gb/s operation over Backplanes and Copper Cables PAR for consideration at the July 2011 plenary.

Best regards,
David


IEEE P802.3bj Standard for Information technology--Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications Amendment: Physical Layer specifications and Management parameters for 100 Gb/s operation over Backplanes and Copper Cables

[1] Draft PAR and 5C:

Draft PAR<http://www.ieee802.org/3/100GCU/par_0511.pdf>.
Draft 5C<http://www.ieee802.org/3/100GCU/5C_0511.pdf>.

[2] Explanatory technical background material:

This project is to amend IEEE Std 802.3 to specify additions to, and appropriate modifications of, IEEE Std 802.3 to add 100 Gb/s 4 lane Physical Layer (PHY) specifications and management parameters for operation on backplanes and twinaxial copper cables. Rapid growth of server, network, and internet traffic is driving the need for higher data rates over backplanes and high density, low cost twinaxial copper cables.

[3] Work plan for the development of managed object definitions:

The project will include a protocol independent specification of managed objects with SNMP management capability to be provided in the future by an amendment to the yet-to-be-approved IEEE P802.3.1 Ethernet MIBs.

[4] Status of the development of the PAR:

The PAR and 5C drafts are pending IEEE 802.3 Working Group approval at the July Plenary. Should the IEEE 802.3 Working Group not approve the submission, it will be removed from the IEEE 802 Executive Committee agenda.

----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.


----------
This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.