doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 1 Proxy Update Element Revision Date: Authors:

doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 2 Abstract This presentation gives an overview of text document 11-09/0857r0 which gives changes to normative text in order to resolve some comments related to the proxy update information element. Changes relate to: abbreviation of Proxy Update –PU  PXU extension of format of Proxy Update element –structure is per proxy information –arbitrary structure of proxy information (individual add/delete, lifetime, proxy mesh STA address) proxied device –external device, represented device

doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 3 PU comment CID 1090 –requests to use other abbreviation ambiguous abbreviation –Proxy Update –Peer U-APSD used in „PU buffer STA“, „PU sleep STA“ comes from IEEE z D4.0 wrong spelling: correct is Pooh! proposal: PU  PXU (PUC  PXUC)

doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 4 Format of PU proxy information on mesh STA –represented MAC address –proxy mesh STA MAC address this mesh STA other mesh STA (= destination mesh STA, if this mesh STA is the source mesh STA) –proxy information lifetime limited flexibility with current PU –either add or delete for all proxy information –no flexibility on proxy information lifetime –mesh STA can only report proxy information where it is proxy mesh STA

doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 5 Format of PXU Add / Delete this proxy information Source Proxy indicates whether Proxy MAC Address subfield is present. If not present, Proxy MAC Address = PXU Originator MAC Address Proxy Information Lifetime subfield is present or not

doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 6 Proxied Device Proxied MAC Address confusing with Proxy MAC Address suggestions for proxying proxied –external might be to broad in situations relating to proxy information: not every external device is necessarily a proxied device –represented proposal –use represented device/address etc. when talking about proxy information and closely related issues –use the more appropriate of external or represented in other cases other suggestions?

doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 7 Motion Move to adopt document 11-09/0857r0 as resolution to comments with CIDs 879, 914, 1090, all with counter.

doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 8 References IEEE s WLAN Mesh Networking draft standard, D /0857r0 „Proxy Update Element Revision“ (proposed text changes)