I2RS Security Related Requirements
draft-hares-i2rs-auth-trans-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-07-03
Replaced by draft-ietf-i2rs-protocol-security-requirements, rfc8241
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
I2RS working group                                              S. Hares
Internet-Draft                                                    Huawei
Intended status: Standards Track                              D. Migault
Expires: January 4, 2016                                      J. Halpern
                                                                Ericsson
                                                            July 3, 2015

                   I2RS Security Related Requirements
                     draft-hares-i2rs-auth-trans-04

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 January 4, 2016.

Copyright Notice

   Copyright (c) 2015 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 January 4, 2016                [Page 1]
Internet-Draft         I2RS Security Requirements              July 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Security-Related Requirements . . . . . . . . . . . . . . . .   4
     2.1.  Mutual authentication of I2RS client and I2RS Agent . . .   4
     2.2.  Transport Requirements Based on Mutual Authentication . .   5
     2.3.  Data Confidentiality Requirements . . . . . . . . . . . .   5
     2.4.  Message Integrity Requirements  . . . . . . . . . . . . .   5
       2.4.1.  Handling Multiple Messages  . . . . . . . . . . . . .   6
     2.5.  Role-Based Data Model Security  . . . . . . . . . . . . .   6
   3.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The Interface to the Routing System (I2RS) provides read and write
   access to information and state within the routing process.  The 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
   were initially described in the [I-D.ietf-i2rs-architecture]
   document.

   [I-D.haas-i2rs-ephemeral-state-reqs] discusses I2RS roles-based 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.

1.1.  Definitions

   This document utilizes the definitions found in the following drafts:
   [RFC4949], and [I-D.ietf-i2rs-architecture]

   Specifically, this document utilizes the following definitions:

Hares, et al.            Expires January 4, 2016                [Page 2]
Internet-Draft         I2RS Security Requirements              July 2015

   Authentication

      [RFC4949] describes authentication as the process of verifying
Show full document text