Asymmetric IPv6 for IoT Networks
draft-jiang-asymmetric-ipv6-02

Document Type Active Internet-Draft (individual)
Last updated 2019-10-28
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                                           S. Jiang
Internet-Draft                              Huawei Technologies Co., Ltd
Intended status: Informational                                     G. Li
Expires: May 1, 2020                                 Huawei Technologies
                                                            B. Carpenter
                                                       Univ. of Auckland
                                                        October 29, 2019

                    Asymmetric IPv6 for IoT Networks
                     draft-jiang-asymmetric-ipv6-02

Abstract

   This document describes a new approach to IPv6 header compression for
   use in scenarios where minimizing packet size is crucial but routing
   performance must be maximised.

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 May 1, 2020.

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

Jiang, et al.              Expires May 1, 2020                  [Page 1]
Internet-Draft               Asymmetric IPv6                October 2019

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Proposed Solution . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Address Transformation at the Gateway . . . . . . . . . . . .   5
   4.  Routing without Decompression . . . . . . . . . . . . . . . .   6
   5.  Address Configuration . . . . . . . . . . . . . . . . . . . .   6
   6.  Compatibility with Existing Protocols . . . . . . . . . . . .   7
   7.  Relationship to Static Context Header Compression . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Change log [RFC Editor: Please remove] . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The large address space of IPv6 is essential for the massive
   expansion of the network edge that will be caused by "Internet of
   Things" (IoT) technology over low-power or 5G links.  However, the
   size of a raw IPv6 packet header causes difficulty due to the small
   maximum transmission units (MTU) allowed by typical low-power, low-
   cost link layers.  For 5G, this aspect is discussed in
   [I-D.ietf-dmm-5g-uplane-analysis].  Thus header compression,
   including address compression, is an important issue.  This decreases
   the size of raw packets, but compressed IP addresses are not
   routeable except by decompressing them completely in every forwarding
   node.  There are two issues here.  The first is the extra computation
   resource needed for compressing or decompressing in constrained IoT
   nodes.  The second is that full-length IPv6 routing will consume more
   memory to store routing tables and packet queues.  Such resource
   consumption is very undesirable in constrained nodes with limited
   storage, CPU power, and battery capacity.

   To mitigate these issues, here we propose a solution enabling the
   shortening of IPv6 addresses inside packets, and the routing of
   packets according to short addresses, without needing the overhead of
   a decompression step prior to route lookup.  Considering that the
   scale and size of edge networks may vary widely, different lengths of
   short address can be used in different domains.

   As an illustrative example, consider an edge network which is known
   to never require more than a few hundred nodes, which in most cases
   will communicate either with each other, or with application layer
Show full document text