Internet Gateway Device Data Model for TR-069

1 TECHNICAL REPORT The Broadband Forum. All rights reserved. TR-098 Internet Gateway Device data Model for TR-069 Issue: 1 Amendment 2 Issue Date: September 2008 Internet Gateway Device data Model for TR-069 TR-098 Amendment 2 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Broadband Forum Technical Report has been approved by members of the Forum. This Broadband Forum Technical Report is not binding on the Broadband Forum, any of its members, or any developer or service provider. This Broadband Forum Technical Report is subject to change, but only with approval of members of the Forum.

2 This Broadband Forum Technical Report is provided "as is," with all faults. Any person holding a copyright in this Broadband Forum Technical Report, or any portion thereof, disclaims to the fullest extent permitted by law any representation or warranty, express or implied, including, but not limited to (a) any warranty of merchantability, fitness for a particular purpose, non-infringement, or title; (b) any warranty that the contents of this Broadband Forum Technical Report are suitable for any purpose, even if that purpose is known to the copyright holder; (c) any warranty that the implementation of the contents of the documentation will not infringe any third party patents, copyrights, trademarks or other rights.

3 This Broadband Forum publication may incorporate intellectual property. The Broadband Forum encourages but does not require declaration of such intellectual property. For a list of declarations made by Broadband Forum member companies, please see Broadband Forum Technical Reports may be copied, downloaded, stored on a server or otherwise re-distributed in their entirety only. The text of this notice must be included in all copies. September 2008 The Broadband Forum. All rights reserved. 2 Internet Gateway Device data Model for TR-069 TR-098 Amendment 2 Issue History Issue Number Issue Date Issue Editor Changes Issue 1 September 2005 Jeff Bernstein, 2 Wire Barbara Stark, BellSouth Issue 1 Issue 1 Amendment 1 November 2006 Jeff Bernstein, 2 Wire John Blackford, 2 Wire Mike Digdon, SupportSoft Heather Kirksey, Motive William Lupton, 2 Wire Anton Okmianski, Cisco Clarification of original document Issue 1 Amendment 2 September 2008 Christele Bouchat, Alcatel William Lupton, 2 Wire Clarification of Amendment 1.

4 data Model extensions ( ); See section 1 for further details Technical comments or questions about this Technical Report should be directed to: Editors William Lupton 2 Wire Christele Bouchat Alcatel-Lucent DSLHome Technical Working Group Chairs Greg Bathrick PMC-Sierra Heather Kirksey Motive September 2008 The Broadband Forum. All rights reserved. 3 Internet Gateway Device data Model for TR-069 TR-098 Amendment 2 Table of Contents 1 Introduction .. 10 11 Document Conventions .. 12 2 data Model Definition .. 12 General Notation.

5 12 data Types .. 12 Vendor-Specific Parameters .. 14 InternetGatewayDevice data Model .. 15 Inform and Notification Requirements ..158 Version data Model Requirements ..169 3 Profile Definitions ..170 Notation ..170 Baseline Profile ..170 EthernetLAN Profile ..175 USBLAN Profile ..176 WiFiLAN Profile ..177 WiFiWMM Profile ..178 WiFiWPS Profile ..179 ADSLWAN Profile ..179 ADSL2 WAN Profile ..181 VDSL2 WAN Profile ..182 PTMWAN Profile ..184 EthernetWAN Profile ..185 POTSWAN Profile ..185 QoS Profile ..186 QoSDynamicFlow Profile ..188 QoSStats Profile ..189 Bridging Profile ..190 BridgingPortVLAN Profile.

6 191 Time Profile ..191 CaptivePortal Profile ..192 IPPing TraceRoute Profile ..193 Download Profile ..193 DownloadTCP Profile ..194 Upload Profile ..194 UploadTCP Profile ..195 UDPEcho Profile ..195 UDPEchoPlus Profile ..195 ATML oopback Profile ..195 DSLD iagnostics Profile ..196 ADSL2 DSLD iagnostics Profile ..196 VDSL2 DSLD iagnostics Profile ..197 DeviceAssociation Profile ..198 UDPConnReq Profile ..198 DHCPCondServing Profile ..199 DHCPO ption Profile ..199 Normative References ..201 Annex A. Queuing and Bridging ..203 Queuing and Bridging Model ..203 Packet Classification ..203 Policing ..206 Queuing and Scheduling.

7 206 Bridging ..207 Default Layer 2/3 QoS Mapping ..209 URN Definitions for App and Flow Tables ..210 ProtocolIdentifier ..210 FlowType ..210 September 2008 The Broadband Forum. All rights reserved. 4 Internet Gateway Device data Model for TR-069 TR-098 Amendment 2 FlowTypeParameters ..211 Example Queuing Architecture for RG (from TR-059) ..211 Layer2 Bridging Use Case: Interface Based Bridging ..213 Relationship between Layer2 Bridging and LAND evice / WAN**Connection ..213 Populating the data Model on Reboot ..214 Updating the data Model on Configuration Changes.

8 215 Bridging Behavior when Layer2 Bridging is not Implemented ..215 Case Studies ..215 Annex B. LinkType and ConnectionType Interdependencies ..218 Appendix I. Managed bridge configuration in a multi-PVC scenario ..220 Description of scenario ..220 Network Traffic Classes and Priorities ..220 Mapping to PVCs ..221 Example Configuration ..222 IGD WAN Connection Device Definitions ..223 IGD Default Queue Definitions ..224 IGD Upstream Classification definitions ..224 IGD Upstream Queue definitions ..225 IGD DHCP Server ..226 IGD DHCP Conditional Serving Pool ..226 Appendix II. Use of the Bridging Objects for VLAN Tagging ..228 Tagged LAN to tagged WAN traffic (VLAN bridging).

9 230 Tagged LAN to tagged WAN traffic (special case with VLAN ID translation) ..231 Untagged LAN to tagged WAN traffic ..233 Internally generated to tagged WAN traffic ..236 Other issues ..237 More than one LAN interface in a bridge ..237 (re-)marking ..237 More than one VLAN ID tag admitted on the same LAN interface ..238 September 2008 The Broadband Forum. All rights reserved. 5 Internet Gateway Device data Model for TR-069 TR-098 Amendment 2 List of Figures Figure 1 Positioning in the End-to-End Architecture .. 10 Figure 2 Queuing Model of an Internet Gateway Device .

10 203 Figure 3 Queuing and Scheduling Example for RG ..212 Figure 4 Example of interface-based bridging ..213 Figure 5 WAN / LAN bridged example ..216 Figure 6 WAN / LAN routed example ..216 Figure 7 Triple Play Service ..220 Figure 8 Triple Play Upstream Priorities ..221 Figure 9 IGD Physical Ingress/Egress Interfaces Block Diagram ..222 Figure 10 IGD Upstream data Model Diagram ..223 Figure 11 Examples of VLAN configuration based on Layer2 Bridging ..229 Figure 12 Example of VLAN configuration in a 2 box scenario ..238 September 2008 The Broadband Forum. All rights reserved. 6 Internet Gateway Device data Model for TR-069 TR-098 Amendment 2 List of Tables Table 1 data types.