Re: [802SEC] Comments on 802.1 PARs
James -
I'm sure that Pat will be responding more fully on your comments in due course; however,
in the case of the missing space in the title of the Qaz PAR text, this is an artefact
produced by the PAR input form/display when it concatenates various fields to construct
the full title. Needless to say, we have absolutely no plans to fix the PAR input
mechanism.
Regards,
Tony
-----Original Message-----
From: James Gilb [mailto:gilb@ieee.org]
Sent: 17 November 2009 20:43
To: Tony Jeffree
Cc: 802 EC
Subject: Comments on 802.1 PARs
Tony
Here are my comments on the three 802.1 PARs.
802.1Qbg
PAR
Some words are cut off in the PDF
5.4 - "managemen" should be "management"
5.5 - "an" is cut off on first line of third paragraph.
5C
- 1.a. "advance" should be "advanced"?
- 1.a. What is reflective relay? It would help if this was defined
somewhere.
- 4.a. Linux is a trademark, use Linux^TM perhaps?
802.1Qbh
PAR
5.2 - Is full-duplex required for this protocol to work? It seems
strange that 802.1Q level standards care if a medium is full duplex or
half duplex. Note that many of the wireless standards are not full
duplex. I think this would be much more useful if it did not require
full duplex.
5C
4.c. "yield increase in reliably" should be "yield an increase in
reliability"
5.a. "Port Extenders are expected to cost less than existing bridges.
This is both intuitive and supported by experience in existing
deployments of this technology. In addition, the resultant reduction
in management complexity brings significant cost advantages." Well, it
isn't intuitive to me. Please explain why port extenders lead to a
cheaper system. In particular, if it reduces the cost of one device,
does it increase cost in another? Is the cost reduction significant?
802.1Qaz
PAR
2.1 Missing space in "NetworksAmendment"
Thanks
James Gilb
802 EC Recording Secretary
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.