LISP Transport for Policy Distribution
draft-kowal-lisp-policy-distribution-00

Document Type Active Internet-Draft (individual)
Authors Michael Kowal  , Marc Portoles-Comeras  , Amit Jain  , Dino Farinacci 
Last updated 2021-03-16
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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                                           M. Kowal
Internet-Draft                                               M. Portoles
Intended status: Experimental                              Cisco Systems
Expires: September 17, 2021                                      A. Jain
                                                        Juniper Networks
                                                            D. Farinacci
                                                             lispers.net
                                                          March 16, 2021

                 LISP Transport for Policy Distribution
                draft-kowal-lisp-policy-distribution-00

Abstract

   This document describes the use of the Locator/ID Separation Protocol
   (LISP) to encode and transport data models for the configuration of
   LISP ITRs.

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 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 September 17, 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Kowal, et al.          Expires September 17, 2021               [Page 1]
Internet-Draft   LISP Transport for Policy Distribution       March 2021

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   2
   3.  Policy Distribution Use Cases . . . . . . . . . . . . . . . .   3
   4.  Policy Distribution: Packet Flow Description  . . . . . . . .   3
     4.1.  Policy Distribution . . . . . . . . . . . . . . . . . . .   4
     4.2.  Policy Updates  . . . . . . . . . . . . . . . . . . . . .   5
   5.  Mapping System Operations . . . . . . . . . . . . . . . . . .   6
   6.  Policy Distribution Process . . . . . . . . . . . . . . . . .   6
   7.  Policy Distribution Encoding  . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   When LISP ITRs are deployed with enough configuration to build a LISP
   overlay, they may require additional configurations such as security,
   QoS, and/or traffic forwarding policies.  As networks continue to
   grow, it can be challenging to ensure these configurations are
   distributed to many ITRs and kept in sync.  LISP network operators
   may wish to re-use their existing LISP architecture to distribute
   these configurations as opposed to configuring them by hand, using a
   script, or investing in a configuration management system.  The
   configurations can be distributed via a mapping system that the
   network operator manages or is managed by a third-party as part of a
   managed service offering.

2.  Definition of Terms

   LISP related terms are defined as part of the LISP specification
   [RFC6830], notably EID, RLOC, Map-Request, Map- Reply, Map-Notify,
   Ingress Tunnel Router (ITR), Egress Tunnel Router (ETR), Map- Server
   (MS) and Map-Resolver (MR).

Kowal, et al.          Expires September 17, 2021               [Page 2]
Internet-Draft   LISP Transport for Policy Distribution       March 2021

3.  Policy Distribution Use Cases

   The ITR could use the mapping system to receive configuration
Show full document text