Skip to main content

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

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Eric Voit , Chennakesava Reddy Gaddam , Guy Fedorkow , Henk Birkholz , Meiling Chen
Last updated 2022-09-03 (Latest revision 2022-03-02)
Replaces draft-voit-rats-trusted-path-routing
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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 for trustworthiness. 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
Chennakesava Reddy Gaddam
Guy Fedorkow
Henk Birkholz
Meiling Chen

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