Hierarchically Located Addressing and Routing Protocol
draft-anonymous-rtgwg-hlarp-00

Document Type Active Internet-Draft (individual)
Last updated 2020-01-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
Network Working Group
Internet-Draft                                               Independant
Expires: July 5, 2020                                    January 2, 2020

         Hierarchically Located Addressing and Routing Protocol
                     draft-anonymous-rtgwg-hlarp-00

Abstract

   This internet-draft describes a protocol with an addressing scheme
   where members of the internet are addressed by their physical
   addresses and by an implementing internet router that can contact
   them.  The packets sent by the protocol include handshake messages,
   client data, and the status of the data being sent.  A routing
   procedure is suggested according to special addresses that carry
   information about the region of a router.

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."

   This Internet-Draft will expire on July 5, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   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

                          Expires July 5, 2020                  [Page 1]
Internet-Draft                    HLARP                     January 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

1.1.  Motivation

   Allocated IP addresses require a fee, are only temporary, and require
   an organization.  An ISP can offer these services at a much greater
   fee.  This internet-draft attempts to provide the permanence of MAC
   addresses and other types of physical addresses for the use of the
   internet.  The infrastructure for physical addressing is already in
   place and already identifies a single transmitting machine.  With IP,
   transmitting machines are identified once more.  The IP addresses are
   distributed for routing purposes and for identification purposes,
   although addressing for routing can be set up without identification.

1.2.  Terminology

      Rank - length of one coordinate

      Root - no coordinates

      Member - user of the HLARP network

      Network Member - member that directly contacts a relay and
      contacts at least one host member

      Host Member - member that represents the user

      Relay - router capable of transferring data between regions that
      implements the described protocol

1.3.  Scope

   This draft focuses on routing and addressing.  The described protocol
   is to be operated between the physical and internet layers.  The
   draft provides a replacement for routing and addressing for IP but
   for no other IP functionality.  Other functionality is provided by
   the internet header within a data packet.  The described protocol
   utilizes addressing features of the physical layer.

2.  Draft Notes

   This notice has been preserved because this is still a draft, and
   this protocol is NOT standardized.  The IETF does NOT permit
   implementors that advertise conformance and/or implementation with
   the described protocol.  This does NOT specify a protocol, but

                          Expires July 5, 2020                  [Page 2]
Internet-Draft                    HLARP                     January 2020

   describe a proposed protocol to the readers.  A mention of
   specification of the discribed protocol has been accidentally
   included and should be changed and interpreted as this is a
   description.  Any IANA registration requested has NOT been made.  The
   draft has been submitted using a Tor exit node and the owner of the
   displayed IP address is NOT responsible for the content of this
   document.  The rules governing the IETF do NOT permit independant
   publication due to the significant IANA registration of IPv14
   (Section 6).

3.  Addressing

   In HLARP, two types of addresses are used.  A member address is used
   to identify a member of the network.  Internet routers that wish to
   abide by the protocol have no need to use a member address and need a
Show full document text