Re: [802SEC] IEEE 802.3 comments on P802.1AS
I wonder if you could please clear up some confusion I have regarding
I understood from your response to Bob that 'In the PAR Scope we have
clarified that this mechanism relates to networks "...composed of LAN
media where the transmission delays are fixed and symmetrical; for
example, IEEE 802.3 full duplex links".' However, I cannot find that
language in the scope of the PAR at the URL you cited.
Also, you mentioned that you had "removed the conflicting wording
from the 5C, where it was superfluous." But the only 5C language that
802.3 mentioned was "full duplex Ethernet or similar links", and that
language DOES exist in the 5C you mentioned.
Could you please help me understand?
At 05:08 PM +0000 06/03/08, Tony Jeffree wrote:
>Many thanks for your comments.
>Item 16 is now dated.
>In Item 17, we refer to IEEE 1588. There are no other projects of
>Item 20b is now answered.
>In the PAR Scope we have clarified that this mechanism relates to
>networks "...composed of LAN media where the transmission delays are
>fixed and symmetrical; for example, IEEE 802.3 full duplex links",
>and have removed the conflicting wording from the 5C, where it was
>There are a small number of other minor typographical changes.
>The revised draft PAR and 5C can be found here:
>At 02:03 08/03/2006, you wrote:
>>We held an 802.3 ad hoc meeting to discuss the AV Bridging PAR and
>>provide the following comments to 802.1. I will forward other
>>comments (if any) from individuals separately.
>>1. The PAR describes the scope expected and promised in early work
>>in this area. The five criteria on the other hand appear to narrow
>>the project scope to only "full duplex Ethernet or similar links".
>>Are there any other MAC WGs that provide such links than 802.3?
>>The PAR and criteria should agree on the scope and application of
>>the intended standard. If the project is only intended to address
>>802.3 links, the PAR should say that.
>>2. The PAR form is not complete. Item 16 is not dated. Item 17
>>should reference related projects in the digital home area (e.g.,
>>UpNP). Item 20b is not answered.
>>We look forward to your response.
>>Chair, IEEE 802.3
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.