[Docs] [txt|pdf|xml|html] [Tracker] [Email] [Nits]

Versions: 00

Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Updates: rfc4191, rfc4861 (if approved)                    June 05, 2017
Intended status: Standards Track
Expires: December 7, 2017


                            The AERO Address
                   draft-templin-6man-aeroaddr-00.txt

Abstract

   IPv6 interfaces are required to have a link-local address that is
   unique on the link.  Nodes normally derive a link local address
   through the use of IPv6 Stateless Address Autoconfiguration (SLAAC)
   along with Duplicate Address Detection (DAD).  This document presents
   a method for a node to construct a link-local address that is assured
   to be unique on the link when the node has already received a
   delegated prefix.  This is through the construction of a link-local
   address format known as the AERO address.

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 December 7, 2017.

Copyright Notice

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



Templin                 Expires December 7, 2017                [Page 1]


Internet-Draft                AERO Address                     June 2017


   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 . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  The AERO Address  . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Intended Use Cases  . . . . . . . . . . . . . . . . . . . . .   3
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .   3
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   IPv6 interfaces are required to have a link-local address that is
   unique on the link [RFC2460][RFC4861].  Nodes normally derive a link
   local address through the use of IPv6 StateLess Address Auto
   Configuration (SLAAC) along with Duplicate Address Detection (DAD)
   [RFC4862].  This document presents a method for a node to construct a
   link-local address that is assured to be unique on the link when the
   node has already received a delegated prefix.  This is through the
   construction of a link-local address format known as the AERO
   address.

2.  Terminology

   The terminology in the normative references applies.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].  Lower case
   uses of these words are not to be interpreted as carrying RFC2119
   significance.

3.  The AERO Address

   An AERO address is an IPv6 link-local address with an interface
   identifier based on a prefix that has been delegated to a node for
   its own exclusive use.  AERO addresses begin with the prefix
   fe80::/64 and include in the interface identifier (i.e., the lower 64



Templin                 Expires December 7, 2017                [Page 2]


Internet-Draft                AERO Address                     June 2017


   bits) a 64-bit prefix taken from one of the node's delegated
   prefixes.  For example, if the node receives the IPv6 prefix:

      2001:db8:1000:2000::/64

   it constructs its corresponding AERO addresses as:

      fe80::2001:db8:1000:2000

   After constructing the AERO address, the node can assign the address
   to the interface over which it received the prefix delegation.  Since
   the prefix delegation is already known to be unique, the node need
   not use Duplicate Address Detection (DAD) to test the AERO address
   for uniqueness since no other node on the link will configure the
   same address.

   AERO addresses can be constructed for any IPv6 prefix that is no
   longer than /64.  For prefixes shorter than /64, the AERO address is
   constructed based on the lowest-numbered /64 prefix taken from the
   shorter prefix.  For example, if the node received the IPv6 prefix:

      2001:db8:1000:2000::/56

   it constructs its corresponding AERO addresses as:

      fe80::2001:db8:1000:2000

4.  Intended Use Cases

   The AERO address is intended for use by mobile networks that comprise
   a mobile router and a tethered network of "Internet of Things"
   devices that travel together with the router as a single unit.  The
   mobile router assigns the AERO address to its upstream interface over
   which it receives a prefix delegation from a delegating router.  The
   manner for receiving the delegated prefix could be through static
   configuration or some automated prefix delegation service.

   Many other use case scenarios are possible (e.g., home networks) but
   the above case extends to multitudes of applications, e.g., a cell
   phone and its associated devices, an airplane and its on-board
   network, etc.

5.  Implementation Status

   Public domain implementations exist that use the AERO address format
   as described in this document.





Templin                 Expires December 7, 2017                [Page 3]


Internet-Draft                AERO Address                     June 2017


6.  IANA Considerations

   This document introduces no IANA considerations.

7.  Security Considerations

   TBD

8.  Acknowledgements

   This work was sponsored through several ongoing initiatives,
   including 1) the NASA Safe Autonomous Systems Operation (SASO)
   program under NASA contract number NNA16BD84C, 2) the FAA SE2025
   contract number DTFAWA-15-D-00030, 3) the Boeing Information
   Technology (BIT) MobileNet program, and 4) the Boeing Research &
   Technology (BR&T) enterprise autonomy program.

9.  References

9.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
              December 1998, <http://www.rfc-editor.org/info/rfc2460>.

   [RFC4861]  Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
              "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
              DOI 10.17487/RFC4861, September 2007,
              <http://www.rfc-editor.org/info/rfc4861>.

   [RFC4862]  Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
              Address Autoconfiguration", RFC 4862,
              DOI 10.17487/RFC4862, September 2007,
              <http://www.rfc-editor.org/info/rfc4862>.

9.2.  Informative References

   [I-D.templin-aerolink]
              Templin, F., "Asymmetric Extended Route Optimization
              (AERO)", draft-templin-aerolink-75 (work in progress), May
              2017.





Templin                 Expires December 7, 2017                [Page 4]


Internet-Draft                AERO Address                     June 2017


Author's Address

   Fred L. Templin (editor)
   Boeing Research & Technology
   P.O. Box 3707
   Seattle, WA  98124
   USA

   Email: fltemplin@acm.org










































Templin                 Expires December 7, 2017                [Page 5]


Html markup produced by rfcmarkup 1.123, available from https://tools.ietf.org/tools/rfcmarkup/