
EC T RACKING I NFORMATION (Blue fields to be completed by CableLabs only)
Project DOCSIS Status N Identifier MULPIv3.0-N-14.1144-2
Affected Specification CM-SP-MULPI V 3.0-I24-140403
ECR Date 5/21/2014 Comment Period End Date 6/4/2014
ECO Date
ECN Date
ECN Effective Date
5/7/2014
6/4/2014
Comment Period End Date
Cert Wave No 111
Overall Type of Change (Tech/Edit/Both) Both
S EVERITY
Non-Critical
Critical
TO OBTAIN LATEST ISSUED S PECIFICATION W ORD VERSION , CLICK HERE : https://www.cablelabs.com/doczone/docsis/requirements/specs/current/issued/
Version 2
C HANGE T YPE
Minor
Major
TO SUBMIT EC , EMAIL COMPLETED FORM TO : docsis_ec@cablelabs.com
SPECIFICATION DOCUMENT DETAILS
Document EC is written against: CM-SP-MULPIv3.0 Issued Version # 24
Primary Author
AUTHOR INFORMATION
First Margo Last Dolas
Email
Company
Additional Contributors
Title of EC mdolas@broadcom.com
Broadcom Corporation
ENGINEERING CHANGE DOCUMENT DETAILS
Ranging Request Message
Country USA
Phone 678-475-3164
Date sent to CableLabs 5/21/14
EC REVISION HISTORY
Date of revised EC 5/21/14
Brief description of revision ATP impacts provided
DETAILED PROPOSED CHANGES
Sections Affected 6.4.5, 6.4.5.2, 6.4.28.1.12, 7.1.3.1, 10.2.3.5.2
REQs Affected Yes Test Plans Affected Yes
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_Spec-TestPlan_EC-Form_10-2013.docx
1 of 3
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:
When the CM is commanded to start using an upstream channel using the TCC initialization technique of “perform either broadcast or unicast ranging”, the type of Ranging Request message to send needs to be specified. When it receives this initialization technique, the CM is required to use the first ranging opportunity it sees. If the CM is initializing on a secondary channel and transmitting in a broadcast or unicast Initial Maintenance opportunity, the
CM is required to send an INIT-RNG-REQ message. If the CM is initializing on a secondary channel and transmitting in a Station Maintenance opportunity, the CM is required to send an RNG-REQ message. However, the CM may not be able to change the type of Ranging Request message based on the type of ranging opportunity it uses.
This EC proposes a simplification to which type of Ranging Request message should be sent when. Specifically, this proposal is as follows”

A DOCSIS 3.0 CM initializing on a DOCSIS 3.0 CMTS
 The CM always sends a B-INIT-RNG-REQ on the first channel on which it initializes.
 The CM sends RNG-REQ messages when initializing on secondary channels, regardless of the type of ranging opportunity
 The CM sends RNG-REQ messages in subsequent station maintenance opportunities.

A DOCSIS 3.0 CM initializing on a DOCSIS 2.0 CMTS
 The CM always sends an INIT-RNG-REQ on the first channel on which it initializes.
 The CM sends RNG-REQ messages when initializing on secondary channels, regardless of the type of ranging opportunity.
 The CM sends RNG-REQ messages in subsequent station maintenance opportunities.
CHANGE DETAILS FOR THE SPECIFICATION:
Complete Engineering Change details for the specification is contained in the following embedded file:
DOCSIS-SpecDetailC hanges.docx
D30 Ranging
Request Message.docx
DOCSIS_Spec-TestPlan_EC-Form_10-2013.docx
2 of 3
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.

CHANGE DETAILS FOR THE TEST PLAN (ATP):
Complete Engineering Change details for the test plan is contained in the following embedded file:
DOCSIS-TestPlanDet ailChanges.docx
End of Request
Additional Instructions to EC Author
Embed_Doc_TrkChg_
Instr.docx
DOCSIS_Spec-TestPlan_EC-Form_10-2013.docx
3 of 3
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.