1 / 11

RFI Tüddelkram

RFI Tüddelkram. Authors:. Date: 2009-11-16. Abstract. Asking the Task Group about a direction for resolving miscellaneous RFI comments. . Content. PANN & RANN in Beacon Implementation Confusion with CIDs 953 & 954 Periodicity in PANN / RANN. Why they should be removed

alaula
Télécharger la présentation

RFI Tüddelkram

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RFI Tüddelkram Authors: Date: 2009-11-16 Michael Bahr, Siemens AG

  2. Abstract Asking the Task Group about a direction for resolving miscellaneous RFI comments. Michael Bahr, Siemens AG

  3. Content • PANN & RANN in Beacon • Implementation Confusion with CIDs 953 & 954 • Periodicity in PANN / RANN Michael Bahr, Siemens AG

  4. Why they should be removed beacon bloat (15+19 = 34 byte) security: not protected implementation cannot count on them method: periodic PANN & RANN management frames inside mesh BSS Why they should be there beacons are sent anyway method: periodic PANN & RANN elements in beacons PANN & RANN in Beacon Michael Bahr, Siemens AG

  5. Strawpoll Should the RANN & PANN be removed from the beacon? • CIDs 442, 846  accept • Yes: No: Don‘t know/Don‘t care: Michael Bahr, Siemens AG

  6. Implementation Confusion with CIDs 953 & 954 Draft D3.04: • still there as dot11MeshHWMPActivated • renaming happened with D3.02 Locations: • Table 7-8 Beacon frame body • Dot11MeshStationConfigEntry Michael Bahr, Siemens AG

  7. Solution (A) Delete dot11MeshHWMPActivated (Accepted resolution to CIDs 953 & 954) • Table 7-8 Beacon frame body • no entry in Dot11MeshStationConfigEntry Michael Bahr, Siemens AG

  8. Solution (B) Replace with MIB variable that holds the path selection protocol identifier of the active path selection protocol • Table 7-8 Beacon frame body • Dot11MeshStationConfigEntry Michael Bahr, Siemens AG

  9. Strawpoll Which solution do you prefer? • Solution (A): delete dot11MeshHWMPActivated • Solution (B): replace with MIB variable dot11MeshActivePathSelectionProtocol A: B: D(on‘t care): Michael Bahr, Siemens AG

  10. Periodicity in PANN / RANN • CIDs 156, 157, and 645 want to add the interval to the Portal Announcement (PANN) element and the Root Announcement (RANN) element respectively • Proposed resolution: • reject • Reasons: • Both PANN and RANN are purely informative elements that only annouce the presence of a portal or a root mesh STA • They don‘t setup any forwarding information that would need to be maintained • Mesh stations in power save mode won‘t miss PANNs and RANNs (stored at transmitting mesh STA until receiver becomes available) Michael Bahr, Siemens AG

  11. Strawpoll on Periodicity in PANN / RANN • Strawpoll to resolve CIDs 156, 157, and 645 with • resolution „Reject“ and • with resolution notes:The inclusion of a periodicity field in the PANN and RANN information elements is not considered necessary, because • Both PANN and RANN are purely informative elements that only annouce the presence of a portal or a root mesh STA • They don‘t setup any forwarding information that would need to be maintained • Mesh stations in power save mode won‘t miss PANNs and RANNs (stored at transmitting mesh STA until receiver becomes available) • Yes: No: Abstain Michael Bahr, Siemens AG

More Related