# do not edit! this file was created from PROJECT.yaml by project-parser.py

# BBF-specific metadata; cf. Word properties
bbfNumber: TR-181
bbfTitle: Device Data Model for CWMP Endpoints and USP Agents
bbfIssue: Issue
bbfVersion: 1 Amendment 7
bbfMonth: November
bbfYear: 2015
bbfType: Technical Report
bbfStatus: DEPRECATED
bbfContrib: ''
bbfMajor: 1
bbfMinor: 7
bbfPatch: 0
bbfMicro: 0
bbfExtra: 0
bbfDraft: ''
bbfBuild: ''

# other top-level variables
notice: tr
reponame: device-data-model
website: https://device-data-model.broadband-forum.org
"tagline": |-
  TR-181 Documentation and Theory of Operations
"summary": |
  See <https://device-data-model.broadband-forum.org> for the
  current TR-181 specification.
"description": |
  TR-181 Issue 2 defines version 2 of the Device data model (Device:2). The
  Device:2 data model applies to all types of TR-069 or USP enabled devices,
  including End Devices, Residential Gateways, and other Network Infrastructure
  Devices.

  The Device:2 data model defined in this Technical Report consists of a set of
  data objects covering things like basic device information, time-of-day configuration,
  network interface and protocol stack configuration, routing and bridging management,
  throughput statistics, and diagnostic tests. It also defines a baseline profile that
  specifies a minimum level of data model support.

  The cornerstone of the Device:2 data model is the interface stacking mechanism. Network
  interfaces and protocol layers are modeled as independent data objects that can be stacked,
  one on top of the other, into whatever configuration a device might support.
bbfWorkArea: ''
bbfProjectStream: ''