Skip to content

Commit 4a016ce

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 129 new elements (2026-05-24)
1 parent 1080495 commit 4a016ce

129 files changed

Lines changed: 1083 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-2331__design-rationale-for-ip-router-interconnection-with-abr-a-non.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-2331
2+
kind: design-rationale
3+
summary: For IP router interconnection with ABR, a non-zero Minimum Cell Rate provides a bandwidth commitment analogous to a provisioned leased-line capacity, which is distinct from per-flow IIS reservations and helps prevent starvation of the aggregate best-effort traffic.
4+
section: Appendix B
5+
topics:
6+
- ip
7+
- qos
8+
- congestion
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__design-rationale-frame-discard-is-based-on-partial-and-early.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2331
2+
kind: design-rationale
3+
summary: Frame discard is based on 'Partial and Early Packet Discard' strategy [ROM94] and applies to all ATM services except loss-less CBR; it is recommended for all IP SVCs because network entities that do not support it must still forward the signaling, enabling graceful degradation.
4+
section: "7"
5+
topics:
6+
- ip
7+
- congestion
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__design-rationale-lij-leaf-initiated-join-atm-anycast-and-switched.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2331
2+
kind: design-rationale
3+
summary: LIJ (Leaf Initiated Join), ATM Anycast, and Switched Virtual Path capabilities from SIG 4.0 are intentionally not discussed in this memo because models for their use in IP over ATM environments had not yet been defined at time of publication.
4+
section: "2"
5+
topics:
6+
- ip
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__design-rationale-traffic-parameters-cannot-be-renegotiated-after-a-call.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2331
2+
kind: design-rationale
3+
summary: Traffic parameters cannot be renegotiated after a call is active in SIG 4.0; negotiation is only possible during call establishment using the Minimum Acceptable or Alternative ATM Traffic Descriptor IEs, which is why IP entities should proactively negotiate PCR to link rate with a minimum of zero.
4+
section: 5.3.2
5+
topics:
6+
- ip
7+
- qos
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__design-rationale-ubr-is-identified-as-the-most-natural-atm.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2331
2+
kind: design-rationale
3+
summary: UBR is identified as the most natural ATM service category for best-effort IP because non-IIS IP has no notion of the performance requirements of the higher layers it supports; it therefore cannot provide a flexible, application-specific traffic signaling interface.
4+
section: 5.3.1
5+
topics:
6+
- ip
7+
- qos
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__interoperability-note-in-sig-4-0-a-setup-or-connect.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2331
2+
kind: interoperability-note
3+
summary: In SIG 4.0, a SETUP or CONNECT message may include ONLY one of the Minimum Acceptable ATM Traffic Descriptor IE or the Alternative ATM Traffic Descriptor IE; including both in the same message is not permitted.
4+
section: 5.3.2
5+
topics:
6+
- ip
7+
- qos
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__interoperability-note-several-traffic-parameter-combination-entries-in-appendix-c.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2331
2+
kind: interoperability-note
3+
summary: Several traffic parameter combination entries in Appendix C are included for backward compatibility with UNI 3.1 and ITU-T Recommendations (Notes 4, 5, 10); with these conformance definitions the CLR commitment applies only to the CLP=0 traffic stream.
4+
section: Appendix C
5+
topics:
6+
- ip
7+
- qos
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__interoperability-note-the-qos-parameter-ie-may-be-omitted-from.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2331
2+
kind: interoperability-note
3+
summary: The QoS Parameter IE may be omitted from a SETUP message if and only if the Extended QoS Parameters IE is included; certain ATM service categories also permit use of the Extended QoS Parameters IE and End-to-End Transit Delay IE in place of the generic QoS Parameter IE.
4+
section: 5.3.4
5+
topics:
6+
- ip
7+
- qos
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__normative-requirement-a-setup-message-establishing-an-atm-connection-for.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2331
2+
kind: normative-requirement
3+
summary: 'A SETUP message establishing an ATM connection for IP and multiprotocol interconnection MUST contain: AAL Parameters, ATM Traffic Descriptor, Broadband Bearer Capability, Broadband Low Layer Information, QoS Parameter, Called Party Number, and Calling Party Number IEs.'
4+
section: "4"
5+
rfc2119_level: MUST
6+
topics:
7+
- ip
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2331__normative-requirement-a-system-implementing-a-public-atm-uni-interface.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-2331
2+
kind: normative-requirement
3+
summary: A system implementing a Public ATM UNI interface serving as the called party of a VCC MUST NOT use an inactivity timer on such a VCC by default, to support layer 3 signalling protocols like RSVP where VCs correspond to reserved flows.
4+
section: "3.1"
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- ip
8+
- qos
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-24"

0 commit comments

Comments
 (0)