Dismiss
InnovationQ will be updated on Sunday, Jan. 21, from 9am - 11am ET. You may experience brief service interruptions during that time.
Browse Prior Art Database

Service Models Explained (RFC8309)

IP.com Disclosure Number: IPCOM000252461D
Original Publication Date: 2018-Jan-01
Included in the Prior Art Database: 2018-Jan-13
Document File: 46 page(s) / 54K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Q. Wu: AUTHOR [+3]

Abstract

In recent years, the number of modules written in the YANG modeling language [RFC6020] for configuration and monitoring has blossomed. Many of these are used for device-level configuration (for example, [RFC7223]) or for control of monolithic functions or protocol instances (for example, [RFC7407]).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                             Q. Wu Request for Comments: 8309                                        W. Liu Category: Informational                              Huawei Technologies ISSN: 2070-1721                                                A. Farrel                                                         Juniper Networks                                                             January 2018

                         Service Models Explained

Abstract

   The IETF has produced many modules in the YANG modeling language.    The majority of these modules are used to construct data models to    model devices or monolithic functions.

   A small number of YANG modules have been defined to model services    (for example, the Layer 3 Virtual Private Network Service Model    (L3SM) produced by the L3SM working group and documented in RFC    8049).

   This document describes service models as used within the IETF and    also shows where a service model might fit into a software-defined    networking architecture.  Note that service models do not make any    assumption of how a service is actually engineered and delivered for    a customer; details of how network protocols and devices are    engineered to deliver a service are captured in other modules that    are not exposed through the interface between the customer and the    provider.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    https://www.rfc-editor.org/info/rfc8309.

 Wu, et al.                    Informational                     [Page 1]
 RFC 8309                Service Models Explained            January 2018

 Copyright Notice

   Copyright (c) 2018 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    (https://trustee.ietf.org/license-info) in effect on the date of    publication of this d...