Re: [STDS-802-11-TGAI] CIDs on Fragmentation and Reassembly from LB201

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Inspired by Dan's fine work in 14/0672, I would like to offer the

following wording for 9.41 and 9.42, which I believe addresses all

comments in 14/0673:

9.41 Element fragmentation

The general format of elements (see 8.4.2.1) limits the information that can be carried in an element to 255 octets. Information that is too large for a single element in an MMPDU shall be fragmented into a series of elements in that MMPDU consisting of the element into which the information does not fit (the leading element), immediately followed by one or more Fragment elements.

NOTE—These elements might be transmitted across different MPDUs, per the procedures for MSDU/MMPDU fragmentation (see 9.5 and 9.6).

The information to be fragmented, of length l_info, shall be divided into portions. The leading element shall contain the first portion of information in the Information field. The length of the Information field in this element shall be 255.

The leading element shall be immediately followed by m Fragment elements, where m is Floor (l_info / 255) – 1, each containing the next portion of information in the Fragmented Data field. The length of the Fragmented Data field in these elements shall be 255.

If n is nonzero, where n is l_info mod 255, these elements shall be immediately followed by a Fragment element containing the remaining portion of information in the Fragmented Data field. The length of the Fragmented Data field in this element shall be n.

Information that fits in a single element shall not be fragmented.

NOTE—This includes the information in a Fragment element.

9.42 Element defragmentation

An element that is immediately followed by one or more Fragment elements shall be identified as a leading element for information that has been fragmented. To reconstruct the original information, the Information field in the leading element shall be concatenated, in order, with the Fragmented Data fields of the Fragment elements that immediately follow it. The defragmentation procedure for each item of information that has been fragmented shall terminate when any element other than a Fragment element is encountered or the end of the MMPDU is reached.

NOTE—A Fragment element only ever follows an element whose Information field has a length of 255.

Mark

Mark RISON, Standards Architect, WLAN English/Esperanto/Français

Samsung Cambridge Solution Centre Tel: +44 1223 434600

Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601

ROYAUME UNI WWW: http://www.samsung.com/uk

From: *** 802.11 TGai - Fast Initial Link Set-Up *** [mailto:STDS-802-11-TGAI@xxxxxxxx] On Behalf Of Dan Harkins
Sent: 14 May 2014 09:16
To: STDS-802-11-TGAI@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGAI] CIDs on Fragmentation and Reassembly from LB201

Hello,

If you made a comment in LB201 on sections 9.41 or 9.42, on element fragmentation

and element reassembly, respectively (you know who you are!), I have a proposed

resolution to your comment(s) and invite you to take a look at two documents and, if

desired, comment on the resolution(s).

The relevant CIDs and the proposed resolutions are in document 11-14/0673r0 and

the proposed text modifications resulting from those CIDs that were accepted or

countered are in document 11-14/0672r0. Both up on mentor.

Please take a look.

regards,

Dan.

_______________________________________________________________________________

IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.

SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAI and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.

Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________

IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.