OSPF Abnormal State Information
draft-chen-ospf-abnormal-state-info-03

Document Type Active Internet-Draft (individual)
Last updated 2019-10-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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)
Internet Engineering Task Force                                  H. Chen
Internet-Draft                                                 Futurewei
Intended status: Standards Track                         October 2, 2019
Expires: April 4, 2020

                    OSPF Abnormal State Information
               draft-chen-ospf-abnormal-state-info-03.txt

Abstract

   This document describes a couple of options for an OSPF router to
   advertise its abnormal state information in a routing domain.

Status of this Memo

   This Internet-Draft is submitted to IETF 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 April 4, 2020.

Copyright Notice

   Copyright (c) 2019 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
   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.

Chen                      Expires April 4, 2020                 [Page 1]
Internet-Draft             OSPF Abnormal State              October 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Conventions Used in This Document . . . . . . . . . . . . . . . 3
   4.  OSPF Router State Information LSA . . . . . . . . . . . . . . . 3
     4.1.  OSPFv2 Router State Information (RSI) Opaque LSA  . . . . . 3
     4.2.  OSPFv3 Router State Information (RSI) Opaque LSA  . . . . . 5
     4.3.  OSPF Router State Information (RSI) TLV . . . . . . . . . . 5
   5.  Attach RSI TLV to Router Inforamtion LSA  . . . . . . . . . . . 6
   6.  Notify Other Systems  . . . . . . . . . . . . . . . . . . . . . 7
   7.  Security  Considerations  . . . . . . . . . . . . . . . . . . . 7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   9.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     10.1. Normative References  . . . . . . . . . . . . . . . . . . . 7
     10.2. Informative References  . . . . . . . . . . . . . . . . . . 8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chen                      Expires April 4, 2020                 [Page 2]
Internet-Draft             OSPF Abnormal State              October 2019

1.  Introduction

   There may be some states that are not normal in an OSPF router, which
   include the state that a link state advertisement (LSA) stays in a
   retransmission list on the router for more than a given time period
   such as more than hello dead interval, and may include the state that
   a database description (DD) packet does not get acknowledged for a
   given period of time.

   If a link state advertisement (LSA) with a topology change in a
   router can not get through over an OSPF interface for a given time
   period, some of the routers in the routing domain may have different
   view of the real network topology, thus routing loops may occur and
   some traffic may get dropped.

   It is useful for an OSPF router in a routing domain to advertise its
   abnormal state information to other routers, or notify some systems
   such as an event management or monitoring system for its abnormal
   state.

   This document describes a couple of options for an OSPF router to
   advertise its abnormal state information in a routing domain.

2.  Terminology

   This document uses terminologies defined in RFC 4970, RFC 2328, and
   RFC 2740.

3.  Conventions Used in This Document

   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.

4.  OSPF Router State Information LSA

   OSPF routers MAY advertise their state information in a area-scoped
   or AS-scoped router state information LSA with a router state
Show full document text