Extensions to OSPF for Advertising Optional Router Capabilities
draft-ietf-ospf-rfc4970bis-05

The information below is for an old version of the document
Document Type Active Internet-Draft (ospf WG)
Last updated 2015-10-08 (latest revision 2015-09-25)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yingzhen Qu
Shepherd write-up Show (last changed 2015-09-09)
IESG IESG state Waiting for AD Go-Ahead
Consensus Boilerplate Unknown
Telechat date
Needs 7 more YES or NO OBJECTION positions to pass.
Responsible AD Alia Atlas
Send notices to draft-ietf-ospf-rfc4970bis.ad@ietf.org, draft-ietf-ospf-rfc4970bis@ietf.org, yiqu@cisco.com, ospf-chairs@ietf.org, draft-ietf-ospf-rfc4970bis.shepherd@ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                     A. Lindem, Ed.
Internet-Draft                                                   N. Shen
Obsoletes: 4970 (if approved)                                 J. Vasseur
Intended status: Standards Track                           Cisco Systems
Expires: March 28, 2016                                      R. Aggarwal
                                                                  Arktan
                                                              S. Shaffer
                                                                  Akamai
                                                      September 25, 2015

    Extensions to OSPF for Advertising Optional Router Capabilities
                   draft-ietf-ospf-rfc4970bis-05.txt

Abstract

   It is useful for routers in an OSPFv2 or OSPFv3 routing domain to
   know the capabilities of their neighbors and other routers in the
   routing domain.  This document proposes extensions to OSPFv2 and
   OSPFv3 for advertising optional router capabilities.  The Router
   Information (RI) Link State Advertisement (LSA) is defined for this
   purpose.  In OSPFv2, the RI LSA will be implemented with an opaque
   LSA type ID.  In OSPFv3, the RI LSA will be implemented with a unique
   LSA type function code.  In both protocols, the RI LSA can be
   advertised at any of the defined flooding scopes (link, area, or
   autonomous system (AS)).  This document obsoletes RFC 4970 by
   providing a revised specification including support for advertisement
   of multiple instances of the RI LSA and a TLV for functional
   capabilities.

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 March 28, 2016.

Lindem, et al.           Expires March 28, 2016                 [Page 1]
Internet-Draft         OSPF Capability Extensions         September 2015

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   3
     1.2.  Summary of Changes from RFC 4970  . . . . . . . . . . . .   3
   2.  OSPF Router Information (RI) LSA  . . . . . . . . . . . . . .   4
     2.1.  OSPFv2 Router Information (RI) Opaque LSA . . . . . . . .   4
     2.2.  OSPFv3 Router Information (RI) Opaque LSA . . . . . . . .   6
     2.3.  OSPF Router Informational Capabilities TLV  . . . . . . .   6
     2.4.  Assigned OSPF Router Informational Capability Bits  . . .   7
     2.5.  OSPF Router Functional Capabilities TLV . . . . . . . . .   8
     2.6.  Flooding Scope of the Router Information LSA  . . . . . .   9
   3.  Backward Compatibility  . . . . . . . . . . . . . . . . . . .  10
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  OSPFv2 Opaque LSA Type Assignment . . . . . . . . . . . .  10
     5.2.  OSPFv3 LSA Function Code Assignment . . . . . . . . . . .  10
     5.3.  OSPF RI LSA TLV Type Assignment . . . . . . . . . . . . .  12
     5.4.  Registry for OSPF RI Informational Capability Bits  . . .  13
     5.5.  Registry for OSPF RI Functional Capability Bits . . . . .  13
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   It is useful for routers in an OSPFv2 [OSPF] or OSPFv3 [OSPFV3]
   routing domain to know the capabilities of their neighbors and other
Show full document text