Trusted Domain SRv6
draft-raviolli-intarea-trusted-domain-srv6-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Andrew Alston , Tom Hill , Tony Przygienda , Luay Jalil | ||
Last updated | 2023-10-04 (Latest revision 2023-04-02) | ||
Replaces | draft-intarea-raviolli-trusted-domain-srv6 | ||
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
SRv6 as designed has evoked interest from various parties, though its deployment is being limited by known security problems in its architecture. This document specifies a standard way to create a solution that closes some of the major security concerns, while retaining the basis of the SRv6 protocol.
Authors
Andrew Alston
Tom Hill
Tony Przygienda
Luay Jalil
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)