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

The information below is for an old version of the document
Document Type Active Internet-Draft (i2rs WG)
Last updated 2016-05-20
Replaces draft-hares-i2rs-auth-trans
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jeffrey Haas
Shepherd write-up Show (last changed 2015-12-31)
IESG IESG state Publication Requested
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alia Atlas
Send notices to "Jeffrey Haas" <jhaas@pfrc.org>
I2RS working group                                              S. Hares
Internet-Draft                                                    Huawei
Intended status: Informational                                D. Migault
Expires: November 21, 2016                                    J. Halpern
                                                                Ericsson
                                                            May 20, 2016

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

Abstract

   This presents security-related requirements for the I2RS protocol for
   mutual authentication, transport protocols, data transfer and
   transactions.

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 November 21, 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.

Hares, et al.           Expires November 21, 2016               [Page 1]
Internet-Draft         I2RS Security Requirements               May 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Security Definitions  . . . . . . . . . . . . . . . . . .   3
     2.2.  I2RS Specific Definitions . . . . . . . . . . . . . . . .   6
   3.  Security-Related Requirements . . . . . . . . . . . . . . . .   7
     3.1.  Mutual authentication of an I2RS client and an I2RS Agent   8
     3.2.  Transport Requirements Based on Mutual Authentication . .   9
     3.3.  Data Confidentiality Requirements . . . . . . . . . . . .  10
     3.4.  Data Integrity Requirements . . . . . . . . . . . . . . .  10
     3.5.  Role-Based Data Model Security  . . . . . . . . . . . . .  11
     3.6.  Security of the environment . . . . . . . . . . . . . . .  12
   4.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  12
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The Interface to the Routing System (I2RS) provides read and write
   access to information and state within the routing process.  An I2RS
   client interacts with one or more I2RS agents to collect information
   from network routing systems.

   This document describes the requirements for the I2RS protocol in the
   security-related areas of mutual authentication of the I2RS client
   and agent, the transport protocol carrying the I2RS protocol
   messages, and the atomicity of the transactions.  These requirements
   align with the description of the I2RS architecture found in
   [I-D.ietf-i2rs-architecture] document which solves the problem
   described in [I-D.ietf-i2rs-problem-statement].

   [I-D.ietf-i2rs-ephemeral-state] discusses I2RS role-based access
   control that provides write conflict resolution in the ephemeral data
   store using the I2RS Client Identity, I2RS Secondary Identity and
   priority.  The draft [I-D.ietf-i2rs-traceability] describes the
   traceability framework and its requirements for I2RS.  The draft
   [I-D.ietf-i2rs-pub-sub-requirements] describes the requirements for
   I2RS to be able to publish information or have a remote client
   subscribe to an information data stream.

Hares, et al.           Expires November 21, 2016               [Page 2]
Show full document text