TR-106 1 - Issue 1 Amendment 11

Sep 2, 2026

Upload by Đào

Compilation of updates for TR-106 Issue 1, capturing the evolution of schema and device-related definitions across amendments. Includes clarifications and editorial improvements, additions such as device type XML schema support, and transitions like moving data model definitions to TR-181 Issue 1 and relocating device requirements to TR-069. Later amendments expand USP (mountable objects) support, introduce new description and template capabilities, and clarify forcedEnabled/forceDefaultEnabled semantics and the effects of deprecating or obsoleting profile items.

LanguageEnglish

CategoryGeneral

FormatPDF

Pages111

Reading Time39 min

AccessFree to download

Issue 1

Issue 1 Amendments (1-11)

| | | | | | | --- | --- | --- | --- | --- | | Issue 1 | September 2005 | | Jeff
Bernstein ,
2Wire
Christele
Bouchat ,
Alcatel
Tim Spets ,
Westell | Original | | Issue 1 Amendment 1 | November 2006 | | Jeff
Bernstein ,
2Wire
John
Blackford ,
2Wire
Mike
Digdon , SupportSoft
Heather
Kirksey ,
Motive
William
Lupton ,
2Wire
Anton
Okmianski ,
Cisco | Clarification of original document | | Issue 1 Amendment 2 | November 2008 | | William
Lupton , 2Wire Håkan
Westin ,
Tilgin | Addition of data model definition XML Schema and normative XML common object and component
definitions | | | | | | | | --- | --- | --- | --- | --- | | Issue 1 Amendment 3 | September 2009 | | William
Lupton , 2Wire Håkan
Westin ,
Tilgin | Addition of device type XML Schema | | Issue 1 Amendment 4 | February 2010 | | William
Lupton ,
2Wire
Paul
Sigurdson ,
Broadband
Forum | Moved data model definitions to TR-181 Issue 1 | | Issue 1 Amendment 5 | November 2010 | | Paul
Sigurdson ,
Broadband Forum | Replaced definitions of named data types such as IPAddress with references to normative XML.
Minor changes to DM Schema (v1 .3) and DT
Schema (v1 . 1) . | | Issue 1 Amendment 6 | July 2011 | | Sarah
Banks ,
Cisco
Andrea
Colmegna ,
FASTWEB
Tim Spets ,
Motorola
Mobility | Removed definition of proxying , now defined in TR- 069.
Removed Common objects. Alias Parameter
Requirements added. | | Issue 1 Amendment 7 | September 2013 | 7 October 2013 | William
Lupton , Cisco | Added descriptions of new features in DM Schema (v1 .4 & v1 .5) and DT Schema (v1 .2 & v1 .3) .
Added Annex defining additional requirements for BBF standard data models. | | | | | | | | --- | --- | --- | --- | --- | | Issue 1 Amendment 8 | 16 March 2018 | 10 May 2018 | Jean-Didier
Ott , Orange
William
Lupton ,
Broadband
Forum | Added support of USP (mountable objects) . Removed references to obsolete data models. Moved device requirements to TR-069 . | | Issue 1 Amendment 9 | | | | Schema updates; document not updated. | | Issue 1 Amendment 10 | 5 November 2020 | 5 November 2020 | William Lupton , Broadband Forum | Converted document to markdown.
Various editorial
improvements. | | Issue 1 Amendment 11 | 27
January 2022 | 27 January 2022 | William Lupton , Broadband Forum | Clarified forcedEnabled and forceDefaultEnabled for USP. Clarified impact of deprecating or obsoleting profile items.
Documented new description templates.
Documented new secured attribute. |

FAQs

What does TR-106 Issue 1 Amendment 11 clarify?

It clarifies forcedEnabled and forceDefaultEnabled for USP, and clarifies the impact when profile items are deprecated or obsoleted.

Which kinds of technical changes were introduced in earlier amendments?

Earlier amendments added or modified XML schema definitions, such as data model and device type schema, and replaced or referenced normative XML definitions for named data types.

How did the document scope change over time?

Several requirements and definitions were moved to other specifications, including moving data model definitions to TR-181 Issue 1 and moving device requirements to TR-069, while obsolete data model references were removed.

Sep 2, 2026

Upload by Đào