Security Context Template
draft-birrane-dtn-scot-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
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)
Delay-Tolerant Networking                                     E. Birrane
Internet-Draft                                                 S. Heiner
Intended status: Standards Track                                 JHU/APL
Expires: January 11, 2021                                  July 10, 2020

                       Security Context Template
                       draft-birrane-dtn-scot-00

Abstract

   This document defines a standard template for security contexts
   written for the Bundle Protocol Security Protocol (BPSec).

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 https://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 11, 2021.

Copyright Notice

   Copyright (c) 2020 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.

Birrane & Heiner        Expires January 11, 2021                [Page 1]
Internet-Draft          Security Context Template              July 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Specification Scope . . . . . . . . . . . . . . . . . . .   3
     1.2.  Related Documents . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  System Overview . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Methods of Establishing Context . . . . . . . . . . . . .   4
       2.1.1.  Out-Of-Band Mode  . . . . . . . . . . . . . . . . . .   4
       2.1.2.  In-Band Mode  . . . . . . . . . . . . . . . . . . . .   5
       2.1.3.  Hybrid Mode . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Security Policy Roles . . . . . . . . . . . . . . . . . .   7
     2.3.  Common Events and Actions . . . . . . . . . . . . . . . .   8
       2.3.1.  Bundle Protocol Reason Codes  . . . . . . . . . . . .   8
       2.3.2.  Event Codes . . . . . . . . . . . . . . . . . . . . .  10
       2.3.3.  Processing Actions  . . . . . . . . . . . . . . . . .  12
     2.4.  Security Policy Considerations  . . . . . . . . . . . . .  14
     2.5.  Security Context Template . . . . . . . . . . . . . . . .  15
       2.5.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .  16
       2.5.2.  Interfaces  . . . . . . . . . . . . . . . . . . . . .  16
       2.5.3.  Definitions . . . . . . . . . . . . . . . . . . . . .  17
       2.5.4.  Canonicalization Algorithms . . . . . . . . . . . . .  17
       2.5.5.  Processing  . . . . . . . . . . . . . . . . . . . . .  18
       2.5.6.  Policy  . . . . . . . . . . . . . . . . . . . . . . .  18
       2.5.7.  IANA Considerations . . . . . . . . . . . . . . . . .  18
   3.  Normative References  . . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   The Bundle Protocol (BP) may operate in environments that prevent
   reliable synchronization of session information, to include
   negotiated cryptographic material.  To accommodate for this
   possibility, BP bundles may use extension blocks to carry annotative
   information.  The Bundle Protocol Security Protocol (BPSec) defines
   security-related extension blocks (security blocks) to carry
   cryptographic material, to optionally include material that might
   otherwise be expected resident at communication endpoints.  To
   accomplish these, BPSec security blocks specify a "security context"
   comprising the material generated for, carried with, and/or otherwise
   utilized by the block.

   Where BPSec security blocks traverse networks for which a
   synchronized security mechanism exists, a security context can be
   defined which minimally identifies endpoint information.  For
   example, in networks that support TLS, a security context can be
   defined to carry TLS record information after a successful TLS
Show full document text