{"text_format":"1","workbook":"xlsx","n_sheets":5,"sheets":["1904.1 MR","Stats","Status change flow","Parameters","Values"],"not_rendered":{"charts":1,"images":1,"macros":1,"external_links":0,"defined_names":4,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"1904.1 MR","index":0,"n_rows":56,"n_cols":21,"rows_kept":56,"cut":false,"hidden":false,"merged":[]}
["Comment\nNumber","TF?/WG","Comment\nStatus","Resolution\nStatus","Commenter\nSatisfaction","Comment\nCategory","Comment\nType","Required","Page #","Clause","Sub-clause","Line #","Comment","Proposed\nChange","Commenter\nName","Commenter\nAffiliation","Commenter\nEmail","Commenter\nPhone","Comment\nResolution","Last modified on","Created On"]
["20130628_1555","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",51,6,"6.5.2.1.1",null,"IETF RFC 4443 is not included in the list of normative references. ","Add \"IETF RFC 4443 (March 2006), <i>Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification</i>, A. Conta, S. Deering, M. Gupta\" into Clause 2 in the correct location (after IETF RFC 4115) ","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Change per comment. Also add reference to IETF RFC 792 (use title and authors from https://tools.ietf.org/html/rfc792). ","2015.04.01, 13:24","2014.08.01, 09:17"]
["20130628_1602","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",111,7,"7.3.2.2",null,"In Table 7-30, the content of field Description contains reference to \"mode with stripping I-Tag\", whereas the Modifier action clearly shows \"[mi]: REMOVE (B_TAG)\".\nThe text should speak therefore of \"stripping B-Tag\" instead\n","Change \"I-Tag\" to \"B-Tag\" in the selected text","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 13:24","2014.08.01, 09:17"]
["20130628_1607","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",111,7,"7.3.2.2",null,"In Table 7-30, the text \"implements the PBB  encapsulation \" references PBB, which is never defined.","[1] Add definition of PBB into 3.2 as follows: PBB: Provider Backbone Bridging \n[2] Modify the selected text in Table 7-30 to read \"implements the Provider Backbone Bridging (PBB) encapsulation \"","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 13:24","2014.08.01, 09:17"]
["20130628_1610","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",111,7,"7.3.2.3",null,"In Table 7-30, the text \"If provisioned, this set of rules implements the PBB encapsulation mode with stripping B-Tag and I-Tag .\" makes reference to \"I-Tag\" which is not defined anywhere. It should be \"I-Header\"","Change the selected text to read \"If provisioned, this set of rules implements the PBB encapsulation mode with stripping B-Tag and I-Header.","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Changes per comment. \r\nAlso, page 104, line 1, change \"I-Tag\" to \"I-Header\"","2015.04.01, 13:24","2014.08.01, 09:17"]
["20130628_1630","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",166,8,"8.5.1",null,"\"The ONU does not process the collected data in any way. The ONU does not keep performance monitoring data for any earlier performance monitoring period but the last one (within the history bin). All data processing on the collected performance monitoring data is performed at the OLT or Element Management System.\" - we use NMS (in the meaning of Network Management System) elsewhere in the standard. ","Change \"Element Management System\" to \"NMS\" for consistency","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 13:24","2014.08.01, 09:17"]
["20130628_1633","Maintenance","Rejected","None","None",null,"Technical","No",166,8,"8.5.1",null,"\"The ONU does not process the collected data in any way. The ONU does not keep performance monitoring data for any earlier performance monitoring period but the last one (within the history bin). All data processing on the collected performance monitoring data is performed at the OLT or Element Management System.\" - we use NMS (in the meaning of Network Management System) elsewhere in the standard. ","Change \"Element Management System\" to \"NMS\" for consistency","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Duplicate of MR #20130628_1630. ","2015.08.19, 10:53","2014.08.01, 09:17"]
["20130628_2328","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",642,14,"14.4.3.9.1",null,"IEEE Std 1588v2 is missing in normative references right now. It needs to be fixed. ","Insert the following reference into Clause 2: \"IEEE Std 1588(tm)-2008, Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems (also known as IEEE Std 1588v2)\"","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","See MR #20130828_2024 for resolution","2015.04.01, 13:25","2014.08.01, 09:17"]
["20130811_1623","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",661,"4A","4A.2.3",null,"AU-RF4 is really the OLT requirement and not the ONU requirement. The original text in 8.4.1.2 reads: \"The OLT shall not provision a queue threshold size that is less than the maximum frame size. \"","Remove AU-RF4 but keep AU-RF5 as it is (do not renumber) Insert AT-RF3 with the description copied from AU-RF4","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Remove AU-RF4 but keep AU-RF5 as it is (do not renumber). Insert AT-RF3 to section 4A.3.3 REPORT MPCP format with the description copied from AU-RF4","2015.04.01, 13:25","2014.08.01, 09:17"]
["20130822_1851","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",6,2,2,null,"MEF 6 and MEF 6.1 are not mentioned in the body of the standard anywhere apart from entries in Clause 2. As such, they do not need to be listed at all. ","Remove entries for MEF 6 and MEF 6.1, and move footnote 7 reference to MEF 10.2 (the line following MEF 6.1 entry)","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Remove entries for MEF 6 and MEF 6.1, and move footnote 8 reference to MEF 10.2 (the line following MEF 6.1 entry)","2015.04.01, 13:25","2014.08.01, 09:17"]
["20130822_1900","Maintenance","Rejected","None","None",null,"Technical","No",459,14,"14.2.2.11",null,"Attribute aOnuCapabilitiesPwrSav contains sub-attribute sVenSpecFieldSize, defining the size of the sVenSpecField. The value of sVenSpecFieldSize can be derived from the Length field value. The sVenSpecFieldSize sub-attribute is therefore unnecessary. ","Implement the following changes:\n[1] Remove \"sVenSpecFieldSize, \" from the list of sub-attributes in paragraph 1 [2] Remove definition of aOnuCapabilitiesPwrSav.sVenSpecFieldSize sub-attribute [3] remove VenSpecFieldSize field in Table 14-19 [4] modify definition of Length field value to read as follows: The size of TLV fields following the Length field, calculated as follows: 3 + N, where N = length of <c>VenSpecField</c> field\n\n<c></c> designates test in Courier New font\n\nImpact = A change in OAM is needed. This would likely involve a new OAM version (see Table 13-15 - new OAM version 0x11) for Package C. ","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","The Task Force believes that the ONU needs to have information to generate response to the OLT query. No changes to the standard are needed. ","2015.04.01, 13:25","2014.08.01, 09:17"]
["20130822_1903","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",405,13,"13.3.3.6.4",null,"\"Additionally, the ResponseCode field is used to indicate whether ...\" - text contains reference to ResponseCode field, which does not exist in Table 13-64. ResponseCode ought to be ErrorStatus.","Change ResponseCode to <c>ErrorStatus</c>\nText in <c></c> needs to be written in Courier New font. \n\nImpact = None, this is document management change","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Apply suggested change to 13.3.3.6.4 and 13.3.3.6.8. ","2015.04.01, 13:25","2014.08.01, 09:17"]
["20130827_1921","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",637,14,"14.4.3.7.5",null,"The definition of sub-attribute aQueueColorMarking.sFieldCode points to Table 14-220 for individual values. However, just pointing to Table 14-220 here is not sufficient, because that table provides numerical equivalents for various options, but does not explain what each value means or what exact field it represents. \n\nNOTE: Page reference is valid for D3.4\n","We have two options available. \n\nOption 1: in the aQueueColorMarking.sFieldCode definition, we need to have here a complete text as in Sub-attribute aRuleSetConfig.sClause.sFieldCode (14.4.3.6.1.1).  \n\nOption 2: Just reference the sub-attribute aRuleSetConfig.sClause.sFieldCode (14.4.3.6.1.1). \n\nMy personal preference is for Option 2. \n\nThus the sentence \n\n\"Individual values for the FieldCode field are defined in Table 14-220.\" \n\nshould be replaced with\n\n\"Individual values for the sFieldCode sub-attribute are as defined for sub-attribute aRuleSetConfig.sClause.sFieldCode (14.4.3.6.1.1).\"\n\nMake sure the cross reference is live and proper text style is used. \n\nImpact = None, it is only clarification for textual description. ","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","In Table 14-220, add a note at the end of FieldCode, Notes column: \"For definitions of individual fields, see Table 6-1.\"\r\n\r\nAdd field code for \"LINK_INDEX\" to Table 6-1 as defined below:\r\nLINK_INDEX | 8 | Index of a LLID within the given ONU","2015.08.19, 11:04","2014.08.01, 09:17"]
["20130827_1932","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",603,14,"14.4.3.3.42",null,"The object context for aCounterRxFramesL2CP attribute is wrong. It is ONU, whereas it ought to be PON / UNI Port \n\nNOTE: Page reference is valid for D3.4","Change \n\n\"The aCounterRxFramesL2CP attribute is associated with the ONU object ... \"\n\nto \n\n\"The aCounterRxFramesL2CP attribute is associated with the UNI Port or PON Port object ... \"\n\nImpact = The existing object context definition is just wrong. A new firmware version will have to be created and pushed to devices. ","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 13:25","2014.08.01, 09:17"]
["20130828_2024","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",642,14,"14.4.3.9.1",null,"Currently, in several locations in the draft we have reference to \"IEEE Std 1588v2\", which is not in the list of normative references included in Clause 2. I assume that we actually mean \"IEEE Std 1588-2008\", which is the updated version of the original 1588 standard\n\nNOTE: Page and line reference valid for D3.4","1) Add a normative reference to Clause for IEEE Std 1588-2008, with the following text:\n\"IEEE Std 1588(tm)-2008, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems\n2) Add a definition in 3.3 for “IEEE 1588v2” with the following text: \"<b>IEEE 1588v2</b>: represents a shortcut notation for IEEE Std 1588(tm)-2008\"\n3) Replace all 6 instances of \"IEEE Std 1588v2\" with \"IEEE 1588v2\"\n\nImpact = None, it is only clarification for existing normative reference\n","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","\"IEEE Std 1588(tm)-2008, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems\r\n2) Add a definition in 3.3 for “IEEE 1588v2” with the following text: \"<b>IEEE 1588v2</b>: represents a shortcut notation for IEEE Std 1588(tm)-2008\"\r\n3) Replace \"IEEE Std 1588\"  in 9A with \"IEEE 1588v2\"","2015.04.01, 13:27","2014.08.01, 09:17"]
["20130924_0355","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",572,14,"14.4.3.2.2",null,"There are a number of issues with this attribute.\n\n1) The context of the object is ambiguous.   Attribute name aUniDynMacAgeLimit indicates UNI context.  The description of this attribute indicates it should be ONU context.  DPoEv2.0 OAM specification indicates the ONU context is correct.\n\n2) Description is incorrect for this object.  Description indicates that the attribute represents the \"maximum size of the MAC address learning table..\"\n\n3) The name of the attribute should also be changed in Table 14-150.","1) Change the name of the attribute to aOnuDynMacAgeLimit\n\n2) Change description to \"This attribute represents the age limit of the dynamic MAC addresses learned by the ONU.\"\n\n3) Change the name of this attribute in Table 14-150 to match the name in (1) - aOnuDynMacAgeLimit.\n\nImpact : Removing ambiguity (of whether this attribute is ONU context or UNI context) would actually reduce the risk of interoperability issues for this attribute in future implementations.  If interoperability issues are brought to light by this change, the interoperability issues already existed.\n","Edwin Mallette","Bright House Networks","edwin.mallette@bhnis.com","1.813.765.4527","Change globally aUniDynMacAgeLimit to aOnuDynMacAgeLimit. Change the description for this atrribute to read: \"This attribute represents the age limit of the dynamic MAC addresses learned by the ONU. The value of 0x00-00 disables the MAC address aging, i.e., the MAC addresses do not age out.\"\r\n\r\nAlso change aUniDynMacTableSize to aOnuDynMacTableSize (global change). \r\n\r\nChange \"This attribute represents the maximum size of the ONU MAC address learning table for the ONU as a whole.\" to \"This attribute represents the maximum size of the MAC address learning table for the ONU as a whole.\" \r\n","2015.04.01, 13:49","2014.08.01, 09:17"]
["20131001_1523","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",572,14,"14.4.3.2.2",null,"The attribute OnuDynMacAgeLimit when set to 0x00-00 is expected to disable the MAC address learning function in the ONU. it is not described in text right now. ","Change the value of the field in Table 14-150 from \"Value of aUniDynMacAgeLimit attribute\" to \"Value of aUniDynMacAgeLimit attribute:<cr>\n0x00-00: MAC learning function is disabled\n0x00-01 - 0xFF-FF: MAC learning function is enabled; the value expresses the MAC aging limit\"\n\nImpact = It is expected that backward compatibility with devices not implementing this specific meaning of this attribute might be affected. However, it is not clear how a device would implement really aging time of 0x00-00 and what it would mean. I expect that all devices in field today implement this specific meaning of OnuDynMacAgeLimit attribute anyway ","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","See MR #20130924_0355 for changes. \r\n","2015.04.01, 13:50","2014.08.01, 09:17"]
["20131028_1808","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",100,7,"7.2.2.3.2",null,"Footnote after Table 7-26 refers to parameter CVID. This parameter is not used in this table.","Delete table footnote 'b'.\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 15:35","2014.08.01, 09:17"]
["20131029_1956","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",581,14,"14.4.3.2.14",null,"Attribute aOnuFwFileName  (0xD7/0x01-0E) is located in the wrong section. It is located in the \"bridging\" subclause, while it should be located in the \"ONU management\" subclause.","Move 14.4.3.2.14 Attribute aOnuFwFileName (0xD7/0x01-0E) to 14.4.3.1.17 \n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917","Move 14.4.3.2.14 Attribute aOnuFwFileName (0xD7/0x01-0E) to 14.4.3.1.17 . Update Table 14-132 accordingly. Update all cross-references as needed. ","2015.04.01, 15:35","2014.08.01, 09:17"]
["20131105_2020","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",578,14,"14.4.3.2.11",null,"In 1904.1, the attribute aUniFloodUnknown is associated with a UNI port. But the same attribute in DPoE 2.0 is associated with an ONU, i.e., it enables/disables flooding on all UNI ports at once.","Controlling flooding per UNI is more flexible, so perhaps this is the method we should adopt in both standards. Otherwise, use ONU object in SIEPON.\n\nImpact = potential impact on ONU OAM parser","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917","Change page 578: \"The aUniFloodUnknown attribute is associated with the UNI Port object (see 14.4.1.1).\" in 14.4.3.2.11, to \"The aUniFloodUnknown attribute is associated with the ONU object (see 14.4.1.1).\"","2015.04.01, 15:35","2014.08.01, 09:17"]
["20131107_1410","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",344,12,"12.3.3.1.4",1,"In the following sentence, the word \"potential\" is inappropriate. The message is sent only if actual errors were detected.\n\n\"In the case of any errors detected during the process of committing the newly downloaded software image, the ONU sends the eOAM_Software_FileTransferAck eOAMPDU with BlockNumber = 0x00-00 and ResponseCode field that holds any of the values specified in Table 13-101, indicating a potential problem with the software image committing step.\"","Remove the word \"potential\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 15:37","2014.08.01, 09:17"]
["20131107_1416","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",344,12,"12.3.3.2.1",null,"Typo in the definition of \"retryLimit\" variable. In the following sentence, the \"retryCountMax\" should be replaced with \"retryLimit\":\n\n\"Once the retryCountMax transmission attempts fail, the given device reacts per Figure 12-21 for the ONU and Figure 12-22 for the OLT.\"","replace \"retryCountMax\" with \"retryLimit\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 15:39","2014.08.01, 09:17"]
["20131107_1440","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",345,12,"12.3.3.2.2",null,"\"This bit array carries the software image fragment (block) carried in the eOAM_Software_FileTransferData eOAMPDU.\"\n\n\"carries\" and \"carried\" in the same sentence. Generally message carries information, but bit array (as any data types) just contains it.","Replace the sentence to read \"This bit array contains the software image fragment (block) carried in the eOAM_Software_FileTransferData eOAMPDU.\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 15:41","2014.08.01, 09:17"]
["20131107_1442","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",347,12,"12.3.3.2.4",null,"\"This function extracts the software image block number block# from the software image pointed to by image and returns in the form of a bit array saved into the blockData variable.\"\n\nMissing \"it\" after \"returns\".","Insert \"it\" after \"returns\".\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 15:41","2014.08.01, 09:17"]
["20131107_1448","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",353,12,"12.3.3.2.6",null,"Two typos in figure 12-22: \n“eOAM_FTA_Error” in state TRANSFER_ERROR should be “eOAMI_FTA_Error” \n“eOAM_FTA_Error” in state COMMIT_ERROR should be “eOAMI_FTA_ErrorCommit”","In state TRANSFER_ERROR, replace “eOAM_FTA_Error”  with “eOAMI_FTA_Error” \nIn state COMMIT_ERROR, replace “eOAM_FTA_Error” with “eOAMI_FTA_ErrorCommit”\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 15:44","2014.08.01, 09:17"]
["20140807_2103","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",400,13,"13.2.3.5",2,"eOAM_Set_Response eOAMPDU is used by ONU to respond to the eOAM_Set_Request eOAMPDU and contains a series of Variable Containers and Object_ID TLVs.","Change eOAM_Get_Request eOAMPDU in this line to eOAM_Set_Request eOAMPDU.\n\nImpact = None","Lu Yang","RITT, CATR","luyang@ritt.cn","+86-10-62300117","Change \"The eOAM_Set_Response eOAMPDU permits the ONU to respond to the eOAM_Get_Request eOAMPDU\" to \"The eOAM_Set_Response eOAMPDU permits the ONU to respond to the eOAM_Set_Request eOAMPDU\"","2015.04.01, 15:45","2014.08.01, 09:17"]
["20140807_2104","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",518,14,"14.2.2.29",18,"When the OLT uses the Fast-Leave Admin Control TLV (0xC9/0x00-48) to configure the ONU IGMP/MLD agent, ‘enable’ is expressed by 0x00-00-00-02. While in this TLV, the status ‘enable’ is expressed by 0x00-00-00-00. We should keep the value consistent.","In Table 14-45, change enable: 0x00-00-00-00 to enable: 0x00-00-00-02\n\nImpact = None","Lu Yang","RITT, CATR","luyang@ritt.cn","+86-10-62300117",null,"2015.04.01, 15:49","2014.08.01, 09:17"]
["20140807_2105","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",545,14,"14.2.5.3",17,"This TLV is used by OLT to configures the fast-leave state function of the ONU, i.e., enable or disable the fast leave function. And it does not relate to the multicast mode. Furthermore, this is an action which means the attribute is write-only, so it can not represent the current state of the multicast mode.","Delete the paragraph: ‘The state of the fast-leave mode carried in this TLV represents the current state of enabled multicast mode of the ONU, e.g., IGMP-controlled multicast without authorization control mode or IGMP-controlled multicast with authorization control mode.’\n\nImpact = None","Lu Yang","RITT, CATR","luyang@ritt.cn","+86-10-62300117",null,"2015.04.01, 15:53","2014.08.01, 09:17"]
["20140807_2106","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",353,12,"12.3.1.6.2",2,"The message used by OLT instructing the ONU verify the downloaded software image is eOAM_Software_EndDownloadRequest eOAMPDU.","Change eOAM_Software_EndTransferRequest eOAMPDU to eOAM_Software_EndDownloadRequest eOAMPDU.\n\nImpact = None","Lu Yang","RITT, CATR","luyang@ritt.cn","+86-10-62300117","Change \"eOAM_Software_EndTransferRequest\" to \"eOAM_Software_EndDownloadRequest\" - three instances. ","2015.04.01, 16:01","2014.08.01, 09:17"]
["20140807_2106a","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",350,12,"12.3.1.6.2",23,"The message used by OLT instructing the ONU verify the downloaded software image is eOAM_Software_EndDownloadRequest eOAMPDU.","Change eOAM_Software_EndTransferRequest eOAMPDU to eOAM_Software_EndDownloadRequest eOAMPDU.\n\nImpact = None","Lu Yang","RITT, CATR","luyang@ritt.cn","+86-10-62300117","See MR #20140807_2016","2015.04.01, 16:02","2014.08.01, 09:17"]
["20140807_2107","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",351,12,"12.3.1.6.2",8,"The message used by OLT instructing the ONU verify the downloaded software image is eOAM_Software_EndDownloadRequest eOAMPDU","Change eOAM_Software_EndTransferRequest eOAMPDU to eOAM_Software_EndDownloadRequest eOAMPDU.\n\nImpact = None","Lu Yang","RITT, CATR","luyang@ritt.cn","+86-10-62300117","See MR #20140807_2016","2015.04.01, 16:02","2014.08.01, 09:17"]
["20131107_1456","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",436,13,"13.4.2.10.4",null,"Wrong description of the BlockNumber field in Table 13-100. \n\n\"This field reflects the sequential number of the current ONU software image fragment carried in this eOAMPDU.\"\n\nThe eOAM_Software_FileTransferAck eOAMPDU does not carry any software image fragments. ","Replace the sentence \n\n\"This field reflects the sequential number of the current ONU software image fragment carried in this eOAMPDU.\"\n\nwith the sentence\n\n\"“This field carries the sequential number of the software image fragment (block) that the ONU expects to receive next.\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 16:04","2014.08.01, 09:17"]
["20131108_2017","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",118,7,"7.4.2.1",null,"\"The OLT handles the IGMP/MLD of the network, and the ONU filters the multicast data stream as instructed by the OLT through eOAM.\"\n\nThe sentence is confusing.","Rephrase as follows:\n\n\"The OLT handles all IGMP/MLD requests form the multicast clients on the given EPON, and the ONU filters the multicast data stream as instructed by the OLT through eOAM.\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 16:05","2014.08.01, 09:17"]
["20131108_2025","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",289,11,"11.3.4.1.2",null,"In table 11-2, the following sentence is poorly worded and is confusing. \n\n\"This rule is added to all rules that direct to iU referring to LLIDU.\"\n\nIt is incorrect to say that a rule is added to another rule.","Rephrase as follows:\n\n\"This rule is added to precede all rules that direct data traffic to iU associated with the unauthenticated LLIDU.\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 16:07","2014.08.01, 09:17"]
["20131108_2037","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",473,14,"14.2.2.22",null,"The following sentence is confusing. \n\n\"The OLT shall place the length of the IPv6 prefix in the lower octet of the sRuleFieldValue sub-attribute and the value of the prefix starting from  the higher octet of the sRuleFieldValue sub-attribute.\"","Rephrase as follows:\n\n\"The OLT shall place the length of the IPv6 prefix in the lowest octet of the sRuleFieldValue sub-attribute and it shall place the value of the prefix in the higher octets of the sRuleFieldValue sub-attribute, starting from the highest octet.\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 16:10","2014.08.01, 09:17"]
["20131108_2040","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",510,14,"14.2.5.1",null,"The following sentence is confusing. \n\n\"The ONU may not respond to the eOAM_Set_Request eOAMPDU carrying this TLV with the eOAM_Set_Response eOAMPDU with the appropriate return code.\"\n\n“may not” can be interpreted as “not allowed”. Also not clear: no response from the ONU or a response, but with an incorrect code?","Rephrase as follows:\n\n\"The ONU may reboot without generating the eOAM_Set_Response eOAMPDU in  response to the eOAM_Set_Request eOAMPDU carrying the ONU Reboot TLV.\"\n\nImpact = None","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 16:11","2014.08.01, 09:17"]
["20131111_0631","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",306,12,"12.2.2.2 ",14,"A field name in the OAMPDU should be a single word by using \"_\" (underscore) to avoid confusion to readers.\nSee also the comment #22206 for IEEE P1904.1/Conformance resolved in the IEEE P1904.1 Working Group.","Change \"Vendor Specific Information\" and \"Vendor Specific Info\" to \"Vendor_Specific_Information\" in 12.2.2.2, Figure 12-7 and Table 12-2.\nImpact = None","Motoyuki Takizawa","Fujitsu Telecom Networks","takizawa.motoyu@jp.fujitsu.com","81-44-814-9032","Change \"Vendor Specific Information\" and \"Vendor Specific Info\" to \"Vendor_Specific_Information\" in 12.2.2.2, Figure 12-7 and Table 12-2, and associated PICS (pages 717, 732)","2015.04.01, 16:14","2014.08.01, 09:17"]
["20140103_1828","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",325,12,"12.3.1.6.5",null,"The value of EventID for eOAMR_ActivationFailure and eOAMR_ActivationSuccess is not correct.\neOAMR_ActivationFailure uses now EventID of 0x00-0E and eOAMR_ActivationSuccess - 0x00-0F. However, the normative Table 9-2 assigns EventID of 0x00-0E to ActivationSuccessEvent and 0x00-0F to ActivationFailureEvent. ","Change the value of EventID in definition of eOAMR_ActivationFailure from 0x00-0E to 0x00-0F. \nChange the value of EventID in definition of eOAMR_ActivationSuccess from 0x00-0F to 0x00-0E.\n\nImpact = None","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 18:36","2014.08.01, 09:17"]
["20140212_1524","Maintenance","Under Discussion","None","None",null,"Technical","No",null,13,"13.4.4",null,"AI from comment #23185 called for an MR on Package A OAM definitions, adding text around the requirement to respond within 1 second, as discussed at December 2013 meeting. ","See siepon_1402_hajduczenia_1a for details of changes - two new subclauses are added: one in Clause 13, and one in Clause 14. \n\nImpact = None, it is just formal description of already existing behaviour. ","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Remove \", with the exception of the ONU’s failure to respond to a The OLT shall not deregister the ONU generating the ONU Busy alarm with the exception of the critical TLVs, as defined 14.4.7\" from the file\"\r\n\r\nPostponed till next meeting to clarify the intent for Critcial TLV. \r\n\r\n20150819: Curtis & Marek to examine information from DPoE interop / email, initiate discussion on the critical OAM in Package A after the meeting.","2015.08.19, 12:00","2014.08.01, 09:17"]
["20140915_1355","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",422,13,"13.4.1.3.1 ",null,"DPoE-SP-OAMv2 was updated recently to I06, with many changes that need to be captured in SIEPON, Package A. ","See 13.4.1.3.1.docx with tracked changes. \n\nImpact: New capabilities are added. Existing devices *may* not be able to support all added features.","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Use rmtf_1410_hajduczenia_1a for changes.","2015.04.01, 16:50","2014.10.14, 09:17"]
["20140915_1412","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",423,13,"13.4.1.3.2",null,"In Table 13-84, the size of ObjectInstance is given as \"2\", but there are objects with size of \"1\" (ONU, PON port, LLID, UNI port), \"2\" (Multicast Logical Link, added in DPoE-SP-OAMv2-I06) or even \"4\" (Queue) as defined in 14.4.1.1.2.","See 13.4.1.3.2.docx with tracked changes.\n\nImpact: New capabilities are added. Existing devices *may* not be able to support all added features.","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Use rmtf_1410_hajduczenia_2.pdf","2015.04.01, 16:52","2014.10.14, 09:17"]
["20140915_1447","Maintenance","Under Discussion","None","None",null,"Technical","No",427,13,"13.4.2",null,"DPoE-SP-OAMv2-I06 introduces a number of changes to the individual eOAMPDUs: (a) eOAM_MC_Control is modified to control dynamic multicast session on per CPE basis, (b) eOAM_MC_ControlResponse becomes has changes in allocation of response codes, (c) eOAM_MC_Control for static multicast sessions, and (d) eOAM_MC_ControlResponse for static multicast control are added","See 13.4.2.docx with tracked changes. \n\nImpact: New capabilities are added. Existing devices *may* not be able to support all added features.","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Use rmtf_1410_hajduczenia_3a.pdf. The status to remain \"Under Discussion\" until behavior is clarified in DPoE specification. \r\n\r\n20150819: On Glen's ToDo list to prepare a contribution on this topic; offline discussion took place.","2015.08.19, 11:53","2014.10.14, 09:17"]
["20140915_1502","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",552,14,"14.4.1.1",null,"DPoE-SP-OAMv2-I06 introduces a number of changes Object Context TLV:\na) multicast LLID context object is added, with opcode 0x00-06\nb) MEP context object is reserved (opcode 0x00-05)\nc) LLID context object is redefined for unicast LLID only (opcode 0x00-02)","See 14.4.1.1.docx with tracked changes\n\nImpact: New capabilities are added. Existing devices *may* not be able to support all added features.","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Use rmtf_1410_hajduczenia_4a.pdf","2015.04.01, 17:22","2014.10.14, 09:17"]
["20140915_1736","Maintenance","Revised / Ready for Ballot","None","None",null,"Technical","No",557,14,"14.4.3, 14.4.4, 14.4.5, and 14.4.6 ",null,"DPoE-SP-OAMv1 I06 adds a number of changes to existing TLV attributes (mainly, changes in size of attributes) and adds a number of new TLVs, associated with ONU identification (Vendor Name, Model Number, Hardware Version, and EPON mode), as well as three TLVs for UNI management (EEE status, POE status, and media type for media-selectable UNIs).","See TLV.docx for list of tracked changes. \n\nImpact: New capabilities are added. Existing devices *may* not be able to support all added features.","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669","Use rmtf_1410_hajduczenia_5a.pdf \r\n\r\nAdd Acronym in 3.2: NVS = Non-Volatile Storage","2015.04.02, 11:18","2014.10.14, 12:42"]
["20141014_1050","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No","187",9,"9.2.4 ",null,"PON_IF_Switch event definition points to 9.2.4.8 (see Table 9-2) but the link is dead (it is text, no hyperlink). Furthermore, 9.2.4.8 defines ONUTempHighAlarm and ONUTempLowAlarm, which in table 9-2 are marked as pointing to 9.2.4.9. \n\nIt seems that:\n1) link for ONUTempHighAlarm and ONUTempLowAlarm should be fixed to point to correct number (9.2.4.8)\n2) link for PON_IF_Switch event should be fixed and point to 9.2.4.9 - make sure that it is live. ","Per comment\n\nImpact: None - incorrect cross-references","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 18:24","2014.10.14, 12:42"]
["20150119_2025","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",297,12,"12.2.1.2.2.5",null,"All eOAMI_... primitives in this clause expect Revision value in Extended Information TLV to be 0x01 (according to 13.2.2.3.1), but all eOAMR_... primitives generate Revision = 0x10","Change Revision value from 0x10 to 0x01 in the definitions of eOAMR_Discovery( versionList ) eOAMR_DiscoveryAck( eOAMver ) eOAMR_RevisionNack\n\nImpact = May affect existing implementations.","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.04.01, 18:27","2014.08.01, 09:17"]
["20150227-1111","Maintenance","Out of Scope","None","None",null,"Technical","No",29,6,"6.5.3",null,"Insert result can not carry values. After insert a new field, a SET result is required to set the value of the new field. And the length of field code should be 1.","change Table 35 as proposed in rmtf_1502_lu_1.pdf \n\nImpact: none","Lu Yang","RITT, CATR","luyang@ritt.cn","86-18510550580","The MR applies to Conformance01, not to the base 1904.1 standard. An identical MR is already submitted against Conformance01.","2015.04.01, 18:27","2015.04.01, 18:27"]
["20150228-0117","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",622,14,"14.4.3.6.1.3",null,"Size of Field code is 1 octet.","In Table 14-223, change the Size of FieldCode from 2 to 1.\n\nImpact: none","Lu Yang","RITT, CATR","luyang@ritt.cn","86-18510550580",null,"2015.04.01, 18:29","2015.04.01, 18:29"]
["20150228-0118","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",622,14,"14.4.3.6.1.3",null,"Size of Field code is 1 octet.","In Table 14-224, change the Size of FieldCode from 2 to 1.\n\nImpact: none","Lu Yang","RITT, CATR","luyang@ritt.cn","86-18510550580",null,"2015.04.01, 18:29","2015.04.01, 18:29"]
["20150228-0118a","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",623,14,"14.4.3.6.1.3",null,"Size of Field code is 1 octet.","In Table 14-225, change the Size of FieldCode from 2 to 1.\n\nImpact: none","Lu Yang","RITT, CATR","luyang@ritt.cn","86-18510550580",null,"2015.04.01, 18:29","2015.04.01, 18:29"]
["20150316-1746","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",4,2,2,null,"IEEE Std 802.1Q(tm)-2011 has bee updated to 2014 version, incorporating a bunch of other versions and revisions. ","Change \"IEEE Std 802.1Qâ„¢-2011\" in Clause 2 to \"IEEE Std 802.1Qâ„¢-2014\". \n\nIn following tables: 7-6, 7-10, 7-11, 7-13, reference to \"IEEE Std 802.1Q, 3.132\" needs to be changed to \"IEEE Std 802.1Q, 3.93\"\n\nIn following tables: 7-10, 7-13 reference to \"IEEE Std 802.1Q, 3.203\" needs to be changed to \"IEEE Std 802.1Q, 3.199\"\n\nAll other references to 802.1Q in the body of the standard are correct as they are today. \n\nImpact: None - it is just editorial update to the latest version of the standard","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 18:31","2015.04.01, 18:31"]
["20131009-0519","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No","299",12,"12.2.1.2.2.4",null,"\"The function should return the value representing the highest (newest) OAM version.\" contains unintentional optional requirement (\"should\") which does not make much sense in the context.\nIt is also not reflected in the PICS today.\nAlso, it is prescribed that the newest / highest OAM version is selected, whereas it can be OLT manufacturer implementation decision what version is going to be used, once common versions have been found between ONU and OLT. The selections should be vendor specific and outside the scope of the specification.","Remove the indicated text altogether - the previous statement, i.e., \"This function selects and returns a single version of extended OAM from the list versionList.\" is more than sufficient to define the function in question.\n\nImpact: Unclear at this time whether the optional requirement was intentional or not. In the worst case scenario, a new software load for OLT would be needed","Marek Hajduczenia","Bright House Networks","marek.hajduczenia@ieee.org","1.813.465.0669",null,"2015.04.01, 18:34","2015.04.01, 18:34"]
["20150804-1945","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",104,7,"7.3.1.3",null,"\"The Replace Tag operation may replace the entire selected tag or only one subfield of B-Tag, I-Tag, or I-Header fields. The operation shall be capable of altering the following subfields: B-DA, B-SA, B_TAG, B-TPID, B-PCP, B-DEI, B-VID, I_TAG, I-TPID, I-PCP, I-DEI, I-UCA, I-RES, I-SID, and I_HEADER.\"\nThe above text mixes field names (like B-SA, I-TPID) with field codes that are to be used only in the code examples (B_TAG, I_HEADER).","Delete words \"B_TAG\", \"I_TAG\", and \"I_HEADER\" from the second sentence. These are not subfields and the preceding sentence already states that these fields can be replaced.\n\nImpact: None. This change does not alter the Replace Tag operation. It just makes the description consistent with the conventions used in the standard.","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917","Delete words \"B_TAG\", \"I_TAG\", and \"I_HEADER\" from the second sentence. ","2015.08.19, 11:56","2015.08.06, 12:38"]
["20150804-1950","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",50,6,"6.5.2.1.1",null,"Wrong name is used for a subfield of B-TAG field.","Replace B_CFI with B_DEI\n\nImpact: None. This is the only instance of B_CFI in the document.","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.08.19, 11:57","2015.08.06, 12:38"]
["20150804-1955","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No","50",6,"6.5.2.1.1",null,"Wrong name is used for a subfield of I-TAG field. Not all subfields of I-TAG are shown.","Replace sentence\n\"Backbone Service Instance Tag (I-component), comprising I_TPID, I_PCP, I_CFI, and I_VID fields, per IEEE Std 802.1Q, 9.7\"\n\nwith the following sentence\n\n\"Backbone Service Instance Tag (I-component), comprising I_TPID, I_PCP, I_DEI, I_UCA, I_RES, and I_SID fields, per IEEE Std 802.1Q, 9.7\"\n\nImpact: None. Fields I_CFI and I_VID do not exist. This change uses the correct names of the subfields and adds missing subfields.","Glen Kramer","Broadcom","gkramer@broadcom.com","707-529-0917",null,"2015.08.19, 11:58","2015.08.06, 12:38"]
["20150806-0858","Maintenance","Accepted / Ready for Ballot","None","None",null,"Technical","No",453,14,"14.2.2.6",null,"The range of sub-attribute aOnuConfigTimeDrift.sHoldOverPeriod is defined as 0-65536, which means holdover timer is set to 65s. This will never happen in EPON sysgtem.","Change the Range of sHoldOverPeriod to:0x00-32 (50) to 0x03-E8 (1000) \nImpact: No impact on existing networks.","Lu Yang","RITT, CATR","luyang@ritt.cn","86-18510550580",null,"2015.08.19, 12:00","2015.08.06, 12:39"]

{"sheet":"Stats","index":1,"n_rows":37,"n_cols":7,"rows_kept":37,"cut":false,"hidden":true,"merged":[]}
[null,"E","ER","T","TR",null,"Totals"]
[0,{"$f":"get_Stats($A2,B$1)","v":0},0,0,0,{"$f":"get_TF_assignment(A2)","v":"WG"},{"$f":"SUM(B2:F2)","v":0}]
[99,0,0,0,0,"WG",{"$f":"SUM(B3:F3)","v":0}]
[1,0,0,0,0,{"$f":"get_TF_assignment(A4)","v":"WG"},{"$f":"SUM(B4:E4)","v":0}]
[2,0,0,2,0,"WG",2]
[3,0,0,0,0,"WG",0]
[4,0,0,0,0,"WG",0]
["4A",0,0,1,0,"TF5",{"$f":"SUM(B8:E8)","v":1}]
["4B",0,0,0,0,"TF5",0]
["4C",0,0,0,0,"TF5",0]
[5,0,0,0,0,"WG",0]
["5A",0,0,0,0,"WG",0]
[6,0,0,4,0,"TF1",4]
[7,0,0,6,0,"TF1",6]
["7A",0,0,0,0,"TF1",0]
[8,0,0,2,0,"TF2",2]
[9,0,0,1,0,"TF3",1]
["9A",{"$f":"get_Stats($A18,B$1)","v":0},0,0,0,"TF3",0]
["9B",0,0,0,0,"TF3",0]
[10,0,0,0,0,"TF3",0]
["10A",0,0,0,0,"TF3",0]
[11,0,0,1,0,"TF4",1]
[12,0,0,12,0,"TF4",12]
[13,0,0,7,0,"TF4",7]
["13A",0,0,0,0,"TF4",0]
[14,0,0,19,0,"TF4",19]
[null,null,null,null,null,null,{"$f":"SUM(G2:G26)","v":55}]
["Totals",{"$f":"SUM(B2:B26)","v":0},{"$f":"SUM(C2:C26)","v":0},{"$f":"SUM(D2:D26)","v":55},{"$f":"SUM(E2:E26)","v":0},{"$f":"SUM(B28:E28)","v":55},{"$f":"IF(F28=G27,\"OK\",\"ERROR\")","v":"OK"}]
[]
["TFs","WG","TF1","TF2","TF3","TF4","TF5"]
["All",{"$f":"SUM(G2:G7,G11:G12)","v":2},{"$f":"SUM(G13:G15)","v":10},{"$f":"SUM(G16)","v":2},{"$f":"SUM(G17:G21)","v":1},{"$f":"SUM(G22:G26)","v":39},{"$f":"SUM(G8:G10)","v":1}]
["E",{"$f":"SUM(B2:B7,B11:B12)","v":0},{"$f":"SUM(B13:B15)","v":0},{"$f":"SUM(B16)","v":0},{"$f":"SUM(B17:B21)","v":0},{"$f":"SUM(B22:B26)","v":0},{"$f":"SUM(B8:B10)","v":0}]
["ER",{"$f":"SUM(C2:C7,C11:C12)","v":0},{"$f":"SUM(C13:C15)","v":0},{"$f":"SUM(C16)","v":0},{"$f":"SUM(C17:C21)","v":0},{"$f":"SUM(C22:C26)","v":0},{"$f":"SUM(C8:C10)","v":0}]
["T",{"$f":"SUM(D2:D7,D11:D12)","v":2},{"$f":"SUM(D13:D15)","v":10},{"$f":"SUM(D16)","v":2},{"$f":"SUM(D17:D21)","v":1},{"$f":"SUM(D22:D26)","v":39},{"$f":"SUM(D8:D10)","v":1}]
["TR",{"$f":"SUM(E2:E7,E11:E12)","v":0},{"$f":"SUM(E13:E15)","v":0},{"$f":"SUM(E16)","v":0},{"$f":"SUM(E17:E21)","v":0},{"$f":"SUM(E22:E26)","v":0},{"$f":"SUM(E8:E10)","v":0}]
["E+ER",{"$f":"SUM(B32:B33)","v":0},{"$f":"SUM(C32:C33)","v":0},0,0,0,0]
["T+TR",{"$f":"SUM(B34:B35)","v":2},{"$f":"SUM(C34:C35)","v":10},2,1,39,1]

{"sheet":"Status change flow","index":2,"n_rows":0,"n_cols":0,"rows_kept":0,"cut":false,"hidden":false,"merged":[[1,0,1,1]]}

{"sheet":"Parameters","index":3,"n_rows":50,"n_cols":8,"rows_kept":50,"cut":false,"hidden":true,"merged":[]}
[10000,"TF1","New","AIP","Satisfied","Technical","Yes",50]
[null,"TF2","Incomplete","Accept","Unsatisfied","Editorial","No",49]
[null,"TF3","Postponed","Reject",null,null,null,48]
[null,"TF4","Resolved",null,null,null,null,47]
[null,"WG","Withdrawn",null,null,null,null,46]
[null,null,"Proposed",null,null,null,null,45]
[null,null,"Closed",null,null,null,null,44]
[null,null,null,null,null,null,null,43]
[null,null,null,null,null,null,null,42]
[null,null,null,null,null,null,null,41]
[null,null,null,null,null,null,null,40]
[null,null,null,null,null,null,null,39]
[null,null,null,null,null,null,null,38]
[null,null,null,null,null,null,null,37]
[null,null,null,null,null,null,null,36]
[null,null,null,null,null,null,null,35]
[null,null,null,null,null,null,null,34]
[null,null,null,null,null,null,null,33]
[null,null,null,null,null,null,null,32]
[null,null,null,null,null,null,null,31]
[null,null,null,null,null,null,null,30]
[null,null,null,null,null,null,null,29]
[null,null,null,null,null,null,null,28]
[null,null,null,null,null,null,null,27]
[null,null,null,null,null,null,null,26]
[null,null,null,null,null,null,null,25]
[null,null,null,null,null,null,null,24]
[null,null,null,null,null,null,null,23]
[null,null,null,null,null,null,null,22]
[null,null,null,null,null,null,null,21]
[null,null,null,null,null,null,null,20]
[null,null,null,null,null,null,null,19]
[null,null,null,null,null,null,null,18]
[null,null,null,null,null,null,null,17]
[null,null,null,null,null,null,null,16]
[null,null,null,null,null,null,null,15]
[null,null,null,null,null,null,null,14]
[null,null,null,null,null,null,null,13]
[null,null,null,null,null,null,null,12]
[null,null,null,null,null,null,null,11]
[null,null,null,null,null,null,null,10]
[null,null,null,null,null,null,null,9]
[null,null,null,null,null,null,null,8]
[null,null,null,null,null,null,null,7]
[null,null,null,null,null,null,null,6]
[null,null,null,null,null,null,null,5]
[null,null,null,null,null,null,null,4]
[null,null,null,null,null,null,null,3]
[null,null,null,null,null,null,null,2]
[null,null,null,null,null,null,null,1]

{"sheet":"Values","index":4,"n_rows":25,"n_cols":7,"rows_kept":25,"cut":false,"hidden":true,"merged":[]}
["None","None","WG","None","Technical","Yes",0]
["New","AIP","TF1","Satisfied","Editorial","No",1]
["Proposed","Accept","TF2","Unsatisfied",null,null,2]
["Postponed","Reject","TF3","TBD",null,null,3]
["Incomplete",null,"TF4",null,null,null,4]
["Withdrawn",null,"TF5",null,null,null,"4A"]
["Resolved",null,null,null,null,null,"4B"]
[null,null,null,null,null,null,"4C"]
[null,null,null,null,null,null,5]
[null,null,null,null,null,null,"5A"]
[null,null,null,null,null,null,6]
[null,null,null,null,null,null,7]
[null,null,null,null,null,null,"7A"]
[null,null,null,null,null,null,8]
[null,null,null,null,null,null,9]
[null,null,null,null,null,null,"9A"]
[null,null,null,null,null,null,"9B"]
[null,null,null,null,null,null,10]
[null,null,null,null,null,null,"10A"]
[null,null,null,null,null,null,11]
[null,null,null,null,null,null,12]
[null,null,null,null,null,null,13]
[null,null,null,null,null,null,"13A"]
[null,null,null,null,null,null,14]
[null,null,null,null,null,null,99]