Use of The IPv4 Reserved-flag for OAM
draft-aghule-intarea-oam-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Ashish Ghule , Ron Bonica | ||
| Last updated | 2020-02-08 (latest revision 2019-08-07) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-aghule-intarea-oam-01.txt
https://www.ietf.org/archive/id/draft-aghule-intarea-oam-01.txt
Abstract
This document defines new IPv4 Operations and Management (OAM) capabilities. In order to support these capabilities, this document defines a new interpretation of the IPv4 Reserved-flag.
Authors
Ashish Ghule
(aghule@juniper.net)
Ron Bonica
(rbonica@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)