Intended status: Standards Track A. Eromenko September 2016
draft-eromenko-ipff-addressing-05

Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
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)
INTERNET-DRAFT
"Internet Protocol Five Fields - Addressing Architecture", 
Alexey Eromenko, 2016-09-29, 
<draft-eromenko-ipff-addressing-05.txt>
expiration date: 2017-03-29

Intended status: Standards Track
                                                             A. Eromenko
                                                          September 2016

                  IP Version 5 Addressing Architecture
             aka Internet Protocol "Five Fields" (IP-FF; draft)

Abstract

   This specification defines the addressing architecture of the IP
   Version 5 (IPFF) protocol.  The document includes the IPFF addressing
   model, text representations of IPFF addresses, definition of IPFF
   unicast addresses, anycast addresses, and multicast addresses.

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 http://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) 2016 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
   (http://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
   2. IPFF Addressing .................................................2
      2.1. Addressing Model ...........................................3
      2.2. Text Representation of Addresses ...........................4
      2.3. Text Representation of Address Prefixes ....................5
      2.4. Address Type Identification ................................6
      2.5. Unicast Addresses ..........................................6
           2.5.1. Private addresses ...................................7
           2.5.1. AutoIP addresses ....................................8
           2.5.3. The Unspecified Address .............................9
           2.5.4. The Loopback Address ................................9
           2.5.5. Global Unicast Addresses ............................9
      2.6. Anycast Addresses .........................................12
           2.6.1. Required Anycast Address ...........................12
      2.7. Multicast Addresses .......................................13
           2.7.1. Pre-Defined Multicast Addresses ....................15
           2.7.2. Silent Multicast Addresses..........................
      2.8. Broadcast Address .........................................
      2.9. A Node's Required Addresses ...............................
   3. Routing and Invalid Addresses ..................................
      3.1. Default Gateway ...........................................
      3.2. Special meaning of /50 subnet prefix ......................
      3.3. Non-contiguous wildcard masks .............................
      3.4. Not all subnets are born equal ............................
   4. Acknowledgements ...............................................

1.  Introduction

   This specification defines the addressing architecture of the IP
   Version 5 protocol.  It includes the basic formats for the various
   types of IPFF addresses (unicast, anycast, and multicast).

2.  IPFF Addressing

   The main benefit of IPFF, is that it looks familiar to all, 
   whom ever used IPv4, just with an extra field. So "five fields".

   Examples:

      192.168.510.971.11

      10.0.0.0.1

      382.201.769.25.133

   IPFF addresses are 50-bit identifiers for interfaces and sets of
   interfaces (where "interface" is as defined in Section 2 of [IPFF]).
   Each field is 10-bits wide, but due to human-memory constraits, 
   values are limited to "999" per field.

   Why go to the great length of dis-guard perfectly useable bits?
   Why not up to 1023.1023.1023.1023.1023, as 10-bit fields imply?
Show full document text