[OSPF] Last Call: <draft-ietf-ospf-rfc4970bis-04.txt> (Extensions to OSPF for Advertising Optional Router Capabilities) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 25 September 2015 00:41 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5E51B4363; Thu, 24 Sep 2015 17:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hAnBdNpXIFMl; Thu, 24 Sep 2015 17:40:57 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 172411B4353; Thu, 24 Sep 2015 17:40:52 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20150925004052.18233.121.idtracker@ietfa.amsl.com>
Date: Thu, 24 Sep 2015 17:40:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/kMCm-bxpLDBnP2KPX6zCp3FH8JI>
Cc: ospf@ietf.org
Subject: [OSPF] Last Call: <draft-ietf-ospf-rfc4970bis-04.txt> (Extensions to OSPF for Advertising Optional Router Capabilities) to Proposed Standard
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2015 00:41:02 -0000

The IESG has received a request from the Open Shortest Path First IGP WG
(ospf) to consider the following document:
- 'Extensions to OSPF for Advertising Optional Router Capabilities'
  <draft-ietf-ospf-rfc4970bis-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-10-08. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-ospf-rfc4970bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-ospf-rfc4970bis/ballot/


No IPR declarations have been submitted directly on this I-D.