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

RE: Inter-frame transmission length


The table really wasn't that descriptive and, since it didn't have any
conformance requirement, it didn't control implementation (that is, no
"shall" statement referenced the table). The conformance requirement in D1.1
was "Though this alignment function may
change the inter-frame length between two specific frames, it shall preserve
the average interframe length, assure transmitted inter-frame at the XGMII
is a minimum of nine octets and that the total transmitted inter-frame at
the XGMII is plus or minus three octets from the total MAC transmitted
inter-frame." People felt that the meaning of this was not clear enough.

The text controlling the modification of IPG by the RS is now in
(page 251 of D3.0). This text ensures that the RS will maintain the average
IPG it gets from the MAC and won't shorten the IPG below 9 (assuming the MAC
is complying with a 12 byte minimum IPG).


-----Original Message-----
From: Lior Reem [mailto:LReem@xxxxxxxxx]
Sent: Sunday, April 29, 2001 3:12 AM
To: '802.3ae'
Subject: Inter-frame transmission length


In D1.1 clause, a Table (46-4) was attached, which described how to
implement an IPG of 12 bytes in average.
Since then, the following draft excluded this table, and almost nothing is
said about how IPG should be transmitted.
This clause doesn't even talks about the average IPG length anymore, which
looks like a real "hole" in the text.
Why is the inter-frame length table excluded?
Is it to enable more flexibility? 
Is it aloud to transmit other IPG length algorithms (any exist)?
Is it aloud to transmit shorter average IPG?


Lior Re'em
Avaya Inc.
Email : lreem@xxxxxxxxx