Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

S. Hares
D. Migault
J. Halpern

Stream:

IETF

Source:

i2rs (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8241

Discuss this RFC: Send questions or comments to the mailing listi2rs@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8241

Abstract

This document presents security-related requirements for theInterface to the Routing System (I2RS) protocol, which provides a newinterface to the routing system described in the I2RS architecturedocument (RFC 7921). The I2RS protocol is implemented by reusingportions 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, mutualpeer authentication, and anti-replay protection. The new I2RSfeatures to consider from a security perspective are as follows: apriority mechanism to handle multi-headed write transactions, anopaque secondary identifier that identifies an application using theI2RS client, and an extremely constrained read-only non-securetransport.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.