Subnet ID Deprecation for IPv6
draft-dykim-6man-sid6-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-03
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                                             DY Kim
Internet-Draft                                               Independent
Intended status: Experimental                          September 3, 2018
Expires: March 7, 2019

                     Subnet ID Deprecation for IPv6
                        draft-dykim-6man-sid6-00

Abstract

   Deprecation of the subnet ID in IPv6 networking is proposed; the
   subnet ID is set to zero so that all nodes in a site carry the same
   prefix.  While the procedures for neighbor discovery and duplicate
   address detection have to be changed, possible simplification gains
   in IPv6 networking including that of intra-site host- and subnet-
   mobility might be worth the modification.  Site-external behaviors
   don't change through this modification, enabling incremental
   deployment of the proposal.  Sites of manageable sizes for which
   scalability is not much a critical issue might consider the mode of
   operation proposed in this document.

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 March 7, 2019.

Copyright Notice

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

DY Kim                    Expires March 7, 2019                 [Page 1]
Internet-Draft                    SID6                    September 2018

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  SID6 Construction . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  IPv6 Address  . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Neighbor Discovery  . . . . . . . . . . . . . . . . . . .   5
     3.3.  Duplicate Address Detection . . . . . . . . . . . . . . .   7
     3.4.  Interior Gateway Protocols  . . . . . . . . . . . . . . .   8
     3.5.  Other Address-Related Protocols . . . . . . . . . . . . .   8
     3.6.  Generalization  . . . . . . . . . . . . . . . . . . . . .   8
   4.  Consequencies . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Recursive Networking  . . . . . . . . . . . . . . . . . .  10
     4.2.  No Locator/ID Separation  . . . . . . . . . . . . . . . .  10
     4.3.  Inherent Interior Mobility  . . . . . . . . . . . . . . .  11
     4.4.  Faster Interior Mobility  . . . . . . . . . . . . . . . .  11
     4.5.  Legacy Exterior Mobility  . . . . . . . . . . . . . . . .  12
     4.6.  Legacy Migration and Multihoming  . . . . . . . . . . . .  12
     4.7.  Usual Use of NPTv6 and ULA  . . . . . . . . . . . . . . .  13
     4.8.  Incremental Deployability . . . . . . . . . . . . . . . .  13
     4.9.  Prefix Aggregation and Scalability  . . . . . . . . . . .  13
     4.10. Incentives for Deployment . . . . . . . . . . . . . . . .  13
   5.  Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     8.2.  Informartive References . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   The idea of IPv4 subnet has been imported intact into IPv6 networking
   so that each subnet (link) in an IPv6 site is assigned a separate
   subnet ID (SID).  As a result, the IPv6 host has to change the link
   prefix every time it moves from one link to another even within the
   same site or routing domain; you have to install MIPv6 agents [MIPv6]
   on every intra-site router and a MIP6 client on every mobile node in
Show full document text