Skip to content

Commit 5cf1365

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 200 new elements (2026-05-24)
1 parent 378b8b5 commit 5cf1365

200 files changed

Lines changed: 1823 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-2533__design-rationale-disjunctive-normal-form-or-of-ands-was-chosen.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: design-rationale
3+
summary: Disjunctive normal form (OR of ANDs) was chosen over the more common clausal/conjunctive normal form because the goal of feature set matching is to find at least one satisfiable disjunction, which maps more naturally to DNF. The feature tag interdependence requires Predicate Calculus rather than simpler Propositional Calculus.
4+
section: "5"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__design-rationale-no-rules-are-defined-for-combining-quality-values.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: design-rationale
3+
summary: No rules are defined for combining quality values across AND-combined sub-predicates; preference information is only meaningful at the top-level OR clause level. Combining sub-predicate preferences is considered an unresolved research problem and is left to specific protocol extensions.
4+
section: "3.7"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__design-rationale-quality-value-parameters-are-permitted-on-any-sub.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: design-rationale
3+
summary: 'Quality value parameters are permitted on any sub-expression in the syntax (not just top-level) for two reasons: (a) to ease composition of separately constructed predicates, and (b) to provide an extensible tagging mechanism for future uses such as explicit matching-rule specification.'
4+
section: "4.1"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__design-rationale-the-feature-set-framework-starts-from-the-assumption.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: design-rationale
3+
summary: The feature set framework starts from the assumption that any feature collection is possible, then progressively excludes instances via Boolean predicates. This predicate-as-relation approach allows the same expression form to describe sender, receiver, and file format capabilities uniformly.
4+
section: "3.3"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__design-rationale-the-ldap-search-filter-syntax-rfc-2254-was.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: design-rationale
3+
summary: The LDAP search filter syntax (RFC 2254) was adopted for feature predicate notation because a feature collection is analogous to a directory entry (named values), and LDAP filters provide a well-understood structure that is easy to parse. Differences include absence of substring/approximate matching and the addition of quality values.
4+
section: "3.5"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__design-rationale-when-a-characteristic-has-different-constraints-for-different.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: design-rationale
3+
summary: When a characteristic has different constraints for different parts of a resource (e.g., MRC stripe-size vs. JBIG stripe-size), separate feature tags must be used. A single feature tag within a conjunction can only hold one value; attempting to assign it two values produces an unsatisfiable predicate.
4+
section: "7.2"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__interoperability-note-feature-values-with-comparison-semantics-not-covered-by.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: interoperability-note
3+
summary: Feature values with comparison semantics not covered by this framework (e.g., multi-part version strings like 'x.y.z') are outside the scope of this specification. Specific applications may define handling, and future work may define extensible data types.
4+
section: "6.3"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__interoperability-note-this-document-s-use-of-feature-set-differs.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2533
2+
kind: interoperability-note
3+
summary: This document's use of 'feature set' differs from Transparent Content Negotiation in HTTP (RFC 2295), which uses the term with a slightly different meaning. Quality value semantics here are also more restricted than those in RFC 2068 HTTP Accept headers.
4+
section: "2"
5+
topics:
6+
- http
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__interoperability-note-unit-designators-with-different-tokens-e-g-default.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-2533
2+
kind: interoperability-note
3+
summary: Unit designators with different tokens (e.g., default dpcm vs. 'dpi') are treated as distinct features during matching, so '(res=200)' and '(res=200dpi)' will not fail to match each other unless a processor with explicit unit knowledge intervenes. Applications should ensure consistent unit usage to avoid spurious mismatches.
4+
section: "6.2"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2533__normative-requirement-feature-comparisons-with-and-without-unit-designators-or.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-2533
2+
kind: normative-requirement
3+
summary: Feature comparisons with and without unit designators, or with different unit designators, are treated as if they involve different features during matching. A predicate '(res=200)' does not automatically match '(res=200dpi)', even if the numeric values are equivalent.
4+
section: "6.2"
5+
rfc2119_level: MUST
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-05-24"

0 commit comments

Comments
 (0)