Doc.: IEEE 802.11-09/1259r0 Submission Nov 2009 Michael Bahr, Siemens AGSlide 1 RFI Tüddelkram...

Nov 2009

Michael Bahr, Siemens AG

Slide 1

doc.: IEEE 802.11-09/1259r0

Submission

RFI TüddelkramDate: 2009-11-16

Name Affiliations Address Phone email Michael Bahr Siemens AG,

Corporate Technology

Otto-Hahn-Ring 6 80200 München Germany

636-49926 bahr et siemens dot com

Authors:

Nov 2009


Slide 2

doc.: IEEE 802.11-09/1259r0

Submission

Abstract

Asking the Task Group about a direction for resolving miscellaneous RFI comments.

Nov 2009


Slide 3

doc.: IEEE 802.11-09/1259r0

Submission

Content

• PANN & RANN in Beacon

• Implementation Confusion with CIDs 953 & 954

• Periodicity in PANN / RANN

Nov 2009


Slide 4

doc.: IEEE 802.11-09/1259r0

Submission

PANN & RANN in Beacon

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

442 17 37-43 7.2 Format of individual frame types

Open the portal and root announcments "may bepresent". And therefore they may also beabsent. So an implementation cannot counton them to be there.

Let's just remove them from beacons becausebeacon bloat is becoming a problem.

Defer Big question. See 846

846 17 38-51 7.2 Format of individual frame types

Open Portal Announcement and RootAnnouncement are management framesimportant for mesh operation. They should beprotected. This is not the case for beacons.Furthermore, it is not necessary that non-peermesh STA know about these twoannouncements.

Do not allow Portal and Root announcementin Beacon. Delete rows 50 and 51.

Defer Big question. See 442

1084 19 32 7.2 Format of individual frame types

Open The "root announcement" and the "portalannouncement" elements are conspicuouslymissing from table 7-15

Add the missing elements? Defer Must be resolved with CIDs 442 and 846

Nov 2009


Slide 5

doc.: IEEE 802.11-09/1259r0

Submission

Strawpoll

Should the RANN & PANN be removed from the beacon?• CIDs 442, 846 accept

• Yes: No: Don‘t know/Don‘t care:

Nov 2009


Slide 6

doc.: IEEE 802.11-09/1259r0

Submission

953 197 24 D. ASN.1 encoding of the MAC and PHY MIB

Closed 05/14/09 dot11MeshHWMPEnabled is never used delete it Accept Done 3,01

954 197-198 65-8 D. ASN.1 encoding of the MAC and PHY MIB

Closed 05/14/09 dot11MeshHWMPEnabled is never used delete it Accept Done 3,01

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

Nov 2009


Slide 7

doc.: IEEE 802.11-09/1259r0

Submission

Solution (A)

Delete dot11MeshHWMPActivated (Accepted resolution to CIDs 953 & 954)

• Table 7-8 Beacon frame body

• no entry in Dot11MeshStationConfigEntry

Nov 2009


Slide 8

doc.: IEEE 802.11-09/1259r0

Submission

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

Nov 2009


Slide 10

doc.: IEEE 802.11-09/1259r0

Submission

Strawpoll

Which solution do you prefer?• Solution (A): delete dot11MeshHWMPActivated

• Solution (B): replace with MIB variable dot11MeshActivePathSelectionProtocol

A: B: D(on‘t care):

Nov 2009


Slide 11

doc.: IEEE 802.11-09/1259r0

Submission

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)

Nov 2009


Slide 12

doc.: IEEE 802.11-09/1259r0

Submission

Motion: Periodicity in PANN / RANN

• Moved, 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)

• Mover: Seconder:

• Yes: No: Abstain

Doc.: IEEE 802.11-09/1259r0 Submission Nov 2009 Michael Bahr, Siemens AGSlide 1 RFI Tüddelkram...

Documents

Transcript of Doc.: IEEE 802.11-09/1259r0 Submission Nov 2009 Michael Bahr, Siemens AGSlide 1 RFI Tüddelkram...