Local Naming Protocol -- LNP (v.1.0)
draft-schaller-dnsop-lnp-00

Document Type Active Internet-Draft (individual)
Last updated 2019-02-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
lnp                                                          C. Schaller
Internet-Draft                                                Schallsoft
Intended-Status: Elective                              February 11, 2019

                   Local Naming Protocol -- LNP (v.1.0)
                        draft-schaller-dnsop-lnp-00

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).
    
    
Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.
   
   
   
   
   
Schaller                 Expires August 11, 2019                [Page 1]

Internet-Draft                 LNP (v.1.0)                 February 2019

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.
   

   
   
Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Standalone LNP  . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  DNS extended LNP  . . . . . . . . . . . . . . . . . . . .   3     
   2.  Protocol version 1.0  . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Wildcards . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Concurrent replies  . . . . . . . . . . . . . . . . . . .   4
     2.3.  No host responding  . . . . . . . . . . . . . . . . . . .   4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5
   
   
   

   
1. Introduction

    In private local area networks or wireless LANs, today mainly DHCP 
    [RFC2131] managed ip address allocation is used. Since the equip-
    ment on the market does not ship with integrated DNS servers, which
    update their records when hosts attach to or detach from the net-
    work, there is less help for private users or user applications 
    trying to access devices services over ip addresses. Actually no 
    service is out of the box available for all operating systems. 
    Microsoft Windows ships with NetBios [RFC 1002], which allows name
    based access, however first after activation of file-sharing. 
    Apples MacOS is delivered with bonjour [RFC 6763], which runs out 
    of the box. Linux and Unix systems can do both, however after 
    explicit installation setup. All those systems are able to use DNS
    [RFC 1035] when connected to ip networks. So why not extend the 
    functionality of the distributed Domain Name System, which already
    has the task to resolv hostnames to ip addresses.
           
    
Schaller                 Expires August 11, 2019                [Page 2]

Internet-Draft                 LNP (v.1.0)                 February 2019

1.1. Standalone LNP
    
    The standalone implementation of LNP uses a UDP broadcast message to
    query the ip address of a host. Therefore the message contains the
    full qualified name of a host connected to the local network. All 
Show full document text