Skip to content

Commit 5946f1b

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 257 new elements (2026-07-06)
1 parent 7a78f67 commit 5946f1b

257 files changed

Lines changed: 2409 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-8738__design-rationale-because-rfc-6066-prohibits-ip-addresses-in-the.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8738
2+
kind: design-rationale
3+
summary: Because RFC 6066 prohibits IP addresses in the TLS SNI HostName field, the reverse DNS mapping (IN-ADDR.ARPA / IP6.ARPA) is used as a workaround to allow the "tls-alpn-01" challenge to function with IP address identifiers without violating TLS extension constraints.
4+
section: "6"
5+
topics:
6+
- acme
7+
- tls
8+
- ip
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__interoperability-note-ip-identifiers-may-be-used-with-the-existing.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8738
2+
kind: interoperability-note
3+
summary: IP identifiers MAY be used with the existing "http-01" and "tls-alpn-01" challenges defined in RFC 8555 and RFC 8737 respectively, extending those challenge types to cover IP address validation without defining new challenge mechanisms.
4+
section: "4"
5+
topics:
6+
- acme
7+
- pkix
8+
- ip
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__normative-requirement-an-acme-server-wishing-to-request-proof-that.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8738
2+
kind: normative-requirement
3+
summary: An ACME server wishing to request proof that a user controls an IPv4 or IPv6 address MUST create an authorization with the identifier type "ip".
4+
section: "3"
5+
rfc2119_level: MUST
6+
topics:
7+
- acme
8+
- pkix
9+
- ip
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__normative-requirement-because-rfc-6066-does-not-permit-ip-addresses.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8738
2+
kind: normative-requirement
3+
summary: Because RFC 6066 does not permit IP addresses in the SNI HostName field, the server MUST use the IN-ADDR.ARPA or IP6.ARPA reverse mapping of the IP address as the SNI HostName field value for "tls-alpn-01" challenges.
4+
section: "6"
5+
rfc2119_level: MUST
6+
topics:
7+
- acme
8+
- tls
9+
- ip
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__normative-requirement-for-the-http-01-challenge-with-ip-identifiers.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8738
2+
kind: normative-requirement
3+
summary: For the "http-01" challenge with IP identifiers, the Host header field MUST be set to the IP address being validated per RFC 7230, using RFC 1123 format for IPv4 and RFC 5952 format for IPv6.
4+
section: "5"
5+
rfc2119_level: MUST
6+
topics:
7+
- acme
8+
- http
9+
- ip
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__normative-requirement-for-the-tls-alpn-01-challenge-the-subjectaltname.yaml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
document: rfc-8738
2+
kind: normative-requirement
3+
summary: For the "tls-alpn-01" challenge, the subjectAltName extension in the validation certificate MUST contain a single iPAddress that matches the address being validated.
4+
section: "6"
5+
rfc2119_level: MUST
6+
topics:
7+
- acme
8+
- tls
9+
- pkix
10+
- ip
11+
extracted_by: claude-sonnet-4-6
12+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__normative-requirement-the-existing-dns-01-challenge-must-not-be.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8738
2+
kind: normative-requirement
3+
summary: The existing "dns-01" challenge MUST NOT be used to validate IP identifiers.
4+
section: "7"
5+
rfc2119_level: MUST NOT
6+
topics:
7+
- acme
8+
- dns
9+
- ip
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__normative-requirement-the-value-field-of-an-ip-identifier-must.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8738
2+
kind: normative-requirement
3+
summary: The value field of an "ip" identifier MUST contain the textual form of the address as defined in RFC 1123 Section 2.1 for IPv4 and RFC 5952 Section 4 for IPv6.
4+
section: "3"
5+
rfc2119_level: MUST
6+
topics:
7+
- acme
8+
- pkix
9+
- ip
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__normative-requirement-when-using-http-01-or-tls-alpn-01.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-8738
2+
kind: normative-requirement
3+
summary: When using "http-01" or "tls-alpn-01" challenges with IP identifiers, the initial DNS resolution step MUST be skipped and the IP address used for validation MUST be the value of the identifier.
4+
section: "4"
5+
rfc2119_level: MUST
6+
topics:
7+
- acme
8+
- pkix
9+
- ip
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-07-06"

‎corpus/elements/rfc-8738__protocol-element-the-ip-identifier-type-uses-the-type-string.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-8738
2+
kind: protocol-element
3+
summary: 'The IP identifier type uses the type string "ip" with the value field containing the textual form of the IP address: RFC 1123 Section 2.1 format for IPv4 and RFC 5952 Section 4 format for IPv6. For example: {"type": "ip", "value": "2001:db8::1"}.'
4+
section: "3"
5+
topics:
6+
- acme
7+
- pkix
8+
- ip
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-07-06"

0 commit comments

Comments
 (0)