1 / 9

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ Resolution for Frame Format Comments - LB67 ] Date Submitted: [ March 16, 2011] Source: [ Larry Taylor] Company: [DTC (UK) ] Address: [] Voice: [] E-Mail:[larry.taylor@acm.org ]

abdul-barnes
Download Presentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

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. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Frame Format Comments - LB67] Date Submitted: [March 16, 2011] Source:[Larry Taylor] Company: [DTC (UK)] Address: [] Voice: [] E-Mail:[larry.taylor@acm.org] Re: [Comment Resolution for TG4g LB67 draft] Abstract:The presentation proposes resolution for LB67 frame format comments Purpose: Presented to the 802.15.4g SUN Task Group for consideration and discussion Notice: This document has been prepared to assist the IEEE P802.15. 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 acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

  2. Comments to be Resolved • Comments on maximum PSDU size: • CID# 8 • CID# 9 • CID# 57 • CID# 259 • CID# 277

  3. Maximum PSDU Size • The comments suggest reducing the maximum PSDU size from 2047 to 1500 or to make the maximum PSDU size variable • These proposed changes need to be considered in the light of the complete set of 802.15.4 amendments • 4e amendment introduces MAC frame format changes for SUN applications • In particular, IE structures are used to carry additional header and payload information • IEs may be destined for the MAC, management plane or NHL • NHL data can be embedded in ‘Payload IEs’ or as MPDU data • Many applications for SUN are expected to be built using MESH techniques • Few systems negotiate maximum PSDU sizes (ex. PPP - only for P-P links) • In a MESH design, especially for low duty cycle systems, routing decisions are rarely fixed because of the cost of route maintenance • Source routing would require knowledge of the smallest maximum PSDU size supported on the path from source to destination

  4. Comments & Proposed Resolution • CID# 8: • Comment (9.1, page 40, line 12-13): • In Table 69, the maximum defined PSDU size (in octets) a 4g PHY shall be able to receive is unreasonably high and does not reflect the SUN applications space and constraints. • Proposed Change: • Change the value of the maximum PSDU that a 4g PHY shall be able to receive from 2048 to 1500 bytes, as defined in 4g PAR. • Recommend Resolution: Reject • Resolution: The 4g PAR states “PHY frame sizes up to a minimum of 1500 octets.” The PAR does not define a maximum PSDU size of 1500 bytes

  5. Comments & Proposed Resolution • CID# 9: • Comment (Annex D.7, page 124, line 12-13): • In Table D.2a, the size of the maximum PSDU a 4g PHY shall be able to receive is unreasonably high and does not reflect the SUN applications space and constraints. • Proposed Change: • Change the value of the maximum PSDU that a 4g PHY shall be able to receive to 1500 bytes, as defined in 4g PAR. • Recommend Resolution: • Resolution as per CID# 8 • Resolution: Slide 5

  6. Comments & Proposed Resolution • CID# 57: • Comment (9.2, page 41, line 12): • Text States "The maximum PSDU size (in octets) the PHY shall be able to receive is 2047". • Proposed Change: • Change text to state "up to 2047" this number is unnecessarily restrictive and could add significant cost to devices that may never use even 1/10 of this PSDU length. • Recommend Resolution: Reject • Resolution: • Variable PSDU limits imply onerous protocol overheads for system architectures expected to be used for SUN systems. Slide 6

  7. Comments & Proposed Resolution • CID# 259: • Comment (5.2.4.2.1, page 15, line 39): • In the SUN PHY Capabilities IE, add a parameter for maximum PSDU size supported by the device. • Proposed Change: • Insert a 2-octet field between Frequency Bands Supported and PHY Type Descriptor(s). The field is the maximum PSDU size supported and has a valid range of 128-2047. • Resolution: • Resolution as per CID# 57 • Resolution Reason: Slide 7

  8. Comment & Proposed Resolution • CID# 277: • Comment (D7.2.1a, page 124, line 12): • A PSDU size of 2047 should not be mandatory for SUN devices. While the protocol supports this value, there may be a variety of devices in the network, e.g. reduced function devices, whose maximum supported packet size is less than 2047. The device's max packet size should be included in the SUN PHY Capabilities IE. • Proposed Change: • Remove the PSDU size requirement that is specific for SUN devices or change the required value to a lower number, e.g. a SUN device shall support a packet size of at least 512 octets. • Resolution: • Resolutions as per CID# 57 • Resolution Reason: Slide 8

  9. Motion • To accept resolutions to CID #s • 8, 9, 57, 259, 277 • As per document • 802.15-11-0250-00-004g

More Related