Skip to content

Commit 6a3febe

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 238 new elements (2026-05-22)
1 parent 8ec0514 commit 6a3febe

238 files changed

Lines changed: 1844 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎corpus/elements/rfc-855__design-rationale-a-default-specification-section-is-required-to-describe.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-855
2+
kind: design-rationale
3+
summary: A 'Default Specification' section is required to describe behavior of hosts that do not implement or use the option, ensuring interoperability with non-implementing peers without explicit negotiation.
4+
section: Documentation Requirements
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__design-rationale-a-motivation-section-is-required-because-merely-defining.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-855
2+
kind: design-rationale
3+
summary: A 'Motivation' section is required because merely defining command meanings is insufficient; explaining why an option was invented helps implementers who may not recognize the problem the option solves.
4+
section: Documentation Requirements
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__design-rationale-designers-of-options-requiring-subnegotiation-must-take-great.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-855
2+
kind: design-rationale
3+
summary: Designers of options requiring subnegotiation must take great care to avoid infinite loops; if both parties can accept any parameter value and each suggests a different value, infinite oscillation of 'acknowledgments' can result where each receiver believes it is merely acknowledging new proposals.
4+
section: A Note on Subnegotiation
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__design-rationale-telnet-options-exist-to-permit-hosts-to-obtain.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-855
2+
kind: design-rationale
3+
summary: Telnet options exist to permit hosts to obtain more elegant solutions to communication problems between dissimilar devices than is possible within the NVT framework. Hosts should be free to invent, test, or discard options at will, while broadly useful options are documented and publicized via RFCs.
4+
section: Introduction
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__interoperability-note-a-receiver-that-cannot-parse-subnegotiation-parameters-may.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-855
2+
kind: interoperability-note
3+
summary: A receiver that cannot parse subnegotiation parameters may still locate the end of the parameter string by scanning for the IAC SE byte sequence, allowing graceful handling without full option comprehension.
4+
section: A Note on Subnegotiation
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__normative-requirement-a-single-option-code-must-not-be-used.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-855
2+
kind: normative-requirement
3+
summary: A single option code MUST NOT be used for several different options. Option codes are assigned by a designated authority (Postel at USC-ISI) to prevent collisions.
4+
section: Introduction
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- registry
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__normative-requirement-documentation-is-generally-required-prior-to-option-code.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-855
2+
kind: normative-requirement
3+
summary: Documentation is generally required prior to option code assignment. Options are to be publicized by publishing their documentation as RFCs.
4+
section: Introduction
5+
rfc2119_level: REQUIRED
6+
topics:
7+
- process
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__normative-requirement-either-party-may-refuse-to-pursue-further-subnegotiation.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-855
2+
kind: normative-requirement
3+
summary: Either party may refuse to pursue further subnegotiation at any time by sending WON'T or DON'T to the other party.
4+
section: A Note on Subnegotiation
5+
rfc2119_level: MAY
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__normative-requirement-if-any-parameter-byte-in-a-subnegotiation-has.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-855
2+
kind: normative-requirement
3+
summary: If any parameter byte in a subnegotiation has value 255 (0xFF), it must be doubled in accordance with general TELNET rules, since 255 is the IAC escape code.
4+
section: A Note on Subnegotiation
5+
rfc2119_level: REQUIRED
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-855__protocol-element-option-documentation-must-contain-at-minimum-five-sections.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-855
2+
kind: protocol-element
3+
summary: 'Option documentation must contain at minimum five sections: (1) Command Name and Option Code, (2) Command Meanings, (3) Default Specification, (4) Motivation, and (5) Description or Implementation Rules.'
4+
section: Documentation Requirements
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

0 commit comments

Comments
 (0)