YANG Models Required for Managing Residential Gateway (RG) Devices
draft-faq-netmod-cpe-yang-profile-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Replaces draft-faq-anima-cpe-yang-profile
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NETMOD WG                                                      I. Farrer
Internet-Draft                                                    Q. Sun
Intended status: Informational                                  S. Zoric
Expires: September 14, 2017                          Deutsche Telekom AG
                                                          M. Abrahamsson
                                                               T-Systems
                                                          March 13, 2017

   YANG Models Required for Managing Residential Gateway (RG) Devices
                  draft-faq-netmod-cpe-yang-profile-01

Abstract

   This document collects together the set of YANG models necessary for
   managing NETCONF-enabled Residential Gateway (RG) devices.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 14, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Farrer, et al.         Expires September 14, 2017               [Page 1]
Internet-Draft           RG YANG Device Profile               March 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Management Requirements . . . . . . . . . . . . . . . . . . .   3
     3.1.  General Requirements  . . . . . . . . . . . . . . . . . .   3
       3.1.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Development Status of Relevant YANG Models  . . . . .   4
     3.2.  Interfaces  . . . . . . . . . . . . . . . . . . . . . . .   4
       3.2.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   4
       3.2.2.  Development Status of Relevant YANG Models  . . . . .   5
     3.3.  IP Management . . . . . . . . . . . . . . . . . . . . . .   5
       3.3.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   5
       3.3.2.  Development Status of Relevant YANG Models  . . . . .   6
     3.4.  Routing and Multicast Management  . . . . . . . . . . . .   6
       3.4.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   6
       3.4.2.  Development of Relevant YANG Models . . . . . . . . .   6
     3.5.  RG NETCONF Server Management  . . . . . . . . . . . . . .   7
       3.5.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   7
       3.5.2.  Development Status of Relevant YANG Models  . . . . .   7
     3.6.  DHCP/SLAAC/ND Management  . . . . . . . . . . . . . . . .   7
       3.6.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   7
       3.6.2.  Development Status of Relevant YANG Models  . . . . .   8
     3.7.  NAT Management  . . . . . . . . . . . . . . . . . . . . .   8
       3.7.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   8
       3.7.2.  Development Status of Relevant YANG Models  . . . . .   9
     3.8.  IPv6 Transition Mechanisms Management . . . . . . . . . .   9
       3.8.1.  Requirements  . . . . . . . . . . . . . . . . . . . .   9
       3.8.2.  Development of Relevant YANG Models . . . . . . . . .   9
     3.9.  Management of Specific Services . . . . . . . . . . . . .  10
       3.9.1.  Requirements  . . . . . . . . . . . . . . . . . . . .  10
       3.9.2.  Development of Relevant YANG Models . . . . . . . . .  10
     3.10. Management of Security Components . . . . . . . . . . . .  10
       3.10.1.  Requirements . . . . . . . . . . . . . . . . . . . .  10
       3.10.2.  Development of Relevant YANG Models  . . . . . . . .  11
     3.11. Remote RG Software Upgrade  . . . . . . . . . . . . . . .  11
Show full document text