In order to provide roaming services, it is necessary to have a standardized method for identifying users. This document defines the syntax for the Network Access Identifier (NAI), the user identity submitted by the client during network authentication. "Roaming" may be loosely defined as the ability to use any one of multiple Internet Service Providers (ISPs), while maintaining a formal, \%customer-vendor relationship with only one. Examples of where roaming capabilities might be required include ISP "confederations" and \%ISP-provided corporate network access support. This document is a revised version of RFC 2486, which originally defined NAIs. Enhancements include international character set and privacy support, as well as a number of corrections to the original RFC. [STANDARDS-TRACK]
IETF · RFCОфициальная английская аннотация
In order to provide roaming services, it is necessary to have a standardized method for identifying users. This document defines the syntax for the Network Access Identifier (NAI), the user identity submitted by the client during network authentication. "Roaming" may be loosely defined as the ability to use any one of multiple Internet Service Providers (ISPs), while maintaining a formal, \%customer-vendor relationship with only one. Examples of where roaming capabilities might be required include ISP "confederations" and \%ISP-provided corporate network access support. This document is a revised version of RFC 2486, which originally defined NAIs. Enhancements include international character set and privacy support, as well as a number of corrections to the original RFC. [STANDARDS-TRACK]
{
"id": "RFC4282",
"number": 4282,
"title_en": "The Network Access Identifier",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "In order to provide roaming services, it is necessary to have a standardized method for identifying users. This document defines the syntax for the Network Access Identifier (NAI), the user identity submitted by the client during network authentication. \"Roaming\" may be loosely defined as the ability to use any one of multiple Internet Service Providers (ISPs), while maintaining a formal, \\%customer-vendor relationship with only one. Examples of where roaming capabilities might be required include ISP \"confederations\" and \\%ISP-provided corporate network access support. This document is a revised version of RFC 2486, which originally defined NAIs. Enhancements include international character set and privacy support, as well as a number of corrections to the original RFC. [STANDARDS-TRACK]",
"authors": [
"B. Aboba",
"M. Beadles",
"J. Arkko",
"P. Eronen"
],
"organizations": [],
"publication_date": "2005-12-01",
"current_status": "PROPOSED STANDARD",
"current_status_ru": "Предлагаемый стандарт",
"publication_status": "PROPOSED STANDARD",
"publication_status_ru": "Предлагаемый стандарт",
"lifecycle": "superseded",
"lifecycle_ru": "Заменён",
"stream": "IETF",
"stream_ru": "IETF",
"area": "sec",
"area_ru": "Безопасность",
"working_group": "radext",
"source_draft": "draft-ietf-radext-rfc2486bis-06",
"page_count": 16,
"doi": "10.17487/RFC4282",
"keywords": [
"NAI",
"nai",
"roaming",
"tunneling"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [
"RFC2486"
],
"obsoleted_by": [
"RFC7542"
],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc4282/",
"html": "https://www.rfc-editor.org/rfc/rfc4282.html",
"txt": "https://www.rfc-editor.org/rfc/rfc4282.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc4282/"
}
}