Skip to main content

Trusted Path Routing
draft-voit-rats-trusted-path-routing-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Eric Voit
Last updated 2020-06-10
Replaced by draft-voit-rats-trustworthy-path-routing, draft-birkholz-rats-network-device-subscription
RFC stream (None)
Intended RFC status (None)
Formats
Additional resources Yang catalog entry for ietf-rats-attestation-stream@2020-03-06.yang
Yang impact analysis for draft-voit-rats-trusted-path-routing
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-voit-rats-trustworthy-path-routing, draft-birkholz-rats-network-device-subscription
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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.

Authors

Eric Voit

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)