RFC1498 · On the Naming and Binding of Network Destinations
On the Naming and Binding of Network Destinations
This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas: First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. This memo provides information for the Internet community. It does not specify an Internet standard.
IETF · RFCОфициальная английская аннотация
This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas: First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. This memo provides information for the Internet community. It does not specify an Internet standard.
{
"id": "RFC1498",
"number": 1498,
"title_en": "On the Naming and Binding of Network Destinations",
"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": "This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas: First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. This memo provides information for the Internet community. It does not specify an Internet standard.",
"authors": [
"J. Saltzer"
],
"organizations": [],
"publication_date": "1993-08-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "informational",
"lifecycle_ru": "Справочный",
"stream": "Legacy",
"stream_ru": "Исторический поток",
"area": "",
"area_ru": "",
"working_group": "",
"source_draft": "",
"page_count": 10,
"doi": "10.17487/RFC1498",
"keywords": [
"NAMES",
"Addresses",
"Routes",
"Objects",
"Nodes",
"Paths"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc1498/",
"html": "https://www.rfc-editor.org/rfc/rfc1498.html",
"txt": "https://www.rfc-editor.org/rfc/rfc1498.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc1498/"
}
}