Update to OSPF Terminology
draft-fox-lsr-ospf-terminology-01
| Document | Type |
Replaced Internet-Draft
(candidate for lsr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mike Fox , Acee Lindem , Alvaro Retana | ||
| Last updated | 2022-04-25 (Latest revision 2022-03-03) | ||
| Replaced by | draft-ietf-lsr-ospf-terminology | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | Christian Hopps | ||
| IESG | IESG state | Replaced by draft-ietf-lsr-ospf-terminology | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | chopps@chopps.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document updates some OSPF terminology to be in line with inclusive language used in the industry. This document updates RFC2328 and RFC5340.
Authors
Mike Fox
Acee Lindem
Alvaro Retana
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)