Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-07.txt

"Acee Lindem (acee)" <> Thu, 06 July 2017 09:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C19591270A3 for <>; Thu, 6 Jul 2017 02:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HfhiZIjY4-03 for <>; Thu, 6 Jul 2017 02:24:49 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9C0531201F8 for <>; Thu, 6 Jul 2017 02:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=8884; q=dns/txt; s=iport; t=1499333089; x=1500542689; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YU1sFLiNp0Hz0e06W3ue/XeKLoM6s5YmkJPpChrCtSQ=; b=HKXrNMgKAnle5ZS+9WlL/V6LPyUqJ5dwtzLe2flyWr5ZcfD+MZjw1qQy ktnxvtxP+Nicjdv85GmSUatnG90RGqfUX+tc4ySvgKSYCnMkEsntbCIye 35gIgNhRltypt6XcuP9Lke3bshOfwyGmxTXqHRfr7tkC1YHz/srsGCsTx o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.40,316,1496102400"; d="scan'208";a="445960800"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Jul 2017 09:24:48 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v669OmBx032236 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 6 Jul 2017 09:24:48 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 6 Jul 2017 05:24:47 -0400
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Thu, 6 Jul 2017 05:24:47 -0400
From: "Acee Lindem (acee)" <>
To: "Peter Psenak (ppsenak)" <>, "Ketan Talaulikar (ketant)" <>, Shraddha Hegde <>
CC: "" <>
Thread-Topic: [OSPF] I-D Action: draft-ietf-ospf-link-overload-07.txt
Thread-Index: AQHS872QjInnv2SGxUWOkn5sMNtx9qJB2ZCAgASX74CAAD2BgP//3OoA
Date: Thu, 06 Jul 2017 09:24:47 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-07.txt
X-Mailman-Version: 2.1.22
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, 06 Jul 2017 09:24:52 -0000

Hi Peter, Shradha, 

On 7/6/17, 3:30 AM, "OSPF on behalf of Peter Psenak (ppsenak)"
< on behalf of> wrote:

>On 06/07/17 05:50 , Ketan Talaulikar (ketant) wrote:
>> Hi Shraddha,
>> Thanks for taking care of some of the comments shared previously.
>>Please find below some more that were probably missed or not taken care
>> 1) I see that the use of link-local scope RI LSA has still been
>>retained in this version and not sure why. RI LSA is for node attributes
>>and it's use for signalling of link is not right IMO. Why not use the
>>link-local scope Extended Link LSA instead?
>an alternative would be to always flood area scope Extended Link LSA. It
>should not harm anything and could be used by other routers in area as a
>"heads-up" that remote link is becoming overloaded.

I think this would be a good way forward as the OSPF Extended Attribute
LSA will most likely be advertised for SR in OSPF Service Provider domains
anyway. So, just advertising the area-scope for all use cases would seem
to be the simplify this approach and get us past this discussion. In fact,
the -00 version of the draft had area-scope alone and I, regretfully, had
suggested the OSPF RI as possible way to get support either scope.


>> 2) Sec 5.1, why is advertising of MAX-METRIC for the link to be
>>overloaded a SHOULD and not a MUST? Isn't this mandatory to ensure
>>backward compatibility? What if the router on which overload is
>>signalled does not do MAX-METRIC but the implementation on the remote
>>side end up doing MAX-METRIC. Would it not result in asymmetric metric
>>in a un-intended manner? Please consider changing all SHOULD here to
>>MUST to ensure backward compatibility.
>> 3) Sec 5.4, can you please make similar change in language related to
>>the RFC4203 reference as you've done in other parts in this version?
>> Also I don't agree with the rationale you've given for not using LLS
>>for the link-local signalling. Even if the hello processing were
>>delegated to the LC, there are already a lot of protocol events which
>>can happen via hello packets (which includes LLS) that require
>>signalling update to the control plane OSPF main process. An
>>implementation aspect such as this should hardly be a good reason to not
>>use LLS for link-local signalling such as overload.
>+1 on the above.
>> Thanks,
>> Ketan
>> -----Original Message-----
>> From: OSPF [] On Behalf Of Shraddha Hegde
>> Sent: 03 July 2017 11:11
>> To:;
>> Cc:
>> Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-07.txt
>> New version of the ospf-link-overload draft is posted.
>> Editorial comments received so far have been addressed in this version.
>> There was one comments to move the link-overload sub-TLV to LLS in
>>hello messages.
>> Many implementations delegate the Hello processing to
>>linecards/different deamons
>> Once adjacency is established. Hello messages are not sent to control
>> post adjacency establishment. The link-overload information typically
>>needs to be processed
>> after adjacency establishment, it introduces unnecessary complexity in
>>hello processing.
>> We had a discussion among authors on this and feel advertising
>>link-overload sub-TLV
>> in the LSAs is the most appropriate mechanism.
>> Rgds
>> Shraddha
>> -----Original Message-----
>> From: OSPF [] On Behalf Of
>> Sent: Monday, July 3, 2017 11:01 AM
>> To:
>> Cc:
>> Subject: [OSPF] I-D Action: draft-ietf-ospf-link-overload-07.txt
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> This draft is a work item of the Open Shortest Path First IGP of the
>>          Title           : OSPF Link Overload
>>          Authors         : Shraddha Hegde
>>                            Pushpasis Sarkar
>>                            Hannes Gredler
>>                            Mohan Nanduri
>>                            Luay Jalil
>> 	Filename        : draft-ietf-ospf-link-overload-07.txt
>> 	Pages           : 14
>> 	Date            : 2017-07-02
>> Abstract:
>>     When a link is being prepared to be taken out of service, the
>>     needs to be diverted from both ends of the link.  Increasing the
>>     metric to the highest metric on one side of the link is not
>>     sufficient to divert the traffic flowing in the other direction.
>>     It is useful for routers in an OSPFv2 or OSPFv3 routing domain to be
>>     able to advertise a link being in an overload state to indicate
>>     impending maintenance activity on the link.  This information can be
>>     used by the network devices to re-route the traffic effectively.
>>     This document describes the protocol extensions to disseminate link-
>>     overload information in OSPFv2 and OSPFv3.
>> The IETF datatracker status page for this draft is:
>> There are also htmlized versions available at:
>> A diff from the previous version is available at:
>> Please note that it may take a couple of minutes from the time of
>>submission until the htmlized version and diff are available at
>> Internet-Drafts are also available by anonymous FTP at:
>> _______________________________________________
>> OSPF mailing list
>> _______________________________________________
>> OSPF mailing list
>> _______________________________________________
>> OSPF mailing list
>> .
>OSPF mailing list