Re: [OSPF] New Version Notification for draft-acee-ospf-rfc4970bis-00.txt

"Acee Lindem (acee)" <> Thu, 31 July 2014 21:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6A3BF1A0183 for <>; Thu, 31 Jul 2014 14:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tO-zykzJTyXL for <>; Thu, 31 Jul 2014 14:54:23 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4DDD31A0181 for <>; Thu, 31 Jul 2014 14:54:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2607; q=dns/txt; s=iport; t=1406843663; x=1408053263; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=pAdohC0hBTJadyhwH8QQZPNlTpwCrwES6eSB71Quv+M=; b=JkrPKFxfbYS1BUq+spAegQ22Uk+zR3jyZ6JDU/bAQyAe2QnZRgQvIWY/ dTaLNSm9iX23W1eFlTrioeNBqYm67os8tV5QtlIzIeMXewLl5/UV3XvJe VAdZb9Ymz3kCCrDjmni9WhE0fsQT+rJ6NEzRL2MfvvzYLqZcYs3W4L9EJ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFANy52lOtJA2K/2dsb2JhbABbgw1SVwTNF4dLAYEMFneEBAEBBDo9EgIBCDYQMiUCBBMJiDkNynsXj1OESwWbdIFSkwSDSWwBgUQ
X-IronPort-AV: E=Sophos;i="5.01,774,1400025600"; d="scan'208";a="65597853"
Received: from ([]) by with ESMTP; 31 Jul 2014 21:54:22 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id s6VLsMM7032538 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <>; Thu, 31 Jul 2014 21:54:22 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Thu, 31 Jul 2014 16:54:22 -0500
From: "Acee Lindem (acee)" <>
To: "" <>
Thread-Topic: New Version Notification for draft-acee-ospf-rfc4970bis-00.txt
Thread-Index: AQHPrNPV9OX1dLnbUUmno3nmSb/zbZu6yxOA
Date: Thu, 31 Jul 2014 21:54:21 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OSPF] New Version Notification for draft-acee-ospf-rfc4970bis-00.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Jul 2014 21:54:25 -0000

Note that I have authored an RFC 4970 BIS draft which better reflects the
requirements. Here is an excerpt describing the changes:

   This document includes the following changes from RFC 4970 [RFC4970]:

   1.  The main change is that an OSPF router will be able to advertise
      multiple instances of the OSPF Router Information LSA.  This
      change permeates through much of the document

   2.  Additionally, Section 2.5 includes a new TLV for functional
      capabilities.  This is constast to the existing TLV which is used
      to advertise capabilities for informational purposes only.

   3.  Finally, references have been updated for drafts that have become
      RFCs and RFCs that have been obsoleted since the publication of
      RFC 4970.


On 7/31/14, 11:26 AM, ""
<> wrote:

>A new version of I-D, draft-acee-ospf-rfc4970bis-00.txt
>has been successfully submitted by Acee Lindem and posted to the
>IETF repository.
>Name:		draft-acee-ospf-rfc4970bis
>Revision:	00
>Title:		Extensions to OSPF for Advertising Optional Router Capabilities
>Document date:	2014-07-31
>Group:		Individual Submission
>Pages:		17
>   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.  A new Router
>   Information (RI) Link State Advertisement (LSA) is proposed for this
>   purpose.  In OSPFv2, the RI LSA will be implemented with a new opaque
>   LSA type ID.  In OSPFv3, the RI LSA will be implemented with a new
>   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.
>Please note that it may take a couple of minutes from the time of
>until the htmlized version and diff are available at
>The IETF Secretariat