Interface to the Routing System Security-Related Requirements
RFC 8241, “Interface to the Routing System Security-Related Requirements”, is an Informational document published in September 2017 by S. Hares, D. Migault, J. Halpern. The canonical text is published by the RFC Editor.
Abstract
This document presents security-related requirements for the Interface to the Routing System (I2RS) protocol, which provides a new interface to the routing system described in the I2RS architecture document (RFC 7921). The I2RS protocol is implemented by reusing portions of existing IETF protocols and adding new features to them. One such reuse is of the security features of a secure transport (e.g., Transport Layer Security (TLS), Secure SHell (SSH) Protocol, Datagram TLS (DTLS)) such as encryption, message integrity, mutual peer authentication, and anti-replay protection. The new I2RS features to consider from a security perspective are as follows: a priority mechanism to handle multi-headed write transactions, an opaque secondary identifier that identifies an application using the I2RS client, and an extremely constrained read-only non-secure transport.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8241 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8240 Report from the Internet of Things Software Update Workshop 2016
- RFC 8242 Interface to the Routing System Ephemeral State Requirements
- RFC 8239 Data Center Benchmarking Methodology
- RFC 8243 Alternatives for Multilevel Transparent Interconnection of Lots of Links
- RFC 8238 Data Center Benchmarking Terminology
- RFC 8244 Special-Use Domain Names Problem Statement
- RFC 8237 MPLS Label Switched Path Pseudowire Status Refresh Reduction for Static PWs
- RFC 8245 Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444