| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Questions on the proposal 1)
How is express traffic identified versus non-express traffic?
a.
Does it use the LLID to identify the difference between the two streams? 2)
Are you using the same method of CRC inversion to identify a frame has been fragmented?
a.
Does the fragments and final frag use the FCS of the entire frame? That is the final FCS of the frame would be the same FCS as if the frame was sent
in a single fragment? Clarifying these items makes the proposal much stronger. Regards Denis Beaudoin DMTS Texas Instruments
dbeaudoin@xxxxxx W: 214-480-3287/77
M: 214-475-9193 From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxxxxx]
Dear IET Task Force members, Attached please find a contribution from myself and Curtis, proposing to reuse in IET the format of preamble already defined and used actively in 802.3. One of the largest advantages of this proposal is that if accepted, we will be automatically
aligned with EPON, making the specification ready for when IET function is extended to EPON. There are no disadvantages of this format, as far as we can tell. I would like to request a 20 minute slot (excluding Q&A) at the upcoming meeting to discuss this presentation and have it considered for adoption in the next version of the draft. Regards
|