Skip to content

Commit 0d92209

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 194 new elements (2026-05-24)
1 parent ebd9a88 commit 0d92209

194 files changed

Lines changed: 1737 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-2486__design-rationale-the-nai-is-intended-to-be-used-by.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-2486
2+
kind: design-rationale
3+
summary: The NAI is intended to be used by the NAS both for identifying the user's home authentication server and as part of the process of opening a new tunnel to determine the tunnel endpoint, supporting VPN use cases via PPTP, L2F, L2TP, and IPsec.
4+
section: "2.3"
5+
topics:
6+
- vpn
7+
- ipsec
8+
- security
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__design-rationale-the-realm-portion-of-the-nai-grammar-permits.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2486
2+
kind: design-rationale
3+
summary: The realm portion of the NAI grammar permits realms beginning with a digit (e.g., 3com.com), unlike the BNF in RFC 1035 (DNS). This change was made to reflect current practice, as such FQDNs are commonly used and accepted by current software.
4+
section: "2.4"
5+
topics:
6+
- dns
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__design-rationale-using-an-fqdn-as-the-realm-name-does.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2486
2+
kind: design-rationale
3+
summary: Using an FQDN as the realm name does not imply use of the DNS for location of the authentication server or for authentication routing. Existing roaming implementations handle authentication server location via local proxy configuration files, not DNS, though DNS SRV records (RFC 2052) could be used.
4+
section: "6"
5+
topics:
6+
- dns
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__interoperability-note-invalid-nai-examples-include-a-realm-without-a.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-2486
2+
kind: interoperability-note
3+
summary: 'Invalid NAI examples include: a realm without a dot (fred@foo), realm labels with underscores (fred@foo_9.com), empty username (@howard.edu), multiple at-signs (fred@bigco.com@smallco.com), and colons or semicolons in the username.'
4+
section: "3"
5+
topics:
6+
- security
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__interoperability-note-the-nai-may-not-necessarily-be-the-same.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2486
2+
kind: interoperability-note
3+
summary: The NAI may not necessarily be the same as the user's e-mail address or the userID submitted in an application-layer authentication. Implementations must not assume these identifiers are equivalent.
4+
section: "2.1"
5+
topics:
6+
- email
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__interoperability-note-there-is-no-requirement-that-the-nai-represent.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2486
2+
kind: interoperability-note
3+
summary: There is no requirement that the NAI represent a valid email address; the NAI realm is an administrative namespace for roaming that happens to use FQDN syntax but is semantically distinct from an SMTP address.
4+
section: "6"
5+
topics:
6+
- email
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__normative-requirement-devices-handling-nais-must-support-an-nai-length.yaml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
document: rfc-2486
2+
kind: normative-requirement
3+
summary: Devices handling NAIs MUST support an NAI length of at least 72 octets. NAS vendors may need to modify their devices to comply.
4+
section: "2.4"
5+
rfc2119_level: MUST
6+
topics:
7+
- radius
8+
- security
9+
extracted_by: claude-sonnet-4-6
10+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__normative-requirement-nai-realm-names-are-required-to-be-unique.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
document: rfc-2486
2+
kind: normative-requirement
3+
summary: NAI realm names are required to be unique, and the rights to use a given NAI realm for roaming purposes are obtained coincident with acquiring rights to use the corresponding fully qualified domain name (FQDN).
4+
section: "6"
5+
rfc2119_level: REQUIRED
6+
topics:
7+
- dns
8+
- security
9+
- registry
10+
extracted_by: claude-sonnet-4-6
11+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__protocol-element-the-network-access-identifier-nai-is-the-userid.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2486
2+
kind: protocol-element
3+
summary: The Network Access Identifier (NAI) is the userID submitted by the client during PPP authentication, taking the form 'user@realm'. Its purpose is to identify the user and assist in routing the authentication request to the home server.
4+
section: "2.1"
5+
topics:
6+
- radius
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

‎corpus/elements/rfc-2486__protocol-element-the-realm-portion-is-defined-as-a-dot.yaml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
document: rfc-2486
2+
kind: protocol-element
3+
summary: The realm portion is defined as a dot-separated sequence of labels, where each label begins with a letter or digit (let-dig) and may contain hyphens. Underscores are not permitted in realm labels.
4+
section: "3"
5+
topics:
6+
- dns
7+
- security
8+
extracted_by: claude-sonnet-4-6
9+
extracted_at: "2026-05-24"

0 commit comments

Comments
 (0)