DATA MODEL DEFINITION
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The above license is used as a license under copyright only. Please reference the Forum IPR Policy for patent licensing terms <https://www.broadband-forum.org/ipr-policy>.
Any moral rights which are necessary to exercise under the above license grant are also deemed granted under this license.
The Parameters defined in this specification make use of a limited subset of the default SOAP data types [SOAP1.1]. These data types and the named data types used by this specification are described below.
Note: A Parameter that is defined to be one of the named data types is reported as such at the beginning of the Parameter's description via a reference back to the associated data type definition (e.g. [MacAddress]). However, such parameters still indicate their SOAP data type.
|Data Type||Base Type||Description|
Base64 encoded binary (no line-length limitation).
A minimum and maximum allowed length can be indicated using the form base64(Min:Max), where Min and Max are the minimum and maximum length in characters before Base64 encoding. If either Min or Max are missing, this indicates no limit, and if Min is missing the colon can also be omitted, as in base64(Max). Multiple comma-separated ranges can be specified, in which case the length MUST be in one of the ranges.
|boolean||-||Boolean, where the allowed values are 0 or 1 (or equivalently, true or false).|
|dateTime||-||The subset of the ISO 8601 date-time format defined by the SOAP dateTime type.|
Integer in the range -2147483648 to +2147483647, inclusive.
For some int types, a value range is given using the form int[Min:Max] or int[Min:Max step Step] where the Min and Max values are inclusive. If either Min or Max are missing, this indicates no limit. If Step is missing, this indicates a step of 1. Multiple comma-separated ranges can be specified, in which case the value will be in one of the ranges.
|string||-||For strings, a minimum and maximum allowed length can be indicated using the form string(Min:Max), where Min and Max are the minimum and maximum string length in characters. If either Min or Max are missing, this indicates no limit, and if Min is missing the colon can also be omitted, as in string(Max). Multiple comma-separated ranges can be specified, in which case the string length will be in one of the ranges.|
Unsigned integer in the range 0 to 4294967295, inclusive.
For some unsignedInt types, a value range is given using the form unsignedInt[Min:Max] or unsigned[Min:Max step Step], where the Min and Max values are inclusive. If either Min or Max are missing, this indicates no limit. If Step is missing, this indicates a step of 1. Multiple comma-separated ranges can be specified, in which case the value will be in one of the ranges.
IP address, i.e. IPv4 address (or IPv4 subnet mask) or IPv6 address.
All IPv4 addresses and subnet masks MUST be represented as strings in IPv4 dotted-decimal notation. Here are some examples of valid IPv4 address textual representations:
All IPv6 addresses MUST be represented using any of the 3 standard textual representations defined in [RFC4291] Sections 2.2.1, 2.2.2 and 2.2.3. Both lower-case and upper-case letters can be used, but use of lower-case letters is RECOMMENDED. Here are some examples of valid IPv6 address textual representations:
IPv6 addresses MUST NOT include zone identifiers. Zone identifiers are discussed in [Section 6/RFC4007].
Unspecified or inapplicable addresses (or IPv4 subnet masks) MUST be represented as empty strings unless otherwise specified by the parameter definition.
All MAC addresses are represented as strings of 12 hexadecimal digits (digits 0-9, letters A-F or a-f) displayed as six pairs of digits separated by colons. Unspecified or inapplicable MAC addresses MUST be represented as empty strings unless otherwise specified by the parameter definition. Possible patterns:
|[802.1D-2004]||IEEE Std 802.1D-2004, Media Access Control (MAC) Bridges, IEEE, 2004.|
|[802.1Q-2005]||IEEE Std 802.1Q-2005, Virtual Bridged Local Area Networks, IEEE, 2006.|
|[RFC862]||RFC 862, Echo Protocol, IETF, 1983.|
|[RFC2131]||RFC 2131, Dynamic Host Configuration Protocol, IETF.|
|[RFC2132]||RFC 2132, DHCP Options and BOOTP Vendor Extensions, IETF.|
|[RFC2225]||RFC 2225, Classical IP and ARP over ATM, IETF.|
|[RFC2474]||RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, IETF.|
|[RFC2516]||RFC 2516, A Method for Transmitting PPP Over Ethernet (PPPoE), IETF.|
|[RFC2616]||RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1, IETF, 1999.|
|[RFC2634]||RFC 2634, Enhanced Security Services for S/MIME, IETF.|
|[RFC2662]||RFC 2662, Definitions of Managed Objects for the ADSL Lines, IETF.|
|[RFC2684]||RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5, IETF.|
|[RFC2697]||RFC 2697, A Single Rate Three Color Marker, IETF.|
|[RFC2698]||RFC 2698, A Two Rate Three Color Marker, IETF.|
|[RFC2898]||RFC 2898, PKCS #5: Password-Based Cryptography Specification Version 2.0, IETF.|
|[RFC3004]||RFC 3004, The User Class Option for DHCP, IETF.|
|[RFC3066]||RFC 3066, Tags for the Identification of Languages, IETF.|
|[RFC3925]||RFC 3925, Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4), IETF.|
|[RFC3986]||RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, IETF.|
|[RFC4122]||RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace, IETF, 2005.|
|[SOAP1.1]||Simple Object Access Protocol (SOAP) 1.1, W3C.|
|[TR-069a2]||TR-069 Amendment 2, CPE WAN Management Protocol, Broadband Forum, December 2007.|
|[TR-098a2]||TR-098 Amendment 2, Internet Gateway Device Data Model for TR-069, Broadband Forum, September 2008.|
|[TR-106a1]||TR-106 Amendment 1, Data Model Template for TR-069-Enabled Devices, Broadband Forum, November 2006.|
|[WPSv1.0]||Wi-Fi Protected Setup Specification Version 1.0h, Wi-Fi Alliance, 2006.|
For a given implementation of this data model, the Agent MUST indicate support for the highest version number of any object or parameter that it supports. For example, even if the Agent supports only a single parameter that was introduced in version 1.4, then it will indicate support for version 1.4. The version number associated with each object and parameter is shown in the Version column.