FlexIP Addressing
draft-moskowitz-flexip-addressing-00

Document Type Active Internet-Draft (individual)
Last updated 2019-01-30
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                       R. Moskowitz
Internet-Draft                                            HTT Consulting
Intended status: Informational                                    GP. Li
Expires: August 3, 2019                                           S. Ren
                                                                  Huawei
                                                        January 30, 2019

                           FlexIP Addressing
                  draft-moskowitz-flexip-addressing-00

Abstract

   This memo proposes an unbounded Flexible Address Space (FAS),
   consisting of a publicly routable Global Address Part (GP) and a
   locally routable Local Address Part (LP).  It expands GP and LP to
   provide address privacy and special LP formats.  Use cases are also
   provided.

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 August 3, 2019.

Copyright Notice

   Copyright (c) 2019 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

Moskowitz, et al.        Expires August 3, 2019                 [Page 1]
Internet-Draft              FlexIP Addressing               January 2019

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Related Work  . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .   3
     2.2.  Notations . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Flexible Address System . . . . . . . . . . . . . . . . . . .   4
     3.1.  Infinite address space  . . . . . . . . . . . . . . . . .   4
     3.2.  Textual representation  . . . . . . . . . . . . . . . . .   5
     3.3.  Some Assignment Principles  . . . . . . . . . . . . . . .   6
   4.  Expanding into the Flexible Address System  . . . . . . . . .   6
     4.1.  Adding a MapID to the Local Part  . . . . . . . . . . . .   6
     4.2.  FlexIP Addressing Privacy Concerns  . . . . . . . . . . .   7
       4.2.1.  Address Privacy via a Cryptographic Mapping Function    7
     4.3.  Inbound FlexIP Address Considerations . . . . . . . . . .   8
     4.4.  Adding a MapID to the Global Part . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  FlexIP Addressing Local Part Use Cases . . . . . . .   9
     A.1.  Case 1: FlexIP METrie as Local Forwarding Part  . . . . .   9
     A.2.  Case 2: Layer 2 forwarding network  . . . . . . . . . . .  10
     A.3.  Case 3: IPv4/IPv6 forwarding network  . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This memo defines a new IP address system, called the Flexible
   Address System (FAS).  Compared to the conventional fixed length IP
   system, FAS is designed with 2 infinite address spaces, Global and
   Local, that can support variable length IP addresses, called flexible
   addresses.  FAS has a global hierarchical structure of flexible
   addresses from the perspective of management.  This hierarchical
   structure may also be used in a local part of FAS.

   It proposes a number of different formats for the Local Part,
   including IPv4/6 addresses and IEEE 802 48 and 64 bit MAC addresses
Show full document text