-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
github-actions
committed
Dec 31, 2023
1 parent
ce41bc2
commit 4ad0f55
Showing
4 changed files
with
165 additions
and
0 deletions.
There are no files selected for viewing
118 changes: 118 additions & 0 deletions
118
data/draft-pignataro-opsawg-oam-whaaat-question-mark-00.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,118 @@ | ||
--- | ||
schema-version: v1.2.3 | ||
id: draft-pignataro-opsawg-oam-whaaat-question-mark-00 | ||
title: | ||
- content: Guidelines for Charactering "OAM" | ||
language: | ||
- en | ||
script: | ||
- Latn | ||
format: text/plain | ||
link: | ||
- content: https://datatracker.ietf.org/doc/html/draft-pignataro-opsawg-oam-whaaat-question-mark-00 | ||
type: src | ||
type: standard | ||
docid: | ||
- id: draft-pignataro-opsawg-oam-whaaat-question-mark-00 | ||
type: Internet-Draft | ||
primary: true | ||
- id: I-D.pignataro-opsawg-oam-whaaat-question-mark | ||
type: IETF | ||
scope: anchor | ||
docnumber: I-D.pignataro-opsawg-oam-whaaat-question-mark | ||
date: | ||
- type: published | ||
value: '2023-12-31' | ||
contributor: | ||
- person: | ||
name: | ||
given: | ||
forename: | ||
- content: Carlos | ||
language: | ||
- en | ||
- language: | ||
- en | ||
initial: C | ||
formatted_initials: | ||
content: C. | ||
language: | ||
- en | ||
surname: | ||
content: Pignataro | ||
language: | ||
- en | ||
completename: | ||
content: Carlos Pignataro | ||
language: | ||
- en | ||
affiliation: | ||
- organization: | ||
name: | ||
- content: North Carolina State University | ||
role: | ||
- type: author | ||
- person: | ||
name: | ||
given: | ||
forename: | ||
- content: Adrian | ||
language: | ||
- en | ||
- language: | ||
- en | ||
initial: A | ||
formatted_initials: | ||
content: A. | ||
language: | ||
- en | ||
surname: | ||
content: Farrel | ||
language: | ||
- en | ||
completename: | ||
content: Adrian Farrel | ||
language: | ||
- en | ||
affiliation: | ||
- organization: | ||
name: | ||
- content: Old Dog Consulting | ||
role: | ||
- type: author | ||
version: | ||
- draft: '00' | ||
revdate: '2023-12-31' | ||
language: | ||
- en | ||
script: | ||
- Latn | ||
abstract: | ||
- content: <p>As the IETF continues to produce and standardize different Operations, | ||
Administration, and Maintenance (OAM) protocols and technologies, various qualifiers | ||
and modifiers are prepended to the OAM acronym. While, at first glance, the most | ||
used appear to be well understood, the same qualifier may be interpreted differently | ||
in different contexts. A case in point is the qualifiers "in-band" and "out-of-band" | ||
which have their origins in the radio lexicon and which have been extrapolated | ||
into other communication networks. This document considers some common qualifiers | ||
and modifiers that are prepended to the OAM acronym, and lays out guidelines for | ||
their use in future IETF work. This document updates RFC 6291 by adding to the | ||
guidelines for the use of the term "OAM".</p> | ||
language: | ||
- en | ||
script: | ||
- Latn | ||
format: text/html | ||
series: | ||
- type: main | ||
title: | ||
content: Internet-Draft | ||
language: | ||
- en | ||
script: | ||
- Latn | ||
format: text/plain | ||
number: draft-pignataro-opsawg-oam-whaaat-question-mark-00 | ||
doctype: internet-draft | ||
ext: | ||
schema-version: v1.0.1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
schema-version: v1.2.3 | ||
id: draft-pignataro-opsawg-oam-whaaat-question-mark | ||
title: | ||
- content: Guidelines for Charactering "OAM" | ||
language: | ||
- en | ||
script: | ||
- Latn | ||
format: text/plain | ||
docid: | ||
- id: draft-pignataro-opsawg-oam-whaaat-question-mark | ||
type: Internet-Draft | ||
primary: true | ||
abstract: | ||
- content: <p>As the IETF continues to produce and standardize different Operations, | ||
Administration, and Maintenance (OAM) protocols and technologies, various qualifiers | ||
and modifiers are prepended to the OAM acronym. While, at first glance, the most | ||
used appear to be well understood, the same qualifier may be interpreted differently | ||
in different contexts. A case in point is the qualifiers "in-band" and "out-of-band" | ||
which have their origins in the radio lexicon and which have been extrapolated | ||
into other communication networks. This document considers some common qualifiers | ||
and modifiers that are prepended to the OAM acronym, and lays out guidelines for | ||
their use in future IETF work. This document updates RFC 6291 by adding to the | ||
guidelines for the use of the term "OAM".</p> | ||
language: | ||
- en | ||
script: | ||
- Latn | ||
format: text/html | ||
relation: | ||
- type: includes | ||
bibitem: | ||
id: draft-pignataro-opsawg-oam-whaaat-question-mark-00 | ||
docid: | ||
- id: draft-pignataro-opsawg-oam-whaaat-question-mark-00 | ||
type: Internet-Draft | ||
primary: true | ||
formattedref: | ||
content: draft-pignataro-opsawg-oam-whaaat-question-mark-00 | ||
format: text/plain | ||
ext: | ||
schema-version: v1.0.1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.