I2RS Environment Security Requirements
draft-ietf-i2rs-security-environment-reqs-04

Document Type Active Internet-Draft (i2rs WG)
Last updated 2017-03-12
Replaces draft-mglt-i2rs-security-environment-reqs
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
Reviews
Stream WG state WG Document Aug 2016
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
I2RS WG                                                       D. Migault
Internet-Draft                                                J. Halpern
Intended status: Informational                                  Ericsson
Expires: September 13, 2017                                     S. Hares
                                                                  Huawei
                                                          March 12, 2017

                 I2RS Environment Security Requirements
              draft-ietf-i2rs-security-environment-reqs-04

Abstract

   This document provides environment security requirements for the I2RS
   architecture.  Environment security requirements are independent of
   the protocol used for I2RS.  The security environment requirements
   are the good security practices to be used during implementation and
   deployment of the code related to the new interface to routing system
   (I2RS) so that I2RS implementations can be securely deployed and
   operated.

   Environmental security requirements do not specify the I2RS protocol
   seecurity requirements.  This is done in another document (draft-
   ietf-i2rs-protocol-security-requirements).

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 September 13, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Migault, et al.        Expires September 13, 2017               [Page 1]
Internet-Draft   I2RS Environment Security Requirements       March 2017

   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.  Terminology and Acronyms  . . . . . . . . . . . . . . . . . .   4
     2.1.  Requirements notation . . . . . . . . . . . . . . . . . .   4
   3.  I2RS Plane Isolation  . . . . . . . . . . . . . . . . . . . .   4
     3.1.  I2RS Plane and Management plane . . . . . . . . . . . . .   5
       3.1.1.  Deadlocks . . . . . . . . . . . . . . . . . . . . . .   6
       3.1.2.  Data Store leaking  . . . . . . . . . . . . . . . . .   7
     3.2.  I2RS Plane and Forwarding Plane . . . . . . . . . . . . .  10
     3.3.  I2RS Plane and Control Plane  . . . . . . . . . . . . . .  11
     3.4.  Requirements  . . . . . . . . . . . . . . . . . . . . . .  11
   4.  I2RS Access Control for Routing System Resources  . . . . . .  14
     4.1.  I2RS Access Control Architecture  . . . . . . . . . . . .  14
       4.1.1.  Access control Enforcement Scope  . . . . . . . . . .  17
       4.1.2.  Notification Requirements . . . . . . . . . . . . . .  17
       4.1.3.  Trust . . . . . . . . . . . . . . . . . . . . . . . .  18
       4.1.4.  Sharing access control Information  . . . . . . . . .  18
       4.1.5.  Sharing Access Control in Groups of I2RS Clients and
               Agents  . . . . . . . . . . . . . . . . . . . . . . .  20
       4.1.6.  Managing Access Control Policy  . . . . . . . . . . .  22
     4.2.  I2RS Agent Access Control Policies  . . . . . . . . . . .  23
       4.2.1.  I2RS Agent Access Control . . . . . . . . . . . . . .  23
       4.2.2.  I2RS Client Access Control Policies . . . . . . . . .  24
       4.2.3.  Application and Access Control Policies . . . . . . .  25
   5.  I2RS Application Isolation  . . . . . . . . . . . . . . . . .  26
     5.1.  Robustness Toward Programmability . . . . . . . . . . . .  26
     5.2.  Application Isolation . . . . . . . . . . . . . . . . . .  27
       5.2.1.  DoS . . . . . . . . . . . . . . . . . . . . . . . . .  27
       5.2.2.  Application Logic Control . . . . . . . . . . . . . .  29
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  29
Show full document text