Docstoc

Download - IEEE

Document Sample
Download - IEEE Powered By Docstoc
					                                       IEEE_Cover

July 2010

                                      IEEE P802.15
                             Wireless Personal Area Networks

Project               IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Title                 802.15.6 Letter Ballot Comment Submission
Date Submitted May 27 2010
Source         Arthur Astrin
               Astrin Radio
               1051 Greenwood, Palo Alto, CA 94301, USA
                      Daniel Lewis
                      NICTA
                      7 London Circuit, Canberra, ACT 2600, Australia

Re:                   d01P802-15-6_Draft_Standard


Abstract              802.15 TG6 Comments Register for LB55
Purpose               [This document is used to submit comments for TG6 Letter Ballot.]
Notice                This document has been prepared to assist the IEEE P802.15. It is offered as a basis for
                      is not binding on the contributing individual(s) or organization(s). The material in this d
                      subject to change in form and content after further study. The contributor(s) reserve(s) t
                      amend or withdraw material contained herein.


Release               The contributor acknowledges and accepts that this contribution becomes the property o
                      may be made publicly available by P802.15.



             DONE:    1837
              LEFT:   0
            TOTAL:    1837
          DEFERED:    0

                      0




                                          Page 1
                                                            IEEE_Cover

             P802-15-6_LB55_Comment_Register.xls
             DCN 15-10-0702-00-0006




ess Personal Area Networks (WPANs)
Submission

             Voice: +1 650 704 2517

             E-mail: astrin@ieee.org
             Voice: +61 2 6267 6252

             E-mail: daniel.lewis@nicta.com.au




 5
ents for TG6 Letter Ballot.]
st the IEEE P802.15. It is offered as a basis for discussion and
 ual(s) or organization(s). The material in this document is
er further study. The contributor(s) reserve(s) the right to add,
erein.


ts that this contribution becomes the property of IEEE and
15.




                                                               Page 2
Name         Affiliation     Category Page   Sub-clause   Line #




             Jones-Petrick
Al Petrick   and Associates Technical

             Jones-Petrick
Al Petrick   and Associates Editorial   17   5.5.2.2      12

             Jones-Petrick
Al Petrick   and Associates Editorial        6.1          2

             Jones-Petrick
Al Petrick   and Associates Editorial   13   5.2          10

             Jones-Petrick
Al Petrick   and Associates Technical 14     5.3          4

             Jones-Petrick
Al Petrick   and Associates Editorial

             Jones-Petrick
Al Petrick   and Associates Editorial   22   6.2.1.1.8

             Jones-Petrick
Al Petrick   and Associates Technical 23     6.2.1.1.9    4

             Jones-Petrick
Al Petrick   and Associates Editorial   25   6.2.1.1.12

             Jones-Petrick
Al Petrick   and Associates Editorial   26   6.2.2

             Jones-Petrick
Al Petrick   and Associates Editorial   27   6.2.3        24

             Jones-Petrick
Al Petrick   and Associates Editorial   27   6.2.3        25

             Jones-Petrick
Al Petrick   and Associates Editorial   27   6.2.3

             Jones-Petrick
Al Petrick   and Associates Technical 28     6.2.3        1

             Jones-Petrick
Al Petrick   and Associates Editorial   28   6.2
             Jones-Petrick
Al Petrick   and Associates Technical 32      6.3.2.3.1    5

             Jones-Petrick
Al Petrick   and Associates Editorial   34    6.3.2.6.2    28

             Jones-Petrick
Al Petrick   and Associates Editorial   41    6.3.6.6.7    2

             Jones-Petrick
Al Petrick   and Associates Editorial   41    6.3.6.8      17

             Jones-Petrick
Al Petrick   and Associates Editorial   41    6.3.6.8      17

             Jones-Petrick
Al Petrick   and Associates Editorial   47    6.3.11.4.2   9

             Jones-Petrick
Al Petrick   and Associates Editorial   53    6.4.8.       1


             Jones-Petrick
Al Petrick   and Associates Technical 58      6.7

             Jones-Petrick
Al Petrick   and Associates Editorial   54    6.4.8.7      7

             Jones-Petrick
Al Petrick   and Associates Editorial   141   9


             Jones-Petrick
Al Petrick   and Associates Technical 142     9.1          10

             Jones-Petrick
Al Petrick   and Associates Editorial   142   9.1

             Jones-Petrick
Al Petrick   and Associates Editorial   144   9.2          15

             Jones-Petrick
Al Petrick   and Associates Technical 146     9.3          4

             Jones-Petrick
Al Petrick   and Associates Editorial   147   9.3

             Jones-Petrick
Al Petrick   and Associates Editorial   148   9.3.2        18
             Jones-Petrick
Al Petrick   and Associates Editorial     150    9.4

             Jones-Petrick
Al Petrick   and Associates Technical 153        9.4.5


             Jones-Petrick
Al Petrick   and Associates Technical 157        9.7

             Jones-Petrick
Al Petrick   and Associates Editorial     165    10.3.1     26

             Jones-Petrick
Al Petrick   and Associates Editorial     166    10.4       5

             Jones-Petrick
Al Petrick   and Associates Editorial     166    10.5

             Jones-Petrick
Al Petrick   and Associates Technical 167        10.5.2

             Jones-Petrick
Al Petrick   and Associates Editorial     134    8.3.1      29



             Jones-Petrick
Al Petrick   and Associates Technical 113        7.12.3.3   113

             Jones-Petrick
Al Petrick   and Associates Technical 110        7.12.2     110

             Jones-Petrick
Al Petrick   and Associates Editorial     108    7.12

             Jones-Petrick
Al Petrick   and Associates   Editorial   54     6.4.8.6
             Texas                        195-
Anuj Batra   Instruments      Technical   208    11
             Texas                        195-
Anuj Batra   Instruments      Technical   208    11
             Texas                        195-
Anuj Batra   Instruments      Technical   208    11
             Texas                        195-
Anuj Batra   Instruments      Technical   208    11
             Texas                        195-
Anuj Batra   Instruments      Technical   208    11
             Texas                        195-
Anuj Batra   Instruments      Technical   208    11
             Texas                   195-
Anuj Batra   Instruments   Technical 208      11
             Texas                   195-
Anuj Batra   Instruments   Technical 208      11
             Texas                   195-
Anuj Batra   Instruments   Technical 208      11
             Texas                   195-
Anuj Batra   Instruments   Technical 208      11
             Texas                   195-
Anuj Batra   Instruments   Technical 208      11
             Texas                   195-
Anuj Batra   Instruments   Technical 208      11
             Texas
Anuj Batra   Instruments   Editorial   195    11.1   4
             Texas
Anuj Batra   Instruments   Editorial   195    11.1   8-11
             Texas
Anuj Batra   Instruments   Technical 195      11.1   12
             Texas
Anuj Batra   Instruments   Editorial   195    11.2   16
             Texas
Anuj Batra   Instruments   Editorial   195    11.2   16-17
             Texas
Anuj Batra   Instruments   Editorial   195    11.2   17
             Texas
Anuj Batra   Instruments   Editorial   195    11.2   18
             Texas
Anuj Batra   Instruments   Editorial   195    11.2   20
             Texas
Anuj Batra   Instruments   Editorial   195    11.2   footnote
             Texas
Anuj Batra   Instruments   Editorial   196    11.3   3
             Texas
Anuj Batra   Instruments   Editorial   196    11.3   3-4
             Texas
Anuj Batra   Instruments   Editorial   196    11.3   15
             Texas
Anuj Batra   Instruments   Technical 197      11.4   7
             Texas
Anuj Batra   Instruments   Editorial   197    11.4   6
             Texas
Anuj Batra   Instruments   Technical 197      11.4   2-6
             Texas
Anuj Batra   Instruments   Editorial   197    11.4   2-6
             Texas                     198-
Anuj Batra   Instruments   Editorial   199    11.4   6-8,1-3
             Texas
Anuj Batra   Instruments   Technical 199      11.5   14
             Texas
Anuj Batra   Instruments   Technical 199      11.5   18-19
             Texas
Anuj Batra   Instruments   Editorial   199    11.5   19
             Texas
Anuj Batra   Instruments   Technical 200     11.6     9
             Texas
Anuj Batra   Instruments   Technical 201     11.6     1
             Texas
Anuj Batra   Instruments   Technical 201     11.6     4
             Texas
Anuj Batra   Instruments   Technical 201     11.6     4
             Texas
Anuj Batra   Instruments   Editorial   201   11.6     4
             Texas
Anuj Batra   Instruments   Editorial   201   11.6     4
             Texas
Anuj Batra   Instruments   Technical 201     11.6     4
             Texas
Anuj Batra   Instruments   Technical 201     11.6     4
             Texas
Anuj Batra   Instruments   Technical 201     11.6     4
             Texas
Anuj Batra   Instruments   Technical 201     11.6     4
             Texas
Anuj Batra   Instruments   Technical 201     11.6.1   7
             Texas
Anuj Batra   Instruments   Editorial   201   11.6.1   7
             Texas
Anuj Batra   Instruments   Technical 201     11.6.1   7-10
             Texas
Anuj Batra   Instruments   Technical 202     11.6.1   1-2
             Texas                   201-
Anuj Batra   Instruments   Technical 202     11.6.1   7-10,1-2
             Texas
Anuj Batra   Instruments   Technical 202     11.6.2   4
             Texas
Anuj Batra   Instruments   Technical 202     11.6.2   4
             Texas
Anuj Batra   Instruments   Technical 202     11.6.2   3-7
             Texas
Anuj Batra   Instruments   Technical 202     11.7     11
             Texas
Anuj Batra   Instruments   Technical 202     11.7     16
             Texas
Anuj Batra   Instruments   Technical 203     11.7     5
             Texas
Anuj Batra   Instruments   Technical 203     11.8.1   9
             Texas
Anuj Batra   Instruments   Technical 203     11.8.1   11
             Texas
Anuj Batra   Instruments   Technical 204     11.8.1   4
             Texas
Anuj Batra   Instruments   Technical 204     11.8.1   1
             Texas
Anuj Batra   Instruments   Technical 204     11.81    9-10
             Texas
Anuj Batra   Instruments   Technical   205     11.8.2      5
             Texas
Anuj Batra   Instruments   Editorial   205     11.8.2      13
             Texas
Anuj Batra   Instruments   Technical   205     11.8.2      13
             Texas
Anuj Batra   Instruments   Technical   206     11.9.1      7
             Texas
Anuj Batra   Instruments   Technical   206     11.9.1      7
             Texas
Anuj Batra   Instruments   Technical   206     11.9.1      11
             Texas
Anuj Batra   Instruments   Technical   206     11.9.1      1-15
             Texas
Anuj Batra   Instruments   Technical   206     11.9.1      1-15
             Texas
Anuj Batra   Instruments   Technical   207     11.9.2      6
             Texas
Anuj Batra   Instruments   Technical   207     11.9.2      7
             Texas
Anuj Batra   Instruments   Technical   207     11.9.3      11
             Texas
Anuj Batra   Instruments   Technical   207     11.9.3      16
             Texas
Anuj Batra   Instruments   Editorial   207     11.9.3      16
             Texas
Anuj Batra   Instruments   Editorial   208     11.10.1     10
             Texas
Anuj Batra   Instruments   Technical   208     11.10.1     13
Billy Verso  DecaWave      Technical   14      5.3         2...2
             Limited
Billy Verso  DecaWave      Technical   19..140 6 and 7,    -
             Limited                           (&maybe8)
Billy Verso  DecaWave      Editorial   21      6.2.1.1.2   4,5
             Limited
Billy Verso  DecaWave      Editorial   22      6.2.1.1.8   15,16
             Limited
Billy Verso  DecaWave      Editorial   27      6.2.3       31
             Limited
Billy Verso  DecaWave      Editorial   57      6.6.2.3     11
             Limited
Billy Verso  DecaWave      Technical   57      6.6.2.3     11..12
             Limited
Billy Verso  DecaWave      Technical   157     9.6.2       2..5
             Limited
Billy Verso  DecaWave      Technical   164     10          1
             Limited
Bob Mason Elster Solutions Technical   9       3           17-20
Bob Mason Elster Solutions Technical   51-52   6.4
Bob Mason Elster Solutions Technical   164     10.1.1      26
             Medtronic
Charles Farlow             Editorial   5       3           20
             Medtronic
Charles Farlow           Editorial   7     3            16
             Medtronic
Charles Farlow           Editorial   9     3            14
             Medtronic
Charles Farlow           Editorial   16    5.5.1.4      28
             Medtronic
Charles Farlow           Editorial   22    6.2.1.1.6    4
             Medtronic
Charles Farlow           Editorial   22    6.2.1.1.7    12
             Medtronic
Charles Farlow           Editorial   24    6.2.1.1.11   40
             Medtronic
Charles Farlow           Technical   32    6.3.2.3.4    16-17
             Medtronic
Charles Farlow           Technical   40    6.3.6.6      9
             Medtronic
Charles Farlow           Technical   47    6.3.11.4.1   6
             Medtronic
Charles Farlow           Technical   47    6.3.11.4.3   15
             Medtronic
Charles Farlow           Editorial   48    6.3.11.5     3
             Medtronic
Charles Farlow           Technical   57    6.6.2.1      1
             Medtronic
Charles Farlow           Technical   57    6.6.2.3      10
             Medtronic
Charles Farlow           Editorial   72    7.2.6        9
             Medtronic
Charles Farlow           Technical   92    7.8          30-31
             Medtronic
Charles Farlow           Technical   93    7.8.1        12
             Medtronic
Charles Farlow           Technical   93    7.8.1        26-28
             Medtronic
Charles Farlow           Technical   94    7.8.2.1      9-10
             Medtronic
Charles Farlow           Technical   95    7.8.2.1.2    16-17
             Medtronic
Charles Farlow           Technical   96    7.8.2.1.3    4
             Medtronic
Charles Farlow           Technical   108   7.12         1
             Medtronic
Charles Farlow           Technical   108   7.12         1
             Medtronic
Charles Farlow           Technical   108   7.12         1
             Medtronic
Charles Farlow           Technical   119   8.1          13
             Medtronic
Charles Farlow           Technical   157   9.7          20
             Medtronic
Charles Farlow           Technical   160   9.7.8        10-16
             Medtronic
Charles Farlow           Editorial   162   9.8.4        6
             Medtronic
Charles Farlow           Technical   162   9.8.4        9-10
             Medtronic
Charles Farlow           Editorial   162   9.8.5        13
             Medtronic
Charles Farlow           Technical   162   9.8.5        16-17
             Medtronic
Charles Farlow           Editorial   164   10.2         31
             Medtronic
Charles Farlow           Editorial   195   11           1
             Medtronic
Charles Farlow           Technical   195   11           1
             Medtronic
Charles Farlow           Editorial   195   11.1         4
             Medtronic
Charles Farlow           Editorial   195   11.1         5
             Medtronic
Charles Farlow           Technical   195   11.2         16-23
             Medtronic
Charles Farlow           Editorial   196   11.3         2
             Medtronic
Charles Farlow           Editorial   196   11.3         7
             Medtronic
Charles Farlow           Editorial   196   11.3         9
             Medtronic
Charles Farlow           Editorial   196   11.3         10
             Medtronic
Charles Farlow           Editorial   196   11.3         12
             Medtronic
Charles Farlow           Editorial   196   11.3         18-20
             Medtronic
Charles Farlow           Editorial   197   11.4         3
             Medtronic
Charles Farlow           Editorial   197   11.4         6
             Medtronic
Charles Farlow           Technical   197   11.4         7-9
             Medtronic
Charles Farlow           Technical   197   11.4         11
             Medtronic
Charles Farlow           Technical   198   11.4         1
             Medtronic
Charles Farlow           Technical   198   11.4         4
             Medtronic
Charles Farlow           Technical   198   11.4         7-8
             Medtronic
Charles Farlow           Technical   199   11.5         10
             Medtronic
Charles Farlow           Technical   199   11.5         16
Charles FarlowMedtronic     Technical   200   11.5         2
Charles FarlowMedtronic     Technical   200   11.5         5
Charles FarlowMedtronic     Technical   200   11.5         7
Charles FarlowMedtronic     Editorial   200   11.6         9
Charles FarlowMedtronic     Technical   201   11.6         2
Charles FarlowMedtronic     Technical   201   11.6         4
Charles FarlowMedtronic     Editorial   201   11.6         4
Charles FarlowMedtronic     Editorial   201   11.6         4
Charles FarlowMedtronic     Editorial   201   11.6.1       7
Charles FarlowMedtronic     Technical   201   11.6.1       9
Charles FarlowMedtronic     Technical   202   11.6.1       1-2
Charles FarlowMedtronic     Technical   202   11.6.2       4-5
Charles FarlowMedtronic     Technical   202   11.7         12
Charles FarlowMedtronic     Technical   204   11.8.1       2
Charles FarlowMedtronic     Technical   205   11.8.2       4
Charles FarlowMedtronic     Technical   206   11.9.1       3-9
Charles FarlowMedtronic     Editorial   206   11.9.1       5-9
Charles FarlowMedtronic     Editorial   206   11.9.1       7-8
Charles FarlowMedtronic     Editorial   206   11.9.1       8
Charles FarlowMedtronic     Technical   206   11.9.1       8
Charles FarlowMedtronic     Technical   206   11.9.2       17-18
Charles FarlowMedtronic     Technical   207   11.9.2       3
Charles FarlowMedtronic     Technical   207   11.9.2       6-7
Charles FarlowMedtronic     Technical   207   11.9.3       11
Charles FarlowMedtronic     Technical   207   11.9.3       12-15
Chris Calvert Landis+Gyr    Technical   52    6.4.6.4      4-8
Chris Calvert Landis+Gyr    Technical   94    7.8.2.1.1    20-22

Chris Calvert Landis+Gyr    Technical 172     10.7.1       10-13
Ciaran        DecaWave
Connell       Limited       Technical 164     10           1

Daniel Popa    Itron, Inc   Technical   201   11.6         4
David Cypher   NIST         Technical   3     2            13
David Cypher   NIST         General     5     3
David Cypher   NIST         Technical   13    5.2          12
David Cypher   NIST         Technical   15    5.5          11
David Cypher   NIST         Editorial   16    5.5.1.1      9
David Cypher   NIST         Editorial   22    6.2.1.1.6    3
David Cypher   NIST         Editorial   22    6.2.1.1.6    4
David Cypher   NIST         Editorial   22    6.2.1.1.8    5
David Cypher   NIST         Technical   24    6.2.1.1.11   40
David Cypher   NIST         Technical   30    6.3.1.10.2   16
David Cypher   NIST         Technical   30    6.3.1.11     19
David Cypher   NIST         Technical   31    6.3.2        15
David Cypher   NIST         Technical   32    6.3.2.3.4    15
David Cypher   NIST         Editorial   34    6.3.2.6.2    28
David Cypher   NIST         Technical   36    6.3.3.2.1    15
David Cypher   NIST         Technical   36    6.3.3.2.2    19
David Cypher   NIST         Technical   37    6.3.4.4      18
David Cypher   NIST         Technical   38    6.3.5.4      26
David Cypher   NIST   Technical   41   6.3.6.8       12
David Cypher   NIST   Technical   43   6.3.7.10      18
David Cypher   NIST   Technical   44   6.3.7.11      2
David Cypher   NIST   Technical   44   6.3.7.18      18
David Cypher   NIST   Technical   45   6.3.8         1
David Cypher   NIST   Technical   47   6.3.11.4.2    8
David Cypher   NIST   Technical   47   6.3.11.4.3    14
David Cypher   NIST   Technical   47   6.3.11.4.3    14
David Cypher   NIST   Technical   47   6.3.11.4.4.   22
David Cypher   NIST   Technical   48   6.3.11.4.4    1
David Cypher   NIST   Editorial   48   6.3.11.5(b)   3
David Cypher   NIST   Editorial   48   6.3.11.5.1    10
David Cypher   NIST   Technical   48   6.3.11.5.1    11
David Cypher   NIST   Editorial   48   6.3.11.5.2    12
David Cypher   NIST   Technical   48   6.3.11.5.2    13
David Cypher   NIST   Editorial   48   6.3.11.5.3    15
David Cypher   NIST   Technical   48   6.3.11.5.3    19
David Cypher   NIST   Editorial   49   6.3.11.5.4    1
David Cypher   NIST   Editorial   49   6.3.11.5.5    9
David Cypher   NIST   Editorial   49   6.3.11.5.6    12
David Cypher   NIST   Editorial   49   6.3.11.5.4    2
David Cypher   NIST   Editorial   49   6.3.11.5.7    17
David Cypher   NIST   Technical   50   6.4.2         5
David Cypher   NIST   Technical   53   6.4.8         1
David Cypher   NIST   Technical   53   6.4.8         1
David Cypher   NIST   Technical   53   6.4.8.3       11
David Cypher   NIST   Technical   54   6.4.8.7       7
David Cypher   NIST   Technical   54   6.4.8.8       9
David Cypher   NIST   Technical   54   6.4.8.8       9
David Cypher   NIST   Technical   54   6.4.8.8A      10
David Cypher   NIST   Technical   56   6.6.1.12      14
David Cypher   NIST   Technical   58   6.7           2
David Cypher   NIST   Technical   64   6.7.8         14
David Cypher   NIST   Technical   64   6.7.10        21
David Cypher   NIST   Technical   66   6.7.11        5
David Cypher   NIST   Technical   67   6.7.15.1      26
David Cypher   NIST   Technical   69   7.1           15
David Cypher   NIST   Technical   71   7.2.3         1
David Cypher   NIST   Technical   72   7.2.6         9
David Cypher   NIST   Technical   72   7.2.7         11
David Cypher   NIST   Technical   73   7.2.7.2       5
David Cypher   NIST   Technical   73   7.2.7.2       6
David Cypher   NIST   Technical   73   7.2.7.2       8
David Cypher   NIST   Technical   75   7.2.9         11
David Cypher   NIST   Technical   76   7.3.1         15
David Cypher   NIST   Editorial   77   7.3.2         22
David Cypher   NIST   Editorial   78   7.4           32
David Cypher   NIST   Technical   79   7.4           19
David Cypher   NIST   Technical   82   7.5.2         26
David Cypher   NIST   Technical   94   7.8.2.1.1     20
David Cypher   NIST   Technical   95   7.8.2.1.2     18
David Cypher   NIST   Technical   97   7.8.2.1.4     3
David Cypher NIST          Technical   98    7.9         9
David Cypher NIST          Technical   105   7.11        8
David Cypher NIST          Technical   107   7.11.2      7
David Cypher NIST          Technical   107   7.11.2      10
David Cypher NIST          Technical   107   7.11.2      14
David Cypher NIST          Editorial   107   7.12        24
David Cypher NIST          Technical   107   7.12        26
David Cypher NIST          Technical   111   7.12.3      16
David Cypher NIST          Editorial   119   8           2
David Cypher NIST          Technical   141   9           2
David Cypher NIST          Editorial   209               5
David Cypher NIST          Technical   57    6.7         21
David Cypher NIST          Technical   59    6.7.2.1     18
David Cypher NIST          Editorial   59    6.7.2.2     19
David Cypher NIST          Editorial   60    6.7.2.3     19
David Cypher NIST          Technical   72    7.2.7       14
David Cypher NIST          Technical   76    7.3.1       29
David Cypher NIST          Technical   80    7.5.1       15
David Cypher NIST          Technical   81    7.5.1.1     26
David Cypher NIST          Technical   84    7.6.2       30
David Cypher NIST          Technical   92    7.8         32
David Cypher NIST          Technical   94    7.8.2.1.2   25
David Cypher NIST          Technical   96    7.8.2.1.4   10
David Cypher NIST          Technical   102   7.10        15
David Cypher NIST          Technical   121   8.1.2       9
David Cypher NIST          Technical   121   8.1.2       18
David Cypher NIST          Technical   121   8.1.2       31
David Cypher NIST          Technical   121   8.1.2       22
David Cypher NIST          Technical   121   8.1.2       24
David Cypher NIST          Technical   123   8.1.3       12
David Cypher NIST          Technical   124   8.1.3       7
David Cypher NIST          Technical   124   8.1.3       11
David Cypher NIST          Technical   124   8.1.3       20
David Cypher NIST          Technical   124   8.1.3       13
David Cypher NIST          Technical   125   8.1.3       15
David Cypher NIST          Technical   125   8.1.4       18
David Cypher NIST          Technical   125   8.1.4       29
David Cypher NIST          Technical   125   8.1.4       33
David Cypher NIST          Technical   125   8.1.4       35
David Cypher NIST          Technical   126   8.1.4       4
David Cypher NIST          Technical   126   8.1.4       19
David Cypher NIST          Technical   128   8.1.5       8
David Cypher NIST          Technical   128   8.1.5       19
David Cypher NIST          Technical   128   8.1.5       27
David Cypher NIST          Technical   132   8.2.1       1
David Cypher NIST          Technical   132   8.2.1       5
David Cypher NIST          Technical   132   8.2.1       7
David Cypher NIST          Editorial   134   8.3.1       29
David Cypher NIST          Editorial   134   8.3.1       30
David Cypher NIST          Technical   160   9.7.7       1
David Cypher NIST          Technical   201   11.6.1      8
             GE            Editorial
David Davenport Global Research        8     3           3
            GE             Editorial
David Davenport Global Research        11   4            18
            GE             Editorial
David Davenport Global Research        13   5.2          12
            GE             Editorial
David Davenport Global Research        14   5.4          23
            GE             Editorial
David Davenport Global Research        21   6.2.1.1.5    23
            GE             Editorial
David Davenport Global Research        22   6.2.1.1.6    3
            GE             Editorial
David Davenport Global Research        22   6.2.1.1.6    4
            GE             Editorial
David Davenport Global Research        24   6.2.1.1.11   40
            GE             Editorial
David Davenport Global Research        29   6.3.1.2      7

            GE             Editorial
David Davenport Global Research        30   6.3.1.10.1   13
            GE             Technical
David Davenport Global Research        30   6.3.1.10.1   14
            GE             Editorial
David Davenport Global Research        30   6.3.1.10.1   17
            GE             Editorial
David Davenport Global Research        30   6.3.1.11     20
            GE             Editorial
David Davenport Global Research        31   6.3.1.11     2
            GE             Editorial
David Davenport Global Research        31   6.3.1.12     20
            GE             Technical
David Davenport Global Research        37   6.3.4.4      22
            GE             Editorial
David Davenport Global Research        41   6.3.6.10     22
            GE             Technical
David Davenport Global Research        41   6.3.6.8      12

            GE             Editorial
David Davenport Global Research        44   6.3.7.18     18
            GE             Editorial
David Davenport Global Research        47   6.3.11.4.1   5
            GE             Editorial
David Davenport Global Research        47   6.3.11.4.2   8
            GE             Editorial
David Davenport Global Research        47   6.3.11.4.2   12
            GE             Technical
David Davenport Global Research        47   6.3.11.4.2   12
            GE             Editorial
David Davenport Global Research        47   6.3.11.4.2   9
            GE             Editorial
David Davenport Global Research        47   6.3.11.4.3   15
            GE             Technical
David Davenport Global Research        47   6.3.11.4.3   15
            GE             Editorial
David Davenport Global Research        48   6.3.11.4.4   1
            GE             Editorial
David Davenport Global Research        48   6.3.11.5.3   19
            GE             Technical
David Davenport Global Research        48   6.3.11.5.1   11
            GE             Editorial
David Davenport Global Research        49   6.3.11.5.4   2
            GE             Editorial
David Davenport Global Research        51   6.4.6        15
            GE             Technical
David Davenport Global Research        52   6.4.7        14
            GE             Technical
David Davenport Global Research        53   6.4.8        1
            GE             Editorial
David Davenport Global Research        53   6.4.8        1
            GE             Editorial
David Davenport Global Research        53   6.4.8.3      11
            GE             Editorial
David Davenport Global Research        54   6.4.8.6      4
            GE             Editorial
David Davenport Global Research        54   6.4.8.6      1
            GE             Technical
David Davenport Global Research        60   6.7.2.3      2
            GE             Technical
David Davenport Global Research        63   6.7.6        1
            GE             Editorial
David Davenport Global Research        64   6.7.10       21
            GE             Editorial
David Davenport Global Research        69   7.1          14
            GE             Editorial
David Davenport Global Research        69   7.1          15
            GE             Editorial
David Davenport Global Research        72   7.2.6        9
            GE             Editorial
David Davenport Global Research        72   7.2.7        11
            GE             Technical
David Davenport Global Research        78   7.4          27
            GE             Editorial
David Davenport Global Research        78   7.4          35
            GE             Editorial
David Davenport Global Research        79   7.4          15
            GE             Editorial
David Davenport Global Research        79   7.5          27
            GE             Editorial
David Davenport Global Research        79   7.5          28
            GE             Editorial
David Davenport Global Research        98   7.9          10
            GE             Editorial
David Davenport Global Research        98    7.9               11
            GE             Editorial
David Davenport Global Research        12    4                 4
            GE             Editorial
David Davenport Global Research        12    4                 4
            GE             Editorial
David Davenport Global Research        12    4                 8
            GE             Technical
David Davenport Global Research        98    7.9.1             24
            GE             Technical
David Davenport Global Research        100   7.9.2             21
            GE             Technical
David Davenport Global Research        99    7.9.2             13
            GE             Editorial
David Davenport Global Research        100   7.9.2             3
            GE             Editorial
David Davenport Global Research        100   7.9.2             7
            GE             Editorial
David Davenport Global Research        107   7.12              24
            GE             Editorial
David Davenport Global Research        107   7.12              26
            GE             Editorial
David Davenport Global Research        107   7.12              27
            GE             Editorial
David Davenport Global Research        107   7.12              28
            GE             Technical
David Davenport Global Research        108   7.12              1
            GE             Technical
David Davenport Global Research        110   7.12.2            19
            GE             Editorial
David Davenport Global Research        111   7.2.3             16
            GE             Technical
David Davenport Global Research        112   7.2.3             4
            GE             Technical
David Davenport Global Research        112   7.2.3             11
            GE             Technical
David Davenport Global Research        112   7.2.3             13
            GE             Technical
David Davenport Global Research        112   7.2.3             16
            GE             Technical
David Davenport Global Research        112   7.2.3             27
            GE             Technical
David Davenport Global Research        112   7.2.3.1           39
            GE             Technical
David Davenport Global Research        113   7.2.3.1           6
            GE             Technical
David Davenport Global Research        111   7.2.3             16
            GE             Editorial
David Davenport Global Research        113   7.12.2.3          34
            GE             Technical
David Davenport Global Research        114   7.12.4            4
            GE             Editorial
David Davenport Global Research        114   7.12.4            7
            GE             Technical
David Davenport Global Research        114   7.12.4            8
            GE             Technical
David Davenport Global Research        117   7.13.4            1
            GE             Editorial
David Davenport Global Research        134   8.3.1             30
            GE             Editorial
David Davenport Global Research        155   9.5.2             14
            GE             Technical
David Davenport Global Research        155   9.5.2             14
            GE             Technical
David Davenport Global Research        196   11.3              17
David Olson Landis+Gyr     Technical   52    6.4.6.4           4-8
David Olson Landis+Gyr     Technical   94    7.8.2.1.1         20-22

David Olson Landis+Gyr     Technical 172     10.7.1            10-13

David Tracey WiSAR Lab     Technical 13      5.2

David Tracey WiSAR Lab     Technical 15      Fig 4a            5

David Tracey WiSAR Lab     Technical 15      Fig 4b            5

David Tracey WiSAR Lab     Technical 17      5.6               36-37

David Tracey WiSAR Lab     Technical 20 (38) 6.2.1.1 (6.3.1)

David Tracey WiSAR Lab     Technical 21      6.2.1.1.5         18-19

David Tracey WiSAR Lab     Technical 29      6.3.1.3           10
David Tracey WiSAR Lab   Technical 29     6.3.1.3          10

David Tracey WiSAR Lab   Technical 31     6.3.2

David Tracey WiSAR Lab   Technical 32     6.3.2.3.2        8

David Tracey WiSAR Lab   Technical 38      6.3.5           12

David Tracey WiSAR Lab   Technical 39     6.3.6.3          17
                                                           Fig 24
                                                           (also fig
David Tracey WiSAR Lab   Technical 40     6.3.6.6          25)

                         Technical        6.3.6.7 (and
David Tracey WiSAR Lab   /Editorial 41    also 6.3.6.8)    7,8

David Tracey WiSAR Lab   Technical 42     6.3.7.0

David Tracey WiSAR Lab   Technical 42     Fig 25

David Tracey WiSAR Lab   Technical 46     Table 9

David Tracey WiSAR Lab   Technical 50     6.4.2

David Tracey WiSAR Lab   Technical 52     6.4.6.4

David Tracey WiSAR Lab   Technical 52     6.4.8

David Tracey WiSAR Lab   Technical 54     6.4.8.6

David Tracey WiSAR Lab   Technical 55     6.6.1.0

David Tracey WiSAR Lab   Technical 55     6.6.1.0

David Tracey WiSAR Lab   Technical 66     Table 15

David Tracey WiSAR Lab   Technical 62     6.7.6

David Tracey WiSAR Lab   Technical 85     7.6.2/Table 17

David Tracey WiSAR Lab   Technical 98     7.9

David Tracey WiSAR Lab   Technical 99/100 7.9              Fig 79/80

David Tracey WiSAR Lab   Technical 99/100 7.9              Fig 79/80

David Tracey WiSAR       Technical 102    7.9.3.2          Fig 81/82
                                   101/10 7.9.3.1 and
David Tracey WiSAR Lab   Technical 2      7.9.3.2          Fig 81/82

David Tracey WiSAR       Technical 103    7.9              16
David Tracey WiSAR             Technical 112     7.12.3.1

David Tracey WiSAR             Technical 116     7.13.2

David Tracey WiSAR Lab         Editorial   15    5.5           5

David Tracey WiSAR Lab         Editorial   22    6.2.1.1.6     3,4

David Tracey WiSAR Lab         Editorial   23    Table 3

David Tracey WiSAR Lab         Editorial   23    6.2.1.1.9

David Tracey WiSAR Lab         Editorial   24    6.2.1.1.11    41

David Tracey WiSAR Lab         Editorial   28    6.3.1

David Tracey WiSAR Lab         Editorial   40    6.3.6.6.3-6

David Tracey WiSAR Lab         Editorial   51    6.4.6

David Tracey WiSAR Lab         Editorial   53    6.4.8.5       3

David Tracey WiSAR Lab         Editorial   57    6.6.2.3

David Tracey WiSAR Lab         Editorial   89    7.6.1         19,20

David Tracey WiSAR Lab         Editorial   100   7.9 on

David Tracey WiSAR Lab         Editorial   100   7.9.2.0       5, 7, 16

David Tracey WiSAR Lab         Editorial   105   Fig 84

David Tracey   WiSAR Lab       Editorial 112    7.12.3.1
Didier Sagan   Zarlink         Technical     19 6.1                     2
Didier Sagan   Semiconductor
               Zarlink         Editorial     21 6.2.1.1.2               4
Didier Sagan   Semiconductor
               Zarlink         Editorial     21 6.2.1.1.3               9
Didier Sagan   Semiconductor
               Zarlink         Editorial     21 6.2.1.1.3              11
Didier Sagan   Semiconductor
               Zarlink         Technical     21 6.2.1.1.5              22
Didier Sagan   Semiconductor
               Zarlink         Editorial     22 6.2.1.1.6               6
Didier Sagan   Semiconductor
               Zarlink         Editorial     22 6.2.1.1.8              15
Didier Sagan   Semiconductor
               Zarlink         Editorial     23 6.2.1.1.9               5
Didier Sagan   Semiconductor
               Zarlink         Editorial     23 6.2.1.1.9               5
Didier Sagan   Semiconductor
               Zarlink         Editorial     23 6.2.1.1.9               5
Didier Sagan   Semiconductor
               Zarlink         Editorial     23 6.2.1.1.9               9
Didier Sagan   Semiconductor
               Zarlink         Editorial     23 6.2.1.1.9               9
Didier Sagan   Semiconductor
               Zarlink         Editorial     23 6.2.1.1.9              12
Didier Sagan   Semiconductor
               Zarlink         Editorial     42 6.3.7                   1
Didier Sagan   Semiconductor
               Zarlink         Technical     44 6.3.8                  21
               Semiconductor
Didier Sagan   Zarlink         Editorial   44   6.3.8     21
Didier Sagan   Semiconductor
               Zarlink         Technical   50   6.4.2.1    8
Didier Sagan   Semiconductor
               Zarlink         Technical   50   6.4.2.3   19
Didier Sagan   Semiconductor
               Zarlink         Technical   51   6.4.6     19
Didier Sagan   Semiconductor
               Zarlink         Editorial   51   6.4.6     19
Didier Sagan   Semiconductor
               Zarlink         Technical   52   6.4.6.3    2
Didier Sagan   Semiconductor
               Zarlink         Editorial   54   6.6.1     20
Didier Sagan   Semiconductor
               Zarlink         Editorial   55   6.6.1.3   11
Didier Sagan   Semiconductor
               Zarlink         Technical   55   6.6.1.4   14
Didier Sagan   Semiconductor
               Zarlink         Editorial   55   6.6.1.4   14
Didier Sagan   Semiconductor
               Zarlink         Technical   55   6.6.1.5   17
Didier Sagan   Semiconductor
               Zarlink         Technical   55   6.6.1.6   21
Didier Sagan   Semiconductor
               Zarlink         Editorial   55   6.6.1.6   21
Didier Sagan   Semiconductor
               Zarlink         Editorial   56   6.6.1.9    4
Didier Sagan   Semiconductor
               Zarlink         Editorial   56   6.6.1.9    4
Didier Sagan   Semiconductor
               Zarlink         Editorial   57   6.6.2.1    1
Didier Sagan   Semiconductor
               Zarlink         Editorial   58   6.7.1      3
Didier Sagan   Semiconductor
               Zarlink         Technical   59   6.7.2      4
Didier Sagan   Semiconductor
               Zarlink         Editorial   60   6.7.2.4    4
Didier Sagan   Semiconductor
               Zarlink         Technical   60   6.7.3     27
Didier Sagan   Semiconductor
               Zarlink         Technical   61   6.7.4      1
Didier Sagan   Semiconductor
               Zarlink         Technical   61   6.7.4      1
Didier Sagan   Semiconductor
               Zarlink         Technical   61   6.7.5      5
Didier Sagan   Semiconductor
               Zarlink         Editorial   70   7.2.1      1
Didier Sagan   Semiconductor
               Zarlink         Editorial   72   7.2.7     10
Didier Sagan   Semiconductor
               Zarlink         Editorial   72   7.2.7     19
Didier Sagan   Semiconductor
               Zarlink         Technical   72   7.2.7     19
Didier Sagan   Semiconductor
               Zarlink         Editorial   73   7.2.7.2    9
Didier Sagan   Semiconductor
               Zarlink         Editorial   73   7.2.7.2   14
Didier Sagan   Semiconductor
               Zarlink         Technical   73   7.2.7.3   17
Didier Sagan   Semiconductor
               Zarlink         Editorial   74   7.2.7.4   29
Didier Sagan   Semiconductor
               Zarlink         Technical   74   7.2.7.4   31
Didier Sagan   Semiconductor
               Zarlink         Editorial   75   7.2.7.4    2
Didier Sagan   Semiconductor
               Zarlink         Editorial   75   7.2.8      4
Didier Sagan   Semiconductor
               Zarlink         Editorial   75   7.2.9      9
Didier Sagan   Semiconductor
               Zarlink         Editorial   75   7.2.9     24
Didier Sagan   Semiconductor
               Zarlink         Editorial   75   7.2.9     24
Didier Sagan   Semiconductor
               Zarlink         Editorial   76   7.3.1     15
Didier Sagan   Semiconductor
               Zarlink         Technical   76   7.3.1     15
Didier Sagan   Semiconductor
               Zarlink         Technical   76   7.3.1     22
Didier Sagan   Semiconductor
               Zarlink         Technical   77   7.3.2     21
Didier Sagan   Semiconductor
               Zarlink         Technical   77   7.3.2     21
Didier Sagan   Semiconductor
               Zarlink         Editorial   77   7.3.2     21
Didier Sagan   Semiconductor
               Zarlink         Technical   77   7.3.2     22
               Semiconductor
Didier Sagan   Zarlink         Technical    78   7.3.3      3
Didier Sagan   Semiconductor
               Zarlink         Editorial    82   7.5.1.2    3
Didier Sagan   Semiconductor
               Zarlink         Technical    84   7.6.1     22
Didier Sagan   Semiconductor
               Zarlink         Technical    84   7.6.1     22
Didier Sagan   Semiconductor
               Zarlink         Technical    84   7.6.1     22
Didier Sagan   Semiconductor
               Zarlink         Technical    84   7.6.1     22
Didier Sagan   Semiconductor
               Zarlink         Technical    84   7.6.1     22
Didier Sagan   Semiconductor
               Zarlink         Technical    84   7.6.1     22
Didier Sagan   Semiconductor
               Zarlink         Editorial    84   7.6.1     22
Didier Sagan   Semiconductor
               Zarlink         Technical    89   7.7.2     14
Didier Sagan   Semiconductor
               Zarlink         Technical    91   7.7.2      7
Didier Sagan   Semiconductor
               Zarlink         Technical    98   7.9        7
Didier Sagan   Semiconductor
               Zarlink         Technical   107   7.12      23
Didier Sagan   Semiconductor
               Zarlink         Technical   107   7.12      23
Didier Sagan   Semiconductor
               Zarlink         Technical   108   7.12.      1
Didier Sagan   Semiconductor
               Zarlink         Technical   108   7.12.1     3
Didier Sagan   Semiconductor
               Zarlink         Technical   109   7.12.2    22
Didier Sagan   Semiconductor
               Zarlink         Technical   157   9.6.2      2
Didier Sagan   Semiconductor
               Zarlink         Technical   157   9.6.4     10
Didier Sagan   Semiconductor
               Zarlink         Technical   160   9.7.8     16
Didier Sagan   Semiconductor
               Zarlink         Technical   162   9.8.4      8
Didier Sagan   Semiconductor
               Zarlink         Technical   163   9.8.6      4
Didier Sagan   Semiconductor
               Zarlink         Technical   163   9.8.6     16
               Semiconductor
Dino Miniutti NICTA           Technical 149                 9
Dino Miniutti NICTA           Technical
              Sunrise Micro
Ed Callaway Devices           Editorial   10    4           25
              Sunrise Micro
Ed Callaway Devices           Editorial   13    5.2         14
              Sunrise Micro
Ed Callaway Devices           Editorial   13    5.2         17
              Sunrise Micro
Ed Callaway Devices           Editorial   10    4           1
              Sunrise Micro
Ed Callaway Devices           Technical 13      5           1
              Sunrise Micro
Ed Callaway Devices           Technical 19      6           1
              Sunrise Micro
Ed Callaway Devices           Technical 14      5.3         10
Emmanuel                      Technical 52      6.4.6.4     4-8
Monnerie      Landis+Gyr
Emmanuel                      Technical 94      7.8.2.1.1   20-22
Monnerie      Landis+Gyr
Emmanuel
Monnerie      Landis+Gyr      Technical   172   10.7.1      10-13
Gahng-Seop AhnCUNY            Technical   29    6.3.1.3     9
Gahng-Seop AhnCUNY            Technical   53    6.4.8.2     7
Gahng-Seop AhnCUNY            Technical   59    6.7.1.2     2
Gahng-Seop AhnCUNY            Technical   76    7.3.1       20
Gang Ding     Olympus         Editorial   94                20
Gang Ding     Olympus         Technical   94                20
Gang Ding     Olympus         Editorial   146               4
Gang Ding     Olympus         Editorial   156               13

                              Technical
Guido Dolmans olst Centre / IMEC-NL 23
            H                                               12

                              Technical
Guido Dolmans olst Centre / IMEC-NL 30
            H                                               15

                              Technical
Guido Dolmans olst Centre / IMEC-NL 64
            H                                               24

                              Technical
Guido Dolmans olst Centre / IMEC-NL 106
            H                                               7
                              Undefine
            H                 d
Guido Dolmans olst Centre / IMEC-NL

                              Technical
Guido Dolmans olst Centre / IMEC-NL 150
            H                                   9.1         7

                              Technical
Guido Dolmans olst Centre / IMEC-NL 169
            H                                   9.8.1       1

                              Technical
Guido Dolmans olst Centre / IMEC-NL 172
            H                                   10          14
                              General
Guido Dolmans olst Centre / IMEC-NL 172
            H                                   10.1.1      27
                              Undefine
                              d
Guido Dolmans olst Centre / IMEC-NL 172
            H                                   10.1.1        27

                              Technical
Guido Dolmans olst Centre / IMEC-NL 175
            H                                   10.5.2

            H                 Technical
Guido Dolmans olst Centre / IMEC-NL       177   10.5.5
            H                 General
Guido Dolmans olst Centre / IMEC-NL       178   10.6.1.1      17
            H                 General
Guido Dolmans olst Centre / IMEC-NL       179   10.7
            H                 General
Guido Dolmans olst Centre / IMEC-NL       183   10.11
                              Undefine
            H                 d
Guido Dolmans olst Centre / IMEC-NL       186   10.11.3
                              Undefine
            H                 d
Guido Dolmans olst Centre / IMEC-NL       188   10.11.4
            H                 General
Guido Dolmans olst Centre / IMEC-NL       179   10.7          8

                              Technical
Guido Dolmans olst Centre / IMEC-NL 179
            H                                   10.7          18

                              Technical
Guido Dolmans olst Centre / IMEC-NL 180
            H                                   10.7          7

                              Technical
Guido Dolmans olst Centre / IMEC-NL 180
            H                                   10.7          7

                              Technical
Guido Dolmans olst Centre / IMEC-NL 180
            H                                   10.7          7
                              Undefine
                              d
Guido Dolmans olst Centre / IMEC-NL 180
            H                                   10.7.1        11
                              General
Guido Dolmans olst Centre / IMEC-NL 183
            H                                   10.10.12

                              Technical
Guido Dolmans olst Centre / IMEC-NL 183
            H                                   10.10.12
                              General
Guido Dolmans olst Centre / IMEC-NL 182
            H                                   10.10.1
                              Editorial
Guido Dolmans olst Centre / IMEC-NL 183
            H                                   10.11.1

                              Technical
Guido Dolmans olst Centre / IMEC-NL 185
            H                                   10.11.2       13

                              Technical
Guido Dolmans olst Centre / IMEC-NL 186
            H                                   10.11.3.1

                              Technical
Guido Dolmans olst Centre / IMEC-NL 190
            H                                   10.13

                              Technical
Guido Dolmans olst Centre / IMEC-NL 192
            H                                  10.15.1         6
Hartman Van                   Technical 52     6.4.6.4         4-8
Wyk         Itron Inc
Hind Chebbo Fujitsu           Editorial     47 6.3.11.4.1             6
Hind Chebbo Fujitsu           Technical     85 7.6.2                  1
Hind Chebbo Fujitsu           Technical    107 7.12                  27
Hind Chebbo Fujitsu           Technical    112 7.12.3&7.12.3.1       11
Hind Chebbo Fujitsu           Technical     47 6.3.11.4.3
Hind Chebbo Fujitsu           Technical     48 6.3.11.5 (b)           7
Hind Chebbo Fujitsu           Editorial     48 6.3.11.5.3            19
Hind Chebbo Fujitsu           Editorial     48 6.3.11.4.4             1
Hind Chebbo Fujitsu           Technical    112 7.12.3                11
Hind Chebbo Fujitsu           Technical    112 7.12.3                24
Hind Chebbo Fujitsu           Technical    112 7.12.3                26
Hind Chebbo Fujitsu           Technical    115 7.13.2                28
Hind Chebbo Fujitsu           Editorial     53 6.4.8                  2
Hind Chebbo Fujitsu      Editorial      109   7.12.2                 24
Hind Chebbo Fujitsu      Technical      109   7.12.2                 25
Hind Chebbo Fujitsu      Editorial      189   10.16.3                 7
Hind Chebbo Fujitsu      Technical       86   7.6.2.1.1               3
Hind Chebbo Fujitsu      Technical       86   7.6.2.1.2       16-17
Hind Chebbo Fujitsu      Editorial       90   7.7.2           3 &8
Hind Chebbo Fujitsu      Editorial       91   7.7.2           9,13&17
Hind Chebbo Fujitsu      Technical       92   7.7.5           21-22
Hind Chebbo Fujitsu      Editorial       72   7.2.6                   9
Hind Chebbo Fujitsu      Technical       20   6.2.1.1                14
Hind Chebbo Fujitsu      Technical       43   6.3.7.3                 5
Hind Chebbo Fujitsu      Technical   99-101   7.9.1 & 7.9.2   6-12, Page 99-10121-23 & 1-4, Page 100-101
Hind Chebbo Fujitsu      Technical       58   6.7                     1
Hind Chebbo Fujitsu      Technical   46-47                    20 of
                                              6.3.11.3& 6.3.11.4.3 page 46 & 18 of page 47
Hind Chebbo Fujitsu      Technical      112                   19-20 &42-45
                                              7.12.3 & 7.12.3.1
Hind Chebbo Fujitsu      Technical       53   6.4.8                   2
Hind Chebbo Fujitsu      Technical      206   11.9.1                 12
             NICT
Hsia-Hsia (Grace) Sung   Editorial   22       6.2.1.1.6       4
             NICT
Hsia-Hsia (Grace) Sung   Editorial   29       6.3.1.4         16
             NICT
Hsia-Hsia (Grace) Sung   Editorial   29       6.3.1.6         28
             NICT
Hsia-Hsia (Grace) Sung   Editorial   34       6.3.2.6.2       28
             NICT
Hsia-Hsia (Grace) Sung   Technical   45       6.3.8           1
             NICT
Hsia-Hsia (Grace) Sung   Technical   45       6.3.8           1
             NICT
Hsia-Hsia (Grace) Sung   Editorial   83       7.5.2.1         30
             NICT
Hsia-Hsia (Grace) Sung   Editorial   86       7.6.2.1.1       1
             NICT
Hsia-Hsia (Grace) Sung   Editorial   87       7.6.2.2.1       19
             NICT
Hsia-Hsia (Grace) Sung   Editorial   91       7.7.2           9
             NICT
Hsia-Hsia (Grace) Sung   Editorial   93       7.8.1           11
             NICT
Hsia-Hsia (Grace) Sung   Technical   94       7.8.2.1.1       22
             NICT
Hsia-Hsia (Grace) Sung   Editorial   95       7.8.2.1.3       20
             NICT
Hsia-Hsia (Grace) Sung   Technical   96       7.8.2.1.4       16
             NICT
Hsia-Hsia (Grace) Sung   Technical   97       7.8.2.1.4       3
             NICT
Hsia-Hsia (Grace) Sung   Editorial   111      7.12.3          15
             NICT
Hsia-Hsia (Grace) Sung   Editorial   112      7.12.3          1
             NICT
Hsia-Hsia (Grace) Sung   Editorial   112      7.12.3          3
             NICT
Hsia-Hsia (Grace) Sung   Technical   112      7.12.3          4
             NICT
Hsia-Hsia (Grace) Sung   Technical   112      7.12.3          11
             NICT
Hsia-Hsia (Grace) Sung   Editorial   112      7.12.3          14
             NICT
Hsia-Hsia (Grace) Sung   Technical   112      7.12.3          19
             NICT
Hsia-Hsia (Grace) Sung   Editorial   113      7.12.3.1        14
             NICT
Hsia-Hsia (Grace) Sung   Editorial   114      7.12.4          16
             NICT
Hsia-Hsia (Grace) Sung   Technical   115      7.13.2          14
             NICT
Hsia-Hsia (Grace) Sung   Technical   115      7.13.2          33
             NICT
Hsia-Hsia (Grace) Sung   Editorial   117      7.13.4          1
             NICT
Hsia-Hsia (Grace) Sung   Technical   118      7.13.4          1
             NICT
Hsia-Hsia (Grace) Sung   Editorial   119      8               12
             NICT
Hsia-Hsia (Grace) Sung   Technical   189      10.16.3         10
Huan-Bang Li NICT        Editorial   12                       12
Huan-Bang Li NICT        Editorial   13       5.2             15
Huan-Bang Li NICT        Editorial   16       5.5.1.2         13-15
Huan-Bang Li NICT        Editorial   55       6.6             7 ++
Huan-Bang Li NICT        Editorial   109      Fig.87          1
Huan-Bang Li NICT       Editorial   109   Fig.88         16
Huan-Bang Li NICT       Technical   117   table 24       1
Huan-Bang Li NICT       Technical   118   table 25       1
Huan-Bang Li NICT       Technical   155   9.5.1          6
Huan-Bang Li NICT       Editorial   172   10.8           16-17
Huan-Bang Li NICT       Editorial   173   10.1           3-7
Huan-Bang Li NICT       Editorial   173   table 54, 55   8, 11
Huan-Bang Li NICT       Editorial   173   table 55       11
Huan-Bang Li NICT       Technical   182   table 61       11
Huan-Bang Li NICT       Editorial   195   11.1           6-7
Huan-Bang Li NICT       Technical   195   11.1           12
Huan-Bang Li NICT       Technical   196   11.2           17
Huan-Bang Li NICT       Technical         11
Ichirou IDA Fujitsu     Technical   30    6.3.1.10.1     14

Ichirou IDA   Fujitsu   Technical 46      6.3.11.3       20

Ichirou IDA   Fujitsu   Editorial 48      6.3.11.5(b)    3
Ichirou IDA   Fujitsu   Technical 74      7.2.7.4        21

Ichirou IDA   Fujitsu   Technical 85      7.6.2          1

Ichirou IDA   Fujitsu   Technical 109     7.12.1         8

Ichirou IDA   Fujitsu   Editorial   160   9.7.8          13 and
                                                         15
Ichirou IDA   Fujitsu   Editorial   113   7.12.3.1       2, 6, 8,
                                                         and 24
Igor Dotlic   NICT      Editorial   164   10.1.1.        27
Igor Dotlic   NICT      Editorial   164   10.2.          31-32
Igor Dotlic   NICT      Editorial   164   10.2.          35,1,2
Igor Dotlic   NICT      Editorial   165   10.2.          10, 11
Igor Dotlic   NICT      Editorial   165   10.3.          18
Igor Dotlic   NICT      Editorial   166   10.4.          Fig. 116
Igor Dotlic   NICT      Editorial   167   10.5.2.        2
Igor Dotlic   NICT      Editorial   169   10.5.5         2
Igor Dotlic   NICT      Editorial   169   10.5.5.        3,4,5
Igor Dotlic   NICT      Editorial   169   10.5.5.        6
Igor Dotlic   NICT      Editorial   169   10.5.5.        12
Igor Dotlic   NICT      Editorial   169   10.5.5         12
Igor Dotlic   NICT      Technical 169     10.6.          19

Igor Dotlic   NICT      Technical 170     10.6.1.        Table 52

Igor Dotlic   NICT      Technical 170     10.6.1.        Table 52
Igor Dotlic   NICT      Editorial   171   10.7.          4,5
Igor Dotlic   NICT      Editorial   172   10.7.          4,5
Igor Dotlic   NICT      Technical 172     10.7.          3,4,5,6.

Igor Dotlic   NICT      Technical 172     10.7.          7,8,9
Igor Dotlic   NICT         Editorial   172     10.9.            26
Igor Dotlic   NICT         Editorial   173     10.1             11
Igor Dotlic   NICT         Editorial   175     10.11.1.         19
Igor Dotlic   NICT         Editorial   175     10.11.1.1        23, 24
Igor Dotlic   NICT         Editorial   177     10.11.2          9
Igor Dotlic   NICT         Editorial   177     10.11.2          9
Igor Dotlic   NICT         Editorial   177     10.11.2          14
Igor Dotlic   NICT         Editorial   177     10.11.2          15
Igor Dotlic   NICT         Editorial   177     10.11.2          4
Igor Dotlic   NICT         Technical 177       10.11.2          14

Igor Dotlic   NICT         Technical 172       10.7.1           13
Igor Dotlic NICT           Editorial   177    10.11.2           13
Igor Dotlic NICT           Editorial   179    10.11.3.2         7
Igor Dotlic NICT           Editorial   179    10.11.3.2         8
Igor Dotlic NICT           Editorial   179    10.11.3.2         9
Igor Dotlic NICT           Editorial   180    10.11.3.2         3,4
Igor Dotlic NICT           Editorial   181    10.11.4.1         4
Igor Dotlic NICT           Editorial   181    10.11.4.2         7
Igor Dotlic NICT           Editorial   181    10.11.4.2         7
Igor Dotlic NICT           Editorial   181    10.11.4.2         13
Igor Dotlic NICT           Editorial   181    10.11.4.3         17
Igor Dotlic NICT           Editorial   183    10.14             1
Igor Dotlic NICT           Editorial   183    10.14             5
Igor Dotlic NICT           Editorial   186    10.15.2           3
Igor Dotlic NICT           Editorial   187    10.15.2           5
Igor Dotlic NICT           Editorial   187    10.15.3           6
Igor Dotlic NICT           Editorial   187    10.15.3           6
Jaehwan Kim ETRI           Technical   168    10.5.4            16
Jaehwan Kim ETRI           Technical   168    10.5.4            19
Jaehwan Kim ETRI           Technical   173    10.10             11
Jaehwan Kim ETRI           Technical   169    10.5.5
Jaehwan Kim ETRI           Editorial   178    10.11.3           4
Jaehwan Kim ETRI           Technical          9.1.4, 157
                                       143,148, 155, 9.3.1.1, 9.5.2, 9.7.1
Jaehwan Kim ETRI           Technical   98                       6
Jaehwan Kim ETRI           Technical   93                       6
Jaehwan Kim ETRI           Technical   94
Jaehwan Kim ETRI           Technical   95     7.8.2.1.3
Jaehwan Kim ETRI           Technical   96     7.8.2.1.4
Jaehwan Kim ETRI           Technical   92     7.8
Jaehwan Kim ETRI           Technical   92     7.8
Jaehwan Kim ETRI           Technical
Jae-Seung Son amsung Electronics
            S              editorial   148     9.3.2            16
Jae-Seung Son amsung Electronics
            S              editorial   149     9.3.3            6
Jae-Seung Son amsung Electronics
            S              editorial   151     9.4.2            20
            S              Technical
Jae-Seung Son amsung Electronics       94-96   7.8.2.1.2
James Gilb SiBEAM          Editorial   1       1                20
James Gilb SiBEAM          Editorial   1       1                24
James Gilb SiBEAM          Editorial   3       2                6
James Gilb SiBEAM          Editorial   5       3                1
James Gilb SiBEAM          Technical   6       3                5
James Gilb SiBEAM             Technical   6       3            40
James Gilb SiBEAM             Technical   10      4            4
James Gilb SiBEAM             Technical   15      5            15
James Gilb SiBEAM             Editorial   20      6.2.1.1.1    16
James Gilb SiBEAM             Technical   20      6.2          4
James Gilb SiBEAM             Editorial   24      6.2.1.1.11   40
James Gilb SiBEAM             Editorial   27      6.2.2        12
James Gilb SiBEAM             Editorial   37      6.3.4.3      9
James Gilb SiBEAM             Editorial   42      6.3.7.3      1
James Gilb SiBEAM             Editorial   46      6.3.10.2     3
James Gilb SiBEAM             Editorial   47      6.3.11.4.2   8
James Gilb SiBEAM             Editorial   48      6.3.11.5     3
James Gilb SiBEAM             Editorial   47      6.3.11.4.1   1
James Gilb SiBEAM             Technical   49      6.3.11.5.5   10
James Gilb SiBEAM             Editorial   52      6.4.8        1
James Gilb SiBEAM             Editorial   53      6.4.8.6      4
James Gilb SiBEAM             Editorial   59      6.7.2        8
James Gilb SiBEAM             Editorial   69      7.1          2
James Gilb SiBEAM             Editorial   72      7.2.6        9
James Gilb SiBEAM             Editorial   74      7.2.7.4      2
James Gilb SiBEAM             Technical   75      7.3          26
James Gilb SiBEAM             Editorial   82      7.5.2        24
James Gilb SiBEAM             Editorial   85      7.6.2        1
James Gilb SiBEAM             Editorial   86      7.6.2.1.1    1
James Gilb SiBEAM             Editorial   94      7.8.2.1.1    20
James Gilb SiBEAM             Editorial   96      7.8.2.1.3    4
James Gilb SiBEAM             Editorial   106     7.11.1       2
James Gilb SiBEAM             Editorial   107     7.11.2       7
James Gilb SiBEAM             Technical   108     7.12         1
James Gilb SiBEAM             Technical   108     7.12         1
             Elster Solutions Technical
Jeff McCullough                           9       3            17-20
             Elster Solutions Editorial
Jeff McCullough                           22      6.2.1.1.6    3
             Elster Solutions Editorial
Jeff McCullough                           22      6.2.1.1.6    4
             Elster Solutions Technical
Jeff McCullough                           51-52   6.4
             Elster Solutions Technical
Jeff McCullough                           164     10.1.1       26
Jin-Meng Ho Texas Instruments Editorial   1       1
Jin-Meng Ho Texas Instruments Editorial   3                    6-11
Jin-Meng Ho Texas Instruments Editorial   7       3            37
Jin-Meng Ho Texas Instruments Editorial   13      5
Jin-Meng Ho Texas Instruments Editorial   16      5.5.1.2      14-15
Jin-Meng Ho Texas Instruments Editorial   16      5.5.1.3      23-24
Jin-Meng Ho Texas Instruments Editorial   16      5.5.1.4      32
Jin-Meng Ho Texas Instruments Editorial   19      6
Jin-Meng Ho Texas Instruments Editorial   21      6.2.1.1.4    15-18
Jin-Meng Ho Texas Instruments Editorial   22      6.2.1.1.6    4
Jin-Meng Ho Texas Instruments Editorial   22      6.2.1.1.8    15
Jin-Meng Ho Texas Instruments Editorial   22      6.2.1.1.8    15
Jin-Meng Ho Texas Instruments Editorial   22      6.2.1.1.8    15
Jin-Meng Ho Texas Instruments Technical   22      6.2.1.1.8    15
Jin-Meng Ho Texas Instruments Editorial   23      6.2.1.1.10   35
Jin-Meng Ho Texas Instruments Editorial   24      6.2.1.1.11   40
Jin-Meng Ho Texas Instruments Technical   25      6.2.1.1.12   12
Jin-Meng Ho                 Technical
              Texas Instruments         25      6.2.1.1.12    14-24
Jin-Meng Ho                 Technical
              Texas Instruments         26      6.2.1.1.12    3
Jin-Meng Ho                 Editorial
              Texas Instruments         26      6.2.2         15
Jin-Meng Ho                 Editorial
              Texas Instruments         27      6.2.2.2       15
Jin-Meng Ho                 Editorial
              Texas Instruments         27      6.2.2.2       17
Jin-Meng Ho                 Editorial
              Texas Instruments         29      6.3.1.4       16
Jin-Meng Ho                 Editorial
              Texas Instruments         29      6.3.1.6       28
Jin-Meng Ho                 Editorial
              Texas Instruments         32      6.3.2.3       1-9
Jin-Meng Ho                 Editorial
              Texas Instruments         32      6.3.2.3.1     6
Jin-Meng Ho                 Editorial
              Texas Instruments         32      6.3.2.3.4     15
Jin-Meng Ho                 Editorial
              Texas Instruments         43      6.3.7.3       1
Jin-Meng Ho                 Technical
              Texas Instruments         45      6.3.8         1-2
Jin-Meng Ho                 Editorial
              Texas Instruments         46      6.3.11.3      20
Jin-Meng Ho                 Technical
              Texas Instruments         46      6.3.11.3      20
Jin-Meng Ho                 Editorial
              Texas Instruments         47      6.3.11.4.1    1-22
Jin-Meng Ho                 Technical
              Texas Instruments         47      6.3.11.4.1    1
Jin-Meng Ho                 Technical
              Texas Instruments         47      6.3.11.4.1    2-6
Jin-Meng Ho                 Technical
              Texas Instruments         47      6.3.11.4.1    1-22
Jin-Meng Ho                 Technical
              Texas Instruments         48      6.3.11.5(b)   3-20
Jin-Meng Ho                 Technical
              Texas Instruments         49      6.3.11.5.4    1-16
Jin-Meng Ho                 Technical
              Texas Instruments         49      6.3.11.5.4    17
Jin-Meng Ho                 Editorial
              Texas Instruments         49      6.3.11.5.4    2
Jin-Meng Ho                 Technical
              Texas Instruments         52      6.4.6.4       5
Jin-Meng Ho                 Technical
              Texas Instruments         52      6.4.6.4       4-8
Jin-Meng Ho                 Technical
              Texas Instruments         52-53   6.4.8
Jin-Meng Ho                 Editorial
              Texas Instruments         57      6.6.2.3       11
Jin-Meng Ho                 Editorial
              Texas Instruments         57      6.6.2.3       11
Jin-Meng Ho                 Editorial
              Texas Instruments         57      6.6.2.3       13
Jin-Meng Ho                 Editorial
              Texas Instruments         58      6.7.1         5
Jin-Meng Ho                 Technical
              Texas Instruments         58      6.7.1         6
Jin-Meng Ho                 Editorial
              Texas Instruments         58      6.7.1.1       10-11
Jin-Meng Ho                 Editorial
              Texas Instruments         59      6.7.1.2       3
Jin-Meng Ho                 Technical
              Texas Instruments         59
Jin-Meng Ho                 Editorial
              Texas Instruments         59      6.7.2         13
Jin-Meng Ho                 Editorial
              Texas Instruments         61      6.7.5         15
Jin-Meng Ho                 Technical
              Texas Instruments         66      6.7.11        5
Jin-Meng Ho                 Technical
              Texas Instruments         66      6.7.11        8-9
Jin-Meng Ho                 Technical
              Texas Instruments         72      7.2.7         15
Jin-Meng Ho                 Editorial
              Texas Instruments         74      7.2.7.4       21
Jin-Meng Ho                 Editorial
              Texas Instruments         74      7.2.7.4       23-24
Jin-Meng Ho                 Editorial
              Texas Instruments         75      7.2.7.4       1-2
Jin-Meng Ho                 Technical
              Texas Instruments         77      7.3.1         76
Jin-Meng Ho                 Editorial
              Texas Instruments         78      7.4           28
Jin-Meng Ho                 Editorial
              Texas Instruments         78      7.4           32
Jin-Meng Ho                 Editorial
              Texas Instruments         78      7.4           36
Jin-Meng Ho                 Technical
              Texas Instruments         79      7.4           1-2
Jin-Meng Ho                 Editorial
              Texas Instruments         83      7.5.2.1       30
Jin-Meng Ho                 Editorial
              Texas Instruments         85      7.6.2         1
Jin-Meng Ho                 Editorial
              Texas Instruments         85      7.6.2         1
Jin-Meng Ho                 Editorial
              Texas Instruments         86      7.6.2.1.1     1
Jin-Meng Ho                 Editorial
              Texas Instruments         87      7.6.2.2.1     17
Jin-Meng Ho                 Editorial
              Texas Instruments         89      7.7.1         20-21
Jin-Meng Ho                 Editorial
              Texas Instruments         89    7.7.1       22
Jin-Meng Ho                 Editorial
              Texas Instruments         91    7.7.2       9-17
Jin-Meng Ho                 Editorial
              Texas Instruments         92    7.7.5       25
Jin-Meng Ho                 Technical
              Texas Instruments         94    7.8.2.1.1   20-22
Jin-Meng Ho                 Technical
              Texas Instruments         94    7.8.2.1.2   24-28
Jin-Meng Ho                 Technical
              Texas Instruments         95    7.8.2.1.2   1-4
Jin-Meng Ho                 Technical
              Texas Instruments         95    7.8.2.1.2   5-19
Jin-Meng Ho                 Editorial
              Texas Instruments         95    7.8.2.1.3   21
Jin-Meng Ho                 Editorial
              Texas Instruments         95    7.8.2.1.3   21
Jin-Meng Ho                 Editorial
              Texas Instruments         95    7.8.2.1.3   22
Jin-Meng Ho                 Editorial
              Texas Instruments         95    7.8.2.1.3   27
Jin-Meng Ho                 Technical
              Texas Instruments         95    7.8.2.1.3   28
Jin-Meng Ho                 Technical
              Texas Instruments         96    7.8.2.1.3   1
Jin-Meng Ho                 Technical
              Texas Instruments         96    7.8.2.1.4   9
Jin-Meng Ho                 Technical
              Texas Instruments         96    7.8.2.1.4   9-29
Jin-Meng Ho                 Editorial
              Texas Instruments         97    7.8.3       17
Jin-Meng Ho                 Editorial
              Texas Instruments         97    7.8.3       18-19
Jin-Meng Ho                 Editorial
              Texas Instruments         98    7.8.3       6
Jin-Meng Ho                 Technical
              Texas Instruments         98    7.9         7
Jin-Meng Ho                 Editorial
              Texas Instruments         107   7.12        26-30
Jin-Meng Ho                 Technical
              Texas Instruments         111   7.12.3      15
Jin-Meng Ho                 Editorial
              Texas Instruments         111   7.12.3      15
Jin-Meng Ho                 Technical
              Texas Instruments         111   7.12.3      16-17
Jin-Meng Ho                 Technical
              Texas Instruments         112   7.12.3      1-10
Jin-Meng Ho                 Technical
              Texas Instruments         112   7.12.3      11-25
Jin-Meng Ho                 Technical
              Texas Instruments         112   7.12.3      26-33
Jin-Meng Ho                 Technical
              Texas Instruments         112   7.12.3      34-37
Jin-Meng Ho                 Technical
              Texas Instruments         112   7.12.3.1    38
Jin-Meng Ho                 Technical
              Texas Instruments         112   7.12.3.1    39-40
Jin-Meng Ho                 Technical
              Texas Instruments         112   7.12.3.1    41-45
Jin-Meng Ho                 Technical
              Texas Instruments         113   7.12.3.1    1-17
Jin-Meng Ho                 Technical
              Texas Instruments         113   7.12.3.2    18-31
Jin-Meng Ho                 Technical
              Texas Instruments         113   7.12.3.3    32
Jin-Meng Ho                 Technical
              Texas Instruments         113   7.12.3.3    33-44
Jin-Meng Ho                 Technical
              Texas Instruments         114   7.12.3.3    1-2
Jin-Meng Ho                 Technical
              Texas Instruments         114   7.12.4      3
Jin-Meng Ho                 Technical
              Texas Instruments         114   7.12.4      4-24
Jin-Meng Ho                 Technical
              Texas Instruments         114   7.12.4      25
Jin-Meng Ho                 Technical
              Texas Instruments         115   7.13.1      4
Jin-Meng Ho                 Technical
              Texas Instruments         115   7.13.2      6-39
Jin-Meng Ho                 Technical
              Texas Instruments         117   7.13.4      1
Jin-Meng Ho                 Technical
              Texas Instruments         117   7.13.4      1
Jin-Meng Ho                 Technical
              Texas Instruments         117   7.13.4      1
Jin-Meng Ho                 Technical
              Texas Instruments         117   7.13.4      1
Jin-Meng Ho                 Editorial
              Texas Instruments         117   7.13.4      1
Jin-Meng Ho                 Technical
              Texas Instruments         117   7.13.4      1
Jin-Meng Ho                 Editorial
              Texas Instruments         118   7.13.4      1
Jin-Meng Ho                 Editorial
              Texas Instruments         118   7.13.4      1
Jin-Meng Ho                 Technical
              Texas Instruments         118   7.13.4      1
Jin-Meng Ho                 Technical
              Texas Instruments         118   7.13.4      1
                          Editorial
Jin-Meng Ho Texas Instruments         119   8           12


                          Editorial
Jin-Meng Ho Texas Instruments         119   8.1         17

                          Editorial
Jin-Meng Ho Texas Instruments         119   8


                          Editorial
Jin-Meng Ho Texas Instruments         121   8.1.2       29-30


                          Editorial
Jin-Meng Ho Texas Instruments         124   8.1.3       18-19


                          Editorial
Jin-Meng Ho Texas Instruments         124   8.1.4       17-18


                          Editorial
Jin-Meng Ho Texas Instruments         126   8.1.4       12
                          Editorial
Jin-Meng Ho Texas Instruments         129   8.1.5       22
                          Editorial
Jin-Meng Ho Texas Instruments         134   8.3.1       11




                          Editorial
Jin-Meng Ho Texas Instruments         134   8.3.1       12-22


                          Editorial
Jin-Meng Ho Texas Instruments         156   9.6.1       14-17


                          Editorial
Jin-Meng Ho Texas Instruments               9, 10, 11




                          Editorial 164
Jin-Meng Ho Texas Instruments               10          14
                          Technical 165
Jin-Meng Ho Texas Instruments               10.2        5
                          Technical 165
Jin-Meng Ho Texas Instruments               10.3       17-22



                          Technical 165
Jin-Meng Ho Texas Instruments               10.3       23-29




                          Technical 165
Jin-Meng Ho Texas Instruments               10.5       16-17

                          Technical 166
Jin-Meng Ho Texas Instruments               10.4       4

                          Technical 166
Jin-Meng Ho Texas Instruments               10.5.1     21

                          Technical 166
Jin-Meng Ho Texas Instruments               10.5.1     21-23




                          Technical 170
Jin-Meng Ho Texas Instruments               10.6.1     1-2



                          Technical 170
Jin-Meng Ho Texas Instruments               10.6.1.3   21



                          Technical 170
Jin-Meng Ho Texas Instruments               10.6.1.3   22




                          Technical 171
Jin-Meng Ho Texas Instruments               10.7       9-10




                          Technical 171
Jin-Meng Ho Texas Instruments               10.7       11-12


                          Editorial
Jin-Meng Ho Texas Instruments         188   10.16      20

                          Editorial
Jin-Meng Ho Texas Instruments         188   10.16.1    34

                          Editorial
Jin-Meng Ho Texas Instruments         189   10.16.2    1
                          Technical 189
Jin-Meng Ho Texas Instruments               10.16.2   1




                          Technical 189
Jin-Meng Ho Texas Instruments               10.16.3   5


                          Editorial 189
Jin-Meng Ho Texas Instruments               10.16.3   6-7
                          Technical 189
Jin-Meng Ho Texas Instruments               10.16.3


                          Technical 189
Jin-Meng Ho Texas Instruments               10.16.3   10-11




                          Technical 190
Jin-Meng Ho Texas Instruments               10.16.3   1




                          Technical 195
Jin-Meng Ho Texas Instruments               11.2      21-23



            Siemens
Joachim W. Walewski AG    Technical PDF 2 Abstract    6

            Siemens
Joachim W. Walewski AG    Editorial   PDF 20 4        1
            Siemens
Joachim W. Walewski AG    Editorial   PDF 20 4        1


            Siemens
Joachim W. Walewski AG    Technical PDF 65 6.6.2.3    11


            Siemens
Joachim W. Walewski AG    Editorial   PDF 149         20



            Siemens
Joachim W. Walewski AG    Technical PDF 155           18--19
            Siemens
Joachim W. Walewski AG      Technical   PDF 178           1
            Siemens
Joachim W. Walewski AG      Editorial         10.14
                                        PDF 191           3
            Siemens
Joachim W. Walewski AG      Editorial         10.15.1
                                        PDF 192           7
            Siemens
Joachim W. Walewski AG      Technical         10.15.1
                                        PDF 192           7

John Buffington
              Itron Inc.    Technical 200      11.6       9

              Itron Inc.
John Buffington             Technical   201    11.6       4
June Chul Roh               Editorial
              Texas Instruments         141               27
June Chul Roh               Editorial
              Texas Instruments         146               4
June Chul Roh               Editorial
              Texas Instruments         148               13,14
June Chul Roh               Editorial
              Texas Instruments         152    9.4.2      2
June Chul Roh               Editorial
              Texas Instruments         153    9.4.5      7-15
June Chul Roh               Editorial
              Texas Instruments         160    9.8.1      20
June Chul Roh               Editorial
              Texas Instruments         162    9.8.4      8
June Chul Roh               Editorial
              Texas Instruments         164    10         7-8
June Chul Roh               Editorial
              Texas Instruments         164    10         9
June Chul Roh               Technical
              Texas Instruments         164    10         13-14
June Chul Roh               Technical
              Texas Instruments         164    10.1       15-24
June Chul Roh               Technical
              Texas Instruments         164    10.1       24
June Chul Roh               Technical
              Texas Instruments         164    10.1.1     26-27
June Chul Roh               Editorial
              Texas Instruments         164    10.2       30
June Chul Roh               Editorial
              Texas Instruments         164    10.2       30-31
June Chul Roh               Editorial
              Texas Instruments         165    10.2       8-9
June Chul Roh               Technical
              Texas Instruments         165    10.2       11-13
June Chul Roh               Technical
              Texas Instruments         165    10.2       14-15
June Chul Roh               Technical
              Texas Instruments         165    10.3       17-22
June Chul Roh               Editorial
              Texas Instruments         166    10.4       1
June Chul Roh               Technical
              Texas Instruments         166    10.4       1
June Chul Roh               Editorial
              Texas Instruments         166    10.4       6
June Chul Roh               Editorial
              Texas Instruments         166    10.4       7
June Chul Roh               Editorial
              Texas Instruments         166    10.4       10
June Chul Roh               Editorial
              Texas Instruments         166    10.5       17
June Chul Roh               Editorial
              Texas Instruments         166    10.5.1     21
June Chul Roh               Editorial
              Texas Instruments         166    10.5.1     21
June Chul Roh               Editorial
              Texas Instruments         166    10.5.1     23
June Chul Roh               Editorial
              Texas Instruments         167    10.5.2     2-3
June Chul Roh               Editorial
              Texas Instruments         167    10.5.2     8
June Chul Roh               Technical
              Texas Instruments         167    10.5.2     9-10
June Chul Roh               Technical
              Texas Instruments         167    10.5.2     1-21
June Chul Roh               Editorial
              Texas Instruments         168    10.5.3     6-8
June Chul Roh               Editorial
              Texas Instruments         168    10.5.4     21
June Chul Roh               Editorial
              Texas Instruments         169    10.5.5     3-4
June Chul Roh               Technical
              Texas Instruments         169    10.5.5     7
June Chul Roh               Technical
              Texas Instruments         169-17010.6
June Chul Roh               Editorial
              Texas Instruments         169-17010.6
June Chul Roh               Editorial
              Texas Instruments         169    10.6       21
June Chul Roh               Editorial
              Texas Instruments         170    10.6.1.2   10
June Chul Roh               Editorial
              Texas Instruments         170    10.6.1.4   13-15
June Chul Roh              Editorial
             Texas Instruments         170    10.6.2.1    17
June Chul Roh              Editorial
             Texas Instruments         170    10.6.2.2    22-25
June Chul Roh              Editorial
             Texas Instruments         171    10.7        2-5
June Chul Roh              Technical
             Texas Instruments         171    10.7        6-10
June Chul Roh              Editorial
             Texas Instruments         171    10.7        15
June Chul Roh              Technical
             Texas Instruments         171    10.7        17
June Chul Roh              Editorial
             Texas Instruments         171    10.7        18
June Chul Roh              Editorial
             Texas Instruments         171    10.7
June Chul Roh              Editorial
             Texas Instruments         172    10.7        8
June Chul Roh              Technical
             Texas Instruments         172    10.7.1      10-13
June Chul Roh              Editorial
             Texas Instruments         172    10.9        26
June Chul Roh              Technical
             Texas Instruments         173    10.10       8-9
June Chul Roh              Technical
             Texas Instruments         173    10.10       11-12
June Chul Roh              Editorial
             Texas Instruments         173    10.10       9
June Chul Roh              Editorial
             Texas Instruments         173    10.10       12
June Chul Roh              Editorial
             Texas Instruments         173    10.10       9
June Chul Roh              Editorial
             Texas Instruments         173    10.10       12
June Chul Roh              Editorial
             Texas Instruments         173    10.10       12
June Chul Roh              Editorial
             Texas Instruments         174    10.10.3     4-5
June Chul Roh              Editorial
             Texas Instruments         174    10.10.5     9-10
June Chul Roh              Editorial
             Texas Instruments         174    10.10.7     13-14
June Chul Roh              Editorial
             Texas Instruments         174    10.10.10    20
June Chul Roh              Technical
             Texas Instruments         175    10.10.11    1-3
June Chul Roh              Editorial
             Texas Instruments         175    10.10.12    5
June Chul Roh              Technical
             Texas Instruments         175    10.11.1     14-20
June Chul Roh              Technical
             Texas Instruments         175    10.11.1     14-20
June Chul Roh              Editorial
             Texas Instruments         176    10.11.1     19-21
June Chul Roh              Technical
             Texas Instruments         177    10.11.2     12-15
June Chul Roh              Editorial
             Texas Instruments         177    10.11.2     6
June Chul Roh              Editorial
             Texas Instruments         177    10.11.2     9
June Chul Roh              Technical
             Texas Instruments         177    10.11.2     1-18
June Chul Roh              Technical
             Texas Instruments         178-18010.11.3
June Chul Roh              Editorial
             Texas Instruments         178    10.11.3     5
June Chul Roh              Editorial
             Texas Instruments         179    10.11.3.2   4-6
June Chul Roh              Technical
             Texas Instruments         179    10.11.3.2   7
June Chul Roh              Technical
             Texas Instruments         179    10.11.3.2   8
June Chul Roh              Editorial
             Texas Instruments         180    10.11.3.2   1
June Chul Roh              Editorial
             Texas Instruments         180    10.11.3.3   5-9
June Chul Roh              Editorial
             Texas Instruments         180    10.11.4     12
June Chul Roh              Editorial
             Texas Instruments         181    10.11.4     1
June Chul Roh              Technical
             Texas Instruments         181    10.11.4     7-9
June Chul Roh              Editorial
             Texas Instruments         181    10.11.4     10
June Chul Roh              Technical
             Texas Instruments         181-18210.11.4.3
June Chul Roh              Editorial
             Texas Instruments         182    10.12       11
June Chul Roh              Technical
             Texas Instruments         182    10.15.1     5-6
June Chul Roh              Editorial
             Texas Instruments         182    10.15.1     7-9
June Chul Roh              Technical
             Texas Instruments         187-18810.15.3
June Chul Roh              Technical
             Texas Instruments         188    10.16       20-33
June Chul Roh              Editorial
             Texas Instruments         188    10.16.1     37
June Chul Roh              Technical
             Texas Instruments         189    10.16.2     1-3
June Chul Roh              Editorial
             Texas Instruments         189    10.16.3     6-7
June Chul Roh              Technical
             Texas Instruments         189    10.16.3     10-11
June Chul Roh              Editorial
             Texas Instruments         190    10.16.3
June Chul Roh              Editorial
             Texas Instruments         190    10.17     7
June Chul Roh              Editorial
             Texas Instruments         192    10.17     1-2
June Chul Roh              Editorial
             Texas Instruments         192    10.17.4   16
June Chul Roh              Editorial
             Texas Instruments         194    10.17.5   1-12
June Chul Roh              Technical
             Texas Instruments         194    10.18     12-15
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
                                       195-
June Chul Roh              Technical
             Texas Instruments         208    11
June Chul Roh              Editorial
             Texas Instruments         195    11.1      4
June Chul Roh              Editorial
             Texas Instruments         195    11.1      8-11

June Chul Roh              Technical
             Texas Instruments         195    11.1      12
June Chul Roh              Editorial
             Texas Instruments         195    11.2      16
June Chul Roh              Editorial
             Texas Instruments         195    11.2      16-17
June Chul Roh              Editorial
             Texas Instruments         195    11.2      20
June Chul Roh              Editorial
             Texas Instruments         196    11.3      3
June Chul Roh              Editorial
             Texas Instruments         196    11.3      3-4

June Chul Roh              Technical 197
             Texas Instruments                11.4      7

June Chul Roh              Technical 197
             Texas Instruments                11.4      2-6
June Chul Roh              Editorial 197
             Texas Instruments                11.4      2-6
                                     198-
June Chul Roh              Editorial 199
             Texas Instruments                11.4      6-8,1-3

June Chul Roh              Technical 199
             Texas Instruments                11.5      14

June Chul Roh              Technical 199
             Texas Instruments                11.5      18-19
June Chul Roh              Editorial 199
             Texas Instruments                11.5      19

June Chul Roh              Technical 200
             Texas Instruments                11.6      9
June Chul Roh              Technical 201
             Texas Instruments              11.6     1

June Chul Roh              Technical 201
             Texas Instruments              11.6     4

June Chul Roh              Technical 201
             Texas Instruments              11.6     4
June Chul Roh              Editorial 201
             Texas Instruments              11.6     4
June Chul Roh              Editorial 201
             Texas Instruments              11.6     4

June Chul Roh              Technical 201
             Texas Instruments              11.6     4

June Chul Roh              Technical 201
             Texas Instruments              11.6     4

June Chul Roh              Technical 201
             Texas Instruments              11.6     4

June Chul Roh              Technical 201
             Texas Instruments              11.6     4

June Chul Roh              Technical 201
             Texas Instruments              11.6.1   7
June Chul Roh              Editorial 201
             Texas Instruments              11.6.1   7

June Chul Roh              Technical 201
             Texas Instruments              11.6.1   7-10

June Chul Roh              Technical 202
             Texas Instruments              11.6.1   1-2
                                     201-
June Chul Roh              Technical 202
             Texas Instruments              11.6.1   7-10,1-2

June Chul Roh              Technical 202
             Texas Instruments              11.6.2   4

June Chul Roh              Technical 202
             Texas Instruments              11.6.2   4

June Chul Roh              Technical 202
             Texas Instruments              11.6.2   3-7

June Chul Roh              Technical 202
             Texas Instruments              11.7     11

June Chul Roh              Technical 202
             Texas Instruments              11.7     16

June Chul Roh              Technical 203
             Texas Instruments              11.7     5

June Chul Roh              Technical 203
             Texas Instruments              11.8.1   9

June Chul Roh              Technical 203
             Texas Instruments              11.8.1   11

June Chul Roh              Technical 204
             Texas Instruments              11.8.1   4

June Chul Roh              Technical 204
             Texas Instruments              11.8.1   1

June Chul Roh              Technical 204
             Texas Instruments              11.81    9-10

June Chul Roh              Technical 205
             Texas Instruments              11.8.2   5
June Chul Roh              Editorial 205
             Texas Instruments              11.8.2   13

June Chul Roh              Technical 205
             Texas Instruments              11.8.2   13
June Chul Roh              Technical 206
             Texas Instruments               11.9.1       7

June Chul Roh              Technical 206
             Texas Instruments               11.9.1       7

June Chul Roh              Technical 206
             Texas Instruments               11.9.1       11

June Chul Roh              Technical 206
             Texas Instruments               11.9.1       1-15

June Chul Roh              Technical 206
             Texas Instruments               11.9.1       1-15

June Chul Roh              Technical 207
             Texas Instruments               11.9.2       6

June Chul Roh              Technical 207
             Texas Instruments               11.9.2       7

June Chul Roh              Technical 207
             Texas Instruments               11.9.3       11

June Chul Roh              Technical 207
             Texas Instruments               11.9.3       16
June Chul Roh              Editorial 207
             Texas Instruments               11.9.3       16
June Chul Roh              Editorial 208
             Texas Instruments               11.10.1      10

June Chul Roh              Technical
             Texas Instruments         208   11.10.1      13
             Yazdandoost Editorial
Kamya Yekeh NICT                       22    6.2.1.1.6    4
             Yazdandoost Editorial
Kamya Yekeh NICT                       47    6.3.11.4.2   12
             Yazdandoost Editorial
Kamya Yekeh NICT                       48    6.3.11.5.3   19
Kamya Yekeh NICT
             Yazdandoost Editorial     195   11.1         6&7
             Yazdandoost Technical
Kamya Yekeh NICT                       195   11.1         4
             Yazdandoost Technical
Kamya Yekeh NICT                       206   11.9.1       4
             NICT
kamya Yekeh Yazdandoost Technical      206   11.9.1       10
             Yazdandoost Technical
Kamya Yekeh NICT                       206   11.9.1       14
Kaoru Yokoo Fujitsu        Editorial   30    6.3.1.10.1   16
                           Technical   44    6.3.8        1
Kaoru Yokoo Fujitsu
Kaoru Yokoo Fujitsu        Editorial   47    6.3.11.4.3   14

Kaoru Yokoo Fujitsu        Technical 48      6.3.11.5.1   11
Kaoru Yokoo Fujitsu        Editorial 53      6.4.8        1
                           Technical 115     7.13.2       35
Kaoru Yokoo Fujitsu
Kaoru Yokoo Fujitsu        Editorial 84      7.6.1        22
                           Technical 89      7.7.1        20
Kaoru Yokoo Fujitsu
Kaoru Yokoo Fujitsu        Editorial   115   7.13.2       37
             Fuji Electric
Kazuyuki Yasukawa          Technical   142   9            4
             Fuji Electric
Kazuyuki Yasukawa          Technical   154   9.4.6.2
             Fuji Electric
Kazuyuki Yasukawa          Editorial   155   9.5.1        2
             T             Editorial
Khanh Tuan Le exas Instruments         164   10           9
             T             Technical
Khanh Tuan Le exas Instruments         164   10           13-14
             T             Technical
Khanh Tuan Le exas Instruments         164   10.1         24
             T             Editorial
Khanh Tuan Le exas Instruments         164   10.2         30
             T             Technical
Khanh Tuan Le exas Instruments         165   10.2         14-15
             T             Editorial
Khanh Tuan Le exas Instruments         166   10.4         10
            T              Technical
Khanh Tuan Le exas Instruments         167    10.5.2     9-10
            T              Technical
Khanh Tuan Le exas Instruments         167    10.5.2     1-21
            T              Editorial
Khanh Tuan Le exas Instruments         170    10.6.2.2   22-25
            T              Editorial
Khanh Tuan Le exas Instruments         171    10.7       18
            T              Technical
Khanh Tuan Le exas Instruments         172    10.7.1     10-13
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11
                                       195-
            T              Technical
Khanh Tuan Le exas Instruments         208    11

            T              Technical 195
Khanh Tuan Le exas Instruments                11.1       12
            T              Editorial 195
Khanh Tuan Le exas Instruments                11.2       16

            T              Technical 197
Khanh Tuan Le exas Instruments                11.4       7

            T              Technical 197
Khanh Tuan Le exas Instruments                11.4       2-6

            T              Technical 199
Khanh Tuan Le exas Instruments                11.5       14

            T              Technical 201
Khanh Tuan Le exas Instruments                11.6       1

            T              Technical 201
Khanh Tuan Le exas Instruments                11.6       4

            T              Technical 201
Khanh Tuan Le exas Instruments                11.6       4

            T              Technical 204
Khanh Tuan Le exas Instruments                11.8.1     4

            T              Technical 205
Khanh Tuan Le exas Instruments                11.8.2     5
            T              Editorial 205
Khanh Tuan Le exas Instruments                11.8.2     13

            T              Technical 205
Khanh Tuan Le exas Instruments                11.8.2     13

            T              Technical 206
Khanh Tuan Le exas Instruments                11.9.1     7

            T              Technical 206
Khanh Tuan Le exas Instruments                11.9.1     7

            T              Technical 206
Khanh Tuan Le exas Instruments                11.9.1     11

            T              Technical 206
Khanh Tuan Le exas Instruments                11.9.1     1-15
            T              Editorial 207
Khanh Tuan Le exas Instruments                11.9.3     16
            T              Editorial
Khanh Tuan Le exas Instruments            208      11.10.1        10

            T              Technical 208
Khanh Tuan Le exas Instruments                     11.10.1        13
                           Editorial 141
Kiran Bynam Samsung Electronics                    9              4
                                     142,                         Table 26
                                                   9.1
                           Technical 143
Kiran Bynam Samsung Electronics                                   to 29
                                     145,                         Table 33,
                                                   9.2
                           Technical 146
Kiran Bynam Samsung Electronics                                   Table 34
                                                                  Figure
                                          147      9.3
                          Editorial
Kiran Bynam Samsung Electronics                                   106
                                                                  Figure
                                          147,
                                                   9.3, 9.3.1.4   108, Line
                                          148
                          Technical
Kiran Bynam Samsung Electronics                                   13
                          editorial 149
Kiran Bynam Samsung Electronics                    9.3.3          6
                          editorial 151
Kiran Bynam Samsung Electronics                    9.4.2          20
                                                                  23,24,25,
                                      153          9.4.61
Kiran Bynam                 Technical
              Samsung Electronics                                 26
Kiran Bynam                 Technical 154
              Samsung Electronics                  9.4.6.2        5,6,7, 11
Kiran Bynam                 editorial 160
              Samsung Electronics                  9.7.8          15
Kiran Bynam                 Technical 164
              Samsung Electronics                  10.1.1         26
Kiran Bynam                 Technical 167
              Samsung Electronics                  10.5.3         22-25
Kiran Bynam                 Technical 170
              Samsung Electronics                  10.6           1
Kiran Bynam                 Technical 170
              Samsung Electronics                  10.6.21.4      14-15
Kiran Bynam                 Editorial 171
              Samsung Electronics                  10.7           2
Kiran Bynam                 Technical 172
              Samsung Electronics                  10.7.1         11,12,13
Kiran Bynam                 Editorial 173
              Samsung Electronics                  10.1           2
Kiran Bynam                 Editorial 180
              Samsung Electronics                  10.11.3.3      6 to 12
Kiran Bynam                 Undefined 180
              Samsung Electronics                  10.11.3.2      2 to 4
                                                                  Table 59,
                                    181            10.11.4.1
                          Technical
Kiran Bynam Samsung Electronics                                   Table 60
                          Technical 182
Kiran Bynam Samsung Electronics                    10.11.4.3      3
                                                                  Figure
                                          185      10.15.2
                          Technical
Kiran Bynam Samsung Electronics                                   127
                                          187 to                  Figure
                                                   10.15.3
                              Technical
Kiran Bynam Samsung Electronics           188                     128
                              Editorial
Kiran Bynam Samsung Electronics           175      10.11          13
                              Technical
Kiran Bynam Samsung Electronics           195      11.1           12 to 14
                              Editorial
Kiran Bynam Samsung Electronics           1        1.2
                              Technical
Kiran Bynam Samsung Electronics           141      9.1
                              Technical
Kiran Bynam Samsung Electronics           142      9.1.1
Kiran Bynam Samsung Electronics
                              Technical   182      10.11.4.3      3
Kiran Bynam Samsung Electronics
                              Editorial   182      10.11.4.3      3
             Elster Solutions Technical
Kuor-Hsin Chang                           9        3              17-20
             Elster Solutions Editorial
Kuor-Hsin Chang                           22       6.2.1.1.6      3
             Elster Solutions Editorial
Kuor-Hsin Chang                           22       6.2.1.1.6      4



             Elster Solutions Editorial
Kuor-Hsin Chang                           23       6.2.1.1.9      15


             Elster Solutions Technical 51-52
Kuor-Hsin Chang                                    6.4
             Elster Solutions Technical 164
Kuor-Hsin Chang                               10.1.1          26




                           G
Makoto Noda Sony Corporation eneral     1     1.2             31




                           G
Makoto Noda Sony Corporation eneral     13    5.3             20




                           G
Makoto Noda Sony Corporation eneral     33    6.3.2.3.4       1

                           T
Makoto Noda Sony Corporation echnical   98    7.9             7
                           T
Makoto Noda Sony Corporation echnical   115   7.13.2          6
                           T
Makoto Noda Sony Corporation echnical   194   10.18           13
                           T
Makoto Noda Sony Corporation echnical   208   11.1            7
            NICT
Marco Hernandez            Technical    118   Table 25        1
            NICT
Marco Hernandez            Technical    178   10.11.3.1       9
            NICT
Marco Hernandez            Technical    183   Equation (93)   1
Matt Boytim Sensus         Editorial    13    5.2             11
Matt Boytim Sensus         Editorial    14    5.3             20
Matt Boytim Sensus         Editorial    36    6.3.3.2.1       18
Matt Boytim Sensus         Editorial    150   9.4.1.1         23
Michael     DecaWave
McLaughlin Limited         Technical    164   10              1
Michael     DecaWave
McLaughlin Limited         Technical    164   10.1            22
Michael     DecaWave
McLaughlin Limited         Technical    165   10.2            1, 2
Michael     DecaWave
McLaughlin Limited        Technical   165    10.2         10,11
Michael     DecaWave
McLaughlin Limited        Editorial   165    10.2         15
Michael     DecaWave
McLaughlin Limited        Technical   172    10.7         5
Michael     DecaWave
McLaughlin Limited        Technical   172    10.9         26
Michael     DecaWave
McLaughlin Limited        Technical   172    10.9         26
Michael     DecaWave
McLaughlin Limited        Editorial   173    10.1         8, 11
Michael     DecaWave
McLaughlin Limited        Editorial   176    10.11.1.1    8
Michael     DecaWave
McLaughlin Limited        Technical   184    10.15.1      5,6
Michael     DecaWave
McLaughlin Limited        Technical   188    10.15.3      7-19
Michael     DecaWave
McLaughlin Limited        Editorial   189    10.16.3      10
Michael     DecaWave                  191,   10.17.2,
McLaughlin Limited        Technical   192    10.17.3      10
Michael     DecaWave
McLaughlin Limited        Editorial   192    10.17.4      10
Michael     DecaWave
McLaughlin Limited        Editorial   193    Figure 137   20
Michael     DecaWave
McLaughlin Limited        Editorial   194     10.17.5     10
            Atmel
Michael Schmidt           Technical   147     9.3
            Samsung Electronics
Noh-Gyoung Kang           Editorial   1       1.2
            Samsung Electronics
Noh-Gyoung Kang           Editorial           10.15.3
                                      187 to 188
Okundu Omeni              Editorial
            Toumaz Technology Ltd         15 5.5                  20
Okundu Omeni              Technical
            Toumaz Technology Ltd         31 6.3.1.13              9
Okundu Omeni              Technical
            Toumaz Technology Ltd         32 6.3.2.3.4            15
Okundu Omeni              Technical
            Toumaz Technology Ltd         53 6.4.8.3              11
Okundu Omeni              Editorial
            Toumaz Technology Ltd         54 6.4.8.6               4
Okundu Omeni              Technical
            Toumaz Technology Ltd         55 6.6.1                 3
Okundu Omeni              Technical
            Toumaz Technology Ltd         56 6.6.1.14             19
Okundu Omeni              Technical
            Toumaz Technology Ltd         57 6.6.2.1               1
Okundu Omeni              Technical
            Toumaz Technology Ltd         69 7.2.1                23
Okundu Omeni              Technical
            Toumaz Technology Ltd         71 7.2.4                 6
Okundu Omeni              Editorial
            Toumaz Technology Ltd         72 7.2.6                 9
Okundu Omeni              Technical
            Toumaz Technology Ltd         74 7.2.7.4              21
Okundu Omeni              Technical
            Toumaz Technology Ltd         75 7.2.9                17
Okundu Omeni              Technical
            Toumaz Technology Ltd         76 7.3.1.1               4
Okundu Omeni              Editorial
            Toumaz Technology Ltd         78 7.3.2                23
Okundu Omeni              Technical
            Toumaz Technology Ltd         93 7.8.1                20
Okundu Omeni              Technical
            Toumaz Technology Ltd         93 7.8.2                29
Okundu Omeni              Technical
            Toumaz Technology Ltd         98 7.9.1                18
Okundu Omeni              Technical
            Toumaz Technology Ltd         98 7.9.1                18
Okundu Omeni              Technical
            Toumaz Technology Ltd        109 7.12.2               26
Okundu Omeni              Technical
            Toumaz Technology Ltd        111 7.12.3               15
           Toumaz Technology Ltd
Okundu Omeni            Technical    112 7.12.3                     11
           Toumaz Technology Ltd
Okundu Omeni            Technical    112 7.12.3                     13
           Toumaz Technology Ltd
Okundu Omeni            Technical    112 7.12.3                     11
           Toumaz Technology Ltd
Okundu Omeni            Technical    111 7.12.4                     15
           Toumaz Technology Ltd
Okundu Omeni            Editorial  141            9           19
           Toumaz Technology Ltd
Okundu Omeni            Editorial  141            9           20
           Toumaz Technology Ltd
Okundu Omeni            Editorial  141            9           25
           Toumaz Technology Ltd
Okundu Omeni            Editorial  141            9           27
           Toumaz Technology Ltd
Okundu Omeni            Editorial  142         9.1.1          12
           Toumaz Technology Ltd
Okundu Omeni            Editorial  142         9.1.2          15
           Toumaz Technology Ltd
Okundu Omeni            Editorial  142         9.1.3          19
           Toumaz Technology Ltd
Okundu Omeni            Editorial  143         9.1.4           3
           Toumaz Technology Ltd
Okundu Omeni            Editorial  143         9.1.5           6
           Toumaz Technology Ltd
Okundu Omeni            Editorial  143         9.1.6           9
           Toumaz Technology Ltd
Okundu Omeni            Editorial  143         9.1.7           3
           Toumaz Technology Ltd
Okundu Omeni            Editorial  149         9.3.3           4
           Toumaz Technology Ltd
Okundu Omeni            Editorial  150        9.4.1.1         14
           Toumaz Technology Ltd
Okundu Omeni            Technical 154         9.4.6.2        8-12
           Toumaz Technology Ltd
Okundu Omeni            Editorial  156         9.5.3           5
           Toumaz Technology Ltd
Okundu Omeni            Editorial  156         9.5.3           7
           Toumaz Technology Ltd
Okundu Omeni            Editorial  156           9.6          13
           Toumaz Technology Ltd
Okundu Omeni            Editorial  160         9.7.7           4
           Toumaz Technology Ltd
Okundu Omeni            Editorial  160         9.7.8          15
           Toumaz Technology Ltd
Okundu Omeni            Editorial  164          10.2          31
           Toumaz Technology Ltd
Okundu Omeni            Editorial  165          10.2          10
           Toumaz Technology Ltd
Okundu Omeni            Editorial  167        10.5.2           1
           Toumaz Technology Ltd
Okundu Omeni            Editorial  167        10.5.3          22
           Toumaz Technology Ltd
Okundu Omeni            Editorial  171          10.7          18
           Toumaz Technology Ltd
Okundu Omeni            Technical 183          10.14           1
           Toumaz Technology Ltd
Okundu Omeni            Technical 187        10.15.3           6
           Toumaz Technology Ltd 195-208
Okundu Omeni            Technical                11            1
           Toumaz Technology Ltd
Okundu Omeni            Technical 199           11.3           1
           Toumaz Technology Ltd
Okundu Omeni            Technical 208           11.5           1
           Toumaz Technology Ltd
Okundu Omeni            Technical 206         11.9.1           2
           Toumaz Technology Ltd
Okundu Omeni            Technical 206         11.9.1          10
           Toumaz Technology Ltd
Okundu Omeni            Technical 208        11.10.1          13
Ouvry      CEA-Leti     Editorial 57     6.6.2.3        11
Ouvry      CEA-Leti     Technical 57     6.6.2.3        11
Ouvry      CEA-Leti     Editorial 117    7.13.4
Ouvry      CEA-Leti     Technical 161    9.8.2          3
Ouvry      CEA-Leti     Editorial 164    10             2

Ouvry       CEA-Leti      Editorial   164   10          6



Ouvry       CEA-Leti      Editorial   164   10          6
Ouvry   CEA-Leti   Editorial   164   10     6




Ouvry   CEA-Leti   Editorial   164   10     6



Ouvry   CEA-Leti   Editorial   164   10     6

Ouvry   CEA-Leti   Editorial   164   10.1   23

Ouvry   CEA-Leti   Editorial   164   10.1   18

Ouvry   CEA-Leti   Editorial   165   10.2   5




Ouvry   CEA-Leti   Editorial   165   10.2   8




Ouvry   CEA-Leti   Editorial   165   10.2   14




Ouvry   CEA-Leti   Editorial   165   10.3   17
Ouvry   CEA-Leti   Editorial   165   10.3     17


Ouvry   CEA-Leti   Editorial   165   10.3     17

Ouvry   CEA-Leti   Editorial   165   10.3     17

Ouvry   CEA-Leti   Editorial   165   10.3     17



Ouvry   CEA-Leti   Technical 165     10.3     17


Ouvry   CEA-Leti   Editorial   165   10.3     24


Ouvry   CEA-Leti   Editorial   165   10.3     17




Ouvry   CEA-Leti   Editorial   165   10.3     17



Ouvry   CEA-Leti   Editorial   165   10.3     17



Ouvry   CEA-Leti   Editorial   166   10.4     4




Ouvry   CEA-Leti   Editorial   166   10.4     9
Ouvry   CEA-Leti   Editorial   166   10.5



Ouvry   CEA-Leti   Technical 166     10.5.1   19
Ouvry   CEA-Leti   Editorial 167     10.5.2   13

Ouvry   CEA-Leti   Technical 168     10.5.4   19


Ouvry   CEA-Leti   Editorial   167   10.5.3   22
Ouvry   CEA-Leti   Editorial   168   10.5.4   13
Ouvry   CEA-Leti   Editorial   171   10.7     1




Ouvry   CEA-Leti   Editorial   171   10.7     2

Ouvry   CEA-Leti   Editorial   171   10.7     2




Ouvry   CEA-Leti   Editorial   171   10.7     2


Ouvry   CEA-Leti   Editorial   171   10.7     2




Ouvry   CEA-Leti   Editorial   171   10.7     2




Ouvry   CEA-Leti   Editorial   171   10.7     2




Ouvry   CEA-Leti   Editorial   171   10.7     2
Ouvry   CEA-Leti   Technical   171   10.7     2
Ouvry   CEA-Leti   Technical   171   10.7     3
Ouvry   CEA-Leti   Technical   171   10.7     3
Ouvry   CEA-Leti   Technical   171   10.7     6
Ouvry   CEA-Leti   Technical   172   10.7     8
Ouvry   CEA-Leti   Editorial   171   10.7     18
Ouvry   CEA-Leti   Technical   172   10.7.1   10
Ouvry       CEA-Leti      Technical   172       10.7.1           8
Ouvry       CEA-Leti      Editorial   172       10.7.1           1
Ouvry       CEA-Leti      Editorial   171       10.7.1           17
Ouvry       CEA-Leti      Editorial   172       10.8             19
Ouvry       CEA-Leti      Editorial   173       10.10.1          14
Ouvry       CEA-Leti      Editorial   several   UWB PHY
Ouvry       CEA-Leti      Editorial   several   UWB PHY
Ouvry       CEA-Leti      Editorial   175       10.11.1          15
Ouvry       CEA-Leti      Technical   177       10.11.2          1
Ouvry       CEA-Leti      Technical   180       10.11.3.3        5
Ouvry       CEA-Leti      Editorial   180       10.11.4.1        16
Ouvry       CEA-Leti      Editorial   181       10.11.4.1        1
Ouvry       CEA-Leti      Editorial   181       10.11.4.2        12
Ouvry       CEA-Leti      Editorial   182       10.12            11
Ouvry       CEA-Leti      Technical   182       10.13            16
Ouvry       CEA-Leti      Technical   183       10.14            1
Ouvry       CEA-Leti      Technical   183       10.14            2
Ouvry       CEA-Leti      Technical   173       10.10
Ouvry       CEA-Leti      Technical   184       10.15.1          5
Ouvry       CEA-Leti      Editorial   184       10.15.1          8
Ouvry       CEA-Leti      Technical   187       10.15.3          6
Ouvry       CEA-Leti      Editorial   191       10.17.3          13
Ouvry       CEA-Leti      Technical   191       10.17.3          13
Ouvry       CEA-Leti      Technical   192       10.17.3          1
Ouvry       CEA-Leti      Editorial   192       10.17.3          12
Ouvry       CEA-Leti      Editorial   192       10.17.4          7
Ouvry       CEA-Leti      Editorial   193       10.17.4          11
Ouvry       CEA-Leti      Editorial   193       10.17.4          15
Ouvry       CEA-Leti      Editorial   193       10.17.4          17
Ouvry       CEA-Leti      Editorial   194       10.17.5          1
Ouvry       CEA-Leti      Technical   194       10.18            14
            Samsung Electonics
Ranjeet Kumar Patro       Technical   97                         19
            Samsung Electonics
Ranjeet Kumar Patro       Technical             7.8.3
            Samsung Electonics
Ranjeet Kumar Patro       Technical   97                         9
            Samsung Electonics
Ranjeet Kumar Patro       Technical   98
            Samsung Electonics
Ranjeet Kumar Patro       Technical   98
            Samsung Electonics
Ranjeet Kumar Patro       Technical   98                         6
Ranjeet Kumar Patro       Editorial
            Samsung Electonics        97                         13 to 14
            Samsung Electonics
Ranjeet Kumar Patro       Technical   92
            Samsung Electonics
Ranjeet Kumar Patro       Technical   92
            Samsung Electonics
Ranjeet Kumar Patro       Technical   92                         35
            Samsung Electonics
Ranjeet Kumar Patro       Technical   93                         1 to 6
            Samsung Electonics
Ranjeet Kumar Patro       Technical   93                         6
            Samsung Electonics
Ranjeet Kumar Patro       Technical   93                         27
            Samsung Electonics
Ranjeet Kumar Patro       Technical   94
            Samsung Electonics
Ranjeet Kumar Patro       Technical   94                         11
            Samsung Electonics
Ranjeet Kumar Patro       Technical   95        7.8.2.1.3
            Samsung Electonics
Ranjeet Kumar Patro       Technical   96        7.8.2.1.4
            Samsung Electonics
Ranjeet Kumar Patro       Technical   92        7.8
            Samsung Electonics
Ranjeet Kumar Patro       Technical   92        7.8
            Samsung Electonics
Ranjeet Kumar Patro       Technical   92-93     7.8.1, 7.8.2.1
            Samsung Electonics
Ranjeet Kumar Patro       Technical   94        7.8.2.1          7
            Samsung Electonics
Ranjeet Kumar Patro       Technical 94       7.8.2.1         7
            Samsung Electonics
Ranjeet Kumar Patro       Technical 94       7.8.2.1         7
            Samsung Electonics
Ranjeet Kumar Patro       Technical 94       7.8.2.1         9
            Samsung Electonics
Ranjeet Kumar Patro       Technical 94       7.8.2.1
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
                                    where
                                    applica
                                    ble in
                                    the
                                    draft
                                    (6.4.8,
                                    6.2.1.1
                                    .10,
            Samsung Electonics
Ranjeet Kumar Patro       Editorial etc)
                                    where
                                    applica
                                    ble in
                                    the
                                    draft
                                    (page
            Samsung Electonics
Ranjeet Kumar Patro       Editorial 9 etc )
            Samsung Electonics
Ranjeet Kumar Patro       Editorial 28
            Samsung Electonics
Ranjeet Kumar Patro       Technical          6.3.1
            Samsung Electonics
Ranjeet Kumar Patro       Technical          6.4.6
            Samsung Electonics
Ranjeet Kumar Patro       Technical/Editorial6
            Samsung Electonics
Ranjeet Kumar Patro       Technical
            Samsung Electonics
Ranjeet Kumar Patro       Technical
            Samsung Electonics
Ranjeet Kumar Patro       Technical Page 516.4.6
            Samsung Electonics
Ranjeet Kumar Patro       Editorial
            Samsung Electonics
Ranjeet Kumar Patro       Editorial
            Samsung Electonics
Ranjeet Kumar Patro       Editorial 79
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Technical 51       6.4.6           10
            Samsung Electonics
Ranjeet Kumar Patro       Technical 69       7.2.1           25
            Samsung Electonics
Ranjeet Kumar Patro       Technical 70       7.2.1           3
            Samsung Electonics
Ranjeet Kumar Patro       Technical 70       7.2.1           12
            Samsung Electonics
Ranjeet Kumar Patro       Technical 70       7.2.3           29
            Samsung Electonics
Ranjeet Kumar Patro       Technical 71       7.2.4           2
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Technical 72                       Table - 18
Ranjeet Kumar Patro
            Samsung Electonics
                          Technical 73       7.3
            Samsung Electonics
Ranjeet Kumar Patro       Technical 76       7.3.1           28
            Samsung Electonics
Ranjeet Kumar Patro       Technical 76       7.3.1.1         32
            Samsung Electonics
Ranjeet Kumar Patro       Technical 77       7.3.1.2         10
            Samsung Electonics
Ranjeet Kumar Patro       Technical 88       7.7             20
            Samsung Electonics
Ranjeet Kumar Patro       Technical 95       7.8.2.1.2       8
            Samsung Electonics
Ranjeet Kumar Patro       Technical 95       7.8.2.1.4       18
            Samsung Electonics
Ranjeet Kumar Patro       Technical 95       7.8.2.1.4       19
            Samsung Electonics
Ranjeet Kumar Patro       Technical 104      7.1             22
            Samsung Electonics
Ranjeet Kumar Patro       Technical where applciable in the draft
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Technical 113       7.12.3.3     32
            Samsung Electonics
Ranjeet Kumar Patro       Technical 111       7.12.3       16
            Samsung Electonics
Ranjeet Kumar Patro       Technical 111       7.12.3       16
            Samsung Electonics
Ranjeet Kumar Patro       Technical 113       7.12.3.3     42
            Samsung Electonics
Ranjeet Kumar Patro       Technical 113       7.12.3.3     40 to 43
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Technical           7.12.3.1
            Samsung Electonics
Ranjeet Kumar Patro       Technical           7.12.3.1     16
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Technical 112       7.12.3.1
            Samsung Electonics
Ranjeet Kumar Patro       Technical 112       7.12.3
            Samsung Electonics
Ranjeet Kumar Patro       Technical 112       7.12.3       26
            Samsung Electonics
Ranjeet Kumar Patro       Technical           7.12.3
            Samsung Electonics
Ranjeet Kumar Patro       Technical           7.12.3
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Technical           7.12.4
            Samsung Electonics
Ranjeet Kumar Patro       Technical 122       7.12.4       9 to 10
            Samsung Electonics
Ranjeet Kumar Patro       Undefined
            Samsung Electonics
Ranjeet Kumar Patro       Technical 52        6.4.8        22
            Samsung Electonics
Ranjeet Kumar Patro       Technical 24        6.2.1.1.11   37
Ranjeet Kumar Patro       Technical 47
            Samsung Electonics                6.3.11.4.3   18
Ranjeet Kumar Patro       Technical 7
            Samsung Electonics                3            1
Ranjeet Kumar Patro       Technical 111
            Samsung Electonics                7.12.3       16
Ranjeet Kumar Patro       Technical 112
            Samsung Electonics                7.12.3.1     38
Ranjeet Kumar Patro       Technical 113
            Samsung Electonics                7.12.3.2     18
Ranjeet Kumar Patro       Technical 113
            Samsung Electonics                7.12.3.3     32
Ranjeet Kumar Patro       Technical 111
            Samsung Electonics                7.12.3       16
Ranjeet Kumar Patro       Technical 111
            Samsung Electonics                7.12.3       16
Rene Struik independent   Technical 119       8.1
Rene Struik   independent   Editorial   119   8.1          19
Rene Struik   independent   Technical 8.1     119
Rene Struik   independent   Editorial   8.1   119          21
Rene Struik   independent   Technical 8.1     119          23
Rene Struik   independent   Editorial   8.1   119          29




Rene Struik   independent   Technical 8.1     119          37
Rene Struik   independent   Technical 8.1     120          4-Jun
Rene Struik   independent   Technical 8.1     120          7-Sep
Rene Struik   independent   Technical 8.1.1   120          20-23
Rene Struik   independent   Technical 8.1.1   120
Rene Struik   independent   Technical 8.1.2   121
Rene Struik   independent   Technical 8.1.2   121
Rene Struik   independent   Technical 8.1.2   121
Rene Struik   independent   Technical 8.1.2   121




Rene Struik   independent   Technical 8.1.2   121
Rene Struik   independent   Technical 8.1.2   121   31




Rene Struik   independent   Technical 8.1.2   121
Rene Struik   independent   Technical 8.1.2   123
Rene Struik   independent   Technical 8.1.3   123   5
Rene Struik   independent   Technical 8.1.4   126       3
Rene Struik   independent   Technical 8.1.4   126       10-Nov
Rene Struik   independent   Technical 8.1.5   128       3
Rene Struik   independent   Technical 8.1.5   128       31
Rene Struik   independent   Technical 8.1.6   130       14
Rene Struik   independent   Technical 8.3.1.1 135
Rene Struik   independent   Technical 8.3.1.2 135-139
Rene Struik   independent   Technical 8.3.2   139       19
Rene Struik   independent   Technical 8.3.2   139       29
Rene Struik   independent   Technical 8.4     140       5-Jul
Rene Struik   independent   Technical 2
Rene Struik   independent   Technical 4       10-Dec
Rene Struik   independent   Technical 5.2     13        Dec-14
Rene Struik   independent   Technical 5.3     13        25-26
Rene Struik   independent   Technical 5.4     15        1-Mar
Rene Struik   independent   Technical 5.5     15
Rene Struik   independent   Technical 5.5.1.1 16
Rene Struik   independent   Technical 5.5.1.2 16        18
Rene Struik   independent   Technical 5.6     17        32
Rene Struik   independent   Technical 5.6               39
Rene Struik   independent   Technical 6.2     20
Rene Struik   independent   Technical 6.2.1   20
Rene Struik   independent   Technical 6.2.1.1 20
Rene Struik   independent                     21
                            Technical 6.2.1.1.4
Rene Struik   independent   Technical 6.2.1.1 20




Rene Struik   independent   Technical 6.2.2   26




Rene Struik   independent   Technical 6.2.2.1 26
Rene Struik   independent   Technical 6.2.2.1 26




Rene Struik   independent   Technical 6.2.2.1 27




Rene Struik   independent                     32
                            Technical 6.3.2.3.1




Rene Struik   independent                     32
                            Technical 6.3.2.3.2
Rene Struik   independent                     33
                            Technical 6.3.2.3.4




Rene Struik   independent   Technical 6.3.2.5 33




Rene Struik   independent   Technical 6.3.3.1 36




Rene Struik   independent                     36
                            Technical 6.3.3.2.1
Rene Struik   independent   Technical 6.3.5    38
                            Technical 47       6.3.11.4.1   1
Roberto
Aiello        independent
                            Technical 52       6.4.6.4      4-8


Roberto
Aiello        independent


           Elster
Rodney Hemminger Solutions Technical 9         3            17-20


            Elster
Rodney Hemminger Solutions Technical   51-52   6.4
            Elster
Rodney Hemminger Solutions Technical   164     10.1.1       26
Ruben                      Technical   52      6.4.6.4      4-8
Salazar     Landis+Gyr
Ruben                      Technical   94      7.8.2.1.1    20-22
Salazar     Landis+Gyr
Ruben
Salazar     Landis+Gyr     Technical   172   10.7.1         10-13
Ryuji Kohno NICT/YNU       Editorial   55    6.6            7 ++
Ryuji Kohno NICT/YNU       Technical         tables 24&25
                                       117&118              1
Ryuji Kohno NICT/YNU       Editorial   165   10.3.          18
Ryuji Kohno NICT/YNU       Technical   182   table 61       11
Ryuji Kohno NICT/YNU       Technical   198   10.17          10-15
Ryuji Kohno NICT/YNU       Technical   206   11.9.1         figure 149
Schwoerer   France TelecomEditorial    57    6.6.2.3        11




Schwoerer     France TelecomTechnical 57       6.6.2.3      11
Schwoerer     France TelecomEditorial 117      7.13.4

Schwoerer     France TelecomTechnical 161      9.8.2        3
Schwoerer   France TelecomEditorial   164   10     2

Schwoerer   France TelecomEditorial   164   10     6



Schwoerer   France TelecomEditorial   164   10     6




Schwoerer   France TelecomEditorial   164   10     6




Schwoerer   France TelecomEditorial   164   10     6



Schwoerer   France TelecomEditorial   164   10     6

Schwoerer   France TelecomEditorial   164   10.1   23

Schwoerer   France TelecomEditorial   164   10.1   18

Schwoerer   France TelecomEditorial   165   10.2   5
Schwoerer   France TelecomEditorial   165   10.2   8




Schwoerer   France TelecomEditorial   165   10.2   14




Schwoerer   France TelecomEditorial   165   10.3   17


Schwoerer   France TelecomEditorial   165   10.3   17


Schwoerer   France TelecomEditorial   165   10.3   17

Schwoerer   France TelecomEditorial   165   10.3   17

Schwoerer   France TelecomEditorial   165   10.3   17



Schwoerer   France TelecomTechnical 165     10.3   17


Schwoerer   France TelecomEditorial   165   10.3   24


Schwoerer   France TelecomEditorial   165   10.3   17




Schwoerer   France TelecomEditorial   165   10.3   17
Schwoerer   France TelecomEditorial   165   10.3     17



Schwoerer   France TelecomEditorial   166   10.4     4




Schwoerer   France TelecomEditorial   166   10.4     9
Schwoerer   France TelecomEditorial   166   10.5



Schwoerer   France TelecomTechnical 166     10.5.1   19
Schwoerer   France TelecomEditorial 167     10.5.2   13

Schwoerer   France TelecomTechnical 168     10.5.4   19


Schwoerer   France TelecomEditorial   167   10.5.3   22


Schwoerer   France TelecomEditorial   168   10.5.4   13
Schwoerer   France TelecomEditorial   171   10.7     1




Schwoerer   France TelecomEditorial   171   10.7     2

Schwoerer   France TelecomEditorial   171   10.7     2




Schwoerer   France TelecomEditorial   171   10.7     2


Schwoerer   France TelecomEditorial   171   10.7     2
Schwoerer   France TelecomEditorial   171   10.7     2




Schwoerer   France TelecomEditorial   171   10.7     2




Schwoerer   France TelecomEditorial   171   10.7     2




Schwoerer   France TelecomTechnical 171     10.7     2


Schwoerer   France TelecomTechnical 171     10.7     3


Schwoerer   France TelecomTechnical 171     10.7     3




Schwoerer   France TelecomTechnical 171     10.7     6




Schwoerer   France TelecomTechnical 172     10.7     8
Schwoerer   France TelecomEditorial 171     10.7     18




Schwoerer   France TelecomTechnical 172     10.7.1   10
Schwoerer   France TelecomTechnical 172     10.7.1      8


Schwoerer   France TelecomEditorial   172   10.7.1      1
Schwoerer   France TelecomEditorial   171   10.7.1      17

Schwoerer   France TelecomEditorial   172   10.8        19




Schwoerer   France TelecomEditorial   173   10.10.1     14


Schwoerer   France TelecomEditorial   several UWB PHY


Schwoerer   France TelecomEditorial   several UWB PHY
Schwoerer   France TelecomEditorial   175     10.11.1   15

Schwoerer   France TelecomTechnical 177     10.11.2     1

Schwoerer   France TelecomTechnical 180     10.11.3.3   5

Schwoerer   France TelecomEditorial   180   10.11.4.1   16
Schwoerer   France TelecomEditorial   181   10.11.4.1   1


Schwoerer   France TelecomEditorial   181   10.11.4.2   12

Schwoerer   France TelecomEditorial   182   10.12       11

Schwoerer   France TelecomTechnical 182     10.13       16
Schwoerer   France TelecomTechnical 183     10.14     1
Schwoerer   France TelecomTechnical 183     10.14     2




Schwoerer   France TelecomTechnical 173     10.10
Schwoerer   France TelecomTechnical 184     10.15.1   5


Schwoerer   France TelecomEditorial   184   10.15.1   8


Schwoerer   France TelecomTechnical 187     10.15.3   6
Schwoerer   France TelecomEditorial 191     10.17.3   13




Schwoerer   France TelecomTechnical 191     10.17.3   13
Schwoerer   France TelecomTechnical 192     10.17.3   1

Schwoerer   France TelecomEditorial   192   10.17.3   12




Schwoerer   France TelecomEditorial   192   10.17.4   7
Schwoerer   France TelecomEditorial   193   10.17.4   11



Schwoerer   France TelecomEditorial   193   10.17.4   15

Schwoerer   France TelecomEditorial   193   10.17.4   17

Schwoerer   France TelecomEditorial   194   10.17.5   1




Schwoerer   France TelecomTechnical 194     10.18     14
Schwoerer   France TelecomEditorial 199     11.4      2


Schwoerer   France TelecomEditorial   199   11.5      10
Schwoerer   France TelecomEditorial   200   11.5      2
Schwoerer   France TelecomEditorial   200   11.6      9
Schwoerer    France TelecomTechnical 201          11.6,1         7
Schwoerer    France TelecomTechnical 202          11.6.2         4



Schwoerer    France TelecomEditorial      203     11.8.1         8
Schwoerer    France TelecomTechnical      203     11.8.1         8
Schwoerer    France TelecomTechnical      205     11.8.1         10
Schwoerer    France TelecomEditorial      205     11.8.1         8
Schwoerer    France TelecomTechnical      205     11.8.2         all section
Schwoerer    France TelecomTechnical      205     11.9.1         all section
Schwoerer    France TelecomTechnical      205     11.9.3         all section
Schwoerer    France TelecomTechnical      195     11.1           12 to 14
Scott Weikel Elster Solutions Technical   9       3              17-20
Scott Weikel Elster Solutions Editorial   22      6.2.1.1.6      3
Scott Weikel Elster Solutions Editorial   22      6.2.1.1.6      4
Scott Weikel Elster Solutions Technical   51-52   6.4
Scott Weikel Elster Solutions Technical   164     10.1.1         26
Seung-Hoon Park               Editorial
             Samsung Electronics            97                    13 to 14
             Samsung Electronics
Seung-Hoon Park               Editorial     52         6.4.8         22
             Samsung Electronics
Seung-Hoon Park               Editorial     24      6.2.1.1.11       37
Seung-Hoon Park               Editorial
             Samsung Electronics
             Samsung Electronics
Seung-Hoon Park               Technical   94-96      7.8.2.1.2
Shinsuke HaraNICT             Technical
Shinsuke HaraNICT                     199
                              Technical           11.4           figure 143
Shinsuke HaraNICT             Technical
                                      206         11.9.1         figure 149
Shinsuke HaraNICT             Technical
                                      206         11.9.1         figure 149
Shinsuke HaraNICT                     207
                              Technical           11.9.2         6
Sridhar Rajagopal
             Samsung Electronics      47
                              Technical           6.3.11.4.3     18
Sridhar Rajagopal
             Samsung Electronics      7
                              Technical           3              1
Sridhar Rajagopal
             Samsung Electronics      111
                              Technical           7.12.3         16
Sridhar Rajagopal
             Samsung Electronics      112
                              Technical           7.12.3.1       38
Sridhar Rajagopal
             Samsung Electronics      113
                              Technical           7.12.3.2       18
Sridhar Rajagopal
             Samsung Electronics      113
                              Technical           7.12.3.3       32
Sridhar Rajagopal
             Samsung Electronics      111
                              Technical           7.12.3         16
Sridhar Rajagopal
             Samsung Electronics      111
                              Technical           7.12.3         16
                                      145,                       Table 33,
Sridhar Rajagopal           Technical 146
              Samsung Electronics                 9.2            Table 34
Sridhar Rajagopal           Technical 175
              Samsung Electronics                 10.11          13
                            Editorial 1
Srinath Hosur Texas Instruments                   1
                            Editorial 3
Srinath Hosur Texas Instruments                                  6-11
                            Editorial 7
Srinath Hosur Texas Instruments                   3              37
                            Editorial 13
Srinath Hosur Texas Instruments                   5
                            Editorial 16
Srinath Hosur Texas Instruments                   5.5.1.2        14-15
                            Editorial 16
Srinath Hosur Texas Instruments                   5.5.1.3        23-24
                            Editorial 16
Srinath Hosur Texas Instruments                   5.5.1.4        32
                            Editorial 19
Srinath Hosur Texas Instruments                   6
                            Editorial 21
Srinath Hosur Texas Instruments                   6.2.1.1.4      15-18
                            Editorial 22
Srinath Hosur Texas Instruments                   6.2.1.1.6      4
                            Editorial 22
Srinath Hosur Texas Instruments                   6.2.1.1.8      15
                            Editorial
Srinath Hosur Texas Instruments         22      6.2.1.1.8     15
                            Editorial
Srinath Hosur Texas Instruments         22      6.2.1.1.8     15
                            Technical
Srinath Hosur Texas Instruments         22      6.2.1.1.8     15
                            Editorial
Srinath Hosur Texas Instruments         23      6.2.1.1.10    35
                            Editorial
Srinath Hosur Texas Instruments         24      6.2.1.1.11    40
                            Technical
Srinath Hosur Texas Instruments         25      6.2.1.1.12    12
                            Technical
Srinath Hosur Texas Instruments         25      6.2.1.1.12    14-24
                            Technical
Srinath Hosur Texas Instruments         26      6.2.1.1.12    3
                            Editorial
Srinath Hosur Texas Instruments         26      6.2.2         15
                            Editorial
Srinath Hosur Texas Instruments         27      6.2.2.2       15
                            Editorial
Srinath Hosur Texas Instruments         27      6.2.2.2       17
                            Editorial
Srinath Hosur Texas Instruments         29      6.3.1.4       16
                            Editorial
Srinath Hosur Texas Instruments         29      6.3.1.6       28
                            Editorial
Srinath Hosur Texas Instruments         32      6.3.2.3       1-9
                            Editorial
Srinath Hosur Texas Instruments         32      6.3.2.3.1     6
                            Editorial
Srinath Hosur Texas Instruments         32      6.3.2.3.4     15
                            Editorial
Srinath Hosur Texas Instruments         43      6.3.7.3       1
                            Technical
Srinath Hosur Texas Instruments         45      6.3.8         1-2
                            Editorial
Srinath Hosur Texas Instruments         46      6.3.11.3      20
                            Technical
Srinath Hosur Texas Instruments         46      6.3.11.3      20
                            Editorial
Srinath Hosur Texas Instruments         47      6.3.11.4.1    1-22
                            Technical
Srinath Hosur Texas Instruments         47      6.3.11.4.1    1
                            Technical
Srinath Hosur Texas Instruments         47      6.3.11.4.1    2-6
                            Technical
Srinath Hosur Texas Instruments         47      6.3.11.4.1    1-22
                            Technical
Srinath Hosur Texas Instruments         48      6.3.11.5(b)   3-20
                            Technical
Srinath Hosur Texas Instruments         49      6.3.11.5.4    1-16
                            Technical
Srinath Hosur Texas Instruments         49      6.3.11.5.4    17
                            Editorial
Srinath Hosur Texas Instruments         49      6.3.11.5.4    2
                            Technical
Srinath Hosur Texas Instruments         52      6.4.6.4       5
                            Technical
Srinath Hosur Texas Instruments         52      6.4.6.4       4-8
                            Technical
Srinath Hosur Texas Instruments         52-53   6.4.8
                            Editorial
Srinath Hosur Texas Instruments         57      6.6.2.3       11
                            Editorial
Srinath Hosur Texas Instruments         57      6.6.2.3       11
                            Editorial
Srinath Hosur Texas Instruments         57      6.6.2.3       13
                            Editorial
Srinath Hosur Texas Instruments         58      6.7.1         5
                            Technical
Srinath Hosur Texas Instruments         58      6.7.1         6
                            Editorial
Srinath Hosur Texas Instruments         58      6.7.1.1       10-11
                            Editorial
Srinath Hosur Texas Instruments         59      6.7.1.2       3
                            Technical
Srinath Hosur Texas Instruments         59
                            Editorial
Srinath Hosur Texas Instruments         59      6.7.2         13
                            Editorial
Srinath Hosur Texas Instruments         61      6.7.5         15
                            Technical
Srinath Hosur Texas Instruments         66      6.7.11        5
                            Technical
Srinath Hosur Texas Instruments         66      6.7.11        8-9
                            Technical
Srinath Hosur Texas Instruments         72      7.2.7         15
                            Editorial
Srinath Hosur Texas Instruments         74      7.2.7.4       21
                            Editorial
Srinath Hosur Texas Instruments         74      7.2.7.4       23-24
                            Editorial
Srinath Hosur Texas Instruments         75      7.2.7.4       1-2
                            Technical
Srinath Hosur Texas Instruments         77      7.3.1         76
                            Editorial
Srinath Hosur Texas Instruments         78      7.4           28
                            Editorial
Srinath Hosur Texas Instruments         78      7.4           32
                            Editorial
Srinath Hosur Texas Instruments         78      7.4           36
                            Technical
Srinath Hosur Texas Instruments         79      7.4           1-2
                            Editorial
Srinath Hosur Texas Instruments         83    7.5.2.1     30
                            Editorial
Srinath Hosur Texas Instruments         85    7.6.2       1
                            Editorial
Srinath Hosur Texas Instruments         85    7.6.2       1



                            Editorial
Srinath Hosur Texas Instruments         86    7.6.2.1.1   1

                            Editorial
Srinath Hosur Texas Instruments         89    7.7.1       20-21
                            Editorial
Srinath Hosur Texas Instruments         89    7.7.1       22
                            Editorial
Srinath Hosur Texas Instruments         91    7.7.2       9-17
                            Editorial
Srinath Hosur Texas Instruments         92    7.7.5       25
                            Technical
Srinath Hosur Texas Instruments         94    7.8.2.1.1   20-22
                            Technical
Srinath Hosur Texas Instruments         94    7.8.2.1.2   24-28
                            Technical
Srinath Hosur Texas Instruments         95    7.8.2.1.2   1-4
                            Technical
Srinath Hosur Texas Instruments         95    7.8.2.1.2   5-19
                            Editorial
Srinath Hosur Texas Instruments         95    7.8.2.1.3   21
                            Editorial
Srinath Hosur Texas Instruments         95    7.8.2.1.3   21
                            Editorial
Srinath Hosur Texas Instruments         95    7.8.2.1.3   22
                            Editorial
Srinath Hosur Texas Instruments         95    7.8.2.1.3   27
                            Technical
Srinath Hosur Texas Instruments         95    7.8.2.1.3   28
                            Technical
Srinath Hosur Texas Instruments         96    7.8.2.1.3   1
                            Technical
Srinath Hosur Texas Instruments         96    7.8.2.1.4   9
                            Technical
Srinath Hosur Texas Instruments         96    7.8.2.1.4   9-29
                            Editorial
Srinath Hosur Texas Instruments         97    7.8.3       17
                            Editorial
Srinath Hosur Texas Instruments         97    7.8.3       18-19
                            Editorial
Srinath Hosur Texas Instruments         98    7.8.3       6
                            Technical
Srinath Hosur Texas Instruments         98    7.9         7
                            Editorial
Srinath Hosur Texas Instruments         107   7.12        26-30
                            Technical
Srinath Hosur Texas Instruments         111   7.12.3      15
                            Editorial
Srinath Hosur Texas Instruments         111   7.12.3      15
                            Technical
Srinath Hosur Texas Instruments         111   7.12.3      16-17
                            Technical
Srinath Hosur Texas Instruments         112   7.12.3      1-10
                            Technical
Srinath Hosur Texas Instruments         112   7.12.3      11-25
                            Technical
Srinath Hosur Texas Instruments         112   7.12.3      26-33
                            Technical
Srinath Hosur Texas Instruments         112   7.12.3      34-37
                            Technical
Srinath Hosur Texas Instruments         112   7.12.3.1    38
                            Technical
Srinath Hosur Texas Instruments         112   7.12.3.1    39-40
                            Technical
Srinath Hosur Texas Instruments         112   7.12.3.1    41-45
                            Technical
Srinath Hosur Texas Instruments         113   7.12.3.1    1-17
                            Technical
Srinath Hosur Texas Instruments         113   7.12.3.2    18-31
                            Technical
Srinath Hosur Texas Instruments         113   7.12.3.3    32
                            Technical
Srinath Hosur Texas Instruments         113   7.12.3.3    33-44
                            Technical
Srinath Hosur Texas Instruments         114   7.12.3.3    1-2
                            Technical
Srinath Hosur Texas Instruments         114   7.12.4      3

                            Technical
Srinath Hosur Texas Instruments         114   7.12.4      4-24
                            Technical
Srinath Hosur Texas Instruments         114   7.12.4      25
                            Technical
Srinath Hosur Texas Instruments         115   7.13.2      6-39
                            Technical
Srinath Hosur Texas Instruments         117   7.13.4      1
                            Technical
Srinath Hosur Texas Instruments         117   7.13.4      1
                            Technical
Srinath Hosur Texas Instruments         117   7.13.4      1
                            Technical
Srinath Hosur Texas Instruments         117   7.13.4      1
                            Editorial
Srinath Hosur Texas Instruments         117   7.13.4      1
                            Technical
Srinath Hosur Texas Instruments         117   7.13.4      1
                            Editorial
Srinath Hosur Texas Instruments         118   7.13.4      1
                            Editorial
Srinath Hosur Texas Instruments         118   7.13.4      1
                            Technical
Srinath Hosur Texas Instruments         118   7.13.4      1
                            Technical
Srinath Hosur Texas Instruments         118   7.13.4      1
                            Editorial
Srinath Hosur Texas Instruments         119   8           12
                            Editorial
Srinath Hosur Texas Instruments         119   8.1         17
                            Editorial
Srinath Hosur Texas Instruments         119   8
                            Editorial
Srinath Hosur Texas Instruments         121   8.1.2       29-30
                            Editorial
Srinath Hosur Texas Instruments         124   8.1.3       18-19
                            Editorial
Srinath Hosur Texas Instruments         124   8.1.4       17-18
                            Editorial
Srinath Hosur Texas Instruments         126   8.1.4       12
                            Editorial
Srinath Hosur Texas Instruments         129   8.1.5       22
                            Editorial
Srinath Hosur Texas Instruments         134   8.3.1       11
                            Editorial
Srinath Hosur Texas Instruments         134   8.3.1       12-22
                            Editorial
Srinath Hosur Texas Instruments         156   9.6.1       14-17
                            Editorial
Srinath Hosur Texas Instruments               9, 10, 11
                            Editorial
Srinath Hosur Texas Instruments         164   10          14
                            Technical
Srinath Hosur Texas Instruments         165   10.2        5
                            Technical
Srinath Hosur Texas Instruments         165   10.3        17-22
                            Technical
Srinath Hosur Texas Instruments         165   10.3        23-29
                            Technical
Srinath Hosur Texas Instruments         165   10.5        16-17
                            Technical
Srinath Hosur Texas Instruments         166   10.4        4
                            Technical
Srinath Hosur Texas Instruments         166   10.5.1      21
                            Technical
Srinath Hosur Texas Instruments         166   10.5.1      21-23
                            Technical
Srinath Hosur Texas Instruments         170   10.6.1      1-2
                            Technical
Srinath Hosur Texas Instruments         171   10.7        9-10
                            Technical
Srinath Hosur Texas Instruments         171   10.7        11-12
                            Editorial
Srinath Hosur Texas Instruments         188   10.16.1     34
                            Editorial
Srinath Hosur Texas Instruments         189   10.16.2     1
                            Technical
Srinath Hosur Texas Instruments         189   10.16.2     1
                            Editorial
Srinath Hosur Texas Instruments         189   10.16.3     6-7
                            Technical
Srinath Hosur Texas Instruments         189   10.16.3
                            Technical
Srinath Hosur Texas Instruments         189   10.16.3     10-11
                            Technical
Srinath Hosur Texas Instruments         190   10.16.3     1
                            Technical
Srinath Hosur Texas Instruments         195   11.2        21-23
Srinath Hosur Texas Instruments                           Figure
                                                          105, 142
                                                          Lines 1 to
                            Editorial   141               3
                            Editorial
Srinath Hosur Texas Instruments         142               4
                            Editorial
Srinath Hosur Texas Instruments         146               4
                            Editorial
Srinath Hosur Texas Instruments         148               13,14
Srinath Hosur Texas Instruments                           16-19,
                                        148               Figure
                            Technical   149   9.3.2       109
                            Editorial
Srinath Hosur Texas Instruments         149   9.4         12,13
                            Editorial
Srinath Hosur Texas Instruments         151    9.4.1.2    17
                            Editorial
Srinath Hosur Texas Instruments         152   9.4.2       2
Srinath Hosur Texas Instruments                         Figure
                            Editorial   150   9.4       110
                            Editorial
Srinath Hosur Texas Instruments         152   9.4.4     8 to 24
Srinath Hosur Texas Instruments
                            Technical   153   9.4.5     4 to 20
                            Editorial
Srinath Hosur Texas Instruments         154   9.4.6.2   6,7
Srinath Hosur Texas Instruments
                            Editorial   154   9.4.6.2   11
Srinath Hosur Texas Instruments
                            Editorial   154   9.4.6.2   8,9
Srinath Hosur Texas Instruments

                            Editorial   156   9.6       12,13
                            Editorial
Srinath Hosur Texas Instruments         160   9.7.8     13
                            Editorial
Srinath Hosur Texas Instruments         160   9.7.8     15
Srinath Hosur Texas Instruments
                            Editorial   160   9.8.1     19
Srinath Hosur Texas Instruments
                            Editorial   160   9.8.1     20
Srinath Hosur Texas Instruments

                            Editorial   162   9.8.4     8
Srinath Hosur Texas Instruments


                            Editorial   164   10        7-8
Srinath Hosur Texas Instruments
                            Editorial   164   10        9
Srinath Hosur Texas Instruments


                            Technical 164     10        13-14
Srinath Hosur Texas Instruments




                            Technical 164     10.1      15-24
Srinath Hosur Texas Instruments
                            Technical 164     10.1      24
Srinath Hosur Texas Instruments
                            Technical 164     10.1.1    26-27
Srinath Hosur Texas Instruments


                            Editorial   164   10.2      30
                            Editorial
Srinath Hosur Texas Instruments         164   10.2      30-31
Srinath Hosur Texas Instruments




                            Editorial   165   10.2     8-9
Srinath Hosur Texas Instruments




                            Technical 165     10.2     11-13
Srinath Hosur Texas Instruments


                            Technical 165     10.2     14-15
Srinath Hosur Texas Instruments


                            Technical   165   10.3     17-22
Srinath Hosur Texas Instruments
                            Editorial   166   10.4     1
Srinath Hosur Texas Instruments
                            Technical   166   10.4     1
Srinath Hosur Texas Instruments
                            Editorial   166   10.4     6
Srinath Hosur Texas Instruments

                            Editorial   166   10.4     7
Srinath Hosur Texas Instruments

                            Editorial   166   10.4     10
Srinath Hosur Texas Instruments


                            Editorial   166   10.5     17
Srinath Hosur Texas Instruments
                            Editorial   166   10.5.1   21
Srinath Hosur Texas Instruments
                            Editorial   166   10.5.1   21
Srinath Hosur Texas Instruments

                            Editorial   166   10.5.1   23
Srinath Hosur Texas Instruments
                            Editorial   167   10.5.2   2-3
Srinath Hosur Texas Instruments
                            Editorial   167   10.5.2   8
Srinath Hosur Texas Instruments

                            Technical 167     10.5.2     9-10
Srinath Hosur Texas Instruments
                            Technical 167     10.5.2     1-21
Srinath Hosur Texas Instruments

                            Editorial   168   10.5.3     6-8
Srinath Hosur Texas Instruments

                            Editorial   168   10.5.4     21
Srinath Hosur Texas Instruments


                            Editorial   169   10.5.5     3-4
Srinath Hosur Texas Instruments




                            Technical 169     10.5.5     7
Srinath Hosur Texas Instruments




                                      169-
                            Technical 170     10.6
Srinath Hosur Texas Instruments
                                      169-
                            Editorial 170     10.6
Srinath Hosur Texas Instruments


                            Editorial   169   10.6       21
Srinath Hosur Texas Instruments
                            Editorial   170   10.6.1.2   10
Srinath Hosur Texas Instruments
                            Editorial   170   10.6.1.4   13-15
Srinath Hosur Texas Instruments
                            Editorial   170   10.6.2.1   17
Srinath Hosur Texas Instruments


                            Editorial   170   10.6.2.2   22-25
Srinath Hosur Texas Instruments



                            Editorial   171   10.7       2-5
Srinath Hosur Texas Instruments




                            Technical 171     10.7       6-10
Srinath Hosur Texas Instruments

                            Editorial   171   10.7       15
Srinath Hosur Texas Instruments


                            Technical   171   10.7       17
                            Editorial
Srinath Hosur Texas Instruments         171   10.7       18
Srinath Hosur Texas Instruments
                            Editorial   171   10.7
                            Editorial
Srinath Hosur Texas Instruments         172   10.7       8
Srinath Hosur Texas Instruments
                            Technical   172   10.7.1     10-13
Srinath Hosur Texas Instruments
                            Editorial   172   10.9       26
Srinath Hosur Texas Instruments




                            Technical 173     10.10      8-9
Srinath Hosur Texas Instruments




                            Technical   173   10.10      11-12
                            Editorial
Srinath Hosur Texas Instruments         173   10.10      9
                            Editorial
Srinath Hosur Texas Instruments         173   10.10      12
Srinath Hosur Texas Instruments
                            Editorial   173   10.10      9
Srinath Hosur Texas Instruments
                            Editorial   173   10.10      12
Srinath Hosur Texas Instruments
                            Editorial   173   10.10      12
Srinath Hosur Texas Instruments
                            Editorial   174   10.10.3    4-5
Srinath Hosur Texas Instruments
                            Editorial   174   10.10.5    9-10
Srinath Hosur Texas Instruments
                            Editorial   174   10.10.7    13-14
Srinath Hosur Texas Instruments
                            Editorial   174   10.10.10   20
Srinath Hosur Texas Instruments




                            Technical 175     10.10.11   1-3
Srinath Hosur Texas Instruments




                            Editorial   175   10.10.12   5
Srinath Hosur Texas Instruments




                            Technical 175     10.11.1    14-20
Srinath Hosur Texas Instruments


                            Technical 175     10.11.1    14-20
Srinath Hosur Texas Instruments
                            Editorial 176     10.11.1    19-21
Srinath Hosur Texas Instruments


                            Technical   177   10.11.2    12-15
Srinath Hosur Texas Instruments
                            Editorial   177   10.11.2    6
                            Editorial
Srinath Hosur Texas Instruments         177   10.11.2    9
Srinath Hosur Texas Instruments
                            Technical   177   10.11.2    1-18
Srinath Hosur Texas Instruments




                                      178-
                            Technical 180      10.11.3
Srinath Hosur Texas Instruments

                            Editorial   178    10.11.3     5
                            Editorial
Srinath Hosur Texas Instruments         179    10.11.3.2   4-6
Srinath Hosur Texas Instruments




                            Technical   179    10.11.3.2   7
Srinath Hosur Texas Instruments
                            Technical   179    10.11.3.2   8
Srinath Hosur Texas Instruments
                            Editorial   180    10.11.3.2   1
Srinath Hosur Texas Instruments
                            Editorial   180    10.11.3.3   5-9
Srinath Hosur Texas Instruments

                            Editorial   180    10.11.4     12
                            Editorial
Srinath Hosur Texas Instruments         181    10.11.4     1
Srinath Hosur Texas Instruments
                            Technical   181    10.11.4     7-9
                            Editorial
Srinath Hosur Texas Instruments         181    10.11.4     10
Srinath Hosur Texas Instruments         181-
                            Technical   182    10.11.4.3
                            Editorial
Srinath Hosur Texas Instruments         182    10.12       11
Srinath Hosur Texas Instruments


                            Technical   182    10.15.1     5-6
                            Editorial
Srinath Hosur Texas Instruments         182    10.15.1     7-9
Srinath Hosur Texas Instruments         187-
                            Technical   188    10.15.3
Srinath Hosur Texas Instruments

                            Technical   188    10.16       20-33
                            Editorial
Srinath Hosur Texas Instruments         188    10.16.1     37
Srinath Hosur Texas Instruments
                            Technical   189    10.16.2     1-3
                            Editorial
Srinath Hosur Texas Instruments         189    10.16.3     6-7
Srinath Hosur Texas Instruments
                            Technical   189    10.16.3   10-11
                            Editorial
Srinath Hosur Texas Instruments         190    10.16.3
                            Editorial
Srinath Hosur Texas Instruments         190    10.17     7
                            Editorial
Srinath Hosur Texas Instruments         192    10.17     1-2
                            Editorial
Srinath Hosur Texas Instruments         192    10.17.4   16
                            Editorial
Srinath Hosur Texas Instruments         194    10.17.5   1-12
Srinath Hosur Texas Instruments
                            Technical   194    10.18     12-15
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
Srinath Hosur Texas Instruments         195-
                            Technical   208    11
                            Editorial
Srinath Hosur Texas Instruments         195    11.1      4
                            Editorial
Srinath Hosur Texas Instruments         195    11.1      8-11
Srinath Hosur Texas Instruments
                            Technical   195    11.1      12
                            Editorial
Srinath Hosur Texas Instruments         195    11.2      16
                            Editorial
Srinath Hosur Texas Instruments         195    11.2      16-17
                            Editorial
Srinath Hosur Texas Instruments         195    11.2      17
                            Editorial
Srinath Hosur Texas Instruments         195    11.2      18
                            Editorial
Srinath Hosur Texas Instruments         195    11.2      20
                            Editorial
Srinath Hosur Texas Instruments         195    11.2      footnote
                            Editorial
Srinath Hosur Texas Instruments         196    11.3      3
                            Editorial
Srinath Hosur Texas Instruments         196    11.3      3-4
                            Editorial
Srinath Hosur Texas Instruments         196    11.3      15
Srinath Hosur Texas Instruments
                            Technical   197    11.4      7
                            Editorial
Srinath Hosur Texas Instruments         197    11.4      6
Srinath Hosur Texas Instruments
                            Technical   197    11.4      2-6
                            Editorial
Srinath Hosur Texas Instruments         197    11.4      2-6
Srinath Hosur Texas Instruments         198-
                            Editorial   199    11.4     6-8,1-3
Srinath Hosur Texas Instruments
                            Technical   199    11.5     14
Srinath Hosur Texas Instruments
                            Technical   199    11.5     18-19
                            Editorial
Srinath Hosur Texas Instruments         199    11.5     19
Srinath Hosur Texas Instruments
                            Technical   200    11.6     9
Srinath Hosur Texas Instruments
                            Technical   201    11.6     1
Srinath Hosur Texas Instruments
                            Technical   201    11.6     4
Srinath Hosur Texas Instruments
                            Technical   201    11.6     4
                            Editorial
Srinath Hosur Texas Instruments         201    11.6     4
                            Editorial
Srinath Hosur Texas Instruments         201    11.6     4
Srinath Hosur Texas Instruments
                            Technical   201    11.6     4
Srinath Hosur Texas Instruments
                            Technical   201    11.6     4
Srinath Hosur Texas Instruments
                            Technical   201    11.6     4
Srinath Hosur Texas Instruments
                            Technical   201    11.6     4
Srinath Hosur Texas Instruments
                            Technical   201    11.6.1   7
                            Editorial
Srinath Hosur Texas Instruments         201    11.6.1   7
Srinath Hosur Texas Instruments
                            Technical   201    11.6.1   7-10
Srinath Hosur Texas Instruments
                            Technical   202    11.6.1   1-2
Srinath Hosur Texas Instruments         201-
                            Technical   202    11.6.1   7-10,1-2
Srinath Hosur Texas Instruments
                            Technical   202    11.6.2   4
Srinath Hosur Texas Instruments
                            Technical   202    11.6.2   4
Srinath Hosur Texas Instruments
                            Technical   202    11.6.2   3-7
Srinath Hosur Texas Instruments
                            Technical   202    11.7     11
Srinath Hosur Texas Instruments
                            Technical   202    11.7     16
Srinath Hosur Texas Instruments
                            Technical   203    11.7     5
Srinath Hosur Texas Instruments
                            Technical   203    11.8.1   9
Srinath Hosur Texas Instruments
                            Technical   203    11.8.1   11
Srinath Hosur Texas Instruments
                            Technical   204    11.8.1   4
Srinath Hosur Texas Instruments
                            Technical   204   11.8.1    1
Srinath Hosur Texas Instruments
                            Technical   204   11.81     9-10
Srinath Hosur Texas Instruments
                            Technical   205   11.8.2    5
                            Editorial
Srinath Hosur Texas Instruments         205   11.8.2    13
Srinath Hosur Texas Instruments
                            Technical   205   11.8.2    13
Srinath Hosur Texas Instruments
                            Technical   206   11.9.1    7
Srinath Hosur Texas Instruments
                            Technical   206   11.9.1    7
Srinath Hosur Texas Instruments
                            Technical   206   11.9.1    11
Srinath Hosur Texas Instruments
                            Technical   206   11.9.1    1-15
Srinath Hosur Texas Instruments
                            Technical   206   11.9.1    1-15
Srinath Hosur Texas Instruments
                            Technical   207   11.9.2    6
Srinath Hosur Texas Instruments
                            Technical   207   11.9.2    7
Srinath Hosur Texas Instruments
                            Technical   207   11.9.3    11
Srinath Hosur Texas Instruments
                            Technical   207   11.9.3    16
                            Editorial
Srinath Hosur Texas Instruments         207   11.9.3    16
                            Editorial
Srinath Hosur Texas Instruments         208   11.10.1   10
Srinath Hosur Texas Instruments
                            Technical   208   11.10.1   13
                                                        Figure
                                                        105, 142
Sverre       Texas                                      Lines 1 to
Brubæk       Instruments    Editorial   141             3
Sverre       Texas
Brubæk       Instruments    Editorial   142             4
Sverre       Texas
Brubæk       Instruments    Editorial   146             4
Sverre       Texas
Brubæk       Instruments    Editorial   148             13,14
                                                        16-19,
Sverre       Texas                                      Figure
Brubæk       Instruments    Technical ##### 9.3.2       109
Sverre       Texas
Brubæk       Instruments    Editorial   149   9.4       12,13
Sverre       Texas
Brubæk       Instruments    Editorial   151   9.4.1.2   17
Sverre       Texas
Brubæk       Instruments    Editorial   152   9.4.2     2
Sverre       Texas                                      Figure
Brubæk       Instruments    Editorial   150   9.4       110
Sverre   Texas
Brubæk   Instruments   Editorial   152   9.4.4     8 to 24
Sverre   Texas
Brubæk   Instruments   Technical 153     9.4.5     4 to 20
Sverre   Texas
Brubæk   Instruments   Editorial   154   9.4.6.2   6,7
Sverre   Texas
Brubæk   Instruments   Editorial   154   9.4.6.2   11
Sverre   Texas
Brubæk   Instruments   Editorial   154   9.4.6.2   8,9
Sverre   Texas
Brubæk   Instruments   Editorial   156   9.6       12,13
Sverre   Texas
Brubæk   Instruments   Editorial   160   9.7.8     13
Sverre   Texas
Brubæk   Instruments   Editorial   160   9.7.8     15
Sverre   Texas
Brubæk   Instruments   Editorial   160   9.8.1     19
Sverre   Texas
Brubæk   Instruments   Editorial   160   9.8.1     20
Sverre   Texas
Brubæk   Instruments   Editorial   162   9.8.4     8
Sverre   Texas
Brubæk   Instruments   Editorial   164   10        7-8
Sverre   Texas
Brubæk   Instruments   Editorial   164   10        9
Sverre   Texas
Brubæk   Instruments   Technical 164     10        13-14
Sverre   Texas
Brubæk   Instruments   Technical 164     10.1      15-24
Sverre   Texas
Brubæk   Instruments   Technical 164     10.1      24
Sverre   Texas
Brubæk   Instruments   Technical 164     10.1.1    26-27
Sverre   Texas
Brubæk   Instruments   Editorial   164   10.2      30
Sverre   Texas
Brubæk   Instruments   Editorial   164   10.2      30-31
Sverre   Texas
Brubæk   Instruments   Editorial   165   10.2      8-9
Sverre   Texas
Brubæk   Instruments   Technical 165     10.2      11-13
Sverre   Texas
Brubæk   Instruments   Technical 165     10.2      14-15
Sverre   Texas
Brubæk   Instruments   Technical 165     10.3      17-22
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.4      1
Sverre   Texas
Brubæk   Instruments   Technical 166     10.4      1
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.4      6
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.4       7
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.4       10
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.5       17
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.5.1     21
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.5.1     21
Sverre   Texas
Brubæk   Instruments   Editorial   166   10.5.1     23
Sverre   Texas
Brubæk   Instruments   Editorial   167   10.5.2     2-3
Sverre   Texas
Brubæk   Instruments   Editorial   167   10.5.2     8
Sverre   Texas
Brubæk   Instruments   Technical 167     10.5.2     9-10
Sverre   Texas
Brubæk   Instruments   Technical 167     10.5.2     1-21
Sverre   Texas
Brubæk   Instruments   Editorial   168   10.5.3     6-8
Sverre   Texas
Brubæk   Instruments   Editorial   168   10.5.4     21
Sverre   Texas
Brubæk   Instruments   Editorial   169   10.5.5     3-4
Sverre   Texas
Brubæk   Instruments   Technical 169     10.5.5     7
Sverre   Texas                   169-
Brubæk   Instruments   Technical 170     10.6
Sverre   Texas                   169-
Brubæk   Instruments   Editorial 170     10.6
Sverre   Texas
Brubæk   Instruments   Editorial   169   10.6       21
Sverre   Texas
Brubæk   Instruments   Editorial   170   10.6.1.2   10
Sverre   Texas
Brubæk   Instruments   Editorial   170   10.6.1.4   13-15
Sverre   Texas
Brubæk   Instruments   Editorial   170   10.6.2.1   17
Sverre   Texas
Brubæk   Instruments   Editorial   170   10.6.2.2   22-25
Sverre   Texas
Brubæk   Instruments   Editorial   171   10.7       2-5
Sverre   Texas
Brubæk   Instruments   Technical 171     10.7       6-10
Sverre   Texas
Brubæk   Instruments   Editorial   171   10.7       15
Sverre   Texas
Brubæk   Instruments   Technical 171     10.7       17
Sverre   Texas
Brubæk   Instruments   Editorial   171   10.7       18
Sverre   Texas
Brubæk   Instruments   Editorial   171   10.7
Sverre   Texas
Brubæk   Instruments   Editorial   172   10.7       8
Sverre   Texas
Brubæk   Instruments   Technical 172     10.7.1     10-13
Sverre   Texas
Brubæk   Instruments   Editorial   172   10.9       26
Sverre   Texas
Brubæk   Instruments   Technical 173     10.10      8-9
Sverre   Texas
Brubæk   Instruments   Technical 173     10.10      11-12
Sverre   Texas
Brubæk   Instruments   Editorial   173   10.10      9
Sverre   Texas
Brubæk   Instruments   Editorial   173   10.10      12
Sverre   Texas
Brubæk   Instruments   Editorial   173   10.10      9
Sverre   Texas
Brubæk   Instruments   Editorial   173   10.10      12
Sverre   Texas
Brubæk   Instruments   Editorial   173   10.10      12
Sverre   Texas
Brubæk   Instruments   Editorial   174   10.10.3    4-5
Sverre   Texas
Brubæk   Instruments   Editorial   174   10.10.5    9-10
Sverre   Texas
Brubæk   Instruments   Editorial   174   10.10.7    13-14
Sverre   Texas
Brubæk   Instruments   Editorial   174   10.10.10   20
Sverre   Texas
Brubæk   Instruments   Technical 175     10.10.11   1-3
Sverre   Texas
Brubæk   Instruments   Editorial   175   10.10.12   5
Sverre   Texas
Brubæk   Instruments   Technical 175     10.11.1    14-20
Sverre   Texas
Brubæk   Instruments   Technical 175     10.11.1    14-20
Sverre   Texas
Brubæk   Instruments   Editorial   176   10.11.1    19-21
Sverre   Texas
Brubæk   Instruments   Technical 177     10.11.2    12-15
Sverre   Texas
Brubæk   Instruments   Editorial   177   10.11.2    6
Sverre   Texas
Brubæk   Instruments   Editorial   177   10.11.2    9
Sverre   Texas
Brubæk   Instruments   Technical 177     10.11.2    1-18
Sverre   Texas                   178-
Brubæk   Instruments   Technical 180     10.11.3
Sverre   Texas
Brubæk   Instruments   Editorial   178   10.11.3    5
Sverre   Texas
Brubæk   Instruments   Editorial   179   10.11.3.2   4-6
Sverre   Texas
Brubæk   Instruments   Technical 179     10.11.3.2   7
Sverre   Texas
Brubæk   Instruments   Technical 179     10.11.3.2   8
Sverre   Texas
Brubæk   Instruments   Editorial   180   10.11.3.2   1
Sverre   Texas
Brubæk   Instruments   Editorial   180   10.11.3.3   5-9
Sverre   Texas
Brubæk   Instruments   Editorial   180   10.11.4     12
Sverre   Texas
Brubæk   Instruments   Editorial   181   10.11.4     1
Sverre   Texas
Brubæk   Instruments   Technical 181     10.11.4     7-9
Sverre   Texas
Brubæk   Instruments   Editorial 181     10.11.4     10
Sverre   Texas                   181-
Brubæk   Instruments   Technical 182     10.11.4.3
Sverre   Texas
Brubæk   Instruments   Editorial   182   10.12       11
Sverre   Texas
Brubæk   Instruments   Technical 182     10.15.1     5-6
Sverre   Texas
Brubæk   Instruments   Editorial 182     10.15.1     7-9
Sverre   Texas                   187-
Brubæk   Instruments   Technical 188     10.15.3
Sverre   Texas
Brubæk   Instruments   Technical 188     10.16       20-33
Sverre   Texas
Brubæk   Instruments   Editorial   188   10.16.1     37
Sverre   Texas
Brubæk   Instruments   Technical 189     10.16.2     1-3
Sverre   Texas
Brubæk   Instruments   Editorial   189   10.16.3     6-7
Sverre   Texas
Brubæk   Instruments   Technical 189     10.16.3     10-11
Sverre   Texas
Brubæk   Instruments   Editorial   190   10.16.3
Sverre   Texas
Brubæk   Instruments   Editorial   190   10.17       7
Sverre   Texas
Brubæk   Instruments   Editorial   192   10.17       1-2
Sverre   Texas
Brubæk   Instruments   Editorial   192   10.17.4     16
Sverre   Texas
Brubæk   Instruments   Editorial   194   10.17.5     1-12
Sverre   Texas
Brubæk   Instruments   Technical 194     10.18       12-15
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas                   195-
Brubæk   Instruments   Technical 208     11
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.1   4
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.1   8-11
Sverre   Texas
Brubæk   Instruments   Technical 195     11.1   12
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.2   16
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.2   16-17
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.2   17
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.2   18
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.2   20
Sverre   Texas
Brubæk   Instruments   Editorial   195   11.2   footnote
Sverre   Texas
Brubæk   Instruments   Editorial   196   11.3   3
Sverre   Texas
Brubæk   Instruments   Editorial   196   11.3   3-4
Sverre   Texas
Brubæk   Instruments   Editorial   196   11.3   15
Sverre   Texas
Brubæk   Instruments   Technical 197     11.4   7
Sverre   Texas
Brubæk   Instruments   Editorial   197   11.4   6
Sverre   Texas
Brubæk   Instruments   Technical 197     11.4   2-6
Sverre   Texas
Brubæk   Instruments   Editorial   197    11.4     2-6
Sverre   Texas                     198-
Brubæk   Instruments   Editorial   199    11.4     6-8,1-3
Sverre   Texas
Brubæk   Instruments   Technical 199      11.5     14
Sverre   Texas
Brubæk   Instruments   Technical 199      11.5     18-19
Sverre   Texas
Brubæk   Instruments   Editorial   199    11.5     19
Sverre   Texas
Brubæk   Instruments   Technical 200      11.6     9
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6     1
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6     4
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6     4
Sverre   Texas
Brubæk   Instruments   Editorial   201    11.6     4
Sverre   Texas
Brubæk   Instruments   Editorial   201    11.6     4
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6     4
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6     4
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6     4
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6     4
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6.1   7
Sverre   Texas
Brubæk   Instruments   Editorial   201    11.6.1   7
Sverre   Texas
Brubæk   Instruments   Technical 201      11.6.1   7-10
Sverre   Texas
Brubæk   Instruments   Technical 202      11.6.1   1-2
Sverre   Texas                   201-
Brubæk   Instruments   Technical 202      11.6.1   7-10,1-2
Sverre   Texas
Brubæk   Instruments   Technical 202      11.6.2   4
Sverre   Texas
Brubæk   Instruments   Technical 202      11.6.2   4
Sverre   Texas
Brubæk   Instruments   Technical 202      11.6.2   3-7
Sverre   Texas
Brubæk   Instruments   Technical 202      11.7     11
Sverre   Texas
Brubæk   Instruments   Technical 202      11.7     16
Sverre   Texas
Brubæk   Instruments   Technical 203      11.7     5
Sverre   Texas
Brubæk   Instruments   Technical 203     11.8.1    9
Sverre   Texas
Brubæk   Instruments   Technical 203     11.8.1    11
Sverre   Texas
Brubæk   Instruments   Technical 204     11.8.1    4
Sverre   Texas
Brubæk   Instruments   Technical 204     11.8.1    1
Sverre   Texas
Brubæk   Instruments   Technical 204     11.81     9-10
Sverre   Texas
Brubæk   Instruments   Technical 205     11.8.2    5
Sverre   Texas
Brubæk   Instruments   Editorial   205   11.8.2    13
Sverre   Texas
Brubæk   Instruments   Technical 205     11.8.2    13
Sverre   Texas
Brubæk   Instruments   Technical 206     11.9.1    7
Sverre   Texas
Brubæk   Instruments   Technical 206     11.9.1    7
Sverre   Texas
Brubæk   Instruments   Technical 206     11.9.1    11
Sverre   Texas
Brubæk   Instruments   Technical 206     11.9.1    1-15
Sverre   Texas
Brubæk   Instruments   Technical 206     11.9.1    1-15
Sverre   Texas
Brubæk   Instruments   Technical 207     11.9.2    6
Sverre   Texas
Brubæk   Instruments   Technical 207     11.9.2    7
Sverre   Texas
Brubæk   Instruments   Technical 207     11.9.3    11
Sverre   Texas
Brubæk   Instruments   Technical 207     11.9.3    16
Sverre   Texas
Brubæk   Instruments   Editorial   207   11.9.3    16
Sverre   Texas
Brubæk   Instruments   Editorial   208   11.10.1   10
Sverre   Texas
Brubæk   Instruments   Technical 208     11.10.1   13
Sverre   Texas         Editorial 1       1
Brubæk   Instruments
Sverre   Texas         Editorial   3               6-11
Brubæk   Instruments
Sverre   Texas         Editorial   7     3         37
Brubæk   Instruments
Sverre   Texas         Editorial   13    5
Brubæk   Instruments
Sverre   Texas         Editorial   16    5.5.1.2   14-15
Brubæk   Instruments
Sverre   Texas         Editorial   16    5.5.1.3   23-24
Brubæk   Instruments
Sverre   Texas         Editorial   16   5.5.1.4      32
Brubæk   Instruments
Sverre   Texas         Editorial   19   6
Brubæk   Instruments
Sverre   Texas         Editorial   21   6.2.1.1.4    15-18
Brubæk   Instruments
Sverre   Texas         Editorial   22   6.2.1.1.6    4
Brubæk   Instruments
Sverre   Texas         Editorial   22   6.2.1.1.8    15
Brubæk   Instruments
Sverre   Texas         Editorial   22   6.2.1.1.8    15
Brubæk   Instruments
Sverre   Texas         Editorial   22   6.2.1.1.8    15
Brubæk   Instruments
Sverre   Texas         Technical 22     6.2.1.1.8    15
Brubæk   Instruments
Sverre   Texas         Editorial   23   6.2.1.1.10   35
Brubæk   Instruments
Sverre   Texas         Editorial   24   6.2.1.1.11   40
Brubæk   Instruments
Sverre   Texas         Technical 25     6.2.1.1.12   12
Brubæk   Instruments
Sverre   Texas         Technical 25     6.2.1.1.12   14-24
Brubæk   Instruments
Sverre   Texas         Technical 26     6.2.1.1.12   3
Brubæk   Instruments
Sverre   Texas         Editorial   26   6.2.2        15
Brubæk   Instruments
Sverre   Texas         Editorial   27   6.2.2.2      15
Brubæk   Instruments
Sverre   Texas         Editorial   27   6.2.2.2      17
Brubæk   Instruments
Sverre   Texas         Editorial   29   6.3.1.4      16
Brubæk   Instruments
Sverre   Texas         Editorial   29   6.3.1.6      28
Brubæk   Instruments
Sverre   Texas         Editorial   32   6.3.2.3      1-9
Brubæk   Instruments
Sverre   Texas         Editorial   32   6.3.2.3.1    6
Brubæk   Instruments
Sverre   Texas         Editorial   32   6.3.2.3.4    15
Brubæk   Instruments
Sverre   Texas         Editorial   43   6.3.7.3      1
Brubæk   Instruments
Sverre   Texas         Technical 45     6.3.8        1-2
Brubæk   Instruments
Sverre   Texas         Editorial   46   6.3.11.3     20
Brubæk   Instruments
Sverre   Texas         Technical 46     6.3.11.3     20
Brubæk   Instruments
Sverre   Texas         Editorial   47   6.3.11.4.1   1-22
Brubæk   Instruments
Sverre   Texas         Technical 47      6.3.11.4.1    1
Brubæk   Instruments
Sverre   Texas         Technical 47      6.3.11.4.1    2-6
Brubæk   Instruments
Sverre   Texas         Technical 47      6.3.11.4.1    1-22
Brubæk   Instruments
Sverre   Texas         Technical 48      6.3.11.5(b)   3-20
Brubæk   Instruments
Sverre   Texas         Technical 49      6.3.11.5.4    1-16
Brubæk   Instruments
Sverre   Texas         Technical 49      6.3.11.5.4    17
Brubæk   Instruments
Sverre   Texas         Editorial   49    6.3.11.5.4    2
Brubæk   Instruments
Sverre   Texas         Technical 52      6.4.6.4       5
Brubæk   Instruments
Sverre   Texas         Technical 52      6.4.6.4       4-8
Brubæk   Instruments
Sverre   Texas         Technical 52-53   6.4.8
Brubæk   Instruments
Sverre   Texas         Editorial   57    6.6.2.3       11
Brubæk   Instruments
Sverre   Texas         Editorial   57    6.6.2.3       11
Brubæk   Instruments
Sverre   Texas         Editorial   57    6.6.2.3       13
Brubæk   Instruments
Sverre   Texas         Editorial   58    6.7.1         5
Brubæk   Instruments
Sverre   Texas         Technical 58      6.7.1         6
Brubæk   Instruments
Sverre   Texas         Editorial   58    6.7.1.1       10-11
Brubæk   Instruments
Sverre   Texas         Editorial   59    6.7.1.2       3
Brubæk   Instruments
Sverre   Texas         Technical 59
Brubæk   Instruments
Sverre   Texas         Editorial   59    6.7.2         13
Brubæk   Instruments
Sverre   Texas         Editorial   61    6.7.5         15
Brubæk   Instruments
Sverre   Texas         Technical 66      6.7.11        5
Brubæk   Instruments
Sverre   Texas         Technical 66      6.7.11        8-9
Brubæk   Instruments
Sverre   Texas         Technical 72      7.2.7         15
Brubæk   Instruments
Sverre   Texas         Editorial   74    7.2.7.4       21
Brubæk   Instruments
Sverre   Texas         Editorial   74    7.2.7.4       23-24
Brubæk   Instruments
Sverre   Texas         Editorial   75    7.2.7.4       1-2
Brubæk   Instruments
Sverre   Texas         Technical 77     7.3.1       76
Brubæk   Instruments
Sverre   Texas         Editorial   78   7.4         28
Brubæk   Instruments
Sverre   Texas         Editorial   78   7.4         32
Brubæk   Instruments
Sverre   Texas         Editorial   78   7.4         36
Brubæk   Instruments
Sverre   Texas         Technical 79     7.4         1-2
Brubæk   Instruments
Sverre   Texas         Editorial   83   7.5.2.1     30
Brubæk   Instruments
Sverre   Texas         Editorial   85   7.6.2       1
Brubæk   Instruments
Sverre   Texas         Editorial   85   7.6.2       1
Brubæk   Instruments
Sverre   Texas         Editorial   86   7.6.2.1.1   1
Brubæk   Instruments
Sverre   Texas         Editorial   89   7.7.1       20-21
Brubæk   Instruments
Sverre   Texas         Editorial   89   7.7.1       22
Brubæk   Instruments
Sverre   Texas         Editorial   91   7.7.2       9-17
Brubæk   Instruments
Sverre   Texas         Editorial   92   7.7.5       25
Brubæk   Instruments
Sverre   Texas         Technical 94     7.8.2.1.1   20-22
Brubæk   Instruments
Sverre   Texas         Technical 94     7.8.2.1.2   24-28
Brubæk   Instruments
Sverre   Texas         Technical 95     7.8.2.1.2   1-4
Brubæk   Instruments
Sverre   Texas         Technical 95     7.8.2.1.2   5-19
Brubæk   Instruments
Sverre   Texas         Editorial   95   7.8.2.1.3   21
Brubæk   Instruments
Sverre   Texas         Editorial   95   7.8.2.1.3   21
Brubæk   Instruments
Sverre   Texas         Editorial   95   7.8.2.1.3   22
Brubæk   Instruments
Sverre   Texas         Editorial   95   7.8.2.1.3   27
Brubæk   Instruments
Sverre   Texas         Technical 95     7.8.2.1.3   28
Brubæk   Instruments
Sverre   Texas         Technical 96     7.8.2.1.3   1
Brubæk   Instruments
Sverre   Texas         Technical 96     7.8.2.1.4   9
Brubæk   Instruments
Sverre   Texas         Technical 96     7.8.2.1.4   9-29
Brubæk   Instruments
Sverre   Texas         Editorial   97   7.8.3       17
Brubæk   Instruments
Sverre   Texas         Editorial   97    7.8.3      18-19
Brubæk   Instruments
Sverre   Texas         Editorial   98    7.8.3      6
Brubæk   Instruments
Sverre   Texas         Technical 98      7.9        7
Brubæk   Instruments
Sverre   Texas         Editorial   107   7.12       26-30
Brubæk   Instruments
Sverre   Texas         Technical 111     7.12.3     15
Brubæk   Instruments
Sverre   Texas         Editorial   111   7.12.3     15
Brubæk   Instruments
Sverre   Texas         Technical 111     7.12.3     16-17
Brubæk   Instruments
Sverre   Texas         Technical 112     7.12.3     1-10
Brubæk   Instruments
Sverre   Texas         Technical 112     7.12.3     11-25
Brubæk   Instruments
Sverre   Texas         Technical 112     7.12.3     26-33
Brubæk   Instruments
Sverre   Texas         Technical 112     7.12.3     34-37
Brubæk   Instruments
Sverre   Texas         Technical 112     7.12.3.1   38
Brubæk   Instruments
Sverre   Texas         Technical 112     7.12.3.1   39-40
Brubæk   Instruments
Sverre   Texas         Technical 112     7.12.3.1   41-45
Brubæk   Instruments
Sverre   Texas         Technical 113     7.12.3.1   1-17
Brubæk   Instruments
Sverre   Texas         Technical 113     7.12.3.2   18-31
Brubæk   Instruments
Sverre   Texas         Technical 113     7.12.3.3   32
Brubæk   Instruments
Sverre   Texas         Technical 113     7.12.3.3   33-44
Brubæk   Instruments
Sverre   Texas         Technical 114     7.12.3.3   1-2
Brubæk   Instruments
Sverre   Texas         Technical 114     7.12.4     3
Brubæk   Instruments
Sverre   Texas         Technical 114     7.12.4     4-24
Brubæk   Instruments
Sverre   Texas         Technical 114     7.12.4     25
Brubæk   Instruments
Sverre   Texas         Technical 115     7.13.2     6-39
Brubæk   Instruments
Sverre   Texas         Technical 117     7.13.4     1
Brubæk   Instruments
Sverre   Texas         Technical 117     7.13.4     1
Brubæk   Instruments
Sverre   Texas         Technical 117     7.13.4     1
Brubæk   Instruments
Sverre   Texas         Technical 117     7.13.4      1
Brubæk   Instruments
Sverre   Texas         Editorial   117   7.13.4      1
Brubæk   Instruments
Sverre   Texas         Technical 117     7.13.4      1
Brubæk   Instruments
Sverre   Texas         Editorial   118   7.13.4      1
Brubæk   Instruments
Sverre   Texas         Editorial   118   7.13.4      1
Brubæk   Instruments
Sverre   Texas         Technical 118     7.13.4      1
Brubæk   Instruments
Sverre   Texas         Technical 118     7.13.4      1
Brubæk   Instruments
Sverre   Texas         Editorial   119   8           12
Brubæk   Instruments
Sverre   Texas         Editorial   119   8.1         17
Brubæk   Instruments
Sverre   Texas         Editorial   119   8
Brubæk   Instruments
Sverre   Texas         Editorial   121   8.1.2       29-30
Brubæk   Instruments
Sverre   Texas         Editorial   124   8.1.3       18-19
Brubæk   Instruments
Sverre   Texas         Editorial   124   8.1.4       17-18
Brubæk   Instruments
Sverre   Texas         Editorial   126   8.1.4       12
Brubæk   Instruments
Sverre   Texas         Editorial   129   8.1.5       22
Brubæk   Instruments
Sverre   Texas         Editorial   134   8.3.1       11
Brubæk   Instruments
Sverre   Texas         Editorial   134   8.3.1       12-22
Brubæk   Instruments
Sverre   Texas         Editorial   156   9.6.1       14-17
Brubæk   Instruments
Sverre   Texas         Editorial         9, 10, 11
Brubæk   Instruments
Sverre   Texas         Editorial   164   10          14
Brubæk   Instruments
Sverre   Texas         Technical 165     10.2        5
Brubæk   Instruments
Sverre   Texas         Technical 165     10.3        17-22
Brubæk   Instruments
Sverre   Texas         Technical 165     10.3        23-29
Brubæk   Instruments
Sverre   Texas         Technical 165     10.5        16-17
Brubæk   Instruments
Sverre   Texas         Technical 166     10.4        4
Brubæk   Instruments
Sverre   Texas         Technical 166     10.5.1      21
Brubæk   Instruments
Sverre       Texas         Technical   166   10.5.1      21-23
Brubæk       Instruments
Sverre       Texas         Technical   170   10.6.1      1-2
Brubæk       Instruments
Sverre       Texas         Technical   171   10.7        9-10
Brubæk       Instruments
Sverre       Texas         Technical   171   10.7        11-12
Brubæk       Instruments
Sverre       Texas         Editorial   188   10.16.1     34
Brubæk       Instruments
Sverre       Texas         Editorial   189   10.16.2     1
Brubæk       Instruments
Sverre       Texas         Technical   189   10.16.2     1
Brubæk       Instruments
Sverre       Texas         Editorial   189   10.16.3     6-7
Brubæk       Instruments
Sverre       Texas         Technical   189   10.16.3
Brubæk       Instruments
Sverre       Texas         Technical   189   10.16.3     10-11
Brubæk       Instruments
Sverre       Texas         Technical   190   10.16.3     1
Brubæk       Instruments
Sverre       Texas         Technical   195   11.2        21-23
Brubæk       Instruments
Taehan Bae   Samsung Electronics
                           editorial   160   9.7.8       15
Taehan Bae   Samsung Electronics
                           Editorial   173   10.1        2
                                                         Figure
Taehan Bae Samsung Electronics
                          Editorial    180   10.11.4     127
              Meiji
Tetsushi Ikegami Univ.    Editorial    173   10.1        Table 55
              Meiji
Tetsushi Ikegami Univ.    Editorial    180   10.11.4     Figure 127
              Meiji
Tetsushi Ikegami Univ.    Technical    181   10.11.4.3
              Meiji
Tetsushi Ikegami Univ.    Technical    182   10.11.4.3   line 2
Tetsushi Ikegami
              NICT        Technical    182   10.13       line 16
                          Technical
Tim Schmidl Texas Instruments          164   10.1.1      26
Comment                                        Proposed Change

                                             Normative text should be added to describing
                                             which parts are mandatory and optional.
Missing normative techical document that     Include a section that describes each of the
describes which PHYs are mandatory/optional. PHYs and how they are required to operate
And how they are required to operate with a  with on MAC. Generate a refernence table, or
single MAC.                                  reference the ISO diagram.


Define "PTK"


Skinny, heavy not appropriate                  Use terms that are more general


reference H1, H2                               Add respective hubs "(H1, H2)"

Figure 2 refenences the hub. No reference to Add reference to node, and remove "client" or
the node. However the MAC client is reference define the node as the client

there's a mix of logical statements Set to 1 and Global change: choose one discriptor
set to "one"                                     throughout document preferrably text


Table 3: b6-b7 not defined or reference        Define

                                               Change "It is set" to "when set to zero the
Reference to "it' on lines 4 through 22        node"


Figure 11 missing "# of bits"                  Add "# of bits"


Figure 11 missing "# of bits"                  Add "# of bits"


missing "(LSB)"                                add least-significant bit "(LSB)"


missing "(MSB)"                                add most-significant bit "(MSB)"


Figure 13 missing "LSB", "MSB"                 Add reference

missing figure showing polynomial connection,
and LSB, MSB logical connection and flow      Add reference diagram

                                               add "# of octets" Global change in technical
Figure 14 missing # of octets                  document
"being run" is ambigous                          Change "being run" to "type"


"PkY" case                                       Change to "PKx"


"Nibble" not defined                             Define in definition section

" = 1" should be change to text to be consistent
throughout the document                          Change "=1" to "When set to one"

" = 0" should be changed to text to be
consistent throughout the document               Change "=0" to "When set to zero"


mix of bit discriptors throughout the document   Global change: change "two bit" to "2-bit"


                                                 Remove character " [ "
                                                 Add Capability Element that defines the
Table 15 Missing "Capability Element" that       number of PHYs supported by the Node. It is
defines how many PHYs are supported by the       possible for a mfg to develop and offer a multi-
"node".                                          mode product.


change "1" to "one" and "0" to zero              Make global change


Figure 105                                       Fix text alignment fo text
Japan and Canada omitted ie 2400MHz is
applicable in Canada under Industry Canada
operating rules. Listing Japan may be useful     Include Japan and Canada with reference to
for other bands                                  regulatory domains

Tables 26 through Table 32 needs alignment
of text                                          Align text in Tables


Extra period                                      remove character " . "
                                                  Add text: The PLCP header shall be
The section is related to generating PLCP         constructed "for transmission" as shown in
header for transmission the receiver is different Figure 106

Figure 106 is for transmission. Title needs to   Add text to title of figure: Block diagram of
be clarified as such                             PLCP header construction "for Tx"

                                                 Change text: "An example" schematic o fthe
Clarification                                    processor order….
Figure 110 is for transmission. Title needs to    Add text in figure title: Block diagram of PSDU
be clarified of such                              construction "for Tx"

No mention of how many bits are needed to         Add statement for how many bits are needed
flush the scrambler.                              for timing consideration
                                                  Add transmit mask for each band to be
Graphical plot of Transmit Mask missing for       consistance with other PHYs in the
each of the frequency bands and regulatory        ammendment on other IEEE 802 standards
domains                                           and ammendments

                                                  change text: applications shall "be given"
Clarification                                     higher priority


Clarification                                     Change "media" to "medium"

                                                  Change Figure 117 title to : PSDU construction
Figure 117 is for transmission                    "for Tx"

No mention of how many bits are needed to       Add statement for how many bits are needed
flush the scrambler when transmitting a packet. for timing consideration

In complete sentence. Missing period or
additional phrase.
                                                  Provide a description of a Piconet in the
Piconet is discussed in general terms wrt a       Clause 3.0 Definitions. Add text and illustration
BAN. but not defined. Pioconet should be          to support how Piconets are part of the BAN
defined early on in the draft as part of the      Network Topology, in Clause 5.2 Network
Network Topology                                  topology page 13.

Figure 89 missing input and output for channel
hopping sequence generation                    Update drawing and text describing operation


Table 21 allign and format text


                                            Add to be and define in Clause 3.0 Definitions
Table 13: The Command Name(s) in the Table, needin text defined

                                               Unless main authors participate attend all to build a transmitter, let alone dram
HBC text is not close to being complete, many missing sections and technically impossiblefuture meetings, and commit to a rec

                                               Insert a section that defines the operating frequency bands
A section on operating frequency bands is missing

A section on channel numbering is missing         Insert a section that defines the channel numbers and center frequencies

                                               Insert a EDTime, CCATime, Channel Switch Time, etc.)
A section on PHY layer timing is missing (pSIFS, pMIFS,section that defines the PHY layer timing

                                                Insert a etc.)
A section on inter-frame spacing is missing (SIFS, MIFS,section that defines the inter-frame spacing

                                                  Insert sections on rx-to-tx, tx-to-rx turnaround times
Sections on rx-to-tx, tx-to-rx turnaround times are missing
                                                 Insert
A section of center frequency switch time is missing a section on center frequency switch time

                                                Insert sections on is missing
Sections on transmit center and symbol clock frequency tolerancestransmit center and symbol clock frequency tolerances

                                                  is missing
Section of transmitter constellation error or EVMInsert a section on transmitter constellation error or EVM

                                                Insert
A section on adjacent channel power ratio is missing a section on adjacent channel power ratio

                                                 Insert a section on adjacent channel rejection
A section on adjacent channel rejection is missing

                                               Add ED measurement time and receiver clear channel assessment are missin
Sections on receiver energy detection, ED threshold, seections on receiver energy detection, ED threshold, ED measurement ti

                                             Pick either HBC or to the reader
HBC and EFC are used interchangeably and this leads to confusionEFC and use it consistently throughout spec. Preference is

                                             Remove the paragraph altogether
This paragraph assumes a particular implementation, which should not be included in a standards

Change bandwidth is 8 MHz, not 4 MHz             Replace "with the bandwidth of 4MHz" by "with the bandwidth of 8MHz"

                                             Replace "Header" with "PLCP Header"
The header should be referred to as a PLCP Header

                                                Remove
PHY Payload is not a typical term in IEEE 802 standards PHY Payload and just replace it with PSDU

Shouldn‘t used "And" to start a sentence         Replace "And PHY Payload" with "The PSDU"

Grammar is awkward                               Replace "The packet structure with PHY Header fields is shown …" with "The P

Figure 139 is not correct                        Replace PHY Header with PLCP Header, and PHY Payload with PSDU and sh

HBC has not been approved in any countries       change "many" to "any"

                                                 Remove last part of sentence: "and transmitted value
Aren't the signal transmitted actually analog? The last part of sentence is confusing and adds noin digital form"

                                              the dominant frequency? What
Don‘t understand the second sentence. What is Clarify by rewritting sentence does it mean? What does it mean to say "most

Grammar is awkward                               Need to insert a "the" between "Since" and "preamble"

Figure 142, what is f_ck?                        Define the values for f_ck

Typo: fCK                                        Replace with f_ck

                                             Please clarify. Can't built a transmitter unless it is known how to is the the Gold
How are the various preambles selected? How do you select which Gold Code polynomial? Who does selection, select PHY ba

                                               Please section
Paragraph is very confusing and hard to understand thisrewrite to clarify

                                                  Remove paragraph, Figure 143
This text doesn't belong in a standard. This text belongs in an academic paper and last line after figure

Figure 144, what is f_ck?                        Define the values for f_ck

                                             Please clarify. Can't built a transmitter unless it is parameter? Or is it the MAC?
How do you select which Gold Code polynomial? Who does selection, is the PHY based on some known how to select the Gold

Reference is missing                             Replace "0" with "Table 70"?
What is DRF?                                        Define DRF. Also define how DRF is selected? Who makes decision PHY or M

Is spreading factor 64 for this section? Why?       Clarify

Is Table 71 for DRF or RI? It is not clear?         Clarify

                                                 Bits should be mapped
How are bits in table mapped to the fields? Is LSB first? Or MSB first? LSB first

                                                      Replace "3 ~ 4" with "3 ~ 5"
Bit position 3 ~ 4 is only 2 bits, but 3 bits are defined

"-" doesn't imply reserved                          Replace "-" with "Reserved"

                                                 "no 01 for
Why are two bit values for sync (00,01) used for Use sync"? no sync and 00 for a Reserved value

                                              Clarify
What is difference between normal and dedicated mode? Why is it needed? Who makes decision (PHY or MAC) to use norma

                                              Clarify
Why are there 3 bits used for BAN ID? How are the BAN ID assigned? Does this mean that 8 simultaneously operating piconet

CRC8 is undefined                                   Please specify the CRC8 polynomial and how it is implemented

                                                Replace "master device and be more generic
Why does this field need to be specified for master and slave devices, shouldslave nodes" with "two devices"

"1x" notation is confusing                          Replace "is set to 1x" with "has a one in the first bit of the field"

                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                                     Specify
What happens if the first bit is set to zero (i.e. no-sync)? text for the condition when the first bit is zero (i.e. no sync)

                                                Replace "master device and particular slave
Why does this field need to be specified for master and slave devices, shouldabe more generic device" with "two devices"

What does 1:1 mean?                                 Explain and clarify

                                            Remore the dedicated device be section 11.6.2
Why is a dedicated mode needed? This is a TDD system, why would a mode and communicating at the same time as another d

                                             Define
What is C, N and L? These values should be specified C, N and L and their values

                                               Define the
What is FSC for this section? What values can be used? FSC values

C, N and L should be defined in Table 73            Define C, N and L in Table 73

Where was Data Rate Field (DRF) defined?            Please define DRF or reference section where DRF was defined

                                           Please clarify or PHY HDR structure for DRP mode and for RI mode
When is RI used? How is PHY HDR modified when RI is used thedoes it remain the same?

"garbage bits" is a terrible term                   Please replace "garbage bits" with something better, like "RI bits"

                                             Please specify how How "garbage bits" are used in T_offset
Figure 147, how many "garbage bits" proceed SFD code T_offset1? manymany before T_offset2? ... How many before T_offse

                                               Please clarify
Need more detail in last sentence. How does a device know that an SFD/RI is being used or an SFD/DRF is being used. Once
                                               Please clarify
Which SFD sequence is used for the pilots? Is the SFD/DRF or SFD/RI? Does it include "garbage bits"

Bit pattern 111 is missing from Table 75            Define bit pattern 111 as Reserved

                                                  Please clarify
What if bit pattern 011 is selected but the payload is less than 128 bytes, do you still insert the pilot pattern?

Typo: fBW                                           Replace "fBW" with "f_BW"

What is the value of f_BW?                          Clarify that f_BW = 8 MHz

                                                    Please replace this TG6. The correct figure can which should have a value of
Figure 149 is incorrect. This is not from the text that was adopted byfigure with the correct figure, be found in document 15-10-2

                                                Update text and found
Text should be updated to match the correct figure, which can befigure in document 15-10-201-02, where the limits should be

                                              Current mask
Where is the TX mask for a center frequency f_c = 27 MHz only works for f_c = 16 MHz and not f_c = 27 MHz. Please upda

                                               or equal to a maximum, not -12 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -12 dBm"

                                               or equal to a maximum, not -39 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -39 dBm"

                                                Please state all clock frequencies that can be used with this chapter
Is the clock frequency 64 MHz for this chapter? Or is it some other number?

                                                 Please means or update numbers refer to and how they should be
Table 77 is confusing. I don't understand what the table clarify andwhat thetable with additional text to improve clarity used in de

                                                Editor please pick either octet or byte and stick with it throughout document
In some places octets are used, in other places bytes are used

                                                   not just less than
PER is usually specified as less than or equal to,Replace "lessthan 1%" by "less than equal to 1%"

                                                 Update sensitivity = -11 dB with correct numbers. Proponents should bring a lin
Table 79 - sensitivity numbers are way too low, they imply an SNR numbers for the modulation scheme, which does not include

                                              Either remove the Management Entity or present bounds, functionality and int
Reference model Figure and text includes a "Management Entity" that may or may not be clarify itsand may or may not do some

                                             Consider whether
General comment: MAC is quite complicated, with lots of options. simpler scheme would be more appropriate to the goal of sm

                                                       Make bit field definitions conform to IEEE norms.
After familiarity with 802.15.4 it is a little confusing to see bit fields in tables (e.g. Table 1 and Table 2) listed with low order bits

                                               Make to field definitions conform the other way arouind in IEEE for 802.15.4-2
Same comment again for Table 3: bitfield order differs bit norm, i.e. the ordering is to IEEE norms. (Please checkStd and corere

CCITT is now called ITU-T                           Change "CCITT" to "ITU-T"

Typo Table-14 Data "rage" field...                  change "rage" to "rate"

                                                Add HBC PHY and PHY has multiple data rates.
HBC PHY not represented in table - it has multiple data rates. UWB data rates, and add UWB phy data rates

                                              Specify a time so that TX is not allowed to begin To allow remote RX allowed
A mimimum time should be specified for RX to TX turn-around,before which TX should not begin. immediately. If TX is time to

                                                  Replace It has very similar bit-rates to 802.15.4a with statement saying somet
The IR-UWB PHY defined in this section is unnecessary. the IR-UWB PHY section (section 10), with a similar complexity, but it
                                                  Consolidate type-I and polled polled allocation. If not, justify the need for both
The function of type-II polled allocation can be achieved by using type-I type-II allocation.
                                                  Consolidate in clause frames.
There is not much difference between the Poll frame defined these two 6.4.5 and the Wakeup frame defined in clause 6.4.7.
"High QoS mode" is mentioned but not defined. Define "High QoS mode".
The definition of "association" is ambiguous.     Change "security association." to "A term synonymous to security association i
A period is missing after the definition.           Add a period after the definition.
A period is missing after the definition.           Add a period after the definition.
                                                    Add a definition of "wakeup arrangement " to clause 3. It is an important conce
The phrase "wakeup arrangement" is not listed in clause 3.
Word misspelled.                                    Change "curren" to "current"
Period missing.                                     Add a period to the end of the sentence.
Errant character.                                   Delete "6." from the front of the sentence.
                                                    Add descriptive text for the Camellia-128 7).
Clause 8 does not specify the Camellia-128 forward cipher function (as illustrated in Tableforward cipher function in clause 8 or
                                                    For the Connection bit fields for wakeup (i.e., the 1 bit field names to "Wakeup
Figure 24 (Connection Change Indicator Format) contains several 1 Change Indicator, changeWakeup Phase, Wakeup Period)
                                                    Add a definition
The term "piconet" is not defined prior to first use in Figure 29. of "piconet " to clause 3.
                                                      use.
The term "coordinator" is not defined prior to firstAdd a definition of "coordinator" to clause 3. Add explanatory text contrasting a
Errant character.                                   Delete "(b)" after the clause number.
                                                    Add a definition of "low power wakeup radio" to clause 3. Add explanatory text
The term "low power wakeup radio" is not defined. First use in Figure 37.
                                                    Update table with information for other modes of data rates, it
The table lists UWB; a mode that is not defined in subclause 9.1. The table lists no optional UWB the standard. also does not lis
                                                    Delete a published standard.
The question "Not acknowledged??" is inappropriate forquestion or add additional detail to the subclause.
                                                    Specify how "a new channel" be compliant with Listen Before Talk (LBT) and
This subclause appears to assume those implementing the IEEE standard willwill be selected. An option is to reference clause
                                                      Figure time durations.
The time durations for T-Poll and (node) listen inSpecify 72 are unclear.
                                                    Specify how Listen Before Talk (LBT)/Least Interfered Channel (LIC) assessm
The language describing channel selection is ambiguous.
                                                    Specify if
It is unclear how a switch to another channel is performed.Listen Before Talk (LBT)/Least Interfered Channel (LIC) assessment
                                                    Provide packet timing and duration for Wakeup, sniffing (i.e., Device listening i
Figure 75 and associated text lacks sufficient timing details.
                                                    Provide specific timing for Poll, Ack and their durations.
Figure 76 and associated text lacks sufficient timing details.
                                                    Populate with for HBC/EFC "Regulatory Rules"
Table 21 contains the phrase "Undefined at the time of writing"regulatory requirements (this is probably not possible until the FC
                                                    Change to "No applicability given "Beacon Shifting"
Table 21 includes the phrase "Limited / No applicability given LBT restrictions" for LBT restrictions" and MICS band communic
                                                    Change sharing" and MICS band communication.
Table 21 includes the code of "S" for "Active piconet timeto "No applicability given MICS regulations" (relay functionality is not p
                                                    The defined in clause 8.1.
Susceptibility of key distribution/association schemeskey distribution/association schemes are aligned (or closely similar to) with
                                                    Define a SRRC filter for the the transmitter.
The standard does not define a Square Root Raised Cosine (SRRC) filter fortransmitter - if nothing else, to enable EVM measu
                                                    Typical EIRP for certified implant interfering with implants (nodes) communica
The ACPR levels for MICS band operation are not adequate to prevent hubs from transmitters is very low: 1.2 nW for FCC ID P
                                                    Subclause 9.8.4 should be renamed subclause 9.8.3.1.
The subclause numbering should align with the subject area.
                                                    Add additional requirements to ensure compliance compliant with standards (
Specifying details for "ED Threshold" is key to ensuring interoperabililty with existing MICS systems with worldwide regulationssu
                                                    Subclause 9.8.5 should be renamed subclause 9.8.3.2.
The subclause numbering should align with the subject area.
                                                      key to ensuring interoperabililty with existing MICS systems compliant with sta
Specifying details for "ED Measurement Time" isAdd additional requirements to ensure compliance with worldwide regulations (
                                                    Add a table that includes frequency bands; update reference.
The text refers to "table 10" but no similar table is found in the clause.
                                                    Add
The abbreviation for HBC is not included in clause 4. HBC to clause 4.
                                                    the HBC PHY to mitigate long for HBC.
There is no data scrambling function defined for Define a scrambling approach strings of 1s or 0s (or systemic patterns) as they
                                                    Add
The abbreviation for EFC is not included in clause 4. EFC to clause 4.
                                                    Add
The abbreviation for SFD is not included in clause 4. SFD to clause 4.
                                                    Revise the entire subclause to describe the method of transforming a PSDU in
The description of packat format is ambiguous and does not conform to standard IEEE 802 conventions.
                                                    Add FSDT to clause 4.
The abbreviation for FSDT is not included in clause 4.
                                                    Add 4.
The abbreviation for FSD/RI is not included in clause FSD/RI to clause 4.
                                                    Add
The abbreviation for S2P is not included in clause 4. S2P to clause 4.
                                                    Add FS-Spreader to clause 4.
The abbreviation for FS-Spreader is not included in clause 4.
                                                    Add
The abbreviation for MUX is not included in clause 4.MUX to clause 4.
                                                    Add is not included in
As illustrated in Figure 140, the abbreviation for MCUMCU to clause 4. clause 4.
                                                     4.
The abbreviation for SF is not included in clauseAdd SF to clause 4.
                                                    Modify other usage (e.g., Figure
The character for clock frequency is not consistent with to make "CK" a subscript.142)
                                                    An upsample by 4 block should be inserted after the Gold Code block in Figure
The signal processing outlined in Figure 142 is not clear.
                                                    Add explanatory polynomials as defined in Table 65.
The text does not explain the reason(s) for having two Gold Codetext.
                                                    Add explanatory text.
The purpose of Table 66 is not clearly defined. Since it is 128 bits in length, is this the Gold Code sequence? From one of the p
                                                     If [1,0,1,0] is defined for a FSC Code and 0, then is not a second with for
Table 67 does not contain sufficient information. Add column titles to clarify Gold inputsbit of outputs.it Defineconsistent table the
                                                    Delete text, Figure 143, and line 4 requirement(s).
The text and associated figure (Figure 143) are informative and do not convey any on page 199. Further, the figure only appe
                                                    Clarify
The "time offset" concept is not adequately explained. if the "time offset" is a circular shift of the Gold Code, or some other sign
                                                    An upsample by 4 block should be inserted after the Time Offset block in Figur
The signal processing outlined in Figure 144 is not clear.
                                                  Add explanatory polynomials as defined in Table 68.
The text does not explain the reason(s) for having two Gold Codetext.
                                                  Add explanatory text.
The purpose of Table 69 is not clearly defined. Since it is 128 bits in length, is this the Gold Code sequence? From one of the p
Table 70 does not contain sufficient information.Add column titles to clarify FSC inputs and outputs. Define a second table for
                                                  Add
The abbreviation for DRF is not included in clause 4. DRF to clause 4.
                                                  Add explanatory text.
The signal processing outlined in Figure 145 is not clear. Is the spreading factor (SF) for FSC equal to 64 in this figure?
                                                  Add a figure not defined.
The transmit order of header parameters listed in Table 71 is clearly defining the transmit order of header parameters.
                                                  Add reference.
Bit 8 "D" in Table 71 does not have a reference (empty parenthesis)
Error in the entry for Pilot Info.                Bit Position "3 - 4" should read "3 - 5"
"1x" is underfined.                               Change "1x" to read "10 or 11"
                                                  Recommend inclusion of the terms in clause 3. Add explanatory text in this su
The terms "chip" and "slot" in the context of HBC are not defined.
                                                  Recommend inclusion the terms in clause the operation with broadcast fram
The terms "chip" and "slot" in the context of HBC are not defined. Lack of definition regarding 3. Add explanatory text in this su
                                                  Recommend changes to align
The terms "master" and "slave" are inappropriate to use in a PHY description. with other sub-clauses (i.e., "hub" and "node").
                                                  Add explanatory document: C, N, L, r0:r15.
Referring to Figure 146, the following terms are not defined in thetext.
                                                  Change the term "Garbage" to "All 1s" or some other descriptive phrase.
The use of the term "Garbage" is inaccurate; these bits are defined.
                                                  Verify the insertion of pilot signals is optional.
The use of the term "can" implies an option for implementation.
                                                  Further liaison with members therapy in the large population industry to esta
The low-frequency spectral mask may not be sufficient to prevent suspension of the implantable medical deviceof patients with
The bandwidth (fBW) is not defined in the clause. Define the signal's bandwidth.
                                                  Use subscripts for center frequency and bandwidth.
The terms defined in these two lines do not match those in Figure 149.
Need to clarify the mask is a requirement.        Change "recommended" to "required" at the beginning of line 8.
                                                  Publish a MHz.
The document does not define a spectral mask for f c = 27 similar mask for fc = 27 MHz.
                                                  The text states "should" and "can"
Need to clarify if conducted and radiated power measurement are both required. indicating an optional subclause. Please cla
The term "far apart" is ambiguous.                Add additional detail.
                                                  Define specific output power limits fact, the standard only requires minimum va
The standard does not define limits for "conduction power" nor "radiation power"; in for HBC transmitters. These parameters are
                                                  Add instead of variable
The sentence "Pilot symbol enables stable operation explanatory text. clock frequency tolerance." does not provide sufficient
                                                  Add requirement.
The terms "allowed" and "example" do not indicate a terms such as "shall" to indicate the appropriate requirement.
                                                  Remove the "Relay This field cannot be used in a reliable way in presence of
The use of a signal strength to define the link quality is questionable.Link Quality" field or find another way to measure the link q
                                                  Remove it or add some text.
This clause is missing some text and need further explanation.

The SFD is not defined                            Define the SFD structure

                                              Replace It has very similar bit-rates to 802.15.4a with statement saying somet
The IR-UWB PHY defined in this section is unnecessary. the IR-UWB PHY section (section 10), with a similar complexity, but it

                                                         so this mean that comments.
There are 3 bits used for BAN ID parameter, andPlease clarify w/r/t 8 simultaneous BANs/piconets can coexist.
Note 3 incorrectly defines NIST                       Change for to of
                                                      Use one term only (e.g. active state (not awake) and inactive (15-10-0324-00-0
The entire clause 3 defines multiple terms for the same thing, which violates the 802.15 OM (LB54) clause 11 state (not hiberna
There is no mMaxBANSizes in Table 23                  Correct term by deleting the final "s" to agree with the name in Table 23
                                                      Change correct
There are two items in the subject verb agreement is not is to are
                                                      Insert Master Key
Use of first occurrence of an acronym (MK) must be spelled out
exclusieve is misspelled                              correct
curren is misspelled                                  correct
                                                      Table 3 header row, add carriage return
Table 3 header row, add carriage return so that b0 is on the same line with b1 b2 and b3 so that b0 is on the same line with b1
What is the 6. Doing on this line?                    Delete
                                                      Select one term
Table 4 third column is named Beacon Shifting Sequence pattern, while the text states Beacon Shifting Sequence Phase terms
                                                      Insert another field in Figure 14, which indicates whether the to Figure 14. Thi
The text states that this field is present only if the channel hopping is currently enabled as encoded according Channel Hopping
                                                       in Figure 17 is marked greater than or equal to or equal to in Figure
The length of the Security Association Date field Correct inconsistency by changing greater than 0, however 0 to 72 19 page 1
Header is not consistent with name in Figure 18 Delete Protocol
Use subscript for the Y                               Beacon Shifting Sequence
Wrong level of indent                                 Change level of indent to same as the other four fields from figure 20
Wrong level of indent                                 Change level of indent to same as the other four fields from figure 20
                                                        indicates that one
Is this index a single bit or multiple bits? Line 18Fix inconsistency can subtract 1 for the value, while line 22 indicates that it ha
                                                        indicates that one
Is this index a single bit or multiple bits? Line 18Fix inconsistency can subtract 1 for the value, while line 22 indicates that it ha
                                                    Delete 2 byte field allowing for the coding of 256 naturally?
Why is there a need to code 256 as zero, when this is aentire sentence
                                                    Correct cross reference and guarantee Phase field uniqueness
Cross reference is wrong. It points to a 1-bit Wakeip Phase field, not a 2-octet Wakeup that there is as in 6.3.6.7 in field naming
                                                    Correct cross reference and guarantee Period field uniqueness
Cross reference is wrong. It points to a 1-bit Wakeip Period field, not a 2-octet Wakeup that there is as in 6.3.6.8in field naming
Cross reference is wrong.                           Change 6.7.11 to 6.7.12
                                                    Properly
Figure 26 contains two fields that are not defined in 6.3.7 define the missing fields (B+EAP1 Length, EAP2 Length)
Wrong level of indent                               Indent level should be one lower than the Command it is part of 6.3.11.4.1.1
Wrong level of indent                               Indent level should be one lower than the Command it is part of 6.3.11.4.1.1
Header is title wrong                               Change to Coexistent Mode
Inconsistency with name of field                    Change data rate to duty cycle to agree with the field name in Figure 29
                                                    Change clause heading
Table 12 column three is inconsistent with Figure 29 anddata rate to duty cycle to agree with the field name in Figure 29
Wrong level of indent and lettering                 Indent level should be five (I.e. 6.3.11.4.2)
Wrong level of indent                               Indent level should be one more than the frame that it belongs to
                                                    Add missing setting
Lacks indication for setting the 1-bit field for accepted or rejected
Wrong level of indent                               Indent level should be one more than the frame that it belongs to
This is a 2-bit filed not a 1-bit field             Insert 2-, to make a 2-bit field to agree with figure 30
Wrong level of indent                               Indent level should be one more than the frame that it belongs to
                                                    Change data 30
Table 13 header row in not consistent with field name in figurerate to duty cycle to agree with the field name in Figure 30
Wrong level of indent                               Level should be at the same level as the other command frames (I.e., 6.3.11.4
Wrong level of indent                               Level should be one more than the command frame that this field is part of (I.e
Wrong level of indent                               Level should be one more than the command frame that this field is part of (I.e
Add space between 31 and in                         Add space between 31 and in
Wrong level of indent                               Level should be at the same level as the other command frames (I.e., 6.3.11.4
Figure 32 the frame status bitmap uses 0, 1, … instead of L-R .. With L-R
                                                    Replace 0, 1,
                                                    Fix inconsistency
Figure 35 has Piconet priority as a 1-bit, while text of 6.4.8.6 states that it is a 2-bit field
                                                     but the text of 6.4.8.1 indicates more than one bit, especially if it is a length fiel
Figure 35 has a beacon period length as a 1-bit, Fix inconsistency
There is no minCAP in Table 23, 24, or 25           Define minCAP
                                                     this document
What is a coordinator? There is no such term inReplace coordinator with hub
                                                     this document
What is a coordinator? There is no such term inReplace coordinator with hub
                                                    Replace coordinators with hubs
What are coordinators? There is no such term in this document
There is no description of the NID 1-bit fields     Insert the missing description of the 1-bit NIDs
Test is not consistent with header                  Insert hub, to make Relayed Hub/Node
                                                    Fix inconsistency
Table 15, row 14, the IE name does not agree with the Description. IN one Bilink and in the other uplink
Header does not agree with the text                 Change Uplink to Downlink
Header does not agree with the text                 Change Uplink to Bilink
                                                    Properly describe the missing IE here
Text states that the fields are defined in 6.3.6, which is a false statement. 6.3.6 does not contain Node address, NID, Uplink, D
What is an OUI-24l?                                 Delete l
                                                    Insert a period after 7.13 sense of.
Insert a period after 7.13 and before MAC, so that the words can be madeand before MAC, so that the words can be made sen
                                                    Fix bit to represent
Table 17 lists user priority requiring a minimum of 3 inconsistency 8 values. There is a piconet priority which is 2-bits. There
What is the "Not acknowledge??" doing here? Delete it
                                                    Delete cross reference to Table 17
What does Table 17 have to do with the Frame Acknowledgement?
                                                    Fix inconsistency
There is no mG-AckDataSubtype in table 3. mG-AckDataSubtype is a MAC sublayer parameter, not a subframe type. Its value
                                                    Replace latter
What is latter? Only a hub is ever mentioned, there is no latter. with identifying entity
                                                    Fix inconsistency
If mG-AckDataSubtype is a valid subtype, then add it to table 3
                                                    Put
The N-Ack and G-Ack are the same, not different () around G-Ack
header not using consistent name                    Insert superframe before boundaries
Insert a space after 7.3.1and before in.            Insert a space after 7.3.1and before in.
Remove the italics on the n inside the word functionRemove the italics on the n inside the word function
There is no Multinode Assignment frame              Insert Connection to use a defined frame
The use of below is not descriptive.                Insert cross reference
                                                     one from clause 6
What is this doing here? Why is it redefining theRemove entire clause
                                                     be replaced by hub and node need to be replaced
Figure 75 Terms coordinator and device need toTerms coordinator and device (four occurrences) by hub and node
                                                     be replaced by hub and node need to be replaced
Figure 77 Terms coordinator and device need toTerms coordinator and device (four occurrences) by hub and node
The use of below is not descriptive.                Insert cross reference
The use of below is not descriptive.                Insert cross reference
There is no Figure 86 (a)                           Correct cross reference
There is no Figure 86 (a)                           Correct cross reference
There is no Figure 86 (b)                           Correct cross reference
Insert a space between 7.12.1 and for               Insert a space between 7.12.1 and for
Replace below with actual cross reference           Replace below with actual cross reference
                                                    is a coordinator? There hub
Entire 7.12.3 and subclauses and 7.12.4: What Replace coordinator withis no such term in this document
Move period before Figure 5 to after                Move period before Figure 5 to after
                                                    Rewrite 802.15.6, when this is to optional narrowband physical layer."
Why is this document defining optional physical layer for "This clause specifies an be 802.15.6?
Annex A; B3 has no entry                            Delete B3
                                                    Change
This is the last line on the page, nothing is defined below.below to in the following sub clauses
Only the Frame Subtype is shown below               Change below to in the following sub clauses
                                                    level, since this to 6.7.2.1.1
Should be one level more than the Allocation ID Change 6.7.2.2 item is part of it
                                                    level, since this to 6.7.2.1.2
Should be one level more than the Allocation ID Change 6.7.2.2 item is part of it
Change below to in the following sub clauses Change below to in the following sub clauses
Delete "as described below" and insert a commaResulting in "… access phase, but not both."
                                                    Replace "as described below" with actual cross a contended allocation."
Where is it described below? Both 7.5.1.1 and 7.5.2.1 have the exact same heading of "Startingreference to 7.5.2.1
                                                     to which this is referring?
Where and what is "as further described below."Replace with cross reference or delete text
                                                    Replace with cross
Where and what is "as described below." to which this is referring? reference or delete text
Delete "described below"                            Delete "described below"
Delete "as described below"                         Delete "as described below"
                                                     this sub "as described below" with "described in this sub clause"
Replace "as described below" with "described in Replace clause"
                                                    Replace "as specified below" with "specified in this sub clause"
Replace "as specified below" with "specified in this sub clause"
Replace below with equation 21                      Replace below with equation 21
Replace below with equation 21                      Replace below with equation 21
                                                       so, use consistent terms because P2 <> P_2
Are P2 and P3 the same as P_2 and P_3 on lineIf29 and line 30?
Where below? Equation 22?                           Replace below with equation 22
Where below? Equation 22?                           Replace below with equation 22
Where below? Equation 26?                           Replace below with equation 26
Replace below with equation 26                      Replace below with equation 26
Replace below with equation 27                      Replace below with equation 27
                                                       so, use consistent terms because P2 <> P_2
Are P2 and P3 the same as P_2 and P_3 on lineIf18 and line 19?
Where below? Equation 27?                           Replace below with equation 27
Where below? Equation 28?                           Replace below with equation 28
Where below? Equation 34?                           Replace below with equation 34
Where below? Equation 34?                           Replace below with equation 34
Where below? Equation 35?                           Replace below with equation 35
Where below? Equation 35?                           Replace below with equation 35
                                                    R
Replace "are defined below" with "are as follows" eplace "are defined below" with "are as follows"
                                                       so, use consistent terms because P2 <> P_2
Are P2 and P3 the same as P_2 and P_3 on lineIf17 and line 18?
Where below? Equation 37?                           Replace below with by equation 37
Where below? Equation 37?                           Replace below with by equation 37
Where below? Equation 41?                           Replace below with by equation 41
Where below? Equation 46?                           Replace below with by equation 46
Where below? Equation 46?                           Replace below with by equation 46
Where below? Equation 46?                           Replace below with by equation 46
                                                      complete.
Missing a period to indicate that the statement isInsert a period.
Delete period at the start of this sentence         Delete the period
                                                      per the below and replace with Equation 68 (as per example on page 50))
Remove below and replace with Equation 68 (asRemoveIEEE Standards Style Manual 2009 ((See its the IEEE Standards Style
As below what?                                      Do not understand what is to be expected
                                                    Change
Use of PTK acronym without defining the acronym first. to "…to create a pairwise temporal key (PTK) between a node…"
                                                  Change to "medical implant communications service, synonymous with this ra
Clarify that medical implant communication service is synonymous with MedRadio which is the FCC's updated name for MedRa
                                                  Change to "mMaxBANSize".
Name of mMaxBANSizes variable is plural, not as listed in Table 23.
                                                  Extend vertical line marking end of beacon period (superframe) n+1 to be of sa
Figure 3 has a vertical line representing end of beaon period (n+1) which is shorter than other similar vertical lines, for no appa
                                                  "It is reserved and set to zero in value of frames."
Relay field is reserved for all other frames. What does reserved mean? Default all other zero should be speficied for reserved
Spelling error with "exclusieve"                  Change to "exclusive"
Spelling error with "curren"                      Change to "current"
Erroneous numbered element starting this line. Delete "6." such that the line begins "g) In data type frames…"
                                                  Change caption of Figure 15 not yet described slot ordering and 15 may be c
Figure 15 caption should reflect beacon shifting enabled as it is illustrated but to read "Allocationin the text. Figure numbering in
                                                  Change to "PNm(n)" to be consistent with
Erroneous variable name Pm(n)                     variables listed in Table 4
                                                      respect to indexed variables "m" and "n". Should explicitly state that n takes v
Headers of Table 4 columns are ambiguous withChange column 1 header to "Beacon Shifting Sequence Index decimal value (m
Erroneous variable name Pm(n)                        Change to "PNm(n)" to be consistent with variables listed in Table 4
                                                     Change
Erroneous reference to Figure 14 rather than Figure 11. to "according to Figure 11."
                                                     Change text to "beacon,
Add reference to section 7.12.2 for channel hopping sequence creation. see clause 7.12.2."
                                                     Change
Erroneous reference to Figure 14 rather than Figure 11. to "according to Figure 11."
                                                     Message Number of 0 or 1. This is an inefficient use of frame payload format
PTK Index field is defined as a one octet field but takes only valuesfield is also defined as a one octet field but takes values of o
Typographic error.                                   Change "Uplink Request" to "Downlink Request"
                                                     Change 256 using be one octet long in the the is shown Figure 23.
Wakeup Period field is defined as taking values from 1 tothis field to one octet. However,both fieldtext and into be two octets lon
Typographic error with referenced section            Change this line to read: "as defined in 6.7.12
number and unnecessary "as"                          and 6.7.13 respectively."
                                                      basic network element in with "BAN Priority"
Figure 29 includes a field "Piconet Priority". TheReplace "Piconet Priority" this document is BAN. Piconet has not been defined
                                                     Change the basic network element instances of "Piconet" to is a BAN. Picon
This subclause title contains "Piconet Priority". However,to "BAN Priority".Change all structure in this document"BAN" throughou
                                                     Change to "BAN Priority"
Table 10 has caption "Piconet Priority". The basic network element in this document is BAN. Piconet has not been defined and
                                                     Change The second column header is erroneous. In addition, the values in th
Table 10 includes four priority levels with specific values. header of second column to read "Relative Priority". Redefine values
Capitalization and grammar.                          Change to "…to coexistence. Table 10 defined the"
Capitalization and grammar.                          Change to "…the sending hub is requesting. Table 11"
                                                     Change all instances of "coordinator" and hubs as the basic entire document.
This line refers to a coordinator rather than a hub. However, clause 5.1 defines nodesto "hub" throughout the elements of a BA
Table 12 is redundant and duplicate of Table 11.Strike Table 12 as shown and change any references to Table 12 to reflect Tab
Table 13 is redundant and duplicate of Table 11.Strike Table 13 as shown and change any references to Table 13 to reflect Tab
                                                     Change equals acceptance or bit field indicates whether the coexistence requ
Text does not clearly define which value of the Status bit sentence to: "This onerejection.
Grammar                                              Add space and correct text as "… as shown in Figure 31 in a Command…"
Grammar                                              Change "optional" to "optionally"
                                                     Delete Wakeup frame and nodes must be actively functions order to receive
Wakeup frames are redundant with the various Poll messages. In addition,utilize various poll framelistening into keep nodes aw
                                                     Change bit field. to show this field is defined a two bit reducing the reserv
Figure 35 includes a field "Piconet Priority" shown as a 1 Figure 35However,"Piconet Priority" as as2abit field, value in 6.4.8.6.
                                                      basic network element in with "BAN Priority"
Figure 35 includes a field "Piconet Priority". TheReplace "Piconet Priority" this document is BAN. Piconet has not been defined
                                                     Include not defined in the MAC sublayer parameter table, parameters this an
Reference is made to variable minCAP. This variable is minCAP as value in PHY-dependent MAC sublyer Table 23. Isor other
Table 13 is redundant and duplicate of Table 10.Delete Table 13 and change any references to Table 13 to reflect Table 10.
                                                     Change the basic network element instances of "Piconet" to is a BAN. Picon
This subclause title contains "Piconet Priority". However,to "BAN Priority".Change all structure in this document"BAN" throughou
                                                      section does to define levels defined in 7.2.3 this field. Should the 4 bit valu
User Priority field is defined as a 4 bit field. ThisAdd referencenot priority the possible values for as acceptable values for setting
                                                     Add text to accompanies connection allocation request that accompanies such
It is not clear whether the connection allocation request that clarify that the such a Group Connection IE applies to each membe
Typographical error.                                 Change title of this subclause to "Delayed Bilink Assignment IE"
Punctuation needed.                                  Change to …offered in 7.12. MAC / PHY optional…"
Punctuation needed.                                  Change to …elucidated in 7.13. MAC sublayer…"
Typographical error.                                 Delete phrase "Not acknowledged??"
Erroneous reference to Table 17.                     Strike reference to Table 17. Keep reference to Table 18.
                                                      possibility of a node of unconnected nodes in this paragraph to account for no
Description of unconnected node should include Expand the definitionseeks to use only RAP/CAP contention based access but
Grammar                                              Change last two lines on this page to read: "The hub shall provide unconnected
Figure 61 contains a typographic error.              Change "Polled llocation" to "Polled allocation" at the right edge of Figure 61.
                                                     Add a
Punctuation and typographical error in variable name. space and correct the variable name such that this line reads "…in 7.5.1
Typographical error.                                 Correct variable name to read "pRandomAccess"
Grammar                                              change "have been already" to "has already been"
Grammar                                          change "have" to "has"
Add definition of RTT acronym                    Add line "RTT Restricted Tree Topology"
Add definition of RN acronym                     Add line "RN Relay Node"
Add definition of SN acronym                     Add line "SN Sensor Node"
                                                 This sends a connection deleted and the node. option for relay is no defined
A sensor node seeking to establish RTT functionality subclause should berequest to a relaysecond However, there discovery (7.
                                                 Clarify the frame". of emergency frame as used in this has not
Reference is made to the reception of an "emergency data definitionIs this a specific frame type? If so, it context. been defined.
                                                 Clarify this subclasue This would introduce risks with respect to occur via a le
A node must not be able to join a BAN by connecting through a relay. to ensure that connection to a BAN cannotsecurity and R
Grammar                                          Change to "A connected or unconnected node may optionally listen…"
Grammar                                          Change to "they become orphaned. Therefore, if a SN experiences a bad con
Punctuation                                      Insert a space such that this line includes "…described in 7.12.1 for coexistenc
Correct ambiguous use of "device".               Change "…for various device" to "…for various BAN"
Correct ambiguous use of "device".               Change "Device mobilty modeling…" to "BAN mobility modeling…"
                                                 mobility following sentences: "The BAN mobility model classification is based o
Add additional text to clarify the exemplary BAN Add the models defined.
                                                 Change cells for UWB Band such that Channel to NB PHY only.
Table 21 shows channel hopping as applicable to UWB band PHY. Channel Hopping applicableHopping is shown as "not appli
                                                 Add sentence to beginning NB PHY table. Text here should state that of chan
Text cites Table 24 for Nch = pChannelsTotal. This value is defined only for of subclause 7.12.2 stating the applicability channe
                                                 Change all instances
Text refers to "coordinator". However basic element of BAN is a hub. of "coordinator" to "hub" in this subclause and throughout
                                                 Define mEDScanDuration present in Table 23.
MAC sublayer parameter mEDScanDuration shown in text is not defined oras a MAC sublayer parameter in Table 23
                                                 Define "BAN enquiry frame" or else relate to existing MAC command types
Text refers to "BAN enquiry frame". Such a frame has not been defined.
                                                 Define mActiveScanDuration present in Table 23.
MAC sublayer parameter mActiveScanDuration shown in text is not defined oras a MAC sublayer parameter in Table 23
                                                 Define mNetworkActivityDuration present in Table 23.
MAC sublayer parameter mNetworkActivityDuration shown in text is not defined oras a MAC sublayer parameter in Table 23.
                                                 Define mPassiveScanDuration present in Table 23.
MAC sublayer parameter mPassiveScanDuration shown in text is not defined oras a MAC sublayer parameter in Table 23
                                                 Change "shall" an optional
"shall" should be a "may" as operation in Time Sharing Mode is to "may" functionality
                                                 Define "coexistence request" and "Coexistence assignment" frames defined.
Text refers to "coexistence request frame" as well as "coexistence assignment frame". These frames have not been as optiona
                                                 Include the sentence: "The time shareing mandatory. The text should explicitly
The time sharing and load reduction mechanisms for coexistence are optional rather than and load reduction coexistence mech
                                                 Change all instances of "piconet" to "BAN" in this
Reference made to "Piconets" which are not defined. "BAN" is the fundamental network element. subclause.
                                                 Replace this of the load control mechanism load control for short-term coexist
The first paragraph is overly complex and the optional nature sentence with: "A hub may use clearly conveyed by rewriting the s
                                                 Replace all instances of "piconet" with "BAN" in this subclause and
Text refers to "piconet" and "coordinator". This document defines "hub" as one of the basic elements of a "BAN". entire docu
                                                 Change "sever drop in the signal proximate "severe drop interference. nois
Typographic error. Also, reduction of signal strength would not reveal presence ofstrength" to BANs causingin the signal to Rath
                                                 Define necessary PHY-dependent MAC sublayer parameters for HBC/EFC phy
There is no table of PHY-dependent MAC sublayer parameters pertainint to HBC/EFC physical layer.
Punctuation                                      Delete period at the start of this line.
                                                 Add channels (pChannelsTotal). However, the number of available channels
Table 42 is cited by Table 24 as listing the number ofa third column to Table 42 with header equal to "Number of Channels, Nch
                                                  Change second MHz row of Table 42 to read:2360-2400 | fc =
Only 1 channel should be reserved as guard band for 2360-2400to lastportion of narrowband PHY.                             2361.00
                                                  Clarify frequency band definition in 11.3 and 11.1.
This line cites frequency band for EFC from 10 MHz to 50 MHz. This frequency band is inconsistent with that defined in subcla
                                                  Remove the "Relay This field cannot be used in a reliable way in presence of
The use of a signal strength to define the link quality is questionable.Link Quality" field or find another way to measure the link q
                                                  Remove it or add some text.
This clause is missing some text and need further explanation.

The SFD is not defined                            Define the SFD structure

Can the hub act as a relay to nodes on its BAN, i.e. Can the recipient and sender ID's be of leaf nodes and used for node to no

                                              Add state transition for Association and receives Association except stateme
The figure 4a does not indicate what happens when the device is in connected state(or remove from all frames(is this allowed s

                                              Remain in connected state (and remove "the all frames except....." statement)
The figure 4b does not indicate what happens when the device is in connected state and receives Association , Disassociation,

                                                  the GTK distribution is hub to node and that the GTK is implied here
GTK description needs to align with 6.3.5 in that Clarification may be required to indicate not multicast as sent to potential memb

                                            Remove sender MAC address from the beacon (as this can the latter the the
Are both sender ID and sender MAC address needed in the beacon? The former is in the MAC header while be sent inis in Con

                                                  recipient and sender ID's - is the recipient ID that of hub node and relay to of o
In relay mode – what are the correct settings for Clarify use of node id's in relay mode. ―From leaf to relayand sender id that hub

pAllocationSlotMin is not defined. Is its size going to be based on minimum/maximum frame durations?
pAllocationSlotResolution is not defined. Is its size going to be based on the pCSMASlotLength?

                                              Clarify – is it to send a for security disassociation and possibly add in the sta
What happens if one end refuses a security associationfailure proceduredisassociation? PTK missing/invalid is shownstatus/err

                                                  Remove MAC Header, so can it be removed from frame payload? It would onl
This Security Level Required field is a repeat of what is inthis field from the Security Association Payload or update state machi

                                                Change PTK is only allowed in connected state (not secured state) as per sta
This line says PTK frame is sent to a ―secured node‖, buttext ―...to a secured node‖ to ―...to a secured node in the connected fig

What is Former Hub Address to be used for?         Need to add a section on the role of this field and suggest making it optional


                                              The use of Connection Change Indicator to refer to in a Connection Assignme
Channel Order IE is shown in the Connection Change Indicator, but Channel Order IE is shown onlyIE's in the Connection Req


                                                                    nd
                                                    the 1 octet of 2 octet.
The text referring to the use of two octets to holdExplain role long superframe sequence number of the wakeup phase is unclea

                                               Suggest that the MAC and PHY capability should be made optional
Mac and PHY Capability of the Hub is in the Beacon, so why is it not needed in all Connection Assignment frames in the Conn

                                                 Add separate diagram for the connection related information elements for us
Inconsistency in fields from NID onwards in fig25 andain fig 49 for Multinode Connection Assignment

Naming of commands and their bit pattern couldSuggest changing Battery Level Inquiry to Battery Level Request and making it
                                              help distinguish request/response

Clarify whether or not block transfers can span more than 1 superframe when the block does not fit the allocation interval?

                                                   Change name Relay Link Quality to Relay it suggests LQI
Text refers to it holding received signal strength – suggest the name should be changed asSignal Strength as per 6.9.8 of 802.

                                               Rename was a B1.
B2 is a legacy name from an earlier proposal where thereB2 frame to indicate its purpose e.g. Contention Beacon

                                                   Piconet needs to be defined – earlier sections. it can be seen to of piconet pri
Piconet priority unclear as piconet is defined in the document's definitions or in from later 7.12.3 Also, the function refer to a part

                                                Rather than future the specific Battery Level bits) as it is only 2 octets.
Current MAC Capability field is limited and cannot provide forinclude commands (except in rsvdIndication command, MAC Capa

                                                 As e.g based on encodings MAC Capability and cipher function?
Should there be Capability fields related to Security,per comment on revising for security levelto define commands in an IE

                                               so can use a bitmask to determine
Why start assignments at 11 – why not 16 or 32 Start assignment IE's at 16 or 32 if assignment or request and to allow for ex

                                              clarified, e.g. presumably each node in the
The operation of Group Connection needs to be Add text on connection phase for groups. group issues a connection request

When would a hub send a Non Beacon (called unicast in 6.2.1.1.9) Management frame with More data =1 to initiate an immedi

It needs to be stated that RTT is provided for scheduled allocation only. Presumably this is the case so as to avoid complicating

                                                 leaf node to relay is as per original the signalling shown for node to relay link
Text in 7.9.2 suggests that the state machine forAdd a state diagram to complementfig 4a/4b (for setup phase only) according t

                                               Add commands relayed)?
Can only data frame types be relayed (or can commands also beto figure 79/80 if allowed

                                               Add clarifying text
When a device is connected to a hub (with allocations) and then initiates the relay procedure what happens to its old slot(s) allo

                                                   Need to clarify whether to orphan and 82 it remain in connected if it was previ
It is unclear what state the node is in after RTT session ends – is it backFigures 81 or does refer to previously connected and un

                                           Suggest defining a maximum Synchronisation interval to avoid continual increm
What happens when the guard time becomes greater than the allocation interval?
                                                  is it envisaged that broadcast be used Hub-Hub communications with the use
No definition for connection setup for hub-hub orA state machine needs to be added for for hub-hub commands as to allow for t

mGT_nominal is defined as Allocation Slot Length/10. What is the basis used for setting the denominator to 10?

Title not specific                                 Rename title to MAC State Diagram

typo's                                             ―exclusieve‖ to ―exclusive‖ and ―curren‖ to ―current‖

Role of bits would be clearer if bit pattern shown as b3 b2 b1 b0 for frame subtype (although note this is not the convention use

                                                    it implies post is a frame and the frame‖
Use of ―send a post‖ is not clear at this point, as replace "send a post" with "post adifference between post and poll operation is

Text overly complicated in g part 1                ―...from its value in the data frame addressed to the same recipient....‖ and also

                                                  Remove not optional.
In figure 14 the RAP1 Start field is dashed, but this field isdashing around RAP1

The titles of IE's should be changed to indicate that they are requests and remove assignment(as they are requests to change

First sentence here needs to state it is also sent by a relay node as per 6.4.6.4. Also state that a relay can do resource allocatio

this is sent to >1 neighbor hub                    ―neighboring coordinator‖ to ―neighboring coordinators‖

Table 11 Title wrong                               Change ―Data Rage...‖ to ―Data Rate....‖

                                           Align naming of these terms
Terms Minimum Interval Length and Minimum Allocations Length are used but name minimum length and allocation length in e

Use of SN – would be clearer to refer to it as leaf node

typo's                                             ―this broadcast messages‖ to ―these broadcast messages‖, ―SN experience‖ to

This figure is overly complex - too much (text) detail in too few drawings

References to BAN descriptor field should be changed to BAN descriptor fields
                                                    contains too many types of access modes and access phases which are redun
General Comment: The MAC is too complex. It Simplify the MAC by removing redundant and unnecessary capabilities. Note: I
                                                      multiple bit fields are displayed in a Table, they should more significant the M
Even though bits are transmitted LSB first, whenChange Table 1 to display the bit field as b2 b1 with thebe displayed withbit on
                                                    Add a table that defines to be, or can be, secure. This needs different frame
In general, it is not clear which frame types and frame transactions need Security options and requirements forto be defined fort
                                                      multiple bit fields are displayed in a Table, they should more significant the M
Even though bits are transmitted LSB first, whenChange Table 2 to display the bit field as b4 b3 with thebe displayed withbit on
                                                     is set in the Header used to indicate Frame as well as in Frame is contained
The use of the Relay bit is not clearly defined. It The Relay bit can bethe encapsulatedthat an encapsulatedthe Header of the "e
                                                    In unicast management and allocation intervals, when node a node, more th
It is not clear that the First Frame / On-Time bit is set on the first frame on all data type frames sent by aahub to receives the Firs
                                                      multiple bit fields are displayed in a Table, bit field as b5 b4 with the more sign
Even though bits are transmitted LSB first, whenChange Table 3 to display the Frame Type they should be displayed with the M
                                                    Confirm that there data frames in in behavior for the different access modes,
Does the behavior of the More bit have the same meaning in uplinkis no difference CSMA, Uplink Allocation Intervals, Bilink allo
                                                    For CSMA access, the Hub More bit is set in a CSMA Uplink access, how doe
The behavior relative to the More bit during CSMA needs clarification. If the should respond to the More bit being set the same
                                                    The Node may set the Hub, that the node has uplink data, it Hub should re
Sect a) 2) Does this mean that for scheduled downlink or Post from the More bit inifan Acknowledgement frame.can set the "Mo
                                                    Change set on a management or data management Hub to the node. What
There is no restriction on the ACK policy if the More bit isthe meaning of the More bit for frame from theor data frames from the
                                                    In sending a Poll immediately following a Post? Wouldn't it to node, the Mor
Sect b) 2) What is the setting when the Hub will be unicast management and data type frames sent by a hub setathe More bit to
                                                    In does the node frames case where its a node, interval bit not ended? i
Sect c) 1) If this is a scheduled uplink access, whatI-Ack and B-Ackdo in thesent by a hub toallocationthe Morehasis set to zero D
After the Connection Request Frame, is the
Connection Assignment frame transmitted             Need period, immediately after
It is stated that the Multinode Connection by Add a explanation for this case. the Beacon,
Assignment is made with a broadcast                 when nodes are required to listen for
It is not clear how Multimode Connection
Assignment is different from Group Connection Clarify the difference.frame shall not be older
At what point is it determined that this oldest    The oldest expected
        needs to be discarded. of frames that than maximum number of frames that than be
frame is the maximum number Who has the
What                                               The the 15 frames received. If more can 15
can both T-Poll replace Pollarequired? Should acknowledged with a B-Ack is 16, so the are
Are be acknowledged with B-Ack. There              Justify why both Delayed Bilink and T-Poll
                                    so that only
T-Poll replace Poll or vice versa, T-Poll" and "B- required. If neither is required, eliminate both.
If T-Poll is required, are "I-Ack &                If T-Poll is required, then:
Ack & T-Poll" also required? Are these
This statement does not adequately specify the A T-Poll is used to mark the beginning of an
                                                   There is no a simple solution to this
What requirement. There needs supports
timingis the indication that a node to be more requirement. It will involve interaction between
unscheduled polling? Access bit be set in the Clarify
Must the Type-I Polling
MAC capability field for Type-II Access            Clarify
Having both Type-I and a Bilink Request IE to Either:
Must thein addition to Unscheduled be set in
phases, Type-II Polling Access bit Polling and 1) Show that Type-II Type Access cannot be
the MAC capability field for a Capability bit
Why is the Schedule Access Delayed Bilink          Clarify
required. Delayed-Polling for a node to send
Why is theIs it not sufficient Access Capability Justify why this bit is required or removed it.
Why is this Is it not sufficient for a node
bit required.defined as Delayed-Polling as to      Justify why this bit is required or removed it.
opposed to Delayed-Bilink? What is the this Clarify cases of the term "Group", clarify the
A search on the term "Group" shows that            For all
It is not used in multiple contexts, and is not    context example of how word:
term is clear how "Group" connection requests Give an with a preceding a Group Assignment
and assignments are made. It is also not clear Request and Connection Assignment are
                                                   Clarify
What is the behavior of a Low Power Wakeup Radio relative to a non-Low Power Wakeup Radio?
When is it necessary and/or allowed to include Either:
                                                   State the Superframe IE in a connection assignment? Under what conditions
Requirements needing Uplink Access Mode the Slottedrequirement and/or recommendation.
can be satisfied with the BiLink Access Mode. 1) Show that BiLink cannot adequately satisfy
The term "Gap" is not clearly defined.             Define "Gap" as follows: When the Wakeup Period field bit is '0', Gap is equ
In the Bilink Allocation Request, there isBiLink Access Mode. In BilinkDownlink access mode is required Post cannotbeginning o
Downlink Access Mode is redundant to no            Either:1) in the why Allocation Request that
                                                   Add a bit Justify BiLink Access, the Hub may perform a and at the be satisfied
way for the node to indicate if this allocation is indicates that a node requests the first
                                                   Add a bit or Delayed Allocation Request that indicates that a node requires a T
How does a node request the need for a T-Poll in a Bilink in the BilinkBilink Allocation Request?
                                                   Either:1) Show Improvised Scheduling is be adequately satisfied Polling is S
Delayed BiLink Mode is not needed when Scheduled BiLink with that Delayed-Bilink cannot available. Unscheduled with eitheral
                                                   Clarify. What what point are nodes expected to listen to multicast frames?
How are Multicast groups formed, assigned, identified, etc. Atis the multicast group assignment mechanism?
                                                   Add details
The requirements/recommendations for retransmission of unacknowledged frames is not clear. What is required/allowed/expe
                                                   The Node sent by the Hub but not received at the receiving
What is the correct behavior when an Acknowledgement ismay retransmit the previous frame after Node? a Poll or on its nex
                                                   After determining that Node but not received at the Hub? Can the Node go to
What is the correct behavior when an Acknowledgement is sent by the the Node is not transmitting, the Hub may attempt to retr
                                                   Explain
The other purpose of B2 is to announce the beginning of CAP. Is there a conflict here in functionality? Sending the B2 Frame
                                                   frame per
Figure 53: This figure implies more than one B2 Explain superframe. Is that the case? It also does not show CAP after B2.
                                                   Set a reasonable timeout based on:1) B-Ack.
What is the timeout for receiving an acknowledge when the Ack policy is set to I-Ack orLow RSSI2) No Frame Sync Correlation
                                                   Add frame expected?‖ description of behavior cleared handle discarded fram
What if the sender has already discarded the ―oldest Clarification and/or How is the B-Ack statusof how toon the receiver such th
                                                    MAC, and the block abort mechanism, or change this requirement that "The s
What if a higher priority PSDU is received by theAdd a Block Transferis not complete because of errors or missing B-Acks? Th
                                                   During a Scheduled Uplink Allocation scheduled uplink Node receives either o
Figure 55 show an uplink frame being transmitter after a B-Ack without a Poll during a Interval, once the allocation. Figure 66 a
                                                    byte history for reasonable limits
Does this mean that the Hub needs to retain a 7 Clarify and add all frames of all blocks, for all Streams of all Nodes for compar
                                                   Add details
Can fragments of MSDUs of different frame subtype and to the same recipient be interleaved? For instance, if a high priority M
                                                   Add details
What constitutes "MSDU with missing fragments?" Does this mean receiving Fragments out-of-order? Does this mean a new M
                                                   Add details
How does the receiver know when it has received the last fragment of an MSDU? If is receives another MSDU with a new sequ
                                                   Modify drawing to show periods for broadcast/multicast frames
Figures 57, 58 and 59 show no period for broadcast/multicast frames, and no period for unscheduled polling. and for unsche
                                                   Remove unnecessary will cause great difficulty in implementation and interope
Figures 57, 58 and 59 show too many options for access phases. Thisand redundant access modes.
                                                   Either:1) latency From EAP1/RAP1 to EAP2/RAP2 is too great, then RAP1, R
RAP1, RAP2, EAP2 are redundant and not needed. If theJustify the need for RAP1, RAP2, and EAP2.OR:2) Remove the Supe
                                                   Either explain, or Node know if EAP1 is zero, the start of RAP1, or the start a
In a Beaconless Mode with Superframe boundaries, how does theremove Beaconless Mode with Superframe boundaries
                                                   Either explain, or remove Beaconless Mode with Superframe boundaries
In a Beaconless Mode with Superframe boundaries, how are the contention periods known to nodes attempting to connect to th
                                                   Show structure and options for superframe structure in Beaconless Mode with
In Figure 59, there is no Frame Structure defined. There is no EAP1/2, no RAP1/2, no CAP, no B2, no period for broadcast/mu
                                                   Define a CAP access period relative to access is required to connect to a netw
Non-Beacon mode with superframe boundaries requires contention access. Contentionthe superframe boundaries and make i
                                                   Only contention access is allowed in Non-Beacon is required to connect to bo
Non-Beacon mode without superframe boundaries requires contention access. Contention accessmode without superframe a n
                                                   CSMA allocation periods behave similar to Unscheduled frame exchange need
It is not clear how the hub responds with management frame during a CSMA allocation. The protocol for Poll, except that the e
                                                   Add an Unscheduled Polling Request IE, and an Unscheduled Polling Allocatio
There is inadequate definition on how Unscheduled Polling is controlled, and requested by a Node. The Node has no means o
                                                   In Unscheduled Polling, the access is initiated by the the sending either a Poll
The behavior of Unscheduled Polling is not adequately defined. There needs to be more definition of Hubprotocol requirements
                                                   After wait after sending a Unscheduled Poll, the next wait when there is a va
During Unscheduled Polling, how long should the Hubthe Hub sends out anPoll before going to it should nodepCCATime for no
                                                   After an should the Hub do an LBT before Polling the next Node? pCCATime
During Unscheduled Polling, if a node does not respond, Unscheduled Poll, if the RSSI level is below RSSImin afterWhat determ
                                                   If a good HCS is received but a bad the Hub, Hub may either re-Poll the same
During Unscheduled Polling, if a good HCS is received but a bad FCS is received by FCS, the should the Hub perform a retry P
                                                   Add Polling Access bits are set to zero in when the Type-I and the Node, ma
In Unscheduled Access, when the Type-I and Type-IIthe sentence:In Unscheduled Access,the MAC Capability of Type-II Polling
                                                   Add details
Need details on unscheduled access, and encoding of Unscheduled Access IE.
                                                   Add a Table to define when to the node? Is there a mechanism allowed. to i
How does the hub know if it needs to provide a T-Poll time reference update a T-Poll is required or when a Poll is for a nodeAdd
                                                   After a In the case where frame to has sent an no frame, if data is does no
At what time if it permissible for the node to go to sleep.node sends an Ack the node the Hub, andAck additionalthe Hub expecte
                                                    transactions should be a 2-Hop Contention, and Scheduled Bilink.
There are many limitations and requirements on Access typeswhen usinglimited to Star Topology that are not defined. The "Rela
                                                   It several requirements that are parameters, this document which will have t
For 863-870MHz in Europe & ETSI Stds. there areis necessary to define settings, not defined inand operations that will allow 86
                                                     depending on the frequency band and location. The consequences can be:1)
If a channel is idle, then there are consequencesAdd a channel occupancy mechanism to bands that have channel occupancy r
                                                    a coexistence mechanism. AFA is the Define a Channel Table format that w
Adaptive Frequency Agility (AFA) is not listed as Add AFA as a coexistence mechanism.most effective coexistence mechanism
                                                   If at improving coexistence? Has any simulation been performed to validate its
Under what conditions is Beacon shifting effective this options is to be included, then the conditions for its use need to be stated
                                                   Verify through simulation means that hopping a collision, the entire SuperFra
Does channel hopping at the SuperFrame interval make any sense? Thisthat channel if there isat the superframe level improve
                                                   Change turn-around time of both to:"The RX-to-TX turnaround time to be the
In Sect 9.6.3, Pg 155, pSIFS is defined as the maximum the first sentence for 9.6.2 Tx to Rx. Therefore, pSIFS needs shall not
                                                   For the Transmitter/Sender:"For burst mode transmissions, the inter-frame spa
The way this statement is written, it gives no tolerance to the transmitter or receiver requirements.
                                                   Add second column excessive interference from two devices. ―ACPR (Node)‖
The ACPR specified for the MICS band is not low enough to prevent in table 8 such that we have hub columns There is a very l
                                                   Modify to "10 dB above the
Need to explicitly reference minimum receiver sensitivity for ED threshold minimum specified receiver sensitivity within a give
                                                   Verify that CCA mode 1 is bands is assumed to ETSI LBT requirements. If not
It is not clear whether the LBT requirement for the MICS and 863-870 MHz suitable to implement implemented using CCA mode
                                                   If by change sentence to "Any CCA and LBT procedures required LBT requir
Does the sentence "Any CCA procedures requiredyes,local regulatory requirements shall also be supported" include by local reg
                                              Specify FCS generation
Document does not specify the generator polynomial for a polynomial
                                              Specify a consistent position for these bits
Figures 105 and 108 have burst mode and scrambler seeds interchanged
"qadrature" should be spelled "quadrature".   Make it so.

                                                Make it so.
"a relay capable node" should be "a relay-capable node".

                                              Add citation.
"Optional mechanisms for coexistence and interference mitigating between adjacent or overlapping BANs are provided." Pleas

                                            Make the list: ISO and OSI, for example.
Some acronyms are missing, and need to be added to it so.

                                                  If there are "shall"s sprinkled through be a boatload more "shall"s 14, l. 27; (s
Is clause 5 normative, or not? Usually it's not, but it's a normative clause, there shouldthe clause (e.g., p. 13, l. 9; p.in the text p

                                                    missing a lot of "shall"s. It's not good enough to say, for where appropriate B
Clause 6 and, in fact, all of the later clauses, areEdit the text to reflect its normative status by using "shall"example, that "The in

                                          and their specifications are SAP.
"Both MAC SAP and PHY SAP are not exposed Define and specify the MACbeyond the scope of this specification." Um, no. Y

                                                  Remove the "Relay This field cannot be used in a reliable way in presence of
The use of a signal strength to define the link quality is questionable.Link Quality" field or find another way to measure the link q


                                               Remove it or add some text.
This clause is missing some text and need further explanation.

The SFD is not defined                           Define the SFD structure
The valid range of L is not specified.           Provide the valid range of L.
The valid range of L is not specified.           Provide the valid range of L.
The valid range of L is not specified.           Provide the valid range of L.
                                                 Put N random length of beacon period is period than 3 seconds, more rando
A beacon period contains only two random access period. If theaccess periods in a beacongreater in Figure 56. Revise the sent
                                                 Put topic.Section 7.8.2.1.2 into the same section7.8.2.1.3 should be 7.8.2.27.8
Sections 7.8.2.1.1 and 7.8.2.1.2 belong to the same 7.8.2.1.1 and 7.8.2.1.3 should be a higher level section
                                                 Please try to clarify
What is the relationship between "Unicast poll aided connected discovery" and "Unicast wakeup mechanism"? Do they depend
"parameters that is needed at receiver"          "parameters that are needed at receiver"
"which is lower"                                 "whichever is lower"

                                              for unicast diagram for broadcast scenario. Can broadcasting
State diagrams, all the message exchanges are Insert state communication. No information about it be secure ? is given. (Text a

                                              Insert Table
A table complementary to Table 3 is needed to present the different frame types and the corresponding security services (No s

                                                     More details are to radio is in for the low power proposal (PHY Capability form
Currently, there is only a bit which is linked with low power wake up be filled in Figure 37 of MAC radio bit. Otherwise wakeup ra

                                                not linked with security. Is the standard going to provide security for "two - hop
Section 7.9 "Two-hop star topology extension" isClarify

                                                Clarify
Section 7.9. Is two-hop star optional or mandatory ?

                                               Define roll-off factor. E.g. 0.5
Section 9.1. The parameters of the pulse shaping are not completely defined. More specifically, the roll-off factor of the SRRC f

                                                    BAN (more relaxed sensitivity spec
The minimum receiver sensitivity is very strict forOne uniform tight than Zigbee and much more tight than Bluetooth LE), which c

                                                 change introduction
According to section 10.18, clear channel assesment is optional. This is not reflected in this introduction.
                                                 Replace differentially coherent PHY by the receiver. Differential phase
Differentially coherent PHY is confusing terminology. Coherence is a potential feature ofdifferential phase shift keying modula
                                               Clarify
Section 10.1.1 and 10.2, lines 12/13 on page 173 contradict each other. Can OOK be used or not?

                                              Remove second scrambler seed, adjust PHY header accordingly (12.6.1.4)
It seems an unnecessary complication to have two different scrambler seeds.

                                                  Remove bit interleaving.
In UWB, there is no significant channel fading. Including interleaving therefore seems unnecessary complication.

                                                 "differentially coherent", the first two are how the phase shift keying and non-c
The modulation is not coherent, non-coherent orReplace differentially coherent PHY by differentialRX detects it. The third does
                                                Replace differentially coherent is not required to recover the keying and non-c
When 'non-coherent detectors' is used in the text, it actually means that the RX PHY by differential phase shiftphase because si
lines 12-13                                     Replace non-coherent modulation by on-off keying, differentially coherent mod
                                                Replace non-coherent modulation by on-off keying

                                                   Replace differentially coherent modulation by differential phase shift keying

                                                   Include which in belong to
The two pools of the preamble are not defined (what is a pool Ci table 53?) which set.
                                                   replace L by value, it might be better to talk about delta_16.
Definition of L for delta_L is confusing, since there is only one16.

                                          Needs apply this to
OOK modulation using the GPPM symbol map. How to clarification. a preamble symbol? Would loose the correlation properties

                                                Needs clarification.
Short pulses will use scrambling. How to apply scrambling during the preamble? Scrambling code is not known during the prea

                                               For discussion be clearly different. Now a DBPSK symbol will confuse an OOK
If preamble structure for DBPSK and OOK is different, it should in the group.

The actual SFD sequence is not defined.            Included definition

                                                Update figure 124?
Tables 54 and 55 include an Nguard that is not present in the symbol structure of figure 124.
tau max in Nguard formula is not defined.       define tau max

                                                    Include
The PRF is only defined in case of the long pulse shape.definition in case of the short pulse shape.
                                                    Improve wording text.
Text is not clear that scrambling affects polarity (+1/-1), rather than on-off keying (0/1) of chips within a burst.
                                                    Resolve conflict with section 10.10.12
Nguard definition differs from definition in section 10.10.12

                                            Replace symbol linear code. This will code.
Current symbol map GPPM doesn't appear to be based on somemap by a linear block require complex distance decoding at th

                                              Relax the RF carrier accuracy
We believe the carrier frequency may deviate more than 20 ppm. Since it is UWB, a receiver will still be able to capture most o

                                                   Specify a then it could be truncated
If an implementer is entirely free to choose the truncation, minimum duration of r(t). to a simple delta function and you always s

                                                 Keep reflect the quality of calculate presence of noise and interference.
The "received signal strength of signals" does not trulyhistory of retries and the link in average packet success rate and use this

Wrong number of bits for the "coexistence Mode" fieldto replace " 3" bits for coxistence mode field with "2"
                                                     One possible providing another poll but be a polled allocation may be conside
In Table 20, the following sentence require clarification:"A poll solution: A future poll maynot considered a poll (with immediate p
                                                     Example of usage or interpretation could be:Static - (1) a single BAN
to clarify more the difference between "Static(S)", "Semi-dynamic(SD)", "Dynamic(D)"; perhaps through use cases in a home
                                                     to replace:"BAN enquiry request" defined.or I believe they are defined (Note:
The frame formats of Ban enquiry frame and Ban enquiry response frame are not with "command-coexistence request" under d
                                                     To Piconet Enquiry Response
table 11- the reserved field should be replaced with use the field value "11" to indicate "Piconet Enquiry Response" frame
                                                     In figure 30 to is missing field figure 30 and need to be defined
BAN Descriptor which is required for coexistence mechanismsreplace the from "Allocation Time/Duty Cycle" with "Allocation Ti
in complete caption for table 13.                    To replace the caption of table 13 "coexistence modes" with "coexistence mod
                                                     table 12: to replace "coexistence modes" with "coexistence modes and allocati
in complete caption in table 12: to replace coexistence mode with coexistence mode and allocation time
When(what timing) the hubs which are not synchronized with each other send or receive both "BAN encuiry" and "Ban encuiry
How should the hub detect no network activity? It does not receive any MAC frame from another hub? (passive scan?)
To state explicitly in which network mode of operation the coexistence mechanisms are applicable.
                                                     The from retransmission with the setting of H0H1=10 since the retry bit in the
How the receipient in HARQ distinguishes new framereceipient should ignore the retry bit during the HARQ process. When PHY
                                                     To replace piconet priority table 13), and reserved bits reduced to 4 bits
in figure 35 piconet priority field of 1 bit should be replaced by 2 bits (see length of "1" with "2"
wrong referencing                                     To replace 6.3.1.10 with 6.3.1.11 &6.3.1.12
How to select a channel hopping sequence that is not used by its neighbor hubs
wrong referencing                                     To replace "table 11" with "table 62"
in figure 66 an I-ACK is missing after the poll frame (see line 12&13)
statement is true except for unconnected node to add "except for unconnected node"
Wrong referencing                                     Line 3: replace figure 71 with figure 69line8: replace figure 71 with figure 69
remove letter a, b, c from caption of figures 69, 70&71
corresponding fields removed                          remove the phrase: "or MSDU……" till the end of the phrase
not relevant                                          delete "Not acknowledged?"
                                                      to update figure 10: to introduce 2 additional bit(s) in the Frame
the rational is to introduce a mechanism for recipient to recognize the progress and end of fragmented block control of the M
                                                      To use the unconnected 6 of in the to indicate the status: ―rejected hub oper
Table 8: to use the value 6 in status code field: to indicate toreserved valuenode table 8unsecure communication the following st
                                                      To replace the text highlighted in the the higlighted the
Page 99-101 Lines 6-12Page 100-101 Lines 21-23 & 1-4to replace the current text in comment with linesfollowing text: " A relay
                                                      to introduce New set and or Bilink) for relaying purposes to distiunguish betwe
to introduce New set of optional Assignement IEs (for uplink/Downlinkof optional Assignement IEs (for uplink/Downlink and or B
There is no definition for Piconet response. Two sugestions for its introduction:a) to use value 5 of table 9 for Piconet Respons
What is the difference between BAN descriptor pertaining to network coexistence in BAN Enquiry Response and BAN descripto
Hub address is missing; BAN descriptor referred in previous comment not explicitly stated
to take into consideration UK & EU regulation with respect to HBC compliance; Note that the HBC measurement presented in 1
Typo                                                  Change "curren" to "current"
                                                       around.
enabled' & 'not enabled' should be the other waySwap the 'enabled' and 'not enabled' in that sentence.
                                                       around.
enabled' & 'not enabled' should be the other waySwap the 'enabled' and 'not enabled' in that sentence.
Sub-clause title font                                 Change "PKY" to PKY with subscript y
                                                      Discuss the frame
EAP1 Length can determined from RAP1 Start in the beaconnecessity of keeping B+EAP1 Length in the multinode connection
                                                       the connection assignment frame and Length in the the beacon frame
EAP2 Length can determined from EAP2 start inDiscuss the necessity of keeping EAP2 RAP2 Start in multinode connection ass
                                                      Text
Text boxes in Fig.65 better with transparent borders boxes with transparent borders
                                                      Text
Text boxes in Fig.66 better with transparent borders boxes with transparent borders
Missing a full stop after "described in Table 20" Add a full stop
                                                      Delete Fig. 70 c in figure
No need to have 'a.' 'b.' 'c.' in figure captions for Fig. 69,a, b, andand Fig. 71captions
Text box mis-aligned in Fig.72                        Adjust the text box for 'group p+1' in Fig.72
                                                      Remove Fig.74, and inconsistent) frame 7.8.2.1.2 to clean up some Fig.34. (
(1) Frame format should not be defined in clause 7. (2) Duplicate (andreview 7.8.2.1.1 and format between Fig.74 and duplicate
Sub-clause numbering                                  Should be sub-clause 7.8.2.2?
                                                      Should relate to Fig.74. If not defined nor the fields to Fig.74
Terminologies (such as session duration and time to start the session) are need to keep allnot relatedin Fig. 74, define all the fie
                                                      (1) i-2 and Channel i-3 in Fig.77. (2) Unclear to Fig.76. (2) Explain how node
(1) Unclear what is Channel i, Channel i-1, Channel Have Fig.77 in the same format as Fig.72 why/how nodes go to off-states d
                                                      Revise the sub-clause title.
Sub-clause title dose not capture the content of following paragraphs well; for instance, Load Reduction is in 7.12.4
"Coordinator" is not used in other sub-clause         Should replace "coordinator" with "hub" for writing consistency, unless otherwis
                                                       abbreviations list.
Energy detection (ED) has not be included in theInclude ED in the abbreviation list on pg.10.
                                                      Review those MAC sublayer parameters.
Values of MAC sublayer parameters introduced in this sub-clause (such as mEDScanDuration) are not provided in Table 23.
BAN enquiry frame is undefined                        Define the BAN enquiry/request frames, or remove it.
                                                      Define those terms, and should use "hub" rather could be unclear throughout
Terms such as "existing coordinator", "BAN coordinator" and "prospective coordinator" used herethan "coordinator"to the reade
What does "BAN descriptor" mean?                      When the term firstly used in the text, should clearly specify what fields in B2 a
                                                      Relate are not defined in with
Terminologies (such as "Next Superframe Start Time" )to fields consistent B2. fields in B2.
Lines 16 & 17 seems repetitive; so as lines 20&21.    Revise, and try to combine them into one sentence if possible.
                                                      (1) Revise the content. (2) Suggestion: remove lines 24-27, and between line
(1) This sub-clause seems have been modified without informing the MAC subgroup members. (2) Contradictions combine line
                                                      Allow the
How to decide the maximum number of retransmission? process to be repeated until receiving a different frame with H0 set b
Typo                                                  For parameter pMICSUnconnectedPollSeparation, change 2xpTIFS to 2xpSIF
                                                      To
Parameters in Table 25 should be further discussedbe discussed and agreed within the MAC subgroup.
Missing the introduction paragraph for 8.4            Including few lines for introducing 8.4 for writing style consistency.
State-0 and state-2 are both with (H0,H1)=(1,0). Should remove state-2; and in state-1 Rx Action description, change 'goes to 2
ultra wide band' is not popular form                  change to 'ultra-wideband'
                                                      Add figure to match with
In Fig.1, Is it possible to show 2-hop examples in the examples of 2-hop the text?
Give the acronym of PTK at its first appearance Give the acronym of PTK at its first appearance
Aloha                                                 ALOHA
                                                      Can we modify the figure
 The three lengths of BP/4*PN_m(n+1), BP/4*PN_m(n+2), BP/4*PN_m(n+3), do not match in the figures
                                                    Add L_2.
In Fig. 88 (b), It is not given which lengths are L_1 or L_1 or L_2 In Fig. 88 (b)
UWB needs both slotted ALOHA and CSMA Add CSMA for UWB
UWB needs both slotted ALOHA and CSMA Add CSMA for UWB
430-440 is not available                            change to: 420-430 and 440-450
why on-off signaling needs to divide a symbol into two half?
Can we have a unified definition for mean PRF and peak PRF?
PRF, P.PRF                                          PRF-> average PRF, P.PRF->peak PRF
what does 'spr' stand for?
                                                     band?
Is it proper to use channel 2 as mandatory in lowchange to channel 3
What is the purpose of this sentence?               delete the sentence
centered at 16MHz, 27MHz with the bandwidth of 4MHz. This does not coincide with the next description.
The frequency band for HBC is from 10 to 50 MHz. This does not coincide with the last description.
The is no description on coexistence                add coexistence description
                                                    A hub shall be able to get
How should we choose the value of the Beacon Shifting Sequence Index? the Beacon Shifting Sequence Index by hearing bea

                                              each other send for receiving the Coexistence Response.
When the hubs which are not synchronized withSpecify the timingor receive both "Coexistence Request" and "Coexistence Re

Wrong numbering for title                        To delete "(b)"
                                                 : "These frames should not be longer than the
Why the following restriction applies for B-ACK? Explanation and usage example are required. frame sent in the last block tran

                                                Additional explanation in Table 20 are as follows,-Immediate not have any an
There are two types of poll, one is immediate poll another is future poll.Unlike immediate poll, future poll does poll is to grantinfo

                                            If nodes do not need to know the RAP1 when beacon hopping is because 
  Ac
How do nodes identify RAP1 and RAP2 length at the very beginning superframe (BP 0) and RAP2 length at BP0 enabled?it's a

Wrong referencing                                 Line 13: to replace '"Table 48" with '"Table 46".Line 15:    to replace "'Table 50"

                                               Line2:
To map the appropriate terminologies already defined to replace "connection request" with "coexistence request" Line6: to rep

                                                   but not defined in the entire text.
Term "differentially coherent PHY" is mentioned Define term "differentially coherent PHY" somewhere in the text.
                                                      channel for implementation." The
" The implementer is free to select any frequencyThe sentence should be removed. sentence is basically not true and in a collis
                                                   "short-pulse burst" and "long pulse" should be referred to as
Here and throughout the text, calling both "long pulse" and "short pulse burst": "a pulse" creates confusion. "transmitted wave
                                                   pulse waveform duration and modulation be removed.
"Different data rates are obtained by changing The part of sentence in the brackets shouldscheme (while maintaining the s
                                                   Define term entire text.
The term "IR-UWB PHY" is mentioned but not defined in the "IR-UWB PHY" somewhere in the text.
                                                   Modify figure to defined in SFD section.
 Fig. depicts that SFD consists of two S_0 symbols, which is not be compliant with the SFD definition.
                                                   "Data whitening is applied
"Data whitening applied using scrambling in order to minimize the DC..." using scrambling in order to minimize the DC..."
                                                   The sentence should be removed.
It is unclear how can bit interleaving protect against quasi-static fading? Dynamic fading is not a part of TRD, thus it should not
                                                   Last signal constellation symbols is already be deleted.
"A binary labeling function that maps blocks of bits to two sentences of the paragraph should defined by the non-coherent modu
                                                   "A simple algebraic interleaver" described is mandatory or considers the sym
From previous and this paragraph it is unclear if Define precisely if the procedureis mandatory or not. Since itnot.
"Notice that" misplaced again and again…           "Notice that" should be deleted, since this is not a supplementary explanation,
                                                    in the last remaining say does not make sense. How can interleaver active in
 "the last codeword, the interleaver is active onlyThe sentence should bits"the complete opposite "the interleaver is not operate o
PHR symbol structure description is lacking.       Add sentence "PHR shall be transmitted using the same modulation as SHR a

                                              Add 3 the of SHR in the case of misdetection
Adding 3 bits of SHR preamble index can be useful for bits receiver;preamble index to the PHR. of SHR sequence (or lack of it)

                                                For example:00 - Chirp pulse01 - Chaotic pulse10 - following reasons:1. Hopp
2 bits should be added to the PHR for transmitted waveform information. This should be done for theShort-pulse burst, static sc

                                                  The sentence should be removed.
"Such SHR field is detectable for both non-coherent and differentially coherent transceivers" This sentence is not true. The prea
                                                  The
Chip time is undefined, except depicting in Fig. 123. sentence should say:"For OOK modulation, the chip time T_c= L T_w, s
                                                  both the same parameters: T_c=128ns the chip time T_c= L T_w, the OOK
If OOK and DBPSK preamble modulations have Modify sentence: "For OOK modulation, and T_w=8ns, duty-cycles of shall hav

                                                Add sentence:"In SHR.
Scrambling option in the case of short-pulse burst is undefined for the case of short-pulse burst transmitted, only static scrambli
                                                 Should be is not true.
"Data rates range from 0.5 Mbps up to 10 Mbps." Sentenceharmonized with tables 54, 55 and 63.
                                                 Instead of PRF=15.625 MHz = 101
Table 55; There is discrepancy in PRF and rest of parameters for R0, R1, R2 put 7.8125 MHz
                                                 Change one of two symbols.
Table 56. Scrambling sequence and LFSR taps (Fig. 125) should have different symbols, since they represent two different thin
                                                 Delete the sentence.
"In dynamic scrambling, the LFSR shall be clocked at the peak PRF of 499.2 MHz, Ncpb times during each burst period." The
                                                 Modify eq. accordingly.
h^{(m-1)} should be used instead h^{(k-1)} in order for expression to be correct.
                                                 Define h^{-1}.
h^{-1} should be defined for the hopping sequence procedure to be complete.
                                                 Instead of \tau_\max put \tau_\max= can change if transceiver concludes \tau_
\tau_\max should be fixed; Formulated like this the sentence suggests that N_{guard}128 ns.
                                                 Delete the end of sentence: "\tau_\max=...".
Formulated like this the sentence suggests that N_{guard} can change if transceiver concludes \tau_\max is not 128ns (which s
                                                 Modify line accordingly.
z^{(m)} should be used to be compliant with other equations.
                                                 Reduce \tau_\max to data
\tau_\max should be reduced to 96ns to allow time hopping at highest96ns rate and thus MUI mitigation.

SFD is not defined                                 Define what SFD is.

Discrepancy with N_{guard} definition in 10.10.12.   Modify one of two definitions in order for them to be the same.
                                                     Modify h^{(m)}.2. k should be omitted, since there is no mention, yet alone def
1. h should be written in a way consistent with 10.11.2 - eq. accordingly.
h^{(m)} should be used instead of h_m^k.             Modify eq. accordingly.
                                                     "for the definition, should BANs hopping sequences. The standard is dealing
k should be omitted, since there is no mention, yet alone k -th BAN" of other be deleted.
"Notice that" misplaced again and again…             "Notice that" should be deleted.
                                                     Define a_m and b_m bits. This way, information if a_m
Table 60: a_m and b_m should be defined as a function of informationas a function of it is unclear bits. represent information
                                                     Modify h^{(m)}.2. k should be omitted, since there is no mention, yet alone def
1. h should be written in a way consistent with 10.11.2 - eq. accordingly.
                                                     m should start from -1 or other expression modification should be made that co
According to the formula, the reference symbol c_{-1} is not transmitted, thus 1st information symbol is lost.
This is not supplementary information but procedure definition. "Notice that" misplaced again and again…
                                                     "Notice that" should be deleted.
                                                     Modify h^{(m)}.2. k should be omitted, since there is no mention, yet alone def
1. h should be written in a way consistent with 10.11.2 - eq. accordingly.
                                                     Modify eq. accordingly.
(93): Since T_p is different for different waveforms, value of 2ns should be inserted instead of symbol T_p, to avoid confusion.
Fig. 128 does not depict mask definition (93)        Modify Fig 128 to comply with M(f) definition.
                                                      f_{err} which should be: expression arbitrary instantaneous this point there
"Let" should be deleted, since this is definition ofThe sentence comes after"f_{err} is an that it is part of. Thus, atfrequency error f
2\pi shouldn't multiply \theta_0                     Modify eq. accordingly.
                                                     Add figure depicting chaotic mask is different values of T_w under the standa
Figure depicting chaotic pulse for different values of T_w under the standard pulse forlacking. Furthermore, having analytical ch
                                                     Define chaotic pulse envelope rise and fall times.
Chaotic pulse envelope rise and fall times are undefined.
Npad is not always positive number                   The floor function should be changed into ceil function
Npad is not always positive number                   The floor function should be changed into ceil function
                                                     The is wrong
The value of PRF for 101 mode(differential coherent)PRF for 101 mode should be changed into 7.8125
                                                     to overcome the burst error
The length 64 for bit interleaving is not sufficient Enlarge the length of interleaving
                                                      This sentence should be included in the chapter 10.11.3 and the detail explan
The sentence, "This represents the concept of the proposal Group PPM (GPPM)", is declared in draft version 6(15-10-0245-06
                                                     It is appropriate for the frequency regulation of Korea
Channel plan of 902-928MHz frequency bands is notproposed to alter the current modulation parameters for bands of 902 MHz
                                                     Rewrite not fit in the
Ambiguity on line 5 and 6. Line 5 and 6 are not well doesline 5 and 6 flow of Medical event report section and not well connecte
                                                     Separate the discovery operation to the channel channel access are
Is the T-Poll transmitted for discovery or for resource allocation? Why discovery mechanism and access operation. combined
                                                     Rewrite the pargraph.
"As illustrated in Figure 73, prior to more frame exchanges with a connected node, the hub shall transmit a 2 group of up to pM
Multicast lockup aided discovery. The concept desciribed in the paragraph is not multiple node discovery. It is more like multiple
                                                     Remove the Multicast lockup aided mechanism. The
Multicast wakeup mechanism. This section clearly describes the multi-node wakeup discovery section.section naming is approp
                                                     Resource allocation and some sort of resource alloctaion under discovery. Wh
The source allocation for MICS devices are not clear. There seems to be discovery mechanism should be separated.
                                                     Add the mechanism.
How resource allocation happens in a network scenraio of one controller device and multiple implant device? Mechanism is mis
                                                     motivation of what condition.
It is not easy to know whcih channel access should be used ineach channel access should be described.
"the PHY header shall be protected"                  the PHY header shall be appended
Shortened bits are removed prior to transmission     Shortening process can be explained better for the clarity of the standard
Pad bits should be appended after BCH encoderThe nature of pad bits can be expressed as random, sequence of altenating ze
                                                     For wake For example, some implantable cardioverter keep sleep during seve
Implant devices usually does not operate for a long period.up scheme in MICS band, it needs a additional wakeup mechanism.
This is not a document, it is a standard.            Change "document" to "standard"
There is no 802.15 MAC.                              Delete "802.15"
                                                     Verify that the correct paragraph(s) are being used here by checking the 2009
It appears that there is a mistake, you should only have one introduction paragraph to the references. These two paragraphs a
                                                      style to 10.5.2 in the 2009 style guide.
The format for the definitions does not follow theRefer guide.
                                                     Delete "Connected_NID" and review all definitions to make sure that they apply
A definition needs to be general, not specific to the standard.
                                                      This into the is an example of one that should be deleted this reason, it scop
"All terms defined in IEEE standards are incorporateddefinitionIEEE-SA Standards Definitions Database.Forbecause it has is im
                                                      Delete are expanded elsewhere.
This is not an acronym expansion. Plus AES and CCM "AES-128 CCM" and the acroread.
                                                      Don't put detailed
Clause 5 should be an informative introduction. Delete Figure 4. figures in Clause 5 that will appear elsewhere. This repeats
The subclause heading is indented too far.            Fix the indentation for 5th level subclause headings throughout the draft.
                                                       defined (nicely) in the ordering from Clause. Repeating the Only include the
The ordering of octets and bits has already beenDelete the bit and octetopening of this Figure 8 going forward. octet and bit orde
Extra "6."                                            Delete "6."
A number without a unit is spelled out.               Change "1" to "one" here and throughout the document when it is used without
                                                      Change "2" spelled out.
This is an example of a number without a unit that should beto "two" and "3" to "three" and check the rest of the draft.
                                                      Fix the cell borders
The cell borders are not correct (i.e., the cell body borders are two thick for the first two rows.)
                                                      Change as indicated.
"ith" should be "i^th" with the i italicized (variables are italics). Also, the spacing between the previous items and this paragraph
                                                       but you are not allowed a depth reorganize the subclauses so a dept of 6 is no
The depth for this heading should probably be 6,Delete the subclause heading or of 6.
Subclause numbering is wrong "6.3.11.5 (b)"           Delete the "(b)".
                                                      Lower case the title except for the first word, proper nouns and acronyms.
"6.3.11.4.1 Command – Coexistence Request", titles are lower case to match the 2009 Style Guide here and throughout the dra
                                                      Change to a requirement.
"The Battery Power Remaining field is set to" doesn't make "The Battery Power Remaining field shall be set to". This applies to
Extra "["                                             Delete "["
                                                       "Life this name to the IEEE editors for review. They may specify a better nam
An IEEE standard cannot make claims of safety.Refer critical Medical" may cross that line.
                                                       6N)". "(= length is the figure and similar lengths from the other IE figures.
Don't put the length of this field in the figure. "(= Delete The6N)" from defined in another figure. Keeping these numbers up to d
                                                       that describes the following clause. It is difficult
It is a mistake to have an introductory paragraphDelete subclause 7.1, it doesn't add any value. to keep up to date and makes
Delete "Not acknowledged??"                           Change as indicated.
"A source—a node or a hub—may"                        Change to "A source node or a hub may"
                                                      Move the "To provide or support time referenced allocations
Clause 5 isn't supposed to define normative requirements.normative descripton from Clause 5 to Clause 7. in its body area n
                                                      is nothing "as defined in 7.5.2.1."
You can't use "as defined below" because there Change tobelow that subclause. or delete the sentence or replace with "Slotte
                                                      Delete the underlining. You may want to split the cell to clarify this. The table h
"Type-I polled allocation (Poll Type = 0)" should not be underlined. In amendments, underlining means added text, so you shou
                                                      I overlap, making the figure hard to read.
In Figure 66, the boxes for Future and Immediate would suggest changing this to a standard message sequence format (ask th
Frame formats belong in Clause 6, not here.           Move this subclause to Clause 6.
The figure title exceeds the margins.                 Correct the figure title, most likely you need to split it into two lines.
                                                      Delete the dashed use of for hibernate and wakeup. here.
"To hibernate—without receiving or transmitting any traffic—in" Theset offs dashes doesn't make senseAdd instead a short para
                                                      Change as indicated.
Change "Figure 86(a)" to "Figure 86" on line 7 and line 10, change "Figure 86(b)" to "Figure 86"
                                                      Delete the column for in the MHz
"10-50 MHz HBC/EFC[a]" is undefined at this time, so you cannot put it"10-50 table.HBC/EFC[a]"
                                                      Delete the column for "2.36 GHz MBANS Band"
"2.36 GHz MBANS Band" is pending, hence it must be deleted.
                                                      Consolidate tpye-I and polled allocation.
The function of type-II plooed allocation can be achieved by using type-Itype-II polled allocation. If not, justify the need for type-I
"exclusieve" should be "exclusive"                    See comment.
"curren" should be "current"                          See comment.
                                                      Consolidate these 6.4.5 and Wakeup frame defined in clause 6.4.7.
There is not much difference between Poll frame defined in clause two frames.
"high QoS mode" is mentioned but not defined. Define what is "High QoS mode".
                                                      They need to be statements. a clearer structure and meaning. Combine gen
The subclauses of this clause overlap back and forth with similar rewritten withSome sentences are grammatically incorrect, irre
                                                      Change "impromptu" to "improvised". Remove the last sentence.
This comment is made based on an earlier comment by an active MAC participant.
"One-periodic" and "1-periodic" -- inconsistencies.   Change "one-periodic" to "1-periodic".
                                                      Restore without any markup to shalls and tone (―shall do‖ changed to ―do‖). T
Quite a few prescriptive shalls in Clause 5 were changedthe original prescriptive descriptive mays.
                                                      Change
Emphasize that all these frames are unsecured frames. the comma in line 14 to "and", add "unsecured frames" before the 1st
                                                      Change the comma in line 23 to secured fraems.
Clarify explicitly that some of these frames are unsecured frames, and some are "and", add "unsecured frames" before the 1st
Clarify "as appropriate".                             Change "as appropriate" to "if control frame authentication was not selected du
                                                      Restore all instances of of "1" are converted to "one", and one", "set … to one
This comment applies to numerous clauses. Some, but not all, instances"one" to "1" in the context of "set tosimilarly some, but
                                                      Would MAC and security make the the draft. Many, but not all, please? Co
This comment applies to many places (especially in the the technical editorclauses) infollowing formatting changesunnumbered
Typo.                                                 Move "not" to before the first "enabled" in this line.
Formatting glitch.                                    Capitalize the first letter of "type" and "subtype".
                                                      Would the technical crowded. (2) The first row needs cleared alignment. (1)
This comment applies to numerous tables. (1) These tables are a bit editor make the following formatting changes please?(3) th
Internal horizontal lines should be thinner.          Thin the internal horizontal lines below the 2nd row.
                                                      Remove the row of "Wakeup" frame from Table 3, subclause in some subcla
The Wakeup frame provides no more functionality and effectiveness than the Poll frame, as explained in detail6.4.7 and related
Unwarranted capitalization.                           Change "Field" to "field" before "encoding".
Duplicate bullet number.                              Delete "6." at the start of the text.
                                                      After "Coexistence format", well (as beacon another
The Coexistence field can be reused to define some fields for B2 frames as add "for noted in frames". comment).
                                                    field, lines 14 and 20, change "first" to "final". (2) In lines 17 is the last one of
Use backward coding for the Fragment Number (1) In so that the recipient knows if the last received fragmentand 22, delete "no
                                                    (1) Insert a new numbered bullet before this line, with the
Define the Coexistence field for B2 frames, so that some fields don't need to appear in the frame payload. following text: h) In B
                                                     6. While Clause 7 is written in prescriptive style (shall, should,
This comment applies to many places of Clause Restore all instances of "shall" to "must" throughout Clause 6. may) to specify
                                                    Would the technical the draft (especially in spacings to security clauses). Th
This comment applies to most paragraphs following a bulleted item ineditor please adjust thethe MAC andbe a bit more uniform
                                                    Move the misplaced commas?
Comma misplaced. Did reformatting in D0 generate othercomma from before to after Figure 12.
"not" misplaced.                                    Move "not" to before the first "enabled" in this line.
"not" misplaced.                                    Move "not" to before the first "enabled" in this line.
Simplify naming.                                    (1) Delete "Required" from the "Security Level Required" field in Figure 18. (2)
This comment applies to many tables in Clause 6. "Field value decimal"… please insert "in" before "decimal" J71and make "i
                                                    Technical Editor, would you
"Protocol" is not part of the field anymore.        Delete "Protocol" from the heading.
Formatting glitch.                                  Make the two internal lines (below the 2nd row) thinner.
                                                    (1) and the the B+EAP1 Length and EAP2 Length which (2) frame is Status
There are some inconsistencies between this frameRemove Connection Assignment frame in 24 onfields. thisMove the based.
Unwarranted capitalization.                         In the table heading, change "Field" to "field".
                                                    (1) Change "Request" discussed, let alone Change "Command Coexistence
(1) The frame formats of these two coexistence commands were neverto "Time Sharing". (2)approved, in the MAC- subgroup. (
                                                    Promote 6.3.11.4.1 to one level higher as 6.3.12, and keep the
6.3.11.4.1 should be a parent subclause of the three subclauses that follow, instead of being at the same level. subclauses tha
                                                    Change "Command - Coexistence Request" to "Command two separate Time
There is no functional difference specified for "coexistence request" and "coexistence response". Hence no - Coexistenceframe
                                                    (1) Change to to frame defined here.
These lines need to be revised in view of the changes made "in"the "for" before "a Command". (2) Insert "time sharing enabled"
                                                    (1) needed to be reworked to be consistent in naming field proposed other se
(1) Both the definition and table for "Piconet priority"Change "Piconet Priority" to "BAN Services", a new and format within the Co
                                                    Remove them along with the figure and table the "status" field, which, however
These are just duplicates of the subclauses for the "Coexistence Request" version, except for within.
Incorrect level for these three subclauses.         Promote 6.3.11.5.4 to one level higher, and keep the two subclauses that defin
Incorrect level for this subclause.                 Promote 6.3.11.5.7 to one level higher.
Incorrect level for this subclause.                 Change "in" to "for" before "a Command".
                                                    (1) Change set…, but to the relay node will set this field.
(1) locally broadcast but not locally multicast. (2) the field is "multicast"not "broadcast" in line 5. (2) Reword the 2nd and 3rd se
                                                    Remove the the quality of the field presence of noise and interference.
The "received signal strength of signals" does not truly reflectRelay Link Qualitylink inand all references to it, unless the propose
                                                    (1) or the MAC header of the definition subclauses (and Table 13 which has a
(1) Many fields are already contained in the beacon Remove all fields and theirB2 frame, and should not be duplicated here, per
Typo.                                               Change "rage" to "rate" in the table heading.
Formatting glitch.                                  Make the two internal lines (below the 2nd row) thinner.
Two much space.                                     Delete this empty line.
                                                    Change "to indicate
Some clarification is needed on why and when this IE is included. ..lengths" to "foretell some information on the superframe (
                                                    Add to needed to be separately included, so is the beacon shifting sequence
If superframe length and allocation slot length fields arethe end of the current IE an optional "Beacon Shifting Sequence" field. f
                                                    somewhere else.
Avoid repeating a definition that is already given Change these two lines to the following: The Superframe Length field is as de
                                                    somewhere else.
Avoid repeating a definition that is already given Change these two lines to the following: The Allocation Slot Length field is as d
                                                    Add
A new subclause is needed to define the new field. a new subclause, 6.7.1.3 Beacon Shifting Sequence, with the following tex
Figure formatting glitch.                           Insert two dashed lines at the start of the bottom fields to indicate continuation
Figure formatting glitch.                           Insert two dashed lines at the start of the bottom fields to indicate continuation
                                                    Insert a Assignment frame should be defined "Node Address" field.
The "Status Code" field now in the Multinode Connectionone-octet "Status Code" field after the on a per node basis and hence
Inconsistent frame reference.                       Change the paragraph to "All the fields after the Length field pertain to the sam
                                                    Remove the row containing functionality
As explained in related comments, the Wakeup frame provides no additional"Wakeup". to the Poll frame.
Typo.                                               Add "final" before "frame sent", and change "last" to "previous" before "block tr
                                                    After "pSIFS", add ", depending on
Need to make a connection with burst mode transmission defined in the PHY spec. whether it is setting the block transmission
Figure 55 was mistakenly changed in this draft. Remove all the test boxes other than those indicating a frame.
                                                    It is time to resolve Type II access phases, other than basis. Remove delayed
(1) There is no technical justification for having separate Type I and technical comments on a technical fragmenting the superfra
                                                     can "send" add "at most".
Need to make it clear that an unconnected nodeAfternot send more than one frame in a shared polled allocation.
Formatting glitch.                                  Make the first "n" a regular instead of an italic letter in "fun ction".
Typo.                                               After "which" change "are" to "is".
                                                    In line 36 of needs to be decoupled from add "the appropriate guard time in th
The "appropriate guard time" is not a fixed value, and hence page 78, after "shorter than" the parameter referenced earlierplus"
Figure 65 was mistakenly changed in this draft. Remove all the test boxes that appear on the top or bottom of the figure.
                                                    Make "Frame" plural
Formatting glitch in the heading of Table 20, introduced in this draft. and delete "(1-1)".
The last statement of Table 20 is not quite clear.Remove the last row of Table 20, and add a new short paragraph after Table 2
Figure 66 was mistakenly changed in this draft. Remove all the test boxes other than those indicating a frame.
Unneeded word at the end.                           Delete "at".
Unfinished cleanup from last draft.                 Delete ", and one or both of the MSDU … nonzero values".
                                                   Change "the hub shall respond with" to
The hub may also send an unsolicited Connection Assignment frame as intended here. ", requested by the node or initiated by
                                                   Delete "a", "b", 'c" in these figure captions.
Figure 69, Figure 70, Figure 71 already have separate figure numbers, but were numbered by "a", "b", and "c" further in this dra
                                                   After this cannot be add a new one
Need to explicity state that an ended scheduled allocation paragraph used anymore. as follows: A node or a hub shall not send
                                                    have appeared here.
This subclause makes no sense and should not Remove it.
                                                     -- when?
No shalls. "…shall send the wakeup messages"Remove these two paragraphs, as they provide unnecessary introductory infor
                                                     this is not how
I explained to the proposers back at the F2F thatRemove them. the I-Ack works: A recipient would not go into the payload to c
                                                   Remove these duplicate but inaccurate and incomplete poll, as specified here.
(1) It increases complexity and decreases efficiency to have a wakeup followed by an Ack and then by a descriptions of the unic
Typo.                                              Change node to "nodes".
                                                   Change "session to "phase" throughout this subclause and Figure 76.
Do not use "session", which has a special meaning per MICS band regulations.
                                                    in Fig. 76.
Need to make a connection with "lockup phase" After "Poll frames", add "forming a lockup phase and".
                                                   After "polled
Need to make a connection with "individual phase" in Fig. 76.allocation", add " thus starting the individual phase for the node as
                                                   Change "shall" to "should".
A "shall" may not always be justified as the nodes might not know in advance the time of pending frame exchanges.
                                                     might have missed earlier
A "shall" may not always be justified as the nodeChange "shall" to "should". polls.
                                                   intent of this duplicate more accurately and consistently, as explained further
Figure 76 and the related text accomplishes the Remove this subclausebut inaccurate and inconsistent subclause 7.8.2.1.4.
                                                    more power consumption for described scheme was not to wake up out and
(1) The described mechanism would only cause It is time to recognize that the all nodes, which would havewell thought several t
                                                   After "it should", performed on other channels.
Tighten up the sentence do expressly convey the same behavior add "similarly send and".
                                                   (1) --- since pMICSFrameSpace after            same its different transmission".
Frame spacing does no longer have the same valueDelete "atthe next frame may be on the end ofor alast framechannel.
"emergency" is a data frame name.                  Capitalize the first letter of "emergency" for consistency.
                                                   Rewrite the whole subclause to address the outstanding issues.
This subclause has yet to define the frame structures used to support the relay functionality, and to specify the access methods
                                                   (1) Move them to end of of 7.12 this new subclause, 7.12.5. that follows.
It will have a better structure to create a separate subclause at thethe end 7.12 for as a paragraph and the table Applicability guid
                                                   Rewrite the implementation to specify does hub is supposed to do for coexis
Much of this subclause is either tangential to coexistence or whole subclausespecific. Ithow a not prescribe testable normative
                                                   Delete "and load reduction" from the heading.
Load reduction is covered in a separate subclause later.
                                                   Delete them as they are not germane to normative coexistence behaviors.
These are not about coexistence per se, but more about BAN creation (and maintenance) which is already described in 7.4.
                                                   Delete them that are implementation germane to normative coexistence beha
Again these are not specific to coexistence but specify things as they are not correct orspecific (which are generally not to be pa
                                                   Delete these that as they reference frames and fields that are not defined or
It is a nonfeasance for someone not to understand somethinglines,he is proposing to a standards group. It is a misfeasanceor c
                                                     coordinator as they are not with respect to it if it is not implementation specific
(1) Again what is a BAN descriptor and what is aDelete them supposed to do defined or germane to normative coexistence beh
                                                   Delete them as they have no substance or are not germane to normative coex
(1) Why shalls? A hub may choose no channel at all and create no BAN. (2) How is a hub supposed to "utilize the information
No need for a new, lower level subclause           Delete the heading.
Certainly not a shall.                             Rephrase them as a "may".
Inaccurate or repeated sentences.                  Remove them.
                                                   Remove 7.12.3.1 if these fundamental issues are not addressed inconsistent
(1) Connection request,, coexistence request, coexistence assignment, coexistence assignment request -- still soby end of the
Is this in essence time sharing as well?           Merge this subclause with 7.12.3.1. Both are about time sharing, and may be
                                                     sharing this subclause to but level higher, be change the heading to "Code d
(1) This subclause should not be under the timePromote subclause 7.12.3, one rather shouldand in parallel. (2) The heading do
                                                   Remove the subclause this subclause -- which coexistence per se, or rewrite
(a) How can interoperability tests be designed based on the language ofwhich is not germane to again is so unfocused and has
                                                     an earlier comment.
This is part of the paragraph with issues noted inRemove it or refine it together with the earlier part of the subclause.
Rephrase the heading in MAC terms.                 Change the heading to "Allocation reduction".
                                                   Rephrase the subclause The 3rd it more concise and precise. Suggested tex
The first two paragraphs need to be rewritten in more concise language. so makeand 4th paragraphs are a repeat of the gener
It is hard to interpret and use table 22.          Edit it -- in line with the BAN's designated services defined for time sharing.
                                                   Add in a Local_Broadcast_NID" before the comma.
Need to include locally broadcast T-Poll frames used "and two-hop extension.
                                                   Restore in this draft existed prior to D0, at the MAC subgroup. Was any usua
This subclause was modified, incorrectly or inaccurately, the text that without a discussionor refine it within the MAC subgroup.
                                                   Change the value entry to pMICSMcastPollSeparation + pMICSPreambleTxTim
Incorrect equation and parameter value for pMICSMcastPollRxTime.
                                                   Change the value entry to ceiling[pMICSChannelsTotal × (pMICSMcastPollRxT
Incorrect equation and parameter value for pMICSMcastPolls.
                                                   Change the value entry
Incorrect equation and parameter value for pMICSMcastPollSeparation. to pMICSPollTxTime + pMIFS = 1614 us
                                                   Change since it is defined with respect to per channel. A large value for this p
The value for pMICSNodeEmergencyRetries is too large the value to 2.
See proposed change.                               Change "NB," to "narrow band (NB) PHY, ", "slotted" to "Slotted", and "UW" to
                                                   Replace the entry the MAC subgroup.
The value in the last row was put in (by me) without a discussion atwith the following: ≥ transmit time of a PHY frame with a MA
Formatting glitch.                                 Make the text in the first row bold and centered, and the bottom line bold.
Formatting glitch.                                 Insert a space before and after each plus sign of this table.
                                                   Revise the an equation containing the underlying parameters. (2) This value sh
(1) The value for pAllohaSlotLength should be first given by entry as noted in the comment.
                                                   Replace the entry with the following: ≥ transmit time of a PHY frame with a MA
The value in the last row was put in without a discussion at the MAC subgroup.
                                                    After line 12 add a new paragraph: Support for
                                                    mandatory and optional cipher functions is
Missing introduction to 8.4                         clarified in 8.4.

Missing comma.                                      Insert a comma after the closing parenthesis.
This comment applies to all the equations in        Technical Editor, please make all the
Clause 8. All these math equations need to be       equations (but not the equation numbers)
in italic font.                                     throughout Clause 8 in italic font.
An underscore after "P" was artificially added in
this rev, resulting in inconsistency with the       Remove the underscore in both lines 29 and
corresponding figure.                               30.
An underscore after "P" was artificially added in
this rev, resulting in inconsistency with the       Remove the underscore in both lines 18 and
corresponding figure.                               19.
An underscore after "P" was artificially added in
this rev, resulting in inconsistency with the       Remove the underscore in both lines 17 and
corresponding figure.                               18.
Too crowded.                                        Leave a blank line before line 12.
Too crowded.                                        Leave a blank line before line 22.
                                                    (1) Insert the following as the first paragraph of
                                                    this subclause:

                                                    Frames shall be transmitted as secured or
                                                    unsecured frames according to Figure 4 and
                                                    Table 23, wherein SL and CFA denote the
                                                    Security Level field and the Control Frame
                                                    Authentication field, respectively, of the
                                                    Security Suite Selector field contained in the
                                                    last Association frame exchanged between the
                                                    sender and the recipient.

It has been suggested to explicitly state what      (2) Create a new table stating the conditions
frames are transmitted as secured frames at         for transmitting unsecured and secured
which conditions.                                   frames.
                                                    Delete the space after "97", and move the next
                                                    line (line 30) back to line 29. Further insert two
Formatting glitch due to misplaced period.          spaces after the period.
SIFS and MIFS are not referenced elsewhere
in the spec. They are not referenced as pSIFS
and pMIFS.                                        Delete this subclause along with Table 45.
                                                  Technical Editor, would you please decapitalize
                                                  in the headings the first letters of those words
These comments apply to many places in            that are not proper nouns or part of a field
Clauses 9-11. Some headings have all the first name throughout these clauses? (If they are
letters capitalized, which is not consistent with part of a field name, they need to be
the required IEEE format.                         capitalized.)
Incorrect grammar.                                Change "media" to "medium".
"during association" -- how and why to enforce
this?                                             Delete "during association".
(1) This subclause is out of PHY's scope. (2)
"full function devices (FFD)" and "reduced
function devices (RFD)" are not defined
elsewhere in the draft.                           Remove this subclause.

(1) This subclause is out of PHY's scope. (2)
Item 1 is addressed in the MAC portion. (3)
Item 2 is purely imaginary. How can "the
coordinator" "enforce non-medical devices to
reduce their EIRP at transmitters"?               Remove this subclause.
                                                  Change "From MAC Via SAP" to "From PHY
Which "SAP"?                                      SAP".
                                                  Change "payload from the MAC via SAP" to
Incorrect statement.                              "MAC frame".
How does the UWB PHY header encode a
MAC payload of 256 octets?                        Change "256" to "255".
                                                  (1) In line 21 and inside Figure 118, change
                                                  "MAC payload" to "MAC frame body". (2) In
Incorrect field names in both the text and        line 21, change "CRC-16-ITU (2 octets) parity
figure. It is advisable to reference the correct  bits" to "FCS (2 octets)". (3) In Figure 118,
name or ask for consultation.                     change "CRC-16" to "FCS".
The narrow band PHY supports burst mode
transmission which reduces inter-frame
spacing from SIFS to MIFS. It is advisable that Use a bit in the PHR to as a "Burst Mode" field,
the UWB PHY had the same support.                in analogy with 9.3.1.3.

Erroneous heading. Table 52 shows the field
name is HARQ, but not HARQ enable. It's also
more relevant to denote the field as HARQ.   Delete "enable".
                                             The sender needs to set H0 and H1 in such a
                                             way that the recipient PHY can unambiguously
                                             distinguish a new PSDU containing the
(1) Both H0 and H1 need to be defined here.  "information bits" for the first time from a
(2) 10.16.3 fails to define H1 (and H0)      retried PSDU containing the "information bits"
correctly.                                   transmitted before.

(1) The last statement is out of PHY's scope --
the PHY cannot tell whether it is part of a hub
or a node. (2) It is not clear either -- "use
preamble with minimum received power level"?      Remove this sentence
Improper language for the standards -- "can be
achieved". The statement does not mean
anything for interoperability.                    Remove this sentence
Hybrid type II ARQ? Is there a "pure" type II
ARQ?                                              Change the heading to "Type II hybrid ARQ"!
Only one error detection code, but not multiple
codes, is defined at the MAC.                     Make "codes" singular.
Only one invertible code, but not multiple such
codes, needs to be defined for HARQ. In fact,
none is defined!                                  Make "codes" singular.
Where is the invertible code defined? How can
interoperability be achieved without a
predefined code? The MAC subgroup had to
spend enormous time creating a mechanism
and drafting the text to support HARQ, yet the Remove HARQ altogether unless such a code
HARQ itself was, and is, not even fully defined is defined or referenced here at the July IEEE
at this stage?                                  session.
                                                Explicitly state that the information bits are the
                                                concatentation of the MAC header and MAC
What are the information bits?                  frame body.
Incorrectly referenced table number.            This should be Table 62.
We already explained to the HARQ proposer
that NACK for HARQ is supported through No Change "NACK" to "No Ack" in the text, table,
Ack at the MAC level.                           and figure throughout this subclause.

HARQ enabled transmission alternates
between a packet containing D and a packet
containing P_sub_D. Accordingly, only two
states are needed in both Table 62 and Figure
135. State 2 is just state 0 in Table 62, and
column 3 is essentially column 1 in Figure 135.
It is simply misleading to have three states and   (1) In Table 62, delete the last row; change
columns. It is advisable to cnsult with            "go to 1" to "go to "state 1", and "go to 2" to "go
references such as Lin and Costello's "Error       to state 0". (2) In Figure 135, delete almost the
Control Coding" in writing and drawing up          entire 3rd column, and have the returning
HARQ.                                              arrow go to 1st column.
How can the transmitter tx D head, which was
the received version of D in the 1st column? If
this comment is still not clear, how can the
transmitter know the received version of its       Remove HARQ altogether unless the issue is
earlier transmitted D?                             addressed.

Incorrect field name in Figure 139.                Change "MAC Payload" to "MAC Frame Body".
                                                   Replace "Mbps" with "Mb/s" (here and
                                                   throughout the document -> search and
"Mbps" is not a SI unit                            replace)
Entry for PRF (pulse-repetition frequency) is
missing                                            Create entry for PRF
Entry for PSD (see Figure 128)                     Create entry for PSD
                                                   Replace "kbps" with "kb/s" (here and
                                                   throughout the document -> search and
"kbps" in Table 14 is not a SI unit                replace)
"and spell out what acronym means first time in
document BCH parity bits."
seems to contain an editorial comment           Replace with "and BCH parity bits"

When ammending communication                     Insert at least two unassigned bits in the
standards one of the issues often encountered PHY header in Figure 108. Suggested position:
is the lack of unassigned fields for future use. starting at position 15
When ammending communication                       Insert at least two unassigned bits in the
standards one of the issues often encountered      PHY header in Figure 108. Suggested position:
is the lack of unassigned fields for future use.   starting at position 15
"Figure 126" should read "Figure 128"              Replace "Figure 126" with "Figure 128"
What is meant by "Level" in Figure 129?            Replace "Level" with more suitable label (e.g.,"Relative PSD")
Figure 129 is not referenced in the text body      Delete Figure 129 or create reference in the text body

Where is DRF "Mode" defined?                       Please clarify what is meant by mode and how it's selected, or should there be

Where is the reference for implmenting CRC8? Need to add a section or reference to an external document(s) that specifies t
Figure 105: there are unintended line breaks. Remove unintended line breaks (there are at least 4 places)
                                                     ―parameters that is needed‖ to ―parameters that are needed‖
Seed table reference is missing                      bit value and corresponding seed table should be referenced here
                                                      Ncw to Ncw = 0
In case of un-coded transmission no need to setRemovezero; (n-k) is anyway zero.
                                                     Edit Figure 113: x(n) consistent.
Notations for the content of the shift register for the scrambler are not--> x[n] (use bracket)
                                                     Use shall be at most or lower than the
The minimum sensitivity numbers can be lower than the numbers listed in Table 49. numbers in Table 49.
                                                       the minimum receiver "10 dB above corresponds to the lowest data rate
ED Threshold should be defined as 10 dB aboveModify first bullet to saysensitity, whichthe minimum specified receiver sensitivi
                                                      But the same terminology
"physical layer convergence procedure" (PLCP).Use in Acronyms section, PLCP stands for "physical layer convergence protoco
Acronym SHR is not well defined                      Synchronization Header (SHR)?, also put it in Acronyms section
                                                       is stated in Sec 10.18. This sentence says CCA provided by PHY, but Sec 10.
The statement on CCA looks different from whatMake clear on CCA.
                                                      the later items in E.g., to 24 to the main sections
Some of items (lines 18 to 24) are not aligned toAlign the sections.line 18"one mandatory modulation", but in Sec 10.11 two mod
"high QoS mode" is not defined at all.               Define clearly what the "high QoS mode" means
"high QoS mode" is not defined at all.               Define clearly "high QoS mode" means and "applications with high QoS mode"
                                                     "transmit" --> "operate"
"transmit" is too narrow in meaning in the sentence "A compliant UWB device shall transmit in at least one of the specified band
Reference is not correct                             "table 10" --> "table 61"
                                                      (on-off modulation with 64-ary waveform coding) and differentially encoded bin
The sentence "A combination of on-off signaling Modify the sentence to avoid any confusion.
                                                       also not defined.
What is "the default mode"? "High QoS mode" isDefine "default mode" and "high QoS mode". In my opinion, all the modes shou
                                                     FEC should be also employed as mandatory for beacon transmission.
Why should FEC be optional during association (beacon transmission)? Beacon should be robust and well protected using FEC
                                                       means a coordinator, and does RFD means a node device? It is not mentione
FFD and RFD are not clearly defined. Does FFDMake RFD and FFD clear in definition. Clearly state what "IR-UWB PHY" mean
Figure 116 needs to be revised.                      Revise figure 116: refer to narrowband PHY, adding length information, and etc
                                                      text.
Figure 116: "S_0" is not defined anywhere in theDefined SFD signal structure.
"length of the payload" is not exactly correct.      "length of the payload" --> "length of MAC frame body"
                                                     Use "header is better to be aligned with narrowband PHY
The terminology "error detection parity bits CRC-4-ITU" wouldcheck sequence (HCS)" as in narrowband PHY.
                                                     Also include packet detection, timing synchronization, and carrier frequency off
The preamble part of SHR are intended more than just coarse timing.
Figure 117 does not include all the PHY operations.  Figure 117 should be revised to include all the PHY layer operations which incl
"MAC payload (0-256 octets)" is not correct.         It should be "MAC frame body (0-255 octets)"
                                                     Use "frame with narrowband PHY
The terminology "CRC-16-ITU" would is better to be aligned check sequence (FCS)" as in narrowband PHY
Figure 118: need to revise the figure.               Use correct terminologies "MAC frame body", and "FCS", and add length inform
First sentence needs to be revised                   E.g., "Data whitening technique shall be applied using a bit scrambling ..."
"initialization vector (sync-word), xinit"           "sync-word" --> "scrambler word", "xinit" --> "x_init" ("init" in subscript)
                                                     Remove the sentence
The sentence, "The sync-words are placed in the data stream through equal intervals, i.e., each frame." is not clear.
                                                     Refer to
Scrambler section could be aligned to narrowband PHY the latest scrambler section in the narrowband PHY
                                                     Align the text and
The bit order is not matched to what is presented in Figure 120. the figure. Probably the current text is correct and just revise
                                                      set to zero." is there any un-coded transmission?
"In the case of un-coded transmission, N_CW is If not, just remove the sentence
                                                     This is not mentioned so constellation modify is sentence.
The sentence "A binary labeling function that maps blocks of bits to signalfar, so need tosymbolsthealready defined by the non-c
                                                     Maybe "n" and "PI(n)" are indices to the scrambled, encoded, zero-padded (if n
Equation 75: "n" and "PI(n)" are not clearly defined. Generally functionality of bit interleaver is not clear: e.g., what is range of n?
                                                     Modify the PHR structure to one of the followings: 1) PHR non-coherent reduce
The PHY header (PHR) is 31 bits in length based on the BCH (31,19) code, and is not compatible with the information is UWB
Terminologies could be aligned to narrowband PHY     "PLCP header" consists of "PHY header", "header check sequence (HCS)", an
Figure 121: needs to revise                          Use the consistent terminologies: "PLCP header" = "PHY header" + "header c
                                                     Use 52.
Notations (L_1, ..., L_7) are not consistent with Tablethe same notations in the text and the table.
"synch-word" looks not correct.                      "Scrambler seed" may be a better terminology.
Title "CRC-4-ITU"                                  Change the subsection title to "Header Check Sequence *(HCS)"
                                                   Use "BCH (31,19) encoder" and add a comment like "BCH (31, 19) code is a s
Terminology "shortened BCH(31,19) encoder" does not look correct.
                                                   Revise the sentence, can be better stated.
Need to revise the sentence. E.g., "SHR is formed by the preamble..." and also include more receiver functionalities that can do
                                                   Make it clear 8 can be assigned to each channel. Then later say the 8 A good
It is not clear how the 8 preamble sequences are assigned: allhow the preamble codes are assigned to frequency band. sequen
                                                   Remove the in Table
The sentence "Notice that Kasami sequences are binary and sentence53, -1 was replaced by 0" is not necessary.
                                                     the the optimized repetition acquisition, and estimation at all receiver.
N_sync = 4 is not large enough to accomplish allFind necessary assessment, number (N_sync) considering the the receiver func
Incorrect reference "table 50"                     "table 50" --> "table 53"
Figure 123 needs to be revised.                    Use the same font and include length information, and etc.
"0"??                                              Correct the reference
No detail is specified on SFD.                     Specify the SFD signal structure? Also check if it is aligned to Figure 116.
                                                    exactly exact date Table the tables.
Data rate range (0.5 Mbps up to 10 Mbps) is not Use the matched to rate in 54 and 55.
                                                   Timing and data rate related parameters should be revised using integer
Table 54: Timing and data rate related parameters should be able to be derived by a simple hardware from basic clock. multip
                                                   Timing and data rate related parameters should be revised using integer
Table 55: Timing and data rate related parameters should be able to be derived by a simple hardware from basic clock. multip
Table 54:unit should be in parenthesis             "nsec" should be with parenthesis
Table 55:unit should be in parenthesis             "nsec" should be with parenthesis
                                                   Last two also should be
Table 54: last two rows should be indicated as "reserved"rows in the text.indicated as "reserved" also in the text.
                                                   the table?
Table 55: What does "Modul. Mode 2" means in "Modul. Mode 2" --> "Modulation"
Table 55: What does "Spr." means in the table? "Spr." --> "Spreading factor" or use math symbol, e.g., "S" and define in the tex
                                                   Add
Adding a reference to time hopping would be better. a reference section (Sec 10.11.2) next to the text "time hopping".
                                                   A
Not clear which column in Table 55 it is referring. dd the same terminology or math symbol used in the Table 55 in the text.
What does "Modulation mode 2" means?               Use a general terminology, e.g., "Modulation"
                                                   Revise the definition.
"R_b = R_s . FECrate": "FECrate" first appears here with nomath expression with clear definition.
Short pulse duration is not exactly 2ns.           Short pulse duration is 1/499.2MHz which approximately 2ns, but not exactly 2
                                                   Suggested sentence: "N_guard parameter is used in time-hopping sequence g
Need to revise the sentence to better express the parameter.
                                                   Apply dynamic scrambling specified in Section 10.11.1.1 as mandatory in crea
Static chip-level scrambling specified in the section is using a fixed scrambling sequence repeatedly in each symbol, whichall th
                                                   Make it clear how this sequence s_n is used in the math fact that the sequence
Not clear how this sequence s_n is used in the math expression for modulation output, e.g., Eq (86). The expression for modula
                                                   Modify the to Sec 10.7.
Table 57: Preamble code number runs 0 to 7 is not aligned preamble code number column so that it runs 1 to 8.
                                                     "not computed lines fly", but is fixed for confusion.
These lines are not necessary to put. N_guard isJust remove theon the12 - 15 to avoid any each data rate as shown in data rate
The hyphen before "where..." is not necessary. Remove the unnecessary hyphen before "where...".
Eq (81): superscript k-1 should be m-1             Eq (81): superscript k-1 should be m-1.
                                                   Add "k >= 0" and initial value for time-hopping sequence "h^{(k-1)} = 0".
Need to add range of "k" and initial parameter for time-hopping sequence.
                                                    at the receivers, one mode 64-ary waveform-coding binary PPM, which requ
Non-coherent modulation requires two decodersAdd a new PHY UWBfor thethat is based on BCH and(aka GPPM), and the ot
                                                   Use the correct chain is not necessary to Remove the receiver chain in Figure
Figure 126: reference to symbol mapper is not correct. Receiver reference (Sec 10.11.3.1).show in the figure.
The sentence is not grammatically correct.         Revise the sentence.
                                                    is used on the Table 58). Notation h_m^k for time-hopping sequence is not th
Eq (85): d_n^m is not defined (note notation d_k1) Define d_n^m, 2) Use the same notation for time-hopping sequence as inali
                                                   Delete redundant
"m" and "T_sym" are repeated. "h_m^k" should be "h^{(11m+n)}" "m" and "T_sym" images. "h_m^k" should "h^{(11m+n)}"
                                                   Modify the Eq using "i" running
Eq (86): better to use the index "i" running from 0 for concise math expression. from 0 to N_cpb -1 for concise math expression
                                                   Just remove the Section.
This section is not necessary since it is implementation dependent.
                                                   Use the correct not correct. Receiver chain is 10.11.4.2). Remove the the figu
Figure 127: references to symbol mapper and pulse shaping arereferences (Sec 10.11.4.1 andnot necessary to show in receive
Table 59 title needs a correction.                 "DBSK" --> "DBPSK"
                                                   1) Use the what is used for time-hopping sequence as in the
Notation h_m^k for time-hopping sequence is not aligned tosame notationin Sec 10.11.2. And T_w is missing. Sec 10.11.2: it s
                                                   Modify the Eq using "i" running
Eq (89): better to use the index "i" running from 0 for concise math expression. from 0 to N_cpb -1 for concise math expression
                                                   Find a should be explicitly specified.
"Seq_m" is not the best notation. Also Barker sequenceconcise notation for "Seq_m". Specify the Barker sequence clearly.
Title is not very relevant to the table.           Use a better title, e.g., "Operating frequency bands for UWB PHY"
                                                   Just remove the sentence "The implementer is free to choose for the pulse of
"The implementer is free to choose the truncation of r(t)." is not very logical. Remember "r(t)" is reference pulsethe truncation cr
Figure 129 is not necessary.                       Remove Figure 129.
                                                   A
Chaotic pulse waveform is not specified in detail. dd detail specification for chaotic pulse.
                                                   Just specify for the case of BCH like
Only BCH code is use on UWB PHY. So not necessary to mention a general termcode."invertible code".
Reference "6.2.3" is correct??                     Use the correct reference.
                                                   Just specify for the case of BCH like
Only BCH code is use on UWB PHY. So not necessary to mention a general termcode."invertible code".
Reference "table 11" is correct?                   Use the correct reference.
                                                   What are the
Table 62: What are the "1" and "2" in the "Rx Action" column? "1" and "2" in the "Rx Action" column?
                                                   Just So not necessary to mention a general term like "invertible code".
Figure 135 title: Only BCH code is use on UWB PHY.specify for the case of BCH code.
"BRF"?                                             "BRF" --> "B_RF"
Table 64 is not referred in the text               Table 64 is not referred in the text
Eq (102): What is M(w_m t)?                        Specify M(w_m t) more explicitly with mathematical expression.
                                                   Just remove dependent.
This section is not necessary to put since it is implementationthe Section.
                                                   Is Slotted aloha no need to If yes, then no need to mention other CCA options
This section is not clear. Is Slotted aloha mandatory? If yes, thenmandatory? mention other CCA options (energy detection or pr
A section on operating frequency bands is missing  Insert a section that defines the operating frequency bands

A section on channel numbering is missing         Insert a section that defines the channel numbers and center frequencies

                                               Insert a EDTime, CCATime, Channel Switch Time, etc.)
A section on PHY layer timing is missing (pSIFS, pMIFS,section that defines the PHY layer timing

                                                Insert a etc.)
A section on inter-frame spacing is missing (SIFS, MIFS,section that defines the inter-frame spacing

                                                  Insert sections on rx-to-tx, tx-to-rx turnaround times
Sections on rx-to-tx, tx-to-rx turnaround times are missing

                                                 Insert
A section of center frequency switch time is missing a section on center frequency switch time

                                                Insert sections on is missing
Sections on transmit center and symbol clock frequency tolerancestransmit center and symbol clock frequency tolerances

                                                  is missing
Section of transmitter constellation error or EVMInsert a section on transmitter constellation error or EVM

                                                Insert
A section on adjacent channel power ratio is missing a section on adjacent channel power ratio

                                                 Insert a section on adjacent channel rejection
A section on adjacent channel rejection is missing

                                               Add ED measurement time and receiver clear channel assessment are missin
Sections on receiver energy detection, ED threshold, seections on receiver energy detection, ED threshold, ED measurement ti

                                             Pick either HBC or to the reader
HBC and EFC are used interchangeably and this leads to confusionEFC and use it consistently throughout spec. Preference is
                                             Remove the paragraph altogether
This paragraph assumes a particular implementation, which should not be included in a standards
Change bandwidth is 8 MHz, not 4 MHz         Replace "with the bandwidth of 4MHz" by "with the bandwidth of 8MHz"

The header should be referred to as a PLCP HeaderReplace "Header" with "PLCP Header"
                                                 Remove
PHY Payload is not a typical term in IEEE 802 standards PHY Payload and just replace it with PSDU
Figure 139 needs to be modified                  Replace PHY Header with PLCP Header, and PHY Payload with PSDU and sh
                                                 Remove last part of sentence: "and transmitted value
Aren't the signal transmitted actually analog? The last part of sentence is confusing and adds noin digital form"
                                                 the dominant frequency? What
Don‘t understand the second sentence. What is Clarify by rewritting sentence does it mean? What does it mean to say "most
Figure 142, what is f_ck?                        Define the values for f_ck

                                             Please clarify. Can't built a transmitter unless it is known how to is the the Gold
How are the various preambles selected? How do you select which Gold Code polynomial? Who does selection, select PHY ba

                                                  Please section
Paragraph is very confusing and hard to understand thisrewrite to clarify
                                                  Remove paragraph, Figure 143
This text doesn't belong in a standard. This text belongs in an academic paper and last line after figure

Figure 144, what is f_ck?                         Define the values for f_ck

                                             Please clarify. Can't built a transmitter unless it is parameter? Or is it the MAC?
How do you select which Gold Code polynomial? Who does selection, is the PHY based on some known how to select the Gold

Reference is missing                              Replace "0" with "Table 70"?
What is DRF?                                      Define DRF. Also define how DRF is selected? Who makes decision PHY or M
Is spreading factor 64 for this section? Why?       Clarify

Is Table 71 for DRF or RI? It is not clear?         Clarify

                                                 Bits should be mapped
How are bits in table mapped to the fields? Is LSB first? Or MSB first? LSB first

                                                      Replace "3 ~ 4" with "3 ~ 5"
Bit position 3 ~ 4 is only 2 bits, but 3 bits are defined
"-" doesn't imply reserved                            Replace "-" with "Reserved"
                                                      "no 01 for
Why are two bit values for sync (00,01) used for Use sync"? no sync and 00 for a Reserved value

                                              Clarify
What is difference between normal and dedicated mode? Why is it needed? Who makes decision (PHY or MAC) to use norma

                                              Clarify
Why are there 3 bits used for BAN ID? How are the BAN ID assigned? Does this mean that 8 simultaneously operating piconet

CRC8 is undefined                                   Please specify the CRC8 polynomial and how it is implemented

                                                Replace "master device and be more generic
Why does this field need to be specified for master and slave devices, shouldslave nodes" with "two devices"

"1x" notation is confusing                    Replace "is set to 1x" with "has a one in the first bit of the field"
                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                                     Specify
What happens if the first bit is set to zero (i.e. no-sync)? text for the condition when the first bit is zero (i.e. no sync)

                                                Replace "master device and particular slave
Why does this field need to be specified for master and slave devices, shouldabe more generic device" with "two devices"

What does 1:1 mean?                                 Explain and clarify

                                            Remore the dedicated device be section 11.6.2
Why is a dedicated mode needed? This is a TDD system, why would a mode and communicating at the same time as another d

                                             Define
What is C, N and L? These values should be specified C, N and L and their values

                                               Define the
What is FSC for this section? What values can be used? FSC values

C, N and L should be defined in Table 73            Define C, N and L in Table 73

Where was Data Rate Field (DRF) defined?            Please define DRF or reference section where DRF was defined

                                           Please clarify or PHY HDR structure for DRP mode and for RI mode
When is RI used? How is PHY HDR modified when RI is used thedoes it remain the same?

"garbage bits" is a terrible term                   Please replace "garbage bits" with something better, like "RI bits"

                                             Please specify how How "garbage bits" are used in T_offset
Figure 147, how many "garbage bits" proceed SFD code T_offset1? manymany before T_offset2? ... How many before T_offse

                                               Please clarify
Need more detail in last sentence. How does a device know that an SFD/RI is being used or an SFD/DRF is being used. Once

                                               Please clarify
Which SFD sequence is used for the pilots? Is the SFD/DRF or SFD/RI? Does it include "garbage bits"

Bit pattern 111 is missing from Table 75          Define bit pattern 111 as Reserved
                                                  Please clarify
What if bit pattern 011 is selected but the payload is less than 128 bytes, do you still insert the pilot pattern?
Typo: fBW                                           Replace "fBW" with "f_BW"

What is the value of f_BW?                          Clarify that f_BW = 8 MHz

                                                    Please replace this TG6. The correct figure can which should have a value of
Figure 149 is incorrect. This is not from the text that was adopted byfigure with the correct figure, be found in document 15-10-2

                                                Update text and found
Text should be updated to match the correct figure, which can befigure in document 15-10-201-02, where the limits should be

                                              Current mask
Where is the TX mask for a center frequency f_c = 27 MHz only works for f_c = 16 MHz and not f_c = 27 MHz. Please upda

                                               or equal to a maximum, not -12 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -12 dBm"

                                               or equal to a maximum, not -39 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -39 dBm"

                                                Please state all clock frequencies that can be used with this chapter
Is the clock frequency 64 MHz for this chapter? Or is it some other number?

                                                 Please means or update numbers refer to and how they should be
Table 77 is confusing. I don't understand what the table clarify andwhat thetable with additional text to improve clarity used in de

                                                  Editor please pick either octet or byte and stick with it throughout document
In some places octets are used, in other places bytes are used
                                                   not just less than
PER is usually specified as less than or equal to,Replace "lessthan 1%" by "less than equal to 1%"
                                                  Update sensitivity = -11 dB with correct numbers. Proponents should bring a lin
Table 79 - sensitivity numbers are way too low, they imply an SNR numbers for the modulation scheme, which does not include

typo                                              Change curren to current
Table 10 is repeated as a Table 13 on page 54 Reference to Table 10
There are two Table 13, page 48 and page 54 Reference to Table 13 either page 48 or page 54
Countries name and regions                        It should not be limited to a few Countries.
                                                  I am not sure,
Electrostatic field can not be used for wireless communication which term HBC group is planning to use. They called as a Elec
HBC power spectrum unit                           dBm instead of dBr
Figure 149                                        dBm/MHz instead of dBr/Mhz
Table 76                                          dBm and dBm/MHz instead of dBr and dBr/Mhz
                                                  Add definition of the Beacon Shifting Ssequence NOT the n- th beacon perio
*n* seems not being defined in table 4.( I presume "n" is phaseof *n* in this table 4
                                                  delete "B+EAP1 Length" and and have been already removed from "Connect
"B+EAP1 Length" and "EAP2 Length" seems redundant as they are in beacon"EAP2 Length" fields from "Multinode Connectio

Wrong Tiltle                                        to replace " Command-Coexistence Response" with Coexistence Mode"
the exact value of "Status" field is not defined.   Define as follows; 0:accepted, 1:rejected

                                                     To replace " 1" bit for Piconet " fields
In Figure 35. Wrong number of field length for "piconet Priority" and "reservedpriority field with "2" bitsTo replace "5" bits for "r
                                                     Clarfiy the logical connection between line35-36 and line it be
Clarification is necessary: In line 35-36, it is prohibited for the sender to transmit another PPDU.When will37-39allowed ? On th

                                             Possible Specification Changeclausse 7.6.2, page posts hub may employ imp
clausse 7.6.2, page 84 : A hub may employ improvised polling and posting access to send polls or 84 : A at previously announ

Not relevant anymore                                to delete the phrase: or MSDU……till the end of the phrase
typo                                                replace "it's" by "its"
                                                    Specify regional
Regional applicability of each frequency band shall be specified. applicability here or in annex.
                                                    Specify be value of roll-off factor.
Roll-off factor of the square root raised cosine filter shall the specified.
                                                     in the preceding text, and is
Operating frequency bands are already specifiedDelete the whole subclause unnecessary to be specified here.
Acronym SHR is not well defined.                    Is it Synchronization Header (SHR)? Please put it in the Acronyms section.
                                                     is stated in Sec 10.18. This
The statement on CCA looks different from whatPlease make clear on CCA. sentence says CCA provided by PHY, but Sec 10.
"high QoS mode" is not defined.                     Please define what the "high QoS mode" means.
                                                    Please consider to use operate instead of transmit.
"transmit" is too narrow in meaning in the sentence "A compliant UWB device shall transmit in at least one of the specified band
                                                    FEC should be also employed as mandatory for beacon transmission.
Why should FEC be optional during association (beacon transmission)? Beacon should be robust and well protected using FEC
                                                    Please also include packet detection, timing synchronization, and carrier freque
The preamble part of SHR are intended more than just coarse timing.
                                              Please reframe or remove the sentence
The sentence, "The sync-words are placed in the data stream through equal intervals, i.e., each frame." is not clear.
                                              Refer to
Scrambler section could be aligned to narrowband PHY the latest scrambler section in the narrowband PHY.
                                              Please look correct.
Terminology "shortened BCH(31,19) encoder" does not use "BCH (31,19) encoder" and add a comment like "BCH (31, 19) cod
Incorrect reference "table 50"                "table 50" --> "table 53" ?
No detail is specified on SFD.                Please specify the SFD signal structure and also check if it is aligned to Figure

                                               Please insert a section that defines the applicable operating frequency bands.
A section on operating frequency bands is missing.

A section on channel numbering is missing.         Please insert a section that defines the channel numbers and center frequenci

                                               Please insert a section that defines the PHY layer timing.
A section on PHY layer timing is missing (pSIFS, pMIFS, EDTime, CCATime, Channel Switch Time, etc.)

                                             Please define RX-to-TX, TX-to-RX turnaround times.
RX-to-TX, TX-to-RX turnaround times are missing.

                                                Please add a section on transmitter constellation error or EVM.
Transmitter constellation error or EVM are missing.

Adjacent channel power ratio is missing            Please add a section on adjacent channel power ratio.

Adjacent channel rejection is missing              Please define adjacent channel rejection

                                               Please add sections on receiver receiver clear channel assessment measurem
Sections on receiver energy detection, ED threshold, ED measurement time and energy detection, ED threshold, ED are missin

Change bandwidth is 8 MHz, not 4 MHz         Replace "with the bandwidth of 4MHz" by "with the bandwidth of 8MHz".
                                             Replace "Header" with "PLCP Header"
The header should be referred to as a PLCP Header

Figure 142, what is f_ck?                          Please define the values for f_ck

                                             Please clarify.
How are the various preambles selected? How to choose which Gold Code polynomial? Who does selection- Is the PHY based

Figure 144, what is f_ck?                          Please define f_ck.

Is spreading factor 64 for this section? Why?      Please clarify.

                                                 Bits should be mapped
How are bits in table mapped to the fields? Is LSB first? Or MSB first? LSB first.

CRC8 is undefined                                  Please specify the CRC8 polynomial and how it is implemented.

"garbage bits" is a terrible term!                 Please replace "garbage bits" with something better.

                                               Please clarify.
Which SFD sequence is used for the pilots? Is the SFD/DRF or SFD/RI? Does it include "garbage bits"
Bit pattern 111 is missing from Table 75       Please define bit pattern 111 as Reserved

                                                  Please clarify.
What if bit pattern 011 is selected but the payload is less than 128 bytes, do you still insert the pilot pattern?

Typo: fBW                                          Replace "fBW" with "f_BW"

What is the value of f_BW?                         Clarify that f_BW = 8 MHz

                                                    Please replace this TG6. The correct figure can which should have a value of
Figure 149 is incorrect. This is not from the text that was adopted byfigure with the correct figure, be found in document 15-10-2

                                                Please update text and in document 15-10-201-02, where the limits should be
Text should be updated to match the correct figure, which can be found figure.
                                                Please be consistent with either octet or byte.
In some places octets are used, in other places bytes are used
                                                   not just less than
PER is usually specified as less than or equal to,Please replace "less than 1%" by "less than equal to 1%"

                                               Please update sensitivity numbers with of -11 dB for the modulation scheme, w
The sensitivity numbers in Table 79 seem to be unreasnably low as they imply an SNR correct parameters and consider the ap
                                               A 802.15.6 compliant
a device can have more than one PHY. Especially in coordinator case device with narrow band PHY shall be able to support tra

                                             We can make D8PSK we rates also as mandatory, given that extra, it could
making D8PSK optional will only make a overhead of negotiation.Sincedataonly need to implement demodulator complexity incrb

                                              don‘t that good cross correlation having the sequences, we can improve this
Two preamble sequences specified in the tablesGiven havewe have lot of choice in properties. The cross correlation goes as big

                                                repetition code
The operation shown in section 9.4.4 is same aschange the spreader block name to repetition code generator


                                                Either scrambler seed bit can be removed from require the purpose seed c
On one hand, it is said that scrambler seed depends on even number of channels. Then, why dohaeder or itsscramblercan bebit
Shortened bits are removed prior to transmissionThe process of how to shorten the bits can be explained clearly(though there a
Pad bits should be appended after BCH encoderThe nature of pad bits can be expressed as random, sequence of altenating ze

frequency deviation is mapped into deltaF    GMSK will support the linear frequency drift and the way the frequency variatio
S90) = exp(j*pi/M)                           This definition is not in sync with the lines 5,6,7 where the encoding during tran
Table 50                                     Table 48
High QOS mode                                Kindly define High QOS mode
                                             Need to provide the process of aligning with BCH information bits length length
Alignement to the codeword length of BCH codes is missing
Table 52                                     Need to have more reserved bits for header as it may not be efficient to transm
scrambler word                               This bit is not required and can be replaced with extra bits for length to maintia
The Synchronization Header is formed         The Synchronization Header shall be formed
Exact definition of SFD is not clear.         Need to identify and place the appropriate sequence with modulations specifie
Reference to Table 63                        This table is non-existent in UWB framework and must be typo. This can be de
Detection is not in scope of specificstion   It can be moved to appendix as recommendation
sm shall be set to zero for Ncb=1            What if it is not equal to 1. Lot of unpredcitability. Need to close all options for c

constellation phase                                Can we change the constellation to pi/2 DBPSK and pi/4 DQPSK
seq(k-1) = 1, for all 1                            altenating sequence of 1's and 0's are better

Can the long pulse support 4 nsec pulse width? can chirp of 4 nsec width support this PSD ?

                                                   filled 134 should be updated. New figure about fitting spectrum mask for ban
Spectra of chatic waves in figure 134 are looselyFigureto spectrum mask limits. It may cause the spectral inefficiency. Please re
Duty cycling for UWB                              Mention UWB PHY supports duty cycling in its modulation and does not have a
                                                  alternative band
Operating at 16MHz and 27MHz with 4MHz bandwidth seems to violate FCC Part 15.205.
                                                  EFC(HBC) related description is required.
There is only description based on the antenna, but electrode.
                                                  In an optional manner, be rates of above 1.5 Mbps
For varios applications such as endoscope capsule, high data rates candatasupported in standard. are supported in narrow b
                                                  Standard must provide experimental results under in-body channel condition.
GFSK and GMSK modulation scheme are very well proved solution for in-body applications at MICS band such as pacemakerI
Understanding of the scheme not clear             Can be breifed with diagram
Link to PSDU timing parameters is not clear       Give a writeup in PSDU timing parameters saying that 6,7 (R0,R1, R2) data ra
                                                  Consolidate tpye-I and polled allocation.
The function of type-II plooed allocation can be achieved by using type-Itype-II polled allocation. If not, justify the need for type-I
"exclusieve" should be "exclusive"                See comment.
"curren" should be "current"                      See comment.
                                                  Change "...when the hub is to send a post to
                                                  the node is indicated in…" to "...when the hub
                                                  is to send a post to the node it is indicated
missing "it"                                      in…"
There is not much difference between Poll
frame defined in clause 6.4.5 and Wakeup
frame defined in clause 6.4.7.                    Consolidate these two frames.
"high QoS mode" is mentioned but not defined. Define what is "High QoS mode".

In subclause 1.2, sentence reads: "This
standard considers effects on portable
antennas due to the presence of a person
(varying with male, female, skinny, heavy, etc.),
radiation pattern shaping to minimize specific
absorption rate (SAR)1 1 into the body, and
changes in characteristics as a result of the
user motions." However, there is no
mentioning of SAR at all in each of PHY
specification parts. It is unclear how this       Some informative text on SAR reduction
standard considers the SAR minimization.          should be present in annex or somewhere.

                                               Service primitives or MIBs are useful interfaces
                                               to manage other entites. Probably BAN
                                               specification can leverage these interfaces as
There is no service primitives or management well. Define such interfaces to make clear what
information base defined at all. Hence, NME or kind of parameters can be manageable from
HME can not control other entities.            external entities.

Most important requirements for BAN are low-
cost and low-power/energy, so efficient
cryptographic algorithms in terms of these
criteria should be considered. In ISO/IEC JTC
1/SC27, ISO/IEC 29192 (lightweight
cryptography) is developed, and it is suitable in
particular for constrained environments (i.e.
low cost, low energy consumption). The scope
of ISO/IEC 29192 includes health-care
systems (e.g. Body Area Networks) and sensor
networks. ISO/IEC 29192 should be
considered in IEEE802.15.6.                       As in comment
I could not find out how the two-hop star         Describe how the security services work in two-
topology links can be secured.                    hop start topology scenario.
                                                  As are many duplicated more detailed description on hybrid ARQ. Also, timer b
The description on hybri ARQ is still unclear. There in comment. Provide descriptions, but the subclause does not contain the ra
                                                    for UWB PHY.
Thre is no energy detection threshold mentionedSpecify the threshold or remove the sentence stating the energy detection.
                                                  Specify the missing specification for receivers.
Many of the specification for receiver are missing. i.e., adjacent channel reduction, energy detection threshold, etc.
pCSMASlotLength=pCCATime+20 us must be doble checked by CSEM
                                                  Symbol mapper of 4 bits it information to 8 bits symbol requires a search reco
Symbol mapper 6 information bits to 12 bits symbol must be simplified as of requires a search of 64 different codewords to of 16
                                                  Last inequality changes to 0.8/Tp<|f-fc|<=1/Tp and adding -20dBr for |f-fc|>1/T
The transmit spectrum mask must have a floor limit rather thangoing to minus infinity
                                                  Clarify.
When it says "There is a hub in a BAN" it is not clear if this is intended to mean there is exactly one hub in a BAN. From contex
                                                  Change to 0, 1, are numbered 0, 1, … s. The text could say 0, 1, … s also to b
The allocation slots are numbered 0, 1, …. In Figure 3 the slots … s.
                                                  Change to [0, 2^128). Same on interval.
Would the interval be more precisely stated as [0, 2^128). That is, a semi closedpage 37 line 29.
                                                  Define and once for consistency.
I see the ceiling function defined twice (page 50 line 23 bothpage 78 line 32) but I do not see the floor function defined anywher

                                              Replace It has very similar bit-rates to 802.15.4a with statement saying somet
The IR-UWB PHY defined in this section is unnecessary. the IR-UWB PHY section (section 10), with a similar complexity, but it

                                             Replace with "At least one mandatory channel in the low band or channel in th
This subclause says the the UWB PHY shall support "One mandatory channel in the low band and one mandatoryone mandato

There should be at least one mandatory pulse shape to ensure interworking.
                                                  Self contradictory, either remove the "different modulation scheme (while main
The draft says: "Different data rates are obtained by changing pulse waveform duration 10 and data rates" or remove "while ma

                                              replace "as" can cause confusion.
Using the word "as" to mean "because" should be avoided. It by "because"

                                                 Say how the of Tc = of the corresponding to
The draft says: "Tw = 8 ns. The chip time shall have duration polarity 128 nspulses is decided. L= 16 for zero-padding. Notice T

                                             Replace 0.5Mbps Tables 54 and the
References to 0.5Mbps up to 10Mbps do not coincide with rates in and 10Mbps by55. user data rates of 0.3954Mbps to 12.656

                                                Replace "0.4882 Mbps" with "0.3954 Mbps". Replace "uncoded" with after cod
This says that the mandatory uncoded rate is 0.4882 Mbps, but this is actually the rate after adding the parity bits, i.e. "before c

P.PRF is not defined                              Replace with Peak PRF or define it.

                                             replace "hoping" by "hopping"
Time hoping sequence should be time hopping sequence

                                              Don't let the implementer choose truncation or at least a size minumum beyon
The implementer should not be allowed to truncate the reference pulse to any size. What if he chooses have a <2ns?

                                                Replace with Table 61.
Neither of these plots correspond to actual channels shown inactual legal 15.6 channels.

                                                   etc.
"go to 1" and "go to 2" should say "go to state 1" Replace "1" and "2" with "state 1" and "state 2"

                                               Fix 61, but Table 64
Line 10 on page 191 says the band plan is as Table the contradiction says that only channel 7 is used. Which is correct?

                                             only centre frequency?
Why does the diagram show 7.9GHz? Is this theRemove "7.9GHz" from Figure 136

                                                Replace 7.5GHz with 7.98GHz
The title for Figure 137 says 7.5GHz center Frequency, but the figure shows a spectrum with a 7.98GHz centre frequency.

                                                     only centre frequency?
Why does the diagram show 7.5GHz? Is this theRemove "7.5GHz" from Figure 138
                                                    Discard the 12, implying that may consider extending the dimension of better
The (63,51) BCH code has a generator polynomial of degreeCRC-4 HCS. You the error detection capabilities are alreadythe BC
                                                    EFC(HBC) related description is required.
There is only description based on the antenna, but electrode.
                                                     filled 134 should be updated. New figure about fitting spectrum mask for ban
Spectra of chatic waves in figure 134 are looselyFigureto spectrum mask limits. It may cause the spectral inefficiency. Please re
figure caption should be plural                     change diagram to diagrams
                                                    this field should whether a indicate the next is active or not. For example and
The current specification of this field can create ambiguity about be used tofuture superframeguaranteed active superframea lo
                                                     That the node is an to use the problem, then indicated in
don‘t we need to say something about this field? If we agree thisneedsapplication cipher functionthat is fine. this field in the fram
                                                    The more than should be this should be >= minCAP
The current wording states that "CAP length is set to CAP lengthminCAP..." set to a value no less than minCAP.
                                                    I suggest changing "Life critical medical" to "High priority medical"
Table 4 gives application specific priorities. Not sure how these classifications are used? Also am a bit wary of the use of "Life c
                                                    change field to support, since this now imcludes battery level indication as wel
the final field in figure 36 - shouldn't it read Command Message command message support
directly related to previous comment 7              this section should be remaned to Command message support and the text mo
how is this field used by the MAC or is it just informational?
                                                      it HID
this paragraph isnt very clear. Can a hub changeclarify after nodes connect to it? If not what does reselect mean?
                                                    should be changed to include of the relay - for
what happens for relay communications? The Senser ID would be the Node IDrelay supportnode.example "The Sender ID field
                                                    delete "Not editing…
delate the last sentence which was probably inserted during acknowledged??"
                                                    change the should to in the last would make it easy is implementers of B-Ack
the sentence "These frames should not be longer than the frame sent shall. This block transmission" forredundant, because a d
                                                    we can know the last fragment has been 1st frame
there is still the outstanding issue of how a recipient could either use a countdown with the received? bit in the MAC header indic
                                                     must be specified. Otherwise, the implied is allowed to transmit 10 frames for
are these frames of fixed length? If they are, thisthis needs to be much clearer. A node that medium access allocation is ambigu
delete "(beacon period)"                            this is non-beacon mode and superframe should be used instead of beacon pe
                                                     table 24) is not long 24; pMICSUnconnectedPollRxTime = pMICSUnconnecte
 pMICSUnconnectedPollRxTime (as sepcified inchange entry in tableenough for a node to receive one of 2 adjacent T-Poll fram
                                                    I don‘t see any functional advantage for having a separate wakeup frame, espe
the poll and wakeup frames appear to have the same functionality (see figures 73 & 75 and 76 & 77). Why do we need both of
                                                    we can use the relay
how does a sensor node know that an ACK is from a relaying node? field in the MAC header to indicate this in ACK frames fro
                                                    change 7.2.4 to add optional reception of ACK frame with RN to 7.2.4 because
For a sensor node to overhear an ACK from an RN, it needs to be able to receive this message, but accordingSender address
                                                       would this taken at the end
pChannelSwitchTime is 100 us (table 44). Whereneeds to betime come from? of the superframe for channel change. We might
                                                    I am not
This entire section is dislocated from the rest of the text. sure it is needed. So it should be taken out or completely rewritten to r
what is a BAN enquiry frame? I don‘t see it defined anywhere. should be changed to "Coexistence request"
                                                     "BAN enquiry"
what is a BAN enquiry response frame? I don‘t see it defined anywhere. should be changed to "Coexistence response"
                                                     "BAN enquiry response"
                                                     make ED mandatory for before transmitting the BAN enquiry frame? Wouldn‘t
in the "active scan based" method, It appears the hub doesn't do any ED time sharing/load reduction enabled hubs. This should
                                                     I of not sure this clause definition of severe for information. So I suggest that
This entire section is also dislocated from the restam the text. What is the is useful other than interference? How would load con
                                                     change "a SCRAMBLER SEED" to the word field
SCRAMBLER SEED is the only part of the comma separated list that does not have"a SCRAMBLER SEED field"
                                                       to be removed
original editor's comment still in place and needsremove the text "spell out what acronym means first time in document"
                                                     add rate between "any" and "of" in this line
slight ambiguity of meaning on whether a single data"one"is used during PSDU transmission
                                                     reformat diagram text lines in split words
Formatting of text within boxes leads to single words being split acrossto avoid figure 105
"modulatons" should be singular                      change "modulations" to "modulation"
As comment above                                     As comment above
As comment above                                     As comment above
As comment above                                     As comment above
As comment above                                     As comment above
As comment above                                     As comment above
As comment above                                     As comment above
missing "which" in this sentence                     add ", which" between "code" and "is"
"codeword" should be plural                          change "codeword" to "codewords"
                                                     Specify period of the transmission. Is a time t=0 from is the time at which th
It is not entirely clear what is on air during the 1st symbolthe IQ constellation point valueit@ transitionwhich S(0) to the 1st conste
full stop is in incorrect position                   change "in. Table 43" to "in Table 43."
                                                     change column 2 heading order is odd
Heading of rightmost column in table 43 is not very descriptive, and columnto "Condition"; and swap columns so that "Preamble
text should read "whichever is lower"                change "which" to "whichever"
text should read "..when measured for.."             change "measure" to "measured"
Table reference is incorrect                         "Table 50" should be changed to "Table 48"
Table reference is incorrect                         Not sure which table should be referred to instead of table 10..
                                                     I assume the final part in brackets should be removed? If modulation scheme
Sentence is contradictory: "Different data rates are obtained by changing pulse waveform duration 10 and not, please clarify me
                                                     Refer PHY section, apart scrambler
The whole of 10.5.2 seems identical to 9.4.5 in the NB to single section on from some different terminology. Is this repetition ne
                                                     Refer to single
Same comment as above but on the BCH encoder description section on BCH (51, 63) encoder?
Table reference is incorrect                         "table 50" should be changed to "Table 53"
                                                     Add than line to is still defined as range of according to gradient mask to -20d
Spectral mask at offsets from channel centre greater extra 0.8/Tp M(f) definition for reducing (f-fc) > 0.8/Tp, setting defined by 3r
                                                     Add explicitely clear and would benefit other sections
Section describing the chaotic pulse waveform is not equations for the waveforms as in from equations specifying the waveform
                                                     the system such that a transmitter / receiver could be order
HBC section is insufficiently complete to specify Section requires significant expansion and rewriting inbuilt. to be included in s
                                                       region / re-range is <10%, rather than range up to 90%. or remove as only o
Figure 5, if included at all, should show details ofRescalewhere PMDfigure, or remove. Rename curve label, Curve labelling is no
                                                      68 implies 2 possible codes..
Table 69 shows one 128 bit code, whereas tableClarify the number of codes. If 2 are possible, tabulate 2nd code also.
                                                     specify mask for 27MHz or same for
Tx mask is only given for fc=16MHz, not fc=27MHz. Is the mask different case as well 27MHz case?
                                                     Clarify the bandwidth of the signal.
Tx mask plot uses fBW which is defined in text above as "channel bandwidth". In sec 11, page 195, line 12, the bandwidth is st
                                                     Clarify the of -23dB given 10dB NF & How is rx noise computed?
Rx sensitivity levels look very low. -112dBm implies a SNR assumptions for sensitivty. 6dB implementation, assuming matched
Table caption typo                                   rage => rate
                                                      reserved bits. or explain 9.1 which there for the NB reserved not
the use of this table is very unclear with all theseFill in the table It refers to better whyis onlyis so much PHY and bits the others.
limited differences between NB and UWB               table 24 & 25 should be merged
                                                     Add useful as well
An alternate channel rejection specification would be an "alternate channel rejection" specification
Wording of the paragraph to improve for clarity The ultra wideband (UWB) PHY specification is designed to provide a large pa
Unclear paragraph and inappropriate use of           The UWB PHY provides four core
the term "PLCP" which is not a sub-layer             functionalities:
                                                     1) The UWB PHY provides a Data interface to
                                                     the MAC layer under the name of the PD-SAP.
                                                     It handles the frame exchange between the
Wording of the paragraph to improve for clarity MAC and PHY.
                                                2) The UWB PHY constructs the PHY layer
                                                protocol data unit (PPDU) by concatenating the
                                                Synchronization HeadeR (SHR), the Physical
                                                layer HeadeR (PHR) and the Physical Layer
                                                Service data Unit (PSDU), respectively. It
                                                converts the PPDU into an RF signal to be
Wording of the paragraph to improve for clarity transmitted over the wireless medium.
                                                4) The UWB PHY provides a Management
                                                interface to the MAC layer under the name of
                                                the PLME-SAP. This interface is used to
                                                configure the parameters of the PHY, and in
                                                particular to set and get values of the PHY
Wording of the paragraph to improve for clarity Information base (PIB).
                                                3) The UWB PHY optionally provides clear
                                                channel assessment (CCA) indication to the
                                                MAC in order to verify activity on the wireless
Wording of the paragraph to improve for clarity medium.
                                                One mandatory synchronization header (see
SHR=synchronisation header                      7).
                                                One mandatory Forward Error Correction
FEC acronym                                     mechanism (FEC)
                                                this is undefined. Probably the whole sentence
beacon preambles                                is useless

                                                A combination of on-off keying (OOK) with 64-
                                                ary coding and differential phase shift keying
                                                (DPSK) modulation schemes is used to be
                                                able to comply with a large set of receiver
                                                architectures like non-coherent and differently
                                                coherent receivers. Variable data rates is
                                                obtained by changing the pulse waveform
                                                duration, the symbol duration and the
                                                modulation scheme while keeping the
                                                waveform duty cycle constant. On-off keying is
                                                the mandatory modulation format to support
                                                and DPSK is optional for the default mode
                                                Conversely, DPSK is mandatory in the high
Wording of the paragraph to improve for clarity QoS mode, and on-off keying is optional.
                                                The Forward Error Correction (FEC) scheme is
                                                mandatory for the transmission of PHR and
                                                PSDU.It is noted that the use of a systematic
                                                code makes decoding optional at the receiver
Wording of the paragraph to improve for clarity for the PSDU

                                                Full function devices (FFDs) shall implement
                                                the IR-UWB based modulations, so namely the
                                                OOK or DPSK modulation schemes depending
                                                on the mode of operation. They can optionally
                                                implement the FM-UWB mode described in
Wording of the paragraph to improve for clarity section XXX.
                                                Reduced function devices (RFDs) shall either
                                                implement one of the IR-UWB bases
Wording of the paragraph to improve for clarity modulations or the FM-UWB mode.

                                                Only FFDs are allowed to send beacon frame
Wording of the paragraph to improve for clarity and to coordinate beacon-enabled networks.
                                                Only FFDs are allowed to form non-beacon
Wording of the paragraph to improve for clarity enabled networks.
                                                In any case, it is not allowed to form a network
Wording of the paragraph to improve for clarity made of RFDs only
                                                RFD and FFD concepts are meaningless in the
                                                UWB PHY section if not defined at the
                                                beginning of the standard, and in the MAC
RFD and FFD not introduced in the MAC           section. Clarify.
                                                Priority of access to resources is given based
                                                on the fact that the running application is
Wording of the paragraph to improve for clarity medical or non-medical.

                                                 Medical applications are given a higher priority
continuation of previous comment                 than non-medical applications by two means:

                                                 1) If resources in the BAN are becoming
                                                 scarce, frames from the medical applications
                                                 shall be given a higher priority than frames
continuation of previous comment                 from the non-medical applications.
                                                 2) If a medical device receiver suffers a
                                                 degradation of its sensitivity above 1 dB, the
                                                 coordinator shall enforce non-medical devices
continuation of previous comment                 to reduce their EIRP.

                                                The PSDU contains the payload received from
                                                the MAC via the PD-SAP which is formatted for
Wording of the paragraph to improve for clarity further transmission over the wireless medium
                                                The SHR is divided into two parts. The first
                                                part, the preamble is intended for coarse timing
                                                synchronization while the second part is the
                                                start frame delimiter (SFD) for frame
                                                synchronization. The preamble is formed of
Wording of the paragraph to improve for clarity repetitions of Kasami sequences.
Figure 117, replace SAP by PHY-SAP              Figure 117, replace SAP by PHY-SAP

The MPDU internal structure is out of scope of
the PHY specification. Moreover the maximum      Limit th description to role and size of the
length is 255 bytes, and not 256 bytes           MPDU and give a link to the MAC specification
Figure 199 caption                               "the" side-stream scrambler
In the case of un-coded transmission, CW N is    FEC being mandatory, there is NO uncoded
set to zero.                                     transmission case. Remove
                                                 If the encoding process for the BCH is identical
                                                 to the one of the NB PHY, just give a reference
BCH encoding                                     to section 9.4.1.
                                                If the encoding process for the BCH is identical
                                                to the one of the NB PHY, just give a reference
Pad bits                                        to section 9.4.2
SHR Preamble                                    Synchronization Header (SHR)
                                                The SHR is composed of the preamble and the
                                                start-of-frame-delimiter (SFD). The preamble is
                                                commonly used to detect the frame and
                                                perform symbol and carrier timing acquisition,
                                                whereas the SFD is used to indicate the
Wording of the first paragraph to improve for   beginning of the actual useful fields of the
clarity                                         trame.
Separation of preamble and SFD to appear in     Add a subtitle "Preamble" as 10.7.1 after the
titles                                          first paragraph proposed above
                                                In order to perform symbol and carrier level
                                                timing acquisition , a preamble consisting of
                                                known data is transmitted at the beginning of
                                                any frame. Such a preamble aims at being
                                                detectable by a plurality of receivers, including
Wording of the paragraphs to improve for        non-coherent or differentially coherent
clarity                                         receivers.
                                                Kasami sequences of length 63 shall be used
Wording of the paragraphs to improve for        to build the preamble for both the non-coherent
clarity                                         and differentially coherent PHYs.
                                                There are eight possible Kasami sequences
                                                defined in table 3. They shall be used
                                                according to the physical channel in use and
                                                are selected through the PLME-SAP (through
Wording of the paragraphs to improve for        the MLME.SET primitive) to improve co-
clarity                                         existence.

                                                The set of sequences shall be divided into two
                                                pools. Each pool has a set of 4 sequences.
                                                The first pool C1 to C4 shall be used for odd
                                                physical channels. The second pool C5 to C8
                                                shall be used for even physical channels.
                                                Therefore, four logical channels are available
Wording of the paragraphs to improve for        per physical channel by virtue of the sequence
clarity                                         selection in the pool.
                                                The coordinator may scan all the logical
                                                channels and use the preamble with minimum
                                                received power level. Coexistence of BANs
                                                and interference mitigation can be achieved by
                                                virtue of the inherent duty cycling in the
Wording of the paragraphs to improve for        modulation and the preamble sequences with
clarity                                         good correlation properties.
How is selected the Kasami sequence in a pool Introduce a PMLE-SAP and SET primitve to configure such a parameter, plus
Sequence length of 63                           Shorter sequences (eg 31) would simplify the receiver implementation, especia
Number of sequences Ns = 4                      More sequences of smaller length would benefit the performance and the rece
8 sequences in the proposed Kasami set          A larger set (eg Gold codes, which has nearly as excellent crosscorrelation pro
                                                 modulation and 16 for the for the DPSK (differentially coherent) modulation D
The value of L is 16 for the OOK (non coherent) The value of L isis not valid OOK (non coherent) modulation and is 32 for the be
sequence of table 50                            table 53
                                                Define S0, but consistently with not reported
In figure 116, the SFD is defined as being 2 sequences the SFDsuch a definition isthe preamble here, and S0 is never defined (
                                                     OK)
The equations should be provided (links are not Update links to equations or add equations. The case of DPSK, for which the m
Figure 123 caption is not explicit enough            Construction of PREAMBLE symbols from A Kasami sequence IN THE NON C
repetions                                            repetitions
duty cycling factor                                  Add "It is kept constant to 3% whatever the modulation format and the data rat
                                                     Add "In be following, better sake of simplicity when "pulse no ambiguity, the
10.10.1 PRF parameter. The definition which follow will theclearer if afor the teminology is used than there iswaveform".
                                                     Replace bacause "coherence"
"non coherent modulation" is not a very adequate namingby "OOK modulation" is more a matter of reception
                                                     Replace naming bacause "coherence" is more a matter of reception
"differentially coherent modulation" is not a very adequateby "DPSK modulation"
DC bias                                              Remove, this is not the issue
Time hopping                                         It shall not be applied for the differential coherent PHY
                                                     Move is not normative
Detection: the text proposed refres to the receiver and the complete section in annex (informative text)
PPDU                                                 replace by "PSDU" (the preamble has no information bits)
DBSK                                                 DPBSK
Tp is the duration of the pulse shape p(t)           Tp is the parameter of the pulse shape p(t) (as in 15.4h: Tp is defined as the in
"bandwidth" is not precise enough                    In the table "bandwidth" should be replaced by "maximum 3dB Bandwidth"
                                                     Remove, this is too stringent
the central frequencies of the band plan shall have an accuracy of 20 ppm.
                                                     Keep beyond
Figure 128 does not fit the equation (93) for the valuesthe figure and update equation (93) accordingly (last part of the equation
Tp=2ns                                               Tp=1/499.2MHz ~ 2ns
                                                     For the sake of readibility chip duration rounded values exactly 2ns with a fo
Tables 54 and 55: values which are given in ns are integer multiples of thewe can let the "Tp" which is notin the tables, (but 1/49
Tp=2ns                                               Tp=1/499.2MHz ~ 2ns
                                                       truncated to 20Tp satisfying ...
Figure 129 — PSD centered at 4492.8 MHz and 20Tp truncation example is too much ! Propose a tighter truncation fulfilling the
                                                     Remove to section
10.15.3 Chaotic pulse waveform. There are no equations thegenerate the waveforms, thus this text cannot be normative
"Preamble SHR"                                       "Preamble"
2nd Kasami sequence                                  The FM-UWB shall not be restricted to a single Kasami sequence if it suppose
                                                        shall turnaround time
table 64. Several parameters are out of scope orTx-Rx not appear here is already defined in the MAC section and hsall be remo
                                                     Change center frequency 7.9 GHz
Figure 136 — FM-UWB transmitter block diagram. Center frequency is notto "Fc"
                                                     Change the text to a more normative text (remove "VCO" or say it is for signal
This subcarrier signal m(t) modulates the RF VCO (wideband frequency modulator), yielding a constant-envelope UWB examp
This paragraph is redundant                          remove
                                                     Non normative => straightforward to generate using either analog or digital cir
From an implementation point of view the triangular 15 waveform isremove
                                                     Update 7.5 GHz center frequency
Figure 137 — Frequency spectrum of FM-UWB signal atwith a high quality figure, with the right caption for the center frequency
10.17.5 Receiver architecture                        Though given as an example, this section is non normative and can be remove
                                                     If slotted aloha SHALL be employed, then the CCA is preamble detection. cla
The receiver may perform clear channel assessment (CCA) by using either the energy detection or 14 useless. Rephrase toHow
                                                     The complete behavior of the it receives I-ACK or "Pauses its all the channel
It is mentioned that emergency device shall try sending emergency signal untilldevice should be mentioned after transmission".
                                                      like first the medical event report sent without payload.
From the medical event report section, it seems Change emergency data frame issection accordingly Why cannot first emerg
                                                     It should be changed to, "when the channel selected" can be improved further
The statement "when not transmitting, the hub should stay on receiving mode innot transmitting, the hub should stay on receivi
                                                     Change the figure
The figure 78 does not reflect that multiple emergency frames can be transmitted on the same channel before moving to the ne
                                                     Change the
In the figure 78, change the "frame" to "emergency frame" figure
                                                     Rewrite not fit in the
Ambiguity on line 5 and 6. Line 5 and 6 are not well doesline 5 and 6 flow of Medical event report section and not well connecte
                                                     Suggest a not be called emergency frame. Because, emergency frame is trans
If at all, first frame is transmitted with out payload, it should different name to first frame.
The reference to FCC regulation for MICS band Clarifyis missing
The introduction to MICS regulation in MICS section is missing
                                                     Clarify
                                                     Clarify
Mutual discovery: does implant node aslo discover the controller ?
                                                     Rewrite
The paragraph is very complicated. Hard to understand. the whole paragraph.
                                                     Separate the discovery operation to the channel channel access are
Is the T-Poll transmitted for discovery or for resource allocation? Why discovery mechanism and access operation. combined
                                                     Change it channel, when required by the 26 regulations, in the order indicated
The statement "The hub should subsequently select a newto "The hub should subsequently select a new channel for LBT, whe
                                                     Rewrite the pargraph.
"As illustrated in Figure 73, prior to more frame exchanges with a connected node, the hub shall transmit a 2 group of up to pM
                                                     Please mention conditions for further The condition for further change of chan
"The node should not further change the channel 10 unless recommended otherwise."change of channels
Multicast lockup aided discovery. The concept desciribed in the paragraph is not multiple node discovery. It is more like multiple
                                                     Remove the Multicast lockup aided mechanism. The
Multicast wakeup mechanism. This section clearly describes the multi-node wakeup discovery section.section naming is approp
                                                     Resource allocation and some sort of resource alloctaion under discovery. Wh
The source allocation for MICS devices are not clear. There seems to be discovery mechanism should be separated.
                                                     Add the mechanism.
How resource allocation happens in a network scenraio of one controller device and multiple implant device? Mechanism is mis
The channel access and wakeup are mixed.             The paarmeters used for wakeup such as PMICSUnconnectedPolls, PMICSUn
                                                     What if the duration between two samples of After dwelling collected is more th
"It should tune to the channel in which it last received a frame with a valid FCS from the hub". the data to be on the current chan
                                                    It should tune to the channel in which it hub". After dwelling on the current chan
"It should tune to the channel in which it last received a frame with a valid FCS from the last received a frame with a valid FCS f
                                                      in the
Figure : 73, Why device is trasmitting data frameClarify discovery process in reponse to the poll message. It should be 'Ack" fra
                                                    What is the use of order last provided by the hub.
It should switch to another channel, in accordance with the channel this channel ordering and on what basic it is selected. If the
What is the behaviour in case of only downlink traffic is present in a particular session




B2 naming may not be acceptable.                  Suggest a name for B2 message.




                                                    not be acceptable
Type-I and Type II polled allocation naming may Give a name to type I and type II polled allocation
Figure 14: RAP1 start should be under solid line
                                                   Include the text in the section 6.3.1
It is required to explicit mention that Beacon shifting sequence, channel hopping state and next channel hop fields are optional
                                                   Rework section 6.4.6
The functionality of T-Poll message and Poll message presented in the draft are same. The T-Poll should be merged with a Po
                                                   add a to mention the Superframe structure and introduction to channel access
Before describing the MAC frame format, it is required section before section 6
Why two RAPs? RAP 1 and RAP2 can be merged to one RAP
                                                   Suggestion: Provide an annex contention the objective and operation not clea
There are so many channel access proposed (poll access, improvised access, to describe access, TDMA access). It is of each
                                                   Inclusion of sleep bit in nodes message (by reusing
Type II access poll requires sleep bit in the poll message to explicitly tellthe Pollto go to sleep mode an existing bit)
delayed poll description is missing                The operation or protocol related to delayed poll should be added with more de
                                                   Describe the operation of poll to traffic type such as delayed different traffic t
Different structure such as variable Poll Period and fixed Poll Period accordingchannel access with respect to sensitive type ofan
                                                     RAP
Use the more widely used terminology CAP thanSuggesion
                                                   clarification
Beacon shfiting does not seem to improve the coexistence. Why it is required? It adds extra complexity into the system.
                                                   Suggestion: It seems improvised access not required for the BAN
what is the need of improvised access in the BAN MAC? It seems imporvised access improves bandwidth efficiency, but adds
Timed-Poll (T-Poll)                                Since the size of payload in T-poll is constant. The T-poll can be merged with t
                                                   The situation is currently being HID is a node while other device
The Hub shell not reselect the HID equal to a connectNID thatwhen reselecting aused forrequired connected with it are still con
                                                   What if two unconnected nodes select simultaneously? ……
An unconected node without an assigned connected_NID shall choose the unconnected_NID as its NIDClarification.
                                                   I-Ack frame can not contain recipient address field set
I-Ack frame or next (management frame with the frame payload containing aany payload. Clarification to its IEEE MAC addres
Priority mapping                                   The priority mapping is defined for Contention access but not defined in case o
Frame Reception                                    The rules for reception of a frame either by hub or node should be re-looked, s

Ack policy field setting                         Why Ack is required for Poll and T-poll?
Access classification and division               What is the benefit of inactive superframes and why this not not be achieved u
                                                 The RAP related info should be removed from CA frame, since we have addre
Type - I access phase                            Specify, what are the channel access mechanism appliable in this phase
Type - 2 access phase                            Specify, what are the channel access mechanism appliable in this phase
Scheduled access and its variants                Scheduled Access, schduled poll access and delayed poll access terms are us
pMICSWakeupSeparation                            This should be addedd to the table 24
pMICSWakeup                                      This should be addedd to the table 24
pMICSMcastWakeupSeparation                       This should be addedd to the table 24
                                                 The device can use time will hell implementer to utilize this concept better
Additional information how the device can get larger additional guardscaling up factor of Connetion request IE to get additional
                                                 Clarification
Channel hopping does not improve the coexistence performance, but adds extra complexity.
Interference mitigation mode needs clarificationsexplicitly mention that time sharing and offset piconet synchronization are non-
                                                 change the use can word from the use of relays as presented in in the entire
Use of relays for piconet co-existence. TG6 piconet co-existenceof thebenefit"hub" in the document to "co-ordinator" contribution
Termination messages for ending co-existence The explanation related to the co-existence modes is insufficient. The text nee
What is the definition of "current device"?      The explanation related to the time sharing co-existence modes is insufficient.
                                                 From reading the text,
Number of devices, RSSI, existing data rates is not in beacon or B2. it is not clear what does the word "offset synchronization
                                                 The explanation related to the interference mitigation co-existence modes is in
                                                 Add usage of
The way to avoid interference by time information is not clear. nodes as relays to gather information about adjacent piconets an
The meaning of "Minimum" is ambiguous.           It is not clear from the document how the co-existence modes gracefully (or oth
                                                 "current device" should be changed to "existing coordinator".
Current description for time sharing is assuming the case when new piconet starts. Is time sharing applicable for piconet encou
                                                 This one octet field would be set to the not be another piconet even if there wit
What is the exact definition of unoccupied channel? For example, there may be or may the length of reserved slots duration is n
                                                 Clarification
From the consistency with ED scan or Active scan, the sentence "In passive channel scan, coordinator shall try to locate beaco
                                                 coexistence request --> coexistence
"BAN descriptor field" is not used anywhere in the draft except coexistence section. response operation is for static case.Sem
                                                  constraint is implementation-specific.
‗maximum number of BAN descriptor field‘. This Title of 7.12.3 should be "Time sharing" removing "& load reduction"

What is the time unit of increasing slot in Table 22? And which condition triggers increasing slot action?
                                                   "In when inter-piconet message exchange is possible --> need more details.
"by tracking the overflow of total used capacity only passive channel scan, existing coordinator shall try"to locate beacon or B2 m
                                                   the definition of "BAN descriptor field" should be written in B2 or beacon sectio
                                                   change exchaning based constraint to the general time based constraint.
"It is locally broadcast by a hub... " --> B2 message is forthe number frame between other piconet coordinators. Local broadcas
"In B2 frames locally broadcast by a hub... " --> B2 message is for exchanging frame between other piconet coordinators. Loca
                                                   clarification
                                                   explicitly mention that time well in and offset
Co-existence mode terminology needs more clarification and is not defined sharingthe draft piconet synchronization are non-
use of the term "hub"                              change the use of the word "hub" in the document to "co-ordinator" in the entire
                                                   The explanation related to the co-existence modes is insufficient. The text nee
explanation of co-existence modes needs clarification
Time sharing mode needs clarification              The explanation related to the time sharing co-existence modes is insufficient.
                                                   From
Offset BAN synchronization mode needs clarification reading the text, it is not clear what does the word "offset synchronization
Interference mitigation mode needs clarificationsThe explanation related to the interference mitigation co-existence modes is in
                                                   Add usage of nodes benefit from the use of relays about adjacent contribution
Use of relays for piconet co-existence. TG6 piconet co-existence canas relays to gather informationas presented in piconets an
Termination messages for ending co-existence It is not clear from the document how the co-existence modes gracefully (or oth
                                                   Suggested remedy: much less efficient than binary curves, esp. in hardware-a
(TR) Clause 8.1, p. 119: For constrained platforms, prime curves arePick a corresponding binary curve instead, preferably from
                                                 Suggested remedy: reference list. Suggested remedy: cross-reference to
(E) Clause 8.1, p. 119, l. 19: FIPS Pub 186-2 is not mentioned in the cross-reference to FIPS Pub 186-3 instead.                  F
                                                  Suggested remedy: Pick curve with and is crypto strength, preferably from th
(TR) Clause 8.1, p. 119: The elliptic curve specified is the so-called P-192aNIST curve 128-bitalso used with Bluetooth. These c
(E) Clause 8.1, p. 119, l. 21: the prime p    used with the P-192 curve specifiedmore convenient specification of the prime192-
                                                    Suggested remedy: include this is more conveniently specified as p =2 fiel
                                                    Suggested remedy: Define this integer uniquely as defined
(T) Clause 8.1, p. 119, l. 23: the elliptic curve domain parameter a is ambiguously defined, sincea=p-3. as a representati
                                                     ―two communicating parties‖ by ―two communicating parties (A and B)‖. Sugg
(E) Clause 8.1, p. 119, l. 29: Replace the phraseSuggested remedy: Implement as suggested.

(TR) Clause 8.1, p. 119, l. 37: The notion of
―fresh‖ 128-bit random integer can only be
realized if one stores all previously generated
random integers, a clear impracticality. Hence,
one has the weaker notion of randomness,
where one can statistically expect no collisions
between properly generated random numbers
from a huge set. Suggested remedy:               Suggested remedy: remove the word ―fresh‖
remove the word “fresh” here, since this         here, since this leads to unlimited storage
leads to unlimited storage requirements.         requirements.
                                                    Suggested be a need to specify the CMAC of operation instead and invoke in
(TR) Clause 8.1, p. 120, l. 4-6: It is unclear why there would remedy: just use the CCM modemode of operation, since one a key
                                                      Suggested remedy: the output of a keyed hash function (in casu: ―tweaks‖ a
(TR) Clause 8.1, p. 120, l. 7-9: It is not a priori clear that truncation ofonly use keyed hash functions with output sizethe CMACth
                                                    public-key remedy: Use set of security suites instead and on). The specificatio
(TR) Clause 8.1.1, p. 120, l. 20-23: (also with all Suggested based schemes in Clause 8.1 described furtherclearly specify condi
(TR) Clause 8.1.1, p. 120: It is unclear what the
cryptographic assurances are that are provided
by the described protocol. As an example,
where is the entity authentication step (C/R
protocol) that I would have expected).
Suggested remedy: Replace this scheme
by a proper symmetric-key authenticated             Suggested remedy: Replace this scheme by a
key agreement scheme (offering entity               proper symmetric-key authenticated key
                                                    agreement scheme (offering entity
authentication and explicit key                     authentication and explicit key authentication
authentication and avoiding unilateral key          and avoiding unilateral key control). I would be
control). I would be happy to help here.            happy to help here.
                                                Suggested remedy: to a protocol the so-called ephemeral Diffie-Hellman sche
(TR) Clause 8.1.2, p. 121, l. 2-4: This scheme seems to come down This variant ofshould be accompanied by an authorization s
                                                Suggested remedy: Clearly and unambiguously of the the checks that check
(TR) Clause 8.1.2, p. 121: The protocol lacks some safeguards that are essential for the securityspecify protocol, viz.: (a)need to
                                             Suggested random (since roughly half of the function to derive are not a poin
(TR) Clause 8.1.2, p. 121: The computed key DHKey is notremedy: Use proper key derivation192-bit key strings keying materia
                                                Suggested remedy: Introduce as to distinguish different protocol flows in that
(TR) Clause 8.1.2, p. 121: The protocol in Clause 8.1.1 introduced an index so proper protocol flow labels, so as to ensurethe k

(TR) Clause 8.1.2, p. 121: (Also with other
protocols) The CMAC message authentication
code requires as input a random key that ―fits‖
with the underlying block-cipher. Since AES-
128 has 128-bit keys, the key DHKey is drawn
from a much larger set (and not random
either), this does not fit the mechanics (nor the
requirements) of the CMAC construct, as
defined in NIST SP800-38B. This could be
remedied by introducing the derivation
function, as also suggested to be used in
another comment. Suggested remedy: Fix Suggested remedy: Fix this. I would be happy
this. I would be happy to help here.              to help here.
                                                   Suggested remedy: keyed convincing rationale P_2
(TR) Clause 8.1.2, p. 121, l. 31: It is unclear whether truncation of theprovidehash function outputshere. and P_3 does not have

(TR) Clause 8.1.2, p. 121: The identifiers of the
communicating parties are not included with
the DHKey computation, but only included with
the keyed hash function computations. It is not
a priori clear whether this precludes certain
subtle attacks here, as have been known for
other public-key key agreement schemes that
initially did not include this information (e.g.,
unknown key-share attack, etc.). Suggested
remedy: Please provide convincing                   Suggested remedy: Please provide convincing
rationale here.                                     rationale here.
                                                 flows indicated suggest the second protocol flow, so as to allow either ephem
(TR) Clause 8.1.2, p. 123, Fig. 92: The protocol Suggested remedy: Splitthat the second protocol flow includes both the side to
                                                     Suggested remedy: Please explain public keys is supposed to happen. Sugge
(TR) Clause 8.1.3, p. 123, l. 5: It is entirely unclear how the ―out of band‖ transfer of carefully how this works and elaborate on w
(TR) Clause 8.1.4, p. 126, l. 3, Eqn. (30): It is
entirely unclear what the benefit of introducing
the scalar M_X+1 is (in half the cases the
value is 1; in a quarter of the cases 2, etc.).
Suggested remedy: Remove this scalar                Suggested remedy: Remove this scalar (and
(and replace by the constant value „1‟).            replace by the constant value ‗1‘).
                                               Suggested remedy: Provide evidence that this hash the secure.
(TR) Clause 8.1.4, l . 10-11: Most password-based schemes I am aware of (e.g., SPEKE, EKE)protocol ispassword prior to ma
                                                    Suggested remedy: Please explain too this protocol seems to
(TR) Clause 8.1.5, p. 128, l. 3: the size of the display message (16-bit) seems to be whysmall, since itis secure. afford a birthda
                                                   Suggested remedy: the y-coordinate of the elliptic curve
(T) Clause 8.1.5, p. 128, l. 31, Eqn. (37): There is no need to include Remove y-coordinate from equation.point, since it can only
                                                   Suggested remedy: value Nonce_A has, since it does authentication (C/R) pro
(TR) Clause 8.1.6, p. 130, l. 14: It is unclear what function the nonce Replace by proper unilateral entity not provide timeliness/li
                                                Suggested remedy: Please fix this, e.g., due to use CCM* addresses (which
(TR) Clause 8.3.1.1, p. 135, Fig. 98: The nonce construction may yield re-use of nonces, by adoptingof shortmode of operation
                                               Suggested remedy: description could just copy the specification with 802.15.4
(T) Clause 8.3.1.2-8.3.1.5, pp. 135-139: The CCM mode of operation Implement accordingly.
                                                  Suggested remedy: whether the received counter value (SSN) is at least equa
(TR) Clause 8.3.2, p. 139, l. 19: Replay protection relies on checkingImplement accordingly.
                                                 Suggested remedy: Report failed status to allow some remedial action by a
(TR) Clause 8.3.2, p. 139, l. 29: there seems to be merit in flagging replayedaframes, so ascode for any incoming frame that do
                                                    Suggested justification of one crypto primitive for every suite (except for built-
(TR) Clause 8.4, p. 140, l. 5-7: It is hard to see any practicalremedy: define offering more than one cipher purpose, unless there
                                              Suggested and RFC 4086) do not seem generation processes out of scope a
(T) Clause 2: The RNG-related references (NIST SP800-90remedy: Make details re RNGto be used in the remainder of the spe
                                                 Suggested remedy: Define concise AES, AES-128 that covers CBC, CMAC
(T) Clause 4, pp. 10-12: There is a plethora of acronyms related to security, includingset of acronyms CCM, CCM,required funct
                                                   Suggested remedy: Remove is unenforceable restriction from the unenforce
(TR) Clause 5.2, p. 13, l. 12-14: The restriction that inter-node communicationthisnot possible with a one-hop BAN is specificatio
                                                   Suggested remedy: Remove all key management functionality (except clear la
(TR) Clause 5.3, p. 13, l. 25-26: It is suggested that key management functionality could be MAC functionality. This is a for key
                                                  a relative notion of Consider a not facilitating security time, so such facilitate
(TR) Clause 5.4, p.15, l. 1-3: This suggests only Suggested remedy:time, therebymore absolute notion ofservices, as to as delay
                                                 Suggested remedy: Define state the unsecured state so that does not arise e
(TR) Clause 5.5, p. 15, Fig. 4: The state diagrams seem to be inconsistent, since diagram consistently,diagram unsecured state
(TR) Clause 5.5.1.1, p. 16: The order of association and authentication seems to be off: one would expect a device to first assb
                                                Suggested remedy: Redefine security model, so that specific frames can only
(TR) Clause 5.5.1.2, p. 16, l. 18: It is unclear whether ―repealing‖ a security association is tied to aliveness/timeliness guarantee
                                                   Suggested remedy: Please provide timeliness/aliveness with this disassociatio
                                                   Suggested remedy: Allow more flexibility as to particular combination of why th
(TR) Clause 5.6, p. 17, l. 32: it is unclear why encryption and authentication could not be provided for control frames, norsecurit
                                                 Suggested a temporal key explain carefully. See also previous comment on tim
(TR) Clause 5.6, l. 39: The notion of ―session‖ during which remedy: Pleaseis valid is poorly explained. This seems to require a
(TR) Clause 6.2, p. 20, Fig. 8: when authenticity Suggested remedy: elide the FCS field having an FCS fieldis alreadySuggested
                                                  is provided, there is no added value in if data authenticity as well. provided.
(TR) Clause 6.2.1, p. 20, Fig. 9: the MAC header seems to only allow for short 1-octet addresses, thus begging the question ho
                                               Suggested remedy: Implement accordingly.
(TR) Clause 6.2.1.1, p. 20, Fig. 10: (cf. also Clause 6.2.1.1.8, Table 3): The partitioning of the 6 bits used to indicate the frame
                                                   Suggested remedy: Implement accordingly.
                                                  of 1 bit only seems Allow more flexibility flexibility in distinguishing different ke
(TR) Clause 6.2.1.1.4, p. 21: The key index field Suggested remedy: not to allow sufficient in specifying key indicators.
(T) Clause 6.2.1.1, p. 20, Fig. 10: The 4-bit
fragment number/… is often not used. This
suggests that one could economize on frame
size by using a primitive Hufmann coding
(define 1 bit ON/OFF and 4-bits elsewhere if
used). This would save 3 bits in the frame
control field in most cases. Similarly, one could
indicate security info later on in the frame, if
security is actually used (1-bit in FCF; 3 bits
elsewhere if used). Extending this could shave
off at least one octet per frame, where this
octet is only lost again if granularity is actually
required. Suggested remedy: Investigate
potential savings in avg. frame control      Suggested remedy: Investigate potential
field size by adopting the strategy outlined savings in avg. frame control field size by
above.                                       adopting the strategy outlined above.

(TR) Clause 6.2.2, p. 26, Fig. 12: The MIC
subfield should not be visible, since the CCM
construct is a ―black box‖ construct‖, where
one does not have to have any insight on
where the data authenticity bits show up in the
frame. Besides, with CCM, the MIC is actually
a truncated CBC-MAC code that is
subsequently encrypted using a stream cipher.
Since I am sure hardly anyone who
implements the specification does understand
the sentence above, I would strongly suggest
keeping the internal workings of the
cryptographic mode of operation (here: CCM
mode, but could be something else) abstract
and non-visible to people interested in frame
layouts. Suggested remedy: Remove MIC
                                                      Suggested remedy: Remove MIC subfield and
subfield and add language that Frame                  add language that Frame Payload may be
Payload may be secured, depending on                  secured, depending on setting of security level
setting of security level indicator.                  indicator.
(TR) Clause 6.2.2.1, p. 26, l. 25: The
requirement that the frame counter (Security
Sequence Counter) is incremented by one is
too strict and unobservable by other nodes.
Suggested remedy: Replace this by                     Suggested remedy: Replace this by
“incremented (by at least one)”.                      ―incremented (by at least one)‖.
(TR) Clause 6.2.2.1, p. 26: This suggests that
one needs to store a frame counter for every
key, which seems wasteful: a sender only
needs to store one frame counter for outgoing
traffic and just increments this along the way,
independent of frame type and keying material
in question. Suggested remedy: Each
device should only use one frame counter
(Security Sequence Counter) for outgoing             Suggested remedy: Each device should only
frames. Similarly, a recipient only needs to         use one frame counter (Security Sequence
                                                     Counter) for outgoing frames. Similarly, a
store one frame counter per device it                recipient only needs to store one frame counter
receives frames from (so as to implement             per device it receives frames from (so as to
replay protection).                                  implement replay protection).
(TR) Clause 6.2.2.1, p. 27: This suggests that
the SSN frame counter is incremented even in
case of resends. If so, this thwarts the security
service of replay protection (since now, a
device can send the same frame twice, but
with different SSN numbers). Suggested
remedy: Resends should use the same                  Suggested remedy: Resends should use the
frame counter.                                       same frame counter.
(TR) Clause 6.3.2.3.1, p. 32, Table 5: This
suggests that the particular protocols for a
fixed field value are fixed (and as defined in
Clause 8, with only 80-bit crypto strength).
What about algorithm agility here? Why is
there no public-key based authenticated key
agreement scheme with certificates? What
about a proper symmetric-key based
authenticated key agreement scheme?
Suggested remedy: allow much more                    Suggested remedy: allow much more flexibility
flexibility in terms of schemes supported            in terms of schemes supported (algorithm
(algorithm agility!).                                agility!).
(TR) Clause 6.3.2.3.2, p. 32, Table 6: The
security level options seem too limited.
Moreover, this would benefit from making this
dependent on frame type/subtype in question,
so as to allow more flexibility (this is also done
in 802.15.4-2006). Suggested remedy:
Implement accordingly.                               Suggested remedy: Implement accordingly.
(TR) Clause 6.3.2.3.4, p. 33, Table 7: No clue
where Camilia comes from. While this was a
 nd
2   round AES Candidate block cipher,
everyone else in the world who specified
something post 2001 uses AES-128 (a.k.a.
Rijndael). There do not seem to be any
advantages in introducing this somewhat
arbitrary other cipher and lots of
disadvantages: lack of compatibility,
higher implementation cost, control traffic
cost, key management cost. Suggested
remedy: Remove Camilia from the list and Suggested remedy: Remove Camilia from the
make everything except AES-128 a            list and make everything except AES-128 a
reserved value.                             reserved value.
(TR) Clause 6.3.2.5, p. 33, Fig. 19: The
protocol messages should also include a
protocol identifier (e.g., to logically group
different protocol flows corresponding to a
single protocol invocation). Suggested
remedy: implement accordingly (1-octet            Suggested remedy: implement accordingly (1-
field seems sufficient).                          octet field seems sufficient).
(TR) Clause 6.3.3.1, p. 36: The extended
addresses seem to be EUI-48 addresses. This
seems to be too short, given the potential
number of devices in body area networks. Why
not use an EUI-64, so as to be sure to have
globally unique device identifiers? This would
allow not running out of space and would also
allow device certificates based on this address
issued by a CA. Suggested remedy: Use
EUI-64 addresses, rather than 48-bit              Suggested remedy: Use EUI-64 addresses,
entries.                                          rather than 48-bit entries.
Clause 6.3.3.2.1, p. 36: Randomness of the
sender nonce does not provide any
freshness/liveness/timeliness assurances to
the recipient (since not a proper challenge
response protocol). Suggested remedy:
Make this a proper challenge response             Suggested remedy: Make this a proper
protocol. I would be happy to help with           challenge response protocol. I would be happy
this.                                             to help with this.
Clause 6.3.5, p. 38, Fig. 22: The structure of
the group temporal key is unclear. Is this
supposed to specify the structure of keying
material? If so, where are the policy fields,
such as key validity period, key usage, etc?
Moreover, how does the MAC even know
about these (generally) higher-layer concepts?
Shouldn‘t the sender address be the address
of the key originator instead? What about SSN:
shouldn‘t this be a key serial number instead
(cf., e.g., corresponding notions for public keys
with X509 as specified with RFC 5280)?
Suggested remedy: Please clarify intent,            Suggested remedy: Please clarify intent, since
since this is highly unclear now.                   this is highly unclear now.
I don't see any difference between
"coexistence request" and "coexistence              Change "Command - Coexistence Request" to
response".                                          "Command - Coexistence Time Sharing".

The "received signal strength of signals" is not
an accurate represenation of the quality of the
link in presence of noise and interference and
can't be use for an abosulte calibration.        Remove the Relay Link Quality field

The function of type-II polled allocation can be    Consolidate type-I and type-II polled allocation.
achieved by using type-I polled allocation.         If not, justify the need for both
There is not much difference between the Poll
frame defined in clause 6.4.5 and the Wakeup
frame defined in clause 6.4.7.                      Consolidate these two frames.
"High QoS mode" is mentioned but not defined.       Define "High QoS mode".

                                                  Remove the "Relay This field cannot be used in a reliable way in presence of
The use of a signal strength to define the link quality is questionable.Link Quality" field or find another way to measure the link q

                                               Remove it or add some text.
This clause is missing some text and need further explanation.

The SFD is not defined                          Define the SFD structure
Aloha                                           ALOHA
UWB needs CSMA/CA as well as slotted ALOHA.     CSMA/CA should be added for UWB.
                                                 not defined in this document.
Although the term "IR-UWB PHY" is used, it has Define the term "IR-UWB PHY" as a Impulse Radio type of UWB.
                                                 carefully reconsidered according to band same or of 15.4a and 15.4f.
Operating band allocation of 802.15.6 should be Band allocation of 802.15.6 should be the allocationovercompatible as 15.4a.
                                                Need more numenrical analysis for the coexisitence
Coexistence between FM-UWB and IR-UWB should be carefully investigated using more realistic environment. If FM-UWB int
                                                Coexistence between HBC system and other all frequency bands
HBC should not harm for the narrowband and UWB PHY in wearable and implantable BAN forNB and UWB systems must be in
Table caption typo                              rage => rate
the use of this table is very unclear with all
these reserved bits. It refers to 9.1 which is
only for the NB PHY and not the others.
Moreover the numbre of rates (5) is less than Fill in the table or explain better why there is so
the UWB PHY possiblities                        much reserved bits
limited differences between NB and UWB          table 24 & 25 should be merged
An alternate channel rejection specification    Add an "alternate channel rejection"
would be useful as well                         specification
                                                The ultra wideband (UWB) PHY specification is
                                                designed to provide a large panel of
                                                implementation opportunities for high
                                                performance, robustness, low complexity and
                                                ultra low power operation. Moreover, the
                                                interest of UWB lies also in the fact that the
                                                signal power levels are in the order of those
                                                used in the MICS band, therefore providing
                                                very low power levels for the human body and
Wording of the paragraph to improve for clarity low interference to other devices
Unclear paragraph and inappropriate use of      The UWB PHY provides four core
the term "PLCP" which is not a sub-layer        functionalities:
                                                1) The UWB PHY provides a Data interface to
                                                the MAC layer under the name of the PD-SAP.
                                                It handles the frame exchange between the
Wording of the paragraph to improve for clarity MAC and PHY.

                                                2) The UWB PHY constructs the PHY layer
                                                protocol data unit (PPDU) by concatenating the
                                                Synchronization HeadeR (SHR), the Physical
                                                layer HeadeR (PHR) and the Physical Layer
                                                Service data Unit (PSDU), respectively. It
                                                converts the PPDU into an RF signal to be
Wording of the paragraph to improve for clarity transmitted over the wireless medium.
                                                4) The UWB PHY provides a Management
                                                interface to the MAC layer under the name of
                                                the PLME-SAP. This interface is used to
                                                configure the parameters of the PHY, and in
                                                particular to set and get values of the PHY
Wording of the paragraph to improve for clarity Information base (PIB).
                                                3) The UWB PHY optionally provides clear
                                                channel assessment (CCA) indication to the
                                                MAC in order to verify activity on the wireless
Wording of the paragraph to improve for clarity medium.
                                                One mandatory synchronization header (see
SHR=synchronisation header                      7).
                                                One mandatory Forward Error Correction
FEC acronym                                     mechanism (FEC)
                                                this is undefined. Probably the whole sentence
beacon preambles                                is useless
                                                A combination of on-off keying (OOK) with 64-
                                                ary coding and differential phase shift keying
                                                (DPSK) modulation schemes is used to be
                                                able to comply with a large set of receiver
                                                architectures like non-coherent and differently
                                                coherent receivers. Variable data rates is
                                                obtained by changing the pulse waveform
                                                duration, the symbol duration and the
                                                modulation scheme while keeping the
                                                waveform duty cycle constant. On-off keying is
                                                the mandatory modulation format to support
                                                and DPSK is optional for the default mode
                                                Conversely, DPSK is mandatory in the high
Wording of the paragraph to improve for clarity QoS mode, and on-off keying is optional.
                                                The Forward Error Correction (FEC) scheme is
                                                mandatory for the transmission of PHR and
                                                PSDU.It is noted that the use of a systematic
                                                code makes decoding optional at the receiver
Wording of the paragraph to improve for clarity for the PSDU

                                                Full function devices (FFDs) shall implement
                                                the IR-UWB based modulations, so namely the
                                                OOK or DPSK modulation schemes depending
                                                on the mode of operation. They can optionally
                                                implement the FM-UWB mode described in
Wording of the paragraph to improve for clarity section XXX.
                                                Reduced function devices (RFDs) shall either
                                                implement one of the IR-UWB bases
Wording of the paragraph to improve for clarity modulations or the FM-UWB mode.

                                                Only FFDs are allowed to send beacon frame
Wording of the paragraph to improve for clarity and to coordinate beacon-enabled networks.
                                                Only FFDs are allowed to form non-beacon
Wording of the paragraph to improve for clarity enabled networks.
                                                In any case, it is not allowed to form a network
Wording of the paragraph to improve for clarity made of RFDs only
                                                RFD and FFD concepts are meaningless in the
                                                UWB PHY section if not defined at the
                                                beginning of the standard, and in the MAC
RFD and FFD not introduced in the MAC           section. Clarify.
                                                Priority of access to resources is given based
                                                on the fact that the running application is
Wording of the paragraph to improve for clarity medical or non-medical.

                                                Medical applications are given a higher priority
continuation of previous comment                than non-medical applications by two means:

                                                1) If resources in the BAN are becoming
                                                scarce, frames from the medical applications
                                                shall be given a higher priority than frames
continuation of previous comment                from the non-medical applications.
                                                 2) If a medical device receiver suffers a
                                                 degradation of its sensitivity above 1 dB, the
                                                 coordinator shall enforce non-medical devices
continuation of previous comment                 to reduce their EIRP.

                                                The PSDU contains the payload received from
                                                the MAC via the PD-SAP which is formatted for
Wording of the paragraph to improve for clarity further transmission over the wireless medium
                                                The SHR is divided into two parts. The first
                                                part, the preamble is intended for coarse timing
                                                synchronization while the second part is the
                                                start frame delimiter (SFD) for frame
                                                synchronization. The preamble is formed of
Wording of the paragraph to improve for clarity repetitions of Kasami sequences.
Figure 117, replace SAP by PHY-SAP              Figure 117, replace SAP by PHY-SAP

The MPDU internal structure is out of scope of
the PHY specification. Moreover the maximum      Limit th description to role and size of the
length is 255 bytes, and not 256 bytes           MPDU and give a link to the MAC specification
Figure 199 caption                               "the" side-stream scrambler
In the case of un-coded transmission, CW N is    FEC being mandatory, there is NO uncoded
set to zero.                                     transmission case. Remove
                                                 If the encoding process for the BCH is identical
                                                 to the one of the NB PHY, just give a reference
BCH encoding                                     to section 9.4.1.
                                                 If the encoding process for the BCH is identical
                                                 to the one of the NB PHY, just give a reference
Pad bits                                         to section 9.4.2
SHR Preamble                                     Synchronization Header (SHR)
                                                 The SHR is composed of the preamble and the
                                                 start-of-frame-delimiter (SFD). The preamble is
                                                 commonly used to detect the frame and
                                                 perform symbol and carrier timing acquisition,
                                                 whereas the SFD is used to indicate the
Wording of the first paragraph to improve for    beginning of the actual useful fields of the
clarity                                          trame.
Separation of preamble and SFD to appear in      Add a subtitle "Preamble" as 10.7.1 after the
titles                                           first paragraph proposed above
                                                 In order to perform symbol and carrier level
                                                 timing acquisition , a preamble consisting of
                                                 known data is transmitted at the beginning of
                                                 any frame. Such a preamble aims at being
                                                 detectable by a plurality of receivers, including
Wording of the paragraphs to improve for         non-coherent or differentially coherent
clarity                                          receivers.
                                                 Kasami sequences of length 63 shall be used
Wording of the paragraphs to improve for         to build the preamble for both the non-coherent
clarity                                          and differentially coherent PHYs.
                                                There are eight possible Kasami sequences
                                                defined in table 3. They shall be used
                                                according to the physical channel in use and
                                                are selected through the PLME-SAP (through
Wording of the paragraphs to improve for        the MLME.SET primitive) to improve co-
clarity                                         existence.

                                                The set of sequences shall be divided into two
                                                pools. Each pool has a set of 4 sequences.
                                                The first pool C1 to C4 shall be used for odd
                                                physical channels. The second pool C5 to C8
                                                shall be used for even physical channels.
                                                Therefore, four logical channels are available
Wording of the paragraphs to improve for        per physical channel by virtue of the sequence
clarity                                         selection in the pool.
                                                The coordinator may scan all the logical
                                                channels and use the preamble with minimum
                                                received power level. Coexistence of BANs
                                                and interference mitigation can be achieved by
                                                virtue of the inherent duty cycling in the
Wording of the paragraphs to improve for        modulation and the preamble sequences with
clarity                                         good correlation properties.

                                              Introduce a PMLE-SAP and SET primitve to
                                              configure such a parameter, plus introduce the
                                              MAC coexistence mechanisms accordingly
                                              (selection by the Hub ? After having listening to
How is selected the Kasami sequence in a pool beacons of potential other BANs ?)
                                              Shorter sequences (eg 31) would simplify the
                                              receiver implementation, especially in
Sequence length of 63                         presence of large time drifts
                                              More sequences of smaller length would
                                              benefit the performance and the receiver
Number of sequences Ns = 4                    implementation
                                              A larger set (eg Gold codes, which has nearly
                                              as excellent crosscorrelation properties than
                                              Kasami sequences) could be used to improve
                                              coexistence according to the TG TRD, and
                                              would offer a large choice for the SFD
8 sequences in the proposed Kasami set        specification
The value of L is 16 for the OOK (non
coherent) modulation and is not valid for the
DPSK (differentially coherent) modulation     The value of L is 16 for the OOK (non
because the overall duty cycle has to be kept coherent) modulation and is 32 for the DPSK
constant to 3%                                (differentially coherent) modulation
sequence of table 50                          table 53
In figure 116, the SFD is defined as being 2
sequences S0, but such a definition is not
reported here, and S0 is never defined (S0
cannot be constructed from the Kasami
sequence set since no C0 exists)              Define the SFD consistently with the preamble
                                                Update links to equations or add equations.
                                                The case of DPSK, for which the mapping of
                                                the preamble sequence chip is done onto (-
                                                1,+1) in a differential way should be made
                                                clearer. The text could be changed by
                                                something like "Depending on the modulation
                                                mode, the Kasami sequence is transmitted in
                                                an OOK or DPSK fashion: in OOK, each chip
                                                of the kasami sequence for which the value is
                                                zero is mapped to 0 (no signal) whereas in
                                                DPSK, each chip of the Kasami sequence is
                                                mapped according to (0 -> -1 and 1->1) and is
The equations should be provided (links are     differentially encoded before transmission,
not OK)                                         using 1 to initalise the differential encoder."
                                                Construction of PREAMBLE symbols from A
                                                Kasami sequence IN THE NON COHERENT
Figure 123 caption is not explicit enough       MODE
repetions                                       repetitions
                                                Add "It is kept constant to 3% whatever the
duty cycling factor                             modulation format and the data rate"

                                                Add "In the following, for the sake of simplicity
                                                when there is no ambiguity, the long pulse
                                                shape and the burst of short pulses will be
                                                called ―the burst‖. " And replace "pulse
                                                waveform" by burst in all following sections.
10.10.1 PRF parameter. The definition which     And precise that "In the burst of short pulses
follow will be clearer if a better teminology isoption, the PRF shall be interpreted as the
used than "pulse waveform".                     Burst Repetition Frequency."
"non coherent modulation" is not a very
adequate naming bacause "coherence" is
more a matter of reception                       Replace by "OOK modulation"
"differentially coherent modulation" is not a
very adequate naming bacause "coherence" is
more a matter of reception                       Replace by "DPSK modulation"
DC bias                                          Remove, this is not the issue
                                                 It shall not be applied for the differential
Time hopping                                     coherent PHY
Detection: the text proposed refres to the       Move the complete section in annex
receiver and is not normative                    (informative text)
                                                 replace by "PSDU" (the preamble has no
PPDU                                             information bits)
DBSK                                             DPBSK
                                                 Tp is the parameter of the pulse shape p(t) (as
                                                 in 15.4h: Tp is defined as the inverse of 499.2
Tp is the duration of the pulse shape p(t)       MHz)
                                                 In the table "bandwidth" should be replaced by
"bandwidth" is not precise enough                "maximum 3dB Bandwidth"
the central frequencies of the band plan shall
have an accuracy of 20 ppm.                      Remove, this is too stringent
                                                  Keep the figure and update equation (93)
                                                  accordingly (last part of the equation is valid for
Figure 128 does not fit the equation (93) for the 0.8/Tp<|f-fc|<1/Tp, and one should add "-20dBr
values beyond                                     for |f-fc|>=1/Tp)
Tp=2ns                                            Tp=1/499.2MHz ~ 2ns

                                                For the sake of readibility we can let the
Tables 54 and 55: values which are given in ns rounded values in the tables, with a footnote,
are integer multiples of the chip duration "Tp" but we have to give the exact definitions
which is not exactly 2ns (but 1/499.2 MHz).     through equations (which is done in 10.10.4,
Therefore they are rounded values               but here Tp needs to be defined already)
Tp=2ns                                          Tp=1/499.2MHz ~ 2ns

Figure 129 — PSD centered at 4492.8 MHz            20Tp truncation example is too much !
and truncated to 20Tp satisfying ...               Propose a tighter truncation fulfilling the mask
10.15.3 Chaotic pulse waveform. There are no
equations to generate the waveforms, thus this
text cannot be normative                        Remove the section
"Preamble SHR"                                  "Preamble"
                                                The FM-UWB shall not be restricted to a single
                                                Kasami sequence if it supposed to provide
                                                similar coexsitance performance than FM-
                                                UWB. Offer more possiblities or explain how
2nd Kasami sequence                             coexistence is provided.
                                                  shall turnaround time
table 64. Several parameters are out of scope orTx-Rx not appear here is already defined in the MAC section and hsall be remo
Figure 136 — FM-UWB transmitter block
diagram. Center frequency is not 7.9 GHz        Change center frequency to "Fc"
This subcarrier signal m(t) modulates the RF
VCO (wideband frequency modulator), yielding Change the text to a more normative text
a constant-envelope UWB signal with a flat      (remove "VCO" or say it is for example,
power spectral density and steep spectral roll- remove "steep spetral roll-off" since non
off.                                            normative)
This paragraph is redundant                     remove
From an implementation point of view the
triangular 15 waveform is straightforward to
generate using either analog or digital circuit
techniques                                      Non normative => remove
Figure 137 — Frequency spectrum of FM-          Update with a high quality figure, with the right
UWB signal at 7.5 GHz center frequency          caption for the center frequency
                                                Though given as an example, this section is
10.17.5 Receiver architecture                   non normative and can be removed
                                                If slotted aloha SHALL be employed, then the
The receiver may perform clear channel          CCA is useless. Rephrase to clarify. If CCA
assessment (CCA) by using either the energy SHALL be supported, then it should be
detection or 14 preamble detection. However, explained over which time it has to be
slotted aloha shall be employed                 calculated
                                                Explain why figure 143 stand
Does figure 143 represent a required preamble miss detection performance ? for or remove it
The sentence "The SFD field can also indicate"
is unclear. Does "can" mean "shall" ? "Should" Remove "can" and remplace with appropriate
? Something else ?                              wording
Table 68 is identical to table 65               Remove one of the redondant table
"DRF" isn't yet defined                         explain DRF
What do you mean by "master" and "slave"
node ? Coordinator ? Initiating devices &
receiving devices ?                                Clarify the meaning of Master and Slave node
                                                   Clarify the meaning of Master and & receiving
What do you mean by "master" and "slave" node ? Coordinator ? Initiating devices Slave node devices ?
It's unclear wich of the two data rate indication
mode shall be implemtend. Is one of those
mandatory ? Optionnal ? Which one is the           Replance "can" with appropriate "shall" and
default mode ?                                     "should"
                                                   define a default behaviour
No indication is given on any "default" rate indication mode. A implementer doesn't know which one to implement and use
                                                   Explain a be able to decode PHR network allready done with RI,
This mean that a legacy devices joining the network won't legacy device can join a of a transmission operating in RI mode
                                                   Replance "can" required ? Is that an option ?
"Pilot sequence can be inserted in PSDU" is very unclear. Is thatwith appropriate "shall" and "should"
                                                   Explain more in detail what is a pilot sequence
Pilot sequence length is not defined : a single SFD sequence ? Several of them ? How does it work when using higher data rate
                                                   Explain why radio receiver operating in as 1-30 MHz range, those equipemen
Transmit mask seems very weak. Given the high sensivity of the spectrum mask is seen the protective enough, or if it's not, imp
                                                   Give clock how to deal with other clock speed as any clock frequency
Table 77 is specified for 64 MHz clock. You need to explaintolerance value that are applicable withan implementer is free to use
                                                   Explain how this system the 27 MHz ISM band remove mention of any possibl
Intentional radiation on any non allocated band is illegal in Europe. Since is usable in Europe, or is only 400 kHz wide and since
                                                   Consolidate tpye-I and polled polled allocation. If not, justify the need for type-I
The function of type-II polled allocation can be achieved by using type-I type-II allocation.
exclusieve should be "exclusive"                   See comment.
curren should be "current"                         See comment.
                                                   Consolidate these 6.4.5 and Wakeup frame defined in clause 6.4.7.
There is not much difference between Poll frame defined in clause two frames.
high QoS mode is mentioned but not defined. Define what is "High QoS mode".
                                                   "In particular,
What is the purpose of "Emergency frame with no payload"? the node should transmit as the alarm an Emergency data frame
"It is locally broadcast by a hub... " --> B2 message is for exchaning frame between other piconet coordinators. Local broadcas
                                                   locally broadcast -> broadcast
                                                   locally broadcast exchaning frame between other piconet coordinators. Local
"In B2 frames locally broadcast by a hub... " --> B2 message is for-> broadcast
                                                   The detailed
The detailed descripion of GPPM can be included in Annex descripion of GPPM can be included in Annex
                                                    up by a long period such as can be month. Battery based in-body devices can
Implant devices occasionally needs to be wokenAnother wakeup mechanism several considered in MICS band for lond wakeup
                                                   Show HBC can be
HBC is fundamentally questionable in terms of wireless technique satisfied with the requirement of the TRD, such as "6. Trans
                                                   Show the
The computer simulation condition is important but vague channel model for evaluating the performance
The mask seems valid only for fc=16MHz             Show the transmit spectrum mask for fc=27MHz
                                                   Use the units of dBm and dBm/MHz 400MHz
HBC should do no harm for the Narrowband PHY in MICS band starting from around instead of dBr and dBr/MHz
                                                   Show the maximum limits for the conduction the radiation powers
HBC is categorized into not wireless but wired technique, so a special attention is required forand transmit power which should
                                                   explicitly mention that time well in and offset
Co-existence mode terminology needs more clarification and is not defined sharingthe draft piconet synchronization are non-
use of the term "hub"                              change the use of the word "hub" in the document to "co-ordinator" in the entire
                                                   The explanation related to the co-existence modes is insufficient. The text nee
explanation of co-existence modes needs clarification
Time sharing mode needs clarification              The explanation related to the time sharing co-existence modes is insufficient.
                                                   From
Offset BAN synchronization mode needs clarification reading the text, it is not clear what does the word "offset synchronization
Interference mitigation mode needs clarificationsThe explanation related to the interference mitigation co-existence modes is in
                                                   Add usage of nodes benefit from the use of relays about adjacent contribution
Use of relays for piconet co-existence. TG6 piconet co-existence canas relays to gather informationas presented in piconets an
Termination messages for ending co-existence It is not clear from the document how the co-existence modes gracefully (or oth

                                                   don‘t have good cross correlation properties. The cross those developed for U
Two preamble sequences specified in the tablesConsider using more preamble sequences (for example,correlation goes as big
Duty cycling for UWB                              Mention UWB PHY supports duty cycling in its modulation and does not have a
                                                  They need to be statements. a clearer structure and meaning. Combine gen
The subclauses of this clause overlap back and forth with similar rewritten withSome sentences are grammatically incorrect, irre
                                                  Change "impromptu" to "improvised". Remove the last sentence.
This comment is made based on an earlier comment by an active MAC participant.
                                                  Change "one-periodic" to "1-periodic".
"One-periodic" and "1-periodic" -- inconsistencies.
                                                  Restore without any markup to shalls and tone (―shall do‖ changed to ―do‖). T
Quite a few prescriptive shalls in Clause 5 were changedthe original prescriptive descriptive mays.
                                                  Change
Emphasize that all these frames are unsecured frames. the comma in line 14 to "and", add "unsecured frames" before the 1st
                                                  Change the comma in line 23 to secured fraems.
Clarify explicitly that some of these frames are unsecured frames, and some are "and", add "unsecured frames" before the 1st
Clarify "as appropriate".                         Change "as appropriate" to "if control frame authentication was not selected du
                                                  Restore all instances of of "1" are converted to "one", and one", "set … to one
This comment applies to numerous clauses. Some, but not all, instances"one" to "1" in the context of "set tosimilarly some, but
                                                  Would MAC and security make the the draft. Many, but not all, please? Co
This comment applies to many places (especially in the the technical editorclauses) infollowing formatting changesunnumbered
Typo.                                             Move "not" to before the first "enabled" in this line.
Formatting glitch.                                Capitalize the first letter of "type" and "subtype".
                                                    Would the technical crowded. (2) The first row needs cleared alignment. (1)
This comment applies to numerous tables. (1) These tables are a bit editor make the following formatting changes please?(3) th
Internal horizontal lines should be thinner.        Thin the internal horizontal lines below the 2nd row.
                                                    Remove the row of "Wakeup" frame from Table 3, subclause in some subcla
The Wakeup frame provides no more functionality and effectiveness than the Poll frame, as explained in detail6.4.7 and related
Unwarranted capitalization.                         Change "Field" to "field" before "encoding".
Duplicate bullet number.                            Delete "6." at the start of the text.
                                                    After "Coexistence format", well (as beacon another
The Coexistence field can be reused to define some fields for B2 frames as add "for noted in frames". comment).
                                                    field, lines 14 and 20, change "first" to "final". (2) In lines 17 is the last one of
Use backward coding for the Fragment Number (1) In so that the recipient knows if the last received fragmentand 22, delete "no
                                                    (1) Insert a new numbered bullet before this line, with the
Define the Coexistence field for B2 frames, so that some fields don't need to appear in the frame payload. following text: h) In B
                                                     6. While Clause 7 is written in prescriptive style (shall, should,
This comment applies to many places of Clause Restore all instances of "shall" to "must" throughout Clause 6. may) to specify
                                                    Would the technical the draft (especially in spacings to security clauses). Th
This comment applies to most paragraphs following a bulleted item ineditor please adjust thethe MAC andbe a bit more uniform
                                                    Move the misplaced commas?
Comma misplaced. Did reformatting in D0 generate othercomma from before to after Figure 12.
"not" misplaced.                                    Move "not" to before the first "enabled" in this line.
"not" misplaced.                                    Move "not" to before the first "enabled" in this line.
Simplify naming.                                    (1) Delete "Required" from the "Security Level Required" field in Figure 18. (2)
This comment applies to many tables in Clause 6. "Field value decimal"… please insert "in" before "decimal" J71and make "i
                                                    Technical Editor, would you
"Protocol" is not part of the field anymore.        Delete "Protocol" from the heading.
Formatting glitch.                                  Make the two internal lines (below the 2nd row) thinner.
                                                    (1) and the the B+EAP1 Length and EAP2 Length which (2) frame is Status
There are some inconsistencies between this frameRemove Connection Assignment frame in 24 onfields. thisMove the based.
Unwarranted capitalization.                         In the table heading, change "Field" to "field".
                                                    (1) Change "Request" discussed, let alone Change "Command Coexistence
(1) The frame formats of these two coexistence commands were neverto "Time Sharing". (2)approved, in the MAC- subgroup. (
                                                    Promote 6.3.11.4.1 to one level higher as 6.3.12, and keep the
6.3.11.4.1 should be a parent subclause of the three subclauses that follow, instead of being at the same level. subclauses tha
                                                    Change "Command - Coexistence Request" to "Command two separate Time
There is no functional difference specified for "coexistence request" and "coexistence response". Hence no - Coexistenceframe
                                                    (1) Change to to frame defined here.
These lines need to be revised in view of the changes made "in"the "for" before "a Command". (2) Insert "time sharing enabled"
                                                    (1) needed to be reworked to be consistent in naming field proposed other se
(1) Both the definition and table for "Piconet priority"Change "Piconet Priority" to "BAN Services", a new and format within the Co
                                                    Remove them along with the figure and table the "status" field, which, however
These are just duplicates of the subclauses for the "Coexistence Request" version, except for within.
Incorrect level for these three subclauses.         Promote 6.3.11.5.4 to one level higher, and keep the two subclauses that defin
Incorrect level for this subclause.                 Promote 6.3.11.5.7 to one level higher.
Incorrect level for this subclause.                 Change "in" to "for" before "a Command".
                                                    (1) Change set…, but to the relay node will set this field.
(1) locally broadcast but not locally multicast. (2) the field is "multicast"not "broadcast" in line 5. (2) Reword the 2nd and 3rd se
                                                    Remove the the quality of the field presence of noise and interference.
The "received signal strength of signals" does not truly reflectRelay Link Qualitylink inand all references to it, unless the propose
                                                    (1) or the MAC header of the definition subclauses (and Table 13 which has a
(1) Many fields are already contained in the beacon Remove all fields and theirB2 frame, and should not be duplicated here, per
Typo.                                               Change "rage" to "rate" in the table heading.
Formatting glitch.                                  Make the two internal lines (below the 2nd row) thinner.
Two much space.                                     Delete this empty line.
                                                    Change "to indicate
Some clarification is needed on why and when this IE is included. ..lengths" to "foretell some information on the superframe (
                                                    Add to needed to be separately included, so is the beacon shifting sequence
If superframe length and allocation slot length fields arethe end of the current IE an optional "Beacon Shifting Sequence" field. f
                                                    somewhere else.
Avoid repeating a definition that is already given Change these two lines to the following: The Superframe Length field is as de
                                                    somewhere else.
Avoid repeating a definition that is already given Change these two lines to the following: The Allocation Slot Length field is as d
                                                    Add
A new subclause is needed to define the new field. a new subclause, 6.7.1.3 Beacon Shifting Sequence, with the following tex
Figure formatting glitch.                           Insert two dashed lines at the start of the bottom fields to indicate continuation
Figure formatting glitch.                           Insert two dashed lines at the start of the bottom fields to indicate continuation
                                                    Insert a Assignment frame should be defined "Node Address" field.
The "Status Code" field now in the Multinode Connectionone-octet "Status Code" field after the on a per node basis and hence
Inconsistent frame reference.                       Change the paragraph to "All the fields after the Length field pertain to the sam
                                                    Remove the row containing functionality
As explained in related comments, the Wakeup frame provides no additional"Wakeup". to the Poll frame.
Typo.                                               Add "final" before "frame sent", and change "last" to "previous" before "block tr
                                                    After "pSIFS", add ", depending on
Need to make a connection with burst mode transmission defined in the PHY spec. whether it is setting the block transmission
Figure 55 was mistakenly changed in this draft. Remove all the test boxes other than those indicating a frame.
                                                    It is time to resolve Type II access phases, other than basis. Remove delayed
(1) There is no technical justification for having separate Type I and technical comments on a technical fragmenting the superfra
                                                     can "send" add "at most".
Need to make it clear that an unconnected nodeAfternot send more than one frame in a shared polled allocation.
Formatting glitch.                                  Make the first "n" a regular instead of an italic letter in "fun ction".
Typo.                                               After "which" change "are" to "is".
                                                    In line 36 of needs to be decoupled from add "the appropriate guard time in th
The "appropriate guard time" is not a fixed value, and hence page 78, after "shorter than" the parameter referenced earlierplus"
Figure 65 was mistakenly changed in this draft. Remove all the test boxes that appear on the top or bottom of the figure.
                                                   Make "Frame" plural
Formatting glitch in the heading of Table 20, introduced in this draft. and delete "(1-1)".
                                                   Remove the last row of Table 20, and add a
                                                   new short paragraph after Table 20: A hub
The last statement of Table 20 is not quite        may send a post at the start of a poll
clear.                                             announced earlier.
                                                   Remove all the test boxes other than those
Figure 66 was mistakenly changed in this draft. indicating a frame.
Unfinished cleanup from last draft.                Delete ", and one or both of the MSDU … nonzero values".
                                                   Change "the hub shall respond with" to
The hub may also send an unsolicited Connection Assignment frame as intended here. ", requested by the node or initiated by
                                                   Delete "a", "b", 'c" in these figure captions.
Figure 69, Figure 70, Figure 71 already have separate figure numbers, but were numbered by "a", "b", and "c" further in this dra
                                                   After this cannot be add a new one
Need to explicity state that an ended scheduled allocation paragraph used anymore. as follows: A node or a hub shall not send
                                                    have appeared here.
This subclause makes no sense and should not Remove it.
                                                     -- when?
No shalls. "…shall send the wakeup messages"Remove these two paragraphs, as they provide unnecessary introductory infor
                                                     this is not how
I explained to the proposers back at the F2F thatRemove them. the I-Ack works: A recipient would not go into the payload to c
                                                   Remove these duplicate but inaccurate and incomplete poll, as specified here.
(1) It increases complexity and decreases efficiency to have a wakeup followed by an Ack and then by a descriptions of the unic
Typo.                                              Change node to "nodes".
                                                   Change "session to "phase" throughout this subclause and Figure 76.
Do not use "session", which has a special meaning per MICS band regulations.
                                                    in Fig. 76.
Need to make a connection with "lockup phase" After "Poll frames", add "forming a lockup phase and".
                                                   After "polled
Need to make a connection with "individual phase" in Fig. 76.allocation", add " thus starting the individual phase for the node as
                                                   Change "shall" to "should".
A "shall" may not always be justified as the nodes might not know in advance the time of pending frame exchanges.
                                                     might have missed earlier
A "shall" may not always be justified as the nodeChange "shall" to "should". polls.
                                                   intent of this duplicate more accurately and consistently, as explained further
Figure 76 and the related text accomplishes the Remove this subclausebut inaccurate and inconsistent subclause 7.8.2.1.4.
                                                    more power consumption for described scheme is not well thought out and ha
(1) The described mechanism would only cause It is time to recognize that the all nodes, which would have to wake up several t
                                                   After "it should", performed on other channels.
Tighten up the sentence do expressly convey the same behavior add "similarly send and".
                                                   (1) --- since pMICSFrameSpace after            same its different transmission".
Frame spacing does no longer have the same valueDelete "atthe next frame may be on the end ofor alast framechannel.
"emergency" is a data frame name.                  Capitalize the first letter of "emergency" for consistency.
                                                   Rewrite the whole subclause to address the outstanding issues.
This subclause has yet to define the frame structures used to support the relay functionality, and to specify the access methods
                                                   (1) Move them to end of of 7.12 this new subclause, 7.12.5. that follows.
It will have a better structure to create a separate subclause at thethe end 7.12 for as a paragraph and the table Applicability guid
                                                   Rewrite the implementation to specify does hub is supposed to do for coexis
Much of this subclause is either tangential to coexistence or whole subclausespecific. Ithow a not prescribe testable normative
                                                   Delete "and load reduction" from the heading.
Load reduction is covered in a separate subclause later.
                                                   Delete them as they are not germane to normative coexistence behaviors.
These are not about coexistence per se, but more about BAN creation (and maintenance) which is already described in 7.4.
                                                   Delete them that are implementation germane to normative coexistence beha
Again these are not specific to coexistence but specify things as they are not correct orspecific (which are generally not to be pa
                                                   Delete them as they frame, and BAN descriptor? (2) How normative coexiste
(1) What on the earth are BAN enquiry frame, BAN enquiry responseare not defined, correct, or germane tois the hub supposed
                                                     coordinator as they are not with respect to it if it is not implementation specific
(1) Again what is a BAN descriptor and what is aDelete them supposed to do defined or germane to normative coexistence beh
                                                   Delete them as they have no substance or are not germane to normative coex
(1) Why shalls? A hub may choose no channel at all and create no BAN. (2) How is a hub supposed to "utilize the information
No need for a new, lower level subclause           Delete the heading.
Certainly not a shall.                             Rephrase them as a "may".
Inaccurate or repeated sentences.                  Remove them.
                                                   Remove 7.12.3.1 if these fundamental issues are not addressed inconsistent
(1) Connection request,, coexistence request, coexistence assignment, coexistence assignment request -- still soby end of the
Is this in essence time sharing as well?           Merge this subclause with 7.12.3.1. Both are about time sharing, and may be
                                                     sharing this subclause to but level higher, be change the heading to "Code d
(1) This subclause should not be under the timePromote subclause 7.12.3, one rather shouldand in parallel. (2) The heading do
                                                   Remove the subclause this subclause -- which coexistence per se, or rewrite
(a) How can interoperability tests be designed based on the language ofwhich is not germane to again is so unfocused and has
                                                     an earlier comment.
This is part of the paragraph with issues noted inRemove it or refine it together with the earlier part of the subclause.

Rephrase the heading in MAC terms.               Change the heading to "Allocation reduction".
                                                 Rephrase the subclause The 3rd it more concise and precise. Suggested tex
The first two paragraphs need to be rewritten in more concise language. so makeand 4th paragraphs are a repeat of the gener
It is hard to interpret and use table 22.        Edit it -- in line with the BAN's designated services defined for time sharing.
                                                 Restore in this draft existed prior to D0. at the are not correct
This subclause was modified, incorrectly or inaccurately, the text that without a discussion If they MAC subgroup.or complete, pl
                                                 Change the value entry to pMICSMcastPollSeparation + pMICSPreambleTxTim
Incorrect equation and parameter value for pMICSMcastPollRxTime.
                                                 Change the value entry to ceiling[pMICSChannelsTotal × (pMICSMcastPollRxT
Incorrect equation and parameter value for pMICSMcastPolls.
                                                 Change the value entry
Incorrect equation and parameter value for pMICSMcastPollSeparation. to pMICSPollTxTime + pMIFS = 1614 us
                                                   Change since it is defined with respect to per channel. A large value for this p
The value for pMICSNodeEmergencyRetries is too large the value to 2.
See proposed change.                               Change "NB," to "narrow band (NB) PHY, ", "slotted" to "Slotted", and "UW" to
                                                   Replace the entry the MAC subgroup.
The value in the last row was put in (by me) without a discussion atwith the following: ≥ transmit time of a PHY frame with a MA
Formatting glitch.                                 Make the text in the first row bold and centered, and the bottom line bold.
Formatting glitch.                                 Insert a space before and after each plus sign of this table.
                                                   Revise the an equation containing the underlying parameters. (2) This value sh
(1) The value for pAllohaSlotLength should be first given by entry as noted in the comment.
                                                   Replace the entry with the following: ≥ transmit time of a PHY frame with a MA
The value in the last row was put in without a discussion at the MAC subgroup.
Missing introduction to 8.4                        After line 12 add a new paragraph: Support for mandatory and optional cipher
Missing comma.                                     Insert a comma after the closing parenthesis.
                                                   Technical Editor, please make all the to be in italic font.
This comment applies to all the equations in Clause 8. All these math equations needequations (but not the equation numbers
                                                   Remove the underscore in both lines 29 and 30.
An underscore after "P" was artificially added in this rev, resulting in inconsistency with the corresponding figure.
                                                   Remove the underscore in both lines 18 and 19.
An underscore after "P" was artificially added in this rev, resulting in inconsistency with the corresponding figure.
                                                   Remove the underscore in both lines 17 and 18.
An underscore after "P" was artificially added in this rev, resulting in inconsistency with the corresponding figure.
Too crowded.                                       Leave a blank line before line 12.
Too crowded.                                       Leave a blank line before line 22.
                                                   (1) Insert the following secured frames at which conditions.
It has been suggested to explicitly state what frames are transmitted asas the first paragraph of this subclause:Frames shall be
Formatting glitch due to misplaced period.         Delete the space after "97", and move the next line (line 30) back to line 29. F
                                                   the spec. subclause along with Table 45.
SIFS and MIFS are not referenced elsewhere in Delete thisThey are not referenced as pSIFS and pMIFS.
                                                   Technical Editor, would you please decapitalize capitalized, which first letters
These comments apply to many places in Clauses 9-11. Some headings have all the first lettersin the headings the is not consi
Incorrect grammar.                                 Change "media" to "medium".
                                                   Delete "during association".
"during association" -- how and why to enforce this?
                                                   Remove this subclause.
(1) This subclause is out of PHY's scope. (2) "full function devices (FFD)" and "reduced function devices (RFD)" are not define
                                                   Remove this subclause.
(1) This subclause is out of PHY's scope. (2) Item 1 is addressed in the MAC portion. (3) Item 2 is purely imaginary. How can
Which "SAP"?                                       Change "From MAC Via SAP" to "From MAC SAP".
Incorrect statement.                               Change "payload from the MAC via SAP" to "MAC frame".
                                                    payload of 256 "255".
How does the UWB PHY header encode a MACChange "256" tooctets?
                                                    It In line 21 and reference the correct name or ask for consultation.
Incorrect field names in both the text and figure. (1)is advisable to inside Figure 118, change "MAC payload" to "MAC frame bod
                                                   Use a bit in the reduces inter-frame spacing from analogy with 9.3.1.3.
The narrow band PHY supports burst mode transmission which PHR to as a "Burst Mode" field, in SIFS to MIFS. It is advisable
                                                   Remove this sentence
(1) The last statement is out of PHY's scope -- the PHY cannot tell whether it is part of a hub or a node. (2) It is not clear either
                                                   Remove this sentence
Improper language for the standards -- "can be achieved". The statement does not mean anything for interoperability.
                                                   Make "codes" singular.
Only one error detection code, but not multiple codes, is defined at the MAC.
                                                   Make "codes" be defined
Only one invertible code, but not multiple such codes, needs tosingular. for HARQ. In fact, none is defined!
                                                   Remove HARQ altogether without a predefined defined or MAC subgroup at
Where is the invertible code defined? How can interoperability be achievedunless such a code is code? Thereferenced here ha
Incorrectly referenced table number.               This should be Table 62.
                                                   Change "NACK" to "No Ack" in through No Ack at figure throughout
We already explained to the HARQ proposer that NACK for HARQ is supported the text, table, and the MAC level. this subcla
                                                    a In Table 62, delete and a packet containing to 1" to "go to "state 1", and tw
HARQ enabled transmission alternates between(1)packet containing D the last row; change "goP_sub_D. Accordingly, only "g
                                                   Remove HARQ altogether unless the issue is addressed.
How can the transmitter tx D head, which was the received version of D in the 1st column? If this comment is still not clear, ho
Incorrect field name in Figure 139.                Change "MAC Payload" to "MAC Frame Body".



Definition of figure and text is not consistent  Make LSB and MSB definition and transmit order consistent between text and
                                                 Change ―A compliant device … reception in one of the …‖ to ―A compliant devi
Any one band operation is sufficient for compliancy
                                                 ―parameters that is needed‖ to ―parameters that are needed‖
Seed table reference is missing                  bit value and corresponding seed table should be referenced here


                                                   Change MSB and not ordering with LSB to MSB transmission chosen for the
The order of transmission of HCS seems to be MSB to LSB and is LSBconsistentof transmission of HCS
                                                   Specify order
How is the PSDU divided into messages? Transmit order?
                                                   to be transmitted?
first bit of the message – first bit of the messageSpecify what is meant by first bit of message
                                                   Ncw to Ncw = 0
In case of un-coded transmission no need to setRemovezero; (n-k) is anyway zero.
                                                  Redraw figure with appropriate bypass
Bypass should be indicated in case of no spreading for the spreader and bit interleaver.
                                                  Make clear
The bit interleaver is used only for the spread case. This is ambiguous in the document.

                                                   Add description as to how the ambiguous
The first bits coming out of the scrambler to scramble data after initialization is data and the scrambler are clocked or give the s
                                                   – the
the definition is not very clear. Make it more clearer phase for the first transmitted symbol of the PLCP header uses the last s
what is S(0)? Is this the first symbol to be       Make clearer
transmitted of the PLCP preamble?
what is the bit stream – is this the               Clarify
concatenated bit stream?
change to pCCATime shall be the lower of           change to pCCATime shall be the lower of
those specified in Table 44 or by local            those specified in Table 44 or by local
regulatory authorities.                            regulatory authorities.
Channel BW is not specified in Table 48.           Replace "Table 48" with "Table 46"
Wrong reference                                    Change "Table 50" to "Table 48."
Why is it PER < 10%: Should be PER ≤10%.           Change ―less than‖ to "less than or equal to"
                                                   before 10%.
The minimum sensitivity numbers can be lower Use shall be at most or lower than the
than the numbers listed in Table 49.               numbers in Table 49.
ED Threshold should be defined as 10 dB            Modify first bullet to say "10 dB above the
above the minimum receiver sensitity, which        minimum specified receiver sensitivity (see
corresponds to the lowest data rate                9.8.1) OR"
"physical layer convergence procedure"             Use the same terminology
(PLCP). But in Acronyms section, PLCP stands
for "physical layer convergence protocol"

Acronym SHR is not well defined                   Synchronization Header (SHR)?, also put it in
                                                  Acronyms section
The statement on CCA looks different from         Make clear on CCA.
what is stated in Sec 10.18. This sentence
says CCA provided by PHY, but Sec 10.18
says slotted-Aloha shall be used.
Some of items (lines 18 to 24) are not aligned    Align the items in line 18 to 24 to the main
to the later sections. E.g., "one mandatory       sections
modulation", but in Sec 10.11 two modulation
schemes are specified, and which modulation
scheme is mandatory is not clear.

"high QoS mode" is not defined at all.            Define clearly what the "high QoS mode"
                                                  means
"high QoS mode" is not defined at all.            Define clearly "high QoS mode" means and
                                                  "applications with high QoS mode"
"transmit" is too narrow in meaning in the        "transmit" --> "operate"
sentence "A compliant UWB device shall
transmit in at least one of the specified band
groups."
Reference is not correct                          "table 10" --> "table 61"
The sentence "A combination of on-off            Modify the sentence to avoid any confusion.
signaling (on-off modulation with 64-ary
waveform coding) and differentially encoded
binary/quaternary phase shift keying
modulation schemes are used to support non-
coherent and differently coherent transceivers."
is not clear. Two PHY modes are not combined
in any way, they are separated.

What is "the default mode"? "High QoS mode" Define "default mode" and "high QoS mode". In
is also not defined.                            my opinion, all the modes should be all
                                                "optional". It is not logical to specify a certain
                                                PHY mode as mandatory considering there are
                                                multiple UWB PHY modulations as well as
                                                multiple pulse waveforms are specified in the
                                                specification.
Why should FEC be optional during               FEC should be also employed as mandatory
association (beacon transmission)? Beacon       for beacon transmission.
should be robust and well protected using
FEC.
FFD and RFD are not clearly defined. Does       Make RFD and FFD clear in definition. Clearly
FFD means a coordinator, and does RFD           state what "IR-UWB PHY" means, maybe
means a node device? It is not mentioned what mentioning what are addressed in Sec 10.11.3
"IR-UWB PHY" include?                           and 10.11.4.
Figure 116 needs to be revised.                 Revise figure 116: refer to narrowband PHY,
                                                adding length information, and etc.
Figure 116: "S_0" is not defined anywhere in    Defined SFD signal structure.
the text.
"length of the payload" is not exactly correct. "length of the payload" --> "length of MAC
                                                frame body"
The terminology "error detection parity bits    Use "header check sequence (HCS)" as in
CRC-4-ITU" would is better to be aligned with narrowband PHY.
narrowband PHY
The preamble part of SHR are intended more Also include packet detection, timing
than just coarse timing.                        synchronization, and carrier frequency offset
                                                recovery.
Figure 117 does not include all the PHY         Figure 117 should be revised to include all the
operations.                                     PHY layer operations which include
                                                scrambling, FEC, interleaving, symbol
                                                mapping, (spreading) and modulation.
"MAC payload (0-256 octets)" is not correct.    It should be "MAC frame body (0-255 octets)"

The terminology "CRC-16-ITU" would is better Use "frame check sequence (FCS)" as in
to be aligned with narrowband PHY            narrowband PHY
Figure 118: need to revise the figure.       Use correct terminologies "MAC frame body",
                                             and "FCS", and add length information to each
                                             portion.
First sentence needs to be revised           E.g., "Data whitening technique shall be
                                             applied using a bit scrambling ..."
"initialization vector (sync-word), xinit"   "sync-word" --> "scrambler word", "xinit" -->
                                             "x_init" ("init" in subscript)
The sentence, "The sync-words are placed in        Remove the sentence
the data stream through equal intervals, i.e.,
each frame." is not clear.
Scrambler section could be aligned to              Refer to the latest scrambler section in the
narrowband PHY                                     narrowband PHY
The bit order is not matched to what is            Align the text and the figure. Probably the
presented in Figure 120.                           current text is correct and just revise Figure
                                                   120, or simply remove Figure 120.
"In the case of un-coded transmission, N_CW        If not, just remove the sentence
is set to zero." is there any un-coded
transmission?
The sentence "A binary labeling function that      This is not mentioned so far, so need to modify
maps blocks of bits to signal constellation        the sentence.
symbols is already defined by the non-coherent
modulation."
Equation 75: "n" and "PI(n)" are not clearly    Maybe "n" and "PI(n)" are indices to the
defined. Generally functionality of bit         scrambled, encoded, zero-padded (if
interleaver is not clear: e.g., what is range ofnecessary) bits before and after bit interleaver,
n? Maybe n = 0, 1, ... N_I-1. Is it basically a maybe in each 64-bit block. Need to clearly
block interleaver?                              specify the functionality of bit interleaver in this
                                                section.
The PHY header (PHR) is 31 bits in length       Modify the PHR structure to one of the
based on the BCH (31,19) code, and is not       followings: 1) PHR information is reduced to 14
compatible with the non-coherent UWB PHY        bits and apply BCH (30,18) to have PHR of
mode (Sec 10.11.3). More specifically, the      length 30 bits. 14-bit PHR information forms as
length of the PHR (31 bits) is not aligned to a follows -- data rate (bit 0-2), MAC frame body
symbol boundary of group PPM (GPPM). The length (bit 3-10), HARQ (bit 11-12). Scrambler
symbol mapping of the GPPM is defined as 6 seed (bit 13). 2) PHR information is 20 bits and
bits which are mapped onto 12 bits (or 1        apply BCH (36,24) to have PHR of length 36
symbol). Thus, a symbol consists of 12 bits     bits. 20-bit PHR information forms as follows --
and the number of information must be a         data rate (bit 0-2), reserved (bit 3), MAC frame
multiple of 6 bits. Since the PLCP header is of body length (bit 4-11), reserved (bit 12-13),
length 31 bits, the last GPPM symbol would      HARQ (bit 14-15), reserved (bit 16), scrambler
consist of 1 bit and 5 zero or pad bits. The 5  seed (bit 17), reserved (bit 18-19).
zero or pad bits contains no information and is
just overhead.

Terminologies could be aligned to narrowband "PLCP header" consists of "PHY header",
PHY                                               "header check sequence (HCS)", and "BCH
                                                  parity bits"
Figure 121: needs to revise                       Use the consistent terminologies: "PLCP
                                                  header" = "PHY header" + "header check
                                                  sequence (HCS)" + "BCH parity bits". Include
                                                  also length information of each field.
Notations (L_1, ..., L_7) are not consistent with Use the same notations in the text and the
Table 52.                                         table.
"synch-word" looks not correct.                   "Scrambler seed" may be a better terminology.

Title "CRC-4-ITU"                                  Change the subsection title to "Header Check
                                                   Sequence *(HCS)"
Terminology "shortened BCH(31,19) encoder" Use "BCH (31,19) encoder" and add a
does not look correct.                     comment like "BCH (31, 19) code is a
                                           shortened code derived from a BCH (63, 51)
                                           code."
Need to revise the sentence. E.g., "SHR is Revise the sentence, and also include more
formed by the preamble..." can be better   receiver functionalities that can do with the
stated.                                    SHR: packet detection, timing synchronization,
                                           and carrier frequency offset recovery.

It is not clear how the 8 preamble sequences     Make it clear how the preamble codes are
are assigned: all 8 can be assigned to each      assigned to frequency band. A good way is
channel. Then later say the 8 sequences shall    what is stated in line 8-10, but need to more
be divided into two pools.                       details: e.g., C_1, to C_4 are used in each of
                                                 odd-numbered channels, and C_5 to C_8 are
                                                 used in each of even-numbered channels.

The sentence "Notice that Kasami sequences       Remove the sentence
are binary and in Table 53, -1 was replaced by
0" is not necessary.
N_sync = 4 is not large enough to accomplish     Find the optimized repetition number (N_sync)
all the necessary assessment, acquisition, and   considering all the receiver functionalities and
estimation at the receiver.                      procedures, and detailed simulation study.

Incorrect reference "table 50"                   "table 50" --> "table 53"
Figure 123 needs to be revised.                  Use the same font and include length
                                                 information, and etc.
"0"??                                            Correct the reference
No detail is specified on SFD.                   Specify the SFD signal structure? Also check if
                                                 it is aligned to Figure 116.
Data rate range (0.5 Mbps up to 10 Mbps) is      Use the exact date rate in the tables.
not exactly matched to Table 54 and 55.
Table 54: Timing and data rate related         Timing and data rate related parameters
parameters should be able to be derived by a   should be revised using integer multiples of
simple hardware from basic clock.              basic clock (chip time of short pulse),
                                               1/499.2MHz = 2.003205 ns. For example,
                                               T_sym = 2015.28 for the mandatory data rate
                                               (but currently 2048 ns).
Table 55: Timing and data rate related         Timing and data rate related parameters
parameters should be able to be derived by a should be revised using integer multiples of
simple hardware from basic clock.              basic clock (chip time of short pulse),
                                               1/499.2MHz = 2.003205 ns. For example,
                                               T_sym = 2015.28 for the mandatory data rate
                                               (but currently 2048 ns).
Table 54:unit should be in parenthesis         "nsec" should be with parenthesis
Table 55:unit should be in parenthesis         "nsec" should be with parenthesis
Table 54: last two rows should be indicated as Last two rows should be indicated as
"reserved" also in the text.                   "reserved" also in the text.
Table 55: What does "Modul. Mode 2" means "Modul. Mode 2" --> "Modulation"
in the table?
Table 55: What does "Spr." means in the        "Spr." --> "Spreading factor" or use math
table?                                         symbol, e.g., "S" and define in the text.
Adding a reference to time hopping would be       Add a reference section (Sec 10.11.2) next to
better.                                           the text "time hopping".
Not clear which column in Table 55 it is          Add the same terminology or math symbol
referring.                                        used in the Table 55 in the text.
What does "Modulation mode 2" means?              Use a general terminology, e.g., "Modulation"

"R_b = R_s . FECrate": "FECrate" first appears Revise the math expression with clear
here with no definition.                       definition.
Short pulse duration is not exactly 2ns.       Short pulse duration is 1/499.2MHz which
                                               approximately 2ns, but not exactly 2ns. All the
                                               timing-related parameters including T_w and
                                               T_sym should be integer multiples of chip time,
                                               T_c = 1/499.2MHz, which is slightly greater
                                               than 2ns.
Need to revise the sentence to better express Suggested sentence: "N_guard parameter is
the parameter.                                 used in time-hopping sequence generation
                                               (see Sec. 10.11.2). Time-hopping sequence
                                               with N_guard guarantees at least T_w N_guard
                                               of separation between the waveforms for the
                                               two consecutive symbols to avoid inter-symbol-
                                               interference." And remove "ceil{ tau_max /
                                               T_w}" since it will be mentioned in time-
                                               hopping sequence section.

Static chip-level scrambling specified in the     Apply dynamic scrambling specified in Section
section is using a fixed scrambling sequence      10.11.1.1 as mandatory in all the cases.
repeatedly in each symbol, which creates          Alternative solution could be using dynamic
severe spectral lines in the transmit spectrum.   scrambling in the noncoherent mode, and
Need to check link budget analysis by taking      static scrambling in the differentially coherent
necessary backoff that is required by static      mode (since higher link margin is expected).
scrambling into account. High/medium date
rates very likely have issues with the transmit
power backoff (to meet the spectral mask) that
would be required by static scrambling.

Not clear how this sequence s_n is used in the    Make it clear how this sequence s_n is used in
math expression for modulation output, e.g.,      the math expression for modulation output,
Eq (86). The fact that the sequence is repeated   e.g., Eq (86).
in each symbol is not shown.
Table 57: Preamble code number runs 0 to 7 is     Modify the preamble code number column so
not aligned to Sec 10.7.                          that it runs 1 to 8.
These lines are not necessary to put. N_guard     Just remove the lines 12 - 15 to avoid any
is "not computed on the fly", but is fixed for    confusion.
each data rate as shown in data rate tables
(Table 54, 55).
The hyphen before "where..." is not necessary.    Remove the unnecessary hyphen before
                                                  "where...".
Eq (81): superscript k-1 should be m-1            Eq (81): superscript k-1 should be m-1.
Need to add range of "k" and initial parameter    Add "k >= 0" and initial value for time-hopping
for time-hopping sequence.                        sequence "h^{(k-1)} = 0".
Non-coherent modulation requires two                Add a new PHY UWB mode that is based on
decoders at the receivers, one for the 64-ary       BCH and binary PPM, which requires only one
waveform-coding (aka GPPM), and the other           FEC decoder at the receiver and allows low-
for the BCH (63,51) code. One FEC is                power and low-complexity transceivers. This
sufficient enough to meet all the technical         mode will allow reusing already-existing
requirements. Why we need two FECs??                designs for many chip venders. One way to
Considering low-complexity and low-power are        add the simple binary PPM mode is that we
the most important in most BAN applications,        just keep the current symbol mapping structure
the requirement for two FECs is definitely not      of non-coherent modulation (Sec 10.11.3) but
good.                                               add a new codebook for binary PPM.

Figure 126: reference to symbol mapper is not       Use the correct reference (Sec 10.11.3.1).
correct. Receiver chain is not necessary to         Remove the receiver chain in Figure 126.
show in the figure.
The sentence is not grammatically correct.          Revise the sentence.
Eq (85): d_n^m is not defined (note notation        1) Define d_n^m, 2) Use the same notation for
d_k is used on the Table 58). Notation h_m^k        time-hopping sequence as in the Sec 10.11.2:
for time-hopping sequence is not aligned to         it should be "h^{(11m+n)}" , 3) add "T_w" after
what is used in Sec 10.11.2. And T_w is             time-hopping sequence "h^{(11m+n)}". Note "k-
missing.                                            th BAN" is not expressed explicitly. Accordingly
                                                    remove "k-th BAN" in line 9.

"m" and "T_sym" are repeated. "h_m^k" should        Delete redundant "m" and "T_sym" images.
be "h^{(11m+n)}"                                    "h_m^k" should "h^{(11m+n)}"
Eq (86): better to use the index "i" running from   Modify the Eq using "i" running from 0 to
0 for concise math expression.                      N_cpb -1 for concise math expression.
This section is not necessary since it is           Just remove the Section.
implementation dependent.
Figure 127: references to symbol mapper and         Use the correct references (Sec 10.11.4.1 and
pulse shaping are not correct. Receiver chain       10.11.4.2). Remove the receiver chain figure
is not necessary to show in the figure.             127.
Table 59 title needs a correction.                  "DBSK" --> "DBPSK"

                                                  1) Use the what is used for time-hopping sequence as in the
Notation h_m^k for time-hopping sequence is not aligned tosame notationin Sec 10.11.2. And T_w is missing. Sec 10.11.2: it s
                                                  Modify the Eq using "i" running
Eq (89): better to use the index "i" running from 0 for concise math expression. from 0 to N_cpb -1 for concise math expression

                                                Find a should be explicitly specified.
"Seq_m" is not the best notation. Also Barker sequenceconcise notation for "Seq_m". Specify the Barker sequence clearly.
Title is not very relevant to the table.        Use a better title, e.g., "Operating frequency bands for UWB PHY"
"The implementer is free to choose the
truncation of r(t)." is not very logical.
Remember "r(t)" is reference pulse for the      Just remove the sentence "The implementer is
pulse criterion.                                free to choose the truncation of r(t)."
Figure 129 is not necessary.                    Remove Figure 129.
Chaotic pulse waveform is not specified in
detail.                                         Add detail specification for chaotic pulse.
Only BCH code is use on UWB PHY. So not
necessary to mention a general term like
"invertible code".                              Just specify for the case of BCH code.
Reference "6.2.3" is correct??                  Use the correct reference.

                                           Just specify for the case of BCH like
Only BCH code is use on UWB PHY. So not necessary to mention a general termcode."invertible code".
Reference "table 11" is correct?           Use the correct reference.
                                                   What are the
Table 62: What are the "1" and "2" in the "Rx Action" column? "1" and "2" in the "Rx Action" column?
                                                   Just So not necessary to mention a general term like "invertible code".
Figure 135 title: Only BCH code is use on UWB PHY.specify for the case of BCH code.
"BRF"?                                             "BRF" --> "B_RF"
Table 64 is not referred in the text               Table 64 is not referred in the text
Eq (102): What is M(w_m t)?                        Specify M(w_m t) more explicitly with mathematical expression.
                                                   Just remove dependent.
This section is not necessary to put since it is implementationthe Section.

                                                 Is Slotted aloha no need to If yes, then no need to mention other CCA options
This section is not clear. Is Slotted aloha mandatory? If yes, thenmandatory? mention other CCA options (energy detection or pr

                                               Unless main authors participate attend all to build a transmitter, let alone dram
HBC text is not close to being complete, many missing sections and technically impossiblefuture meetings, and commit to a rec

                                               Insert a section that defines the operating frequency bands
A section on operating frequency bands is missing

A section on channel numbering is missing         Insert a section that defines the channel numbers and center frequencies

                                               Insert a EDTime, CCATime, Channel Switch Time, etc.)
A section on PHY layer timing is missing (pSIFS, pMIFS,section that defines the PHY layer timing

                                                Insert a etc.)
A section on inter-frame spacing is missing (SIFS, MIFS,section that defines the inter-frame spacing

                                                  Insert sections on rx-to-tx, tx-to-rx turnaround times
Sections on rx-to-tx, tx-to-rx turnaround times are missing

                                                 Insert
A section of center frequency switch time is missing a section on center frequency switch time

                                                Insert sections on is missing
Sections on transmit center and symbol clock frequency tolerancestransmit center and symbol clock frequency tolerances

                                                  is missing
Section of transmitter constellation error or EVMInsert a section on transmitter constellation error or EVM

                                                Insert
A section on adjacent channel power ratio is missing a section on adjacent channel power ratio

                                                 Insert a section on adjacent channel rejection
A section on adjacent channel rejection is missing

                                               Add ED measurement time and receiver clear channel assessment are missin
Sections on receiver energy detection, ED threshold, seections on receiver energy detection, ED threshold, ED measurement ti
                                               Pick either HBC or to the reader
HBC and EFC are used interchangeably and this leads to confusionEFC and use it consistently throughout spec. Preference is
                                               Remove the paragraph altogether
This paragraph assumes a particular implementation, which should not be included in a standards

Change bandwidth is 8 MHz, not 4 MHz             Replace "with the bandwidth of 4MHz" by "with the bandwidth of 8MHz"
The header should be referred to as a PLCP HeaderReplace "Header" with "PLCP Header"
                                                 Remove
PHY Payload is not a typical term in IEEE 802 standards PHY Payload and just replace it with PSDU
Shouldn‘t used "And" to start a sentence         Replace "And PHY Payload" with "The PSDU"
Grammar is awkward                               Replace "The packet structure with PHY Header fields is shown …" with "The P
Figure 139 is not correct                        Replace PHY Header with PLCP Header, and PHY Payload with PSDU and sh
HBC has not been approved in any countries change "many" to "any"
                                                 Remove last part of sentence: "and transmitted value
Aren't the signal transmitted actually analog? The last part of sentence is confusing and adds noin digital form"
                                                 the dominant frequency? What
Don‘t understand the second sentence. What is Clarify by rewritting sentence does it mean? What does it mean to say "most
Grammar is awkward                               Need to insert a "the" between "Since" and "preamble"
Figure 142, what is f_ck?                         Define the values for f_ck
Typo: fCK                                         Replace with f_ck
                                             Please clarify. Can't built a transmitter unless it is known how to is the the Gold
How are the various preambles selected? How do you select which Gold Code polynomial? Who does selection, select PHY ba
                                               Please section
Paragraph is very confusing and hard to understand thisrewrite to clarify
                                                  Remove paragraph, Figure 143
This text doesn't belong in a standard. This text belongs in an academic paper and last line after figure

Figure 144, what is f_ck?                           Define the values for f_ck

                                             Please clarify. Can't built a transmitter unless it is parameter? Or is it the MAC?
How do you select which Gold Code polynomial? Who does selection, is the PHY based on some known how to select the Gold
Reference is missing                                Replace "0" with "Table 70"?
What is DRF?                                        Define DRF. Also define how DRF is selected? Who makes decision PHY or M

Is spreading factor 64 for this section? Why?       Clarify

Is Table 71 for DRF or RI? It is not clear?         Clarify

                                                 Bits should be mapped
How are bits in table mapped to the fields? Is LSB first? Or MSB first? LSB first
                                                      Replace "3 ~ 4" with "3 ~ 5"
Bit position 3 ~ 4 is only 2 bits, but 3 bits are defined
"-" doesn't imply reserved                            Replace "-" with "Reserved"
                                                 "no 01 for
Why are two bit values for sync (00,01) used for Use sync"? no sync and 00 for a Reserved value

                                              Clarify
What is difference between normal and dedicated mode? Why is it needed? Who makes decision (PHY or MAC) to use norma

                                              Clarify
Why are there 3 bits used for BAN ID? How are the BAN ID assigned? Does this mean that 8 simultaneously operating piconet

CRC8 is undefined                                   Please specify the CRC8 polynomial and how it is implemented

                                                Replace "master device and be more generic
Why does this field need to be specified for master and slave devices, shouldslave nodes" with "two devices"
"1x" notation is confusing                          Replace "is set to 1x" with "has a one in the first bit of the field"
                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                                     Specify
What happens if the first bit is set to zero (i.e. no-sync)? text for the condition when the first bit is zero (i.e. no sync)

                                                Replace "master device and particular slave
Why does this field need to be specified for master and slave devices, shouldabe more generic device" with "two devices"

What does 1:1 mean?                                 Explain and clarify

                                            Remore the dedicated device be section 11.6.2
Why is a dedicated mode needed? This is a TDD system, why would a mode and communicating at the same time as another d

                                             Define
What is C, N and L? These values should be specified C, N and L and their values

                                               Define the
What is FSC for this section? What values can be used? FSC values

C, N and L should be defined in Table 73            Define C, N and L in Table 73

Where was Data Rate Field (DRF) defined?            Please define DRF or reference section where DRF was defined

                                           Please clarify or PHY HDR structure for DRP mode and for RI mode
When is RI used? How is PHY HDR modified when RI is used thedoes it remain the same?

"garbage bits" is a terrible term                   Please replace "garbage bits" with something better, like "RI bits"
                                             Please specify how How "garbage bits" are used in T_offset
Figure 147, how many "garbage bits" proceed SFD code T_offset1? manymany before T_offset2? ... How many before T_offse

                                               Please clarify
Need more detail in last sentence. How does a device know that an SFD/RI is being used or an SFD/DRF is being used. Once

                                               Please clarify
Which SFD sequence is used for the pilots? Is the SFD/DRF or SFD/RI? Does it include "garbage bits"
Bit pattern 111 is missing from Table 75           Define bit pattern 111 as Reserved
                                                  Please clarify
What if bit pattern 011 is selected but the payload is less than 128 bytes, do you still insert the pilot pattern?

Typo: fBW                                          Replace "fBW" with "f_BW"

What is the value of f_BW?                         Clarify that f_BW = 8 MHz


                                                    Please replace this TG6. The correct figure can which should have a value of
Figure 149 is incorrect. This is not from the text that was adopted byfigure with the correct figure, be found in document 15-10-2

                                                Update text and found
Text should be updated to match the correct figure, which can befigure in document 15-10-201-02, where the limits should be

                                              Current mask
Where is the TX mask for a center frequency f_c = 27 MHz only works for f_c = 16 MHz and not f_c = 27 MHz. Please upda

                                               or equal to a maximum, not -12 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -12 dBm"

                                               or equal to a maximum, not -39 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -39 dBm"

                                                Please state all clock frequencies that can be used with this chapter
Is the clock frequency 64 MHz for this chapter? Or is it some other number?

                                                  Please means or update numbers refer to and how they should be
Table 77 is confusing. I don't understand what the table clarify andwhat thetable with additional text to improve clarity used in de
                                                  Editor please pick either octet or byte and stick with it throughout document
In some places octets are used, in other places bytes are used
                                                   not just less than
PER is usually specified as less than or equal to,Replace "lessthan 1%" by "less than equal to 1%"

                                                 Update sensitivity = -11 dB with correct numbers. Proponents should bring a lin
Table 79 - sensitivity numbers are way too low, they imply an SNR numbers for the modulation scheme, which does not include



Definition of figure and text is not consistent    Make LSB and MSB definition and transmit order consistent between text and

                                                 Change ―A compliant device … reception in one of the …‖ to ―A compliant devi
Any one band operation is sufficient for compliancy

                                                   ―parameters that is needed‖ to ―parameters that are needed‖

Seed table reference is missing                    bit value and corresponding seed table should be referenced here


                                             Change MSB and not ordering with LSB to MSB transmission chosen for the
The order of transmission of HCS seems to be MSB to LSB and is LSBconsistentof transmission of HCS

                                            Specify order
How is the PSDU divided into messages? Transmit order?

                                                   to be transmitted?
first bit of the message – first bit of the messageSpecify what is meant by first bit of message

                                               Ncw to Ncw = 0
In case of un-coded transmission no need to setRemovezero; (n-k) is anyway zero.

                                               Redraw figure with appropriate bypass
Bypass should be indicated in case of no spreading for the spreader and bit interleaver.
                                                  Make clear
The bit interleaver is used only for the spread case. This is ambiguous in the document.

                                                  Add description as to how the ambiguous
The first bits coming out of the scrambler to scramble data after initialization is data and the scrambler are clocked or give the s

                                                   – the
the definition is not very clear. Make it more clearer phase for the first transmitted symbol of the PLCP header uses the last s

                                                   Make clearer
what is S(0)? Is this the first symbol to be transmitted of the PLCP preamble?

                                                  bit stream?
what is the bit stream – is this the concatenated Clarify

                                               specified pCCATime shall local regulatory authorities.
change to pCCATime shall be the lower of thosechange to in Table 44 or by be the lower of those specified in Table 44 or by loc

Channel BW is not specified in Table 48.          Replace "Table 48" with "Table 46"

Wrong reference                                   Change "Table 50" to "Table 48."

Why is it PER < 10%: Should be PER ≤10%.          Change ―less than‖ to "less than or equal to" before 10%.

                                              Use shall be at most or lower than the
The minimum sensitivity numbers can be lower than the numbers listed in Table 49. numbers in Table 49.

                                              the minimum receiver "10 dB above corresponds to the lowest data rate
ED Threshold should be defined as 10 dB aboveModify first bullet to saysensitity, whichthe minimum specified receiver sensitivi

                                              But the same terminology
"physical layer convergence procedure" (PLCP).Use in Acronyms section, PLCP stands for "physical layer convergence protoco

Acronym SHR is not well defined                   Synchronization Header (SHR)?, also put it in Acronyms section

                                              is stated in Sec 10.18. This sentence says CCA provided by PHY, but Sec 10.
The statement on CCA looks different from whatMake clear on CCA.

                                                 the later items in E.g., to 24 to the main sections
Some of items (lines 18 to 24) are not aligned toAlign the sections.line 18"one mandatory modulation", but in Sec 10.11 two mod

"high QoS mode" is not defined at all.            Define clearly what the "high QoS mode" means

"high QoS mode" is not defined at all.            Define clearly "high QoS mode" means and "applications with high QoS mode"

                                                 "transmit" --> "operate"
"transmit" is too narrow in meaning in the sentence "A compliant UWB device shall transmit in at least one of the specified band

Reference is not correct                          "table 10" --> "table 61"

                                                (on-off modulation with 64-ary waveform coding) and differentially encoded bin
The sentence "A combination of on-off signaling Modify the sentence to avoid any confusion.

                                               also not defined.
What is "the default mode"? "High QoS mode" isDefine "default mode" and "high QoS mode". In my opinion, all the modes shou

                                              FEC should be also employed as mandatory for beacon transmission.
Why should FEC be optional during association (beacon transmission)? Beacon should be robust and well protected using FEC

                                             means a coordinator, and does RFD means a node device? It is not mentione
FFD and RFD are not clearly defined. Does FFDMake RFD and FFD clear in definition. Clearly state what "IR-UWB PHY" mean

Figure 116 needs to be revised.                   Revise figure 116: refer to narrowband PHY, adding length information, and etc

                                                text.
Figure 116: "S_0" is not defined anywhere in theDefined SFD signal structure.

"length of the payload" is not exactly correct.   "length of the payload" --> "length of MAC frame body"
                                                Use "header is better to be aligned with narrowband PHY
The terminology "error detection parity bits CRC-4-ITU" wouldcheck sequence (HCS)" as in narrowband PHY.

                                             Also include packet detection, timing synchronization, and carrier frequency off
The preamble part of SHR are intended more than just coarse timing.

                                                Figure 117 should be revised to include all the PHY layer operations which incl
Figure 117 does not include all the PHY operations.

"MAC payload (0-256 octets)" is not correct.       It should be "MAC frame body (0-255 octets)"

                                               Use "frame with narrowband PHY
The terminology "CRC-16-ITU" would is better to be aligned check sequence (FCS)" as in narrowband PHY

Figure 118: need to revise the figure.             Use correct terminologies "MAC frame body", and "FCS", and add length inform

First sentence needs to be revised                 E.g., "Data whitening technique shall be applied using a bit scrambling ..."

"initialization vector (sync-word), xinit"         "sync-word" --> "scrambler word", "xinit" --> "x_init" ("init" in subscript)

                                              Remove the sentence
The sentence, "The sync-words are placed in the data stream through equal intervals, i.e., each frame." is not clear.

                                              Refer to
Scrambler section could be aligned to narrowband PHY the latest scrambler section in the narrowband PHY

                                                Align the text and
The bit order is not matched to what is presented in Figure 120. the figure. Probably the current text is correct and just revise

                                                set to zero." is there any un-coded transmission?
"In the case of un-coded transmission, N_CW is If not, just remove the sentence

                                                This is not mentioned so constellation modify is sentence.
The sentence "A binary labeling function that maps blocks of bits to signalfar, so need tosymbolsthealready defined by the non-c

                                                  Maybe "n" and "PI(n)" are indices to the scrambled, encoded, zero-padded (if n
Equation 75: "n" and "PI(n)" are not clearly defined. Generally functionality of bit interleaver is not clear: e.g., what is range of n?

                                              Modify the PHR structure to one of the followings: 1) PHR non-coherent reduce
The PHY header (PHR) is 31 bits in length based on the BCH (31,19) code, and is not compatible with the information is UWB

                                              "PLCP header" consists of "PHY header", "header check sequence (HCS)", an
Terminologies could be aligned to narrowband PHY

Figure 121: needs to revise                        Use the consistent terminologies: "PLCP header" = "PHY header" + "header c

                                                   Use 52.
Notations (L_1, ..., L_7) are not consistent with Tablethe same notations in the text and the table.

"synch-word" looks not correct.                    "Scrambler seed" may be a better terminology.

Title "CRC-4-ITU"                                  Change the subsection title to "Header Check Sequence *(HCS)"

                                            Use "BCH (31,19) encoder" and add a comment like "BCH (31, 19) code is a s
Terminology "shortened BCH(31,19) encoder" does not look correct.

                                               Revise the sentence, can be better stated.
Need to revise the sentence. E.g., "SHR is formed by the preamble..." and also include more receiver functionalities that can do

                                                Make it clear 8 can be assigned to each channel. Then later say the 8 A good
It is not clear how the 8 preamble sequences are assigned: allhow the preamble codes are assigned to frequency band. sequen

                                             Remove the in Table
The sentence "Notice that Kasami sequences are binary and sentence53, -1 was replaced by 0" is not necessary.

                                                 the the optimized repetition acquisition, and estimation at all receiver.
N_sync = 4 is not large enough to accomplish allFind necessary assessment, number (N_sync) considering the the receiver func

Incorrect reference "table 50"                     "table 50" --> "table 53"
Figure 123 needs to be revised.                  Use the same font and include length information, and etc.

"0"??                                            Correct the reference

No detail is specified on SFD.                   Specify the SFD signal structure? Also check if it is aligned to Figure 116.

                                                exactly exact date Table the tables.
Data rate range (0.5 Mbps up to 10 Mbps) is not Use the matched to rate in 54 and 55.

                                               Timing and data rate related parameters should be revised using integer
Table 54: Timing and data rate related parameters should be able to be derived by a simple hardware from basic clock. multip

                                               Timing and data rate related parameters should be revised using integer
Table 55: Timing and data rate related parameters should be able to be derived by a simple hardware from basic clock. multip

Table 54:unit should be in parenthesis           "nsec" should be with parenthesis

Table 55:unit should be in parenthesis           "nsec" should be with parenthesis

                                                 Last two also should be
Table 54: last two rows should be indicated as "reserved"rows in the text.indicated as "reserved" also in the text.

                                             the table?
Table 55: What does "Modul. Mode 2" means in "Modul. Mode 2" --> "Modulation"

Table 55: What does "Spr." means in the table? "Spr." --> "Spreading factor" or use math symbol, e.g., "S" and define in the tex

                                              Add
Adding a reference to time hopping would be better. a reference section (Sec 10.11.2) next to the text "time hopping".

                                                  A
Not clear which column in Table 55 it is referring. dd the same terminology or math symbol used in the Table 55 in the text.

What does "Modulation mode 2" means?             Use a general terminology, e.g., "Modulation"

                                               Revise the definition.
"R_b = R_s . FECrate": "FECrate" first appears here with nomath expression with clear definition.

Short pulse duration is not exactly 2ns.         Short pulse duration is 1/499.2MHz which approximately 2ns, but not exactly 2

                                                Suggested sentence: "N_guard parameter is used in time-hopping sequence g
Need to revise the sentence to better express the parameter.

                                                   Apply dynamic scrambling specified in Section 10.11.1.1 as mandatory in crea
Static chip-level scrambling specified in the section is using a fixed scrambling sequence repeatedly in each symbol, whichall th

                                                Make it clear how this sequence s_n is used in the math fact that the sequence
Not clear how this sequence s_n is used in the math expression for modulation output, e.g., Eq (86). The expression for modula

                                              Modify the to Sec 10.7.
Table 57: Preamble code number runs 0 to 7 is not aligned preamble code number column so that it runs 1 to 8.

                                                 "not computed lines fly", but is fixed for confusion.
These lines are not necessary to put. N_guard isJust remove theon the12 - 15 to avoid any each data rate as shown in data rate

The hyphen before "where..." is not necessary. Remove the unnecessary hyphen before "where...".

Eq (81): superscript k-1 should be m-1           Eq (81): superscript k-1 should be m-1.

                                                 Add "k >= 0" and initial value for time-hopping sequence "h^{(k-1)} = 0".
Need to add range of "k" and initial parameter for time-hopping sequence.

                                             at the receivers, one mode 64-ary waveform-coding binary PPM, which requ
Non-coherent modulation requires two decodersAdd a new PHY UWBfor thethat is based on BCH and(aka GPPM), and the ot

                                               Use the correct chain is not necessary to Remove the receiver chain in Figure
Figure 126: reference to symbol mapper is not correct. Receiver reference (Sec 10.11.3.1).show in the figure.
The sentence is not grammatically correct.        Revise the sentence.

                                                is used on the Table 58). Notation h_m^k for time-hopping sequence is not th
Eq (85): d_n^m is not defined (note notation d_k1) Define d_n^m, 2) Use the same notation for time-hopping sequence as inali

                                             Delete redundant
"m" and "T_sym" are repeated. "h_m^k" should be "h^{(11m+n)}" "m" and "T_sym" images. "h_m^k" should "h^{(11m+n)}"

                                                  Modify the Eq using "i" running
Eq (86): better to use the index "i" running from 0 for concise math expression. from 0 to N_cpb -1 for concise math expression

                                                 Just remove the Section.
This section is not necessary since it is implementation dependent.

                                             Use the correct not correct. Receiver chain is 10.11.4.2). Remove the the figu
Figure 127: references to symbol mapper and pulse shaping arereferences (Sec 10.11.4.1 andnot necessary to show in receive

Table 59 title needs a correction.                "DBSK" --> "DBPSK"

                                              1) Use the what is used for time-hopping sequence as in the
Notation h_m^k for time-hopping sequence is not aligned tosame notationin Sec 10.11.2. And T_w is missing. Sec 10.11.2: it s

                                                  Modify the Eq using "i" running
Eq (89): better to use the index "i" running from 0 for concise math expression. from 0 to N_cpb -1 for concise math expression

                                                Find a should be explicitly specified.
"Seq_m" is not the best notation. Also Barker sequenceconcise notation for "Seq_m". Specify the Barker sequence clearly.

Title is not very relevant to the table.          Use a better title, e.g., "Operating frequency bands for UWB PHY"

                                                Just remove the sentence "The implementer is free to choose for the pulse of
"The implementer is free to choose the truncation of r(t)." is not very logical. Remember "r(t)" is reference pulsethe truncation cr

Figure 129 is not necessary.                      Remove Figure 129.

                                                 A
Chaotic pulse waveform is not specified in detail. dd detail specification for chaotic pulse.

                                           Just specify for the case of BCH like
Only BCH code is use on UWB PHY. So not necessary to mention a general termcode."invertible code".

Reference "6.2.3" is correct??                    Use the correct reference.

                                           Just specify for the case of BCH like
Only BCH code is use on UWB PHY. So not necessary to mention a general termcode."invertible code".

Reference "table 11" is correct?                  Use the correct reference.

                                                What are the
Table 62: What are the "1" and "2" in the "Rx Action" column? "1" and "2" in the "Rx Action" column?

                                              Just So not necessary to mention a general term like "invertible code".
Figure 135 title: Only BCH code is use on UWB PHY.specify for the case of BCH code.

"BRF"?                                            "BRF" --> "B_RF"

Table 64 is not referred in the text              Table 64 is not referred in the text

Eq (102): What is M(w_m t)?                       Specify M(w_m t) more explicitly with mathematical expression.

                                                   Just remove dependent.
This section is not necessary to put since it is implementationthe Section.

                                                 Is Slotted aloha no need to If yes, then no need to mention other CCA options
This section is not clear. Is Slotted aloha mandatory? If yes, thenmandatory? mention other CCA options (energy detection or pr

                                               Unless main authors participate attend all to build a transmitter, let alone dram
HBC text is not close to being complete, many missing sections and technically impossiblefuture meetings, and commit to a rec
                                               Insert a section that defines the operating frequency bands
A section on operating frequency bands is missing

A section on channel numbering is missing         Insert a section that defines the channel numbers and center frequencies

                                               Insert a EDTime, CCATime, Channel Switch Time, etc.)
A section on PHY layer timing is missing (pSIFS, pMIFS,section that defines the PHY layer timing

                                                Insert a etc.)
A section on inter-frame spacing is missing (SIFS, MIFS,section that defines the inter-frame spacing

                                                  Insert sections on rx-to-tx, tx-to-rx turnaround times
Sections on rx-to-tx, tx-to-rx turnaround times are missing

                                                 Insert
A section of center frequency switch time is missing a section on center frequency switch time

                                                Insert sections on is missing
Sections on transmit center and symbol clock frequency tolerancestransmit center and symbol clock frequency tolerances

                                                  is missing
Section of transmitter constellation error or EVMInsert a section on transmitter constellation error or EVM

                                                Insert
A section on adjacent channel power ratio is missing a section on adjacent channel power ratio

                                                 Insert a section on adjacent channel rejection
A section on adjacent channel rejection is missing

                                               Add ED measurement time and receiver clear channel assessment are missin
Sections on receiver energy detection, ED threshold, seections on receiver energy detection, ED threshold, ED measurement ti

                                             Pick either HBC or to the reader
HBC and EFC are used interchangeably and this leads to confusionEFC and use it consistently throughout spec. Preference is

                                             Remove the paragraph altogether
This paragraph assumes a particular implementation, which should not be included in a standards

Change bandwidth is 8 MHz, not 4 MHz              Replace "with the bandwidth of 4MHz" by "with the bandwidth of 8MHz"

                                             Replace "Header" with "PLCP Header"
The header should be referred to as a PLCP Header

                                                Remove
PHY Payload is not a typical term in IEEE 802 standards PHY Payload and just replace it with PSDU

Shouldn‘t used "And" to start a sentence          Replace "And PHY Payload" with "The PSDU"

Grammar is awkward                                Replace "The packet structure with PHY Header fields is shown …" with "The P

Figure 139 is not correct                         Replace PHY Header with PLCP Header, and PHY Payload with PSDU and sh

HBC has not been approved in any countries        change "many" to "any"

                                                 Remove last part of sentence: "and transmitted value
Aren't the signal transmitted actually analog? The last part of sentence is confusing and adds noin digital form"

                                              the dominant frequency? What
Don‘t understand the second sentence. What is Clarify by rewritting sentence does it mean? What does it mean to say "most

Grammar is awkward                                Need to insert a "the" between "Since" and "preamble"

Figure 142, what is f_ck?                         Define the values for f_ck

Typo: fCK                                         Replace with f_ck

                                             Please clarify. Can't built a transmitter unless it is known how to is the the Gold
How are the various preambles selected? How do you select which Gold Code polynomial? Who does selection, select PHY ba
                                               Please section
Paragraph is very confusing and hard to understand thisrewrite to clarify

                                                  Remove paragraph, Figure 143
This text doesn't belong in a standard. This text belongs in an academic paper and last line after figure

Figure 144, what is f_ck?                           Define the values for f_ck

                                             Please clarify. Can't built a transmitter unless it is parameter? Or is it the MAC?
How do you select which Gold Code polynomial? Who does selection, is the PHY based on some known how to select the Gold

Reference is missing                                Replace "0" with "Table 70"?

What is DRF?                                        Define DRF. Also define how DRF is selected? Who makes decision PHY or M

Is spreading factor 64 for this section? Why?       Clarify

Is Table 71 for DRF or RI? It is not clear?         Clarify

                                                 Bits should be mapped
How are bits in table mapped to the fields? Is LSB first? Or MSB first? LSB first

                                                      Replace "3 ~ 4" with "3 ~ 5"
Bit position 3 ~ 4 is only 2 bits, but 3 bits are defined

"-" doesn't imply reserved                          Replace "-" with "Reserved"

                                                 "no 01 for
Why are two bit values for sync (00,01) used for Use sync"? no sync and 00 for a Reserved value

                                              Clarify
What is difference between normal and dedicated mode? Why is it needed? Who makes decision (PHY or MAC) to use norma

                                              Clarify
Why are there 3 bits used for BAN ID? How are the BAN ID assigned? Does this mean that 8 simultaneously operating piconet

CRC8 is undefined                                   Please specify the CRC8 polynomial and how it is implemented

                                                Replace "master device and be more generic
Why does this field need to be specified for master and slave devices, shouldslave nodes" with "two devices"

"1x" notation is confusing                          Replace "is set to 1x" with "has a one in the first bit of the field"

                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                              Clarify
What are the registers? Where are they located? Are they in the transmitter or receiver? What are the pre-set values and how a

                                                     Specify
What happens if the first bit is set to zero (i.e. no-sync)? text for the condition when the first bit is zero (i.e. no sync)

                                                Replace "master device and particular slave
Why does this field need to be specified for master and slave devices, shouldabe more generic device" with "two devices"

What does 1:1 mean?                                 Explain and clarify

                                            Remore the dedicated device be section 11.6.2
Why is a dedicated mode needed? This is a TDD system, why would a mode and communicating at the same time as another d

                                             Define
What is C, N and L? These values should be specified C, N and L and their values

                                               Define the
What is FSC for this section? What values can be used? FSC values

C, N and L should be defined in Table 73            Define C, N and L in Table 73
Where was Data Rate Field (DRF) defined?           Please define DRF or reference section where DRF was defined

                                           Please clarify or PHY HDR structure for DRP mode and for RI mode
When is RI used? How is PHY HDR modified when RI is used thedoes it remain the same?

"garbage bits" is a terrible term                  Please replace "garbage bits" with something better, like "RI bits"

                                             Please specify how How "garbage bits" are used in T_offset
Figure 147, how many "garbage bits" proceed SFD code T_offset1? manymany before T_offset2? ... How many before T_offse

                                               Please clarify
Need more detail in last sentence. How does a device know that an SFD/RI is being used or an SFD/DRF is being used. Once

                                               Please clarify
Which SFD sequence is used for the pilots? Is the SFD/DRF or SFD/RI? Does it include "garbage bits"

Bit pattern 111 is missing from Table 75           Define bit pattern 111 as Reserved

                                                  Please clarify
What if bit pattern 011 is selected but the payload is less than 128 bytes, do you still insert the pilot pattern?

Typo: fBW                                          Replace "fBW" with "f_BW"

What is the value of f_BW?                         Clarify that f_BW = 8 MHz

                                                    Please replace this TG6. The correct figure can which should have a value of
Figure 149 is incorrect. This is not from the text that was adopted byfigure with the correct figure, be found in document 15-10-2

                                                Update text and found
Text should be updated to match the correct figure, which can befigure in document 15-10-201-02, where the limits should be

                                              Current mask
Where is the TX mask for a center frequency f_c = 27 MHz only works for f_c = 16 MHz and not f_c = 27 MHz. Please upda

                                               or equal to a maximum, not -12 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -12 dBm"

                                               or equal to a maximum, not -39 dBm" to "shall be less
Transmit power should be specified as less thanReplace "shall be more than the way it is defined now than -39 dBm"

                                                Please state all clock frequencies that can be used with this chapter
Is the clock frequency 64 MHz for this chapter? Or is it some other number?

                                                 Please means or update numbers refer to and how they should be
Table 77 is confusing. I don't understand what the table clarify andwhat thetable with additional text to improve clarity used in de

                                                Editor please pick either octet or byte and stick with it throughout document
In some places octets are used, in other places bytes are used

                                                   not just less than
PER is usually specified as less than or equal to,Replace "lessthan 1%" by "less than equal to 1%"

                                                 Update sensitivity = -11 dB with correct numbers. Proponents should bring a lin
Table 79 - sensitivity numbers are way too low, they imply an SNR numbers for the modulation scheme, which does not include

                                               They need to be statements. a clearer structure and meaning. Combine gen
The subclauses of this clause overlap back and forth with similar rewritten withSome sentences are grammatically incorrect, irre

                                            Change "impromptu" to "improvised". Remove the last sentence.
This comment is made based on an earlier comment by an active MAC participant.

                                                 Change "one-periodic" to "1-periodic".
"One-periodic" and "1-periodic" -- inconsistencies.

                                                 Restore without any markup to shalls and tone (―shall do‖ changed to ―do‖). T
Quite a few prescriptive shalls in Clause 5 were changedthe original prescriptive descriptive mays.

                                              Change
Emphasize that all these frames are unsecured frames. the comma in line 14 to "and", add "unsecured frames" before the 1st

                                                  Change the comma in line 23 to secured fraems.
Clarify explicitly that some of these frames are unsecured frames, and some are "and", add "unsecured frames" before the 1st
Clarify "as appropriate".                        Change "as appropriate" to "if control frame authentication was not selected du

                                            Restore all instances of of "1" are converted to "one", and one", "set … to one
This comment applies to numerous clauses. Some, but not all, instances"one" to "1" in the context of "set tosimilarly some, but

                                              Would MAC and security make the the draft. Many, but not all, please? Co
This comment applies to many places (especially in the the technical editorclauses) infollowing formatting changesunnumbered

Typo.                                            Move "not" to before the first "enabled" in this line.

Formatting glitch.                               Capitalize the first letter of "type" and "subtype".

                                              Would the technical crowded. (2) The first row needs cleared alignment. (1)
This comment applies to numerous tables. (1) These tables are a bit editor make the following formatting changes please?(3) th

Internal horizontal lines should be thinner.     Thin the internal horizontal lines below the 2nd row.

                                             Remove the row of "Wakeup" frame from Table 3, subclause in some subcla
The Wakeup frame provides no more functionality and effectiveness than the Poll frame, as explained in detail6.4.7 and related

Unwarranted capitalization.                      Change "Field" to "field" before "encoding".

Duplicate bullet number.                         Delete "6." at the start of the text.

                                               After "Coexistence format", well (as beacon another
The Coexistence field can be reused to define some fields for B2 frames as add "for noted in frames". comment).

                                            field, lines 14 and 20, change "first" to "final". (2) In lines 17 is the last one of
Use backward coding for the Fragment Number (1) In so that the recipient knows if the last received fragmentand 22, delete "no

                                                 (1) Insert a new numbered bullet before this line, with the
Define the Coexistence field for B2 frames, so that some fields don't need to appear in the frame payload. following text: h) In B

                                              6. While Clause 7 is written in prescriptive style (shall, should,
This comment applies to many places of Clause Restore all instances of "shall" to "must" throughout Clause 6. may) to specify

                                              Would the technical the draft (especially in spacings to security clauses). Th
This comment applies to most paragraphs following a bulleted item ineditor please adjust thethe MAC andbe a bit more uniform

                                            Move the misplaced commas?
Comma misplaced. Did reformatting in D0 generate othercomma from before to after Figure 12.

"not" misplaced.                                 Move "not" to before the first "enabled" in this line.

"not" misplaced.                                 Move "not" to before the first "enabled" in this line.

Simplify naming.                                 (1) Delete "Required" from the "Security Level Required" field in Figure 18. (2)

This comment applies to many tables in Clause 6. "Field value decimal"… please insert "in" before "decimal" J71and make "i
                                              Technical Editor, would you

"Protocol" is not part of the field anymore.     Delete "Protocol" from the heading.

Formatting glitch.                               Make the two internal lines (below the 2nd row) thinner.

                                               (1) and the the B+EAP1 Length and EAP2 Length which (2) frame is Status
There are some inconsistencies between this frameRemove Connection Assignment frame in 24 onfields. thisMove the based.

Unwarranted capitalization.                      In the table heading, change "Field" to "field".

                                               (1) Change "Request" discussed, let alone Change "Command Coexistence
(1) The frame formats of these two coexistence commands were neverto "Time Sharing". (2)approved, in the MAC- subgroup. (

                                                Promote 6.3.11.4.1 to one level higher as 6.3.12, and keep the
6.3.11.4.1 should be a parent subclause of the three subclauses that follow, instead of being at the same level. subclauses tha
                                                  Change "Command - Coexistence Request" to "Command two separate Time
There is no functional difference specified for "coexistence request" and "coexistence response". Hence no - Coexistenceframe

                                                 (1) Change to to frame defined here.
These lines need to be revised in view of the changes made "in"the "for" before "a Command". (2) Insert "time sharing enabled"

                                                   (1) needed to be reworked to be consistent in naming field proposed other se
(1) Both the definition and table for "Piconet priority"Change "Piconet Priority" to "BAN Services", a new and format within the Co

                                                 Remove them along with the figure and table the "status" field, which, however
These are just duplicates of the subclauses for the "Coexistence Request" version, except for within.

Incorrect level for these three subclauses.       Promote 6.3.11.5.4 to one level higher, and keep the two subclauses that defin

Incorrect level for this subclause.               Promote 6.3.11.5.7 to one level higher.

Incorrect level for this subclause.               Change "in" to "for" before "a Command".

                                                   (1) Change set…, but to the relay node will set this field.
(1) locally broadcast but not locally multicast. (2) the field is "multicast"not "broadcast" in line 5. (2) Reword the 2nd and 3rd se

                                                 Remove the the quality of the field presence of noise and interference.
The "received signal strength of signals" does not truly reflectRelay Link Qualitylink inand all references to it, unless the propose

                                                 (1) or the MAC header of the definition subclauses (and Table 13 which has a
(1) Many fields are already contained in the beacon Remove all fields and theirB2 frame, and should not be duplicated here, per

Typo.                                             Change "rage" to "rate" in the table heading.

Formatting glitch.                                Make the two internal lines (below the 2nd row) thinner.

Two much space.                                   Delete this empty line.

                                              Change "to indicate
Some clarification is needed on why and when this IE is included. ..lengths" to "foretell some information on the superframe (

                                                   Add to needed to be separately included, so is the beacon shifting sequence
If superframe length and allocation slot length fields arethe end of the current IE an optional "Beacon Shifting Sequence" field. f

                                                   somewhere else.
Avoid repeating a definition that is already given Change these two lines to the following: The Superframe Length field is as de

                                                   somewhere else.
Avoid repeating a definition that is already given Change these two lines to the following: The Allocation Slot Length field is as d

                                               Add
A new subclause is needed to define the new field. a new subclause, 6.7.1.3 Beacon Shifting Sequence, with the following tex

Figure formatting glitch.                         Insert two dashed lines at the start of the bottom fields to indicate continuation

Figure formatting glitch.                         Insert two dashed lines at the start of the bottom fields to indicate continuation

                                               Insert a Assignment frame should be defined "Node Address" field.
The "Status Code" field now in the Multinode Connectionone-octet "Status Code" field after the on a per node basis and hence

Inconsistent frame reference.                     Change the paragraph to "All the fields after the Length field pertain to the sam

                                             Remove the row containing functionality
As explained in related comments, the Wakeup frame provides no additional"Wakeup". to the Poll frame.

Typo.                                             Add "final" before "frame sent", and change "last" to "previous" before "block tr

                                              After "pSIFS", add ", depending on
Need to make a connection with burst mode transmission defined in the PHY spec. whether it is setting the block transmission

Figure 55 was mistakenly changed in this draft. Remove all the test boxes other than those indicating a frame.
                                                    It is time to resolve Type II access phases, other than basis. Remove delayed
(1) There is no technical justification for having separate Type I and technical comments on a technical fragmenting the superfra

                                              can "send" add "at most".
Need to make it clear that an unconnected nodeAfternot send more than one frame in a shared polled allocation.

Formatting glitch.                                Make the first "n" a regular instead of an italic letter in "fun ction".

Typo.                                             After "which" change "are" to "is".

                                                 In line 36 of needs to be decoupled from add "the appropriate guard time in th
The "appropriate guard time" is not a fixed value, and hence page 78, after "shorter than" the parameter referenced earlierplus"

Figure 65 was mistakenly changed in this draft. Remove all the test boxes that appear on the top or bottom of the figure.

                                                  Make "Frame" plural
Formatting glitch in the heading of Table 20, introduced in this draft. and delete "(1-1)".

The last statement of Table 20 is not quite clear.Remove the last row of Table 20, and add a new short paragraph after Table 2

Figure 66 was mistakenly changed in this draft. Remove all the test boxes other than those indicating a frame.

Unfinished cleanup from last draft.               Delete ", and one or both of the MSDU … nonzero values".

                                              Change "the hub shall respond with" to
The hub may also send an unsolicited Connection Assignment frame as intended here. ", requested by the node or initiated by

                                               Delete "a", "b", 'c" in these figure captions.
Figure 69, Figure 70, Figure 71 already have separate figure numbers, but were numbered by "a", "b", and "c" further in this dra

                                                After this cannot be add a new one
Need to explicity state that an ended scheduled allocation paragraph used anymore. as follows: A node or a hub shall not send

                                             have appeared here.
This subclause makes no sense and should not Remove it.

                                            -- when?
No shalls. "…shall send the wakeup messages"Remove these two paragraphs, as they provide unnecessary introductory infor

                                                  this is not how
I explained to the proposers back at the F2F thatRemove them. the I-Ack works: A recipient would not go into the payload to c

                                                 Remove these duplicate but inaccurate and incomplete poll, as specified here.
(1) It increases complexity and decreases efficiency to have a wakeup followed by an Ack and then by a descriptions of the unic

Typo.                                             Change node to "nodes".

                                               Change "session to "phase" throughout this subclause and Figure 76.
Do not use "session", which has a special meaning per MICS band regulations.

                                              in Fig. 76.
Need to make a connection with "lockup phase" After "Poll frames", add "forming a lockup phase and".

                                               After "polled
Need to make a connection with "individual phase" in Fig. 76.allocation", add " thus starting the individual phase for the node as

                                                 Change "shall" to "should".
A "shall" may not always be justified as the nodes might not know in advance the time of pending frame exchanges.

                                                 might have missed earlier
A "shall" may not always be justified as the nodeChange "shall" to "should". polls.

                                                intent of this duplicate more accurately and consistently, as explained further
Figure 76 and the related text accomplishes the Remove this subclausebut inaccurate and inconsistent subclause 7.8.2.1.4.

                                              more power consumption for described scheme is not well thought out and ha
(1) The described mechanism would only cause It is time to recognize that the all nodes, which would have to wake up several t

                                              After "it should", performed on other channels.
Tighten up the sentence do expressly convey the same behavior add "similarly send and".
                                            (1) --- since pMICSFrameSpace after        same its different transmission".
Frame spacing does no longer have the same valueDelete "atthe next frame may be on the end ofor alast framechannel.

"emergency" is a data frame name.                 Capitalize the first letter of "emergency" for consistency.

                                                Rewrite the whole subclause to address the outstanding issues.
This subclause has yet to define the frame structures used to support the relay functionality, and to specify the access methods

                                                   (1) Move them to end of of 7.12 this new subclause, 7.12.5. that follows.
It will have a better structure to create a separate subclause at thethe end 7.12 for as a paragraph and the table Applicability guid

                                                  Rewrite the implementation to specify does hub is supposed to do for coexis
Much of this subclause is either tangential to coexistence or whole subclausespecific. Ithow a not prescribe testable normative

                                               Delete "and load reduction" from the heading.
Load reduction is covered in a separate subclause later.

                                              Delete them as they are not germane to normative coexistence behaviors.
These are not about coexistence per se, but more about BAN creation (and maintenance) which is already described in 7.4.

                                                 Delete them that are implementation germane to normative coexistence beha
Again these are not specific to coexistence but specify things as they are not correct orspecific (which are generally not to be pa

                                              Delete them as they frame, and BAN descriptor? (2) How normative coexiste
(1) What on the earth are BAN enquiry frame, BAN enquiry responseare not defined, correct, or germane tois the hub supposed

                                                coordinator as they are not with respect to it if it is not implementation specific
(1) Again what is a BAN descriptor and what is aDelete them supposed to do defined or germane to normative coexistence beh

                                             Delete them as they have no substance or are not germane to normative coex
(1) Why shalls? A hub may choose no channel at all and create no BAN. (2) How is a hub supposed to "utilize the information

No need for a new, lower level subclause          Delete the heading.

Certainly not a shall.                            Rephrase them as a "may".

Inaccurate or repeated sentences.                 Remove them.

                                                Remove 7.12.3.1 if these fundamental issues are not addressed inconsistent
(1) Connection request,, coexistence request, coexistence assignment, coexistence assignment request -- still soby end of the

Is this in essence time sharing as well?          Merge this subclause with 7.12.3.1. Both are about time sharing, and may be

                                                sharing this subclause to but level higher, be change the heading to "Code d
(1) This subclause should not be under the timePromote subclause 7.12.3, one rather shouldand in parallel. (2) The heading do

                                                Remove the subclause this subclause -- which coexistence per se, or rewrite
(a) How can interoperability tests be designed based on the language ofwhich is not germane to again is so unfocused and has

                                                   an earlier comment.
This is part of the paragraph with issues noted inRemove it or refine it together with the earlier part of the subclause.

Rephrase the heading in MAC terms.                Change the heading to "Allocation reduction".

                                                 Rephrase the subclause The 3rd it more concise and precise. Suggested tex
The first two paragraphs need to be rewritten in more concise language. so makeand 4th paragraphs are a repeat of the gener

It is hard to interpret and use table 22.         Edit it -- in line with the BAN's designated services defined for time sharing.

                                                Restore in this draft existed prior to D0. at the are not correct
This subclause was modified, incorrectly or inaccurately, the text that without a discussion If they MAC subgroup.or complete, pl

                                               Change the value entry to pMICSMcastPollSeparation + pMICSPreambleTxTim
Incorrect equation and parameter value for pMICSMcastPollRxTime.

                                               Change the value entry to ceiling[pMICSChannelsTotal × (pMICSMcastPollRxT
Incorrect equation and parameter value for pMICSMcastPolls.

                                               Change the value entry
Incorrect equation and parameter value for pMICSMcastPollSeparation. to pMICSPollTxTime + pMIFS = 1614 us
                                            Change since it is defined with respect to per channel. A large value for this p
The value for pMICSNodeEmergencyRetries is too large the value to 2.

See proposed change.                              Change "NB," to "narrow band (NB) PHY, ", "slotted" to "Slotted", and "UW" to

                                                 Replace the entry the MAC subgroup.
The value in the last row was put in (by me) without a discussion atwith the following: ≥ transmit time of a PHY frame with a MA

Formatting glitch.                                Make the text in the first row bold and centered, and the bottom line bold.

Formatting glitch.                                Insert a space before and after each plus sign of this table.

                                                 Revise the an equation containing the underlying parameters. (2) This value sh
(1) The value for pAllohaSlotLength should be first given by entry as noted in the comment.

                                                  Replace the entry with the following: ≥ transmit time of a PHY frame with a MA
The value in the last row was put in without a discussion at the MAC subgroup.

Missing introduction to 8.4                       After line 12 add a new paragraph: Support for mandatory and optional cipher

Missing comma.                                    Insert a comma after the closing parenthesis.

                                                Technical Editor, please make all the to be in italic font.
This comment applies to all the equations in Clause 8. All these math equations needequations (but not the equation numbers

                                                  Remove the underscore in both lines 29 and 30.
An underscore after "P" was artificially added in this rev, resulting in inconsistency with the corresponding figure.

                                                  Remove the underscore in both lines 18 and 19.
An underscore after "P" was artificially added in this rev, resulting in inconsistency with the corresponding figure.

                                                  Remove the underscore in both lines 17 and 18.
An underscore after "P" was artificially added in this rev, resulting in inconsistency with the corresponding figure.

Too crowded.                                      Leave a blank line before line 12.

Too crowded.                                      Leave a blank line before line 22.

                                                  (1) Insert the following secured frames at which conditions.
It has been suggested to explicitly state what frames are transmitted asas the first paragraph of this subclause:Frames shall be

Formatting glitch due to misplaced period.        Delete the space after "97", and move the next line (line 30) back to line 29. F

                                              the spec. subclause along with Table 45.
SIFS and MIFS are not referenced elsewhere in Delete thisThey are not referenced as pSIFS and pMIFS.

                                            Technical Editor, would you please decapitalize capitalized, which first letters
These comments apply to many places in Clauses 9-11. Some headings have all the first lettersin the headings the is not consi

Incorrect grammar.                                Change "media" to "medium".

                                                 Delete "during association".
"during association" -- how and why to enforce this?

                                                 Remove this subclause.
(1) This subclause is out of PHY's scope. (2) "full function devices (FFD)" and "reduced function devices (RFD)" are not define

                                                 Remove this subclause.
(1) This subclause is out of PHY's scope. (2) Item 1 is addressed in the MAC portion. (3) Item 2 is purely imaginary. How can

Which "SAP"?                                      Change "From MAC Via SAP" to "From MAC SAP".

Incorrect statement.                              Change "payload from the MAC via SAP" to "MAC frame".

                                        payload of 256 "255".
How does the UWB PHY header encode a MACChange "256" tooctets?
                                                    It In line 21 and reference the correct name or ask for consultation.
Incorrect field names in both the text and figure. (1)is advisable to inside Figure 118, change "MAC payload" to "MAC frame bod

                                            Use a bit in the reduces inter-frame spacing from analogy with 9.3.1.3.
The narrow band PHY supports burst mode transmission which PHR to as a "Burst Mode" field, in SIFS to MIFS. It is advisable

                                                  Remove this sentence
(1) The last statement is out of PHY's scope -- the PHY cannot tell whether it is part of a hub or a node. (2) It is not clear either

                                               Remove this sentence
Improper language for the standards -- "can be achieved". The statement does not mean anything for interoperability.

                                                 Make "codes" singular.
Only one error detection code, but not multiple codes, is defined at the MAC.

                                                 Make "codes" be defined
Only one invertible code, but not multiple such codes, needs tosingular. for HARQ. In fact, none is defined!

                                               Remove HARQ altogether without a predefined defined or MAC subgroup at
Where is the invertible code defined? How can interoperability be achievedunless such a code is code? Thereferenced here ha

Incorrectly referenced table number.              This should be Table 62.

                                             Change "NACK" to "No Ack" in through No Ack at figure throughout
We already explained to the HARQ proposer that NACK for HARQ is supported the text, table, and the MAC level. this subcla

                                             a In Table 62, delete and a packet containing to 1" to "go to "state 1", and tw
HARQ enabled transmission alternates between(1)packet containing D the last row; change "goP_sub_D. Accordingly, only "g

                                               Remove HARQ altogether unless the issue is addressed.
How can the transmitter tx D head, which was the received version of D in the 1st column? If this comment is still not clear, ho

Incorrect field name in Figure 139.               Change "MAC Payload" to "MAC Frame Body".
Table 50                                          Table 48
Refernce to Table 63                              This table is non-existent in UWB framework and must be typo. This can be de

                                                    Kindly remove this
Receiver flow diagram is out of scope of the specification.
"Spr" should be "Spreading parameter"              Replace "Spr" with "Spreading parameter", or specify abbreviation
Reffered sub-clause numbers are wrong              12.11.4.1 should be 10.11.4.1 and 12.11.4.2 should be 10.11.4.2
NB is Spreading parameter and equals to 1 or 7 Add proper explanations
Specify exact codeword of Barker code in table
                                                   Statement of frequency of only applies for differentially coherent PHYs the us
What is a definition of central frequency? If this means carrierline 16 should stationary UWB-IR type waveform, some of thatpro
High QoS mode needs a precise definition           Provide a precise definition of high QoS mode
Must Be Satisfied?
(enter Yes or No)    Resolution




Yes




Yes




Yes




Yes
Yes




Yes




Yes




Yes
Yes



Yes




Yes




Yes


Yes




Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes



Yes

Yes

Yes

Yes

Yes
             Yes

             Yes

             Yes



             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

te and stick with it throughout document

             Yes

             Yes
             Yes

             no

             No

             No

             No

             No

             No

             Yes

             Yes

             Yes
             Yes
             Yes
             Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes


Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes


No

Yes

Yes

No

No

No

Yes
Yes

Yes

No

No

No


No


No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

Yes

Yes

No
Yes

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No
No
No
No
No
Yes
No
No
No
No
No
No
No
No
No
Yes
No
Yes
Yes
Yes
No
Yes
No
No
Yes
No
Yes
Yes
No
No
No
No
No
Yes
No
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
Yes
No
Yes
No
No
No
No
No
No
Yes
Yes
Yes
Yes
No
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

No

No

No

No

Yes.

Yes.

Yes.
Yes

Yes

Yes

Yes
Yes
Yes
Yes
Yes
No
No
No

No

Yes

Yes

No

Yes

Yes

No

Yes
Yes
No

No

No
yes
yes
yes

yes

yes
yes

no

yes

yes

yes

yes
yes

yes
yes
no

no

yes

yes

yes
Yes

      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
      Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
        Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

BLANK
BLANK
BLANK
BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
             BLANK
on Shifting Sequence Index by hearing beacons of neighbor hubs.

Coexistence Response.




are as follows,-Immediate poll is to grant an immediate polled allocation to the node-Future poll is to inform the node of an intended future po

AP1 and RAP2 length at BP0 because it's a transient period, specify so.

 '"Table 46".Line 15:   to replace "'Table 50" with "'Table 48"

est" with "coexistence request" Line6: to replace   "assignment" with "response"Line 8; to delete   "assignment" at the beginning of the lineL

              Yes
              No
              No
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes

              Yes

              Yes
              Yes
              Yes
              Yes

              Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes


Yes

Yes


Yes


Yes


Yes


Yes
Yes
Yes




Yes


Yes


Yes




Yes
Yes
Yes



Yes




Yes

Yes

Yes

Yes




Yes



Yes



Yes




Yes




Yes


Yes

Yes

Yes
Yes




Yes


Yes
Yes


Yes




Yes




Yes



Yes

Yes
Yes


Yes


No



No
No
No
No
Yes

Yes

Yes
Yes
Yes
Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes

Yes

Yes
Yes

Yes

Yes

Yes
Yes

Yes
Yes

Yes

Yes
Yes
Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes



Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes
             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

              Yes
te and stick with it throughout document
              Yes

             Yes
             Yes
             Yes
             Yes
             Yes
             Yes
             Yes
             Yes
             Yes
             No
             Yes

             No
             Yes

             No
             No

             No
             No

             No
             No
             No
             No
             Yes
             Yes
             Yes
             No
             Yes
             Yes
Yes
Yes
Yes
Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes



Yes

Yes

Yes
No
Yes

Yes
yes

yes

Yes

Yes


Yes
Yes
No

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes
Yes

Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes



No


Yes
             Yes




             No




             No




             No

               No
               No
               No
               No
               Yes
tion to 8 bits symbol requires a search of 16 codewords to recover 4 bits of information simplifying the receiver considerably
f-fc|<=1/Tp and adding -20dBr for |f-fc|>1/Tp
               No
               No
               No
               No

             Yes

             Yes

             Yes
             Yes

             No

             Yes

             Yes

             Yes

             No

             No

             Yes

             Yes

             No

             Yes

             No

             No

              No
 consider extending the dimension of the BCH code by the 4 . Complexity of the decoder may be slightly increase.
              Yes
              Yes
              No
              Yes
              No
              No
              No
              Yes
              Yes
              No
              No
              Yes
              No
              Yes
              Yes
              Yes
              No
              Yes
              Yes
AC header to indicate this in ACK frames from relaying nodes that are currently accepting new relay connections. This way a node doesn‘t ne
 ion of ACK frame with RN Sender address if Sensor node is a relayed Node
              Yes
              Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes



Yes
Yes




Yes



Yes

Yes

Yes

Yes




Yes




Yes




Yes
Yes


Yes

Yes

Yes



Yes


Yes


Yes




Yes



Yes



Yes




Yes
Yes



Yes
Yes

Yes


Yes
Yes
Yes




Yes

Yes




Yes


Yes




Yes




Yes




Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes
              YES
              YES
              YES
              YES
              YES
              YES
              YES




             YES
equently select a new channel for LBT, when required by the regulations, in the order indicated in the list"

er change of channels
ultiple node discovery. It is more like multipler node wakeup mechanism.
               YES
               YES

uch as PMICSUnconnectedPolls, PMICSUnconnectedPollRxTime cannot apply to channel access
amples of the data to be collected is more than PMICSPollRxTime. The same rule can not be applicable for data session
ch it last received a frame with a valid FCS from the hub. After dwelling on the current channel for "multiple of" PMICSPollRxTime.

ering and on what basic it is selected. If the coordinator has to change the channel first it will perform LBT for for at least 10 ms and the time




              YES




olled allocation




              YES
              YES
              YES
              YES


                YES
s constant. The T-poll can be merged with the poll message. This will reduce the total number of management frame and therefore MAC com
 D is required while other device are still connected, should be detailed out
 ect simultaneously? Clarification.
 yload. Clarification
Contention access but not defined in case of scheduled, schduled poll and delayed poll access also the meaning of eexceleent effort control
either by hub or node should be re-looked, since lot of changes has been done in MAC behaviour during the multiple discussion sessions. Su


 rframes and why this not not be achieved using inactive period in side a superframe
moved from CA frame, since we have addressed this comment in beijing meeting
ss mechanism appliable in this phase
ss mechanism appliable in this phase
ccess and delayed poll access terms are used in first paragrapg but not detailed. Either all three mechansims shouldbe detailed out here ref



or of Connetion request IE to get additional slots to increase Gta length
               YES
               NO
               YES
               YES
               YES
               YES
               YES
               YES
d to "existing coordinator".
 Is time sharing applicable for piconet encounter case?
  the the length of reserved slots duration with the number of slots which can be informed to neighboring coordinator as exclusion period for c

e response operation is for static case.Semi-dynamic case should be described seperately. "       If coordinator detects inter-piconet interferen
ring" removing "& load reduction"

creasing slot action?
coordinator shall try to locate beacon or B2 message in a channel. And prospective coordinator shall enable its receiver for at least mPassive
ld" should be written in B2 or beacon section.
nt to the general time based constraint.

              YES
              NO
              YES
              YES
              YES
              YES
              YES
              YES
              Yes
              Yes
              Yes
              Yes
              Yes
              Yes




              Yes
              Yes
              Yes
              Yes
Yes
Yes
Yes
Yes
Yes




Yes
Yes




Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes




Yes




Yes
Yes




Yes




Yes




Yes
Yes




Yes




Yes




Yes
Yes
Yes


Yes




Yes


Yes
Yes
Yes

Yes

Yes


Yes
Yes
YES
Yes
Yes
Yes




Yes
Yes

Yes
Yes

Yes



Yes




Yes




Yes



Yes

Yes

Yes

Yes
Yes




Yes




Yes


Yes


Yes

Yes

Yes



Yes


Yes


Yes




Yes
Yes



Yes




Yes
Yes



Yes
Yes

Yes


Yes


Yes
Yes




Yes

Yes




Yes


Yes
Yes




Yes




Yes




Yes


Yes


Yes




Yes




Yes
Yes




Yes
Yes


Yes
Yes

Yes




Yes


Yes


Yes
Yes

Yes

Yes

Yes
Yes


Yes

Yes

Yes
Yes
Yes




Yes
Yes


Yes


Yes
Yes




Yes
Yes

Yes




Yes
Yes



Yes

Yes

Yes




Yes
Yes


Yes
No
No
Yes
Yes



Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
YES
NO
YES
YES
YES
YES
YES
YES

YES
YES
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes



Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes



Yes
Yes
Yes
Yes


Yes
Yes
Yes
Yes
Yes
Yes

Yes
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed

Yes
Yes   15 min late after ballott closed
Yes   15 min late after ballott closed
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed


Yes
Yes   15 min late after ballott closed
      15 min late after ballott closed




Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed



Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed

Yes
      15 min late after ballott closed


Yes
Yes   15 min late after ballott closed
      15 min late after ballott closed
Yes
Yes   15 min late after ballott closed
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed




Yes
Yes   15 min late after ballott closed
Yes   15 min late after ballott closed
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed


Yes
      15 min late after ballott closed
Yes
Yes   15 min late after ballott closed
      15 min late after ballott closed
Yes
      15 min late after ballott closed




Yes
      15 min late after ballott closed

Yes
Yes   15 min late after ballott closed
      15 min late after ballott closed




Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed
Yes
      15 min late after ballott closed

Yes
Yes   15 min late after ballott closed

Yes
Yes

Yes
Yes



Yes
Yes

Yes


Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Yes
Yes

Yes
Yes
Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes
Yes
Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes



Yes

Yes

Yes
             Yes

             Yes

             Yes
             Yes

             Yes



             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

              Yes
te and stick with it throughout document
              Yes

             Yes



             Yes

             Yes

             Yes

             Yes


             Yes

             Yes

             Yes

             Yes

             Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes



             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

             Yes

te and stick with it throughout document

             Yes

             Yes
             Yes

             Yes

             Yes

             Yes

             Yes

             Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
e of an intended future poll(immediate or future) or post.




the beginning of the lineLine 24: to replace   "connection" with "coexistence"
his way a node doesn‘t need to have a list of available relaying nodes beforehand. Also because it is for ACK frames only, this bit can be turn
CSPollRxTime.

 least 10 ms and the time spent by the device at each channel is approximately 3 ms, therefore the device could be in any random channel w




me and therefore MAC complexity.



f eexceleent effort controlled load traffic is not clear in the context of BAN
e discussion sessions. Suggesion.




uldbe detailed out here reference should be provided where these has been discussed in detail
r as exclusion period for coexistence. And it also indicates the earliest B2 time, because the length of reserved slot is on the period between

cts inter-piconet interference at the initial phase of superframe, it stops piconet operation and waits to receive B2 from neighboring coordinat



eiver for at least mPassiveScanDuration duration waiting for B2."
ACK frames only, this bit can be turned off if a relaying node is no longer accepting new relay connections.
ce could be in any random channel when the coordinator will actually poll the device. There is no performance improvement of using channe
served slot is on the period between the start time of next superframe and the time of B2 message transmission when no delay poll occurs.

ceive B2 from neighboring coordinator. The specific superframe structure of BAN helps this opertaion reduce latency of exchanging coexiste
mance improvement of using channel ordering for divice discovery process
smission when no delay poll occurs.

educe latency of exchanging coexistence information, because coordinator can send B2 as coexistence response in this superframe by the s
response in this superframe by the structure of B2 and CAP following several types of channel access periods. "
ID Number          PageSub-clause # Comment
            Category          Line
S14-1              PDF 20
            Editorial  4      1     Entry for PRF (pulse-repetition frequency) is
                                    missing
S14-2              PDF 20
            Editorial  4      1     Entry for PSD (see Figure 128)

S14-3              1
            Editorial   1             The subclauses of this clause overlap back
                                      and forth with similar statements. Some
                                      sentences are grammatically incorrect,
                                      irrelevant to their section headings, or unfit with
                                      a formal standard. They need to be rewritten
                                      with a clearer structure and meaning.


S14-4              7
            Editorial   3      37     "One-periodic" and "1-periodic" --
                                      inconsistencies.
S14-5              10
            Editorial   4      25     "qadrature" should be spelled "quadrature".
S14-6              10
            Editorial   4      1      Some acronyms are missing, and need to be
                                      added to the list: ISO and OSI, for example.

S14-7            9
            Technical 3        17-20 The function of type-II plooed allocation can be
                                     achieved by using type-I polled allocation.




S14-8            3
            Technical 2        13    Note 3 incorrectly defines NIST
S14-9            5
            General   3              The entire clause 3 defines multiple terms for
                                     the same thing, which violates the 802.15 OM
                                     (LB54) clause 11 (15-10-0324-00-0000 1.1,
                                     bullet 5)
S14-10           9
            Technical 3        17-20 The function of type-II polled allocation can be
                                     achieved by using type-I polled allocation.

S14-11           9
            Technical 3        17-20 The function of type-II plooed allocation can be
                                     achieved by using type-I polled allocation.

S14-12           9
            Technical 3        17-20 The function of type-II polled allocation can be
                                     achieved by using type-I polled allocation.

S14-13           9
            Technical 3        17-20 The function of type-II polled allocation can be
                                     achieved by using type-I polled allocation.

S14-14             1
            Editorial   1             The subclauses of this clause overlap back
                                      and forth with similar statements. Some
                                      sentences are grammatically incorrect,
                                      irrelevant to their section headings, or unfit with
                                      a formal standard. They need to be rewritten
                                      with a clearer structure and meaning.
S14-15          7
         Editorial   3     37   "One-periodic" and "1-periodic" --
                                inconsistencies.
S14-16          1
         Editorial   1          The subclauses of this clause overlap back
                                and forth with similar statements. Some
                                sentences are grammatically incorrect,
                                irrelevant to their section headings, or unfit with
                                a formal standard. They need to be rewritten
                                with a clearer structure and meaning.


S14-17          7
         Editorial   3     37   "One-periodic" and "1-periodic" --
                                inconsistencies.
S14-18          5
         Editorial   3     20   The definition of "association" is ambiguous.


S14-19          7
         Editorial   3     16   A period is missing after the definition.
S14-20          9
         Editorial   3     14   A period is missing after the definition.
S14-21          8
         Editorial   3     3    Use of PTK acronym without defining the
                                acronym first.

S14-22          11
         Editorial   4     18   Clarify that medical implant communication
                                service is synonymous with MedRadio which is
                                the FCC's updated name for this radio service.

S14-23          12
         Editorial   4     4    Add definition of RTT acronym



S14-24          12
         Editorial   4     4    Add definition of RN acronym



S14-25          12
         Editorial   4     8    Add definition of SN acronym



S14-26          1
         Editorial   1.2        There is only description based on the
                                antenna, but electrode.




S14-27        7
         Technical 3       1    use of the term "hub"
S14-28          1
         Editorial   1   20   This is not a document, it is a standard.




S14-29          1
         Editorial   1   24   There is no 802.15 MAC.




S14-30          3
         Editorial   2   6    It appears that there is a mistake, you should
                              only have one introduction paragraph to the
                              references. These two paragraphs appear to
                              conflict.
S14-31          5
         Editorial   3   1    The format for the definitions does not follow
                              the style guide.
S14-32        6
         Technical 3     5    A definition needs to be general, not specific to
                              the standard.




S14-33        6
         Technical 3     40   "All terms defined in IEEE standards are
                              incorporated into the IEEE-SA Standards
                              Definitions Database.
                              For this reason, it is important that terms and
                              definitions have as general an application as
                              possible." 2009 Style Guide


S14-34        10
         Technical 4     4    This is not an acronym expansion. Plus AES
                              and CCM are expanded elsewhere.
S14-35        1
         General     1.2   31     In subclause 1.2, sentence reads: "This
                                  standard considers effects on portable
                                  antennas due to the presence of a person
                                  (varying with male, female, skinny, heavy,
                                  etc.), radiation pattern shaping to minimize
                                  specific absorption rate (SAR)1 1 into the
                                  body, and changes in characteristics as a
                                  result of the user motions." However, there is
                                  no mentioning of SAR at all in each of PHY
                                  specification parts. It is unclear how this
                                  standard considers the SAR minimization.

S14-36        7
         Technical 3       1      use of the term "hub"




S14-37          1
         Editorial   1.2          There is only description based on the
                                  antenna, but electrode.




S14-38          7
         Editorial   3     6-11   This comment is made based on an earlier
                                  comment by an active MAC participant.




S14-39        PDF A
         Technical 2 bstract6     "Mbps" is not a SI unit


S14-40          3
         Editorial   3x    6-11   This comment is made based on an earlier
                                  comment by an active MAC participant.

S14-41          3
         Editorial   3x    6-11   This comment is made based on an earlier
                                  comment by an active MAC participant.
S14-42   Technical 2   (T) Clause 2: The RNG-related references
                       (NIST SP800-90 and RFC 4086) do not
                       seem to be used in the remainder of the
                       specification. Moreover, these references
                       are usually only informative, since there
                       are many ways of generating random
                       numbers (also by physical means) and
                       stipulating one method over another is
                       somewhat arbitrary, depending on
                       implementation environment. Most
                       specifications therefore mention the
                       requirement for cryptographically sound
                       randomness, but leave the details of how
                       this should be realized as out of scope
                       exercise. Suggested remedy: Make details
                       re RNG generation processes out of scope
                       and include references as informative
                       references only (after all, one also does not
                       stipulate how to provide side channel
                       resistance of implementations of
                       cryptographic schemes!).

S14-43   Technical 4   (T) Clause 4, pp. 10-12: There is a
                       plethora of acronyms related to security,
                       including AES, AES-128 CCM, CCM,
                       CBC, CMAC, GTK, KCK, KMAC, MIC,
                       MK, PTK, TK. There seems to be room
                       for some clean-up of acronyms here, as
                       well as better clarification (elsewhere) or
                       the relationship between acronyms with
                       this alphabet soup, since now this is utterly
                       confusing. This remark also applies to
                       error detection code-related acronyms,
                       including FCS, CRC, etc. Suggested
                       remedy: Define concise set of acronyms
                       that covers required functionality. No need
                       to refer to AES-128 CCM, CBC, CMAC
                       (cf. comments), one of KMAC or MIC,
                       and some of the key types, my thinks.
DEFER
Proposed Change                            Resolution
Create entry for PRF                       Accept comment                     0   Done

Create entry for PSD                       Accepted in principle. PSD is      0   Done
                                           power spectral density
They need to be rewritten with a           Reject.                            0   Done
clearer structure and meaning.
Combine general statements and             Subclause 1 is taken from the
application examples currently             TG6 PAR. Per IEEE
scattered in 1.2, 1.3, and 1.4 into        document guidelines of 2009,
1.1. Rephrase 1.2 in technical             scope purpose and need are
terms. Delete the critique of PAN          to be included exactly as in the
from 1.3.                                  PAR.
Change "one-periodic" to "1-               Accept comment                     0   Done
periodic".
Make it so.                                Accept comment                     0   Done
Make it so.                                Accept in principle comment        0   Done


Consolidate tpye-I and type-II polled Reject.                                 0   Done
allocation. If not, justify the need for
type-II.                                 Refer to subclauses 6 and 7
                                         for specification of different
                                         polling mechanisms which are
                                         needed for various application
                                         scenarios.
Change for to of                         Accept comment                       0   Done
Use one term only (e.g. active state Accept comment. Delete page              0   Done
(not awake) and inactive state (not 5, line 21 and page 6, line 40
hibernation state)

Consolidate type-I and type-II polled      Same as S14-7                      0   Done
allocation. If not, justify the need for
both
Consolidate tpye-I and type-II polled      Same as S14-7                      0   Done
allocation. If not, justify the need for
type-II.
Consolidate tpye-I and type-II polled      Same as S14-7                      0   Done
allocation. If not, justify the need for
type-II.
Consolidate type-I and type-II polled      Same as S14-7                      0   Done
allocation. If not, justify the need for
both
They need to be rewritten with a           Same as S14-3                      0   Done
clearer structure and meaning.
Combine general statements and
application examples currently
scattered in 1.2, 1.3, and 1.4 into
1.1. Rephrase 1.2 in technical
terms. Delete the critique of PAN
from 1.3.
Change "one-periodic" to "1-           E.                                0   Done - Same as S14-4
periodic".
They need to be rewritten with a       Same as S14-3                     0   Done
clearer structure and meaning.
Combine general statements and
application examples currently
scattered in 1.2, 1.3, and 1.4 into
1.1. Rephrase 1.2 in technical
terms. Delete the critique of PAN
from 1.3.
Change "one-periodic" to "1-           Same as S14-15                    0   Done
periodic".
Change "security association." to "A   E.                                0   Done
term synonymous to security
association in this standard."
Add a period after the definition.     E.                                0   Done
Add a period after the definition.     E.                                0   Done
Change to "…to create a pairwise       E.                                0   Done
temporal key (PTK) between a
node…"
Change to "medical implant             Rejected.                         0   Done
communications service,
synonymous with MedRadio service       This acronym is correct as
                                       written in the text.
Add line "RTT Restricted Tree          Rejected.                         0   Done
Topology"
                                       RTT is no longer used as a
                                       term in the updated draft.
Add line "RN   Relay Node"             Rejected.                         0   Done

                                       RN is no longer used as a term
                                       in the updated draft.
Add line "SN   Sensor Node"            Rejected.                         0   Done

                                       SN is no longer used as a term
                                       in the updated draft.
EFC(HBC) related description is        Reject.                           0   Done
required.
                                      Subclause 1 is taken from the
                                      TG6 PAR. Per IEEE
                                      document guidelines of 2009,
                                      scope purpose and need are
                                      to be included exactly as in the
                                      PAR.
change the use of the word "hub" in Reject.                              0   Done
the document to "co-ordinator" in
the entire draft. The term "hub" does Hub is term used throughout
not appropriate for a BAN co-         the document as member of
ordinator. Hub has connotations for BAN topology.
ethernet and USB hubs.
Change "document" to "standard"          Reject.                            0   Done

                                         Subclause 1 is taken from the
                                         TG6 PAR. Per IEEE
                                         document guidelines of 2009,
                                         scope purpose and need are
                                         to be included exactly as in the
                                         PAR. In addition, the existing
                                         text is correct as written as
                                         "this standard defines a
                                         standard" would not be
                                         appropriate.
Delete "802.15"                          Reject.                            0   Done

                                         Subclause 1 is taken from the
                                         TG6 PAR. Per IEEE
                                         document guidelines of 2009,
                                         scope purpose and need are
                                         to be included exactly as in the
                                         PAR.
Verify that the correct paragraph(s)     E.                                 0   Ok, but check
are being used here by checking the
2009 style guide.

Refer to 10.5.2 in the 2009 style        E.                                 0   Ok, but check
guide.
Delete "Connected_NID" and review        Accept in principle.               0   TODO
all definitions to make sure that they
apply to all standards and not just to   Create new glossary
this standard. For things that apply     subclause, add definitions to
to this standard, define the terms in    this new glossary subclause.
the Clauses. Review all the
definitions, probably at least half
should be removed from Clause 3.

This definition is an example of one     Accept in principle.               0   TODO
that should be deleted because it
has scope only in this standard.         Create new glossary
Also, it is wrong to have two terms      subclause, add definitions to
that mean the same thing. Delete         this new glossary subclause.
this definition and change all
occurrences of "hibernation" to
"inactive"
Delete "AES-128 CCM" and the             Accept.                            0   Done
acroread.
Some informative text on SAR          Reject.                            0   Done
reduction should be present in
annex or somewhere.                   Subclause 1 is taken from the
                                      TG6 PAR. Per IEEE
                                      document guidelines of 2009,
                                      scope purpose and need are
                                      to be included exactly as in the
                                      PAR.




change the use of the word "hub" in See S14-27                           0   Done
the document to "co-ordinator" in
the entire draft. The term "hub" does
not appropriate for a BAN co-
ordinator. Hub has connotations for
ethernet and USB hubs.
EFC(HBC) related description is       Accepted.                          0   Done
required.                             The following sentence has
                                      been inserted at the end of
                                      section 1.2: "Also, it considers
                                      using electrodes instead of the
                                      portable antennas, to use the
                                      human body as a transmission
                                      channel."


Change "impromptu" to                 Accept in principle.               0   Done
"improvised". Remove the last
sentence.                             TG6 considered numerous
                                      synonyms and found no better
                                      alternative to convey the
                                      intended meaning.

                                      Delete the final sentence of
                                      this definition.
Replace "Mbps" with "Mb/s" (here      Accept.                            0   Done
and throughout the document ->
search and replace)
Change "impromptu" to                 See S14-38                         0   Done
"improvised". Remove the last
sentence.
Change "impromptu" to                 See S14-38                         0   Done
"improvised". Remove the last
sentence.
Suggested remedy: Make details      Accept in principle.             0   Done
re RNG generation processes out
                                    Move two references (lines 19-
of scope and include references     20, 29) from subclause 2 to
as informative references only      Annex A, our informative
(after all, one also does not       bibliography.
stipulate how to provide side
channel resistance of
implementations of
cryptographic schemes!).




Suggested remedy: Define          TG discussed and agreed to         0   Done
concise set of acronyms that      proposed resolution (reject) of
                                  DCN 0676-00.
covers required functionality. No
need to refer to AES-128 CCM,
CBC, CMAC (cf. comments),
one of KMAC or MIC, and some
of the key types, my thinks.




                            DONE: 43
 LEFT: 0
TOTAL: 43
DEFER 0
Done - Same as S14-4
Ok, but check   Default text from template



Ok, but check
ID       Cate Pag Sub-
Number   gory e claus        Line #   Comment
S5-1     Edit 13   5                  Quite a few prescriptive shalls in Clause 5 were
         orial                        changed without any markup to descriptive tone
                                      (―shall do‖ changed to ―do‖). This clause
                                      specifies (high level) functional behaviors which
                                      need to be tested for interoperability. Once a
                                      ―shall do‖ is changed to a ―do‖, the behavior
                                      that is supposed to be tested for C&I will no
                                      longer be tested, thus resulting in
                                      interoperability issues.



S5-2     Edit    16 5.5.1.   14-15    Emphasize that all these frames are unsecured
         orial        2               frames.


S5-3     Edit    16 5.5.1.   23-24    Clarify explicitly that some of these frames are
         orial        3               unsecured frames, and some are secured
                                      fraems.




S5-4     Edit    16 5.5.1.    32      Clarify "as appropriate".
         orial        4

S5-5     Edit    16 5.5.1.     9      Use of first occurrence of an acronym (MK)
         orial        1               must be spelled out
S5-6     Edit    17 5.5.2.    12      Define "PTK"
         orial        2
S5-7     Edit    13   5               Quite a few prescriptive shalls in Clause 5 were
         orial                        changed without any markup to descriptive tone
                                      (―shall do‖ changed to ―do‖). This clause
                                      specifies (high level) functional behaviors which
                                      need to be tested for interoperability. Once a
                                      ―shall do‖ is changed to a ―do‖, the behavior
                                      that is supposed to be tested for C&I will no
                                      longer be tested, thus resulting in
                                      interoperability issues.



S5-8     Edit    16 5.5.1.   14-15    Emphasize that all these frames are unsecured
         orial        2               frames.
S5-9    Edit    16 5.5.1.   23-24   Clarify explicitly that some of these frames are
        orial        3              unsecured frames, and some are secured
                                    fraems.




S5-10   Edit    16 5.5.1.    32     Clarify "as appropriate".
        orial        4

S5-11   Edit    13   5              Quite a few prescriptive shalls in Clause 5 were
        orial                       changed without any markup to descriptive tone
                                    (―shall do‖ changed to ―do‖). This clause
                                    specifies (high level) functional behaviors which
                                    need to be tested for interoperability. Once a
                                    ―shall do‖ is changed to a ―do‖, the behavior
                                    that is supposed to be tested for C&I will no
                                    longer be tested, thus resulting in
                                    interoperability issues.



S5-12   Edit    16 5.5.1.   14-15   Emphasize that all these frames are unsecured
        orial        2              frames.


S5-13   Edit    16 5.5.1.   23-24   Clarify explicitly that some of these frames are
        orial        3              unsecured frames, and some are secured
                                    fraems.




S5-14   Edit    16 5.5.1.    32     Clarify "as appropriate".
        orial        4

S5-15   Edit    16 5.5.1.    28     The phrase "wakeup arrangement" is not listed
        orial        4              in clause 3.



S5-16   Edit    16 5.5.1.   13-15   Give the acronym of PTK at its first appearance
        orial        2
S5-17   Edit    13 5.2       14     "a relay capable node" should be "a relay-
        orial                       capable node".
S5-18   Edit    13   5.2    17     "Optional mechanisms for coexistence and
        orial                      interference mitigating between adjacent or
                                   overlapping BANs are provided." Please cite a
                                   subclause here, so the hapless reader doesn't
                                   have to flip through the document. Where are
                                   these mechanisms?
S5-19   Tec     13   5      1      Is clause 5 normative, or not? Usually it's not,
        hnic                       but there are "shall"s sprinkled through the
        al                         clause (e.g., p. 13, l. 9; p. 14, l. 27; p. 15, l. 4; p.
                                   16, l. 17; p. 17, l. 3; and p. 17, l. 16).



S5-20   Tec     14   5.3    10     "Both MAC SAP and PHY SAP are not exposed
        hnic                       and their specifications are beyond the scope of
        al                         this specification." Um, no. You could possibly
                                   make that case for the PHY SAP, but not for
                                   the MAC SAP, which is definitely exposed to
                                   the next higher layer (NHL). If the MAC SAP is
                                   not defined in the standard, how do you expect
                                   to achieve software interoperability? Unless the
                                   interface is standardized, a given NHL design
                                   won't work with the 15.6 MACs from two
                                   different vendors.

S5-21   Tec     13   5.2    12     There is no mMaxBANSizes in Table 23
        hnic
        al
S5-22   Tec     15   5.5    11     There are two items in the subject verb
        hnic                       agreement is not correct
        al
S5-23   Edit    13   5.2    10     reference H1, H2
        orial
S5-24   Tec     14   5.3    4      Figure 2 refenences the hub. No reference to
        hnic                       the node. However the MAC client is reference
        al

S5-25   Tec     14   5.3   2...2   Reference model Figure and text includes a
        hnic                       "Management Entity" that may or may not be
        al                         present and may or may not do something. No
                                   actual functionality or interfaces are identiified.
                                   Is this application level functionality or what is
                                   it? All required management information and
                                   interfaces should be defined as part of the
                                   standard, while application level functionalty
                                   should not be defined as part of the standard.



S5-26   Edit    13   5.2    12     Name of mMaxBANSizes variable is plural, not
        orial                      as listed in Table 23.
S5-27   Edit    14   5.4    23     Figure 3 has a vertical line representing end of
        orial                      beaon period (n+1) which is shorter than other
                                   similar vertical lines, for no apparent reason.

S5-28   Tec     15   5      15     Clause 5 should be an informative introduction.
        hnic                       Don't put detailed figures in Clause 5 that will
        al                         appear elsewhere. This repeats normative
                                   information that will lead errors in the draft.

S5-29   Edit    13   5.2    11     When it says "There is a hub in a BAN" it is not
        orial                      clear if this is intended to mean there is exactly
                                   one hub in a BAN. From context I think so but
                                   the text could better clarify.

S5-30   Edit    14   5.3    20     The allocation slots are numbered 0, 1, …. In
        orial                      Figure 3 the slots are numbered 0, 1, … s. The
                                   text could say 0, 1, … s also to be consistent
                                   and better delimit the sentence.
S5-31   Gen     13   5.3    20     There is no service primitives or management
        eral                       information base defined at all. Hence, NME or
                                   HME can not control other entities.




S5-32   Edit    13   5.2    15     In Fig.1, Is it possible to show 2-hop examples
        orial                      in the figure to match with the text?



S5-33   Tec     13   5.2           Can the hub act as a relay to nodes on its BAN,
        hnic                       i.e. Can the recipient and sender ID's be of leaf
        al                         nodes and used for node to node
                                   communication? This would be useful for
                                   certain consumer apps

S5-34   Tec     17   5.6   36-37   GTK description needs to align with 6.3.5 in
        hnic                       that the GTK distribution is hub to node and not
        al                         multicast as implied here


S5-35   Edit    15   5.5    5      Title not specific
        orial
S5-36   Tec 5.2   13   12-14   (TR) Clause 5.2, p. 13, l. 12-14: The
        hnic                   restriction that inter-node communication is
        al
                               not possible with a one-hop BAN is
                               unenforceable (any device can just open its
                               transmitter or receiver, and may not be
                               aware of the “device type” of the
                               communicating party). Moreover, the
                               current definition does not take into
                               account lifecycle aspects, where it may very
                               well be that the hub of the day is replaced
                               by another one over time, without
                               (hopefully) the network falling apart (after
                               all, that would be a medical emergency by
                               itself!). The same happened with 802.15.4-
                               2003/2006 at the time (RFD/FFD
                               distinction), but that is no reason to repeat
                               this unenforceable constraint here again.
                               Suggested remedy: Remove this
                               unenforceable restriction from the
                               specification.
S5-37   Tec 5.3   13   25-26   (TR) Clause 5.3, p. 13, l. 25-26: It is
        hnic                   suggested that key management
        al
                               functionality could be MAC functionality.
                               This is a clear layer violation, since
                               management functionality is higher-layer
                               end-to-end functionality. Besides, if this
                               would “live” at the MAC, then one would
                               have to specify the structure of keying
                               material, including key value, key
                               originator, key validity period, and other
                               attributes the MAC may not even know
                               about. With 802.15.3 standard, Paul
                               Nikolic ruled all this key management
                               functionality out of scope of WPAN efforts
                               (in March 2003). Suggested remedy:
                               Remove all key management functionality
                               (except for key usage) from the
                               specification.
S5-38   Tec 5.5    15   (TR) Clause 5.5, p. 15, Fig. 4: The state
        hnic            diagrams seem to be inconsistent, since the
        al
                        unsecured state diagram does not arise
                        easily from the secured one. Suggested
                        remedy: Define state diagram consistently,
                        so that unsecured state transitions are just
                        more lax than secured state transitions, but
                        certainly not inconsistent herewith.

S5-39   Tec 5.5.   16   (TR) Clause 5.5.1.1, p. 16: The order of
        hnic 1.1        association and authentication seems to be
        al
                        off: one would expect a device to first
                        associate (and thereby getting a temporary
                        lease of life to communicate and consume
                        resources) and, depending on whether
                        security is required, engage in additional
                        security protocols (e.g., to authenticate
                        itself, to set up a secure and authentic
                        channel to be used for key distribution or
                        for secure data transfer). Now, it seems that
                        a device can only get to an associated state
                        with master keys from orphan state. Why
                        not associate, followed by limited
                        allowance for unsecured traffic if frames in
                        question are related to some higher-layer
                        key agreement scheme?? Suggested
                        remedy: Redefine security model, so that
                        specific frames can only be communicated
                        if cryptographic keying material there and
                        security processing on frames used.
S5-40   Tec 5.5.   16   18   (TR) Clause 5.5.1.2, p. 16, l. 18: It is
        hnic 1.2             unclear whether “repealing” a security
        al
                             association is tied to aliveness/timeliness
                             guarantees. If not, the disassociation can be
                             replayed at a later moment in time (or
                             delayed, if recipient device temporarily
                             offline/asleep, etc.) Suggested remedy:
                             Please provide timeliness/aliveness with
                             this disassociation command.




S5-41   Tec 5.6    17   32   (TR) Clause 5.6, p. 17, l. 32: it is unclear
        hnic                 why encryption and authentication could
        al
                             not be provided for control frames, nor why
                             the actual combination of security services
                             provided should not be allowed to depend
                             on the frame type/subtype in question (and
                             potentially configured, depending on
                             application scenario at hand). Now, lots of
                             security services seem to be cast in stone,
                             irrespective of potentially widely varying
                             application scenarios. Suggested remedy:
                             Allow more flexibility as to particular
                             combination of security services offered
                             (e.g., what about more than 32-bit
                             authenticity tags?) and as to flexibility as
                             function of frame type in question. This
                             could easily be accommodated by indexing
                             the particular combination of security
                             services in the frame itself (or storing as
                             side information on recipient device). I
                             would be happy to help with this.
S5-42   Tec 5.6             39      (TR) Clause 5.6, l. 39: The notion of
        hnic                        “session” during which a temporal key is
        al
                                    valid is poorly explained. This seems to
                                    require a relative notion of time between
                                    communicating devices and, with keys, in
                                    general a more absolute notion of time.
                                    Suggested remedy: Please explain
                                    carefully. See also previous comment on
                                    timeliness and notion of time.
S5-43   Edit    15   5.5    20      figure caption should be plural
        orial
S5-44   Tec     15   5.5   Fig 4a   The figure 4a does not indicate what happens
        hnic                        when the device is in connected state and
        al                          receives Association (is this allowed so as to
                                    change the security level?).




S5-45   Tec     15   5.5   Fig4b    The figure 4b does not indicate what happens
        hnic                        when the device is in connected state and
        al                          receives Association , Disassociation, PTK or
                                    GTK frames

S5-46   Tec     23   5x     12      State diagrams, all the message exchanges are
        hnic                        for unicast communication. No information
        al                          about broadcasting is given. (Text above Figure
                                    4)
S5-47   Tec    15   5.4   1-Mar   (TR) Clause 5.4, p.15, l. 1-3: This suggests
        hnic                      only a relative notion of time, thereby not
        al
                                  facilitating security services, such as delay
                                  protection. The latter could be useful if one
                                  relays information at a later time in the
                                  network, with devices that were not around
                                  or asleep earlier on, just processing this,
                                  even if the frames in question may have
                                  “aged”. This could also be relevant in terms
                                  of keying material, which is now claimed to
                                  be valid during a “session” (Clause 5.6, p.
                                  17, l. 39), which seems to require a notion
                                  of time. Suggested remedy: Consider a
                                  more absolute notion of time, so as to
                                  facilitate detection of stale frames and stale
                                  data in tables.


                                                                                    DO
                                                                                     L
                                                                                   TO
                                                                                   DE
Proposed Change                              Resolution
Restore the original prescriptive shalls and Accept in principle.                 0
mays.
                                             Editorial - subclause 5 to be not
                                             normative (descriptive). Subclause
                                             6 and others to be prescriptive.




Change the comma in line 14 to "and",      E.                                     0
add "unsecured frames" before the 1st
comma in line 15, and add after this
comman "as well as".
Change the comma in line 23 to "and",      E.                                     0
add "unsecured frames" before the 1st
comma in line 15, and add after this
comma "as well as". Further change
"control unsecured frames" to "control
secured or unsecured frames depending
on whether control frame authentication
was selected during their association".
Change "as appropriate" to "if control     E.                                     0
frame authentication was not selected
during their association".
Insert Master Key                          E.                                     0

                                           E.                                     0

Restore the original prescriptive shalls and See S5-1.                            0
mays.




Change the comma in line 14 to "and",      E.                                     0
add "unsecured frames" before the 1st
comma in line 15, and add after this
comman "as well as".
Change the comma in line 23 to "and",        E.                                    0
add "unsecured frames" before the 1st
comma in line 15, and add after this
comma "as well as". Further change
"control unsecured frames" to "control
secured or unsecured frames depending
on whether control frame authentication
was selected during their association".
Change "as appropriate" to "if control       E.                                    0
frame authentication was not selected
during their association".
Restore the original prescriptive shalls and See S5-1.                             0
mays.




Change the comma in line 14 to "and",          E.                                  0
add "unsecured frames" before the 1st
comma in line 15, and add after this
comman "as well as".
Change the comma in line 23 to "and",          E.                                  0
add "unsecured frames" before the 1st
comma in line 15, and add after this
comma "as well as". Further change
"control unsecured frames" to "control
secured or unsecured frames depending
on whether control frame authentication
was selected during their association".
Change "as appropriate" to "if control         E.                                  0
frame authentication was not selected
during their association".
Add a definition of "wakeup arrangement "      TG discussed and agreed to reject   0
to clause 3. It is an important concept that   this comment.
deserves a definition.
                                               No special meaning for "wakeup
                                               arrangement" in this document.
Give the acronym of PTK at its first           See S5-6.                           0
appearance
Make it so.                                    E.                                  0
Add citation.                               E.                                     0




If it's a normative clause, there should be See S5-1.                              0
a boatload more "shall"s in the text
(substantally every sentence). If it's not a
normative clause, the "shall"s listed in this
comment should be removed, and
replaced with "could", "may", "is", or some
other non-mandatory wording.
Define and specify the MAC SAP.               TG discussed and agreed to reject    0
                                              this comment.

                                            MAC SAP is clearly specified as
                                            being beyond the scope of this
                                            document. Including abstract
                                            primitives will not provide any
                                            additional detail beyond the details
                                            already included in the document.



Correct term by deleting the final "s" to   Accept. Editorial comment.             0
agree with the name in Table 23

Change is to are                            Accept. Editorial comment.             0


Add respective hubs "(H1, H2)"              E.                                     0

Add reference to node, and remove           Accept in principle.                   0
"client" or define the node as the client
                                            Change "MAC client" to "MAC client
                                            (higher layer)"
Either remove the Management Entity or      TG discussed and agreed to reject      0
clarify its bounds, functionality and       this comment.
interfaces.
                                            This comment is out of scope as
                                            specified in the text.
                                            "However, the presence of the NME
                                            or HME and the partitioning between
                                            the NME or HME and the MAC or
                                            the PHY is not 15 mandated, nor is
                                            the behavior of the NME or HME
                                            specified, in this standard."

Change to "mMaxBANSize".                    E.                                     0
Extend vertical line marking end of beacon E.                                   0
period (superframe) n+1 to be of same
size as other, similar lines in the figure.

Delete Figure 4.                          See S5-1.                             0




Clarify.                                  E.                                    0




Change to 0, 1, … s.                      E.                                    0



Service primitives or MIBs are useful     TG discussed and agreed to reject     0
interfaces to manage other entites.       this comment.
Probably BAN specification can leverage
these interfaces as well. Define such     MAC parameter tables are already
interfaces to make clear what kind of     provided.
parameters can be manageable from
external entities.
Add examples of 2-hop                     TG discussed and agreed to reject     0
                                          this comment.

                                          Two hop extended topology is
                                          described in 7.9.
                                          TG discussed and agreed to reject     0
                                          this comment.

                                            No actionable change is proposed
                                            related to two hop extended
                                            topology.
Clarification may be required to indicate   TG discussed and agreed to accept   0
that the GTK is sent to potential members this comment.
of the multicast group (to be created) in a
unicast manner.                             Change implemented in DCN 0679-
                                            00.
Rename title to MAC State Diagram           E.                                  0

                                          Change to "MAC and Security State
                                          Diagrams"
Suggested remedy: Remove this              Reject.                                  0
unenforceable restriction from the
specification.                             This text specifies the normative
                                           behavior of the BAN topology using
                                           "may". Such behavior as described
                                           by the comment could occur but
                                           would not be normative.




Suggested remedy: Remove all key           TG discussed and agreed to reject        0
management functionality (except for key   this comment.
usage) from the specification.
                                           (1) What is suggested is key
                                           generation, not key management.
                                           No key management functionality is
                                           specified in this draft. (2) Key
                                           generation is extensively specified in
                                           IEEE 802.11, throught IEEE 802.11i
                                           and 802.11s.
Suggested remedy: Define state diagram       TG discussed and agreed to reject         0
consistently, so that unsecured state        this comment.
transitions are just more lax than secured
state transitions, but certainly not         It is already the case the unsecured
inconsistent herewith.                       state transitions are more lax than
                                             secured state transitions - the
                                             former does not go through the two
                                             middle states which the latter has to
                                             go through.


Suggested remedy: Redefine security          TG discussed and agreed to reject         0
model, so that specific frames can only be   this comment.
communicated if cryptographic keying
material there and security processing on    There is not a separate
frames used.                                 authentication state. Entity
                                             authentication, if required, is part of
                                             security association. All traffic is
                                             indeed unsecured until the Secured
                                             state is reached, as explicitly stated
                                             in 5.5.1.1, 5.5.1.2 and 5.5.1.3.
Suggested remedy: Please provide               TG discussed and agreed to reject        0
timeliness/aliveness with this                 this comment.
disassociation command.
                                               Replay is not an issue here, since
                                               once a node is disassociated a
                                               replay of an earlier Security
                                               Association frame would be simply
                                               ignored - the node and the hub are
                                               already disassociated from each
                                               other. If the node and the hub re-
                                               associate and, hence, establish a
                                               new master key, a replay of an
                                               earlier Security Association frame
                                               based on a repealed key would fail
                                               the security check with the new
                                               master key. In summary,
                                               aliveness/timeliness is provided by
                                               possession of the valid master key.


Suggested remedy: Allow more flexibility       TG discussed and agreed to reject        0
as to particular combination of security       this comment.
services offered (e.g., what about more
than 32-bit authenticity tags?) and as to      (1) Authentication is provided for
flexibility as function of frame type in       control type frames – as is stated by
question. This could easily be                 lines 31-32 (a node and a hub jointly
accommodated by indexing the particular        select … whether to require
combination of security services in the        authentication for control frames.
frame itself (or storing as side information   Encryption of control type frames is
on recipient device). I would be happy to      not needed, since some of them do
help with this.                                not have a frame payload and
                                               hence would not be encrypted
                                               anyway. (2) The widely used IEEE
                                               802.11i approach of having a fixed
                                               length authentication tag is followed
                                               in this draft. (3) Control type frames
                                               do have a choice of being secured
                                               or not, so security service is already
                                               a function of frame type/subtype
Suggested remedy: Please explain             TG discussed and agreed to reject      0
carefully. See also previous comment on      this comment.
timeliness and notion of time.
                                             (1) The explanation is technically
                                             valid. (2) The suggested remedy
                                             does not offer an improved or
                                             specific explanation.




change diagram to diagrams                   E.                                     0

Add state transition for Association (or   Reject.                                  0
remove from all frames except statement).
Also adding arrowheads outwards from       The proposed change is already
the associated/secured states for security shown in Figure 4a.
disassociation would clarify that
disassociation causes the connected state
to change to orphan for a disassociation

Remain in connected state (and remove        Reject.                                0
"the all frames except....." statement) or
was the intention to transition state to     Text of this section specifies that
orphan (in which case show this)             such frames are not allowed to be
                                             transmitted at this state.
Insert state diagram for broadcast           Reject.                                0
scenario. Can it be secure ?
                                             Broadcast can be secure once all
                                             individual nodes have completed
                                             their secure connection, as shown in
                                             Figure 4.
                                             See S5-34.
Suggested remedy: Consider a more            TG discussed and agreed to reject      0
absolute notion of time, so as to facilitate this comment.
detection of stale frames and stale data in
tables.                                      (1) The time reference alluded to in
                                             the comment is for medium access.
                                             (2) No absolute notion of time is
                                             identified to be needed for the
                                             security services specified in this
                                             draft.




                                    DONE:    47
                                     LEFT:   0
                                   TOTAL:    47
                                   DEFER     0
  ID   Categ Pag Sub- Lin             Comment                           Proposed Change           Must
Numbe ory      e clau e #                                                                          Be
   r
S6-001 Editori     se
               21 6.2. 15- This comment applies to many                                           Satis
                                                                 Would the technical editor make Yes
       al         1.1. 18 places (especially in the MAC          the following formatting changes
                  4        and security clauses) in the          please? Convert the remaining
                           draft. Many, but not all,             unnumbered bullets into
                           unnumbered bullets have been          numbered ones, whenever
                           converted to numbered ones.           reasonable.
                           Need to be consistent.




S6-002 Editori   22 6.2. 4    Typo.                              Move "not" to before the first       Yes
       al           1.1.                                         "enabled" in this line.
                    6


S6-003 Editori   22 6.2. 15   Formatting glitch.                 Capitalize the first letter of "type" Yes
       al           1.1.                                         and "subtype".
                    8
S6-004 Editori   22 6.2. 15   This comment applies to            Would the technical editor make Yes
       al           1.1.      numerous tables. (1) These         the following formatting changes
                    8         tables are a bit crowded. (2)      please? (1) Increase the
                              The first row needs cleared        spacing between rows for all
                              alignment. (3) the position of     these similar tables. (2) Make
                              some entries need to be            "b4b5" or similar bit designations
                              adjusted closer to the center.     a separate row from "…value" in
                                                                 the first row of all these similar
                                                                 tables. (3) Move the numbers in
                                                                 the first columns and similar
                                                                 columns (from second row on)
                                                                 closer to the center of the
                                                                 column in all these similar tables.

S6-005 Editori   22 6.2. 15   Internal horizontal lines should   Thin the internal horizontal lines   Yes
       al           1.1.      be thinner.                        below the 2nd row.
                    8
S6-006 Techni    22 6.2. 15   The Wakeup frame provides no       Remove the row of "Wakeup"        Yes
       cal          1.1.      more functionality and             frame from Table 3, subclause
                    8         effectiveness than the Poll        6.4.7 and subclause 7.8.2.1.1
                              frame, as explained in detail in   (which should have never
                              some related comments.             appeared). Accordingly, change
                                                                 "1011" to "0111" in the preceding
                                                                 row (for reserved frame subtype
                                                                 values of control type frames).
S6-007 Editori   23 6.2. 35   Unwarranted capitalization.       Change "Field" to "field" before    Yes
       al           1.1.                                        "encoding".
                    10




S6-008 Editori   24 6.2. 40   Duplicate bullet number.          Delete "6." at the start of the text. Yes
       al           1.1.
                    11
S6-009 Techni    25 6.2. 12  The Coexistence field can be       After "Coexistence format", add     Yes
       cal          1.1.     reused to define some fields for   "for beacon frames".
                    12       B2 frames as well (as noted in
                             another comment).
S6-010 Techni    25 6.2. 14- Use backward coding for the        (1) In lines 14 and 20, change      Yes
       cal          1.1. 24 Fragment Number field, so that      "first" to "final". (2) In lines 17
                    12       the recipient knows if the last    and 22, delete "non-first". (3) In
                             received fragment is the last      line 18, change "incremented by
                             one of an MSDU or a                one from its value" to "set to the
                             management frame.                  number of the fragments of the
                                                                frame payload minus one in the
                                                                frame containing the first
                                                                fragment, and is decremented by
                                                                one successively". (4) In lines
                                                                19 and 24, change "previous" to
                                                                "next". (5) In line 23, change
                                                                "incremented by one from its
                                                                value" to "set to the number of
                                                                the fragments of the MSDU
                                                                minus one in the frame
                                                                containing the first fragment, and
                                                                is decremented by one
                                                                successively".
S6-011 Techni   26 6.2. 3   Define the Coexistence field for   (1) Insert a new numbered bullet Yes
       cal         1.1.     B2 frames, so that some fields     before this line, with the following
                   12       don't need to appear in the        text: h) In B2 frames, it is used
                            frame payload.                     as a Coexistence field, which is
                                                               formatted as shown in a new
                                                               figure. The BAN Priority field is
                                                               set according to a new table to
                                                               indicate the priority of the
                                                               services provided to the BAN of
                                                               this hub. (2) Insert a new figure -
                                                               Coexistence format for B2
                                                               frames, defining two fields:
                                                               b0b1 for BAN Priority and b2b3
                                                               for Reserved. (3) Insert a new
                                                               table - BAN Priority field
                                                               encoding, defining 4 field values
                                                               0-3 and 4 corresponding BAN
                                                               services: Highest priority medical
                                                               services, general health
                                                               services, mixed medical and non-
                                                               medical services, non-medical
                                                               services.
S6-012 Editori   26 6.2. 15   This comment applies to many Restore all instances of "shall" to Yes
       al           2         places of Clause 6. While          "must" throughout Clause 6.
                              Clause 7 is written in
                              prescriptive style (shall, should,
                              may) to specify MAC functional
                              behaviors, Clause 6 is written in
                              descriptive style (…field IS set
                              to…) to define MAC frame
                              formats. This clause originally
                              had a few musts that were
                              intentionally spelled out that
                              way; they were all changed to
                              shalls in D0. There are two
                              potential concerns with the
                              change: (a) ―shall‖ does not
                              necessarily convey the same
                              meaning or intent of ―must‖.
                              Example (page 32, lines 11-12):
                              ―The Control Frame
                              Authentication field is set to one
                              if control type frames sent from
                              or to this sender SHALL be
                              authenticated‖. (b) These shalls
                              are inconsistent with the style of
                              Clause 6 which is meant to be
                              descriptive but not prescriptive.




S6-013 Editori   27 6.2. 15   This comment applies to most         Would the technical editor       Yes
       al           2.2       paragraphs following a bulleted      please adjust the spacings to be
                              item in the draft (especially in     a bit more uniform for all these
                              the MAC and security clauses).       similar instances of the draft?
                              There is a big space between
                              the (typically short) paragraph
                              and the next line of the following
                              set of bulleted paragraphs, but
                              only a small space between the
                              last bulleted paragraph and the
                              next one. However, the
                              preceding paragraph is often
                              more closely related to the
                              bulleted items than the
                              paragraph that follows those
                              items is in their meaning.

S6-014 Editori   27 6.2. 17   Comma misplaced. Did                 Move the comma from before to Yes
       al           2.2       reformatting in D0 generate          after Figure 12.
                              other misplaced commas?
S6-015 Editori   29 6.3. 16   "not" misplaced.                   Move "not" to before the first     Yes
       al           1.4                                          "enabled" in this line.

S6-016 Editori   29 6.3. 28   "not" misplaced.                   Move "not" to before the first     Yes
       al           1.6                                          "enabled" in this line.

S6-017 Editori   32 6.3. 1-9 Simplify naming.                     (1) Delete "Required" from the      Yes
       al           2.3                                           "Security Level Required" field in
                                                                  Figure 18. (2) In lines 7-8,
                                                                  delete "Required". (3) In Table
                                                                  6's heading, change "required" to
                                                                  "Level".
S6-018 Editori   32 6.3. 6    This comment applies to many Technical Editor, would you                Yes
       al           2.3.      tables in Clause 6. "Field value please insert "in" before
                    1         decimal"…                           "decimal" J71and make "in
                                                                  decimal" in a separate line in this
                                                                  and other similar tables?
S6-019 Editori   32 6.3. 15   "Protocol" is not part of the field Delete "Protocol" from the          Yes
       al           2.3.      anymore.                            heading.
                    4
S6-020 Editori   43 6.3. 1    Formatting glitch.                 Make the two internal lines        Yes
       al           7.3                                          (below the 2nd row) thinner.

S6-021 Techni    45 6.3. 1-2 There are some inconsistencies      (1) Remove the B+EAP1 Length Yes
       cal          8        between this frame and the          and EAP2 Length fields. (2)
                             Connection Assignment frame         Move the Status Code field into
                             in 24 on which this frame is        the Node Connection
                             based.                              Assignment IE. (3) Change the
                                                                 length bound for the Node
                                                                 Connection Assignment IE fields
                                                                 to 15.
S6-022 Editori   46 6.3. 20   Unwarranted capitalization.        In the table heading, change    Yes
       al           11.3                                         "Field" to "field".

S6-023 Techni    46 6.3. 20   (1) The frame formats of these     (1) Change "Request" to "Time Yes
       cal          11.3      two coexistence commands           Sharing". (2) Change "Command
                              were never discussed, let alone    - Coexistence Response" to
                              approved, in the MAC subgroup.     "Reserved".
                              (2) At most only one command
                              for coexistence is need, as
                              explained in another comment.

S6-024 Editori   47 6.3. 1-22 6.3.11.4.1 should be a parent      Promote 6.3.11.4.1 to one level Yes
       al           11.4      subclause of the three             higher as 6.3.12, and keep the
                    .1        subclauses that follow, instead    subclauses that define the fields
                              of being at the same level.        of this command at current level.
S6-025 Techni   47 6.3. 1    There is no functional difference   Change "Command -             Yes
       cal         11.4      specified for "coexistence          Coexistence Request" to
                   .1        request" and "coexistence           "Command - Coexistence Time
                             response". Hence no two             Sharing".
                             separate frames are needed.

S6-026 Techni   47 6.3. 2-6 These lines need to be revised (1) Change "in" to "for" before "a Yes
       cal         11.4      in view of the changes made to Command". (2) Insert "time
                   .1        the frame defined here.           sharing enabled" before "hub" (2
                                                               instances). (3) Change "to
                                                               request coexistence on the
                                                               same physical channel" to
                                                               "convey certain coexistence
                                                               information". (4) Change
                                                               "Request" to "Time Sharing" in
                                                               the figure caption.
S6-027 Techni   47 6.3. 1-22 (1) Both the definition and table (1) Change "Piconet Priority" to Yes
       cal         11.4      for "Piconet priority" needed to "BAN Services", a new field
                   .1        be reworked to be consistent in proposed in the Coexistence
                             naming and format with other      field of the MAC header of B2
                             sections. (2) There is no         frames. Accordingly, change the
                             difference in functional          definition to "The BAN Services
                             behaviors between "time           field is as defined in 6.2.1.1.12
                             sharing" and "offset piconet      h) and Table 4" (which were
                             synchronization" -- both of which proposed for B2 frames). (2)
                             cannot require superframe         Remove the "coexistence mode"
                             boundary synchronization          field in Figure 29, subclause
                             between networks. There is no 6.3.11.4.3 which was misspelled
                             functional description for        as "coexistence response", and
                             "piconet enquiry". Therefore,     Table 11. (3) Change "Allocation
                             there is no functional use of the Time /duty cycle" in both Figure
                             "coexistence mode" field. (3)     29 and 6.3.11.4.4 to "Allocation
                             The Allocation Time / Duty        Percentage", and change the
                             Cycle field essentially has the   definition to the following: The
                             same definition under both "time Allocation Percentage field is set
                             sharing" and "offset piconet      to P such that this hub is to use
                             synchronization" modes. It just an aggregate allocation of up to
                             means the percentage of the       4×P % of the total time on its
                             total allocation of one network. operating channel for its body
                                                               area network (BAN). (4) Delete
                                                               Table 12 (mislabeled as
                                                               "coexistence modes").
S6-028 Techni    48 6.3. 3-20 These are just duplicates of the Remove them along with the             Yes
       cal          11.5      subclauses for the "Coexistence figure and table within.
                    (b)       Request" version, except for the
                              "status" field, which, however, is
                              meaningless. There is no
                              functional difference specified
                              for "coexistence request
                              accepted" and "coexistence
                              request rejected". In particular,
                              what does the acceptance or
                              rejection of a coexistence
                              request by network 2 mean to
                              network 1 that made the
                              request? Nothing in either
                              case.

S6-029 Techni    49 6.3. 1-16 Incorrect level for these three        Promote 6.3.11.5.4 to one level Yes
       cal          11.5      subclauses.                            higher, and keep the two
                    .4                                               subclauses that define the fields
                                                                     of this command at the current
                                                                     level.
S6-030 Techni    49 6.3. 17    Incorrect level for this              Promote 6.3.11.5.7 to one level Yes
       cal          11.5       subclause.                            higher.
                    .4
S6-031 Editori   49 6.3. 2     Incorrect level for this              Change "in" to "for" before "a   Yes
       al           11.5       subclause.                            Command".
                    .4
S6-032 Techni    52 6.4. 5     (1) locally broadcast but not         (1) Change "multicast" to         Yes
       cal          6.4        locally multicast. (2) the field is   "broadcast" in line 5. (2) Reword
                               set…, but not the relay node will     the 2nd and 3rd sentences for
                               set this field.                       stylistic consistency with other
                                                                     sections.

S6-033 Techni    52 6.4. 4-8 The "received signal strength of        Remove the Relay Link Quality Yes
       cal          6.4      signals" does not truly reflect         field and all references to it,
                             the quality of the link in              unless the proposers provide a
                             presence of noise and                   revised text that addresses this
                             interference.                           fundamental issue. Note that the
                                                                     field value must be "absolute" in
                                                                     the sense that all devices will
                                                                     generate the same value
                                                                     independent of their internal
                                                                     calibration levels they used in
                                                                     estimating that value.
S6-034 Techni 52-   6.4.      (1) Many fields are already         (1) Remove all fields and their    Yes
       cal    53    8         contained in the beacon or the      definition subclauses (and Table
                              MAC header of the B2 frame,         13 which has already appeared
                              and should not be duplicated        earlier), except the "Reserved
                              here, per the discussion at the     slots" and "NID" fields. (2)
                              last IEEE meeting. In particular,   Rename "Reserved slots' as
                              the Beacon Period Length and        "Earliest Next B2", and reword its
                              Allocation Slot Length fields are   definition as follows: The
                              verbatim duplicates from the        Earliest Next B2 field is set to E
                              beacon. The CAP Length field        such that the earliest next B2
                              is equivalent to the Sequence       time occurs not earlier than the
                              Number / Poll-Post Window           end of the allocation slot
                              field of the MAC header of the      numbered E in the next beacon
                              B2 frame, as the latter field       period (superframe). (3) Restore
                              encodes the end time of CAP         the definition subclause for the
                              (and B2's end time is the start     NID field, with the following
                              time of CAP). The Offset to         definition: One or more NID
                              Start Time field value is readily   fields are optionally present.
                              calculated from the B2 and          When present, each NID field is
                              beacon transmission times.          set to the NID of a node from
                              The Piconet Priority field is now   which this hub received a frame
                              defined as the BAN Services         requiring group acknowledgment
                              field, which is part of the         since the last transmitted B2
                              Coexistence field of the MAC        frame.
                              header of the B2 frame. The
                              beacon frame is easier to
                              receive since it is sent at known
                              times, and has more information
                              useful or desirable for
                              coexistence. Thus it would be a
                              backward step to copy some
                              fields from the beacon into the
S6-035 Editori   57 6.6. 11   B2 and then have coexistence
                              Typo.                               Change "rage" to "rate" in the    Yes
       al           2.3                                           table heading.

S6-036 Editori   57 6.6. 11   Formatting glitch.                  Make the two internal lines       Yes
       al           2.3                                           (below the 2nd row) thinner.

S6-037 Editori   57 6.6. 13   Two much space.                     Delete this empty line.           Yes
       al           2.3

S6-038 Editori   58 6.7. 5    Some clarification is needed on Change "to indicate ..lengths" to Yes
       al           1         why and when this IE is         "foretell some information on the
                              included.                       superframe (beacon period)
                                                              structure that is contained in
                                                              beacons which are not being
                                                              transmitted frequently or at all"
S6-039 Techni    58 6.7. 6   If superframe length and            Add to the end of the current IE   Yes
       cal          1        allocation slot length fields are   an optional "Beacon Shifting
                             needed to be separately             Sequence" field.
                             included, so is the beacon
                             shifting sequence field when
                             beacon shifting is enabled.
S6-040 Editori   58 6.7. 10- Avoid repeating a definition that    Change these two lines to the     Yes
       al           1.1 11 is already given somewhere             following: The Superframe
                             else.                                Length field is as defined in
                                                                  6.3.1.2 for the Beacon Period
                                                                  Length field.
S6-041 Editori   59 6.7. 3      Avoid repeating a definition that Change these two lines to the     Yes
       al           1.2         is already given somewhere        following: The Allocation Slot
                                else.                             Length field is as defined in
                                                                  6.3.1.3.
S6-042 Editori   59 6.7. 13     Figure formatting glitch.         Insert two dashed lines at the    Yes
       al           2                                             start of the bottom fields to
                                                                  indicate continuation from the
                                                                  top fields.
S6-043 Editori   61 6.7. 15     Figure formatting glitch.         Insert two dashed lines at the    Yes
       al           5                                             start of the bottom fields to
                                                                  indicate continuation from the
                                                                  top fields.
S6-044 Techni    66 6.7. 5      The "Status Code" field now in Insert a one-octet "Status Code"     Yes
       cal          11          the Multinode Connection          field after the "Node Address"
                                Assignment frame should be        field.
                                defined on a per node basis and
                                hence should be moved here.

S6-045 Techni    66 6.7. 8-9 Inconsistent frame reference.       Change the paragraph to "All the Yes
       cal          11                                           fields after the Length field
                                                                 pertain to the same node and
                                                                 are defined as in 6.3.7 for
                                                                 Connection Assignment frames,
                                                                 except the Node Address field
                                                                 which is set to the IEEE MAC
                                                                 address of the node."

S6-046 Techni    52 6.4. 4-8 The use of a signal strength to     Remove the "Relay Link Quality" Yes
       cal          6.4       define the link quality is         field or find another way to
                              questionable. This field cannot    measure the link quality.
                              be used in a reliable way in
                              presence of noise or
                              interference
S6-047 Editori   22 6.2.    3 "exclusieve" should be             See comment.                       Yes
       al           1.1.      "exclusive"
                    6

S6-048 Editori   22 6.2.      4 "curren" should be "current"     See comment.                       Yes
       al           1.1.
                    6
S6-049 Editori   23 6.2.   15 missing "it"                         Change "...when the hub is to     No
       al           1.1.                                           send a post to the node is
                    9                                              indicated in…" to "...when the
                                                                   hub is to send a post to the node
                                                                   it is indicated in…"
S6-050 Editori   22 6.2.    3 exclusieve is misspelled             correct                           Yes
       al           1.1.
                    6
S6-051 Editori   22 6.2.    4 curren is misspelled                 correct                           Yes
       al           1.1.
                    6
S6-052 Editori   22 6.2.    5 Table 3 header row, add          Table 3 header row, add          No
       al           1.1.      carriage return so that b0 is on carriage return so that b0 is on
                    8         the same line with b1 b2 and b3 the same line with b1 b2 and b3

S6-053 Techni    24 6.2.   40 What is the 6. Doing on this         Delete                            Yes
       cal          1.1.      line?
                    11
S6-054 Techni    30 6.3.   16 Table 4 third column is named        Select one term                   Yes
       cal          1.10      Beacon Shifting Sequence
                    .2        pattern, while the text states
                              Beacon Shifting Sequence
                              Phase terms do not agree.




S6-055 Techni    30 6.3.   19 The text states that this field is   Insert another field in Figure 14, Yes
       cal          1.11      present only if the channel          which indicates whether the
                              hopping is currently enabled as      Channel Hopping State will be
                              encoded according to Figure 14.      included.
                              This is a self reference because
                              there is no other field stating if
                              channel hopping is enabled.

S6-056 Techni    31 6.3.   15 The length of the Security           Correct inconsistency by          Yes
       cal          2         Association Date field in Figure     changing greater than or equal
                              17 is marked greater than or         to 0 to 72
                              equal to 0, however in Figure 19
                              page 19 the field is fixed with a
                              size of 72.
S6-057 Techni    32 6.3.   15 Header is not consistent with        Delete Protocol                   Yes
       cal          2.3.      name in Figure 18
                    4
S6-058 Editori   34 6.3.   28 Use subscript for the Y              Beacon Shifting Sequence          Yes
       al           2.6.
                    2

S6-059 Techni    36 6.3.   15 Wrong level of indent                Change level of indent to same    Yes
       cal          3.2.                                           as the other four fields from
                    1                                              figure 20
S6-060 Techni    36 6.3.   19 Wrong level of indent                Change level of indent to same    Yes
       cal          3.2.                                           as the other four fields from
                    2                                              figure 20
S6-061 Techni    37 6.3.   18 Is this index a single bit or        Fix inconsistency                 Yes
       cal          4.4       multiple bits? Line 18 indicates
                              that one can subtract 1 for the
                              value, while line 22 indicates
                              that it has a value of zero or one
                              only.
S6-062 Techni    38 6.3.   26 Is this index a single bit or        Fix inconsistency                 Yes
       cal          5.4       multiple bits? Line 18 indicates
                              that one can subtract 1 for the
                              value, while line 22 indicates
                              that it has a value of zero or one
                              only.
S6-063 Techni    41 6.3.   12 Why is there a need to code          Delete entire sentence            Yes
       cal          6.8       256 as zero, when this is a 2
                              byte field allowing for the coding
                              of 256 naturally?
S6-064 Techni    43 6.3.   18 Cross reference is wrong. It         Correct cross reference and       Yes
       cal          7.10      points to a 1-bit Wakeip Phase       guarantee that there is
                              field, not a 2-octet Wakeup          uniqueness in field naming.
                              Phase field as in 6.3.6.7

S6-065 Techni    44 6.3.    2 Cross reference is wrong. It         Correct cross reference and       Yes
       cal          7.11      points to a 1-bit Wakeip Period      guarantee that there is
                              field, not a 2-octet Wakeup          uniqueness in field naming.
                              Period field as in 6.3.6.8

S6-066 Techni    44 6.3.   18 Cross reference is wrong.            Change 6.7.11 to 6.7.12           Yes
       cal          7.18

S6-067 Techni    45 6.3.    1 Figure 26 contains two fields        Properly define the missing fields Yes
       cal          8         that are not defined in 6.3.7        (B+EAP1 Length, EAP2 Length)

S6-068 Techni    47 6.3.    8 Wrong level of indent                Indent level should be one lower Yes
       cal          11.4                                           than the Command it is part of
                    .2                                             6.3.11.4.1.1


S6-069 Techni    47 6.3.   14 Wrong level of indent                Indent level should be one lower Yes
       cal          11.4                                           than the Command it is part of
                    .3                                             6.3.11.4.1.1
S6-070 Techni    47 6.3.   14 Header is title wrong               Change to Coexistent Mode          Yes
       cal          11.4
                    .3


S6-071 Techni    47 6.3.   22 Inconsistency with name of field Change data rate to duty cycle to Yes
       cal          11.4                                       agree with the field name in
                    .4.                                        Figure 29
S6-072 Techni    48 6.3.    1 Table 12 column three is         Change data rate to duty cycle to Yes
       cal          11.4      inconsistent with Figure 29 and agree with the field name in
                    .4        clause heading                   Figure 29
S6-073 Editori   48 6.3.    3 Wrong level of indent and        Indent level should be five (I.e. Yes
       al           11.5      lettering                        6.3.11.4.2)
                    (b)


S6-074 Editori   48 6.3.   10 Wrong level of indent               Indent level should be one more Yes
       al           11.5                                          than the frame that it belongs to
                    .1


S6-075 Techni    48 6.3.   11 Lacks indication for setting the 1- Add missing setting                Yes
       cal          11.5      bit field for accepted or rejected
                    .1
S6-076 Editori   48 6.3.   12 Wrong level of indent               Indent level should be one more Yes
       al           11.5                                          than the frame that it belongs to
                    .2


S6-077 Techni    48 6.3.   13 This is a 2-bit filed not a 1-bit   Insert 2-, to make a 2-bit field to Yes
       cal          11.5      field                               agree with figure 30
                    .2


S6-078 Editori   48 6.3.   15 Wrong level of indent               Indent level should be one more Yes
       al           11.5                                          than the frame that it belongs to
                    .3


S6-079 Techni    48 6.3.   19 Table 13 header row in not          Change data rate to duty cycle to Yes
       cal          11.5      consistent with field name in       agree with the field name in
                    .3        figure 30                           Figure 30
S6-080 Editori   49 6.3.    1 Wrong level of indent               Level should be at the same       Yes
       al           11.5                                          level as the other command
                    .4                                            frames (I.e., 6.3.11.4.3


S6-081 Editori   49 6.3.    9 Wrong level of indent               Level should be one more than Yes
       al           11.5                                          the command frame that this
                    .5                                            field is part of (I.e., 6.3.11.4.3.1)
S6-082 Editori   49 6.3.   12 Wrong level of indent            Level should be one more than Yes
       al           11.5                                       the command frame that this
                    .6                                         field is part of (I.e., 6.3.11.4.3.2)

S6-083 Editori   49 6.3.    2 Add space between 31 and in      Add space between 31 and in      Yes
       al           11.5
                    .4


S6-084 Editori   49 6.3.   17 Wrong level of indent            Level should be at the same      Yes
       al           11.5                                       level as the other command
                    .7                                         frames (I.e., 6.3.11.4.4
S6-085 Techni    50 6.4.    5 Figure 32 the frame status       Replace 0, 1, .. With L-R        Yes
       cal          2         bitmap uses 0, 1, … instead of L-
                              R
S6-086 Techni    53 6.4.    1 Figure 35 has Piconet priority as Fix inconsistency               Yes
       cal          8         a 1-bit, while text of 6.4.8.6
                              states that it is a 2-bit field

S6-087 Techni    53 6.4.    1 Figure 35 has a beacon period Fix inconsistency                   Yes
       cal          8         length as a 1-bit, but the text of
                              6.4.8.1 indicates more than one
                              bit, especially if it is a length
                              field
S6-088 Techni    53 6.4.   11 There is no minCAP in Table        Define minCAP                  Yes
       cal          8.3       23, 24, or 25

S6-089 Techni    54 6.4.    7 What is a coordinator? There is Replace coordinator with hub      Yes
       cal          8.7       no such term in this document


S6-090 Techni    54 6.4.    9 What is a coordinator? There is Replace coordinator with hub      Yes
       cal          8.8       no such term in this document

S6-091 Techni    54 6.4.    9 What are coordinators? There     Replace coordinators with hubs   Yes
       cal          8.8       is no such term in this
                              document

S6-092 Techni    54 6.4.   10 There is no description of the   Insert the missing description of Yes
       cal          8.8A      NID 1-bit fields                 the 1-bit NIDs



S6-093 Techni    56 6.6.   14 Test is not consistent with      Insert hub, to make Relayed      Yes
       cal          1.12      header                           Hub/Node

S6-094 Techni    64 6.7.   14 Header does not agree with the Change Uplink to Downlink          Yes
       cal          8         text

S6-095 Techni    64 6.7.   21 Header does not agree with the Change Uplink to Bilink            Yes
       cal          10        text
S6-096 Techni    66 6.7.    5 Text states that the fields are    Properly describe the missing IE Yes
       cal          11        defined in 6.3.6, which is a false here
                              statement. 6.3.6 does not
                              contain Node address, NID,
                              Uplink, Downlink, Bilink
                              Assignment IEs Delayed Bilink
                              Assignment IE, Channel order
                              IE or Channel Hopping IE

S6-097 Techni    67 6.7.   26 What is an OUI-24l?               Delete l                          Yes
       cal          15.1

S6-098 Techni    59 6.7.   18 Only the Frame Subtype is         Change below to in the following Yes
       cal          2.1       shown below                       sub clauses

S6-099 Editori   59 6.7.   19 Should be one level more than Change 6.7.2.2 to 6.7.2.1.1           Yes
       al           2.2       the Allocation ID level, since this
                              item is part of it
S6-100 Editori   60 6.7.   19 Should be one level more than Change 6.7.2.2 to 6.7.2.1.2           Yes
       al           2.3       the Allocation ID level, since this
                              item is part of it
S6-101 Editori   22 6.2.    3 "exclusieve" should be              See comment.                    Yes
       al           1.1.      "exclusive"
                    6
S6-102 Editori   22 6.2.    4 "curren" should be "current"      See comment.                      Yes
       al           1.1.
                    6
S6-103 Techni    52 6.4. 4-8 The use of a signal strength to    Remove the "Relay Link Quality" Yes
       cal          6.4       define the link quality is        field or find another way to
                              questionable. This field cannot   measure the link quality.
                              be used in a reliable way in
                              presence of noise or
                              interference
S6-104 Techni    52 6.4. 4-8 The use of a signal strength to    Remove the "Relay Link Quality" Yes
       cal          6.4       define the link quality is        field or find another way to
                              questionable. This field cannot   measure the link quality.
                              be used in a reliable way in
                              presence of noise or
                              interference
S6-105 Editori   22 6.2.      Table 3: b6-b7 not defined or     Define
       al           1.1.      reference
                    8


S6-106 Techni    23 6.2.    4 Reference to "it' on lines 4      Change "It is set" to "when set to Yes
       cal          1.1.      through 22                        zero the node"
                    9
S6-107 Editori   25 6.2.      Figure 11 missing "# of bits"   Add "# of bits"
       al           1.1.
                    12


S6-108 Editori   26 6.2.      Figure 11 missing "# of bits"   Add "# of bits"
       al           2



S6-109 Editori   27 6.2.   24 missing "(LSB)"                 add least-significant bit "(LSB)"
       al           3



S6-110 Editori   27 6.2.   25 missing "(MSB)"                 add most-significant bit "(MSB)"
       al           3



S6-111 Editori   27 6.2.      Figure 13 missing "LSB", "MSB" Add reference
       al           3



S6-112 Techni    28 6.2.    1 missing figure showing          Add reference diagram               Yes
       cal          3         polynomial connection, and
                              LSB, MSB logical connection
                              and flow

S6-113 Techni    32 6.3.    5 "being run" is ambigous         Change "being run" to "type"        Yes
       cal          2.3.
                    1
S6-114 Editori   34 6.3.   28 "PkY" case                        Change to "PKx"
       al           2.6.
                    2




S6-115 Editori   41 6.3.    2 "Nibble" not defined              Define in definition section
       al           6.6.
                    7


S6-116 Editori   41 6.3.   17 " = 1" should be change to text   Change "=1" to "When set to
       al           6.8       to be consistent throughout the   one"
                              document


S6-117 Editori   41 6.3.   17 " = 0" should be changed to text Change "=0" to "When set to
       al           6.8       to be consistent throughout the zero"
                              document


S6-118 Editori   47 6.3.    9 mix of bit discriptors throughout Global change: change "two bit"
       al           11.4      the document                      to "2-bit"
                    .2


S6-119 Editori   53 6.4.    1                                   Remove character " [ "
       al           8.
S6-120 Editori    54 6.4.     7 change "1" to "one" and "0" to      Make global change
       al            8.7        zero



S6-121 Editori    54 6.4.       Table 13: The Command               Add in text and define in Clause
       al            8.6        Name(s) in the Table, need to       3.0 Definitions
                                be defined


S6-122-
S6-159
missing
?
S6-159 Techni    52 6.4. 4-8 The use of a signal strength to        Remove the "Relay Link Quality" Yes
        cal         6.4      define the link quality is             field or find another way to
                             questionable. This field cannot        measure the link quality.
                             be used in a reliable way in
                             presence of noise or
                             interference
S6-160 Techni 19.. 6     -   General comment: MAC is quite          Consider whether simpler           no
       cal     140 and       complicated, with lots of              scheme would be more
                    7,       options.                               appropriate to the goal of small
                    (&m                                             low power embedded &
                    ayb                                             wearable devices.
                    e8)
S6-161 Editori   21 6.2. 4,5 After familiarity with 802.15.4 it     Make bit field definitions conform No
       al           1.1.     is a little confusing to see bit       to IEEE norms.
                    2        fields in tables (e.g. Table 1 and
                             Table 2) listed with low order
                             bits first. IEEE should have a
                             defined policy on this and have
                             a unifrom way to do it applied in
                             all standards. The ordering is
                             the other way arouind in IEEE
                             Std 802.15.4-2006, see e.g.
                             Table 80 (for instance).

S6-162 Editori    22 6.2. 15,1 Same comment again for Table         Make bit field definitions conform No
       al            1.1. 6    3: bitfield order differs to norm,   to IEEE norms. (Please check
                     8         i.e. the ordering is the other way   for and corerect other instances
                               arouind in IEEE Std 802.15.4-        of same thing in draft)
                               2006, see e.g. Table 80 (for
                               instance).
S6-163 Editori    27 6.2.   31 CCITT is now called ITU-T            Change "CCITT" to "ITU-T"          No
       al            3


S6-164 Editori    57 6.6.    11 Typo Table-14 Data "rage"           change "rage" to "rate"            No
       al            2.3        field...
S6-165 Techni    57 6.6. 11.. HBC PHY not represented in       Add HBC PHY and data rates,            No
       cal          2.3 12 table - it has multiple data rates. and add UWB phy data rates
                              UWB PHY has multiple data
                              rates.


S6-166 Techni PDF 6.6.     11 "kbps" in Table 14 is not a SI     Replace "kbps" with "kb/s" (here Yes
       cal    65 2.3          unit                               and throughout the document ->
                                                                 search and replace)

S6-167 Editori   22 6.2.    3 exclusieve should be "exclusive"   See comment.                         Yes
       al           1.1.
                    6
S6-168 Editori   22 6.2.    4 curren should be "current"         See comment.                         Yes
       al           1.1.
                    6
S6-169 Editori   21 6.2. 15- This comment applies to many        Would the technical editor make Yes
       al           1.1. 18 places (especially in the MAC        the following formatting changes
                    4         and security clauses) in the       please? Convert the remaining
                              draft. Many, but not all,          unnumbered bullets into
                              unnumbered bullets have been       numbered ones, whenever
                              converted to numbered ones.        reasonable.
                              Need to be consistent.

S6-170 Editori   22 6.2. 4    Typo.                              Move "not" to before the first       Yes
       al           1.1.                                         "enabled" in this line.
                    6
S6-171 Editori   22 6.2. 15   Formatting glitch.                 Capitalize the first letter of "type" Yes
       al           1.1.                                         and "subtype".
                    8
S6-172 Editori   22 6.2. 15   This comment applies to            Would the technical editor make Yes
       al           1.1.      numerous tables. (1) These         the following formatting changes
                    8         tables are a bit crowded. (2)      please? (1) Increase the
                              The first row needs cleared        spacing between rows for all
                              alignment. (3) the position of     these similar tables. (2) Make
                              some entries need to be            "b4b5" or similar bit designations
                              adjusted closer to the center.     a separate row from "…value" in
                                                                 the first row of all these similar
                                                                 tables. (3) Move the numbers in
                                                                 the first columns and similar
                                                                 columns (from second row on)
                                                                 closer to the center of the
                                                                 column in all these similar tables.

S6-173 Editori   22 6.2. 15   Internal horizontal lines should   Thin the internal horizontal lines   Yes
       al           1.1.      be thinner.                        below the 2nd row.
                    8
S6-174 Techni    22 6.2. 15   The Wakeup frame provides no       Remove the row of "Wakeup"        Yes
       cal          1.1.      more functionality and             frame from Table 3, subclause
                    8         effectiveness than the Poll        6.4.7 and subclause 7.8.2.1.1
                              frame, as explained in detail in   (which should have never
                              some related comments.             appeared). Accordingly, change
                                                                 "1011" to "0111" in the preceding
                                                                 row (for reserved frame subtype
                                                                 values of control type frames).

S6-175 Editori   23 6.2. 35   Unwarranted capitalization.        Change "Field" to "field" before    Yes
       al           1.1.                                         "encoding".
                    10
S6-176 Editori   24 6.2. 40   Duplicate bullet number.           Delete "6." at the start of the text. Yes
       al           1.1.
                    11
S6-177 Techni    25 6.2. 12  The Coexistence field can be        After "Coexistence format", add     Yes
       cal          1.1.     reused to define some fields for    "for beacon frames".
                    12       B2 frames as well (as noted in
                             another comment).
S6-178 Techni    25 6.2. 14- Use backward coding for the         (1) In lines 14 and 20, change      Yes
       cal          1.1. 24 Fragment Number field, so that       "first" to "final". (2) In lines 17
                    12       the recipient knows if the last     and 22, delete "non-first". (3) In
                             received fragment is the last       line 18, change "incremented by
                             one of an MSDU or a                 one from its value" to "set to the
                             management frame.                   number of the fragments of the
                                                                 frame payload minus one in the
                                                                 frame containing the first
                                                                 fragment, and is decremented by
                                                                 one successively". (4) In lines
                                                                 19 and 24, change "previous" to
                                                                 "next". (5) In line 23, change
                                                                 "incremented by one from its
                                                                 value" to "set to the number of
                                                                 the fragments of the MSDU
                                                                 minus one in the frame
                                                                 containing the first fragment, and
                                                                 is decremented by one
                                                                 successively".
S6-179 Techni   26 6.2. 3   Define the Coexistence field for   (1) Insert a new numbered bullet Yes
       cal         1.1.     B2 frames, so that some fields     before this line, with the following
                   12       don't need to appear in the        text: h) In B2 frames, it is used
                            frame payload.                     as a Coexistence field, which is
                                                               formatted as shown in Figure 12.
                                                               The BAN Services field is set
                                                               according to Table 4 to indicate
                                                               the services provided to the BAN
                                                               of this hub. (2) Insert a new
                                                               figure, Figure 12 - Coexistence
                                                               format for B2 frames, defining
                                                               two fields: b0b1 for BAN
                                                               Services and b2b3 for Reserved.
                                                               (3) Insert a new table, Table 4 -
                                                               BAN Services field encoding,
                                                               defining 4 field values 0-3 and 4
                                                               corresponding BAN services: life
                                                               critical services, general health
                                                               services, mixed medical and non-
                                                               medical services, non-medical
                                                               services.
S6-180 Editori   26 6.2. 15   This comment applies to many Restore all instances of "shall" to Yes
       al           2         places of Clause 6. While          "must" throughout Clause 6.
                              Clause 7 is written in
                              prescriptive style (shall, should,
                              may) to specify MAC functional
                              behaviors, Clause 6 is written in
                              descriptive style (…field IS set
                              to…) to define MAC frame
                              formats. This clause originally
                              had a few musts that were
                              intentionally spelled out that
                              way; they were all changed to
                              shalls in D0. There are two
                              potential concerns with the
                              change: (a) ―shall‖ does not
                              necessarily convey the same
                              meaning or intent of ―must‖.
                              Example (page 32, lines 11-12):
                              ―The Control Frame
                              Authentication field is set to one
                              if control type frames sent from
                              or to this sender SHALL be
                              authenticated‖. (b) These shalls
                              are inconsistent with the style of
                              Clause 6 which is meant to be
                              descriptive but not prescriptive.




S6-181 Editori   27 6.2. 15   This comment applies to most         Would the technical editor       Yes
       al           2.2       paragraphs following a bulleted      please adjust the spacings to be
                              item in the draft (especially in     a bit more uniform for all these
                              the MAC and security clauses).       similar instances of the draft?
                              There is a big space between
                              the (typically short) paragraph
                              and the next line of the following
                              set of bulleted paragraphs, but
                              only a small space between the
                              last bulleted paragraph and the
                              next one. However, the
                              preceding paragraph is often
                              more closely related to the
                              bulleted items than the
                              paragraph that follows those
                              items is in their meaning.

S6-182 Editori   27 6.2. 17   Comma misplaced. Did                 Move the comma from before to Yes
       al           2.2       reformatting in D0 generate          after Figure 12.
                              other misplaced commas?
S6-183 Editori   29 6.3. 16   "not" misplaced.                   Move "not" to before the first     Yes
       al           1.4                                          "enabled" in this line.

S6-184 Editori   29 6.3. 28   "not" misplaced.                   Move "not" to before the first     Yes
       al           1.6                                          "enabled" in this line.

S6-185 Editori   32 6.3. 1-9 Simplify naming.                     (1) Delete "Required" from the      Yes
       al           2.3                                           "Security Level Required" field in
                                                                  Figure 18. (2) In lines 7-8,
                                                                  delete "Required". (3) In Table
                                                                  6's heading, change "required" to
                                                                  "Level".
S6-186 Editori   32 6.3. 6    This comment applies to many Technical Editor, would you                Yes
       al           2.3.      tables in Clause 6. "Field value please insert "in" before
                    1         decimal"…                           "decimal" J71and make "in
                                                                  decimal" in a separate line in this
                                                                  and other similar tables?
S6-187 Editori   32 6.3. 15   "Protocol" is not part of the field Delete "Protocol" from the          Yes
       al           2.3.      anymore.                            heading.
                    4
S6-188 Editori   43 6.3. 1    Formatting glitch.                 Make the two internal lines        Yes
       al           7.3                                          (below the 2nd row) thinner.

S6-189 Techni    45 6.3. 1-2 There are some inconsistencies      (1) Remove the B+EAP1 Length Yes
       cal          8        between this frame and the          and EAP2 Length fields. (2)
                             Connection Assignment frame         Move the Status Code field into
                             in 24 on which this frame is        the Node Connection
                             based.                              Assignment IE. (3) Change the
                                                                 length bound for the Node
                                                                 Connection Assignment IE fields
                                                                 to 15.
S6-190 Editori   46 6.3. 20   Unwarranted capitalization.        In the table heading, change    Yes
       al           11.3                                         "Field" to "field".

S6-191 Techni    46 6.3. 20   (1) The frame formats of these     (1) Change "Request" to "Time Yes
       cal          11.3      two coexistence commands           Sharing". (2) Change "Command
                              were never discussed, let alone    - Coexistence Response" to
                              approved, in the MAC subgroup.     "Reserved".
                              (2) At most only one command
                              for coexistence is need, as
                              explained in another comment.

S6-192 Editori   47 6.3. 1-22 6.3.11.4.1 should be a parent      Promote 6.3.11.4.1 to one level Yes
       al           11.4      subclause of the three             higher as 6.3.12, and keep the
                    .1        subclauses that follow, instead    subclauses that define the fields
                              of being at the same level.        of this command at current level.
S6-193 Techni   47 6.3. 1    There is no functional difference   Change "Command -             Yes
       cal         11.4      specified for "coexistence          Coexistence Request" to
                   .1        request" and "coexistence           "Command - Coexistence Time
                             response". Hence no two             Sharing".
                             separate frames are needed.

S6-194 Techni   47 6.3. 2-6 These lines need to be revised (1) Change "in" to "for" before "a Yes
       cal         11.4      in view of the changes made to Command". (2) Insert "time
                   .1        the frame defined here.           sharing enabled" before "hub" (2
                                                               instances). (3) Change "to
                                                               request coexistence on the
                                                               same physical channel" to
                                                               "convey certain coexistence
                                                               information". (4) Change
                                                               "Request" to "Time Sharing" in
                                                               the figure caption.
S6-195 Techni   47 6.3. 1-22 (1) Both the definition and table (1) Change "Piconet Priority" to Yes
       cal         11.4      for "Piconet priority" needed to "BAN Services", a new field
                   .1        be reworked to be consistent in proposed in the Coexistence
                             naming and format with other      field of the MAC header of B2
                             sections. (2) There is no         frames. Accordingly, change the
                             difference in functional          definition to "The BAN Services
                             behaviors between "time           field is as defined in 6.2.1.1.12
                             sharing" and "offset piconet      h) and Table 4" (which were
                             synchronization" -- both of which proposed for B2 frames). (2)
                             cannot require superframe         Remove the "coexistence mode"
                             boundary synchronization          field in Figure 29, subclause
                             between networks. There is no 6.3.11.4.3 which was misspelled
                             functional description for        as "coexistence response", and
                             "piconet enquiry". Therefore,     Table 11. (3) Change "Allocation
                             there is no functional use of the Time /duty cycle" in both Figure
                             "coexistence mode" field. (3)     29 and 6.3.11.4.4 to "Allocation
                             The Allocation Time / Duty        Percentage", and change the
                             Cycle field essentially has the   definition to the following: The
                             same definition under both "time Allocation Percentage field is set
                             sharing" and "offset piconet      to P such that this hub is to use
                             synchronization" modes. It just an aggregate allocation of up to
                             means the percentage of the       4×P % of the total time on its
                             total allocation of one network. operating channel for its body
                                                               area network (BAN). (4) Delete
                                                               Table 12 (mislabeled as
                                                               "coexistence modes").
S6-196 Techni    48 6.3. 3-20 These are just duplicates of the Remove them along with the             Yes
       cal          11.5      subclauses for the "Coexistence figure and table within.
                    (b)       Request" version, except for the
                              "status" field, which, however, is
                              meaningless. There is no
                              functional difference specified
                              for "coexistence request
                              accepted" and "coexistence
                              request rejected". In particular,
                              what does the acceptance or
                              rejection of a coexistence
                              request by network 2 mean to
                              network 1 that made the
                              request? Nothing in either
                              case.

S6-197 Techni    49 6.3. 1-16 Incorrect level for these three        Promote 6.3.11.5.4 to one level Yes
       cal          11.5      subclauses.                            higher, and keep the two
                    .4                                               subclauses that define the fields
                                                                     of this command at the current
                                                                     level.
S6-198 Techni    49 6.3. 17    Incorrect level for this              Promote 6.3.11.5.7 to one level Yes
       cal          11.5       subclause.                            higher.
                    .4


S6-199 Editori   49 6.3. 2     Incorrect level for this              Change "in" to "for" before "a   Yes
       al           11.5       subclause.                            Command".
                    .4


S6-200 Techni    52 6.4. 5     (1) locally broadcast but not         (1) Change "multicast" to         Yes
       cal          6.4        locally multicast. (2) the field is   "broadcast" in line 5. (2) Reword
                               set…, but not the relay node will     the 2nd and 3rd sentences for
                               set this field.                       stylistic consistency with other
                                                                     sections.
S6-201 Techni   52 6.4. 4-8 The "received signal strength of   Remove the Relay Link Quality Yes
       cal         6.4      signals" does not truly reflect    field and all references to it,
                            the quality of the link in         unless the proposers provide a
                            presence of noise and              revised text that addresses this
                            interference.                      fundamental issue. Note that the
                                                               field value must be "absolute" in
                                                               the sense that all devices will
                                                               generate the same value
                                                               independent of their internal
                                                               calibration levels they used in
                                                               estimating that value.
S6-202 Techni 52-   6.4.      (1) Many fields are already         (1) Remove all fields and their    Yes
       cal    53    8         contained in the beacon or the      definition subclauses (and Table
                              MAC header of the B2 frame,         13 which has already appeared
                              and should not be duplicated        earlier), except the "Reserved
                              here, per the discussion at the     slots" and "NID" fields. (2)
                              last IEEE meeting. In particular,   Rename "Reserved slots' as
                              the Beacon Period Length and        "Earliest Next B2", and reword its
                              Allocation Slot Length fields are   definition as follows: The
                              verbatim duplicates from the        Earliest Next B2 field is set to E
                              beacon. The CAP Length field        such that the earliest next B2
                              is equivalent to the Sequence       time occurs not earlier than the
                              Number / Poll-Post Window           end of the allocation slot
                              field of the MAC header of the      numbered E in the next beacon
                              B2 frame, as the latter field       period (superframe). (3) Restore
                              encodes the end time of CAP         the definition subclause for the
                              (and B2's end time is the start     NID field, with the following
                              time of CAP). The Offset to         definition: One or more NID
                              Start Time field value is readily   fields are optionally present.
                              calculated from the B2 and          When present, each NID field is
                              beacon transmission times.          set to the NID of a node from
                              The Piconet Priority field is now   which this hub received a frame
                              defined as the BAN Services         requiring group acknowledgment
                              field, which is part of the         since the last transmitted B2
                              Coexistence field of the MAC        frame.
                              header of the B2 frame. The
                              beacon frame is easier to
                              receive since it is sent at known
                              times, and has more information
                              useful or desirable for
                              coexistence. Thus it would be a
                              backward step to copy some
                              fields from the beacon into the
S6-203 Editori   57 6.6. 11   B2 and then have coexistence
                              Typo.                               Change "rage" to "rate" in the    Yes
       al           2.3                                           table heading.

S6-204 Editori   57 6.6. 11   Formatting glitch.                  Make the two internal lines       Yes
       al           2.3                                           (below the 2nd row) thinner.

S6-205 Editori   57 6.6. 13   Two much space.                     Delete this empty line.           Yes
       al           2.3

S6-206 Editori   58 6.7. 5    Some clarification is needed on Change "to indicate ..lengths" to Yes
       al           1         why and when this IE is         "foretell some information on the
                              included.                       superframe (beacon period)
                                                              structure that is contained in
                                                              beacons which are not being
                                                              transmitted frequently or at all"
S6-207 Techni    58 6.7. 6    If superframe length and            Add to the end of the current IE   Yes
       cal          1         allocation slot length fields are   an optional "Beacon Shifting
                              needed to be separately             Sequence" field.
                              included, so is the beacon
                              shifting sequence field when
                              beacon shifting is enabled.


S6-208 Editori   58 6.7. 10- Avoid repeating a definition that Change these two lines to the         Yes
       al           1.1 11 is already given somewhere          following: The Superframe
                             else.                             Length field is as defined in
                                                               6.3.1.2 for the Beacon Period
                                                               Length field.
S6-209 Editori   59 6.7. 3   Avoid repeating a definition that Change these two lines to the         Yes
       al           1.2      is already given somewhere        following: The Allocation Slot
                             else.                             Length field is as defined in
                                                               6.3.1.3.
S6-210 Editori   59 6.7. 13 Figure formatting glitch.          Insert two dashed lines at the        Yes
       al           2                                          start of the bottom fields to
                                                               indicate continuation from the
                                                               top fields.
S6-211 Editori   61 6.7. 15 Figure formatting glitch.          Insert two dashed lines at the        Yes
       al           5                                          start of the bottom fields to
                                                               indicate continuation from the
                                                               top fields.
S6-212 Techni    66 6.7. 5   The "Status Code" field now in Insert a one-octet "Status Code"         Yes
       cal          11       the Multinode Connection          field after the "Node Address"
                             Assignment frame should be        field.
                             defined on a per node basis and
                             hence should be moved here.

S6-213 Techni    66 6.7. 8-9 Inconsistent frame reference.        Change the paragraph to "All the Yes
       cal          11                                            fields after the Length field
                                                                  pertain to the same node and
                                                                  are defined as in 6.3.7 for
                                                                  Connection Assignment frames,
                                                                  except the Node Address field
                                                                  which is set to the IEEE MAC
                                                                  address of the node."

S6-214 Editori   21 6.2. 15- This comment applies to many         Would the technical editor make Yes
       al           1.1. 18 places (especially in the MAC         the following formatting changes
                    4        and security clauses) in the         please? Convert the remaining
                             draft. Many, but not all,            unnumbered bullets into
                             unnumbered bullets have been         numbered ones, whenever
                             converted to numbered ones.          reasonable.
                             Need to be consistent.

S6-215 Editori   22 6.2. 4    Typo.                               Move "not" to before the first     Yes
       al           1.1.                                          "enabled" in this line.
                    6
S6-216 Editori   22 6.2. 15   Formatting glitch.                 Capitalize the first letter of "type" Yes
       al           1.1.                                         and "subtype".
                    8
S6-217 Editori   22 6.2. 15   This comment applies to            Would the technical editor make Yes
       al           1.1.      numerous tables. (1) These         the following formatting changes
                    8         tables are a bit crowded. (2)      please? (1) Increase the
                              The first row needs cleared        spacing between rows for all
                              alignment. (3) the position of     these similar tables. (2) Make
                              some entries need to be            "b4b5" or similar bit designations
                              adjusted closer to the center.     a separate row from "…value" in
                                                                 the first row of all these similar
                                                                 tables. (3) Move the numbers in
                                                                 the first columns and similar
                                                                 columns (from second row on)
                                                                 closer to the center of the
                                                                 column in all these similar tables.

S6-218 Editori   22 6.2. 15   Internal horizontal lines should   Thin the internal horizontal lines   Yes
       al           1.1.      be thinner.                        below the 2nd row.
                    8
S6-219 Techni    22 6.2. 15   The Wakeup frame provides no       Remove the row of "Wakeup"        Yes
       cal          1.1.      more functionality and             frame from Table 3, subclause
                    8         effectiveness than the Poll        6.4.7 and subclause 7.8.2.1.1
                              frame, as explained in detail in   (which should have never
                              some related comments.             appeared). Accordingly, change
                                                                 "1011" to "0111" in the preceding
                                                                 row (for reserved frame subtype
                                                                 values of control type frames).

S6-220 Editori   23 6.2. 35   Unwarranted capitalization.        Change "Field" to "field" before     Yes
       al           1.1.                                         "encoding".
                    10
S6-221 Editori   24 6.2. 40   Duplicate bullet number.           Delete "6." at the start of the text. Yes
       al           1.1.
                    11
S6-222 Techni    25 6.2. 12   The Coexistence field can be     After "Coexistence format", add        Yes
       cal          1.1.      reused to define some fields for "for beacon frames".
                    12        B2 frames as well (as noted in
                              another comment).
S6-223 Techni   25 6.2. 14- Use backward coding for the         (1) In lines 14 and 20, change      Yes
       cal         1.1. 24 Fragment Number field, so that       "first" to "final". (2) In lines 17
                   12       the recipient knows if the last     and 22, delete "non-first". (3) In
                            received fragment is the last       line 18, change "incremented by
                            one of an MSDU or a                 one from its value" to "set to the
                            management frame.                   number of the fragments of the
                                                                frame payload minus one in the
                                                                frame containing the first
                                                                fragment, and is decremented by
                                                                one successively". (4) In lines
                                                                19 and 24, change "previous" to
                                                                "next". (5) In line 23, change
                                                                "incremented by one from its
                                                                value" to "set to the number of
                                                                the fragments of the MSDU
                                                                minus one in the frame
                                                                containing the first fragment, and
                                                                is decremented by one
                                                                successively".

S6-224 Techni   26 6.2. 3    Define the Coexistence field for   (1) Insert a new numbered bullet Yes
       cal         1.1.      B2 frames, so that some fields     before this line, with the following
                   12        don't need to appear in the        text: h) In B2 frames, it is used
                             frame payload.                     as a Coexistence field, which is
                                                                formatted as shown in Figure 12.
                                                                The BAN Services field is set
                                                                according to Table 4 to indicate
                                                                the services provided to the BAN
                                                                of this hub. (2) Insert a new
                                                                figure, Figure 12 - Coexistence
                                                                format for B2 frames, defining
                                                                two fields: b0b1 for BAN
                                                                Services and b2b3 for Reserved.
                                                                (3) Insert a new table, Table 4 -
                                                                BAN Services field encoding,
                                                                defining 4 field values 0-3 and 4
                                                                corresponding BAN services: life
                                                                critical services, general health
                                                                services, mixed medical and non-
                                                                medical services, non-medical
                                                                services.
S6-225 Editori   26 6.2. 15   This comment applies to many Restore all instances of "shall" to Yes
       al           2         places of Clause 6. While          "must" throughout Clause 6.
                              Clause 7 is written in
                              prescriptive style (shall, should,
                              may) to specify MAC functional
                              behaviors, Clause 6 is written in
                              descriptive style (…field IS set
                              to…) to define MAC frame
                              formats. This clause originally
                              had a few musts that were
                              intentionally spelled out that
                              way; they were all changed to
                              shalls in D0. There are two
                              potential concerns with the
                              change: (a) ―shall‖ does not
                              necessarily convey the same
                              meaning or intent of ―must‖.
                              Example (page 32, lines 11-12):
                              ―The Control Frame
                              Authentication field is set to one
                              if control type frames sent from
                              or to this sender SHALL be
                              authenticated‖. (b) These shalls
                              are inconsistent with the style of
                              Clause 6 which is meant to be
                              descriptive but not prescriptive.




S6-226 Editori   27 6.2. 15   This comment applies to most         Would the technical editor       Yes
       al           2.2       paragraphs following a bulleted      please adjust the spacings to be
                              item in the draft (especially in     a bit more uniform for all these
                              the MAC and security clauses).       similar instances of the draft?
                              There is a big space between
                              the (typically short) paragraph
                              and the next line of the following
                              set of bulleted paragraphs, but
                              only a small space between the
                              last bulleted paragraph and the
                              next one. However, the
                              preceding paragraph is often
                              more closely related to the
                              bulleted items than the
                              paragraph that follows those
                              items is in their meaning.

S6-227 Editori   27 6.2. 17   Comma misplaced. Did                 Move the comma from before to Yes
       al           2.2       reformatting in D0 generate          after Figure 12.
                              other misplaced commas?
S6-228 Editori   29 6.3. 16   "not" misplaced.                   Move "not" to before the first     Yes
       al           1.4                                          "enabled" in this line.

S6-229 Editori   29 6.3. 28   "not" misplaced.                   Move "not" to before the first     Yes
       al           1.6                                          "enabled" in this line.

S6-230 Editori   32 6.3. 1-9 Simplify naming.                     (1) Delete "Required" from the      Yes
       al           2.3                                           "Security Level Required" field in
                                                                  Figure 18. (2) In lines 7-8,
                                                                  delete "Required". (3) In Table
                                                                  6's heading, change "required" to
                                                                  "Level".
S6-231 Editori   32 6.3. 6    This comment applies to many Technical Editor, would you                Yes
       al           2.3.      tables in Clause 6. "Field value please insert "in" before
                    1         decimal"…                           "decimal" J71and make "in
                                                                  decimal" in a separate line in this
                                                                  and other similar tables?
S6-232 Editori   32 6.3. 15   "Protocol" is not part of the field Delete "Protocol" from the          Yes
       al           2.3.      anymore.                            heading.
                    4
S6-233 Editori   43 6.3. 1    Formatting glitch.                 Make the two internal lines        Yes
       al           7.3                                          (below the 2nd row) thinner.

S6-234 Techni    45 6.3. 1-2 There are some inconsistencies      (1) Remove the B+EAP1 Length Yes
       cal          8        between this frame and the          and EAP2 Length fields. (2)
                             Connection Assignment frame         Move the Status Code field into
                             in 24 on which this frame is        the Node Connection
                             based.                              Assignment IE. (3) Change the
                                                                 length bound for the Node
                                                                 Connection Assignment IE fields
                                                                 to 15.
S6-235 Editori   46 6.3. 20   Unwarranted capitalization.        In the table heading, change    Yes
       al           11.3                                         "Field" to "field".

S6-236 Techni    46 6.3. 20   (1) The frame formats of these     (1) Change "Request" to "Time Yes
       cal          11.3      two coexistence commands           Sharing". (2) Change "Command
                              were never discussed, let alone    - Coexistence Response" to
                              approved, in the MAC subgroup.     "Reserved".
                              (2) At most only one command
                              for coexistence is need, as
                              explained in another comment.

S6-237 Editori   47 6.3. 1-22 6.3.11.4.1 should be a parent      Promote 6.3.11.4.1 to one level Yes
       al           11.4      subclause of the three             higher as 6.3.12, and keep the
                    .1        subclauses that follow, instead    subclauses that define the fields
                              of being at the same level.        of this command at current level.
S6-238 Techni   47 6.3. 1    There is no functional difference   Change "Command -             Yes
       cal         11.4      specified for "coexistence          Coexistence Request" to
                   .1        request" and "coexistence           "Command - Coexistence Time
                             response". Hence no two             Sharing".
                             separate frames are needed.

S6-239 Techni   47 6.3. 2-6 These lines need to be revised (1) Change "in" to "for" before "a Yes
       cal         11.4      in view of the changes made to Command". (2) Insert "time
                   .1        the frame defined here.           sharing enabled" before "hub" (2
                                                               instances). (3) Change "to
                                                               request coexistence on the
                                                               same physical channel" to
                                                               "convey certain coexistence
                                                               information". (4) Change
                                                               "Request" to "Time Sharing" in
                                                               the figure caption.
S6-240 Techni   47 6.3. 1-22 (1) Both the definition and table (1) Change "Piconet Priority" to Yes
       cal         11.4      for "Piconet priority" needed to "BAN Services", a new field
                   .1        be reworked to be consistent in proposed in the Coexistence
                             naming and format with other      field of the MAC header of B2
                             sections. (2) There is no         frames. Accordingly, change the
                             difference in functional          definition to "The BAN Services
                             behaviors between "time           field is as defined in 6.2.1.1.12
                             sharing" and "offset piconet      h) and Table 4" (which were
                             synchronization" -- both of which proposed for B2 frames). (2)
                             cannot require superframe         Remove the "coexistence mode"
                             boundary synchronization          field in Figure 29, subclause
                             between networks. There is no 6.3.11.4.3 which was misspelled
                             functional description for        as "coexistence response", and
                             "piconet enquiry". Therefore,     Table 11. (3) Change "Allocation
                             there is no functional use of the Time /duty cycle" in both Figure
                             "coexistence mode" field. (3)     29 and 6.3.11.4.4 to "Allocation
                             The Allocation Time / Duty        Percentage", and change the
                             Cycle field essentially has the   definition to the following: The
                             same definition under both "time Allocation Percentage field is set
                             sharing" and "offset piconet      to P such that this hub is to use
                             synchronization" modes. It just an aggregate allocation of up to
                             means the percentage of the       4×P % of the total time on its
                             total allocation of one network. operating channel for its body
                                                               area network (BAN). (4) Delete
                                                               Table 12 (mislabeled as
                                                               "coexistence modes").
S6-241 Techni    48 6.3. 3-20 These are just duplicates of the Remove them along with the             Yes
       cal          11.5      subclauses for the "Coexistence figure and table within.
                    (b)       Request" version, except for the
                              "status" field, which, however, is
                              meaningless. There is no
                              functional difference specified
                              for "coexistence request
                              accepted" and "coexistence
                              request rejected". In particular,
                              what does the acceptance or
                              rejection of a coexistence
                              request by network 2 mean to
                              network 1 that made the
                              request? Nothing in either
                              case.

S6-242 Techni    49 6.3. 1-16 Incorrect level for these three        Promote 6.3.11.5.4 to one level Yes
       cal          11.5      subclauses.                            higher, and keep the two
                    .4                                               subclauses that define the fields
                                                                     of this command at the current
                                                                     level.
S6-243 Techni    49 6.3. 17    Incorrect level for this              Promote 6.3.11.5.7 to one level Yes
       cal          11.5       subclause.                            higher.
                    .4
S6-244 Editori   49 6.3. 2     Incorrect level for this              Change "in" to "for" before "a   Yes
       al           11.5       subclause.                            Command".
                    .4
S6-245 Techni    52 6.4. 5     (1) locally broadcast but not         (1) Change "multicast" to         Yes
       cal          6.4        locally multicast. (2) the field is   "broadcast" in line 5. (2) Reword
                               set…, but not the relay node will     the 2nd and 3rd sentences for
                               set this field.                       stylistic consistency with other
                                                                     sections.

S6-246 Techni    52 6.4. 4-8 The "received signal strength of        Remove the Relay Link Quality Yes
       cal          6.4      signals" does not truly reflect         field and all references to it,
                             the quality of the link in              unless the proposers provide a
                             presence of noise and                   revised text that addresses this
                             interference.                           fundamental issue. Note that the
                                                                     field value must be "absolute" in
                                                                     the sense that all devices will
                                                                     generate the same value
                                                                     independent of their internal
                                                                     calibration levels they used in
                                                                     estimating that value.
S6-247 Techni 52-   6.4.      (1) Many fields are already         (1) Remove all fields and their    Yes
       cal    53    8         contained in the beacon or the      definition subclauses (and Table
                              MAC header of the B2 frame,         13 which has already appeared
                              and should not be duplicated        earlier), except the "Reserved
                              here, per the discussion at the     slots" and "NID" fields. (2)
                              last IEEE meeting. In particular,   Rename "Reserved slots' as
                              the Beacon Period Length and        "Earliest Next B2", and reword its
                              Allocation Slot Length fields are   definition as follows: The
                              verbatim duplicates from the        Earliest Next B2 field is set to E
                              beacon. The CAP Length field        such that the earliest next B2
                              is equivalent to the Sequence       time occurs not earlier than the
                              Number / Poll-Post Window           end of the allocation slot
                              field of the MAC header of the      numbered E in the next beacon
                              B2 frame, as the latter field       period (superframe). (3) Restore
                              encodes the end time of CAP         the definition subclause for the
                              (and B2's end time is the start     NID field, with the following
                              time of CAP). The Offset to         definition: One or more NID
                              Start Time field value is readily   fields are optionally present.
                              calculated from the B2 and          When present, each NID field is
                              beacon transmission times.          set to the NID of a node from
                              The Piconet Priority field is now   which this hub received a frame
                              defined as the BAN Services         requiring group acknowledgment
                              field, which is part of the         since the last transmitted B2
                              Coexistence field of the MAC        frame.
                              header of the B2 frame. The
                              beacon frame is easier to
                              receive since it is sent at known
                              times, and has more information
                              useful or desirable for
                              coexistence. Thus it would be a
                              backward step to copy some
                              fields from the beacon into the
S6-248 Editori   57 6.6. 11   B2 and then have coexistence
                              Typo.                               Change "rage" to "rate" in the    Yes
       al           2.3                                           table heading.

S6-249 Editori   57 6.6. 11   Formatting glitch.                  Make the two internal lines       Yes
       al           2.3                                           (below the 2nd row) thinner.

S6-250 Editori   57 6.6. 13   Two much space.                     Delete this empty line.           Yes
       al           2.3

S6-251 Editori   58 6.7. 5    Some clarification is needed on Change "to indicate ..lengths" to Yes
       al           1         why and when this IE is         "foretell some information on the
                              included.                       superframe (beacon period)
                                                              structure that is contained in
                                                              beacons which are not being
                                                              transmitted frequently or at all"
S6-252 Techni    58 6.7. 6   If superframe length and            Add to the end of the current IE    Yes
       cal          1        allocation slot length fields are   an optional "Beacon Shifting
                             needed to be separately             Sequence" field.
                             included, so is the beacon
                             shifting sequence field when
                             beacon shifting is enabled.
S6-253 Editori   58 6.7. 10- Avoid repeating a definition that    Change these two lines to the      Yes
       al           1.1 11 is already given somewhere             following: The Superframe
                             else.                                Length field is as defined in
                                                                  6.3.1.2 for the Beacon Period
                                                                  Length field.
S6-254 Editori   59 6.7. 3      Avoid repeating a definition that Change these two lines to the      Yes
       al           1.2         is already given somewhere        following: The Allocation Slot
                                else.                             Length field is as defined in
                                                                  6.3.1.3.
S6-255 Editori   59 6.7. 13     Figure formatting glitch.         Insert two dashed lines at the     Yes
       al           2                                             start of the bottom fields to
                                                                  indicate continuation from the
                                                                  top fields.
S6-256 Editori   61 6.7. 15     Figure formatting glitch.         Insert two dashed lines at the     Yes
       al           5                                             start of the bottom fields to
                                                                  indicate continuation from the
                                                                  top fields.
S6-257 Techni    66 6.7. 5      The "Status Code" field now in Insert a one-octet "Status Code"      Yes
       cal          11          the Multinode Connection          field after the "Node Address"
                                Assignment frame should be        field.
                                defined on a per node basis and
                                hence should be moved here.

S6-258 Techni    66 6.7. 8-9 Inconsistent frame reference.       Change the paragraph to "All the Yes
       cal          11                                           fields after the Length field
                                                                 pertain to the same node and
                                                                 are defined as in 6.3.7 for
                                                                 Connection Assignment frames,
                                                                 except the Node Address field
                                                                 which is set to the IEEE MAC
                                                                 address of the node."

S6-259 Editori   22 6.2.      4 Word misspelled.                 Change "curren" to "current"        Yes
       al           1.1.
                    6

S6-260 Editori   22 6.2.     12 Period missing.                  Add a period to the end of the      Yes
       al           1.1.                                         sentence.
                    7

S6-261 Editori   24 6.2.     40 Errant character.                Delete "6." from the front of the   Yes
       al           1.1.                                         sentence.
                    11
S6-262 Techni    32 6.3. 16- Clause 8 does not specify the          Add descriptive text for the         Yes
       cal          2.3. 17 Camellia-128 forward cipher             Camellia-128 forward cipher
                    4        function (as illustrated in Table      function in clause 8 or delete as
                             7).                                    an option from Table 7.

S6-263 Techni    40 6.3.     9 Figure 24 (Connection Change         For the Connection Change            Yes
       cal          6.6        Indicator Format) contains           Indicator, change the 1 bit field
                               several 1 bit fields for wakeup      names to "Wakeup Phase
                               (i.e., Wakeup Phase, Wakeup          Change" and "Wakeup Period
                               Period) that have the same           Change"; this change also
                               name in Figure 23 (with a            impacts subclauses that
                               different definition/field width).   reference 6.3.6.6.1 and
                                                                    6.3.6.6.2.
S6-264 Techni    47 6.3.     6 The term "piconet" is not            Add a definition of "piconet " to    Yes
       cal          11.4       defined prior to first use in        clause 3.
                    .1         Figure 29.

S6-265 Techni    47 6.3.   15 The term "coordinator" is not         Add a definition of "coordinator" Yes
       cal          11.4      defined prior to first use.           to clause 3. Add explanatory text
                    .3                                              contrasting a coordinator with a
                                                                    hub. Note - the term
                                                                    "coordinator" is used widely
                                                                    throughout the document.

S6-266 Editori   48 6.3.     3 Errant character.                    Delete "(b)" after the clause        Yes
       al           11.5                                            number.



S6-267 Techni    57 6.6.     1 The term "low power wakeup           Add a definition of "low power     Yes
       cal          2.1        radio" is not defined. First use     wakeup radio" to clause 3. Add
                               in Figure 37.                        explanatory text regarding this
                                                                    field or, as another option,
                                                                    should the field be deleted as too
                                                                    implementation specific?
S6-268 Techni    57 6.6.   10 The table lists UWB; a mode           Update table with information for Yes
       cal          2.3       that is not defined in subclause      other modes of the standard.
                              9.1. The table lists no optional
                              UWB data rates, it also does
                              not list HBC.




S6-269 Editori   21 6.2.   23 Relay field is reserved for all       "It is reserved and set to zero in   Yes
       al           1.1.      other frames. What does               all other frames."
                    5         reserved mean? Default value
                              of zero should be speficied for
                              reserved state.
S6-270 Editori   22 6.2.    3 Spelling error with "exclusieve"    Change to "exclusive"            Yes
       al           1.1.
                    6


S6-271 Editori   22 6.2.    4 Spelling error with "curren"        Change to "current"              Yes
       al           1.1.
                    6


S6-272 Editori   24 6.2.   40 Erroneous numbered element          Delete "6." such that the line   Yes
       al           1.1.      starting this line.                 begins "g) In data type
                    11                                            frames…"


S6-273 Editori   29 6.3.    7 Figure 15 caption should reflect    Change caption of Figure 15 to Yes
       al           1.2       beacon shifting enabled as it is    read "Allocation slot ordering and
                              illustrated but not yet described   numbering in beacon periods
                              in the text. Figure 15 may be       with exemplary beacon shifting"
                              confusing to those unfamiliar
                              with beacon shifting which is not
                              taught until later in the
                              document.

S6-274 Editori   30 6.3.   13 Erroneous variable name Pm(n) Change to "PNm(n)" to be            Yes
       al           1.10                                    consistent with variables listed in
                    .1                                      Table 4


S6-275 Techni    30 6.3.   14 Headers of Table 4 columns areChange column 1 header to           Yes
       cal          1.10      ambiguous with respect to     "Beacon Shifting Sequence
                    .1        indexed variables "m" and "n".Index decimal value (m)".
                              Should explicitly state that nChange column 2 header to
                              takes values n = 0,1,2,3,4.   "Beacon shifting Sequence
                                                            values, n = 0,1,2,3,4".
S6-276 Editori   30 6.3.   17 Erroneous variable name Pm(n) Change to "PNm(n)" to be            Yes
       al           1.10                                    consistent with variables listed in
                    .1                                      Table 4


S6-277 Editori   30 6.3.   20 Erroneous reference to Figure       Change to "according to Figure   Yes
       al           1.11      14 rather than Figure 11.           11."



S6-278 Editori   31 6.3.    2 Add reference to section 7.12.2 Change text to "beacon, see          Yes
       al           1.11      for channel hopping sequence clause 7.12.2."
                              creation.
S6-279 Editori   31 6.3.   20 Erroneous reference to Figure      Change to "according to Figure      Yes
       al           1.12      14 rather than Figure 11.          11."



S6-280 Techni    37 6.3.   22 PTK Index field is defined as a    Message Number field is also       Yes
       cal          4.4       one octet field but takes only     defined as a one octet field but
                              values of 0 or 1. This is an       takes values of only 0 to 3. As
                              inefficient use of frame payload   such, it could be represented as
                              format for PTK frames.             a 4 bit field. Change both PTK
                                                                 Index and Message Number
                                                                 fields to be 4 bits long and share
                                                                 a single octet.
S6-281 Editori   41 6.3.   22 Typographic error.                 Change "Uplink Request" to         Yes
       al           6.10                                         "Downlink Request"



S6-282 Techni    41 6.3.   12 Wakeup Period field is defined     Change this field to be one octet Yes
       cal          6.8       as taking values from 1 to 256     long in both the text and in
                              using one octet. However, the      Figure 23.
                              field is shown to be two octets
                              long in Figure 23.
S6-283 Editori   44 6.3.   18 Typographic error with             Change this line to read: "as       Yes
       al           7.18      referenced section number and      defined in 6.7.12 and 6.7.13
                              unnecessary "as"                   respectively."


S6-284 Editori   47 6.3.    5 Figure 29 includes a field         Replace "Piconet Priority" with     Yes
       al           11.4      "Piconet Priority". The basic      "BAN Priority"
                    .1        network element in this
                              document is BAN. Piconet has
                              not been defined and should be
                              striken.
S6-285 Editori   47 6.3.    8 This subclause title contains      Change to "BAN Priority".           Yes
       al           11.4      "Piconet Priority". However, the
                    .2        basic network element structure    Change all instances of "Piconet"
                              in this document is a BAN.         to "BAN" throughout the
                              Piconet has not been defined       document.
                              and should be striken.
S6-286 Editori   47 6.3.   12 Table 10 has caption "Piconet      Change to "BAN Priority"            Yes
       al           11.4      Priority". The basic network
                    .2        element in this document is
                              BAN. Piconet has not been
                              defined and should be striken.
S6-287 Techni    47 6.3.   12 Table 10 includes four priority    Change header of second           Yes
       cal          11.4      levels with specific values. The   column to read "Relative
                    .2        second column header is            Priority". Redefine values to
                              erroneous. In addition, the        reflect the desired QoS with
                              values in this table have          preference for medical traffic.
                              ambiguous meaning. What is a       Higher value number should
                              life critical medical device?      correspond to higher priority.
                              What is a qualified medical
                              priority? What is "general         00 = Entertainment, No Medical
                              monitoring"?                       Data
                                                                 01 = Medical, Low QoS Priority
                                                                 10 = Medical, Medium QoS
                                                                 Priority
                                                                 11 = Medical, High QoS Priority


S6-288 Editori   47 6.3.    9 Capitalization and grammar.        Change to "…to coexistence.       Yes
       al           11.4                                         Table 10 defined the"
                    .2


S6-289 Editori   47 6.3.   15 Capitalization and grammar.        Change to "…the sending hub is Yes
       al           11.4                                         requesting. Table 11"
                    .3


S6-290 Techni    47 6.3.   15 This line refers to a coordinator Change all instances of           Yes
       cal          11.4      rather than a hub. However,       "coordinator" to "hub" throughout
                    .3        clause 5.1 defines nodes and      the entire document.
                              hubs as the basic elements of a
                              BAN. Coordinator is not defined
                              and not necessarily
                              synonymous with hub.

S6-291 Editori   48 6.3.    1 Table 12 is redundant and          Strike Table 12 as shown and      Yes
       al           11.4      duplicate of Table 11.             change any references to Table
                    .4                                           12 to reflect Table 11.


S6-292 Editori   48 6.3.   19 Table 13 is redundant and          Strike Table 13 as shown and      Yes
       al           11.5      duplicate of Table 11.             change any references to Table
                    .3                                           13 to reflect Table 11.


S6-293 Techni    48 6.3.   11 Text does not clearly define    Change sentence to: "This one Yes
       cal          11.5      which value of the Status bit   bit field indicates whether the
                    .1        equals acceptance or rejection. coexistence request is accepted
                                                              (value = 1) or rejected (value =
                                                              0).
S6-294 Editori   49 6.3.    2 Grammar                             Add space and correct text as      Yes
       al           11.5                                          "… as shown in Figure 31 in a
                    .4                                            Command…"


S6-295 Editori   51 6.4.   15 Grammar                             Change "optional" to "optionally" Yes
       al           6



S6-296 Techni    52 6.4.   14 Wakeup frames are redundant         Delete Wakeup frame and utilize Yes
       cal          7         with the various Poll messages.     various poll frame functions to
                              In addition, nodes must be          keep nodes awake.
                              actively listening in order to
                              receive such wakeup frames.
                              Hence, nodes to be kept
                              "awake" must be told following
                              some other frame exchange
                              which is equivalent to a poll or
                              ACK+Poll.
S6-297 Techni    53 6.4.    1 Figure 35 includes a field          Change Figure 35 to show             Yes
       cal          8         "Piconet Priority" shown as a 1     "Piconet Priority" as a 2 bit field,
                              bit field. However, this field is   reducing the reserved bits
                              defined as a two bit value in       accordingly.
                              6.4.8.6.
S6-298 Editori   53 6.4.    1 Figure 35 includes a field          Replace "Piconet Priority" with    Yes
       al           8         "Piconet Priority". The basic       "BAN Priority"
                              network element in this
                              document is BAN. Piconet has
                              not been defined and should be
                              striken.
S6-299 Editori   53 6.4.   11 Reference is made to variable       Include minCAP as value in PHY- Yes
       al           8.3       minCAP. This variable is not        dependent MAC sublyer
                              defined in the MAC sublayer         parameters or other appropriate
                              parameter table, Table 23. Is       location.
                              this an application parameter?




S6-300 Editori   54 6.4.    4 Table 13 is redundant and           Delete Table 13 and change any Yes
       al           8.6       duplicate of Table 10.              references to Table 13 to reflect
                                                                  Table 10.
S6-301 Editori   54 6.4.    1 This subclause title contains         Change to "BAN Priority".           Yes
       al           8.6       "Piconet Priority". However, the
                              basic network element structure       Change all instances of "Piconet"
                              in this document is a BAN.            to "BAN" throughout the
                              Piconet has not been defined          document.
                              and should be striken.
S6-302 Techni    60 6.7.    2 User Priority field is defined as a   Add reference to priority levels    Yes
       cal          2.3       4 bit field. This section does not    defined in 7.2.3 as acceptable
                              define the possible values for        values for setting User Priority
                              this field. Should the 4 bit          field.
                              values of subclause 7.2.3 be
                              used? Should the 2 bit values
                              of subclause 6.3.11.4.2 be
                              used?


S6-303 Techni    63 6.7.    1 It is not clear whether the           Add text to clarify that the  Yes
       cal          6         connection allocation request         connection allocation request
                              that accompanies such a Group         that accompanies such a Group
                              Connection IE applies to each         Connection IE applies to each
                              member of the group or the            member of the group.
                              aggregate of the group.


S6-304 Editori   64 6.7.   21 Typographical error.                  Change title of this subclause to Yes
       al           10                                              "Delayed Bilink Assignment IE"



S6-305 Techni       6.3.      It is required to explicit mention Include the text in the section
       cal          1         that Beacon shifting sequence, 6.3.1
                              channel hopping state and next
                              channel hop fields are optional
                              in beacon message

S6-306 Techni       6.4.      The functionality of T-Poll      Rework section 6.4.6
       cal          6         message and Poll message
                              presented in the draft are same.
                              The T-Poll should be merged
                              with a Poll message. Additional
                              complexity in maintaining the T-
                              Poll message

S6-307 Techni Pag 6.4.        Type II access poll requires          Inclusion of sleep bit in the Poll YES
       cal    e 51 6          sleep bit in the poll message to      message (by reusing an existing
                              explicitly tell nodes to go to        bit)
                              sleep mode
S6-308 Techni    51 6.4.     10 Timed-Poll (T-Poll)              Since the size of payload in T-
       cal          6                                            poll is constant. The T-poll can
                                                                 be merged with the poll
                                                                 message. This will reduce the
                                                                 total number of management
                                                                 frame and therefore MAC
                                                                 complexity.
S6-309 Techni    52 6.4. 22     "It is locally broadcast by a    change the number based
       cal          8           hub... " --> B2 message is for   constraint to the general time
                                exchaning frame between other based constraint.
                                piconet coordinators. Local
                                broadcast is only for broadcast
                                to all nodes in a BAN (Table 16)

S6-310 Techni    24 6.2. 37     "In B2 frames locally broadcast      clarification
       cal          1.1.        by a hub... " --> B2 message is
                    11          for exchanging frame between
                                other piconet coordinators.
                                Local broadcast is only for
                                broadcast to all nodes in a BAN
                                (Table 16)
S6-311 Techni    47 6.3.     18 Co-existence mode terminology        explicitly mention that time       YES
       cal          11.4        needs more clarification and is      sharing and offset piconet
                    .3          not defined well in the draft        synchronization are non-
                                                                     interference modes. Rename
                                                                     "piconet enquiry" (term not
                                                                     defined or used anywhere else in
                                                                     the draft) in Tables 11, 12, 13 to
                                                                     "interference mitigation mode"

S6-312 Editori   57 6.6.     11 Table caption typo                   rage => rate                          Yes
       al           2.3


S6-313 Techni    57 6.6.     11 the use of this table is very        Fill in the table or explain better   Yes
       cal          2.3         unclear with all these reserved why there is so much reserved
                                bits. It refers to 9.1 which is only bits
                                for the NB PHY and not the
                                others. Moreover the numbre of
                                rates (5) is less than the UWB
                                PHY possiblities

S6-314 Techni    47 6.3. 1      I don't see any difference           Change "Command -                     Yes
       cal          11.4        between "coexistence request"        Coexistence Request" to
                    .1          and "coexistence response".          "Command - Coexistence Time
                                                                     Sharing".
S6-315 Techni    52 6.4. 4-8 The "received signal strength of Remove the Relay Link Quality             Yes
       cal          6.4      signals" is not an accurate       field
                             represenation of the quality of
                             the link in presence of noise and
                             interference and can't be use for
                             an abosulte calibration.

S6-316 Editori   20 6.2.   16 The subclause heading is              Fix the indentation for 5th level   Yes
       al           1.1.      indented too far.                     subclause headings throughout
                    1                                               the draft.
S6-317 Editori   24 6.2.   40 Extra "6."                            Delete "6."                         Yes
       al           1.1.
                    11
S6-318 Editori   27 6.2.   12 A number without a unit is            Change "1" to "one" here and      Yes
       al           2         spelled out.                          throughout the document when it
                                                                    is used without a unit. Also look
                                                                    for other occurrences, e.g., "0",
                                                                    "2", and spell them out as well.

S6-319 Editori   37 6.3.    9 This is an example of a number        Change "2" to "two" and "3" to    Yes
       al           4.3       without a unit that should be         "three" and check the rest of the
                              spelled out.                          draft.
S6-320 Editori   42 6.3.    1 The cell borders are not correct      Fix the cell borders              Yes
       al           7.3       (i.e., the cell body borders are
                              two thick for the first two rows.)

S6-321 Editori   46 6.3.    3 "ith" should be "i^th" with the i     Change as indicated.                Yes
       al           10.2      italicized (variables are italics).
                              Also, the spacing between the
                              previous items and this
                              paragraph needs to be
                              increased.
S6-322 Editori   47 6.3.    8 The depth for this heading            Delete the subclause heading or Yes
       al           11.4      should probably be 6, but you         reorganize the subclauses so a
                    .2        are not allowed a depth of 6.         dept of 6 is not required. This
                                                                    affects a few subclauses in this
                                                                    area.
S6-323 Editori   48 6.3.    3 Subclause numbering is wrong          Delete the "(b)".                Yes
       al           11.5      "6.3.11.5 (b)"



S6-324 Editori   47 6.3.    1 "6.3.11.4.1 Command –                 Lower case the title to match the Yes
       al           11.4      Coexistence Request", titles are      2009 Style Guide here and
                    .1        lower case except for the first       throughout the draft.
                              word, proper nouns and
                              acronyms.
S6-325 Techni    49 6.3.   10 "The Battery Power Remaining          Change to "The Battery Power        Yes
       cal          11.5      field is set to" doesn't make a       Remaining field shall be set to".
                    .5        requirement.                          This applies to all the field
                                                                    descriptions.
S6-326 Editori   52 6.4.    1 Extra "["                          Delete "["                        Yes
       al           8


S6-327 Editori   53 6.4.    4 An IEEE standard cannot make Refer this name to the IEEE             Yes
       al           8.6       claims of safety. "Life critical   editors for review. They may
                              Medical" may cross that line.      specify a better name. I
                                                                 understand the idea behind it,
                                                                 but different wording may be
                                                                 required.
S6-328 Editori   59 6.7.    8 Don't put the length of this field Delete "(= 6N)" from the figure   Yes
       al           2         in the figure. "(= 6N)". The       and similar lengths from the
                              length is defined in another       other IE figures.
                              figure. Keeping these numbers
                              up to date as the standard
                              changes will only lead to errors.

S6-329 Techni    52 6.4. 4-8 The "received signal strength of    Keep history of retries and       Yes
       cal          6.4      signals" does not truly reflect     calculate average packet
                             the quality of the link in          success rate and use this for
                             presence of noise and               quality of link
                             interference.
S6-330 -
S367
missing
?
S6-367 Editori   36 6.3.   18 Would the interval be more         Change to [0, 2^128). Same on No
         al         3.2.      precisely stated as [0, 2^128).    page 37 line 29.
                    1         That is, a semi closed interval.

S6-368 Techni    29 6.3.    9 The valid range of L is not        Provide the valid range of L.     Yes
       cal          1.3       specified.


S6-369 Techni    53 6.4.    7 The valid range of L is not        Provide the valid range of L.     Yes
       cal          8.2       specified.


S6-370 Techni    59 6.7.    2 The valid range of L is not        Provide the valid range of L.     Yes
       cal          1.2       specified.
S6-371 Gener     33 6.3.    1 Most important requirements for     As in comment                    No
       al           2.3.      BAN are low-cost and low-
                    4         power/energy, so efficient
                              cryptographic algorithms in
                              terms of these criteria should be
                              considered. In ISO/IEC JTC
                              1/SC27, ISO/IEC 29192
                              (lightweight cryptography) is
                              developed, and it is suitable in
                              particular for constrained
                              environments (i.e. low cost, low
                              energy consumption). The
                              scope of ISO/IEC 29192
                              includes health-care systems
                              (e.g. Body Area Networks) and
                              sensor networks. ISO/IEC
                              29192 should be considered in
                              IEEE802.15.6.
S6-372 Techni    47 6.3.   18 Co-existence mode terminology       explicitly mention that time       YES
       cal          11.4      needs more clarification and is     sharing and offset piconet
                    .3        not defined well in the draft       synchronization are non-
                                                                  interference modes. Rename
                                                                  "piconet enquiry" (term not
                                                                  defined or used anywhere else in
                                                                  the draft) in Tables 11, 12, 13 to
                                                                  "interference mitigation mode"

S6-373 Editori   22 6.2.    4 typo                                Change curren to current         Yes
       al           1.1.
                    6




S6-374 Editori   47 6.3.   12 Table 10 is repeated as a Table Reference to Table 10                Yes
       al           11.4      13 on page 54
                    .2




S6-375 Editori   48 6.3.   19 There are two Table 13, page        Reference to Table 13 either     Yes
       al           11.5      48 and page 54                      page 48 or page 54
                    .3
S6-376 Editori   22 6.2.    4 Typo                                 Change "curren" to "current"          Yes
       al           1.1.
                    6


S6-377 Editori   29 6.3.   16 enabled' & 'not enabled' should Swap the 'enabled' and 'not                Yes
       al           1.4       be the other way around.        enabled' in that sentence.



S6-378 Editori   29 6.3.   28 enabled' & 'not enabled' should Swap the 'enabled' and 'not                Yes
       al           1.6       be the other way around.        enabled' in that sentence.



S6-379 Editori   34 6.3.   28 Sub-clause title font                Change "PKY" to PKY with              Yes
       al           2.6.                                           subscript y
                    2


S6-380 Techni    45 6.3.    1 EAP1 Length can determined           Discuss the necessity of keeping Yes
       cal          8         from RAP1 Start in the beacon        B+EAP1 Length in the multinode
                              frame                                connection assignment frame


S6-381 Techni    45 6.3.    1 EAP2 Length can determined           Discuss the necessity of keeping Yes
       cal          8         from EAP2 start in the               EAP2 Length in the multinode
                              connection assignment frame          connection assignment frame
                              and RAP2 Start in the beacon
                              frame
S6-382 Editori   57 6.6.   11 Table caption typo                   rage => rate                          Yes
       al           2.3
S6-383 Techni    57 6.6.   11 the use of this table is very        Fill in the table or explain better   Yes
       cal          2.3       unclear with all these reserved why there is so much reserved
                              bits. It refers to 9.1 which is only bits
                              for the NB PHY and not the
                              others. Moreover the numbre of
                              rates (5) is less than the UWB
                              PHY possiblities

S6-384 Editori   30 6.3.   16 *n* seems not being defined in       Add definition of *n* in this table No
       al           1.10      table 4.                             4
                    .1        ( I presume "n" is phase of the
                              Beacon Shifting Ssequence
                              NOT the n-th beacon period.)
S6-385 Techni    44 6.3.    1 "B+EAP1 Length" and "EAP2            delete "B+EAP1 Length" and            Yes
       cal          8         Length" seems redundant as           "EAP2 Length" fields from
                              they are in beacon and have          "Multinode Connection
                              been already removed from            Assignment" frame
                              "Connection Assignment"
                              frame.
S6-386 Editori   47 6.3.   14 Wrong Tiltle                      to replace " Command-                 No
       al           11.4                                        Coexistence Response" with
                    .3                                          Coexistence Mode"
S6-387 Techni    48 6.3.   11 the exact value of "Status" field Define as follows;                    Yes
       cal          11.5      is not defined.                   0:accepted, 1:rejected
                    .1
S6-388 Editori   53 6.4.    1 In Figure 35. Wrong number of To replace " 1" bit for Piconet          No
       al           8         field length for "piconet Priority" priority field with "2" bits
                              and "reserved " fields              To replace "5" bits for "reserved"
                                                                  field with "4" bits
S6-389 Techni    30 6.3.   14 How should we choose the            A hub shall be able to get the
       cal          1.10      value of the Beacon Shifting        Beacon Shifting Sequence Index
                    .1        Sequence Index?                     by hearing beacons of neighbor
                                                                  hubs.
S6-390 Techni    46 6.3.   20 When the hubs which are not Specify the timing for receiving
       cal          11.3      synchronized with each other        the Coexistence Response.
                              send or receive both
                              "Coexistence Request" and
                              "Coexistence Response"?
                              The exact timing(allocation
                              phase) is defined in the
                              document?
S6-391 Editori   48 6.3.    3 Wrong numbering for title           To delete "(b)"
       al           11.5
                    (b)


S6-392 Techni 20 6.2.         Are both sender ID and sender       Remove sender MAC address           No
       cal    (38) 1.1        MAC address needed in the           from the beacon (as this can be
                   (6.3.      beacon? The former is in the        sent in the Connection
                   1)         MAC header while the latter is in   Assignment from the hub) or
                              the Beacon Payload. Removal         specifically show the need for it
                              of MAC address would save 6         in the beacon
                              octets.

S6-393 Techni    21 6.2. 18- In relay mode – what are the         Clarify use of node id's in relay  No
       cal          1.1. 19 correct settings for recipient and    mode. ―From leaf to relay node
                    5        sender ID's - is the recipient ID    and relay to hub, the sender id is
                             that of hub and sender id that of    the leaf node id and the recipient
                             original leaf node sender?           id is the hub id.‖ or is it ―From
                                                                  leaf to relay node, the sender id
                                                                  is the leaf node id and the
                                                                  recipient id is the relay id. From
                                                                  relay to hub, the sender id is the
                                                                  leaf node id and the recipient id
                                                                  is updated to that of the hub id‖

S6-394 Techni    29 6.3.   10 pAllocationSlotMin is not                                               Yes
       cal          1.3       defined. Is its size going to be
                              based on minimum/maximum
                              frame durations?
S6-395 Techni   29 6.3.     10 pAllocationSlotResolution is not                                       Yes
       cal         1.3         defined. Is its size going to be
                               based on the
                               pCSMASlotLength?
S6-396 Techni   31 6.3.        What happens if one end              Clarify failure procedure for     Yes
       cal         2           refuses a security association –     security disassociation and
                               is it to send a disassociation?      possibly add status/error code to
                               PTK missing/invalid is shown in      security disassociation
                               the state machine on P 24, but
                               no message is defined to carry
                               this status and there is no field
                               to carry it in a security
                               disassociation frame either?

S6-397 Techni   32 6.3.      8 This Security Level Required         Remove this field from the        No
       cal         2.3.        field is a repeat of what is in      Security Association Payload or
                   2           MAC Header, so can it be             update state machine to allow
                               removed from frame payload? It       update of Security Association.
                               would only be needed in both
                               places if a security association
                               was allowed in the connected
                               state to change an existing level
                               with the current level carrried in
                               the MAC Header and new level
                               in frame payload?

S6-398 Techni   38          12 This line says PTK frame is sent Change text ―...to a secured     No
       cal           6.3.      to a ―secured node‖, but PTK is node‖ to ―...to a secured node in
                     5         only allowed in connected state the connected state‖
                               (not secured state) as per fig 4a

S6-399 Techni   39 6.3.   17 What is Former Hub Address to Need to add a section on the         No
       cal         6.3        be used for?                    role of this field and suggest
                                                              making it optional
S6-400 Techni   40 6.3. Fig Channel Order IE is shown in      The use of Connection Change No
       cal         6.6 24 the Connection Change               Indicator to refer to IE's in the
                        (als Indicator, but Channel Order IE Connection Request and
                        o fig is shown only in a Connection   Assignment frames needs to be
                        25) Assignment and not in the         made consistent
                              Connection Request? Similarly
                              the Group Connection IE in a
                              Request is not covered by the
                              Connection Change Indicator.
                              Also there are >8 optional IE's
                              in an Assignment frame.
S6-401 Techni    41 6.3. 7,8 The text referring to the use of       Explain role of 2nd octet.         No
       cal/Edi      6.7      two octets to hold the 1 octet
       torial       (and     long superframe sequence
                    also     number of the wakeup phase is
                    6.3.     unclear as to the use of the 2nd
                    6.8)     octet and why a 2nd octet is
                             needed - is it to allow a node to
                             sleep for 64K superframes. No
                             mention of encoding of 2nd
                             octet at all in wakeup period in
                             6.3.6.8.
S6-402 Techni    42 6.3.     Mac and PHY Capability of the          Suggest that the MAC and PHY       No
       cal          7.0      Hub is in the Beacon, so why is        capability should be made
                             it not needed in all Connection        optional in the Connection
                             Assignment frames                      Assignment for use only in non
                                                                    beacon modes.

S6-403 Techni    50 6.4.      Clarify whether or not block                                      No
       cal          2         transfers can span more than 1
                              superframe when the block
                              does not fit the allocation
                              interval?
S6-404 Techni    52 6.4.      Text refers to it holding received Change name Relay Link Quality No
       cal          6.4       signal strength – suggest the      to Relay Signal Strength
                              name should be changed as it
                              suggests LQI as per 6.9.8 of
                              802.15.4 (and would that be
                              more appropriate to use here?).
                              Also, would it better to send a
                              rolling average of the signal
                              strength to a prospective node
                              rather than an instantaneous
                              value as implied here?

S6-405 Techni    52 6.4.      B2 is a legacy name from an           Rename B2 frame to indicate its No
       cal          8         earlier proposal where there          purpose e.g. Contention Beacon
                              was a B1.


S6-406 Techni    54 6.4.      Piconet priority unclear as           Piconet needs to be defined –      No
       cal          8.6       piconet is defined in the             from later 7.12.3 it can be seen
                              document's definitions or in          to refer to a particular BAN
                              earlier sections. Also, the           (nodes connected to a hub) in
                              function of piconet priority is not   the case of co-existing
                              stated, i.e. its use in deciding      BAN's/hubs.
                              allocations in the CAP when
                              multiple BAN's (piconets) exist.
                              Similarly piconet interaction
                              support is not referenced or
                              defined elsewhere
S6-407 Techni    55 6.6.       Current MAC Capability field is      Rather than include the specific No
       cal          1.0        limited and cannot provide for       Battery Level Indication
                               future commands (except in           command, MAC Capability
                               rsvd bits) as it is only 2 octets.   should not include commands at
                                                                    all or it should list all the
                                                                    supported Command ID's. It
                                                                    would be preferable to use a new
                                                                    Commands Capability IE for this
                                                                    in specified frames such as
                                                                    Connection Request/Assignment
                                                                    and remove the commands
                                                                    supported from the 2 octet MAC
                                                                    Capability


S6-408 Techni    55 6.6.       Should there be Capability fields As per comment on revising            No
       cal          1.0        related to Security, e.g based on MAC Capability to define
                               encodings for security level and commands in an IE
                               cipher function?

S6-409 Techni    62 6.7.     The operation of Group               Add text on connection phase for No
       cal          6        Connection needs to be               groups.
                             clarified, e.g. presumably each
                             node in the group issues a
                             connection request with its NID
                             and Group ID, but how do they
                             treat received multicasts to their
                             pre-installed group ID while in
                             orphan state or does a node
                             send a connection request to
                             hub with the group size set to a
                             pre-installed max group size to
                             connect them all (line 22) and
                             which node does this if so (and
                             presumably the hub returns
                             current group size in the
                             assignment frame)?
S6-410 Editori   22 6.2. 3,4 typo's                               ―exclusieve‖ to ―exclusive‖ and  No
       al           1.1.                                          ―curren‖ to ―current‖
                    6
S6-411 Editori   23 6.2.     Use of ―send a post‖ is not clear replace "send a post" with "post No
       al           1.1.     at this point, as it implies post is a frame‖
                    9        a frame and the difference
                             between post and poll operation
                             is not stated until 7.6?

S6-412 Editori   24 6.2.   41 Text overly complicated in g          ―...from its value in the data     No
       al           1.1.      part 1                                frame addressed to the same
                    11                                              recipient....‖ and also remove 6
                                                                    at start
S6-413 Editori   28 6.3.     In figure 14 the RAP1 Start field Remove dashing around RAP1         No
       al           1        is dashed, but this field is not
                             optional.
S6-414 Editori   40 6.3.     The titles of IE's should be                                         No
       al           6.6.     changed to indicate that they
                    3-6      are requests and remove
                             assignment(as they are
                             requests to change which will
                             not take effect until the
                             assignment is sent by the hub).
                             This would align with 6.3.7.13-
                             16
S6-415 Editori   51 6.4.     First sentence here needs to                                         No
       al           6        state it is also sent by a relay
                             node as per 6.4.6.4. Also state
                             that a relay can do resource
                             allocation using a T-Poll

S6-416 Editori   53 6.4.   3 this is sent to >1 neighbor hub     ―neighboring coordinator‖ to     No
       al           8.5                                          ―neighboring coordinators‖


S6-417 Editori   57 6.6.     Table 11 Title wrong                Change ―Data Rage...‖ to ―Data   No
       al           2.3                                          Rate....‖

S6-418 Editori   19    6     This comment applies to             Restore all instances of "one" to Yes
       al                    numerous clauses. Some, but         "1" in the context of "set to one",
                             not all, instances of "1" are       "set … to one", "setting to one",
                             converted to "one", and similarly   or "setting … to one". Likewise,
                             some, but not all, instances of     restore all instances of "zero" to
                             "0" are converted to "zero". The    "1" in the context of "set to zero",
                             draft also has "random access       "set … to zero", "setting to zero",
                             phase one" and "random              or "setting … to zero". (I have
                             access phase 2". It is not          made these changes in the draft
                             advisable to strictly follow the    revision I am working on.)
                             English grammar rules here
                             (that single-digit numbers must
                             be spelled out). Rather, it is
                             more consistent to use the math
                             symbol, especially when such a
                             symbol appears in a table as
                             well (such as in a field value
                             column).
S6-419 Techni    19    6     1 Clause 6 and, in fact, all of the    Edit the text to reflect its      Yes.
       cal                     later clauses, are missing a lot     normative status by using "shall"
                               of "shall"s. It's not good enough    where appropriate in clauses 6-
                               to say, for example, that "The       11. (This will be about 20,000
                               BAN ID field is set to the           additional uses.)
                               abbreviated address of the body
                               area network (BAN) in which the
                               current frame is transferred"
                               [6.2.1.4]. This should read,
                               "The BAN ID field shall be set to
                               the abbreviated address of the
                               body area network (BAN) in
                               which the current frame is
                               transferred."
S6-420 Techni 51-     6.4      There is not much difference         Consolidate these two frames.     Yes
       cal    52               between Poll frame defined in
                               clause 6.4.5 and Wakeup frame
                               defined in clause 6.4.7.
S6-421 Techni    58   6.7    2 Table 15, row 14, the IE name        Fix inconsistency                 Yes
       cal                     does not agree with the
                               Description. IN one Bilink and
                               in the other uplink
S6-422 Techni    57   6.7   21 This is the last line on the page,   Change below to in the following Yes
       cal                     nothing is defined below.            sub clauses

S6-423 Techni 51-     6.4      There is not much difference   Consolidate these two frames.           Yes
       cal    52               between the Poll frame defined
                               in clause 6.4.5 and the Wakeup
                               frame defined in clause 6.4.7.

S6-424 Techni 51-     6.4      There is not much difference  Consolidate these two frames.   Yes
       cal    52               between Poll frame defined in
                               clause 6.4.5 and Wakeup frame
                               defined in clause 6.4.7.
S6-425 Editori        6.1    2 Skinny, heavy not appropriate Use terms that are more general
       al



S6-426 Editori   28   6.2      Figure 14 missing # of octets        add "# of octets" Global change
       al                                                           in technical document



S6-427 Techni    58   6.7      Table 15 Missing "Capability         Add Capability Element that       Yes
       cal                     Element" that defines how many       defines the number of PHYs
                               PHYs are supported by the            supported by the Node. It is
                               "node".                              possible for a mfg to develop
                                                                    and offer a multi-mode product.
S6-428
missing
?
S6-429 Techni 51-     6.4   There is not much difference  Consolidate these two frames.           Yes
       cal    52            between Poll frame defined in
                            clause 6.4.5 and Wakeup frame
                            defined in clause 6.4.7.




S6-430 Techni 51-     6.4   There is not much difference   Consolidate these two frames.          Yes
       cal    52            between the Poll frame defined
                            in clause 6.4.5 and the Wakeup
                            frame defined in clause 6.4.7.




S6-431 Editori   19    6    This comment applies to             Restore all instances of "one" to Yes
       al                   numerous clauses. Some, but         "1" in the context of "set to one",
                            not all, instances of "1" are       "set … to one", "setting to one",
                            converted to "one", and similarly   or "setting … to one". Likewise,
S6-432 Editori   19    6    some, but not all, instances of
                            This comment applies to             restore all instances of "zero" to Yes
                                                                Restore all instances of "one" to
       al                   numerous clauses. Some, but         "1" in the context of "set to one",
                            not all, instances of "1" are       "set … to one", "setting to one",
                            converted to "one", and similarly   or "setting … to one". Likewise,
                            some, but not all, instances of     restore all instances of "zero" to
                            "0" are converted to "zero". The    "1" in the context of "set to zero",
                            draft also has "random access       "set … to zero", "setting to zero",
                            phase one" and "random              or "setting … to zero". (I have
                            access phase 2". It is not          made these changes in the draft
                            advisable to strictly follow the    revision I am working on.)
                            English grammar rules here
                            (that single-digit numbers must
                            be spelled out). Rather, it is
                            more consistent to use the math
                            symbol, especially when such a
                            symbol appears in a table as
                            well (such as in a field value
                            column).
S6-433 Techni          6      Before describing the MAC         add a section before section 6
       cal/Edi                frame format, it is required to
       torial                 mention the Superframe
                              structure and introduction to
                              channel access
S6-434 Techni    20   6.2   4 The ordering of octets and bits   Delete the bit and octet ordering Yes
       cal                    has already been defined          from Figure 8 going forward.
                              (nicely) in the opening of this   Only include the ordering in the
                              Clause. Repeating the octet       figure if the convention is not
                              and bit ordering in each figure   being followed. If the convention
                              can only lead to mistakes and     is not being followed, then you
                              misunderstanding.s                probably want to follow it anyway
                                                                (CRCs and some security fields
                                                                are exceptions).

S6-435
missing
?
S6-436 Editori   55   6.6 7 ++ Aloha                            ALOHA                            BLA
        al                                                                                       NK

S6-437 Editori   55   6.6 7 ++ Aloha                            ALOHA
       al

S6-438 Techni    20 6.2.      (TR) Clause 6.2.1, p. 20, Fig. 9: Suggested remedy: Implement      Yes
       cal          1         the MAC header seems to only accordingly.
                              allow for short 1-octet
                              addresses, thus begging the
                              question how the full extended
                              addresses are to be
                              communicated. Suggested
                              remedy: Allow addressing
                              option where the full
                              extended address is included
                              in the MAC frame.
S6-439 Techni   20 6.2.   (TR) Clause 6.2.1.1, p. 20, Fig. Suggested remedy: Implement           Yes
       cal         1.1    10: (cf. also Clause 6.2.1.1.8,     accordingly.
                          Table 3): The partitioning of the
                          6 bits used to indicate the frame
                          type/subtype seems to be
                          wasteful. As an example, 13/16
                          Management frames seem to
                          be used and 10/16 control
                          frames, but only 1/16 data
                          frames. It seems better to
                          define this as a ―flat‖ 6-bit frame
                          type space (with 24/64 used
                          frame types), since this allows
                          more flexibility in allocating the
                          remaining 40 reserved options.
                          Suggested remedy:
                          Implement accordingly.


S6-440 Techni   21 6.2.   (TR) Clause 6.2.1.1.4, p. 21:          Suggested remedy: Allow more    Yes
       cal         1.1.   The key index field of 1 bit only      flexibility in specifying key
                   4      seems not to allow sufficient          indicators.
                          flexibility in distinguishing
                          different keys during the lifetime
S6-441 Techni   20 6.2.   of the system. Moreover, only
                          (T) Clause 6.2.1.1, p. 20, Fig.        Suggested remedy: Investigate Yes
       cal         1.1    10: The 4-bit fragment                 potential savings in avg. frame
                          number/… is often not used.            control field size by adopting the
                          This suggests that one could           strategy outlined above.
                          economize on frame size by
                          using a primitive Hufmann
                          coding (define 1 bit ON/OFF
                          and 4-bits elsewhere if used).
                          This would save 3 bits in the
                          frame control field in most
                          cases. Similarly, one could
                          indicate security info later on in
                          the frame, if security is actually
                          used (1-bit in FCF; 3 bits
                          elsewhere if used). Extending
                          this could shave off at least one
                          octet per frame, where this octet
                          is only lost again if granularity is
                          actually required. Suggested
                          remedy: Investigate potential
                          savings in avg. frame control
                          field size by adopting the
                          strategy outlined above.
S6-442 Techni   26 6.2.   (TR) Clause 6.2.2, p. 26, Fig.     Suggested remedy: Remove         Yes
       cal         2      12: The MIC subfield should not    MIC subfield and add language
                          be visible, since the CCM          that Frame Payload may be
                          construct is a ―black box‖         secured, depending on setting of
                          construct‖, where one does not     security level indicator.
                          have to have any insight on
                          where the data authenticity bits
                          show up in the frame. Besides,
                          with CCM, the MIC is actually a
                          truncated CBC-MAC code that
                          is subsequently encrypted using
                          a stream cipher. Since I am
                          sure hardly anyone who
                          implements the specification
                          does understand the sentence
                          above, I would strongly suggest
                          keeping the internal workings of
                          the cryptographic mode of
                          operation (here: CCM mode, but
                          could be something else)
                          abstract and non-visible to
                          people interested in frame
                          layouts. Suggested remedy:
                          Remove MIC subfield and
                          add language that Frame
                          Payload may be secured,
                          depending on setting of
                          security level indicator.


S6-443 Techni   26 6.2.   (TR) Clause 6.2.2.1, p. 26, l. 25: Suggested remedy: Replace this Yes
       cal         2.1    The requirement that the frame by ―incremented (by at least
                          counter (Security Sequence         one)‖.
                          Counter) is incremented by one
                          is too strict and unobservable by
                          other nodes. Suggested
                          remedy: Replace this by
                          “incremented (by at least
                          one)”.
S6-444 Techni   26 6.2.   (TR) Clause 6.2.2.1, p. 26: This   Suggested remedy: Each device Yes
       cal         2.1    suggests that one needs to         should only use one frame
                          store a frame counter for every    counter (Security Sequence
                          key, which seems wasteful: a       Counter) for outgoing frames.
                          sender only needs to store one     Similarly, a recipient only needs
                          frame counter for outgoing         to store one frame counter per
                          traffic and just increments this   device it receives frames from
                          along the way, independent of      (so as to implement replay
                          frame type and keying material     protection).
                          in question. Suggested
                          remedy: Each device should
                          only use one frame counter
                          (Security Sequence Counter)
                          for outgoing frames.
                          Similarly, a recipient only
                          needs to store one frame
                          counter per device it receives
                          frames from (so as to
                          implement replay protection).


S6-445 Techni   27 6.2.   (TR) Clause 6.2.2.1, p. 27: This Suggested remedy: Resends      Yes
       cal         2.1    suggests that the SSN frame      should use the same frame
                          counter is incremented even in counter.
                          case of resends. If so, this
                          thwarts the security service of
                          replay protection (since now, a
                          device can send the same
                          frame twice, but with different
                          SSN numbers). Suggested
                          remedy: Resends should use
                          the same frame counter.
S6-446 Techni   32 6.3.   (TR) Clause 6.3.2.3.1, p. 32,      Suggested remedy: allow much Yes
       cal         2.3.   Table 5: This suggests that the more flexibility in terms of
                   1      particular protocols for a fixed   schemes supported (algorithm
                          field value are fixed (and as      agility!).
                          defined in Clause 8, with only 80-
                          bit crypto strength). What about
                          algorithm agility here? Why is
                          there no public-key based
                          authenticated key agreement
                          scheme with certificates? What
                          about a proper symmetric-key
                          based authenticated key
                          agreement scheme?
                          Suggested remedy: allow
                          much more flexibility in
                          terms of schemes supported
                          (algorithm agility!).

S6-447 Techni   32 6.3.   (TR) Clause 6.3.2.3.2, p. 32,   Suggested remedy: Implement           Yes
       cal         2.3.   Table 6: The security level     accordingly.
                   2      options seem too limited.
                          Moreover, this would benefit
                          from making this dependent on
                          frame type/subtype in question,
                          so as to allow more flexibility
                          (this is also done in 802.15.4-
                          2006). Suggested remedy:
                          Implement accordingly.

S6-448 Techni   33 6.3.   (TR) Clause 6.3.2.3.4, p. 33,        Suggested remedy: Remove         Yes
       cal         2.3.   Table 7: No clue where Camilia       Camilia from the list and make
                   4      comes from. While this was a         everything except AES-128 a
                          2nd round AES Candidate block        reserved value.
                          cipher, everyone else in the
                          world who specified something
                          post 2001 uses AES-128 (a.k.a.
                          Rijndael). There do not seem to
                          be any advantages in
                          introducing this somewhat
                          arbitrary other cipher and lots of
                          disadvantages: lack of
                          compatibility, higher
                          implementation cost, control
                          traffic cost, key management
                          cost. Suggested remedy:
                          Remove Camilia from the list
                          and make everything except
                          AES-128 a reserved value.
S6-449 Techni   33 6.3.   (TR) Clause 6.3.2.5, p. 33, Fig. Suggested remedy: implement            Yes
       cal         2.5    19: The protocol messages            accordingly (1-octet field seems
                          should also include a protocol       sufficient).
                          identifier (e.g., to logically group
                          different protocol flows
                          corresponding to a single
                          protocol invocation). Suggested
                          remedy: implement accordingly
                          (1-octet field seems sufficient).




S6-450 Techni   36 6.3.   (TR) Clause 6.3.3.1, p. 36: The Suggested remedy: Use EUI-64 Yes
       cal         3.1    extended addresses seem to be addresses, rather than 48-bit
                          EUI-48 addresses. This seems entries.
                          to be too short, given the
                          potential number of devices in
                          body area networks. Why not
                          use an EUI-64, so as to be sure
                          to have globally unique device
                          identifiers? This would allow not
                          running out of space and would
                          also allow device certificates
                          based on this address issued by
                          a CA. Suggested remedy: Use
                          EUI-64 addresses, rather than
                          48-bit entries.


S6-451 Techni   36 6.3.   Clause 6.3.3.2.1, p. 36:            Suggested remedy: Make this a       Yes
       cal         3.2.   Randomness of the sender            proper challenge response
                   1      nonce does not provide any          protocol. I would be happy to
                          freshness/liveness/timeliness       help with this.
                          assurances to the recipient
                          (since not a proper challenge
                          response protocol). Suggested
                          remedy: Make this a proper
                          challenge response protocol. I
                          would be happy to help with this.
S6-452 Techni   38 6.3.      Clause 6.3.5, p. 38, Fig. 22: The Suggested remedy: Please             Yes
       cal         5         structure of the group temporal clarify intent, since this is highly
                             key is unclear. Is this supposed unclear now.
                             to specify the structure of keying
                             material? If so, where are the
                             policy fields, such as key validity
                             period, key usage, etc?
                             Moreover, how does the MAC
                             even know about these
                             (generally) higher-layer
                             concepts? Shouldn‘t the sender
                             address be the address of the
                             key originator instead? What
                             about SSN: shouldn‘t this be a
                             key serial number instead (cf.,
                             e.g., corresponding notions for
                             public keys with X509 as
                             specified with RFC 5280)?
                             Suggested remedy: Please
                             clarify intent, since this is highly
                             unclear now.


S6-453 Techni   31 6.3.    9 The current specification of this   this field should be used to     Yes
       cal         1.13      field can create ambiguity about    indicate the next guaranteed
                             whether a future superframe is      active superframe and another
                             active or not. For example a low    bit (we can use the relay bit in
                             duty cycle node wants to use        the MAC header for this) used to
                             RAP1 for access and uses the        indicate if the next superframe
                             beacon to synchronize before        would be active or not.
                             contending in RAP1. if it hears a
                             beacon without an inactive
                             duration, it could assume that
                             every superframe is active, but
                             could find that the next beacon
                             indicated there would be a
                             number of subsequent inactive
                             superframes.


S6-454 Techni   32 6.3.   15 don‘t we need to say something If we agree this is an application No
       cal         2.3.      about this field? That the node problem, then that is fine.
                   4         needs to use the cipher function
                             indicated in this field in the
                             frame received from the hub?

S6-455 Techni   53 6.4.   11 The current wording states that The CAP length should be set to No
       cal         8.3       "CAP length is set to more than a value no less than minCAP.
                             minCAP..." this should be >=
                             minCAP
S6-456 Editori   54 6.4.    4 Table 4 gives application         I suggest changing "Life critical   No
       al           8.6       specific priorities. Not sure how medical" to "High priority
                              these classifications are used? medical"
                              Also am a bit wary of the use of
                              "Life critical Medical"

S6-457 Techni    55 6.6.    3 the final field in figure 36 -     change field to command            Yes
       cal          1         shouldn't it read Command          message support
                              Message support, since this
                              now imcludes battery level
                              indication as well as
                              coexistence support
                              commands?
S6-458 Techni    56 6.6.   19 directly related to previous       this section should be remaned Yes
       cal          1.14      comment 7                          to Command message support
                                                                 and the text modified accordingly


S6-459 Techni    57 6.6.    1 how is this field used by the                                         No
       cal          2.1       MAC or is it just informational?



S6-460 Editori   47 6.3.    6 Wrong number of bits for the       to replace " 3" bits for coxistence Yes
       al           11.4      "coexistence Mode" field           mode field with "2"
                    .1


S6-461 Techni    47 6.3.      table 11- the reserved field    To use the field value "11" to        Yes
       cal          11.4      should be replaced with Piconet indicate "Piconet Enquiry
                    .3        Enquiry Response                Response" frame


S6-462 Techni    48 6.3.    7 BAN Descriptor which is            In figure 30 to replace the field Yes
       cal          11.5      required for coexistence           "Allocation Time/Duty Cycle" with
                    (b)       mechanisms is missing from         "Allocation Time/Duty Cycle/BAN
                              figure 30 and need to be           Descriptor" but still BAN
                              defined                            descriptor need to be defined

S6-463 Editori   48 6.3.   19 in complete caption for table 13. To replace the caption of table     Yes
       al           11.5                                        13 "coexistence modes" with
                    .3                                          "coexistence modes and
                                                                allocation time"

S6-464 Editori   48 6.3.    1 in complete caption in table 12: table 12: to replace "coexistence Yes
       al           11.4      to replace coexistence mode      modes" with "coexistence modes
                    .4        with coexistence mode and        and allocation time"
                              allocation time
S6-465 Editori   53 6.4.        2 in figure 35 piconet priority field To replace piconet priority length Yes
       al           8             of 1 bit should be replaced by of "1" with "2"
                                  2 bits (see table 13), and
                                  reserved bits reduced to 4 bits

S6-466 Techni    20 6.2.       14 the rational is to introduce a      to update figure 10: to introduce Yes
       cal          1.1           mechanism for recipient to          2 additional bit(s) in the Frame
                                  recognize the progress and end      control of the MAC header to
                                  of fragmented block                 indicate to the receiver the
                                                                      fragment conditions.




S6-467 Techni    43 6.3.        5 Table 8: to use the value 6 in      To use the reserved value 6 of      Yes
       cal          7.3           status code field: to indicate to   table 8 to indicate the status:
                                  unconnected node in the             ―rejected hub operating in secure
                                  unsecure communication the          mode”
                                  following status ―rejected hub
                                  operating in secure mode” in
                                  Connection Assignment frame.
S6-468 Techni    58    6.7      1 to introduce New set of optional    to introduce New set of optional    Yes
       cal                        Assignement IEs (for                Assignement IEs (for
                                  uplink/Downlink and or Bilink)      uplink/Downlink and or Bilink)
                                  for relaying purposes to
                                  distiunguish between the
                                  assignement of relaying node
                                  and the relayed node in the
                                  connection assignement of the
                                  relaying node
S6-469 Techni 46-     6.3.   20 There is no definition for Piconet                                        Yes
       cal    47      11.3   of   response. Two sugestions for its
                      &      pag introduction:a) to use value 5 of
                      6.3.   e 46 table 9 for Piconet Response
                      11.4   &    OR b) to use value 11 of table
                      .3     18 11. If we chose to select case a)
                             of   I suggest to remove Piconet
                             pag enquiri from table 11 to table 9
                             e 47 and assign it a value of 4


S6-470 Techni    53 6.4.        2 Hub address is missing; BAN                                             Yes
       cal          8             descriptor referred in previous
                                  comment not explicitly stated
S6-471 Techni    42 6.3. Fig Inconsistency in fields from NID    Add a separate diagram for the No
       cal          7.0 25 onwards in fig25 and in fig 49        connection related information
                             for Multinode Connection            elements for use in single Node
                             Assignment                          and multinode Connection IE's in
                                                                 fig 25 and 49 in order to ensure
                                                                 their fields remain consistent

S6-472 Techni    46 6.3. Tabl Naming of commands and their Suggest changing Battery Level No
       cal          11.3 e 9 bit pattern could help distinguish Inquiry to Battery Level Request
                              request/response                  and making it equal to 2 and
                                                                Indication to 3 – giving a
                                                                convention of even numbers for
                                                                requests
S6-473 Techni    58 6.7 Tabl Why start assignments at 11 – Start Assignment IE's at 16 or 32
       cal               e 15 why not 16 or 32 so can use a
                              bitmask to determine if
                              assignment or request and to
                              allow for expansion of requests?

S6-474 Editori   22 6.2. Tabl Role of bits would be clearer if                                    No
       al           1.1. e 3 bit pattern shown as b3 b2 b1
                    8         b0 for frame subtype (although
                              note this is not the convention
                              used elsewhere)
S6-475 Techni    59 6x        A new subclause is needed to       Add a new subclause, 6.7.1.3      Yes
       cal                    define the new field.              Beacon Shifting Sequence, with
                                                                 the following text for the
                                                                 definition: The Beacon Shifting
                                                                 Sequence field is present only if
                                                                 beacon shifting is enabled.
                                                                 When present, it is as defined in
                                                                 6.3.1.10.
S6-476 Techni    59 6x         A new subclause is needed to      Add a new subclause, 6.7.1.3      Yes
       cal                     define the new field.             Beacon Shifting Sequence, with
                                                                 the following text for the
                                                                 definition: The Beacon Shifting
                                                                 Sequence field is present only if
                                                                 beacon shifting is enabled.
                                                                 When present, it is as defined in
                                                                 6.3.1.10.
S6-477 Techni    59 6x         A new subclause is needed to      Add a new subclause, 6.7.1.3      Yes
       cal                     define the new field.             Beacon Shifting Sequence, with
                                                                 the following text for the
                                                                 definition: The Beacon Shifting
                                                                 Sequence field is present only if
                                                                 beacon shifting is enabled.
                                                                 When present, it is as defined in
                                                                 6.3.1.10.
S6-478 Editori whe 6x    Type-I and Type II polled          Give a name to type I and type II
       al      re        allocation naming may not be       polled allocation
               appli     acceptable
               cabl
               e in
               the
               draft
               (pag
               e9
               etc )



S6-479 Editori   28 6x   Figure 14: RAP1 start should be
       al                under solid line



S6-480 Techni      6x    Why two RAPs? RAP 1 and
       cal               RAP2 can be merged to one
                         RAP




S6-481 Techni      6x    There are so many channel          Suggestion: Provide an annex to YES
       cal               access proposed (poll access,      describe the objective and
                         improvised access, contention      operation of each channel
                         access, TDMA access). It is not    access.
                         clear whcih channel access
                         should be used in what
                         scenario. So, the guidandce to
                         the user should be provided

S6-482 Editori     6x    delayed poll description is        The operation or protocol related YES
       al                missing                            to delayed poll should be added
                                                            with more detail.


S6-483 Editori     6x    Different structure such as        Describe the operation of poll      YES
       al                variable Poll Period and fixed     channel access with respect to
                         Poll Period according to traffic   different type of traffic
                         type such as delayed sensitive
                         traffic and power constraint
                         traffic should be described.
S6-484 Techni   30 6x   15 A table complementary to Table Insert Table                           Yes
       cal                 3 is needed to present the
                           different frame types and the
                           corresponding security services
                           (No security, authentication
                           only, encryption only,
                           authentication and encryption)
                           that can be applied to each
                           frame.

S6-485 Techni   64 6x   24 Currently, there is only a bit     More details are to be filled in for Yes
       cal                 which is linked with low power     the low power radio bit.
                           wake up radio is in Figure 37 of   Otherwise wakeup radios will not
                           MAC proposal (PHY Capability       be compatible; wakeup radio will
                           format).                           not be able to wakeup the node.




S6-486 Editori whe 6x      B2 naming may not be               Suggest a name for B2              YES
       al      re          acceptable.                        message.
               appli
               cabl
               e in
               the
               draft
               (6.4.
               8,
               6.2.
               1.1.
               10,
               etc)
S6-487 Techni    20   6.2 Figu (TR) Clause 6.2, p. 20, Fig. 8:           Suggested remedy: elide the         Yes
       cal                re 8 when authenticity is provided,            FCS field if data authenticity is
                               there is no added value in                already provided.
                               having an FCS field as well.
                                Suggested remedy: elide the
                                FCS field if data authenticity
                                is already provided.

S6-488 Editori   52 6.4. 22     "It is locally broadcast by a    locally broadcast -> broadcast
       al           8           hub... " --> B2 message is for
                                exchaning frame between other
                                piconet coordinators. Local
                                broadcast is only for broadcast
                                to all nodes in a BAN (Table 16)
                                                                                                             Yes
S6-489 Editori   24 6.2. 37     "In B2 frames locally broadcast          locally broadcast -> broadcast
       al           1.1.        by a hub... " --> B2 message is
                    11          for exchaning frame between
                                other piconet coordinators.
                                Local broadcast is only for
                                broadcast to all nodes in a BAN
                                (Table 16)                                                                   Yes
S6-490 Techni    19   6.1     2 General Comment: The MAC is              Simplify the MAC by removing        No
       cal                      too complex. It contains too             redundant and unnecessary
                                many types of access modes               capabilities. Note: Individual
                                and access phases which are              comments & proposals are
                                redundant and add                        provided for specific areas of
                                unnecessarily to the complexity          concern.
                                of the MAC. Each access type
                                requires additional definition for
                                various details of behavior that
                                are similar, but slightly different
                                from, the other access modes.
                                Each additional access mode
                                includes things such as IE's,
                                functionality of over-loaded bits
                                in the Frame Header,
                                restrictions on use, and impact
                                to the superframe structure, just
                                to mention a few. In addition to
                                adding to the complexity, by
                                stating that various access
                                modes are optional means that
                                inter-operability will be difficult to
                                achieve between the various
                                manufacturers.
S6-491 Editori   21 6.2.    4 Even though bits are               Change Table 1 to display the bit No
       al           1.1.      transmitted LSB first, when        field as b2 b1 with the more
                    2         multiple bit fields are displayed significant bit on the left.
                              in a Table, they should be
                              displayed with the MSB bit on
                              the left. This is the conventional
                              display order for multiple digit
                              number, whether binary, hex, or
                              decimal. Otherwise, it causes
                              great confusion. Example:
                              Binary Value b'10001010 =
                              0x8A = 138 decimal
                              b"10001010 is not equal to 0x51
                              or to 81 decimal.


S6-492 Editori   21 6.2.    9 In general, it is not clear which   Add a table that defines Security No
       al           1.1.      frame types and frame               options and requirements for
                    3         transactions need to be, or can     different frame types.
                              be, secure. This needs to be
                              defined for each frame type. Is
                              there any security for ACK and
                              Poll type frames?




S6-493 Editori   21 6.2.   11 Even though bits are               Change Table 2 to display the bit No
       al           1.1.      transmitted LSB first, when        field as b4 b3 with the more
                    3         multiple bit fields are displayed significant bit on the left.
                              in a Table, they should be
                              displayed with the MSB bit on
                              the left. This is the conventional
                              display order for multiple digit
                              number, whether binary, hex, or
                              decimal. Otherwise, it causes
                              great confusion. Example:
                              Binary Value b'10001010 =
                              0x8A = 138 decimal
                              b"10001010 is not equal to 0x51
                              or to 81 decimal.
S6-494 Techni    21 6.2.   22 The use of the Relay bit is not      The Relay bit can be used to      Yes
       cal          1.1.      clearly defined. It is set in the    indicate that an encapsulated
                    5         Header the encapsulated Frame        Frame is contained within the
                              as well as in the Header of the      current transacted frame. So,
                              "encapsulating" frame. When          the definition of this bit should
                              the "Relayed" node sends a           be:
                              Frame to the "Relaying" node,        The Relay field is set to 1 in
                              does the "Relayed" node set the      frames sent to or from a
                              Relay bit? This is a non-            relaying node in a two-hop
                              encapsulated Frame, destined         extended star network. It shall
                              for the Hub. When the                only be set in frames which
                              "Relaying" node receives this        contain an encapsulated frame
                              frame and encapsulates it for        which is being relayed. It shall
                              transmission to the Hub, does it     not be set in the header of the
                              set the Relay bit in the outer       encapsulated frame, but only
                              Header? When the Hub                 in the outer header of a frame
                              transmits an encapsulated
                                                                   that contains an encapsulated
                              frame to a "Relayed" node, does
                                                                   relayed frame. It is reserved in
                              it set the Relay bit in the
                                                                   all other frames.
                              encapsulated Header? Does it
                              set the Relay bit in the Outer
                              Header? When the "Relaying"
                              node de-encapsulated the
                              Frame received from the Hub
                              and destined for the "Relayed"
                              node, does it set the relay bit in
                              the Header?


S6-495 Editori   22 6.2.    6 It is not clear that the First       In unicast management and data No
       al           1.1.      Frame / On-Time bit is set on        type frames sent by a hub to a
                    6         the first frame on all allocation    node, the First Frame / On-Time
                              intervals, when a node receives      bit shall be set to 1 on the first
                              more than one allocation per         frame in all scheduled allocation
                              superframe. This needs               intervals when the frame starts
                              clarification.                       at the beginning of the allocation
                                                                   interval, even if the allocation
                                                                   interval is not the first allocation
                                                                   interval for a particular node.
                                                                   This is also true for improvised
                                                                   (dynamically scheduled) non-
                                                                   reoccurring scheduled accesses.
                                                                   It shall be set to 0 in all other
                                                                   frames within the current
                                                                   allocation interval.
S6-496 Editori   22 6.2.   15 Even though bits are                  Change Table 3 to display the      No
       al           1.1.      transmitted LSB first, when           Frame Type bit field as b5 b4
                    8         multiple bit fields are displayed     with the more significant bit on
                              in a Table, they should be            the left. Also, change the Sub-
                              displayed with the MSB bit on         Frame Type field to b3 b2 b1 b0,
                              the left. This is the conventional    with the more significant bit on
                              display order for multiple digit      the left.
                              numbers, whether binary, hex,         Change all Tables in this
                              or decimal. Otherwise, it             document to display multiple digit
                              causes great confusion.               fields in the correct
                              Example:                              representation with MSB on the
                              Binary Value b'10001010 =             left.
                              0x8A = 138 decimal
                              b"10001010 is not equal to 0x51
                              or to 81 decimal.
                              The terms "0110-1110" in line 7
                              of table 3 is ambiguous and
                              incorrect. In binary notation this
                              defines a range from 6 to 14
                              decimal, which is not correct.
                              The correct range is 6 to 7.


S6-497 Editori   23 6.2.    5 Does the behavior of the More         Confirm that there is no          No
       al           1.1.      bit have the same meaning in          difference in behavior for the
                    9         uplink data frames in CSMA,           different access modes, of
                              Uplink Allocation Intervals, Bilink   define the differences.
                              allocation Intervals,
                              Unscheduled Polling intervals,
                              Delayed Polling intervals,
                              Improvised Polling Intervals? Is
                              the response by the Hub the
                              same in all of these cases.
                              Does the behavior of the More
                              bit have the same meaning in
                              acknowledgement frames from
                              the Node to the Hub in
                              response to downlink/posted
                              frames in Downlink Allocation
                              Intervals, Bilink allocation
                              Intervals, Unscheduled Polling
                              intervals, Delayed Polling
                              intervals, Improvised Polling
                              Intervals, CSMA allocation? Is
                              the response by the Hub the
                              same in all of these cases.
S6-498 Editori   23 6.2.   5 The behavior relative to the         For CSMA access, the Hub           No
       al           1.1.     More bit during CSMA needs           should respond to the More bit
                    9        clarification. If the More bit is    being set the same as it does in
                             set in a CSMA Uplink access,         other modes. When the I-Ack
                             how does the Hub respond             policy is set to I-Ack or B-Ack on
                             when the I-Ack policy is set to I-   an uplink data or management
                             Ack or B-Ack? Does the Hub           frame, the Hub may respond
                             respond with an Ack or an            with either an Ack, or an
                             Ack+Poll? If with an Ack, can        Ack+Poll. If an Ack only, the
                             the Node send the next frame         Node may not send another
                             pSIFS after the end of the           Frame during the current access
                             Acknowledge frame transaction        until a Poll is received. If an
                             without another LBT? If with         Ack+Poll, or a Poll is received,
                             only an Ack, does this indicate      the Node may send another
                             that the Node should not send        Frame pSIFS after the end of the
                             another frame? If with an            current frame transaction without
                             Ack+Poll, can the Node send          another LBT. If the I-Ack Policy
                             the next frame pSIFS after the       is set to N-Ack or L-Ack, the
                             end of the Acknowledge frame         Node may send another frame
                             transaction without another          pSIFS after the end of the
                             LBT? If the I-Ack field is set to    current frame transaction without
                             N-Ack or L-Ack, can the Node         another LBT.
                             send the next frame pSIFS after
                             the end of the current frame
                             transaction without another
                             LBT?
S6-499 Editori   23 6.2.   5 Sect a) 2) Does this mean that    The Node may set the More bit No
       al           1.1.     for scheduled downlink or Post    in an Acknowledgement frame.
                    9        from the Hub, that if the node    Hub should respond to the More
                             has uplink data, it can set the   bit being set the same as it does
                             "More Data" bit during the ACK    in other modes. When the I-Ack
                             ―frame‖? If so, what are the      policy is set to I-Ack or B-Ack on
                             options from the hub? Does it     an uplink data or management
                             poll for immediate uplink         frame, the Hub may respond
                             transaction? Does it perform      with either an Ack, or an
                             improvised scheduling? May a      Ack+Poll. If the Hub sends an
                             node send uplink data duri9ng a   Ack only, the Node may not send
                             downlink allocation period?       another Frame during the current
                             Does this mean that the Node      access until a Poll is received. If
                             must support Polling to send an   an Ack+Poll, or a Poll is received
                             uplink frame during a downlink    by the Node, the Node may send
                             allocation period?                another Frame pSIFS after the
                                                               end of the current frame
                                                               transaction, or if a delayed poll,
                                                               receive the poll in the improvised
                                                               scheduled slot. If the I-Ack
                                                               Policy is set to N-Ack or L-Ack,
                                                               the Node may send another
                                                               frame pSIFS after the end of the
                                                               current frame transaction,
                                                               providing adequate time remains
                                                               in the allocation interval.
S6-500 Editori   23 6.2.   9 There is no restriction on the        Change the meaning of the More No
       al           1.1.     ACK policy if the More bit is set     bit for management or data
                    9        on a management or data frame         frames from the Hub to Node as
                             from the Hub to the node. What        follows:
                             would be the response if an           It is set to 1 if the hub is to
                             ACK policy is set to I-Ack or B-      send a post to the node pSIFS
                             Ack? In this case, the Node           after the end of the current
                             should reply with either the I-       frame transaction when the
                             Ack or B-Ack, causing a               Ack policy is N-Ack or L-Ack,
                             collision. Stating that this bit      or to send a post to the node
                             being set indicates a Post            pSIFS after the end of the
                             pSIFS after the end of the            Acknowledge frame
                             current frame transaction,            transaction when the Ack
                             negates the ability to use this bit   policy is I-Ack or B-Ack.
                             to allow the Node to go to sleep
                             after the last transmission, in
                             the case where the allocation
                             interval has not completed. A
                             better use of this bit is to
                             combine it with the Ack policy.
                             If the More Bit is set, and an I-
                             Ack or B-Ack is requested, then
                             the Node will know that it must
                             continue listening after it
                             transmits the Ack. If the More
                             bit is 0, then the Node can go to
                             sleep after sending the Ack.


S6-501 Editori   23 6.2.   9 Sect b) 2) What is the setting        In unicast management and data No
       al           1.1.     when the Hub will be sending a        type frames sent by a hub to a
                    9        Poll immediately following a          node, the More bit is set to one if
                             Post? Wouldn't it set the More        the hub is to send a post or a
                             bit to a 1 in the Posted Frame to     poll to the node pMIFS after the
                             indicated that the Node will          end of the current frame when
                             immediately receive another           the ACK policy is N-Ack or L-
                             Frame to prevent the node from        Ack, or pSIFS after the I-Ack or
                             going to sleep.                       B-Ack frame from the Node to
                                                                   the Hub if the Ack Policy is set to
                                                                   I-Ack or B-Ack.
S6-502 Editori   23 6.2.   12 Sect c) 1) If this is a scheduled   In I-Ack and B-Ack frames sent No
       al           1.1.      uplink access, what does the        by a hub to a node, the More bit
                    9         node do in the case where its       is set to zero if the hub is not to
                              allocation interval has not         send a post or a poll to the node
                              ended? Does this mean that          after the end of the current. In
                              the Hub will switch to receive      this case, the Node may not
                              mode waiting for a frame from       send another frame, and current
                              the node? In scheduled uplink,      access allocation is terminated,
                              what allows the node to send        even if the allocation period has
                              another frame after receiving an    not expired. This is true for all
                              I-Ack or B-Ack from the Hub, if     access modes.
                              there is sufficient time for
                              another frame in the current
                              uplink allocation? Is setting the
                              More bit to zero in the Ack form
                              the Hub adequate, or does the
                              Node need a Poll before
                              sending another frame. If the
                              More bit is set to zero in the
                              Ack, does this mean that the
                              node may not send another
                              frame and may go to sleep?
                              Has scheduled uplink behavior
                              been defined in this document?



S6-503 Editori   42 6.3.    1 After the Connection Request     Need explanation for this case.    No
       al           7         Frame, is the Connection
                              Assignment frame transmitted
                              by the Hub expected pSIFS
                              later? Or, does the Hub
                              perform an I-Ack per Ack policy
                              and then "Post" the Connection
                              Assignment Frame pMIFS after
                              the Ack Frame? What happens
                              when the Hub does not have
                              enough time to process the
                              request in time to send it
                              immediately after the Request
                              or Ack? In that case, how is the
                              Assignment Frame sent, since
                              this occurs during a contention
                              period and the Hub shall not
                              initiate a Post?
S6-504 Techni    44 6.3.   21 It is stated that the Multinode    Add a period, immediately after Yes
       cal          8         Connection Assignment is made      the Beacon, when nodes are
                              with a broadcast (multicast)       required to listen for
                              frame. When do nodes listen        broadcast/multicast frames when
                              for broadcast or multicast         beacon mode is enabled.
                              frames? This could be useful
                              for quickly changing the
                              superframe structure, but there
                              needs to be a well define time
                              when nodes are listening.

S6-505 Editori   44 6.3.   21 It is not clear how Multimode   Clarify the difference.           No
       al           8         Connection Assignment is
                              different from Group Connection
                              Assignment.

S6-506 Techni    50 6.4.    8 At what point is it determined     The oldest expected frame shall Yes
       cal          2.1       that this oldest frame needs to    not be older than the 15 frames
                              be discarded. Who has the          received. If more than 15 newer
                              responsibility and how is this     frames are received, then the
                              decision made, and what criteria   oldest frame expected shall be
                              is used to make it. Is the         changed such that no more the
                              discard decision the               15 newer frames are present at
                              responsibility of the sender or    the receiver. Once an oldest
                              the receiver? Once a discard       frame expected is changed to a
                              decision is made, how is that      high number, the sending node
                              decision communicated to the       shall discard any frames older
                              other side? This determines the    than the oldest expected. The
                              buffering requirements on both     sender may not save the oldest
                              the sender and receiver sides.     frame expected, depending on
                                                                 its buffering capabilities. It may
                                                                 chose to ignore the oldest frame
                                                                 expected, and instead, send the
                                                                 oldest frame in its buffer which
                                                                 has not been acknowledged.


S6-507 Techni    50 6.4.   19 What is the maximum number         The maximum number of frames Yes
       cal          2.3       of frames that can be              that can be acknowledged with a
                              acknowledged with a B-Ack.         B-Ack is 16, so the maximum
                              There needs to be a reasonable     value of N is 2.
                              limit, since newer frames from
                              the oldest expected frame
                              cannot be forwarded, and
                              therefore must be buffered until
                              it is decided to discard the
                              "oldest" expected frame.
S6-508 Techni    51 6.4.   19 Are both T-Poll replace Poll          Justify why both Delayed Bilink    Yes
       cal          6         required? Should T-Poll replace       and T-Poll are required. If
                              Poll or vice versa, so that only      neither is required, eliminate
                              one type is used? Why are both        both. If T-Poll is not required,
                              needed? T-Poll was added to           eliminate it.
                              support Delayed Bilink Access.
                              Can both Delayed Bilink and T-
                              Poll be eliminated.

S6-509 Editori   51 6.4.   19 If T-Poll is required, are "I-Ack &   If T-Poll is required, then:         No
       al           6         T-Poll" and "B-Ack & T-Poll"          A T-Poll is used to mark the
                              also required? Are these              beginning of an allocation
                              combinations also needed for          interval to synchronize the clocks
                              consistency? Is T-Poll required       of those nodes which do not, or
                              only for the first frame of an        did not, receive the beacon. A T-
                              allocation interval, and after that   Poll is only sent at the beginning
                              Poll is used?                         of a Scheduled Bilink or Delayed
                                                                    Bilink allocation. All other Polling
                                                                    in that same allocation interval
                                                                    shall use a Poll or I-Ack+Poll or
                                                                    B-Ack+Poll.

S6-510 Techni    52 6.4.    2 This statement does not               There is no a simple solution to Yes
       cal          6.3       adequately specify the timing         this requirement. It will involve
                              requirement. There needs to be        interaction between the PHY and
                              more accuracy defined by              the MAC, most likely with some
                              referencing the offset to a           timing information supplied to the
                              specific symbol/bit location in       MAC by the PHY on the receiver
                              the frame. How is the beginning       side. There also needed to be a
                              transmission defined relative to      tight link between the MAC and
                              the beginning of the slot?            the PHY on the sender side so
                                                                    that the encoded value matches
                                                                    the delay from the start of the
                                                                    current slot. An accuracy must
                                                                    be defined such that guard times
                                                                    are not violated.
S6-511 Editori   54 6.6.   20 What is the indication that a      Clarify                            No
       al           1         node supports unscheduled
                              polling?




S6-512 Editori   55 6.6.   11 Must the Type-I Polling Access     Clarify                            No
       al           1.3       bit be set in the MAC capability
                              field for a Bilink Request IE to
                              be included in the Connection
                              Request Frame?

S6-513 Techni    55 6.6.   14 Having both Type-I and Type-II     Either:                             Yes
       cal          1.4       Access phases, in addition to      1) Show that Type-II Type
                              Unscheduled Polling and            Access cannot be adequately
                              Contention Access, is              covered with Scheduled Bilink,
                              redundant and unnecessary.         Improvised BiLink, Unscheduled
                              Type-I access phase handles        Polling, and Contention Access
                              variable data requirements with    OR:
                              Improvised Polling.                2) Remove Type-II Access
                              Unscheduled Polling and            Phase. Retain the ability to
                              Contention Access also handles     specify either slot based
                              variable data requirements.        allocation or frame based
                              Unscheduled Polling and            allocation in Polls and T-Polls for
                              Contention Access can provide      Unscheduled Polling Access and
                              both time based and frame          Contention Access
                              based allocation.




S6-514 Editori   55 6.6.   14 Must the Type-II Polling Access Clarify                               No
       al           1.4       bit be set in the MAC capability
                              field for a Delayed Bilink
                              Request IE to be included in the
                              Connection Request Frame?
S6-515 Techni    55 6.6.   17 Why is the Schedule Access         Justify why this bit is required or Yes
       cal          1.5       Capability bit required. Is it not removed it.
                              sufficient for a node to send a
                              Schedule type allocation
                              request IE to indicate that it
                              supports Scheduled access? Is
                              there any time that a node
                              would receive scheduled access
                              without requesting it in an IE?

S6-516 Techni    55 6.6.   21 Why is the Delayed-Polling         Justify why this bit is required or Yes
       cal          1.6       Access Capability bit required. removed it.
                              Is it not sufficient for a node to
                              send a Delayed Bilink allocation
                              request IE to indicate that it
                              supports Delayed-Polling
                              access? Is there any time that
                              a node would receive Delayed-
                              Polling access without
                              requesting it in an IE? Why is
                              this defined as Delayed-Polling
                              as opposed to Delayed-Bilink?

S6-517 Editori   55 6.6.   21 Why is this defined as Delayed- Clarify                                No
       al           1.6       Polling as opposed to Delayed-
                              Bilink? What is the difference?
                              Hasn't Delayed-Polling been
                              replaced with Delayed-Bilink?

S6-518 Editori   56 6.6.    4 A search on the term "Group"        For all cases of the term           No
       al           1.9       shows that this term is used in     "Group", clarify the context with a
                              multiple contexts, and is not       preceding word:
                              clarified in the different cases.   Multicast Group (for a group that
                              In Sect 6.6.1.9, it refers to a     responds to a multicast
                              group of nodes, that receive        address), Pico-Net Group (for
                              Group assignment, and G-Ack         use with GTK), G-Ack Group (for
                              response. Page 17, Sect 5.5         a group that uses group
                              and Page 38, Sect 6.3.5 refers      assignment and responds to a G-
                              to Group Temporal Key, in           Ack), and similar for all other
                              which case "Group" has a            uses of the word "Group"
                              different meaning. The phase
                              "group of nodes" is also used in
                              several places, with a different
                              meanings, sometimes, but not
                              always as a multicast group.
                              The term "Group" as used in
                              Sect 6.6.1.9 is also not clearly
                              distinguished between
                              "Multinode Connection" in
                              6.6.1.10.
S6-519 Editori   56 6.6.   4 It is not clear how "Group"         Give an example of how a Group No
       al           1.9      connection requests and             Assignment Request and
                             assignments are made. It is         Connection Assignment are
                             also not clear what limitations     made and how the IE's are
                             are on connection assignments       formatted.
                             for G-Ack Groups. Is there a
                             limit of one frame per node per
                             superframe for G-Ack Group
                             Nodes?

S6-520 Editori   57 6.6.   1 What is the behavior of a Low  Clarify                              No
       al           2.1      Power Wakeup Radio relative to
                             a non-Low Power Wakeup
                             Radio?

S6-521 Editori   58 6.7.   3 When is it necessary and/or         State the requirement and/or    No
       al           1        allowed to include the Slotted      recommendation.
                             Superframe IE in a connection
                             assignment? Under what
                             conditions is it recommended, if
                             not required?
S6-522 Techni    59 6.7.   4 Requirements needing Uplink         Either:                          Yes
       cal          2        Access Mode can be satisfied        1) Show that BiLink cannot
                             with the BiLink Access Mode.        adequately satisfy the needs for
                             In BiLink Mode, after a Poll, the   transacting Scheduled Uplink
                             Uplink Data Frame may be sent       Frames, and that it is worth the
                             by the Node. If a T-Poll is used,   additional complexity
                             the Node may skip listening to      Or:
                             the Beacon, and only wake-up        2) Remove Uplink Access Mode,
                             during its scheduled allocation.    Uplink Request IE, and Uplink
                             This saves power for the node.      Assignment IE.
S6-523 Editori   60 6.7.    4 The term "Gap" is not clearly      Define "Gap" as follows: When No
       al           2.4       defined.                           the Wakeup Period field bit is
                                                                 '0', Gap is equal to the number
                                                                 of slots between the last slot
                                                                 of the allocation period and
                                                                 first slot the next allocation
                                                                 period for the same node in
                                                                 the same superframe, such
                                                                 that if the next allocation
                                                                 period starts immediately after
                                                                 the current allocation period,
                                                                 the Gap = 0. When the
                                                                 Wakeup Period field bit is '1',
                                                                 Gap is equal to the number of
                                                                 superframes between the
                                                                 current allocation period and
                                                                 the next allocation period for
                                                                 the same node, such that if
                                                                 allocations for the node occur
                                                                 in every superframe then the
                                                                 Gap = 0.

S6-524 Techni    60 6.7.   27 Downlink Access Mode is            Either:                         Yes
       cal          3         redundant to BiLink Access         1) Justify why Downlink access
                              Mode. In BiLink Access, the        mode is required and cannot be
                              Hub may perform a Post at the      satisfied with other modes, and
                              beginning of the Allocation        that it is worth the additional
                              Interval, which is the same as a   complexity.
                              Downlink. Downlink Access          Or:
                              Mode provides no advantage or      2) Remove Downlink Access
                              capability that is not already     Mode, Downlink Request IE, and
                              present in BiLink Mode.            Downlink Assignment IE.
                                                                                        TOTAL:
                                                                                          LEFT:
                                                                                         DONE:
                                                                                        DEFER
                Resolution                    CID

E                                                             0




E                                                             0




E                                                             0


Same as S6-172                                                0




E -- -- Make similar changes in all similar                   0
tables.

Reject.                                             Same as   0
                                                    S6-174
Wakeup frame provides unique
functionality for non-beacon non-
superframe mode of operation.
E                                        0




E                                        0


Reject.                                  0

New text of DCN 0755-00 addresses this
comment.
Rejected                                 0
Reject.                                  0

New text of DCN 0755-00 addresses this
comment.
E    0




E.   0




E    0
E                                                  0


E                                                  0 Same as S6-015


E. Accept                                          0

Changes implemented DCN 0678-00.



E                                                  0




Same as S6-187                           Same as   0
                                         S6-187

Same as S6-188                           Same as   0
                                         S6-188

Same as S6-189                                     0




E                                        Same as   0
                                         S6-190

Reject.                                            0

New text of DCN 0755-00 addresses this
comment.




TG discussed and agreed to accept in     Same as   0
principle.                               S6-192

New text of DCN 0755-00 addresses this
comment.
Same as S6-314   0




Same as S6-194   0




Same as S6-195   0
Same as S6-196   Same as   0
                 S6-196




Same as S6-197   Same as   0
                 S6-197



Same as S6-243   Same as   0
                 S6-243

Same as S6-199             0


Same as S6-200             0




Same as S6-201   Same as   0
                 S6-201
Same as S6-202             0




Same as S6-203             0


Same as S6-204   Same as   0
                 S6-204

Same as S6-205   Same as   0
                 S6-205

Same as S6-206             0
Same as S6-207             0




Same as S6-208             0




Same as S6-209             0



Same as S6-210   Same as   0
                 S6-210


Same as S6-211   Same as   0 Same as S6-042
                 S6-211


Same as S6-212   Same as   0
                 S6-212




Same as S6-213             0




Same as S6-103   Same as   0
                 S6-103




E                Same as   0
                 S6-101


E                Same as   0
                 S6-102
Rejected. The sentence is correct.               0
"When the hub is to send a post to the
node" is the subject of the sentence.


Same as S6-47                                    0


Same as S6-48                                    0


E -- Make similar changes in all similar         0
tables.


Same as S6-8                                     0


Accepted in principle: (1) In the table's        0
heading, change "sequences" to
"Sequence field encoding". (2) In the left
column, after "index" add "m in" (with "m"
in italic). (3) in the middle column, change
"valeus" to "as function of
Beacon Shifting Sequence Phase n = 0,
1, 2, …, 15
" (with n in italic), and delete all instances
of ", n = 0, 1, ...". except the header entry
italic. (4) In lines 2 and 41, page 24, after
"incremented by one", add ", modulo 256,
".

See updated text/table in DCN 0677-00.


Accepted in principle: See S6-277.               0




Reject. Figure 17 is correct showing             0
greater than or equal to zero as general
case.



Same as S6-187                                   0
Reject. The proposed change includes a               0
typographical error, citing irrelevant
"beacon shifting sequence". See S6-379.

E. Accept.                                           0


E. Accept.                                           0 Same as S6-059


Accept in principle. Change text on line             0
18-19 to "…is set to the modulo-2 sum of
one plus its value used…"

Changes implemented in DCN 0678-00.

See S6-280.                                Same as   0 Same as S6-061
                                           S6-61




See S6-282.                                          0



We should Accept, This is an editorial               0
comment. DCN 0679-00 already
addresses this comment.


We should Accept, This is an editorial               0
comment. DCN 0679-00 already
addresses this comment.


We should Accept, This is an editorial               0
comment. DCN 0679-00 already
addresses this comment.
See S6-385.                                          0


TG discussed and agreed to accept in                 0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in       Same as   0 Same as S6-068
principle.                                 S6-68

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in                0
principle.

New text of DCN 0755-00 addresses this
comment.
Same as S6-72                                       0


Accept. Change to "duty cycle" in Table             0
12 heading.

TG discussed and agreed to accept in                0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in                0
principle.

New text of DCN 0755-00 addresses this
comment.
Same as S6-293                                      0


TG discussed and agreed to accept in      Same as   0
principle.                                S6-74

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in                0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in      Same as   0
principle.                                S6-74

New text of DCN 0755-00 addresses this
comment.
Accept. Same as S6-463                              0


TG discussed and agreed to accept in                0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in                0
principle.

New text of DCN 0755-00 addresses this
comment.
E.                                                 0



TG discussed and agreed to accept in               0
principle.

New text of DCN 0755-00 addresses this
comment.
E.                                                 0


MAC subgroup discussed and agreed to               0
proposed resolution in DCN 0677-00.

TG discussed and agreed to accept.                 0

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept.                 0

New text of DCN 0755-00 addresses this
comment.

See S6-299                                         0


TG discussed and agreed to accept.                 0

New text of DCN 0755-00 addresses this
comment in subclause 6.4.8
Same as S6-89                            Same as   0 Same as S6-089
                                         S6-89

TG discussed and agreed to accept.                 0

New text of DCN 0755-00 addresses this
comment in subclause 6.4.8
TG discussed and agreed to accept in               0
principle.

New text of DCN 0755-00 addresses this
comment in subclause 6.4.8
Accept. Editorial.                                 0


Accept. E.                                         0


Accept. Editorial                                  0
MAC subgroup discussed and agreed to                  0
proposed resolution in DCN 0677-00.




Accept. E.                                            0


Accept. E.                                            0


Same as S6-100.                                       0


E.                                                    0


Same as S6-47                                         0


Same as S6-48                                         0


See S6-201.                                           0




Same as S6-103                              Same as   0 Same as S6-103
                                            S6-103




Technical. Rejected: Those two bits are               0
not supposed to be covered in this table.



Rejected. "if" is more accurate.                      0
E -- Rejected                                   0




Same as S6-107                                  0 Same as S6-107




E. Replace subsequent instances of the          0
term in this subclause with the acronym.
Also add the acronym to the Acronym
clause.

E. Replace subsequent instances of the          0
term in this subclause with the acronym.
Also add the acronym to the Acronym
clause.

Rejected. The general convention is             0
stated at the Conventions subclause.



Accepted in principle. Al P. to provide the     0
diagram.



Accept in principle. Edit lines 4 and 5 to      0
read "... to Table 5 to indicate the security
association protocol."

Changes implemented in DCN 0678-00.
Reject. The proposed change includes a        0
typographical error, citing "x" rather than
"y". See S6-379.




MAC subgroup discussed and agreed to          0
proposed resoluation in DCN 0677-00.



Reject.                                       0

Text is accurate as written.


Reject. This line in the text does not        0
include "=0".



TG discussed and agreed to accept in          0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept.            0

New text of DCN 0755-00 addresses this
comment.
E.                                                        0




TG discussed and agreed to accept in                      0
principle.

New text of DCN 0755-00 addresses this
comment in subclause 6.4.8
Check                                                     0



Same as S6-103                                  Same as   0
                                                S6-103




Same as S6-490                                            0




Same as S6-491                                            0




Same as S6-493                                            0




Rejected. In the literature it is often still             0
referred to as CCITT in connection with
this generator polynomial.

E.                                                        0
Accept in principle.                          0

Need to include data rates for UWB -
tables 54, 55 and 63 (7 optional bits) - as
well as HBC - table 72 of DCN 0741-02 (3
optional bits)
Accept.                                       0



Same as S6-47                                 0


Same as S6-48                                 0


Same as S6-1                                  0




Same as S6-2                                  0


Same as S6-3                                  0


E -- Also make internal horizontal lines      0
thinner.




Same as S6-5                                  0
Same as S6-6    0




Same as S6-7    0


Same as S6-8    0


Same as S6-9    0



Same as S6-10   0
Same as S6-11   0
Same as S6-12   Same as   0
                S6-12




Same as S6-13   Same as   0
                S6-13




Same as S6-14   Same as   0
                S6-14
Same as S6-15                          Same as   0
                                       S6-15

Same as S6-16                          Same as   0 Same as S6-183
                                       S6-16

Same as S6-17                                    0




Same as S6-18                          Same as   0
                                       S6-18



E.                                               0
Changes implemented in DCN 0678-00.

E.                                               0


MAC subgroup discussed and agreed to             0
proposed resolution in DCN 0677-00.




Same as s6-190                                   0


Same as S6-23.                                   0




Same as S6-24                                    0
Same as S6-314                           0




TG discussed and agreed to accept in     0
principle.

New text of DCN 0755-00 addresses this
comment.




TG discussed and agreed to accept in     0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in     0
principle.

New text of DCN 0755-00 addresses this
comment.




TG discussed and agreed to accept in     0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in     0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in     0
principle.

New text of DCN 0755-00 addresses this
comment.
Accept. E.                               0
Accept in principle.                              0

Definition of Relay Link Quality to be
changed:

(1) Insert a "1" if > 50% of
communications with hub in this
superframe was successful (e.g. CRC
passed, ACKs received, frames sent);

(2) At the end of a superframe period shift
bits to the right (zero is shifted in left most
bit), (last, right-most bit is discarded);

(3) All bits set to zero if relay goes to
sleep.

newest (current superframe)
 [ | | | | | | | ]
     oldest (8 superframes ago).
TG discussed and agreed to accept in        0
principle.

New text of DCN 0755-00 addresses this
comment.




E.                                          0


E,                                          0


E.                                          0


Accept in principle.                        0

Text of DCN 0677-02 addresses this
comment.
Also add paragraph to subclause 7 stating
when this slotted superframe IE is
necessary.
Discussion - accept.                                  0

Also need to include Channel Hopping
and Inactive Superframe fields as both
are necessary to ensure the node can find
the subsequent beacon messages. This
is also for the benefit of a relayed node
that cannot hear the beacons.
E.                                                    0




E.                                                    0



E.                                                    0



E.                                                    0 Same as S6-210



Accept.                                               0

This has been addressed in text of 0677-
00.

See S6-471.
Accept. E.                                            0




Same as S6-1                                          0




Same as S6-2                                Same as   0
                                            S6-170
Same as S6-3               0


Same as S6-172   Same as   0
                 S6-172




Same as S6-5     Same as   0
                 S6-173

Same as S6-6     Same as   0
                 S6-174




Same as S6-7               0


Same as S6-8     Same as   0
                 S6-176

Same as S6-9               0
Same as S6-10   0




Same as S6-11   0
Same as S6-12   Same as   0
                S6-12




Same as S6-13   Same as   0
                S6-13




Same as S6-14   Same as   0
                S6-14
Same as S6-15    Same as   0
                 S6-15

Same as S6-16    Same as   0 Same as S6-228
                 S6-184

Same as S6-17              0




Same as S6-18    Same as   0
                 S6-18



Same as S6-187   Same as   0
                 S6-187

Same as S6-188   Same as   0
                 S6-188

Same as S6-189             0




Same as S6-235   Same as   0
                 S6-190

Same as S6-191             0




Same as S6-24    Same as   0
                 S6-192
Same as S6-314   0




Same as S6-194   0




Same as S6-195   0
TG discussed and agreed to accept in     Same as   0
principle.                               S6-196

New text of DCN 0755-00 addresses this
comment.




Same as S6-197                           Same as   0
                                         S6-197



Same as S6-198                           Same as   0
                                         S6-198

Same as S6-199                                     0


Same as S6-200                                     0




Same as S6-201                           Same as   0
                                         S6-201
Same as S6-202             0




Same as S6-203             0


Same as S6-204   Same as   0
                 S6-204

Same as S6-205   Same as   0
                 S6-205

Same as S6-206             0
Same as S6-207             0




Same as S6-208             0




Same as S6-209             0



Same as S6-210   Same as   0
                 S6-210


Same as S6-211   Same as   0 Same as S6-255
                 S6-211


Same as S6-212   Same as   0
                 S6-212




Same as S6-213             0




Same as S6-48              0



E                          0



Same as S6-8               0
Reject. Reference to Camellia-128 can       0
be found on page 3.

Robert Moskowitz offered to provide
additional descriptive text.
Accept. Changes to be made to Figure        0
24 and subclauses.




Rejected. "Piconet" is changed to "BAN".    0
See S6-284. "Piconet" is not a term used
in this spec.

Reject. See resolution of S6-290.           0




TG discussed and agreed to accept in        0
principle.

New text of DCN 0755-00 addresses this
comment.
See S6-485                                  0




Accept.                                     0

However, not enough bits for all optional
data rates defined by UWB and possibly
HBC PHYs. What to do?

Expand the final sentence "Table 14 is
specified based on 9.1" to include
subclauses 10 and 11 define UWB and
HBC PHYs.
Rejected. A technical but not editorial     0
comment. All reserved fields are set to
zero as stated in 6.1.
Same as S6-47                                   0




Same as S6-48                                   0




Same as S6-8                                    0




Accepted in principle: Create two               0
subclauses under 6.3.1.2, one for the
case without beacon shifting, and the
other for the case with beacon shifting.
Jin-Meng to bring the proposed resolution
back to the group for review and
resolution.

See DCN 0677-00 for updated text.
E                                               0




Editorial. Accepted in principle: Delete        0
the middle column from Table 4.
Addressed by S6-54 resolution.



Same as S6-274                                  0




Accepted.                                       0




Editorial. Accepted in principle: Before        0
the period, insert ", as further specified in
7.12.2" (section number needs to be soft
coded).
Accepted                                     0




TG discussed agreed to proposed              0
resolution (accept in principle) of DCN
0676-00.

Changes implemented in DCN 0678-01,
including corrected PTK Control format.


E. Accept.                                   0




MAC subgroup discussed and agreed to         0
proposed resoluation in DCN 0677-00.



E.                                           0




Technical. Accepted in principle. Table      0
10 is now moved into 6.2.1 as a result of
S6-11, so just make a reference to it. The
name is now changed to BAN Priority.


E. Accepted.                                 0




TG discussed and agreed to accept in         0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in       0
principle.

New text of DCN 0755-00 addresses this
comment.




TG discussed and agreed to accept in       0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in       0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in       0
principle.

New text of DCN 0755-00 addresses this
comment.



Reject. Table 12 adds new information in   0
third column.



Accept in principle. Table 13 duplicate    0
with Table 12. Delete Table 13 and
change references to reflect Table 12.


TG discussed and agreed to accept in       0
principle.

New text of DCN 0755-00 addresses this
comment.
TG discussed and agreed to accept in              0
principle.

New text of DCN 0755-00 addresses this
comment.
E.                                                0




Agree in principle. See doc 915-02 for text       0
to replace this subclause




                                              1
TG discussed and agreed to accept.                0

New text of DCN 0755-00 addresses this
comment.

TG discussed and agreed to accept.                0

New text of DCN 0755-00 addresses this
comment.


MAC subgroup discussed and agreed to              0
add a new field (1 octet long, after EAP2
Start field) in Connection Assignment
frame and Node Assignment IE called
"Minimum CAP Length" which, when zero
indicated no fixed minimum length. B2 bit
in beacon header definition does not
change.




TG discussed and agreed to accept.                0

New text of DCN 0755-00 addresses this
comment.
Same as S6-285                                0




Accept.                                       0

Text of DCN 0679-00 addresses this
comment.




Accept in principle.                          0

Add text to indicate that the connection
assignment allocation is used by the
aggregate members of the group where
the specific utilization of this allocation
among the group nodes is beyond the
scope of this document.
E.                                            0




Accepted in principle: In line 24, page       0
107, insert "optional" before
"mechanisms".



See S6-308.                                   0




MAC subgroup discussed and agreed this        0
is addressed by proposed resolution of S6-
501, using More Data bit.
MAC subgroup discussed and agreed to     0
proposed resolution in DCN 0677-00.




TG discussed and agreed to accept.       0

New text of DCN 0755-00 addresses this
comment.



Accepted in principle: Delete "locally   0
broadcast by a hub in its body area
network (BAN)".




TG discussed and agreed to accept in     0
principle.

New text of DCN 0755-00 addresses this
comment.




E.                                       0



See