OSPF Transport Instance Extensions
draft-ietf-ospf-transport-instance-08

The information below is for an old version of the document
Document Type Active Internet-Draft (ospf WG)
Last updated 2012-04-04
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          A. Lindem
Internet-Draft                                                  Ericsson
Intended status: Standards Track                                  A. Roy
Expires: October 6, 2012                                    S. Mirtorabi
                                                           Cisco Systems
                                                           April 4, 2012

                   OSPF Transport Instance Extensions
               draft-ietf-ospf-transport-instance-08.txt

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 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 October 6, 2012.

Copyright Notice

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

Lindem, et al.           Expires October 6, 2012                [Page 1]
Internet-Draft     OSPF Transport Instance Extensions         April 2012

   (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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Lindem, et al.           Expires October 6, 2012                [Page 2]
Internet-Draft     OSPF Transport Instance Extensions         April 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Requirements notation  . . . . . . . . . . . . . . . . . .  4
   2.  OSPF Transport Instance  . . . . . . . . . . . . . . . . . . .  5
     2.1.  OSPFv2 Transport Instance Packets Differentiation  . . . .  5
     2.2.  OSPFv3 Transport Instance Packets Differentiation  . . . .  5
     2.3.  Instance Relationship to Normal OSPF Instances . . . . . .  5
       2.3.1.  Ships in the Night Relationship to Normal OSPF
               Instances  . . . . . . . . . . . . . . . . . . . . . .  6
       2.3.2.  Tighter Coupling with Normal OSPF Instances  . . . . .  6
     2.4.  Network Prioritization . . . . . . . . . . . . . . . . . .  6
     2.5.  OSPF Transport Instance Omission of Routing Calculation  .  6
     2.6.  Non-routing Instance Separation  . . . . . . . . . . . . .  7
     2.7.  Non-Routing Sparse Topologies  . . . . . . . . . . . . . .  7
       2.7.1.  Remote OSPF Neighbor . . . . . . . . . . . . . . . . .  8
   3.  OSPF Transport Instance Information Encoding . . . . . . . . .  9
     3.1.  OSPFv2 Transport Instance Information Encoding . . . . . .  9
     3.2.  OSPFv3 Transport Instance Information Encoding . . . . . .  9
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
Show full document text