Skip to main content

Abstract next-hop addresses in IP VPNs
draft-malyushkin-bess-ip-vpn-abstract-next-hops-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Igor Malyushkin
Last updated 2023-02-18 (Latest revision 2022-08-17)
RFC stream (None)
Intended RFC status (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

draft-malyushkin-bess-ip-vpn-abstract-next-hops-00 Abstract This document discusses the IP VPN convergence aspects and specifies procedures for IP VPN to signal the attachment circuit failure. The specified procedures help significantly improve the IP VPN convergence. About This Document This note is to be removed before publishing as an RFC. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-malyushkin-bess-ip-vpn- abstract-next-hops/. Discussion of this document takes place on the BGP Enabled ServiceS Working Group mailing list (mailto:bess@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/bess/. Subscribe at https://www.ietf.org/mailman/listinfo/bess/.

Authors

Igor Malyushkin

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