Proposed resolution for CID 8113: Revised. On page 1969 line 22, replace with as defined in 12.6.16”. “Lifetime” “Lifetime, CID 8115 Location Comment Proposed Change Clause: What is the lifetime of a Add ", as defined in 12.x.y.z" to the end of the referenced line 12.6.1.1.10 Mesh Page: 1970 Line: 47 Discussion If a Mesh GTKSA had a defined lifetime, the comment could be resolved with something like this: Revised. On page 1970 line 47, replace with as defined in 12.x.y.z“. “Lifetime” “Lifetime, However, Mesh GTKSA does not really have a separate lifetime, i.e., it is valid until deleted/replaced as part of mesh termination or GTK rekeying (with the same Key ID and from the same peer as far as the Mesh GTKSA” is concerned). While this could be explicitly described, it is likely simplest to “receive just delete the Lifetime item from Mesh GTKSA. context (page 1970): Proposed resolution for CID 8115: Revised. On page 1970 line 47, delete the Lifetime item. CID 8325 Location Comment Proposed Change The contents of the Authentication Mesh Peering On page 2146 line 16, add a new item to Clause: Exchange element in Mesh Group Key Inform frames is the list after the GTKdata field item: 14.6.3 described as far as the GTKdata field is concerned. Page: 2146 However, there is no note about the IGTKdata field here. "-- If management frame protection is Line: 14 That field should be noted here as it would need to be used, the IGTKdata field shall be present." present when management frame protection is used. Discussion Note that this is my own comment, so someone else want to take a quick look to confirm.. My proposed action on this should not come as a surprise. REVmc/D6.0 context: Page 2145: Page 2146:
Proposed resolution for CID 8113: Revised. On page 1969 line 22, replace “Lifetime” with “Lifetime, as defined in 12.6.16”. CID 8115 Location Comment Proposed Change Clause: 12.6.1.1.10 Page: 1970 Line: 47 What is the lifetime of a Mesh Add ", as defined in 12.x.y.z" to the end of the referenced line Discussion If a Mesh GTKSA had a defined lifetime, the comment could be resolved with something like this: Revised. On page 1970 line 47, replace “Lifetime” with “Lifetime, as defined in 12.x.y.z“. However, Mesh GTKSA does not really have a separate lifetime, i.e., it is valid until deleted/replaced as part of mesh termination or GTK rekeying (with the same Key ID and from the same peer as far as the “receive Mesh GTKSA” is concerned). While this could be explicitly described, it is likely simplest to just delete the Lifetime item from Mesh GTKSA. context (page 1970): Proposed resolution for CID 8115: Revised. On page 1970 line 47, delete the Lifetime item. CID 8325 Location Comment Proposed Change Clause: 14.6.3 Page: 2146 Line: 14 The contents of the Authentication Mesh Peering Exchange element in Mesh Group Key Inform frames is described as far as the GTKdata field is concerned. However, there is no note about the IGTKdata field here. That field should be noted here as it would need to be present when management frame protection is used. On page 2146 line 16, add a new item to the list after the GTKdata field item: "-- If management frame protection is used, the IGTKdata field shall be present." Discussion Note that this is my own comment, so someone else want to take a quick look to confirm.. My proposed action on this should not come as a surprise. REVmc/D6.0 context: Page 2145: Page 2146: