Host Identification with Provider Independent Address
draft-shyam-hipi-00

Document Type Active Internet-Draft (individual)
Last updated 2020-01-29
Stream (None)
Intended RFC status (None)
Formats plain text 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)
INTERNET DRAFT                                          S. Bandyopadhyay
draft-shyam-hipi-00.txt                                 January 26, 2020
Intended status: Experimental
Expires: July 26, 2020

         Host Identification with Provider Independent Address
                        draft-shyam-hipi-00.txt

Abstract

   This is a protocol to identify a host with a provider independent
   address.  It is useful to identify a host uniquely in a multihomed
   environment where each host gets associated with more than one
   provider assigned addresses. By means of associating a host with a
   provider independent address, customers/customer networks will be
   able to retain their number even after changing their service
   provider(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 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."

   This Internet-Draft will expire on July 26, 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
   (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.

Bandyopadhyay             Expires July 26, 2020                 [Page 1]
Internet Draft     Host Identification with PI Address  January 26, 2020

1. Introduction

   Provider independent (PI) addressing can be conceived as naming a
   host with a number. It can be used by customer networks who would
   like to retain their number even after changing their service
   provider; also it is useful to designate a host uniquely if the
   customer network is multihomed. Just like in name services, as an
   address needs to be resolved corresponding to a name to initiate
   communication, the same is required for PI addressing. Each globally
   unique PI address will be associated to at least one global unicast
   provider assigned (PA) address. For a host with single interface,
   this number will be same as the number of service providers the
   customer network is associated with. This protocol resolves PA
   addresses associated with a PI address with the approach of DNS. Out
   of the entire internet protocol addresses, it expects same size of
   address space to be allocated to PI addresses as the address space
   allocated for provider assigned unicast addresses. As specified in
   section 3.2.1 of the architectural specification[1], it assumes
   address space with prefix ``00" will be assigned for PA addresses and
   address space with prefix ``01" will be assigned for PI addresses.

2. PI address resolution

   This section tries to come up with a solution for PI address
   resolution with the approach of DNS[2] with necessary differences.
   Just like name space in DNS, entire address range with prefix 01 will
   be the address space used by PI addresses. Servers that will hold the
   information of mapping between PI addresses and corresponding PA
   addresses will be called as PIMapServers and the programs that will
   be used to resolve addresses will be called as PIMapResolvers.

   In case of DNS where name is used in hierarchical format to resolve
   the addresses, PI address resolution will be based on the prefix of
   the PI address used for resolution.  The prefix is determined based
   on the architectural model used for the internet. Based on the prefix
   information addresses of a list of servers can be found out that will
   act as regional servers which will be used to resolve mapped PA
   addresses corresponding to that PI address. A prefix will serve a
   fixed address space within entire PI address space. Address space
   belonging to a prefix will be distributed within customer networks of
   heterogeneous sizes. Address space allocation and the mapping of
   associated PA address(es) will be assigned by a regional authority.
   The regional authority will be fully responsible for the operation of
   regional servers in that region.

   Like DNS, there are some root servers which will have some fixed
   addresses, under which there are some prefixes which will act as top-
   level-domains. In case of CIDR based hierarchy, these prefixes may be

Bandyopadhyay             Expires July 26, 2020                 [Page 2]
Show full document text