Skip to content

Commit 36dcae3

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 202 new elements (2026-05-24)
1 parent 7e57b69 commit 36dcae3

202 files changed

Lines changed: 1648 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-2445__design-rationale-floating-time-date-time-without-utc-designator-or.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2445
2+
kind: design-rationale
3+
summary: Floating time (DATE-TIME without UTC designator or TZID) represents the same hour/minute/second regardless of time zone — for example, 'busy 11 AM to 1 PM daily in any time zone.' Floating time SHOULD only be used where that semantics is actually desired; fixed times MUST use UTC or local-with-TZID.
4+
section: 4.3.5
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__design-rationale-the-default-character-set-for-an-icalendar-object.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2445
2+
kind: design-rationale
3+
summary: The default character set for an iCalendar object is UTF-8 (RFC 2279). There is no per-property character set parameter; the MIME 'charset' Content-Type parameter applies to the entire body part. Use of non-US-ASCII-compatible character sets is NOT recommended.
4+
section: 4.1.4
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__design-rationale-the-optinfo-mime-parameter-may-only-convey-semantics.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2445
2+
kind: design-rationale
3+
summary: The 'optinfo' MIME parameter MAY only convey semantics already present in the parsed iCalendar body and consistent with it — for example, conveying an Attendee's response status. It cannot introduce new semantics or override the body, ensuring that parsing the body part always produces an authoritative result.
4+
section: "3.2"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__interoperability-note-the-icalendar-format-is-based-on-the-earlier.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2445
2+
kind: interoperability-note
3+
summary: 'The iCalendar format is based on the earlier vCalendar (VCAL) industry specification and reuses elements from RFC 2425, though iCalendar is not a profile of RFC 2425. It is designed to be transport-independent: usable over SMTP, HTTP, file systems, clipboard, drag/drop, and point-to-point links.'
4+
section: "3.6"
5+
topics:
6+
- email
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__normative-requirement-an-individual-vtimezone-calendar-component-must-be-specified.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2445
2+
kind: normative-requirement
3+
summary: An individual VTIMEZONE calendar component MUST be specified for each unique TZID parameter value referenced within the iCalendar object. A SOLIDUS prefix on a TZID value indicates membership in a globally defined time zone registry.
4+
section: 4.2.19
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__normative-requirement-binary-content-information-in-an-icalendar-object-should.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2445
2+
kind: normative-requirement
3+
summary: Binary content information in an iCalendar object SHOULD be referenced using a URI within a property value. If inline binary is necessary, it MUST be encoded using BASE64 (RFC 2045), the ENCODING property parameter MUST be specified, and binary content external to the object MUST be referenced by a URI.
4+
section: 4.1.3
5+
rfc2119_level: SHOULD
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__normative-requirement-if-a-property-s-value-type-is-value.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2445
2+
kind: normative-requirement
3+
summary: If a property's value type is VALUE=BINARY, the inline encoding parameter MUST be specified as ENCODING=BASE64. No additional BACKSLASH character encoding is defined for the BINARY value type.
4+
section: 4.2.7
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__normative-requirement-lines-of-text-should-not-be-longer-than.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2445
2+
kind: normative-requirement
3+
summary: Lines of text SHOULD NOT be longer than 75 octets, excluding the line break. Long lines SHOULD be folded by inserting a CRLF immediately followed by a single linear white space character (SPACE or HTAB) between any two characters.
4+
section: "4.1"
5+
rfc2119_level: SHOULD
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__normative-requirement-property-parameter-values-that-contain-colon-semicolon-or.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2445
2+
kind: normative-requirement
3+
summary: Property parameter values that contain COLON, SEMICOLON, or COMMA characters MUST be specified as quoted-string text values. Property parameter values MUST NOT contain the DOUBLE-QUOTE character; DOUBLE-QUOTE is used solely as a quoted-string delimiter.
4+
section: "4.2"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2445__normative-requirement-the-method-mime-content-type-parameter-must-be.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2445
2+
kind: normative-requirement
3+
summary: The 'method' MIME content-type parameter MUST be the same value as the METHOD component property in the iCalendar object. If one is present, the other MUST also be present.
4+
section: "3.2"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

0 commit comments

Comments
 (0)