Deprecating the Use of Router Alert in LSP Ping
draft-kompella-mpls-lspping-norao-02
Document | Type |
Replaced Internet-Draft
(mpls WG)
Expired & archived
|
|
---|---|---|---|
Authors | Kireeti Kompella , Ron Bonica , Greg Mirsky | ||
Last updated | 2022-12-10 | ||
Replaced by | draft-ietf-mpls-lspping-norao | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Candidate for WG Adoption | |
Document shepherd | Loa Andersson | ||
IESG | IESG state | Replaced by draft-ietf-mpls-lspping-norao | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | loa@pi.nu |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
LSP ping messages (RFC 8029) are encapsulated in IP headers that include a Router Alert Option (RAO). The rationale for including an RAO is questionable. Furthermore, RFC6398 identifies security vulnerabilities associated with the RAO. Therefore, this document removes the RAO from LSP ping message encapsulations. It updates RFCs 7506 and 8029. This document also recommends the use of an IPv6 loopback address (:::1/128) and discourages the use of an IPv4 loopback address mapped to IPv6.
Authors
Kireeti Kompella
Ron Bonica
Greg Mirsky
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)