LISP Mapping Service Functions Discovery (LMSFD) using OSPF
draft-boucadair-lisp-function-discovery-03

Document Type Active Internet-Draft (individual)
Last updated 2016-11-24
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                                       M. Boucadair
Internet-Draft                                              C. Jacquenet
Intended status: Standards Track                                  Orange
Expires: May 28, 2017                                  November 24, 2016

      LISP Mapping Service Functions Discovery (LMSFD) using OSPF
               draft-boucadair-lisp-function-discovery-03

Abstract

   This document specifies extensions to the Open Shortest Path First
   (OSPF) protocol for the discovery of Locator/ID Separation Protocol
   (LISP) Mapping Service functions, especially the Map-Resolver (MR)
   and Map-Server (MS) LISP components.

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 RFC 2119 [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 May 28, 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
   publication of this document.  Please review these documents

Boucadair & Jacquenet     Expires May 28, 2017                  [Page 1]
Internet-Draft         Service Function Discovery          November 2016

   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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Mapping Service Function Discovery (MSFD) TLV . . . . . . . .   5
     3.1.  MSF-TYPE sub-TLV  . . . . . . . . . . . . . . . . . . . .   6
     3.2.  MSF-LOCATOR sub-TLV . . . . . . . . . . . . . . . . . . .   6
     3.3.  MSF-DESCRIPTION sub-TLV . . . . . . . . . . . . . . . . .   7
     3.4.  MSF-EPOCH sub-TLV . . . . . . . . . . . . . . . . . . . .   7
     3.5.  MSF-UNAVAILABILITY-TIMER sub-TLV  . . . . . . . . . . . .   8
     3.6.  MSF-REBOOT-TIMER sub-TLV  . . . . . . . . . . . . . . . .   8
     3.7.  MSF-DIAGNOSIS sub-TLV . . . . . . . . . . . . . . . . . .   9
     3.8.  MS-STATUS sub-TLV . . . . . . . . . . . . . . . . . . . .   9
     3.9.  MSF-STATUS sub-TLV  . . . . . . . . . . . . . . . . . . .   9
   4.  Mapping Service Reachability Information  . . . . . . . . . .  10
   5.  OSPF Operation  . . . . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Locator/ID Separation Protocol (LISP, [RFC6830] ) operation relies
   upon a mapping mechanism that is used by ingress/egress Tunnel
   Routers (xTR) to forward traffic over the LISP network.  The ability
   of dynamically discovering the Map-Resolver (MR) and Map-Server (MS)
   entities that provide such mapping services is meant to facilitate
   global LISP operation (automatic discovery of Map-Resolvers and Map-
   Servers).

   The dynamically-acquired information will not only be used by xTR
   routers but also by management platforms (e.g., a service controller,
   a network manager, etc.) to forward traffic over the LISP network or
   to get an up-to-date view of the global LISP network topology,
Show full document text