Re: [OSPF] AD review of draft-ietf-ospf-rfc4970bis-02

"Acee Lindem (acee)" <> Thu, 24 September 2015 19:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5E26A1A8763; Thu, 24 Sep 2015 12:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sTZ7oGEEa_zR; Thu, 24 Sep 2015 12:09:05 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CB7BA1A8782; Thu, 24 Sep 2015 12:09:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=44984; q=dns/txt; s=iport; t=1443121744; x=1444331344; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=cW5neEBGaucbdGo+/PtNwr1U8kmMBDkV/16ahSn1tQU=; b=Sp/LExkiL/0nI0s3hM8MCFe91WD/B86Te51Ec2La4Wnkb0U58QL68A6X +toZ1YIvr2Y2fGKAEbLxKdDOIQYZarebGFydNGQCkjL+th2iR3zLws15I IXkG8fzG4MULRIK0mKnXAE7i+z75RI1EuiZ4DtmY7hlg0ydGjEs3ZeWXZ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.17,582,1437436800"; d="scan'208,217"; a="31797190"
Received: from ([]) by with ESMTP; 24 Sep 2015 19:09:02 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t8OJ92Jv003469 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 24 Sep 2015 19:09:02 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 24 Sep 2015 14:09:01 -0500
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Thu, 24 Sep 2015 14:09:01 -0500
Received: from ([]) by ([]) with mapi id 14.03.0248.002; Thu, 24 Sep 2015 14:09:01 -0500
From: "Acee Lindem (acee)" <>
To: Alia Atlas <>
Thread-Topic: [OSPF] AD review of draft-ietf-ospf-rfc4970bis-02
Thread-Index: AQHQ9YIst/tfqaD4vUilavXsqepMPZ5KQImAgAE1KPSAACkoAIAAD96AgACuwACAAARFgA==
Date: Thu, 24 Sep 2015 19:09:01 +0000
Message-ID: <>
References: <> <> <036301d0f6b0$54e4c460$> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_004EF2D7DCB94469B088E66169F4A598ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: OSPF List <>, "" <>
Subject: Re: [OSPF] AD review of draft-ietf-ospf-rfc4970bis-02
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, 24 Sep 2015 19:09:09 -0000

Hi Alia,

On Sep 24, 2015, at 2:53 PM, Alia Atlas <<>> wrote:


I just took a quick look at this version and the IANA section looks much better.
I don't see an extra paragraph talking about backwards compatibility…

Maybe because it is very brief. I wanted to avoid discussion of specific existing TLVs.

3.  Backward Compatibility

   For backward compatibility, previously advertised Router Information
   TLVs SHOULD continue to be advertised in the first instance, i.e., 0,
   of the Router Information LSA.  If a Router Information TLV is
   advertised in multiple Router Information LSA instances and the
   multiple instance processing is not explicitly specified in the RFC
   defining that Router Information TLV, the Router Instance TLV in the
   Router Information LSA with the numerically smallest Instance ID will
   be used and subsequent instances will be ignored.


I'd like to get this out for IETF Last Call today, if you can spin a quick version.


On Thu, Sep 24, 2015 at 8:28 AM, Acee Lindem (acee) <<>> wrote:
Hi Tom,

I believe the 04 update addresses your comments and will make IANA’s job a
lot easier.

A new version of I-D, draft-ietf-ospf-rfc4970bis-04.txt
has been successfully submitted by Acee Lindem and posted to the
IETF repository.

Name:           draft-ietf-ospf-rfc4970bis
Revision:       04
Title:          Extensions to OSPF for Advertising Optional Router Capabilities
Document date:  2015-09-24
Group:          ospf
Pages:          15

   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


On 9/24/15, 7:31 AM, "OSPF on behalf of Acee Lindem (acee)"
<<> on behalf of<>> wrote:

>Hi Tom,
>On 9/24/15, 6:02 AM, "t.petch" <<>> wrote:
>>Alia having alerted me to the IANA Considerations :-( two further
>>Jeff Haas has written an excellent I-D recommending that the first and
>>last points of a numeric registry should be reserved, which I agree
>>with. In that light, I suggest reserving 8191 in OSPFv3 LSA Function
>I must admit that I thought this whole discussion was much ado about
>nothing but I’m certainly not opposed to reserving the last function code.
>If we run into a situation where we use the whole OSPFv3 LSA Function Code
>space, it will mean that OSPFv3 has been wildly successful!
>>Second, 5226bis proposes a cleaner terminology, replacing top-level
>>registry, registry, sub-registry, sub-sub registry etc with Registry
>>within Group.  (OSPF has eleven Groups, BGP but one).  I see that OSPFv3
>>LSA Function Codes is in the Open Shortest Path First v3 (OSPFv3)
>>Parameters Group.  I think that you are implying that IANA should update
>>some but not all the references for that Registry.  Thus the reference
>>for the Registry as a whole should be for this new I-D but the reference
>>for individual entries for the most part do not change except where they
>>are to RFC4970(?).
>Yes - Are you suggesting I state the registry is unchanged from RFC 4970
>other than the change to the reservation policy and the reservation of
>>Likewise for OSPF RI TLVs  which is in the Open Shortest Path First v2
>>(OSPFv2) Parameters Group, some references will need updating, others
>>will not, and I think that that needs specifying in the I-D.
>Yes - are you suggesting any change of text?
>>OSPF Router Informational Capability Bits I think is another Registry
>>within the same Group while OSPF Router Functional Capability Bits I
>>think is a new Registry; I don't know which Group it fits best with but
>>I think that that should be specified.
>This new registry should go in the "Open Shortest Path First v2 (OSPFv2)
>Parameters" group the same as the existing "OSPF Router Informational
>Capability Bits”.
>>Tom Petch
>>----- Original Message -----
>>From: "Acee Lindem (acee)" <<>>
>>To: "Alia Atlas" <<>>; "OSPF List" <<>>;
>>Sent: Wednesday, September 23, 2015 3:37 PM
>>Subject: Re: [OSPF] AD review of draft-ietf-ospf-rfc4970bis-02
>>> Hi Alia,
>>> From: Alia Atlas <<><<>>>
>>> Date: Tuesday, September 22, 2015 at 6:00 PM
>>> To: OSPF WG List <<><<>>>,
>>> Subject: AD review of draft-ietf-ospf-rfc4970bis-02
>>> As is customary, I have done my AD review of
>>draft-ietf-ospf-rfc4970bis-02.  First, let me thank Acee for his work on
>>this draft.
>>> I have two major concerns before asking for an IETF Last Call.  I
>>would like to have them
>>> resolved by this Thursday so that the draft can make the Oct 15 IESG
>>> First, from a process concern, I do not see any active discussion on
>>the OSPF mailing list - even to simply say "yes - go forward".  I don't
>>see anything about this draft or discussion in minutes for IETF 92 or
>>IETF 93.   I'd prefer some indication besides silence and lack of
>>opposition.  I do realize that there are some process or
>>protocol-tidying drafts where there isn't
>>> much interest.  However, I am particularly concerned because this is
>>changing RFC4970 is a way that should be backwards compatible but might
>>trigger issues.   I would encourage WG participants to PLEASE RESPOND!
>>> Second, I can see the intent that by creating an Opaque ID and
>>creating a special meaning for 0, the draft is making efforts to
>>preserve backwards compatibility.  Please add a paragraph or subsection
>>that articulates how and why backwards compatibility isn't an issue.
>>> I will add more on this.
>>>   For extra credit, what happens if the same TLV information is
>>advertised in multiple RI LSAs (as part of moving it from one RI LSA to
>>> This depends on the context of the TLV. In some cases the router
>>information is additive and in others conflicts need to be resolved.
>>> Are there any implementations of this draft?  Has backwards
>>compatibility been verified at all?
>>> Many implementations of RFC 4970. I don’t know of any implementations
>>that originate multiple RI LSAs. However, with all the proposed OSPF RI
>>LSA usages, I can see them coming.
>>> My minor issue is around the IANA considerations; I have detailed
>>comments below.
>>> Here are additional comments.
>>> 1) In Sec 2: "The first Opaque ID, i.e., 0, should always contain the
>>>    Informational Capabilities TLV and, if advertised, the Router
>>>    Functional Capabilities TLV."  and Sec 2.2 "The first instance ID,
>>i.e., 0,
>>>    should always contain the Router Informational Capabilities TLV
>>>    if advertised, the Router Functional Capabilities TLV."
>>>    Since I assume this is important for backwards compatibility,
>>should those
>>>    be SHOULD instead of should?
>>> Yes.
>>> 2) In Sec 2.3: "The first defined TLV in the body of an RI LSA is the
>>>    Informational Capabilities TLV."
>>>    Surely that is only for the first Opaque ID=0?  Does each
>>subsequent RI LSA
>>>    also need to contain a Router Informational Capabilities TLV??
>>> No. Will clarify this.
>>> 3) In Sec 4 IANA Considerations:  This section is defining the
>>different IANA policies;
>>> when RFC4970 was written, RFC5226 didn't exist.  But since you're
>>doing a bis,
>>> perhaps you can align to the policies in RFC5226 and remove the
>>unnecessary text??
>>> Yes. I think of already done this.
>>> 4) In Sec 4 IANA Considerations:  The registry for OSPFv3 LSA Function
>>Codes can
>>> be found at
>>l#ospfv3-parameters-3 and what is in the draft doesn't match up.  I'd
>>settle for defining the ranges, and value 12 - but it's up to you and
>>IANA on the preferences.  Would it make sense to change the policy from
>>Standards Action to IETF Review here also?
>>> Yes - I think this draft should change the policy for OSPFv3 LSA
>>Functions codes since RFC 4970 initially created the registry. If were
>>going to change the policy (and I think we want to do this), it makes
>>sense to do it here from a continuity standpoint.
>>> Same thing applies to the OSPF RI TLVS
>>ml#ospfv2-parameters-9 )   Also here, I think there
>>> was agreement among the 4 of us who commented on the WG mailing list
>>to change this
>>> from Standards Action to IETF Review.
>>> Yes.
>>> 5) In Sec 4 IANA Considerations: "All Router Functional Capability TLV
>>>        additions are to be assigned through standards action."   Given
>>the discussion
>>> about IETF Review vs. Standards Action for other registries, are you
>>sure you want
>>> Standards Action?
>>> No  - I will change this.
>>> I'm sure that we'll get this moving along quickly.
>>> Great - will work on this today in preparation for the tomorrow’s
>>> Thanks,
>>> Acee
>>> Thanks again!
>>> Alia
>>> _______________________________________________
>>> OSPF mailing list
>OSPF mailing list