Skip to content

Commit 990a82a

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

216 files changed

Lines changed: 1720 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-1225__design-rationale-minimal-pop3-server-implementations-need-only-parse-the.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-1225
2+
kind: design-rationale
3+
summary: Minimal POP3 server implementations need only parse the maildrop into component messages and are NOT required to parse individual messages internally. This keeps server complexity low while allowing more capable clients to exploit optional features like TOP.
4+
section: The AUTHORIZATION State
5+
topics:
6+
- email
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__design-rationale-pop3-is-designed-for-a-split-ua-model.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-1225
2+
kind: design-rationale
3+
summary: POP3 is designed for a 'split-UA' model where mail posting (SMTP) and retrieval (POP3) are separated, allowing resource-limited workstations to participate in the mail system without running a full MTS. The client host acts as a user agent, not a trusted MTS entity.
4+
section: The POP and the Split-UA model
5+
topics:
6+
- email
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__design-rationale-the-spec-strongly-encourages-implementing-the-optional-top.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-1225
2+
kind: design-rationale
3+
summary: The spec strongly encourages implementing the optional TOP and RPOP commands instead of augmenting drop or scan listings with additional parsed data. The stated philosophy is to place intelligence in the POP3 client rather than the server, keeping server implementations minimal.
4+
section: Optional POP3 Commands
5+
topics:
6+
- email
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__interoperability-note-the-octet-count-assigned-to-a-message-by.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-1225
2+
kind: interoperability-note
3+
summary: The octet count assigned to a message by the POP3 server may differ from the byte count on the server host due to local end-of-line conventions. For example, a server using single-character line endings must count each as two octets when reporting message sizes.
4+
section: Message Format
5+
topics:
6+
- email
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__normative-requirement-after-parsing-the-maildrop-the-server-assigns-sequential.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-1225
2+
kind: normative-requirement
3+
summary: After parsing the maildrop, the server assigns sequential integer message-ids starting at 1 (the n-th message gets id n), notes each message's size in octets, and sets 'highest number accessed' to the id of the last message previously referenced by RETR. All message-ids and sizes are expressed in decimal.
4+
section: The AUTHORIZATION State
5+
rfc2119_level: MUST
6+
topics:
7+
- email
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__normative-requirement-all-messages-transmitted-during-a-pop3-session-are.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-1225
2+
kind: normative-requirement
3+
summary: All messages transmitted during a POP3 session are assumed to conform to RFC 822 (Standard for the Format of ARPA-Internet Text Messages).
4+
section: Message Format
5+
rfc2119_level: MUST
6+
topics:
7+
- email
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__normative-requirement-the-pop3-server-listens-on-tcp-port-110.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-1225
2+
kind: normative-requirement
3+
summary: The POP3 server listens on TCP port 110. When a client establishes a TCP connection, the server sends a greeting response, and the session enters the AUTHORIZATION state.
4+
section: A Short Digression
5+
rfc2119_level: MUST
6+
topics:
7+
- email
8+
- tcp
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__normative-requirement-the-reply-text-following-ok-or-err-is.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-1225
2+
kind: normative-requirement
3+
summary: The reply text following +OK or -ERR is significant only in its indicator token; any trailing text on the response line MAY be ignored by the client. The sole exception is STAT, whose drop listing format carries structured data the client must parse.
4+
section: Optional POP3 Commands
5+
rfc2119_level: MAY
6+
topics:
7+
- email
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__normative-requirement-upon-successful-authentication-the-pop3-server-must-acquire.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-1225
2+
kind: normative-requirement
3+
summary: Upon successful authentication, the POP3 server MUST acquire an exclusive-access lock on the maildrop before entering the TRANSACTION state. If the lock cannot be acquired, the server MUST respond with -ERR and, if a lock was transiently acquired, MUST release it before rejecting the command.
4+
section: The AUTHORIZATION State
5+
rfc2119_level: MUST
6+
topics:
7+
- email
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-22"

‎corpus/elements/rfc-1225__protocol-element-the-dele-command-marks-a-specified-message-as.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-1225
2+
kind: protocol-element
3+
summary: The DELE command marks a specified message as deleted; actual deletion is deferred until the UPDATE state. Any subsequent reference to the deleted message-id returns an error. DELE also updates 'highest number accessed' if appropriate.
4+
section: The TRANSACTION State
5+
topics:
6+
- email
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-22"

0 commit comments

Comments
 (0)