I2RS Security Related Requirements
draft-ietf-i2rs-protocol-security-requirements-17

Document Type Active Internet-Draft (i2rs WG)
Last updated 2017-07-20 (latest revision 2016-09-29)
Replaces draft-hares-i2rs-auth-trans
Stream IETF
Intended RFC status Informational
Formats plain text pdf xml 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 Ed Queue
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
RFC Editor RFC Editor state EDIT
I2RS working group                                              S. Hares
Internet-Draft                                                    Huawei
Intended status: Informational                                D. Migault
Expires: April 2, 2017                                        J. Halpern
                                                                Ericsson
                                                      September 29, 2016

                   I2RS Security Related Requirements
           draft-ietf-i2rs-protocol-security-requirements-17

Abstract

   This presents security-related requirements for the I2RS protocol
   which provides a new interface to the routing system described in the
   I2RS architecture document (RFC7921).  The I2RS protocol is a re-use
   protocol implemented by re-using portions of existing IETF protocols
   and adding new features to these protocols.  The I2RS protocol re-
   uses security features of a secure transport (E.g.  TLS, SSH, DTLS)
   such as encryption, message integrity, mutual peer authentication,
   and replay protection.  The new I2RS features to consider from a
   security perspective are: a priority mechanism to handle multi-headed
   write transactions, an opaque secondary identifier which identifies
   an application using the I2RS client, and an extremely constrained
   read-only non-secure transport.  This document provides the detailed
   requirements for these security features.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 2, 2017.

Hares, et al.             Expires April 2, 2017                 [Page 1]
Internet-Draft         I2RS Security Requirements         September 2016

Copyright Notice

   Copyright (c) 2016 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
   (http://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.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     2.2.  Security Definitions  . . . . . . . . . . . . . . . . . .   4
     2.3.  I2RS Specific Definitions . . . . . . . . . . . . . . . .   5
   3.  Security Features and Protocols: Re-used and New  . . . . . .   7
     3.1.  Security Protocols Re-Used by the I2RS Protocol . . . . .   7
     3.2.  New Features Related to Security  . . . . . . . . . . . .   8
     3.3.  I2RS Protocol Security Requirements vs. IETF Management
           Protocols . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Security-Related Requirements . . . . . . . . . . . . . . . .  10
     4.1.  I2RS Peers(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 Transport and Insecure
           Transport . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.5.  Management Protocol Security  . . . . . . . . . . . . . .  15
     4.6.  Role-Based Data Model Security  . . . . . . . . . . . . .  16
     4.7.  Security of the environment . . . . . . . . . . . . . . .  17
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  18
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  19
Show full document text