Interface to the Routing System (I2RS) Ephemeral State Requirements
RFC 8242
|
| Document |
Type |
|
RFC - Informational
(September 2017; No errata)
|
|
Last updated |
|
2017-09-15
|
|
Replaces |
|
draft-haas-i2rs-ephemeral-state-reqs
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
(wg milestone:
Aug 2016 - Request publication ...
)
|
|
Document shepherd |
|
Joe Clarke
|
|
Shepherd write-up |
|
Show
(last changed 2016-09-22)
|
| IESG |
IESG state |
|
RFC 8242 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alia Atlas
|
|
Send notices to |
|
"Joe Clarke" <jclarke@cisco.com>
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
No IANA Actions
|
Internet Engineering Task Force (IETF) J. Haas
Request for Comments: 8242 Juniper
Category: Informational S. Hares
ISSN: 2070-1721 Huawei
September 2017
Interface to the Routing System (I2RS) Ephemeral State Requirements
Abstract
"An Architecture for the Interface to the Routing System" (RFC 7921)
abstractly describes a number of requirements for ephemeral state (in
terms of capabilities and behaviors) that any protocol suite
attempting to meet the needs of the Interface to the Routing System
(I2RS) protocol has to provide. This document describes, in detail,
requirements for ephemeral state for those implementing the I2RS
protocol.
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/rfc8242.
Haas & Hares Informational [Page 1]
RFC 8242 I2RS Ephemeral State Requirements September 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
(https://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.
Table of Contents
1. Introduction ....................................................3
1.1. Requirements Language ......................................4
2. Architectural Requirements for Ephemeral State ..................4
3. Ephemeral State Requirements ....................................5
3.1. Persistence ................................................5
3.2. Constraints ................................................6
3.3. Hierarchy ..................................................6
3.4. Ephemeral Configuration Overlapping Local Configuration ....6
4. YANG Features for Ephemeral State ...............................7
5. NETCONF Features for Ephemeral State ............................7
6. RESTCONF Features for Ephemeral State ...........................7
7. Requirements regarding Supporting Multi-Head Control via
Client ..........................................................7
8. Multiple Message Transactions ...................................9
9. Pub/Sub Requirements Expanded for Ephemeral State ...............9
10. IANA Considerations ...........................................10
11. Security Considerations .......................................10
12. Normative References ..........................................10
Acknowledgements ..................................................12
Authors' Addresses ................................................12
Haas & Hares Informational [Page 2]
RFC 8242 I2RS Ephemeral State Requirements September 2017
1. Introduction
The Interface to the Routing System (I2RS) Working Group (WG) is
chartered with providing architecture and mechanisms to inject into
and retrieve information from the routing system. The I2RS
Architecture document [RFC7921] abstractly documents a number of
requirements for implementing the I2RS and defines ephemeral state as
"state that does not survive the reboot of a routing device or the
reboot of the software handling the I2RS software on a routing
device" (see Section 1.1 of [RFC7921]). Section 2 of this document
describes the specific requirements that the I2RS WG has identified
based on the I2RS architecture's abstract requirements. The
Interface to the Routing System (I2RS) Working Group (WG) is
chartered with providing architecture and mechanisms to inject into
and retrieve information from the routing system. The I2RS
Architecture document [RFC7921] abstractly documents a number of
Show full document text