RFC 8309: Service Models Explained
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8309
- Published
- January 2018
- Authors
- Q. Wu; W. Liu; A. Farrel
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8342Network Management Datastore Architecture (NMDA)Updated
March 2018
- RFC 6991Common YANG Data TypesObsoleted
July 2013
- RFC 8515URN Namespace for ETSI DocumentsCurrent
February 2019
- RFC 9243A YANG Data Model for DHCPv6 ConfigurationCurrent
June 2022
- RFC 9403A YANG Data Model for RIB ExtensionsCurrent
November 2023
- RFC 8349A YANG Data Model for Routing Management (NMDA Version)Current
March 2018
- RFC 8407Guidelines for Authors and Reviewers of Documents Containing YANG Data ModelsObsoleted
October 2018
- RFC 8040RESTCONF ProtocolUpdated
January 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?