Re: [802SEC] Call for Comments on 802.23 draft
Rather than try to figure out Commentary (which seems too specific at this stage anyway), I'm just going to send a couple of quick thoughts in this email. Overall, the document is much improved, but needs a little more specificity and some re-orientation.
Section 5.3: This section has a lot of good stuff in it. I would suggest moving the section 5.3.2. to a new subsection titled something like "Overview of existing 802 location capabilities).
Section 5.3.1.1: The references you're looking for are RFC 5985, RFC 4776, and draft-ietf-geopriv-rfc3825bis (soon to be RFC ).
Section 6.1: The content of this section is true, but not too helpful. I would expect this section to list what this group will be defining in support of location. As I recall from the interim, there were two use cases discussed: (1) provision of location from the last-hop 802 element to the EUT and (2) provision of location to a management device. Use case 1 is addressed with LLDP plus a location MIB, while use case two is addressed with SNMP and a location MIB, plus a way to discover the right SNMP device to query. So this section should give the above overview (in a less abbreviated form), and have placeholders for the definigion of (a) a location MIB, and (b) a discovery mechanism (possibly based on 802.1ag?).
Section 6.2: This section should note that segregating "emergency only" traffic using an "emergency VLAN" is (a) a network-internal choice, and (b) possible to implement in other ways, e.g., MAC address based ACLs.
Section 6.2: This section needs to say something about how the network recognizes which users are "emergency only". This will entail a modification to network access authentication procedures, e.g., by providing default "emergency only" credentials for WEP, WPA, 802.1X, etc. A network device can then decide how to class an EUT's traffic (via VLAN, ACL, etc.) based on whether the used the "emergency only" credentials or a real set of credentials.
Hope this helps,
--Ricahrd
On Jun 13, 2011, at 12:52 AM, Geoff Thompson wrote:
> Colleagues-
>
> In my last e-mail to you (attached below) I announce the availability of the first public version of the 802.23 draft. In that e-mail, I said that I would formally solicit comments to be considered and incorporated into the draft at our next meetings during the 802 Plenary Week in San Franciso the week of July 17.
>
> Please review the draft and record your comments using (the older version of) the 802.16 commenting tool, "Commentary 1.55".
> The tool does allow you to accumulate comments over multiple review sessions.
> Commentary is a standalone application that has both MAC and PC versions.
> Downloadable files are available at:
> http://www.ieee802.org/16/docs/Commentary/
>
> Please use "802.23 Ballot 1" as the fill-in for the field labeled "Letter Ballot Number or Ballot Code"
> Please mail the resulting comment file to me at:
> thompson@ieee.org
> With the subject line:
> Comments on 802.23/D0.9
> This is a 30 day comment period so please get your comments to me by midnight, July 13 AoE
> I will bring the assembled comments to the meeting
> Comments are welcome from any interested or materially interested party.
>
> If you have any question please get in touch with me directly
> Best regards,
> Geoff Thompson, 802.23 WG Chair
>
> =========================================
> Subject: 802.23 Initial Public draft posted
> Date: Tue, 24 May 2011 14:11:00 -0700
> From: Geoff Thompson <thompson@ieee.org>
> Reply-To: thompson@ieee.org
> To: 802-23 Emergency Services <STDS-802-23-emergencyservices@LISTSERV.IEEE.ORG>
> CC: 802 EC <stds-802-sec@IEEE.ORG>
>
> Colleagues-
>
> I am happy to report that 802.23 had a successful meeting in King of
> Prussia, PA. Although we did not have any more attending the meeting
> than normal, we had a very productive meeting with the help of Richard
> Barnes who helped shake out out concepts with respect to operation and
> inter-layer relationships. We reviewed my initial cut at a draft and
> refined and simplified our concepts. In the time since the meeting we
> have generated a new version of the draft which we are making available
> for public review.
>
> The draft is available at the following URL:
>
> https://mentor.ieee.org/802.23/dcn/11/23-11-0013-00-ESWG-draft-p802dot23-d0pt9-pdf-es-wg-draft.pdf
> or alternatively at:
> http://tinyurl.com/3lo9bc6
> You may also retrieve the draft by going to the 802.23 document site
> https://mentor.ieee.org/802.23/documents
> and selecting [Download] for 2011 DCN 13
>
> Geoff
>
> We are happy to accept comments from all interested parties as Observer
> comments. All comments will be considered.
> I would appreciate your review.
>
> I expect to post commenting tools and ask for formally submitted
> comments to be submitted for review at our Working Group meeting
> (Tues/Wed/Thurs AM) at the next 802 Plenary in San Francisco.
> http://ieee802.facetoface-events.com/session/70/page/index/id/index
> http://ieee802.facetoface-events.com/files/sessions/70/announcement.pdf
>
> Best regards,
>
> Geoff
>
> Geoffrey O. Thompson
> Chair, IEEE 802.23 Emergency Services Working Group
>
> GraCaSI Standards Advisors
> 158 Paseo Ct.
> Mountain View, CA 94043-5286
> <thompson@ieee.org>
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.