Interface to the Routing System (I2RS) Security-Related Requirements
RFC 8241

Document Type RFC - Informational (September 2017; No errata)
Last updated 2017-09-15
Replaces draft-hares-i2rs-auth-trans
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 Jeffrey Haas
Shepherd write-up Show (last changed 2015-12-31)
IESG IESG state RFC 8241 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to "Jeffrey Haas" <jhaas@pfrc.org>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                          S. Hares
Request for Comments: 8241                                        Huawei
Category: Informational                                       D. Migault
ISSN: 2070-1721                                               J. Halpern
                                                                Ericsson
                                                          September 2017

  Interface to the Routing System (I2RS) Security-Related Requirements

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.

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/rfc8241.

Hares, et al.                 Informational                     [Page 1]
RFC 8241               I2RS Security 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
   2. Terminology and Concepts ........................................4
      2.1. Requirements Language ......................................4
      2.2. Security Terminology .......................................4
      2.3. I2RS-Specific Terminology ..................................5
      2.4. Concepts ...................................................5
   3. Security Features and Protocols: Reused and New .................6
      3.1. Security Protocols Reused by the I2RS Protocol .............6
      3.2. New Features Related to Security ...........................7
      3.3. I2RS Protocol Security Requirements vs. IETF
           Management Protocols .......................................8
   4. Security-Related Requirements ..................................10
      4.1. I2RS Peer (Agent and Client) Identity Authentication ......10
      4.2. Identity Validation before Role-Based Message Actions .....11
      4.3. Peer Identity, Priority, and Client Redundancy ............12
      4.4. Multi-Channel Transport: Secure and Non-Secure ............13
      4.5. Management Protocol Security ..............................15
      4.6. Role-Based Data Model Security ............................16
      4.7. Security of the Environment ...............................17
   5. IANA Considerations ............................................17
   6. Security Considerations ........................................17
   7. References .....................................................18
      7.1. Normative References ......................................18
      7.2. Informative References ....................................18
   Acknowledgements ..................................................20
   Authors' Addresses ................................................20
Show full document text