Link State Over Ethernet
draft-ymbk-lsvr-lsoe-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-03-14
Replaced by draft-ietf-lsvr-lsoe
Stream (None)
Intended RFC status (None)
Formats plain text 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                                            R. Bush
Internet-Draft                                              Arrcus & IIJ
Intended status: Standards Track                                K. Patel
Expires: September 14, 2018                                       Arrcus
                                                          March 13, 2018

                        Link State Over Ethernet
                        draft-ymbk-lsvr-lsoe-00

Abstract

   Used in a Massive Data Center (MDC), BGP-LS and BGP-SPF need link
   neighbor discovery, liveness, and addressability data.  Link State
   Over Ethernet protocols provide link discovery, exchange AFI/SAFIs,
   and discover addresses over raw Ethernet.  These data are pushed
   directly to BGP-LS/SPF, obviating the need for centralized controller
   architectures.  This protocol is more widely applicable, and has been
   designed to support a wide range of routing and similar protocols
   which need link discovery and characterisation.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
   be interpreted as described in RFC 2119 [RFC2119] only when they
   appear in all upper case.  They may also appear in lower or mixed
   case as English words, without normative meaning.

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 14, 2018.

Bush & Patel           Expires September 14, 2018               [Page 1]
Internet-Draft          Link State Over Ethernet              March 2018

Copyright Notice

   Copyright (c) 2018 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Top Level Overview  . . . . . . . . . . . . . . . . . . . . .   4
   5.  Ethernet to Ethernet Protocols  . . . . . . . . . . . . . . .   5
     5.1.  Inter-Link Ether Protocol Overview  . . . . . . . . . . .   5
     5.2.  PDUs and Frames . . . . . . . . . . . . . . . . . . . . .   7
       5.2.1.  Frame TLV . . . . . . . . . . . . . . . . . . . . . .   7
       5.2.2.  Link KeepAlive / Hello  . . . . . . . . . . . . . . .  10
       5.2.3.  Capability Exchange . . . . . . . . . . . . . . . . .  10
       5.2.4.  Timer Negotiation . . . . . . . . . . . . . . . . . .  11
     5.3.  The AFI/SAFI Exchanges  . . . . . . . . . . . . . . . . .  11
       5.3.1.  AFI/SAFI Capability Exchange  . . . . . . . . . . . .  11
       5.3.2.  The AFI/SAFI PDU Skeleton . . . . . . . . . . . . . .  12
       5.3.3.  AFI/SAFI ACK  . . . . . . . . . . . . . . . . . . . .  13
       5.3.4.  Add/Drop/Prim . . . . . . . . . . . . . . . . . . . .  13
       5.3.5.  IPv4 Announce / Withdraw  . . . . . . . . . . . . . .  13
       5.3.6.  IPv6 Announce / Withdraw  . . . . . . . . . . . . . .  14
       5.3.7.  MPLS IPv4 Announce / Withdraw . . . . . . . . . . . .  14
       5.3.8.  MPLS IPv6 Announce / Withdraw . . . . . . . . . . . .  15
   6.  Layer 2.5 and 3 Liveness  . . . . . . . . . . . . . . . . . .  16
   7.  The North/South Protocol  . . . . . . . . . . . . . . . . . .  16
     7.1.  Topology Request for Full State . . . . . . . . . . . . .  16
     7.2.  PDU from Link Layer to Shim . . . . . . . . . . . . . . .  17
     7.3.  Link/ASN sub-PDU  . . . . . . . . . . . . . . . . . . . .  17
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
Show full document text