D1.0 Proposed Comment Responses by ID
152 pages
English

D1.0 Proposed Comment Responses by ID

-

Le téléchargement nécessite un accès à la bibliothèque YouScribe
Tout savoir sur nos offres
152 pages
English
Le téléchargement nécessite un accès à la bibliothèque YouScribe
Tout savoir sur nos offres

Description

Draft 1.0 Comments IEEE P802.3ba D1.0 40Gb/s and 100Gb/s Ethernet comments Task force ReviewCl 82 SC 82.2.8 P 125 L 25 # Cl 82 SC 82.2.18.2 P 134 L 41 #1 4Seung-Hwan, Kim ETRI Seung-Hwan, Kim ETRIComment Type E Comment Status D Comment Type T Comment Status DSpelling: Should be change 'de-skew' to 'deskew' for consistency. Should be change 'per 31.25' to 'per 31.25 us'.SuggestedRemedy SuggestedRemedyProposed Response Proposed ResponseResponse Status W Response Status WPROPOSED ACCEPT. PROPOSED ACCEPT.Cl 82 SC 82.2.4.4 P 122 L 725 # 2 Cl 82 SC 82.2.17.3 P 137 L 30 # 5Seung-Hwan, Kim ETRI Seung-Hwan, Kim ETRIComment Type T Comment Status D Comment Type T Comment Status D amsmAt Data Block Formats and Control Block Formats : Should be change 'am_cnt = 2 *' to 'am_cnt = 4 *'.The slash('/') is used to seperate and represent two 4 bytes transfer in 10GBase-R,SuggestedRemedybut in 40G/100GBase-R there is no need slash('/') between 8 bytes.SuggestedRemedyProposed ResponseResponse Status WPROPOSED REJECT.Proposed ResponseResponse Status W PROPOSED ACCEPT. If I understand the comment correctly, the am_cnt = 2 * is from the VALID_AM to 2_GOOD state transition. This should be 2, only two good markers in a row gets in you lock.Also covered by #202Cl 82 SC 82.2.17.3 P 137 L 33 # 6Cl 82 SC 82.2.17.2.2 P 131 L 18 # 3Seung-Hwan, Kim ETRISeung-Hwan, Kim ETRIComment Type T Comment Status D amsmComment Type T Comment Status DShould be change '2_GOOD' to ...

Informations

Publié par
Nombre de lectures 44
Langue English

Extrait

Draft 1.0 Comments IEEE P802.3ba D1.0 40Gb/s and 100Gb/s Ethernet comments Task force Review
Cl 82 SC 82.2.8 P 125 L 25 # Cl 82 SC 82.2.18.2 P 134 L 41 #
1 4
Seung-Hwan, Kim ETRI Seung-Hwan, Kim ETRI
Comment Type E Comment Status D Comment Type T Comment Status D
Spelling: Should be change 'de-skew' to 'deskew' for consistency. Should be change 'per 31.25' to 'per 31.25 us'.
SuggestedRemedy SuggestedRemedy
Proposed Response Proposed Response
Response Status W Response Status W
PROPOSED ACCEPT. PROPOSED ACCEPT.
Cl 82 SC 82.2.4.4 P 122 L 725 # 2 Cl 82 SC 82.2.17.3 P 137 L 30 # 5
Seung-Hwan, Kim ETRI Seung-Hwan, Kim ETRI
Comment Type T Comment Status D Comment Type T Comment Status D amsm
At Data Block Formats and Control Block Formats : Should be change 'am_cnt = 2 *' to 'am_cnt = 4 *'.
The slash('/') is used to seperate and represent two 4 bytes transfer in 10GBase-R,
SuggestedRemedy
but in 40G/100GBase-R there is no need slash('/') between 8 bytes.
SuggestedRemedy
Proposed Response
Response Status W
PROPOSED REJECT.
Proposed Response
Response Status W

PROPOSED ACCEPT.
If I understand the comment correctly, the am_cnt = 2 * is from the VALID_AM to 2_GOOD
state transition. This should be 2, only two good markers in a row gets in you lock.
Also covered by #202
Cl 82 SC 82.2.17.3 P 137 L 33 # 6
Cl 82 SC 82.2.17.2.2 P 131 L 18 # 3
Seung-Hwan, Kim ETRI
Seung-Hwan, Kim ETRI
Comment Type T Comment Status D amsm
Comment Type T Comment Status D
Should be change '2_GOOD' to '4_GOOD'.
Should be change 'rx_raw<63>' to 'rx_raw<71>'.
SuggestedRemedy
SuggestedRemedy
Proposed Response
Response Status W
Proposed Response
Response Status W
PROPOSED REJECT.
PROPOSED ACCEPT.
This should remain 2_GOOD. The baseline has two good markers to get in lock.
change 'rx_raw<63>' to 'rx_raw<71>'.
Dupe of #527
TYPE: TR/technical required ER/editorial required GR/general required T/technical E/editorial G/general
Page 1 of 152
COMMENT STATUS: D/dispatched A/accepted R/rejected RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawn
Comment ID # 6 11/7/2008 11:21:10 AM
SORT ORDER: Comment ID Draft 1.0 Comments IEEE P802.3ba D1.0 40Gb/s and 100Gb/s Ethernet comments Task force Review
Cl 82 SC 82.2.4.4 P 122 L # Cl 01 SC 1.4 P 23 L 20 #
7 9
Wong, Don Cisco Systems Anslow, Peter Nortel Networks
Comment Type ER Comment Status D Comment Type T Comment Status D
Figure 82-5 The definition of 40GBASE-SR4 is "IEEE 802.3 Physical Layer specification for 40 Gb/s
using 40GBASE-R encoding over four lanes of, short reach, multi mode fiber." This
For BlockTypeField 0xb4, 0xcc, 0xd2 & 0xe1, missing one more "single bit" field (marked implies that the fibre alone determines the reach.
by thin rectangle).
SuggestedRemedy
SuggestedRemedy
Re-word as: "40GBASE-SR4: IEEE 802.3 Physical Layer specification for 40 Gb/s using
Add "thin rectangle" for BlockTypeField 0xb4, 0xcc, 0xd2 & 0xe1. 40GBASE-R encoding over four lanes of multi mode fiber with short reach. (See IEEE
802.3, Clause 86.)"
Proposed Response
Response Status W
PROPOSED ACCEPT. Similarly re-word 100GBASE-SR10 definition to:
[Added missing subclause number 82.2.4.4 to subclause field]
"100GBASE-SR10: IEEE 802.3 Physical Layer specification for 100 Gb/s using
100GR encoding over ten lanes of multi mode fiber with short reach. (See IEEE
Will add the appropriate rectangles. 802.3, Clause 86.)"
Proposed Response Response Status
W
Cl 82 SC 82.2.17.3 P 137 L 23 #
8
PROPOSED ACCEPT.
Shafai, Farhad Sarance Technologies
Comment Type TR Comment Status D
Cl 01 SC 1.4 P 23 L 35 # 10
The state diagram in figure 152-12 shows that after am_lock is achieved, if there are 4
Anslow, Peter Nortel Networks
!am_valid conditions in a fixed window of 4 alignment marker periods, then am_lock is set
Comment Type T Comment Status D
to false. Because the window is fixed in time, it is possible that up to 6 !am_valid
conditions may occur and the state machine will remain in lock (i.e. 3 !am_valid conditions
The definition of 100GBASE-ER4 "IEEE 802.3 Physical Layer specification for 100 Gb/s
in one window followed immediately by 3 more !am_valid conditions in the next window).
using 100GBASE-R encoding over four WDM lanes, extended long reach, single mode
fiber." This implies that the fibre alone determines the reach.
SuggestedRemedy
SuggestedRemedy
Suggested remedy is to make the window "sliding". That is, if there are four consecutive
!am_valid conditions over any four align maker periods, then the am_lock is set to false.
Re-word as: "100GBASE-ER4: IEEE 802.3 Physical Layer specification for 100 Gb/s using
100GBASE-R encoding over four WDM lanes on single mode fiber with extended reach.
Proposed Response Response Status W
(See IEEE 802.3, Clause 88.)"
PROPOSED ACCEPT.
Similarly re-word 100GBASE-LR4 definition to:
Make the appropriate changes to the state machine to have a sliding window.
"100GBASE-LR4: IEEE 802.3 Physical Layer specification for 100 Gb/s using 100GBASE-
R encoding over four WDM lanes on single mode fiber with long reach. (See IEEE 802.3,
Apparantly the commenter has commented using Draft 0.9 with old clause numbers. The
Clause 88.)"
clause number and subclause fields have been corrected to 82 to import into the comment
Proposed Response
Response Status W
database.
PROPOSED ACCEPT.
TYPE: TR/technical required ER/editorial required GR/general required T/technical E/editorial G/general
Page 2 of 152
COMMENT STATUS: D/dispatched A/accepted R/rejected RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawn
Comment ID # 10 11/7/2008 11:21:10 AM
SORT ORDER: Comment ID Draft 1.0 Comments IEEE P802.3ba D1.0 40Gb/s and 100Gb/s Ethernet comments Task force Review
Cl 01 SC 1.4 P 23 L 1 # Cl 01 SC 1.4 P 23 L 50 #
11 13
Anslow, Peter Nortel Networks Anslow, Peter Nortel Networks
Comment Type T Comment Status D Comment Type E Comment Status D
The definition of 40GBASE-LR4 is missing The modified definition for "1.4.311 RMS spectral width" is shown in italic font. The font
should match the base document
SuggestedRemedy
SuggestedRemedy
Add the definition as:
Change the font of the modified definition for RMS spectral width to match the base
"40GBASE-LR4: IEEE 802.3 Physical Layer specification for 40 Gb/s using 40GBASE-R
document
encoding over four WDM lanes on single mode fiber with long reach. (See IEEE 802.3,
Clause 87.)"
Proposed Response Response Status
W
Proposed Response
Response Status W
PROPOSED ACCEPT.
PROPOSED ACCEPT.
Change font style to normal from italic
Cl 01 SC 1.4 P 23 L 44 #
12
Cl SC P L #
01 1.5 24 5 14
Anslow, Peter Nortel Networks
Anslow, Peter Nortel Networks
Comment Type E Comment Status D
Comment Type Comment Status
E D
The definition of virtual lanes is awkwardly worded:
The abbreviation for CAUI is expanded as "100Gb/s Attachment Unit Interface" but the
"Virtual Lane: In 40GBASE-R and 100GBASE-R, the PCS distributes encoded data to
other abbreviations use "Gigabit" rather than "Gb/s"
multiple logical lanes, these logical lanes are called virtual lanes. They are called virtual
lanes since one or more of PCS lanes can be multiplexed and carried on a physical lane
SuggestedRemedy
together at the PMA interface."
Change to "100 Gigabit Attachment Unit Interface"
SuggestedRemedy
Proposed Response
Response Status W
Re-word as:
PROPOSED ACCEPT.
"Virtual Lane: In 40GBASE-R and 100GBASE-R, the PCS distributes encoded data to
multiple logical lanes, these logical lanes are called virtual lanes since one or more of the
Cl 01 SC 1.5 P 24 L 11 # 15
PCS lanes can be multiplexed and carried on a physical lane together at the PMA
interface."
Anslow, Peter Nortel Networks
Proposed Response
Response Status W
Comment Type T Comment Status D
PROPOSED ACCEPT.
The abbreviation OPU3 is expanded as "Optical Payload Unit 3" but OPU is defined in ITU-
T G.709 as "Optical channel Payload Unit"
SuggestedRemedy
Change to "Optical channel Payload Unit 3"
Proposed Response
Response Status W
PROPOSED ACCEPT.
TYPE: TR/technical required ER/editorial required GR/general required T/technical E/editorial G/general
Page 3 of 152
COMMENT STATUS: D/dispatched A/accepted R/rejected RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawn
Comment ID # 15 11/7/2008 11:21:10 AM
SORT ORDER: Comment ID Draft 1.0 Comments IEEE P802.3ba D1.0 40Gb/s and 100Gb/s Ethernet comments Task force Review
Cl 04 SC 4.4.2 P 25 L 46 # Cl 45 SC 45.2.1.4 P 33 L 47 #
16 18
Anslow, Peter Nortel Networks Anslow, Peter Nortel Networks
Comment Type

  • Univers Univers
  • Ebooks Ebooks
  • Livres audio Livres audio
  • Presse Presse
  • Podcasts Podcasts
  • BD BD
  • Documents Documents