Skip to content

Commit 89c1ed8

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 170 new elements (2026-05-22)
1 parent a7ed699 commit 89c1ed8

170 files changed

Lines changed: 1307 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-2427__design-rationale-because-dlcis-have-only-local-significance-and-are.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2427
2+
kind: design-rationale
3+
summary: Because DLCIs have only local significance and are modified in transit, a Frame Relay station has no source hardware address to populate in ARP requests. The solution is to use the DLCI from the incoming Frame Relay header to back-fill the ARP source hardware address at the receiver, violating strict layering but enabling correct address resolution.
4+
section: "6"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__design-rationale-fragmentation-was-removed-from-this-document-compared-to.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2427
2+
kind: design-rationale
3+
summary: Fragmentation was removed from this document (compared to RFC 1490) because no interoperable implementations of the RFC 1490 fragmentation algorithm existed and the mechanism was considered insufficient for some Frame Relay applications. Fragmentation is now handled by FRF.12.
4+
section: "13"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__design-rationale-ip-is-encapsulated-using-nlpid-0xcc-rather-than.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2427
2+
kind: design-rationale
3+
summary: IP is encapsulated using NLPID 0xCC rather than SNAP because it saves 48 bits per frame and is consistent with the established practice for IP encapsulation in X.25. Where a protocol has an assigned NLPID, SNAP is wasteful and should not be used.
4+
section: "7"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__design-rationale-the-common-pdu-header-and-trailer-are-carried.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2427
2+
kind: design-rationale
3+
summary: 'The Common PDU Header and Trailer are carried in bridged 802.6 frames to enable pipelining at the egress bridge: the BAsize field contains the PDU length, allowing the bridge to begin transmitting 802.6 segments before receiving the complete PDU.'
4+
section: "4.2"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__interoperability-note-for-iso-protocols-such-as-clnp-nlpid-0x81.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2427
2+
kind: interoperability-note
3+
summary: For ISO protocols such as CLNP (NLPID 0x81), the NLPID is considered part of the protocol data and must not be stripped before passing to upper layers. For non-ISO protocols like IP (NLPID 0xCC), the NLPID is purely a demultiplexing value and not part of the protocol.
4+
section: "8"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__interoperability-note-non-canonical-mac-destination-addresses-are-used-for.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2427
2+
kind: interoperability-note
3+
summary: Non-canonical MAC destination addresses are used for encapsulated IEEE 802.5 and FDDI bridged frames (following RFC 1638 precedent), while canonical MAC destination addresses are used for all other bridging encapsulations (802.3, 802.4, 802.6).
4+
section: "4.2"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__interoperability-note-the-common-pdu-header-and-trailer-of-an.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2427
2+
kind: interoperability-note
3+
summary: The Common PDU Header and Trailer of an encapsulated 802.6 frame must not be simply copied to the outgoing 802.6 subnetwork, because the encapsulated BEtag value may conflict with the previous BEtag value transmitted by the egress bridge.
4+
section: "4.2"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__normative-requirement-a-compliant-station-must-send-and-accept-the.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2427
2+
kind: normative-requirement
3+
summary: A compliant station must send and accept the NLPID-encapsulated version of protocols that have an assigned NLPID. It MAY accept a SNAP-encapsulated version of such protocols but is not required to, as those frames are noncompliant.
4+
section: "13"
5+
rfc2119_level: MAY
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__normative-requirement-a-frame-relay-network-must-support-at-least.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2427
2+
kind: normative-requirement
3+
summary: A Frame Relay network must support at least a 262-octet maximum frame size. A Frame Relay DTE must allow the maximum acceptable frame size to be configurable.
4+
section: "3"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-2427__normative-requirement-because-dlcis-have-only-local-significance-arp-hardware.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2427
2+
kind: normative-requirement
3+
summary: Because DLCIs have only local significance, ARP hardware addresses in transit are invalid at the destination. The receiving station must extract the correct Q.922 address from the Frame Relay header and place it in the source hardware address field of the ARP packet.
4+
section: "6"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-22"

0 commit comments

Comments
 (0)