Trusted Path Routing
draft-voit-rats-trustworthy-path-routing-01

Document Type Active Internet-Draft (individual)
Author Eric Voit 
Last updated 2020-10-02
Replaces draft-voit-rats-trusted-path-routing
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)
RATS Working Group                                               E. Voit
Internet-Draft                                                     Cisco
Intended status: Standards Track                        October 02, 2020
Expires: April 5, 2021

                          Trusted Path Routing
              draft-voit-rats-trustworthy-path-routing-01

Abstract

   There are end-users who believe encryption technologies like IPSec
   alone are insufficient to protect the confidentiality of their highly
   sensitive traffic flows.  These end-users want their flows to
   traverse devices which have been freshly appraised and verified.
   This specification describes Trusted Path Routing.  Trusted Path
   Routing protects sensitive flows as they transit a network by
   forwarding traffic to/from sensitive subnets across network devices
   recently appraised as trustworthy.

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 April 5, 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

Voit                      Expires April 5, 2021                 [Page 1]
Internet-Draft                 trust-path                   October 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Terms . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Requirements Notation . . . . . . . . . . . . . . . . . .   4
   3.  Protocol Independent Definitions  . . . . . . . . . . . . . .   4
     3.1.  Trusted Path Routing Service  . . . . . . . . . . . . . .   4
     3.2.  Network Topology Assembly . . . . . . . . . . . . . . . .   5
     3.3.  Link Appraisal  . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Trustworthiness Vector  . . . . . . . . . . . . . . . . .   6
     3.5.  Attestation Results . . . . . . . . . . . . . . . . . . .   8
     3.6.  Stamped Passport  . . . . . . . . . . . . . . . . . . . .   9
     3.7.  Appraising the Stamped Passport . . . . . . . . . . . . .  11
   4.  Implementable Solution  . . . . . . . . . . . . . . . . . . .  13
     4.1.  Prerequisites . . . . . . . . . . . . . . . . . . . . . .  13
     4.2.  Protocol Bindings . . . . . . . . . . . . . . . . . . . .  14
   5.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .  16
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  23
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  23
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  23
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  24
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  25
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  25
   Appendix C.  Open Questions . . . . . . . . . . . . . . . . . . .  26
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  26

1.  Introduction

   There are end-users who believe encryption technologies like IPSec
   alone are insufficient to protect the confidentiality of their highly
   sensitive traffic flows.  These customers want their highly sensitive
   flows to be transported over only network devices recently verified
   as trustworthy.

   With the inclusion of TPM based cryptoprocessors into network
   devices, it is now possible for network providers to identify
   potentially compromised devices as well as potentially exploitable
   (or even exploited) vulnerabilities.  Using this knowledge, it then
   becomes possible to redirect sensitive flows around these devices.

   Trusted Path Routing provides a method of establishing Trusted
   Topologies which only include trust-verified network devices.
Show full document text