OSPF Graceful Link shutdown
draft-ietf-ospf-link-overload-12

Document Type Active Internet-Draft (ospf WG)
Last updated 2018-01-16
Replaces draft-hegde-ospf-link-overload
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf xml html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Acee Lindem
Shepherd write-up Show (last changed 2017-12-06)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Yes
Telechat date On agenda of 2018-01-25 IESG telechat
Responsible AD Alia Atlas
Send notices to Acee Lindem <acee@cisco.com>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Open Shortest Path First IGP                                    S. Hegde
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                               P. Sarkar
Expires: July 20, 2018                                        H. Gredler
                                                              Individual
                                                              M. Nanduri
                                                        ebay Corporation
                                                                L. Jalil
                                                                 Verizon
                                                        January 16, 2018

                      OSPF Graceful Link shutdown
                    draft-ietf-ospf-link-overload-12

Abstract

   When a link is being prepared to be taken out of service, the traffic
   needs to be diverted from both ends of the link.  Increasing the
   metric to the highest value on one side of the link is not sufficient
   to divert the traffic flowing in the other direction.

   It is useful for routers in an OSPFv2 or OSPFv3 routing domain to be
   able to advertise a link as being in a graceful-shutdown state to
   indicate impending maintenance activity on the link.  This
   information can be used by the network devices to re-route the
   traffic effectively.

   This document describes the protocol extensions to disseminate
   graceful-link-shutdown information in OSPFv2 and OSPFv3.

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 https://datatracker.ietf.org/drafts/current/.

Hegde, et al.             Expires July 20, 2018                 [Page 1]
Internet-Draft         OSPF graceful link shutdown          January 2018

   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 July 20, 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.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Flooding Scope  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Graceful-Link-Shutdown sub-TLV  . . . . . . . . . . . . . . .   4
     4.1.  OSPFv2 graceful-link-shutdown sub-TLV . . . . . . . . . .   4
     4.2.  Remote IPv4 Address Sub-TLV . . . . . . . . . . . . . . .   5
     4.3.  Local/Remote Interface ID Sub-TLV . . . . . . . . . . . .   5
     4.4.  OSPFv3 Graceful-Link-Shutdown sub-TLV . . . . . . . . . .   6
     4.5.  BGP-LS Graceful-Link-Shutdown TLV . . . . . . . . . . . .   6
     4.6.  Distinguishing parallel links . . . . . . . . . . . . . .   7
   5.  Elements of procedure . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Point-to-point links  . . . . . . . . . . . . . . . . . .   8
     5.2.  Broadcast/NBMA links  . . . . . . . . . . . . . . . . . .   9
     5.3.  Point-to-multipoint links . . . . . . . . . . . . . . . .   9
     5.4.  Unnumbered interfaces . . . . . . . . . . . . . . . . . .   9
     5.5.  Hybrid Broadcast and P2MP interfaces  . . . . . . . . . .  10
   6.  Backward compatibility  . . . . . . . . . . . . . . . . . . .  10
   7.  Applications  . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Pseudowire Services . . . . . . . . . . . . . . . . . . .  10
     7.2.  Controller based Traffic Engineering Deployments  . . . .  11
     7.3.  L3VPN Services and sham-links . . . . . . . . . . . . . .  12
     7.4.  Hub and spoke deployment  . . . . . . . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
Show full document text