MULPIv2.0-N-13.0099

advertisement
CableLabsīƒ’ī€ Specification Engineering Change (EC) Form
Project
EC TRACKING INFORMATION (Blue fields to be completed by CableLabs only)
N Identifier MULPIv2.0-N-13.0099-1
Status
DPoE
Affected Specification
ECR Date
ECO Date
ECN Date
ECN Effective Date
Version
DPOE-SP-MULPIV2.0-I03-130808
7/18/2013
Comment Period End Date 8/1/2013
SEVERITY
8/1/2013
Comment Period End Date 8/15/2013
Non-Critical
Minor
8/15/2013
105
Critical
Cert Wave No
Overall Type of Change (Tech/Edit/Both) Both
TO OBTAIN LATEST ISSUED SPECIFICATION VERSION, CLICK HERE :
https://www.cablelabs.com/doczone/dpoe/requirements/specs/current/issued/
TO SUBMIT EC, EMAIL COMPLETED FORM TO: dpoe-ec@cablelabs.com
SPECIFICATION DOCUMENT DETAILS
Document EC is written against: DPoE-SP-MULPIv2.0 Issued Version # I01
AUTHOR INFORMATION
Primary Author
Email
Company
Additional Contributors
First Marek Last Hajduczenia
marek.hajduczenia@zte.pt
ZTE Corporation
Curtis Knittle (CableLabs)
Title of EC
Date sent to CableLabs
Error in DPoE Version Number TLV
Country
Phone
Portugal
+351-961-121-851
ENGINEERING CHANGE DOCUMENT DETAILS
EC REVISION HISTORY
Date of revised EC
Brief description of revision
DETAILED PROPOSED CHANGES
Sections Affected
REQs Affected
C.9.1, C.9, C.9.2 - C.9.5, C.9.7
Yes
Test Plans Affected
Unknown
OTHER RELATED ENGINEERING CHANGES (LIST ALL THE APPLY)
The following EC(s) are recommended to be processed in conjunction with this document:
EC#
Title of EC
Affected Document
DETAILED DESCRIPTION OF PROBLEM:
Definition of DPoE Version Number TLV, included in C.9.1 in DPoE-SP-MULPIv2, makes reference to 802.3
OAM INFOPDU, specifically, to the “TLV type 0xEF”, which supposedly “refers to Info TLV extension”. Closer
inspection of the content of Table 57–6—Information TLV types, in IEEE Std 802.3-2012, indicates that the proper
code point for Organization Specific Information TLV is 0xFE and not 0xEF as provided in the published
MULPIv2 spec.
DPoE_Spec-TestPlan_EC-Form_01-2013.docx
1 of 2
In submitting the Engineering Change Request ("ECR"), the Author(s) [primary author, additional authors, and contributors], individually and as
an authorized representative of the Company, agrees that if CableLabs incorporates this ECR in whole or in part into the relevant Specification,
all intellectual property in the ECR shall be licensed royalty free, and without confidentiality, under the terms of the "Cable Data Services License
Agreement" ("Contribution Agreement"). CableLabs may disclose the content of this ECR to CableLabs' members and such others as is
necessary for the development of CableLabs' specifications. Questions about the Authors' licensing of intellectual property in this ECR
submission may be directed to legal@cablelabs.com.
1
There are also further wording inconsistencies which need to be corrected to better describe the Information
OAMPDU and DPoE extended Info OAMPDU. The current wording is at best unclear, and at places, technically
incorrect.
Furthermore, there is no specific text describing mandatory requirements for the DPoE System to use the values
polled from the DPoE ONU to populate specific DHCP TLVs sent by the vCM. There is only informative text,
leaving it open for implementers to use arbitrary values, should they choose to do that. Once the text is clarified, as
proposed, it is also not necessary to repeat in each and every DHCP TLV that the value for this parameter is
retrieved via OAMPDUs and TLVs.
CHANGE DETAILS:
Complete Engineering Change details are contained in the following embedded file:
DPoE-SpecDetailCha
nges.docx
End of Request
INSTRUCTIONS TO EC AUTHOR
Track Change
Instructions.docx
DPoE_Spec-TestPlan_EC-Form_01-2013.docx
2 of 2
In submitting the Engineering Change Request ("ECR"), the Author(s) [primary author, additional authors, and contributors], individually and as
an authorized representative of the Company, agrees that if CableLabs incorporates this ECR in whole or in part into the relevant Specification,
all intellectual property in the ECR shall be licensed royalty free, and without confidentiality, under the terms of the "Cable Data Services License
Agreement" ("Contribution Agreement"). CableLabs may disclose the content of this ECR to CableLabs' members and such others as is
necessary for the development of CableLabs' specifications. Questions about the Authors' licensing of intellectual property in this ECR
submission may be directed to legal@cablelabs.com.
Download