"4480400023","06/18/2008 23:20:57 EDT",95,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",36,"General Interest","Disapprove","Samsung Electronics","Editorial",280,"L.3",32,"""the802.16""",,"Yes","""the 802.16""","Agree",,,," 06/19/08"
"4480300023","06/18/2008 23:20:57 EDT",94,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",35,"General Interest","Disapprove","Samsung Electronics","Technical",256,"I",26,"""The maximum attainable speed of information transfer over a given communication channel can be constant, as it is usually the case with network segments involving only wired links, or it can be time varying at different scales, as is often the case for segments involving wireless links.""  You've just stated above that ""segment"" is synonymous with ""link"", thus a segment cannot be made up of multiple links",,"Yes","""The maximum attainable speed of information transfer over a given communication channel can be constant, as it is usually the case with communication channels involving only wired links, or it can be time varying at different scales, as is often the case for communication channels involving wireless links.""","Agree","Update accordingly",,,
"4480200023","06/18/2008 23:20:57 EDT",93,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",34,"General Interest","Disapprove","Samsung Electronics","Editorial",256,"I",22,"""A communication medium represents one or multiple point-to-point network segments termed links in this standard""",,"Yes","""A communication medium represents one or multiple point-to-point network segments (which are termed ""links"" in this standard)""",,"Agree","Ref Cmt #94",,
"4480100023","06/18/2008 23:20:57 EDT",92,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",33,"General Interest","Disapprove","Samsung Electronics","Editorial",250,"G.7",14,"""IEEE Std 802.21 (2009)""",,"Yes","""IEEE Std 802.21-2009""","Agree","Updated accordingly. Comment also applies to G.6",,," 06/19/08"
"4480000023","06/18/2008 23:20:57 EDT",91,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",32,"General Interest","Disapprove","Samsung Electronics","Technical",200,"C.3.8",19,"Definition field is blank",,"Yes","Fill in the definition field",,,"TODO: Check the previous contribution on adding 802.16 params. (Ajay or Jin Lee)",,
"4479900023","06/18/2008 23:20:57 EDT",90,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",31,"General Interest","Disapprove","Samsung Electronics","Editorial",168,"8.6.3.11",26,"""This message is used by an MIHF on the serving network to communicate to an MIHF on the candidate network, an intent to initiate a handover""",,"Yes","""This message is used by an MIHF on the serving network to communicate to an MIHF on the candidate network an intent to initiate a handover""","Agree",,,," 06/19/08"
"4479800023","06/18/2008 23:20:57 EDT",89,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",30,"General Interest","Disapprove","Samsung Electronics","Editorial",156,"8.6",53,"""these fields are not optional in the implementation, but only in their use.""",,"Yes","""these fields are mandatory in the implementation, but optional in their use.""","Agree",,,," 06/19/08"
"4479700023","06/18/2008 23:20:57 EDT",88,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",29,"General Interest","Disapprove","Samsung Electronics","Editorial",155,"8.4.2.1",4,"The fragment size may be smaller than the maximum fragment size and shall be larger than that can generate more than 128 fragments",,"Yes","The fragment size may be smaller than the maximum fragment size and shall be larger than the value that can generate more than 128 fragments","Agree",,,," 06/19/08"
"4479600023","06/18/2008 23:20:57 EDT",87,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",28,"General Interest","Disapprove","Samsung Electronics","Editorial",136,"7.5.1.2.2",4,"""Indicate that the data is sent reliably""",,"Yes","""Indicate that the data is to be sent reliably"" or ""Indicate that the data will be sent reliably""","Disagree","The same flag is used in sending and in receiving, so the use of the future tense is not appropriated if the same text is used in both places (7.5.1.1.2 & 7.5.1.2.2)  If consistency is not maintained, the flag would look as thought it has different meanings.",,,
"4479500023","06/18/2008 23:20:57 EDT",86,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",27,"General Interest","Disapprove","Samsung Electronics","Editorial",135,"7.5.1.1.2",16,"""Indicate that the data is sent reliably""",,"Yes","""Indicate that the data is to be sent reliably"" or ""Indicate that the data will be sent reliably""","Disagree","The same flag is used in sending and in receiving, so the use of the future tense is not appropriated if the same text is used in both places (7.5.1.1.2 & 7.5.1.2.2)  If consistency is not maintained, the flag would look as thought it has different meanings.",,,
"4479400023","06/18/2008 23:20:57 EDT",85,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",26,"General Interest","Disapprove","Samsung Electronics","Editorial",134,"7.4.25.4.4",19,"""utilizes""",,"No","""uses""","Disagree","These are synonyms.  Why make the comment?  Why make a change?",,,
"4479300023","06/18/2008 23:20:57 EDT",84,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",25,"General Interest","Disapprove","Samsung Electronics","Editorial",119,"7.4.21.4.4",39,"""Since MIH_Net_HO_Commit request message contains actions to effect the handover, and the response has the status of those actions, the link to the old PoS may not be accessible (e.g. break before make) to receive the response before L3 connectivity has been established on the new link and only if the MN knows the old PoS L3 address thus, the old PoS may not receive this response.""  What a sprawling sentence.",,"Yes","""Since MIH_Net_HO_Commit.request message contains actions to effect the handover, the link to the old PoS may not be accessible (e.g. break before make) to receive the MIH_Net_HO_Commit.response before L3 connectivity has been established on the new link; only if the MN knows the old PoS L3 address could the old PoS receive this response.""",,"Working on alternate wording",,,
"4479200023","06/18/2008 23:20:57 EDT",83,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",24,"General Interest","Disapprove","Samsung Electronics","Editorial",114,"7.4.20.2.4",23,"""Upon receipt of this primitive MIH User on the serving network""",,"Yes","""Upon receipt of this primitive an MIH User on the serving network""","Agree",,,," 06/19/08"
"4479100023","06/18/2008 23:20:57 EDT",82,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",23,"General Interest","Disapprove","Samsung Electronics","Editorial",116,"7.4.21.1.4",47,"""Upon receipt of this primitive MIHF shall send an MIH_NET_HO_Commit request message""",,"Yes","""Upon receipt of this primitive an MIHF shall send an MIH_NET_HO_Commit request message""","Agree",,,," 06/19/08"
"4479000023","06/18/2008 23:20:57 EDT",81,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",22,"General Interest","Disapprove","Samsung Electronics","Technical",33,"5.7.4.2",18,"""the controlled port is in closed state so that MIH messages cannot go through""",,"Yes","""the controlled port is in blocked state so that MIH messages cannot go through""","Agree",,,,
"4478900023","06/18/2008 23:20:57 EDT",80,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",21,"General Interest","Disapprove","Samsung Electronics","Technical",33,"5.7.4.2",15,"""Port closed state""",,"Yes","""Port blocked state""","Agree",,,,
"4478800023","06/18/2008 23:20:57 EDT",79,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",20,"General Interest","Disapprove","Samsung Electronics","Technical",33,"5.7.4.1",7,"""Port open state: LSAP transport""",,"Yes","""Port unblocked state: LSAP transport""","Agree",,,,
"4478700023","06/18/2008 23:20:57 EDT",78,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",19,"General Interest","Disapprove","Samsung Electronics","Technical",33,"5.7.4.1",9,"""the controlled port is open to the transport of authenticated messages""",,"Yes","""the controlled port is unblocked to the transport of authenticated messages""","Agree",,,,
"4478600023","06/18/2008 23:20:57 EDT",77,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",18,"General Interest","Disapprove","Samsung Electronics","Technical",32,"5.7.4",60,"""whereas the controlled port is closed until authentication and association are successful.""",,"Yes","""whereas the controlled port is blocked until authentication and association are successful.""","Agree","Change ""closed"" state to ""blocked"" state wherever applicable.",,,
"4478500023","06/18/2008 23:20:57 EDT",76,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",17,"General Interest","Disapprove","Samsung Electronics","Technical",32,"5.7.4",57,"""802.1X REV""",,"Yes","""802.1X-2004""","Agree",,,,
"4478400023","06/18/2008 23:20:57 EDT",75,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",16,"General Interest","Disapprove","Samsung Electronics","Editorial",31,"5.6.2.10",62,"""defined in the IEEE Std 802.16""",,"Yes","""defined in IEEE Std 802.16""","Agree",,,," 06/19/08"
"4478300023","06/18/2008 23:20:57 EDT",74,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",15,"General Interest","Disapprove","Samsung Electronics","Editorial",31,"5.6.2.9",53,"""defined in the IEEE Std 802.2""",,"Yes","""defined in IEEE Std 802.2""","Agree",,,," 06/19/08"
"4478200023","06/18/2008 23:20:57 EDT",73,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",14,"General Interest","Disapprove","Samsung Electronics","Editorial",31,"5.6.2.7",36,"""defined in the IEEE P802.11u/D2.0""",,"Yes","""defined in IEEE P802.11u/D2.0""","Agree",,,," 06/19/08"
"4478100023","06/18/2008 23:20:57 EDT",72,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",13,"General Interest","Disapprove","Samsung Electronics","Editorial",31,"5.6.2.6",29,"""defined in the IEEE Std 802.16""",,"Yes","""defined in IEEE Std 802.16""","Agree",,,," 06/19/08"
"4478000023","06/18/2008 23:20:57 EDT",71,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",12,"General Interest","Disapprove","Samsung Electronics","Editorial",31,"5.6.2.5",21,"""defined in the IEEE Std 802.16""",,"Yes","""defined in IEEE Std 802.16""","Agree",,,," 06/19/08"
"4477900023","06/18/2008 23:20:57 EDT",70,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",11,"General Interest","Disapprove","Samsung Electronics","Editorial",22,"5.5.1",65,"""Link layer Discovery Protocol (LLDP)""",,"Yes","""Link Layer Discovery Protocol (LLDP)""","Agree",,,," 06/19/08"
"4477800023","06/18/2008 23:20:57 EDT",69,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",10,"General Interest","Disapprove","Samsung Electronics","Editorial",13,"5.1.2",30,"""However irrespective of that, there should be no need for the user to re-establish the service.""",,"Yes","""However, irrespective of that, there should be no need for the user to re-establish the service.""","Agree",,,," 06/19/08"
"4477700023","06/18/2008 23:20:57 EDT",68,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",9,"General Interest","Disapprove","Samsung Electronics","Editorial",92,"7.4.10.1.1",52,"""or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users, who have subscribed to this remote event.""",,"Yes","""or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users who have subscribed to this remote event.""","Principle","removed comma from 7.4.10.1.1 and removed both commas offsetting the who clause in 7.4.10.1.3, since this is an essential clause.",,," 06/19/08"
"4477600023","06/18/2008 23:20:57 EDT",67,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",8,"General Interest","Disapprove","Samsung Electronics","Editorial",91,"7.4.8.1.1",10,"""or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users, who have subscribed to this remote event.""",,"Yes","""or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users who have subscribed to this remote event.""","Principle","removed comma from 7.4.8.1.1 and removed both commas offsetting the who clause in 7.4.8.1.3, since this is an essential clause.",,," 06/19/08"
"4477500023","06/18/2008 23:20:57 EDT",66,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",7,"General Interest","Disapprove","Samsung Electronics","Editorial",90,"7.4.7.1.1",8,"""or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users, who have subscribed to this remote event.""",,"Yes","""or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users who have subscribed to this remote event.""","Principle","removed comma from 7.4.7.1.1 and removed both commas offsetting the who clause in 7.4.7.1.3, since this is an essential clause.",,," 06/19/08"
"4477400023","06/18/2008 23:20:57 EDT",65,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",6,"General Interest","Disapprove","Samsung Electronics","Editorial",63,"7.3.5.4",53,"""MIH Users prepare to initiate handovers.""",,"Yes","""MIH Users then prepare to initiate handovers.""","Principle","Alternate proposal: add "",then,"" since this is a transitional expression 6/19/08 Occurs on page 65, not 63)",,,"06/19/08"
"4477300023","06/18/2008 23:20:57 EDT",64,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",5,"General Interest","Disapprove","Samsung Electronics","Technical",47,"6.5.1",23,"""Other information here is more vendor specific in nature."" What is ""here"" referring to?  This paragraph?  This sentence?  This clause?  This document?",,"Yes","Please be more precise","Agree","For example, classification of different networks into categories, such as  public, enterprise, home, and others, influences a handover decision. These higher layer services information is more vendor specific in nature.",,,
"4477200023","06/18/2008 23:20:57 EDT",63,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",4,"General Interest","Disapprove","Samsung Electronics","Editorial",45,"6.4.3.2.1",11,"""In this case the network commits to do the handover and sends the choice of selected network and associated PoA.""",,"Yes","""Command used by the net to notify the MN of the decided target network information.""","Principle","Alternate proposal: ""Command used by the network to notify the MN of the decided target network information.""",,,"06/19/08"
"4477100023","06/18/2008 23:20:57 EDT",62,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",3,"General Interest","Disapprove","Samsung Electronics","Technical",39,"6.3.4.1",38,"""This event is a discrete event, i.e., it is not associated with other events with a state machine.""  I'm having a difficult time understanding this sentence.",,"Yes","""This event is a discrete event, i.e., it is not associated with events within a state machine.""","Principle","""This event is a discrete event, i.e., it is not associated with other events.""",,,
"4477000023","06/18/2008 23:20:57 EDT",61,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",2,"General Interest","Disapprove","Samsung Electronics","Technical",39,"6.3.4.1",33,"""This event is a discrete event, i.e., it is not associated with other events with a state machine.""  I'm having a difficult time understanding this sentence.",,"Yes","""This event is a discrete event, i.e., it is not associated with events within a state machine.""","Principle","""This event is a discrete event, i.e., it is not associated with other events.""",,,
"4476900023","06/18/2008 23:20:57 EDT",60,"Chaplin, Clint","clint.chaplin@gmail.com","+1(408)239-3348","Individual",1,"General Interest","Disapprove","Samsung Electronics","Editorial",5,"2",27,"""IEEE P802.11k/D13.0""",,"No","""IEEE Std 802.11k-2008""","Agree","Updated accordingly. Also removed ""Draft standard for"" text and updated text in Annex I.3.4 and Table C.13",,,"06/19/08"
"4473600023","06/18/2008 14:34:12 EDT",59,"Cheng, Yuu Heng","yhcheng@research.telcordia.com","17326992185","Individual",2,"General Interest","Approve","Telcordia Technologies","Editorial",178,"Annex B",1,"This mapping is corresponding to the ""Information Element ID"" described in p51L62"". The title does not match",,"No","Rename ""Type identifiers for information elements"" to ""Information Element Identifiers"" throughout this annex. Also consistency throughout the draft, e.g., in p53L63, ""Type="" should become ""Information Element ID="". Correct the ""type"" and ""data type"" description throughout the document.","Agree","Updated as indicated and for alignment updated tables 12, 13, & 14 and MIIS schema annex",,,"06/19/08"
"4473500023","06/18/2008 14:34:12 EDT",58,"Cheng, Yuu Heng","yhcheng@research.telcordia.com","17326992185","Individual",1,"General Interest","Approve","Telcordia Technologies","Technical",144,"8.2.3.3 Table 22",60,"It is not sufficient to use only ACK-Rsp bit to distinguish source and destination state machine for response messages. Because for piggy back response messages (S) and the ACK response for a response (D) will both have ACK-Rsp set in a response message. The difference is that if there are additional payload. Please see contribution",,"No","Add a column ""Payload"" as the forth column to distingush the piggyback ack response with ack response to the response message. Please refer to contribution https://mentor.ieee.org/802.21/file/08/21-08-0182-00-0000-d11-table22.doc","Agree","Update the table according to contribution http://mentor.ieee.org/802.21/file/08/21-08-0182-00-0000-d11-table22.doc",,,
"4473400023","06/18/2008 13:18:42 EDT",57,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",8,"General Interest","Approve","NIST","Technical",94,"7.4.12.1.2",53,"An indication primitive (i.e, a notification) should not have a status parameter, since the indication would not be sent unless the MIH_Link_Handover_Complete is complete.",,"No","Remove LinkHandoverStatus parameter from list and table.",,,"TODO: Jin Lee",,
"4473300023","06/18/2008 13:18:42 EDT",56,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",7,"General Interest","Approve","NIST","Editorial",177,"Annex A",19,"Reference within the Bibliography is old.  Newer one exists.",,"No","Replace ""-10.txt, 2006-09"" with ""-19.txt, 2008-01"" and add ""and Diameter"" to title.","Agree",,,,"06/19/08"
"4473200023","06/18/2008 13:18:42 EDT",55,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",6,"General Interest","Approve","NIST","Editorial",48,"6.5.4",41,"The cross-reference C.3.8 is not correct.  Not all types are defined in C.3.8.  They are all however referenced if the entire Annex C is referenced.",,"No","Replace C.3.8 with Annex C","Agree","Updated accordingly",,,"06/19/08"
"4473100023","06/18/2008 13:18:42 EDT",54,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",5,"General Interest","Approve","NIST","Technical",73,"7.3.13.1.1",57,"The last sentence with reference is cyclical.",,"No","remove entire sentence.","Agree","The sentence is redundant.",,,
"4473000023","06/18/2008 13:18:42 EDT",53,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",4,"General Interest","Approve","NIST","Technical",177,"A",6,"Should 802.3 be moved from Bibliography (Annex A) to Normative reference (Clause 2)",,"No","move 802.3 from Annex A to Normative reference and remove any bibliography cross-references.","Agree",,,,
"4472900023","06/18/2008 13:18:42 EDT",52,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",3,"General Interest","Approve","NIST","Editorial",261,"I.3.2",61,"The word, packet, should be packets in the equation, since it is a ""number of""",,"No","change packet to packets","Agree","Updated accordingly",,,"06/19/08"
"4472800023","06/18/2008 13:18:42 EDT",51,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",2,"General Interest","Approve","NIST","Editorial",253,"G.8.6",45,"Allowed values for timers not present.",,"No","Use range values from MIB for consistency","Agree","Updated accordingly",,,"06/19/08"
"4472700023","06/18/2008 13:18:42 EDT",50,"Cypher, David","david.cypher@nist.gov","1 301 975 4855","Individual",1,"General Interest","Approve","NIST","General",,,,"IEEE Standard Style Manual items need to be addressed.  See Contribution 21-08-0174-00-0000 for details.",,"No","Accept proposed changes in contribution 21-08-0174-00-0000.","Agree",,,,"06/19/08"
"4472500023","06/18/2008 00:24:19 EDT",49,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",22,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.3, Page: 265, Line: 54) For Link_Action, the IEEE 802.11 column indicates ""N/A"".  However, 802.11u does provide a primitive for this named ""MSGCF-ESS-Link-Command"". 

There needs to be some alignment between Link_action and the MSGCF primitives provided by 802.11u.  The actions needed by the Link_Action primitive are implemented in 802.11u as MSGCF-ESS-Link-Command, MSGCF-ESS-Link-Scan.request and MSGCF-ESS-Link-Scan.confirm.  So one 802.21 primitive maps into 3 MSGCF primitives.",,"Yes","Clarify whether or not this overlap is desired and amend the text accordingly.",,,,,
"4472400023","06/18/2008 00:24:19 EDT",48,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",21,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.2, Page: 265, Line: 54) For Link_Action, the IEEE 802.11 column indicates ""N/A"".  However, 802.11u does provide a primitive for this named ""MSGCF-ESS-Link-Command"".",,"Yes","Amend the text.",,,,,
"4472300023","06/18/2008 00:24:19 EDT",47,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",20,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 52-53) For Link_Configure_Thresholds, the IEEE 802.11 column indicates ""MLME-MEASURE.request and MLME-MREQUEST.request"".  However, 802.11u provides primitives for this named ""MSGCF-Set-ESS-Link-Parameters.request"" and ""MSGCF-Set-ESS-Link-Parameters.confirm"".",,"Yes","Amend the text.",,,,,
"4472200023","06/18/2008 00:24:19 EDT",46,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",19,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 50) For Link_Get_Parameters, the IEEE 802.11 column indicates ""N/A"".  However, 802.11u does provide primitives for this named ""MSGCF-ESS-Link-Scan.request"" and ""MSGCF-ESS-Link-Scan.confirm"".",,"Yes","Amend the text.",,,,,
"4472100023","06/18/2008 00:24:19 EDT",45,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",18,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 39-40) As far as I know, there are no primitives defined for Link_Handover_Complete.",,"Yes","Delete the reference to MLME-LinkHandoverComplete.indication.",,,,,
"4472000023","06/18/2008 00:24:19 EDT",44,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",17,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 36-38) As far as I know, there are no primitives defined for Link_Handover_Imminent.",,"Yes","Delete the reference to MLME-LinkHandoverImminent.indication.",,,,,
"4471900023","06/18/2008 00:24:19 EDT",43,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",16,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 33-34) For Link_Going_Down, the IEEE 802.11 column indicates ""MLME-LinkGoingDown.indication"".  However, 802.11u has a different name for this primitive which is ""MSGCF-ESS-Link-Going-Down""",,"Yes","Amend the text.",,,,,
"4471800023","06/18/2008 00:24:19 EDT",42,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",15,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 30-32) Link_Parameters_Report should be MSGCF-ESS-Link-Threshold-Report.",,"Yes","Amend the text.",,,,,
"4471700023","06/18/2008 00:24:19 EDT",41,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",14,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 28-29) For Link_Down, the IEEE 802.11 column indicates ""MLME-LinkDown.indication"".  However, 802.11u has a different name for this primitive which is ""MSGCF-ESS-Link-Down""",,"Yes","Amend the text.",,,,,
"4471600023","06/18/2008 00:24:19 EDT",40,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",13,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 27) For Link_Up, the IEEE 802.11 column indicates ""MLME-LinkUp.indication"".  However, 802.11u has a different name for this primitive which is ""MSGCF-ESS-Link-Up""",,"Yes","Amend the text.",,,,,
"4471500023","06/18/2008 00:24:19 EDT",39,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",12,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex J.1, Page: 265, Line: 25) For Link_Detected, the IEEE 802.11 column indicates ""N/A"".  However, 802.11u does provide a primitive for this named ""MSGCF-ESS-Link-Detected""",,"Yes","Amend the text.",,,"Discuss (802.11u  Cmt #39 through #49)",,
"4471400023","06/18/2008 00:24:19 EDT",38,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",11,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex I.3.2, Page: 262, Line: 1) The text refers to a ""QoS Metric information element"" in 802.11.",,"Yes","As far as I'm aware, there is no such information element in 802.11k.  Correct the text to refer to the proper IE.",,,"TODO: Nada",,
"4471300023","06/18/2008 00:24:19 EDT",37,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",10,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: D, Page: 215, Line: 3-14) TLV type values are only defined for values between 1 and 127 inclusive.",,"Yes","Specify that the type values between 128 and 255 inclusive are reserved (or specify the designation).","Agree","Add a row   (Reserved) | 128-255 | (Reserved for extension)",,,
"4471200023","06/18/2008 00:24:19 EDT",36,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",9,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex C.3.8, Page: 204, Line: 29-36) Wireless - IEEE 802.11 can also operate in the 4.9- and 3.65-GHz bands.",,"Yes","Add a bit for these bands.","Superceed",,"Ref Cmt  #13",,
"4471100023","06/18/2008 00:24:19 EDT",35,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",8,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex C.3.8, Page: 203, Line: 6-28) There is an entry for 802.11 LCI in the table, but this does not address new capabilities coming in 802.11v.",,"Yes","Change ""IEEE 802.11 LCI"" to ""IEEE 802.11""; add a new type as ""LbyR with IEEE 802.11"".  Note that 802.11v supports both methods.",,,"Discuss (is 802.11v already a standard?)",,
"4471000023","06/18/2008 00:24:19 EDT",34,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",7,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex C.3.4, Page: 191, Line: 55) Expressing  signal strength as a percentage is fine, but 802.21 should also support an absolute scale since there will be many different manufacturers of MNs and the percentage scale will, in general, be slightly different for them.  I realize that 802.11 defined percentage, but I still think dBm is superior, especially given that 802.21 supports multiple network types, so a single, absolute scale is the best choice.",,"Yes","Add a new type for Signal strength that reports the measurement on an absolute scale, like dBm.  E.g., add a SIG_STRENGTH_DBM data type.",,,"Discuss (802.11)",,
"4470900023","06/18/2008 00:24:19 EDT",33,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",6,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: Annex C.3.4, Page: 189, Line: 15) These definitions are much better than d9, however, a cross reference to Annex I.3 would tie the names very precisely to their definitions.",,"Yes","Add the cross reference.","Principle","Add individual cross-references to those that are present in Annex I",,,
"4470800023","06/18/2008 00:24:19 EDT",32,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",5,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: 8.5, Page: 156, Line: 9-26) The TLV encoding should permit vendor-specific TLVs wherein there is an OUI defined along with a vendor-specific type.

The reason given by 802.21 WG for not incorporating this comment was that it could not think of an easy way to do this.  This is not a sufficient reason.",,"Yes","Add vendor-specific TLV definition here and in Annex C.  One example that would be acceptable to me is to define an optional field in the TLV that is present when the Type is a pre-defined value (e.g., 100).",,"A list of experimental TLVs are defined in Table D-2 that allows vendor-specific TLV.","Discuss.",,
"4470700023","06/18/2008 00:24:19 EDT",31,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",4,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: 8.5, Page: 156, Line: 9-26) The TLV encoding should permit vendor-specific TLVs wherein there is an OUI defined along with a vendor-specific type.",,"Yes","Add vendor-specific TLV definition here and in Annex C.","Superceed",,"Ref Cmt 32",,
"4470600023","06/18/2008 00:24:19 EDT",30,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",3,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: 6.5.4, Page: 49, Line: 43-44) The text states that this is an ""Indicator whether the access network is a mobile network.""

I believe IE_NET_MOBILE_NETWORK was added to address a comment on draft 9.0 requesting a means to identify that the network itself is mobile (e.g., an access network which is on an airplane, bus or ship--which itself may be in motion).  As such, location-based queries have a different context (the actual location of the network depends upon when the query was posted).

While the commenter applauds the efforts of 802.21, several issues still need to be addressed to properly clarify this specification.",,"Yes","Add a definition in clause 3 for ""mobile network""

On P12L14, the term ""mobile network"" is included in the meaning of the abbreviation of PLMN.   This is unfortunate since while the abbreviation is correct, it clouds the meaning of the term ""mobile network"" provided in the definition of IE_NET_MOBILE_NETWORK.

Same comment applies to the definition of LAC in Table C-3, P183L17-20.

Same comment applies to the definition of PLMN_ID in Table C-3, P183L35-41.

Please consider whether or not the RDF needs to be clarified as well (P223L24-28).",,,"Discuss",,
"4470500023","06/18/2008 00:24:19 EDT",29,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",2,"Producer","Disapprove","Cisco Systems, Inc.","Technical",,,,"Clause: J.1, Page: 264, Line: 54) 7.3.9 Link_Capability_Discover, and the 7.3.10, 11 Link_Event pair are not present in any Annex J tables - are they available in general?",,"No","Delete unavailable primitives.",,"Propse Reject: The left most column should list all primitives that is required in 802.21. The table shows what are the primitives that requires additional extension to the specific media in order to support all 802.21 features.","Discuss",,
"4470400023","06/18/2008 00:24:19 EDT",28,"Myles, Andrew","andrew.myles@cisco.com","+61 2 94407860","Individual",1,"Producer","Disapprove","Cisco Systems, Inc.","Editorial",,,,"Clause: G.5.1, Page: 249, Line: 25) clause is empty.",,"No","Fill or delete","Disagree","G.5.1 is blank as per the instruction from G.4.3.  The space is left blank for the identification of the implementation.  Since there is no standard method for describing all possible implementations, just blank space is provided.",,,
"4470300023","06/17/2008 20:24:46 EDT",27,"Gupta, Vivek","vivekggupta@ieee.org","5034732456","Individual",2,"General Interest","Approve","Intel","General",52,"6.5.6",38,"Operators may want to push policies or other IEs to Mobile devices. The IS could easily support that. Add a capability for operators to push information as well, as opposed to UEs just querying this information.",,"No","Add push capability through MIH_Get_Information.indication primitive.",,"Proposed Reject. This is a new feature. Please socialize and provide detail contribution.",,,
"4470200023","06/17/2008 20:21:19 EDT",26,"Gupta, Vivek","vivekggupta@ieee.org","5034732456","Individual",1,"General Interest","Approve","Intel","General",46,"6.5",,"The Information service supports different information elements. The IS should also support an opque data type (a blob datatype) that could be used to represent policies. This would allow operators to download policies using IS as well.",,"No","Add a datatype that can be used to represent policies",,"Proposed Reject: The vendor specific IE allows operators to represent opque data type.",,,
"4470100023","06/17/2008 18:25:48 EDT",25,"Turner, Michelle","m.d.turner@ieee.org","732-562-3825",,1,,,,"Editorial",1,"1",31,"The initial clause of the document is entitled 1. Introduction, please be advised that the introduction is generally reserved for the frontmatter.
Clause 1, is usually the Overview. 1.1 Scope, 1.2 Purpose.
Please see 10.3 of the IEEE Style Manual for document structure and information on what is typically included in the Overview.",,"Yes",,"Agree","Need to change heading of 1.3 or reorganized text, since we cannot have two overview headings in the same clause",,,"06/19/08"
"4470000023","06/17/2008 16:41:27 EDT",24,"Montemurro, Michael","montem@sympatico.ca","-4031","Individual",7,"General Interest","Disapprove","Research in Motion","Technical",41,"6.2.4",17,"I had an earlier comment which argued that Registration was required for the Event Service and Command Service because the messages were stateful. The text was updated to address the comment. The text changes in this draft revert the text.",,"Yes","Make Registration mandatory for Event and Command service",,,"Discuss",,
"4469900023","06/17/2008 16:41:27 EDT",23,"Montemurro, Michael","montem@sympatico.ca","-4031","Individual",6,"General Interest","Disapprove","Research in Motion","Technical",39,"5.7",12,"This clause provides normative text. However it is part of an informative clause.",,"Yes","Decide on what parts of the clause are normative and what parts of the clause are informative. Keep the informative parts in Clause 5 and move the normative parts to clause 6 or 8.","Superceed",,"Ref Cmt 19",,
"4469800023","06/17/2008 16:41:27 EDT",22,"Montemurro, Michael","montem@sympatico.ca","-4031","Individual",5,"General Interest","Disapprove","Research in Motion","Technical",40,"5.7.4.2",29,"The title should refer to controlled port",,"Yes","Replace ""port"" with ""controlled port""","Agree",,"Ref Cmt 21.",,
"4469700023","06/17/2008 16:41:27 EDT",21,"Montemurro, Michael","montem@sympatico.ca","-4031","Individual",4,"General Interest","Disapprove","Research in Motion","Technical",40,"5.7.4.1",20,"The title should refer to controlled port",,"Yes","Replace ""port"" with ""controlled port""","Agree",,,,
"4469600023","06/17/2008 16:41:27 EDT",20,"Montemurro, Michael","montem@sympatico.ca","-4031","Individual",3,"General Interest","Disapprove","Research in Motion","Technical",40,"5.7.4",14,"WEP is not a viable security mode for IEEE 802.11. It should definitely not be specifically called out in another standard.",,"Yes","Replace the 3rd paragraph with the following sentence: "" When the MIH protocol is used across IEEE 802.11 networks, MIH frames may be exchanged when the STA has successfully authenticated and associated to the IEEE 802.11 Access Point.",,,"Discuss",,
"4469500023","06/17/2008 16:41:27 EDT",19,"Montemurro, Michael","montem@sympatico.ca","-4031","Individual",2,"General Interest","Disapprove","Research in Motion","Technical",39,"5.7.2",23,"The assignment of an Ethertype should be in a normative clause. In this specification, Clause 5 seems to be informative.",,"Yes","Move the contents of 5.7.2 to a normative clause (Clause 6 or 8).",,"Clause 5 is normative.","Discuss: Verify Clause 5 is normative.",,
"4469400023","06/17/2008 16:41:27 EDT",18,"Montemurro, Michael","montem@sympatico.ca","-4031","Individual",1,"General Interest","Disapprove","Research in Motion","Technical",40,"5.7.4",1,"I'm not sure what the purpose of this clause is. Basically the only statement that needs to be made is that MIH frames over L2 are exchanged over the controlled port.",,"Yes","Remove this clause and add the following sentence to the previous clause: ""When IEEE 802.1X is enabled, MIH frames may only be passed through the controlled port.",,,"Discuss with Cmt #20",,
"4469300023","06/17/2008 16:02:54 EDT",17,"Ohba, Yoshihiro","yohba@tari.toshiba.com","201-592-0281","Individual",2,"Producer","Approve","Toshiba America Research, Inc.","Technical",151,"8.2.4.3.1",20,"The current specification mentions that MIHF discovery at L3 is out of the scope, but for completion it should also mention the work being done in the IETF for MIHF discovery at L3.",,"No","- Add the following text to Clause 8.2.4.3.1:
""MIHF discovery mechanisms at layer 3 are defined in the IETF [1][2][3].""
- Add the following references:
[1] http://www3.tools.ietf.org/html/draft-ietf-mipshop-mstp-solution-04.
[2] http://www3.tools.ietf.org",,"Add the corresponding reference.",,,
"4468700023","06/17/2008 10:29:59 EDT",16,"Jee, Junghoon","jhjee@etri.re.kr","8.20E+12","Individual",3,"Producer","Approve","Electronics and Telecommunications Research Instit","Technical",157,"8.6.1.1",40,"By including the SupportedMihEventList, SupportedMihCommandList and SupportedISQueryTypeList, it is possible for peer MIHF entities to identify each other's capability only through one transaction. Therefore, that parameters should be mandatory not optional. Please refer the contribution of 21-07-0082-01 again.",,"No","Please delete the optional keywords in those parameters.",,"The one transaction is an optional feature as stated in 7.4.1.1.1 p76. No changes required.",,,
"4468600023","06/17/2008 10:12:09 EDT",15,"Jee, Junghoon","jhjee@etri.re.kr","8.20E+12","Individual",2,"Producer","Approve","Electronics and Telecommunications Research Instit","Technical",153,"8.4.1.1",28,"The M and FN parts are only useful when using the Eternet transport. In other cases, there's an overhead of one byte by adding that part.",,"No","Please define different header formats. One which is defined for the case when using Ethernet transport and the other which is defined for all other cases.",,"Proposed reject: There is no extra octet.  The header is the same size as it was previously.  M and F bits are from the reserved bits.",,,
"4468500023","06/17/2008 09:43:28 EDT",14,"Jee, Junghoon","jhjee@etri.re.kr","8.20E+12","Individual",1,"Producer","Approve","Electronics and Telecommunications Research Instit","Editorial",293,"L.4.3",64,"The figure titles and the corresponding figures need to be correctly placed in the right form.",,"No","Please place the figure in the page 291 with the figure title of the Figure L-6. Also, please place the figure in the page 292 with the figure title of the Figure L-6a.","Agree","Updated accordingly",,,"06/19/08"
"4463800023","06/16/2008 15:23:33 EDT",13,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",9,"Producer","Disapprove","Nortel Networks","Technical",204,"C.3.8",32,"The revised 802.11 portion of Table C-14 reduces the direct coupling between 802.21 and 802.11 and the result is a cleaner, clearer specification. A necessaru, minimum level of coupling remains. The revised text shows two bit assignments for 802.11, one for 2.4 GHz and another for 5 GHz. However, this specification is incomplete since 802.11 includes definitions for two other bands of operation, namely 316-353 THz (refer to 802.11-2007 cl. 16, IR PHY) and 3.65-3.70 GHz (refer to 802.11y, which recently completed the sponsor ballot process and is now being formally published by IEEE-SA).",,"Yes","Add bit assignments for the 802.11 316-353 THz and 3.65-3.70 GHz bands respectively.",,,"Discuss (802.11)
Cmt 36 Clause: Annex C.3.8, Page: 204, Line: 29-36) Wireless - IEEE 802.11 can also operate in the 4.9- and 3.65-GHz bands.",,
"4463700023","06/16/2008 14:32:26 EDT",12,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",8,"Producer","Disapprove","Nortel Networks","Editorial",294,"L.5",10,"The text of this clause makes several references to Figure L-7 and an ""AP"" entity within that figure. However, the figure does not show an ""AP"" entity.",,"Yes","Show or label the AP entity, or entities, in Figure L-7. Once the AP entities are shown or indicated it will also be necessary to show said AP(s) as being connected to the Internet cloud in the figure, in addition to any existing connections or message flows across those connections. (Connections in this figure seem to be indicated with thin lines, whereas message flows are indicated with thick lines equipped with arrowheads.)",,,"Discuss (Technical)",,
"4463600023","06/16/2008 14:25:56 EDT",11,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",7,"Producer","Disapprove","Nortel Networks","Editorial",294,"L.5",17,"In the phrase ""with Inter-working IE set"" it is unclear whether the word ""set"" is intended as a noun or a verb. In either case the text would be clearer without the word ""set"".",,"Yes","Change ""with Inter-working IE set"" to ""with Inter-working IE"".",,,"Discuss (Technical)",,
"4463500023","06/16/2008 14:21:17 EDT",10,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",6,"Producer","Disapprove","Nortel Networks","Technical",291,"L.4.3",1,"For completeness, the Link Up Indication portion of the figure could include an (optional) LinkDown Indication from the MAC WiMAX to the MN MIHF and subsequently to the MN MIH User.",,"No","Change the title of the ""Link Up Indication"" portion of the Figure L-6 to ""Link Status Change"". Add an optional Link Down Indication that precedes the LinkUpIndications. The LinkDownIndication would flow from the MAC WiMAX to the MN MIHF and subsequently to the MN MIH User. Show those Link Down Indications with a dotted signal line and with the signal text enclosed in parentheses, as in ""(Link Down Indication)"". Do NOT include a Link Going Down Indication, since the whole point of the break-before-make scenario is that no early notification of the link breakage is provided. Add corresponding text to paragraph 5 (revised) to describe the possible presence of a Link Down Indication at that point in sequence.",,,"TODO: Junghoon",,
"4463400023","06/16/2008 14:09:04 EDT",9,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",5,"Producer","Disapprove","Nortel Networks","Technical",293,"L.4.3",27,"The text for paragraph 5 describes a different scenario than that covered by clause L.4.3. At the same time the ""Link Up Indication"" portion of Figure L-6 is not described anywhere.",,"Yes","Remove the existing text of paragraph 5. Add new text for paragraph 5 to describe the Link Up Indication portion of Figure L-6.",,,"TODO: Junghoon",,
"4463300023","06/16/2008 14:01:51 EDT",8,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",4,"Producer","Disapprove","Nortel Networks","Editorial",293,"L.4.3",47,"Grammar: Missing preposition.",,"Yes","Change ""responds the message"" to ""responds to the message"".","Agree","Updated accordingly",,,"06/19/08"
"4463200023","06/16/2008 13:59:49 EDT",7,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",3,"Producer","Disapprove","Nortel Networks","Editorial",293,"L.4.3",46,"This last numbered paragraph is labeled ""10)"", but there are only eight paragraphs.",,"Yes","Renumber the paragraphs correctly.","Agree","Updated accordingly",,,"06/19/08"
"4463100023","06/16/2008 13:56:09 EDT",6,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",2,"Producer","Disapprove","Nortel Networks","Editorial",293,"L.4.3",65,"Figure title for Figure L-6a is shown on this page, but the figure itself is on page 292. The figure title should be bound more closely to the actual figure, preferably on the same page, just below the figure.",,"Yes","Move the Figure title to accompany the actual figure.","Agree","Fix the alignment.",,,"06/19/08"
"4463000023","06/16/2008 13:53:43 EDT",5,"Engwer, Darwin","dengwer@nortel.com","408-495-2588","Individual",1,"Producer","Disapprove","Nortel Networks","Editorial",293,"L.4.3",63,"Figure title for Figure L-6 is shown on this page, but the figure itself is on page 291. The figure title should be bound more closely to the actual figure, preferably on the same page, just below the figure.",,"Yes","Move the Figure title to accompany the actual figure.","Agree","Fix the alignment.",,,"06/19/08"
"4462300023","06/16/2008 07:00:18 EDT",4,"Taniuchi, Kenichi","ktaniuchi@tari.toshiba.com","908-561-4270","Individual",1,"Producer","Approve","Toshiba","Editorial",216,"Annex E",9,"Basic Schema needs to be revised based on change from D9.",,"No","Replace the schema with text file in 21-08-0180-00-0000-Basic_Schema_D11.doc","Agree","Update the basic schema. Reference http://mentor.ieee.org/802.21/file/08/21-08-0180-00-0000-revised-basic-schema.doc",,,"06/19/08"
"4450200023","06/13/2008 10:03:53 EDT",3,"Ohba, Yoshihiro","yohba@tari.toshiba.com","201-592-0281","Individual",1,"Producer","Approve","Toshiba America Research, Inc.","Technical",234,"F.2",10,"The MIH MIB in D11 fails to pass the IETF MIB validation tool (http://www.ops.ietf.org/mib-review-tools.html). It should be updated to pass the MIB validation tool. The MIB should be revised to pass the validation tool.",,"No","Replace the MIB with the one described in https://mentor.ieee.org/802.21/file/08/21-08-0015-10-0000-mih-mib.doc, which passes the IETF MIB validation tool.","Agree","Update the MIB. Please refer to http://mentor.ieee.org/802.21/file/08/21-08-0015-10-0000-mih-mib.doc",,,"06/19/08"
"4412600023","06/04/2008 07:21:44 EDT",2,"Jeffree, Anthony","tony@jeffree.co.uk","-5368","Individual",2,"General Interest","Disapprove","Cisco, HP, Broadcom, Adva","Technical",,,,"In your (revised) response to my comment #145 on the second recirc you state: ""The MIH Protocol is interoperable at both L2 and L3. At L2 the MIH Protocol uses an ethertype as specified by MIH Protocol Ethertype to achieve interoperability. The IEEE 802.21 WG has applied for this ethertype with the IEEE ethernet assignment body. At L3 the MIH Protocol frames are encapsulated within IP frames using a transport protocol such as UDP/TCP/SCTP. Please refer to subclause 5.7. for more details on transport considerations. The protocol behavior is specified in clause 8."" Firstly, if you haven't yet been allocated an Ethertype, then the specification is incomplete and cannot be published; please note that this isn't simply an administrative/editorial issue, as the Ethertype allocation process involves technical vetting of the protocol specification by the IEEE RA's consultant. Secondly, the specification of the protocol doesn't appear to make any clear statements about how L2 addressing is used ""...when destination MIHF ID is not known to a sending MIHF"" (8.3.1.) The following sentence in 8.3.1 states: ""When MIH protocol message with broadcast MIHF ID is transmitted over data plane, the MIH protocol message is broadcasted over either L2 or L3 data plane."" If what you are suggesting is that the protocol makes use of the broadcast MAC address (all F's), then think again; this is not a great idea in a LAN environment, as the scope of that address is literally every station on the LAN. No self-respecting protocol specification uses the broadcast MAC address these days. If you mean to use one or more of the reserved group addresses specified in Clause 8 of IEEE Std 802.1Q that have defined transmission scopes within LAN environments, then you'd better specify which addresses you plan to use, and in what circumstances.",,"Yes","(1.) Specify the Ethertype value in the draft. This is a pre-(not post-) condition for getting the standard approved, for the reasons stated in the comment. (2.) Specify, in detail, how individual and group MAC addressing is used in support of this protocol.",,,"Discuss",,
"4412500023","06/04/2008 07:21:44 EDT",1,"Jeffree, Anthony","tony@jeffree.co.uk","-5368","Individual",1,"General Interest","Disapprove","Cisco, HP, Broadcom, Adva","Technical",,,,"In your (revised) response to my comment #143 on recirc 2 you state: ""The PICS Proforma has been developed w.r.t the following references: [1] ITU-T Recommendation X.290 (1995), OSI conformance testing methodology and framework for protocol
Recommendations for ITU-T applications - General concepts. and [2] ITU-T Recommendation X.296 (1995), OSI conformance testing methodology and framework for protocol
Recommendations for ITU-T applications - Implementation conformance statements."" Both recommendations refer to (protocol specification) conformance clauses, which is a concept that is discussed, defined, and mandated in Recommendation X.291 (1995) for ""Each base specification, which specifies an OSI protocol, abstract syntax, encoding rules, or information object..."" (Clause 6 of Rec X.291). If you are claiming that the PICS proforma has been developed with respect to those two references then: (a) the list of references is incomplete, because X.291 is also part of the story, as you are developing an OSI protocol; and (b) your specification is incomplete, as it does not include a protocol specification conformance clause.",,"Yes","Add a reference to X.291 in Clause 2 of the draft, and follow its guidance (in Clause 6 and elsewhere) by developing a protocol specification conformance clause.",,,"Discuss",,