Skip to content

Commit bb9a545

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 28 new elements (2026-05-24)
1 parent 878d04c commit bb9a545

28 files changed

Lines changed: 210 additions & 0 deletions

File tree

‎corpus/elements/rfc-2371__design-rationale-tip-achieves-simplicity-by-specifying-only-how-different.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2371
2+
kind: design-rationale
3+
summary: TIP achieves simplicity by specifying only how different nodes agree on the outcome of a transaction, deliberately leaving the subject matter of the transaction to be communicated via other protocols. This avoids all issues related to application communication semantics and data representation.
4+
section: "1"
5+
topics:
6+
- security
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__design-rationale-tip-supports-both-push-and-pull-transaction-models.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2371
2+
kind: design-rationale
3+
summary: TIP supports both 'push' and 'pull' transaction models. In push, the superior's TM exports the transaction to the subordinate before the application sends work. In pull, the application passes a transaction reference and the subordinate's TM pulls it on demand. Both models result in the superior knowing to involve the subordinate in two-phase commit.
4+
section: "6"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__design-rationale-tmp-is-intentionally-not-a-general-purpose-multiplexing.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2371
2+
kind: design-rationale
3+
summary: TMP is intentionally not a general-purpose multiplexing protocol. It is designed solely for TIP's short request-response messages; protocols with large messages can exceed receiver buffering and cause deadlock under TMP, which TIP avoids because all TIP messages are short.
4+
section: A.1
5+
topics:
6+
- tcp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__normative-requirement-a-subordinate-that-notices-a-connection-failure-in.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2371
2+
kind: normative-requirement
3+
summary: A subordinate that notices a connection failure in Prepared state SHOULD periodically create a new connection to the superior and send QUERY until it receives QUERIEDNOTFOUND (abort) or the superior sends RECONNECT on a new connection.
4+
section: "15"
5+
rfc2119_level: SHOULD
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__normative-requirement-all-implementations-must-support-receipt-of-pipelined-lines.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2371
2+
kind: normative-requirement
3+
summary: All implementations MUST support receipt of pipelined lines. A line received when it is not the other party's turn is held and processed when the connection state requires it; responses must be issued in the order lines were received. An error on any line causes the connection to enter Error state and all subsequent lines are discarded.
4+
section: "12"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__normative-requirement-if-the-connection-fails-in-begun-or-enlisted.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2371
2+
kind: normative-requirement
3+
summary: If the connection fails in Begun or Enlisted state and COMMIT has not been sent, the transaction will be aborted. If COMMIT was sent, the outcome is unknown to the superior and must be determined by application-specific means.
4+
section: "15"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__normative-requirement-tip-operates-over-tcp-optionally-using-tls-to.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-2371
2+
kind: normative-requirement
3+
summary: TIP operates over TCP, optionally using TLS to provide a secured and authenticated connection, and optionally using a multiplexing protocol over the same TCP or TLS connection.
4+
section: "4"
5+
rfc2119_level: REQUIRED
6+
topics:
7+
- tcp
8+
- tls
9+
- security
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__normative-requirement-tip-urls-must-be-guaranteed-globally-unique-for.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2371
2+
kind: normative-requirement
3+
summary: TIP URLs must be guaranteed globally unique for all time to prevent possible non-deterministic behavior from duplicate identifiers. How uniqueness is achieved is implementation-specific.
4+
section: "8"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__protocol-element-a-tip-transaction-manager-address-takes-the-form.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2371
2+
kind: protocol-element
3+
summary: A TIP transaction manager address takes the form <hostport><path>, where <hostport> is <host>[:<port>] and <path> is a URI-style path identifying the specific transaction manager at that host. The <hostport> is used for TCP connection endpoint; the <path> routes to the specific TM.
4+
section: "7"
5+
topics:
6+
- tcp
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2371__protocol-element-a-tip-url-takes-the-form-tip-transaction.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2371
2+
kind: protocol-element
3+
summary: A TIP URL takes the form tip://<transaction manager address>?<transaction string>, where the transaction string is either a URN ("urn:<NID>:<NSS>") for standard global identifiers, or a printable ASCII sequence for non-standard identifiers whose uniqueness is guaranteed by combining it with the transaction manager address.
4+
section: "8"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

0 commit comments

Comments
 (0)