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

Re: [802SEC] Comments on P802.3 PARs



James,

 

Thank you for your review and feedback on the P802.3cd and the P802.3bs
documentation.  I¹m the Study group chair for the two study groups
producing this documentation. Here is some feedback on your input and
questions.

 

P802.3cd

PAR comments:

2.1: The title appears to be wrong "Approved Draft Standard for Ethernet",
shouldn't it be "Standard for Ethernet"? If this is a myProject issue,
when simply refer it to the NesCom administrator.

 
This is indeed the title that the myBallot system populated and can't be
changed. The reason for this title was that the latest revision of the
IEEE Std 802.3 had been approved by the IEEE-SA Standards Board but had
not use been published. During that phase standards are titled 'Approved
Draft Standard ...'. While IEEE Std 802.3-2015 has now been published, on
checking myBallot today it appears this is yet to be updated there. We
will do as you suggest and refer this to the NesCom administrator.

 

5.2.b: The scope defines data rates but not the media or distance (or
equivalent measure).  Is wireless a valid media for this project?
Free-space optics?  Near-field?  Please specify the targeted media
(copper, backplane, optical, carrier pigeon, Š) and the target distance
(e.g., typically 1 m).

Accept.  We adopted modifications to the P802.3cd PAR scope. The reach
aspects were not included as multiple reaches exist and these are
addressed in the P802.3cd Objectives.  The modified scope is as follows:

Define Ethernet Media Access Control (MAC) parameters, Physical Layer
specifications, and management parameters for the transfer of Ethernet
format frames at 50 Gb/s over copper and optical media. Define additional
Physical Layer specifications and management parameters at 100 Gb/s, over
copper and optical media. Define additional Physical Layer specifications
and management parameters at  200 Gb/s over copper and multimode fiber
physical media.

The updated PAR document is available here:
http://www.ieee802.org/3/50G/public/Mar16/P802_3cd_PAR_160316.pdf
 


CSD comments:

Distinct Identity: The reasoning here indicates that 802.3bs will have
200 Gb/s, but not over ³backplanes, twin-axial copper cables and MMF"
However, as the scope does not limit the media, this project appears to
be a superset of 802.3bs. If it isn¹t, the scope should be written to
restrict the work so that it does not overlap.

As noted in Item 5.2b, modifications to the P802.3cd PAR scope were made
that restricts the work between the two projects from overlapping.  No
changes to the CSD responses were made.


The CSD can be viewed here:
http://www.ieee802.org/3/50G/public/CSD_50G_NGOATH_01_0116.pdf


 

802.3bs

PAR comments:

5.2.b: The physical media is not identified for these data rates nor is
the reach.  Please add to the scope that these data rates are defined  for
single-mode fiber and add a range target, e.g., at ranges greater  than 1
km

Accept.  We altered the modifications to the P802.3bs PAR scope to
identify the physical media. The reach aspects were not included as
multiple reaches exist and these are addressed in the 802.3bs Objectives.
The modified scope is as follows:

Define Ethernet Media Access Control (MAC) parameters, physical layer
specifications, and management parameters for the transfer of Ethernet
format frames at 200 Gb/s over single-mode fiber and 400 Gb/s over optical
physical media.

The updated PAR document is available at:
http://www.ieee802.org/3/50G/public/Mar16/P802_3bs_PAR_160316.pdf

 

CSD comments:

Distinct Identity: Change "200 Gb/s over single-mode fiber and 400Gb/s
Ethernet" to be "200 Gb/s and 400 Gb/s Ethernet over single-mode fiber"

As noted, the scope of both projects has been modified that distinguishes
the distinct identity of 200GbE in each project.  The media for 200GbE in
802.3bs will be limited to single-mode fiber, and for 400GbE, the optical
media may be either based on single-mode or multi-mode fiber.   Therefore,
your proposed language does not reflect the updated scope of the project
as related to 400GbE, which also includes multi-mode fiber and as a
consequence, no changes were made to the CSD.

The CSD can be viewed here:
http://www.ieee802.org/3/50G/public/NGAOTH_802d3bs_CSD_modification_0116.pd
f 

RegardsŠMark 






On 3/15/16, 12:36 PM, "***** IEEE 802 Executive Committee List ***** on
behalf of James P. K. Gilb" <STDS-802-SEC@ieee.org on behalf of
gilb@ieee.org> wrote:

>David
>
>Hear are my comments:
>
>P802.3cd
>
>PAR comments:
>
>2.1: The title appears to be wrong "Approved Draft Standard for
>Ethernet", shouldn't it be "Standard for Ethernet"? If this is a
>myProject issue, when simply refer it to the NesCom administrator.
>
>  5.2.b: The scope defines data rates but not the media or distance (or
>equivalent measure).  Is wireless a valid media for this project?
>Free-space optics?  Near-field?  Please specify the targeted media
>(copper, backplane, optical, carrier pigeon, ...) and the target
>distance (e.g., typically 1 m).
>
>CSD comments:
>
>Distinct Identity: The reasoning here indicates that 802.3bs will have
>200 Gb/s, but not over "backplanes, twin-axial copper cables and MMF"
>However, as the scope does not limit the media, this project appears to
>be a superset of 802.3bs. If it isn't, the scope should be written to
>restrict the work so that it does not overlap.
>
>P802.3cc
>
>PAR comments:
>
>5.2.b: "as amended by the IEEE P802.3by project." The scope is to be
>written as present tense, i.e., that IEEE P802.3by has been completed
>(otherwise it would not amend IEEE 802.3-2015).  However, once .3by is
>approved, it is automatically part of 802.3 and you don't need to call
>out all of the amendments.
>
>I suspect the problem is that 5.3 should be marked as Yes and IEEE
>P802.3by be listed.  Then delete "as amended by the IEEE P802.3by
>project."
>
>5.2.b: The need states that the goal is 100 m SMF, this should be stated
>in the Scope, i.e., change "operation by specifying" to be "operation at
>reaches greater than 100 m by specifying"
>
>CSD comments:
>
>Distinct Identity: The reasoning states that there is no other 25 Gb/s
>PHY with > 100 m reach, yet this is not a requirement in the scope.  If
>this requirement is added to the scope, then the statement here would be
>true.
>
>802.3bt
>
>PAR comments:
>
>5.2.b: Present tense is required in the scope, hence the PAR cannot say
>"may be enabled".  Change to "are enabled" or "are optionally enabled"
>or "are enabled as an option"
>
>8.1: Typo, change "5.2B" to be "5.2.b"
>
>CSD comments: No comments.
>
>802.3bs
>
>PAR comments:
>
>5.2.b: The physical media is not identified for these data rates nor is
>the reach.  Please add to the scope that these data rates are defined
>for single-mode fiber and add a range target, e.g., at ranges greater
>than 1 km
>
>CSD comments:
>
>Distinct Identity: Change "200 Gb/s over single-mode fiber and 400
>Gb/s Ethernet" to be "200 Gb/s and 400 Gb/s Ethernet over single-mode
>fiber"
>
>Thanks
>
>James Gilb
>
>----------
>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.