OSPF Transport Instance Extensions
draft-acee-lsr-ospf-transport-instance-01

Document Type Active Internet-Draft (individual)
Authors Acee Lindem  , Yingzhen Qu  , Abhay Roy  , Sina Mirtorabi 
Last updated 2020-11-02
Replaces draft-ietf-ospf-transport-instance
Stream (None)
Intended RFC status (None)
Formats plain text 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)
LSR Workgroup                                                  A. Lindem
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                                   Y. Qu
Expires: May 6, 2021                                           Futurewei
                                                                  A. Roy
                                                            Arrcus, Inc.
                                                            S. Mirtorabi
                                                           Cisco Systems
                                                        November 2, 2020

                   OSPF Transport Instance Extensions
               draft-acee-lsr-ospf-transport-instance-01

Abstract

   OSPFv2 and OSPFv3 include a reliable flooding mechanism to
   disseminate routing topology and Traffic Engineering (TE) information
   within a routing domain.  Given the effectiveness of these
   mechanisms, it is convenient to envision using the same mechanism for
   dissemination of other types of information within the domain.
   However, burdening OSPF with this additional information will impact
   intra-domain routing convergence and possibly jeopardize the
   stability of the OSPF routing domain.  This document presents
   mechanism to relegate this ancillary information to a separate OSPF
   instance and minimize the impact.

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 May 6, 2021.

Lindem, et al.             Expires May 6, 2021                  [Page 1]
Internet-Draft           OSPF Transport Instance           November 2020

Copyright Notice

   Copyright (c) 2020 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.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Possible Use Cases  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  MEC Service Discovery . . . . . . . . . . . . . . . . . .   3
     3.2.  Application Data Dissemination  . . . . . . . . . . . . .   4
     3.3.  Intra-Area Topology for BGP-LS Distribution . . . . . . .   4
   4.  OSPF Transport Instance . . . . . . . . . . . . . . . . . . .   4
     4.1.  OSPFv2 Transport Instance Packet Differentiation  . . . .   5
     4.2.  OSPFv3 Transport Instance Packet Differentiation  . . . .   5
     4.3.  Instance Relationship to Normal OSPF Instances  . . . . .   5
     4.4.  Network Prioritization  . . . . . . . . . . . . . . . . .   5
     4.5.  OSPF Transport Instance Omission of Routing Calculation .   6
     4.6.  Non-routing Instance Separation . . . . . . . . . . . . .   6
     4.7.  Non-Routing Sparse Topologies . . . . . . . . . . . . . .   7
       4.7.1.  Remote OSPF Neighbor  . . . . . . . . . . . . . . . .   7
     4.8.  Multiple Topologies . . . . . . . . . . . . . . . . . . .   8
   5.  OSPF Transport Instance Information Encoding  . . . . . . . .   8
     5.1.  OSPFv2 Transport Instance Information Encoding  . . . . .   9
     5.2.  OSPFv3 Transport Instance Information Encoding  . . . . .   9
   6.  Manageability Considerations  . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

Lindem, et al.             Expires May 6, 2021                  [Page 2]
Show full document text