Re: [OSPF] FW: New Version Notification for draft-ietf-ospf-prefix-link-attr-00.txt

"Acee Lindem (acee)" <> Sat, 06 September 2014 18:05 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 986621A00D7 for <>; Sat, 6 Sep 2014 11:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -16.153
X-Spam-Status: No, score=-16.153 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=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SsYvS88WThnR for <>; Sat, 6 Sep 2014 11:05:41 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C57871A007F for <>; Sat, 6 Sep 2014 11:05:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=4633; q=dns/txt; s=iport; t=1410026740; x=1411236340; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=IZUnBHn0h91FMpulWnm8sDbnLgIO0A18xLcv1jIr5Go=; b=cIbib8uDaa4qoTnRCxCUuMQeT59WRSHRJh7kaMVKrrudwgctCxF7s365 4M8jLyi0YH8yJu+nqIM8JOy0TXiM5SRUkl2x5hbCOaSiph5J3kmEgVCEY 74vKx3gbdiHQbFqreyswQ1Eldr9B/OrVjmY5/vWfsBdUkI3CZ1dON9wQh E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.04,479,1406592000"; d="scan'208";a="75579097"
Received: from ([]) by with ESMTP; 06 Sep 2014 18:05:39 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id s86I5dBw002886 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 6 Sep 2014 18:05:39 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Sat, 6 Sep 2014 13:05:38 -0500
From: "Acee Lindem (acee)" <>
To: "A. Przygienda" <>, "Peter Psenak (ppsenak)" <>
Thread-Topic: [OSPF] FW: New Version Notification for draft-ietf-ospf-prefix-link-attr-00.txt
Thread-Index: AQHPtlGQNLZvkWuqU0uFf/90h1EvfZvOlLMAgB6rngCAAKUNAIAAZ/CAgAG9yoCAAP6WgIAAwyoAgADiowCAAfqIgP//9ESA
Date: Sat, 6 Sep 2014 18:05:37 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [OSPF] FW: New Version Notification for draft-ietf-ospf-prefix-link-attr-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: Sat, 06 Sep 2014 18:05:44 -0000

On 9/6/14, 10:47 AM, "A. Przygienda" <> wrote:

>>>>> It's also wise to add 'if the same extended prefix TLV (i.e. for same
>>>>> prefix) is seen twice in same opaque LSA only use the first and force
>>>>> people to put all sub-tlvs into a single tlv.
>>>> it's kind of obvious, but we can add a text to be sure.
>>> As I see it, the purpose of an RFC is to assure interoperability. If
>>> there are two
>>> interpretations available of the same packet that will make two
>>> solutions not interoperable,
>>> the standard has to mandate the correct one.
>> ok, we will add a text to make it clear.
>>>> because existing LSA are not extensible, any additional link/prefix
>>>> attributes must be advertised in a separate LSAs. We called it
>>>> "extended", but it does not mean that existence of the extended LSA
>>>> require existence of the base LSA. I had a text in the original SR
>>>> draft around that, we can add it here too.
>>> yepp, once it spelled out, it's obvious but the first conclusion one
>>> jumps to is that they are inter-dependent otherwise.
>> ok, we will add a text to clarify.
>>>>> Acee, you mean remove the restriction ?  I see how some
>>>>> implementations
>>>>> may benefit from cramming all type-3 into the same opaque but I would
>>>>> also suggest to not restrict this and remove the text.
>>>> the restriction can not be removed. All the Extended Prefix TLVs that
>>>> you put in a singe Extended Prefix LSA will only use a flooding scope
>>>> of the Extended LSA itself.
>>> I still think it's not clear what the original paragraph means.
>> prefixes can have different flooding scope. Today intra-area and
>> inter-area prefixes have area flooding scope and external prefixes
>> have domain wide flooding scope. You can not mix prefixes of different
>> flooding scope in a single Extended Prefix LSA, because Extended
>> Prefix LSA can only have a single flooding scope.
>yes, this is now clearly spelled out.  I suggest adding that to the
>draft with a MUST NOT and addition that if they are, the behavior of the
>protocol is unspecified/incorrect.

I guess I still see this is a tautology since the LSA type defines the
flooding scope that need not be in the draft. If you advertise a prefix in
an LSA with a given flooding scope, then by definition, the prefix is
advertised at the flooding scope of that LSA. Let me try and reword this
so that it reflects the required flooding scope for the prefix.

>>>>>        * what happens if the same extended prefix TLV shows up
>>>>> twice in
>>>>> two different opaques of same type ?  You use the one that is in
>>>>> opaque ID ?
>>>> I would call it a bug on the originator side.
>>> yes, but still, the draft should mandate what the desired behavior is @
>>> this point in time otherwise some will use the lower ID, some higher
>>> some none of the above & the implementations will not interop ?
>> ok, we will add a tiebreaker there.
>All my issues have been adressed then except concerns about the 'any
>prefix in any opaque'. Let me explain.
>Let's say I have an extended prefix X providing service X'.  The prefix
>is advertised in opaque O_1.
>If I remove it from O_1 and move it to O_2 (due to running out of space,
>weak implemenation and so on)
>but O_1 is flooded out there before people pick up O_2, service X' will
>be interrupted.
>This sounds not too bad but imagine you advertise 50 new prefixes that
>slide 50 prefixes from the original
>O_1.  Same for deletions. Now your protocol becomes quite fragile (if
>interested further,
>look @ ISIS treatement of that problem)

OSPFv3 has this situation today as well for Router-LSA links - in this
case, implementations will reoriginate all the changed Router-LSAs at
³nearly" the same time and, more often than not, the changed LSAs are
processed by other OSPFv3 Routers in the same SPF cycle. This is an
implementation issue and the protocol itself need not try and guarantee
seamless transition. However, I will think about how to add some guidance.
One of the many advantages of OSPF over ISIS is that OSPF allows for
intelligent grouping of information in separate LSAs to avoid the inherent
problems with regeneration of LSPs.


>Waiting for new version
>-- -tony
>OSPF mailing list