Re: [802SEC] 802.3ar congestion management PAR
Our thanks to 802.1 for review of our PAR. The responses to your
1. The revised draft PAR has changed the selection to "Yes" with
appropriate explanatory text.
2. The project objectives are used within 802.3 as an agreement of work
between a Task Force and 802.3, they are not part of the 802 process for
PARs. The objective is a statement of what is expected from cooperative
work between 802.3 and 802.1, and has not been revised since the
decision to solicit 802.1 work on congestion management initiated at
your Ottawa interim meeting.
Chair, IEEE 802.3 Working Group
>[mailto:email@example.com] On Behalf Of Tony Jeffree
>Sent: Tuesday, November 16, 2004 2:42 PM
>Subject: [802SEC] 802.3ar congestion management PAR
>Dear Bob -
>802.1 comments on 802.3ar congestion management PAR:
>1) In section 13, the Scope refers to "support of 802 congestion
>management", which does not exist at present, and it is not
>charter to develop. Therefore, some 802-wide action is
>required before this
>portion of the 802.3ar PAR can be completed. The PAR should
>this is the case, and the answer "no" to the question on
>2) With regard to the stated project objectives, 802.3 has
>not defined buffering, and congestion management is intimately
>with buffering. If 802.3 is planning to change this, then the service
>offered to a Bridge will change significantly. If not, then
>the problem is
>not 802.3's alone.
>Therefore, this work should be connected with, and be
>dependent upon, work
>undertaken in a broader scope than 802.3.
>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.