Deploying Identifier-Locator Addressing (ILA) in datacenter networks
draft-lapukhov-ila-deployment-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
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                                        P. Lapukhov
Internet-Draft                                                  Facebook
Intended status: Informational                          October 31, 2016
Expires: May 4, 2017

  Deploying Identifier-Locator Addressing (ILA) in datacenter networks
                    draft-lapukhov-ila-deployment-01

Abstract

   Identifier-Locator Addressing architecture defined in
   [I-D.herbert-nvo3-ila] proposes the use of locator-identifier split
   in IPv6 address to realize workload mobility and more efficient use
   of network resources.  This document describes how ILA can be
   implemented in datacenter using BGP as the control-plane protocol.
   Generally speaking, ILA could be built using different control
   planes, and BGP is one particular instantiation.  The motivation is
   BGP being a well-known protocol, sufficient for small to medium size
   deployments, on scale of few millions of identifier to locator
   mappings.  Defining more generic and scalable control plane variants
   is outside of scope of 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 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 May 4, 2017.

Copyright Notice

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

Lapukhov                   Expires May 4, 2017                  [Page 1]
Internet-Draft        draft-lapukhov-ila-deployment         October 2016

   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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  ILA deployment process  . . . . . . . . . . . . . . . . . . .   5
   4.  Preparing the network . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Data-center network topology  . . . . . . . . . . . . . .   6
     4.2.  Configuring locator addressing  . . . . . . . . . . . . .   7
   5.  Deploying ILA routers . . . . . . . . . . . . . . . . . . . .  10
     5.1.  ILA Redirect Message  . . . . . . . . . . . . . . . . . .  10
     5.2.  Configuration parameters  . . . . . . . . . . . . . . . .  10
     5.3.  ILA router operation  . . . . . . . . . . . . . . . . . .  11
     5.4.  Scaling considerations  . . . . . . . . . . . . . . . . .  12
   6.  Deploying ILA hosts . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Configuration parameters  . . . . . . . . . . . . . . . .  13
     6.2.  Providing task isolation  . . . . . . . . . . . . . . . .  13
     6.3.  ILA host operation  . . . . . . . . . . . . . . . . . . .  14
   7.  Using BGP as the ILA control plane  . . . . . . . . . . . . .  16
     7.1.  BGP topology  . . . . . . . . . . . . . . . . . . . . . .  16
     7.2.  Any-to-any mapping distribution . . . . . . . . . . . . .  17
     7.3.  Hub-and-spoke mapping distribution  . . . . . . . . . . .  17
   8.  Push vs pull mapping distribution modes . . . . . . . . . . .  18
   9.  ILA address management  . . . . . . . . . . . . . . . . . . .  18
     9.1.  Decentralized address management  . . . . . . . . . . . .  18
     9.2.  Centralized address management  . . . . . . . . . . . . .  19
     9.3.  Role of Task scheduler  . . . . . . . . . . . . . . . . .  19
   10. ILA domain federation . . . . . . . . . . . . . . . . . . . .  20
   11. Operational Considerations  . . . . . . . . . . . . . . . . .  20
     11.1.  Operational procedures for ILA routers . . . . . . . . .  21
     11.2.  ICMPv6 Message generation by transit devices . . . . . .  21
     11.3.  Multicast routing  . . . . . . . . . . . . . . . . . . .  22
     11.4.  Potential ILA mapping table complications  . . . . . . .  22
Show full document text