CableLabsSpecification Engineering Change (EC) Form
Project
EC TRACKING INFORMATION (Blue fields to be completed by CableLabs only)
DOCSIS
N Identifier MULPIv3.1-N-15.1339-2
Status
CM-SP-MULPIV3.1-I06-150611
7/15/2015
Comment Period End Date 7/29/2015
SEVERITY
7/29/2015
Comment Period End Date 8/12/2015
Non-Critical
8/12/2015
116
Critical
Cert Wave No
Overall Type of Change (Tech/Edit/Both) Technical
Affected Specification
ECR Date
ECO Date
ECN Date
ECN Effective Date
Version
2
CHANGE TYPE
Minor
Major
TO OBTAIN LATEST ISSUED SPECIFICATION WORD VERSION, CLICK HERE:
https://www.cablelabs.com/doczone/docsis/requirements/specs/current/issued/
TO SUBMIT EC, EMAIL COMPLETED FORM TO: docsis_ec@cablelabs.com
SPECIFICATION DOCUMENT DETAILS
Document EC is written against: CM-SP-MULPIv3.1 Issued Version # I06
AUTHOR INFORMATION
Primary Author
Email
Company
Additional Contributors
First Margo Last Dolas
mdolas@broadcom.com
Broadcom Corporation
Title of EC
Date sent to CableLabs
Explicit MAP and UCD location
7/15/15
Country
Phone
USA
770-232-0018
ENGINEERING CHANGE DOCUMENT DETAILS
EC REVISION HISTORY
Date of revised EC
Brief description of revision
DETAILED PROPOSED CHANGES
Sections Affected
REQs Affected
6.4.28.1.7; 7.3.1; 7.3.2
Yes
Test Plans Affected
No
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
NOTE! IMPORTANT EC AUTHOR INSTRUCTIONS:
For an ECR to advance to ECO status:
- Requirements Affected section of the embedded DOCSIS-SpecDetailChange.docx must be completed.
- If applicable, the embedded TestPlanDetailChanges.docx must be completed.
For an ECO to advance to ECN status:
- If applicable, compiled MIB files and final Schema docs must be attached before requested changes can
move to ECN status and noted as attachments in the table directly below.
DOCSIS_3.1_Spec-TestPlan_EC-Form_6-2014.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 "Data Over Cable Service
Interface Specifications 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.
This Engineering Change has the following file(s) attached.
Type of Attachment(s) (Visio, Word, txt,
.yang, etc.)
File Name of Attachment(s)
DETAILED DESCRIPTION OF PROBLEM:
MAPs and UCDs for upstream channels can be sent on any downstream channel in the CM’s Receive Channel Set
but the CM is not told explicitly which downstream channel is used to transport the MAPs and UCDs.
With lower channel count scenarios prior to the introduction of the back-up primary downstream channel, requiring
the CM to discover the locations of the MAPs and UCDs was less problematic. However, with higher downstream
channel counts and the addition of back-up primary channels, explicitly telling the CM on which channels the
MAPs and UCDs reside helps ensure consistent operation. For example, there are no clear expectations that the
MAP and UCD placed on the assigned primary downstream channel and back-up primary downstream channels are
the same.
This EC proposes adding a TLV to the MDD to explicitly tell the CM the downstream channels on which MAPs
and UCDs for each upstream channel are sent in order to make transitions occur more quickly and seamlessly.
CHANGE DETAILS FOR THE SPECIFICATION:
Complete Engineering Change details for the specification are contained in the following embedded file:
EChange_MULPIv3.1
-15.1339-1.docx
End of Request
Additional Instructions to EC Author
Embed_Doc_TrkChg_
Instr.docx
DOCSIS_3.1_Spec-TestPlan_EC-Form_5-2014.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 "Data Over Cable Service
Interface Specifications 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.