Accounting in NETCONF and RESTCONF
draft-mahesh-netconf-accounting-03

Document Type Active Internet-Draft (individual)
Last updated 2017-07-18
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 0 warnings.
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)
Network Working Group                                    M. Jethanandani
Internet-Draft                                        Cisco Systems, Inc
Intended status: Standards Track                           July 17, 2017
Expires: January 18, 2018

                   Accounting in NETCONF and RESTCONF
                   draft-mahesh-netconf-accounting-03

Abstract

   This document defines an accounting record for NETCONF and RESTCONF.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 January 18, 2018.

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

Jethanandani            Expires January 18, 2018                [Page 1]
Internet-Draft       NETCONF and RESTCONF Accounting           July 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Compatability with remote AAA servers . . . . . . . . . .   2
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Accounting Record . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Data Model Definitions  . . . . . . . . . . . . . . . . . . .   5
     3.1.  Data Organization . . . . . . . . . . . . . . . . . . . .   5
     3.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Appendix A.  Accounting model examples  . . . . . . . . . . . . .  12
     A.1.  <edit-config> Example for Accounting  . . . . . . . . . .  12
     A.2.  <get> Example for Accounting  . . . . . . . . . . . . . .  12
     A.3.  NACM rule for Accounting  . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   NETCONF [RFC6241] and RESTCONF [RFC8040] protocol operations are
   authenticated and authorized as part of the Authentication,
   Authorization and Accounting (AAA) framework.  An accounting record
   is generated as part of the same framework for each of these
   operations to satisfy the accounting part of AAA, but there has been
   no effort to define such a record.  Having an accounting record that
   is consistent across vendors allows for the operator to compare
   operations across devices from different vendors.  This document
   defines such a record and a corresponding YANG data model (ietf-
   netconf-am.yang).

   The rest of this document will use NETCONF to imply both NETCONF and
   RESTCONF, but where applicable will call out each protocol
   specifically.

1.1.  Compatability with remote AAA servers

   This document does not cover how the server interacts with remote AAA
   servers and any interaction is out of scope of this document.  A
   particular implementation can make the records available as part of
   <get> request, send a notification every time a accounting record is
Show full document text