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

Re: [802SEC] Comments on 802.1Q ECMP

Tony
Oops, I forgot that. You are correct, it is not necessary to include the scope and purpose in an amendment.
If the intention is not to include the scope and purpose in the published amendment, then I retract that comment.
If the intention of the group is to include the scope and purpose in the amendment, then it would be best if it is changed. 

Thanks for the clarification.

James Gilb

On 03/14/2011 11:21 PM, Tony Jeffree wrote:

James -

The WG will respond formally to your comments in due course, but I would
observe that with reference to you point on 5.2, this is a draft PAR for an
*amendment* to a base standard, and as such, the scope stated in 5.2 is the
scope of the *project*, and is not, nor is it required to be, a statement of
the wording of the Scope subclause of the standard itself. Therefore, your
rationale for requesting the deletion of the sentence is invalid. The
sentence is certainly relevant to the scope of the project, which is why it
was there in the draft PAR.

Regards,
Tony


On 15 March 2011 05:50, James P. K. Gilb<gilb@ieee.org>  wrote:


All

Section 5.2

"It is anticipated that a new Tag will be defined possibly including a Time
to Live (TTL) field."

Delete this sentence as it will not look right in the published standard.
  Furthermore, this is an implementation detail, I think that the scope is
sufficient without it.

Section 5.3

My assumption is that 802.1aq is not broken without the addition of the new
project, but rather the new project enhances the capabilities provided in
802.1aq and that 802.1aq has advanced through a significant part of the
process.

If both these are true, then this subsection should include that
information.  If my assumption is not true, then it would be better to
include this as part of the 802.1aq project.

Section 5.4

Because the purpose will go into the draft unmodified, remove references to
802.1aq and simply reference the features of 802.1aq.  For example, in the
first sentence, change it to say "... equal cost paths than the Equal Cost
Tree (ECT) mechanism ..."

Also do not use "would be used", rather say "This standard is used with the
802.1 control plane and uses specific ..."

Delete "This standard may ... the new Tag formats".

In the third paragraph, change to "Both ECT and ECMP can be used at the
same time ..."

No comments on the 5C.

Thanks

James Gilb
IEEE 802 LMSC Recording Secretary

----------
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.