LISP Canonical Address Format (LCAF)
draft-ietf-lisp-lcaf-14

Document Type Active Internet-Draft (lisp WG)
Last updated 2016-07-21 (latest revision 2016-07-20)
Replaces draft-farinacci-lisp-lcaf
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Luigi Iannone
Shepherd write-up Show (last changed 2016-07-21)
IESG IESG state Publication Requested
Consensus Boilerplate Unknown
Telechat date
Responsible AD Deborah Brungard
Send notices to "Luigi Iannone" <ggx@gigix.net>
Network Working Group                                       D. Farinacci
Internet-Draft                                               lispers.net
Intended status: Experimental                                   D. Meyer
Expires: January 20, 2017                                        Brocade
                                                             J. Snijders
                                                      NTT Communications
                                                           July 19, 2016

                  LISP Canonical Address Format (LCAF)
                        draft-ietf-lisp-lcaf-14

Abstract

   This draft defines a canonical address format encoding used in LISP
   control messages and in the encoding of lookup keys for the LISP
   Mapping Database System.

Requirements Language

   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].

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 January 20, 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

Farinacci, et al.       Expires January 20, 2017                [Page 1]
Internet-Draft    LISP Canonical Address Format (LCAF)         July 2016

   (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.  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.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   4
   3.  LISP Canonical Address Format Encodings . . . . . . . . . . .   5
   4.  LISP Canonical Address Applications . . . . . . . . . . . . .   7
     4.1.  Segmentation using LISP . . . . . . . . . . . . . . . . .   7
     4.2.  Carrying AS Numbers in the Mapping Database . . . . . . .   9
     4.3.  Assigning Geo Coordinates to Locator Addresses  . . . . .  10
     4.4.  NAT Traversal Scenarios . . . . . . . . . . . . . . . . .  12
     4.5.  Multicast Group Membership Information  . . . . . . . . .  14
     4.6.  Traffic Engineering using Re-encapsulating Tunnels  . . .  15
     4.7.  Storing Security Data in the Mapping Database . . . . . .  17
     4.8.  Source/Destination 2-Tuple Lookups  . . . . . . . . . . .  18
     4.9.  Replication List Entries for Multicast Forwarding . . . .  20
     4.10. Applications for AFI List Type  . . . . . . . . . . . . .  21
       4.10.1.  Binding IPv4 and IPv6 Addresses  . . . . . . . . . .  21
       4.10.2.  Layer-2 VPNs . . . . . . . . . . . . . . . . . . . .  22
       4.10.3.  ASCII Names in the Mapping Database  . . . . . . . .  23
       4.10.4.  Using Recursive LISP Canonical Address Encodings . .  24
       4.10.5.  Compatibility Mode Use Case  . . . . . . . . . . . .  25
   5.  Experimental LISP Canonical Address Applications  . . . . . .  26
     5.1.  Convey Application Specific Data  . . . . . . . . . . . .  26
     5.2.  Generic Database Mapping Lookups  . . . . . . . . . . . .  27
     5.3.  PETR Admission Control Functionality  . . . . . . . . . .  29
     5.4.  Data Model Encoding . . . . . . . . . . . . . . . . . . .  30
     5.5.  Encoding Key/Value Address Pairs  . . . . . . . . . . . .  31
     5.6.  Multiple Data-Planes  . . . . . . . . . . . . . . . . . .  32
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  34
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  34
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  35
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  35
Show full document text