2 References

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

2.1 Normative references

References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) appliesThe following referenced documents are necessary, partially or totally, for the application of the present document. Their use in the context of this TS is specified by the normative statements that are referring back to this clause.

~~The following referenced documents are necessary for the application of the present document.~~

[1] oneM2M TS-0001: "Functional Architecture".

[2] oneM2M TS-0004: "Service Layer Core Protocol Specification".

[3] oneM2M TS-0011: "Common Terminology".

[4] BBF: "TR-069 CPE WAN Management Protocol", Issue: 1 Amendment 5, November 2013.

[5] BBF: "TR-106 Data Model Template for TR-069-Enabled Devices", Issue 1, Amendment 7, September 2013.

[6] BBF: "TR-181 Device Data Model for TR-069, Issue 2 Amendment 11", July 2016.

[7] BBF: "TR-131 ACS Northbound Interface Requirements, Issue:1", November 2009.

[8] oneM2M TS-0022: "Field Device Configuration".

2.2 Informative references

The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.

[i.1] oneM2M Drafting Rules.

NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.