1. LB93 Unresolved RFI Comments
March 2007
doc.: IEEE /0300r0
March 2007
LB93 Unresolved RFI Comments
Date:
Authors:
Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Guenael Strutt, Motorola
Guenael Strutt, Motorola

2. March 2007
doc.: IEEE /0300r0
March 2007
Abstract
Compendium of proposed resolutions or work related to RFI comments in TGs
Guenael Strutt, Motorola
Guenael Strutt, Motorola

3. Overview Currently 484 open comments in RFI
March 2007
doc.: IEEE /0300r0
March 2007
Overview
Currently 484 open comments in RFI
100% of deferred comments have been categorized
Standalone comments (55) are not assigned to any volunteer
Volunteers needed! (Please coordinate)
For details on RFI classification, please refer to 07/0238r1 – RFI Hillsboro
Guenael Strutt, Motorola
Guenael Strutt, Motorola

4. Open comments by category
March 2007
doc.: IEEE /0300r0
March 2007
Open comments by category
Complete submission under review!
OLSR update in progress!
Forwarding rewrite in progress!
Essential terminology issues (almost) resolved!
Metrics update in progress!
Complete submission under review!
Frame definition update in progress!
Guenael Strutt, Motorola
Guenael Strutt, Motorola

5. RFI4: Terminology Only 4 comments but essential work!
March 2007
doc.: IEEE /0300r0
March 2007
RFI4: Terminology
Only 4 comments but essential work!
General definitions
“Proxy”
Routing/forwarding definitions
“Mesh broadcast” and “restricted mesh broadcast”
“Propagation” (no “re-transmission” or “flooding”)
HWMP definitions
Originator
Destination
Forward/reverse path
Next hop/precursor
Sequence number
Almost done with a suggested resolution… but it is everyone’s responsibility to use the correct terminology everywhere in the draft!
Guenael Strutt, Motorola
Guenael Strutt, Motorola

6. There will probably be a separate submission for each sub-category
March 2007
doc.: IEEE /0300r0
March 2007
RFI3: Metrics
Sub-categorization:
Extensible Routing Framework
Airtime metric
Link State Announcement
Presentation: r0
There will probably be a separate submission for each sub-category
Guenael Strutt, Motorola
Guenael Strutt, Motorola

7. March 2007
doc.: IEEE /0300r0
March 2007
RFI7-8: Forwarding
doc: r0 – Updated texts for frame addressing and forwarding in a mesh network
Guenael Strutt, Motorola
Guenael Strutt, Motorola

8. RFI12: Interworking Better describe frame handling by the Mesh Portal
March 2007
doc.: IEEE /0300r0
March 2007
RFI12: Interworking
Better describe frame handling by the Mesh Portal
There is some overlap with RFI2: portals must also carry data to proxies
Guenael Strutt, Motorola
Guenael Strutt, Motorola

9. March 2007
doc.: IEEE /0300r0
March 2007
RFI2: Proxy
Two new frame formats (Request and Reply) to update an MP proxy entry to root.
Update in the interworking section to handle broadcast frame and sequence number handling for a frame generated by a proxied device.
Sequence number section has more details on how to handle destination sequence numbers.
Update in RREP processing section on how to create/maintain precursor list.
RREQ/RREP IE is updated to include a proxied device address. This is useful when an MP generates a RREQ on behalf of a legacy device. The current text uses a flag to indicate if the "proxied device address" is present in RREQ/RREP. However we can very well make it a fixed field.
New text on Proxy Update Request and Proxy Update Reply IE handling.
Guenael Strutt, Motorola
Guenael Strutt, Motorola

10. March 2007
doc.: IEEE /0300r0
March 2007
RFI13: Mesh Data Frame
Outline of document (submission) in progress. First draft of document by end of this week for review.
Will address Clause 11A.2.4 and parts of Clause 7. Text will be refined to clear up confusion and give more thorough descriptions.
Guenael Strutt, Motorola
Guenael Strutt, Motorola

11. March 2007
doc.: IEEE /0300r0
March 2007
References
doc.: IEEE /0023r19 – Resolution of comments received during IEEE Letter Ballot 93
doc.: IEEE /0238r1 – RFI Hillsboro
Guenael Strutt, Motorola
Guenael Strutt, Motorola