Local Naming Protocol -- LNP (v.1.0)
draft-schaller-dnsop-lnp-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Christian Schaller | ||
Last updated | 2019-08-17 (Latest revision 2019-02-13) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Local (or Lightweight) Naming Protocol (LNP) is an application- level protocol for local area networks. It is a distributed, stateless protocol which intents in resolving hostnames to ip addresses without the need of any Domain Name Server. In private local area networks, ip addressses are often dynamically allocated through DHCP. The LNP can be seen as a DNS extension, which uses broadcast udp messages (similar to ARP on IP-MAC-level) to request ip addresses for hosts with a given host- or domain-name. Thus it will be possible in dynamic local area networks to access ip-based services on hosts by their hostnames, without further management. Comments are solicited and should be addressed to the working group's mailing list at dnsop@ietf.org and/or the author(s).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)