Skip to content

Commit b725b68

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 182 new elements (2026-05-22)
1 parent 5c8b95b commit b725b68

182 files changed

Lines changed: 1411 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-1171__design-rationale-lcp-packets-are-always-sent-in-their-full.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-1171
2+
kind: design-rationale
3+
summary: LCP packets are always sent in their full standard form regardless of negotiated Configuration Options. This ensures Configure-Request packets remain recognizable even when one end mistakenly believes the link to be Open.
4+
section: "4.4"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__design-rationale-ppp-does-not-require-modem-control-signals-rts.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-1171
2+
kind: design-rationale
3+
summary: PPP does not require modem control signals (RTS, CTS, DCD, DTR), though using them when available allows greater functionality and performance. This minimizes physical-layer requirements so PPP can operate across any DTE/DCE interface.
4+
section: "2"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__design-rationale-the-ppp-protocol-field-is-defined-to-be.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-1171
2+
kind: design-rationale
3+
summary: The PPP Protocol field is defined to be consistent with the ISO 3309 extension mechanism for Address fields, even though it is not part of the HDLC standard. This maintains standards alignment while enabling multi-protocol multiplexing.
4+
section: "3.1"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__design-rationale-there-is-no-version-field-in-the-lcp.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-1171
2+
kind: design-rationale
3+
summary: There is no version field in the LCP packet format. If a new version of LCP is needed, a new Data Link Layer Protocol field value is intended to differentiate it from Version 1. A Version 1 implementation will always respond to unknown Protocols with a recognizable Version 1 packet, providing a deterministic fallback.
4+
section: "4.4"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__interoperability-note-on-asynchronous-links-character-stuffing-is-used-for.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-1171
2+
kind: interoperability-note
3+
summary: On asynchronous links, character stuffing is used for transparency. The Control Escape octet (0x7d) causes the following octet to be XOR'd with 0x20. All octets less than 0x20, plus 0x7e and 0x7d, are escaped. The receiver strips escape sequences prior to FCS computation.
4+
section: A
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__interoperability-note-the-fcs-field-is-calculated-over-all-bits.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-1171
2+
kind: interoperability-note
3+
summary: The FCS field is calculated over all bits of the Address, Control, Protocol, and Information fields, excluding start/stop bits, transparency-inserted bits or octets, Flag Sequences, and the FCS field itself. The FCS is transmitted with the coefficient of the highest term first.
4+
section: "3.1"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__normative-requirement-all-protocol-field-values-must-be-odd-the.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-1171
2+
kind: normative-requirement
3+
summary: All Protocol field values MUST be odd; the least significant bit of the least significant octet MUST equal '1'. Additionally, the least significant bit of the most significant octet MUST equal '0'. Frames violating these rules must be treated as having an unrecognized Protocol.
4+
section: "3.1"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__normative-requirement-before-any-ip-packets-may-be-communicated-both.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-1171
2+
kind: normative-requirement
3+
summary: Before any IP packets may be communicated, both LCP and IPCP must reach the Open state. Larger IP datagrams exceeding the PPP maximum Information field length must be fragmented as necessary.
4+
section: "5.1"
5+
rfc2119_level: MUST
6+
topics:
7+
- ip
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__normative-requirement-each-nak-d-configuration-option-in-a-configure.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-1171
2+
kind: normative-requirement
3+
summary: Each nak'd Configuration Option in a Configure-Nak MUST be modified to a value acceptable to the Configure-Nak sender. Acceptable options must be filtered out; unacceptable options must not be reordered.
4+
section: 4.4.3
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1171__normative-requirement-max-restarts-must-be-configurable-but-should-default.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-1171
2+
kind: normative-requirement
3+
summary: Max-Restarts MUST be configurable but should default to 10 retransmissions. It indicates the number of packet retransmissions required before reasonable assurance that the link is closed. Any timeout used for loop detection MUST also be configurable.
4+
section: "4.3"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

0 commit comments

Comments
 (0)