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

Shraddha Hegde <> Mon, 10 July 2017 04:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 56A741204DA for <>; Sun, 9 Jul 2017 21:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Status: No, score=-2.022 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_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 499vEgfQrzL1 for <>; Sun, 9 Jul 2017 21:52:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B7A9A1201FA for <>; Sun, 9 Jul 2017 21:52:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=89pxUS717S3Y24rhvCbqmciz2YRdiqr+VDiOYDbg9Qs=; b=Yb5oeih065VaIyt6zj1/G0zVd4bsvtuLP/Eyi4K8ih7qDVlpGRzt+8Tp5Q1y49rdf15Eyk5Lk4CZgNVyqEDoE9H0e8e51fPxfmTK3CqpfKMSkSnXMhH1/aCBS2Aiqt+AUp4DuP1B+HLzBpwB9LXmCzKUT11e+bXDaecIYoS5FsA=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.4; Mon, 10 Jul 2017 04:52:11 +0000
Received: from ([]) by ([]) with mapi id 15.01.1261.012; Mon, 10 Jul 2017 04:52:11 +0000
From: Shraddha Hegde <>
To: "Acee Lindem (acee)" <>, "Peter Psenak (ppsenak)" <>, "Ketan Talaulikar (ketant)" <>
CC: "" <>
Thread-Topic: [OSPF] I-D Action: draft-ietf-ospf-link-overload-07.txt
Thread-Index: AQHS872MmunnbxdiUkySE3Vqotv+OqJBlF3ggASaFICAAD2BgIAAH/6AgAX7z+A=
Date: Mon, 10 Jul 2017 04:52:11 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR05MB2419; 7:BDcQ04MdMeBlnwtzrANNB8Q7L0N85e/OPyMfh21SvBfWlsLHRgQ580R6CR9TcZ1GhKkdAz3IJnlpFZBYVTU2qvoIzoy5Jv2glm9QGtoZZo7X0iExrSxktrbMrl+Y9dQIqk6g2pfQG+8SE/nxictNTH6lZsRbOzyNkW6shgczayQLQsSZkCe5AUjsMNgKmDPun2BoezhViGCVS3YMla9IWTv3NUZJstvaePrfy5Cn4YWHVIgnbYZLSGHgRuOPUJMwsUEv422bikrsIYf5MsdNPUa8yJXTCbWAy17yWnCE9S0Q3p1a5HVH8FbHb+yFYcIoOFiSKy8duuxbUSGiD1CvRG1KDHU5HYjJ+9XbltdkXMZiWYexRd7t3JKcgaORbFw/BQV7ivsoHg7dUCowvqqVdRtXWc0KMuO/s53wYjnhUvkHp8hGI3MjAMX2mw8hzJuieqtHDGDnjXwD2bQz9Yn6eR4h0kPrGDrep5U0WvdcFosf+y4XtnoB2PljpfNRR7YMZc7eq2B9IHN18/Nqh24OFn+RjNqFZfe3TZUekHKmDeb2fsDRfBqPX5TX9+ywe/BQCF/p2DHhfFwMiwWYeRFXdeW8Ku/0aabuufm609ROJcYCyJbeM4VqABGCxoIA0eum/8RFxIRmzCyHWCWMC2TcweBvroaqjXXPojrO0NMv1Md1XfqGJAmpRT0xfZT9/WcCyoCnOAlNdtzJUHYQO6SrXcl0GQEq7lKqHf40CkvUCOEASH1vZTjVWU9xmTFQJVO872f573iHcoaSnvoLkkTP+/UENdgeNtqexUIlRALAs2E=
x-ms-office365-filtering-correlation-id: 92a40031-340e-4b25-ce76-08d4c74f6d44
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN3PR05MB2419;
x-ms-traffictypediagnostic: BN3PR05MB2419:
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(278178393323532)(133145235818549)(120809045254105)(236129657087228)(138986009662008)(95692535739014)(167848164394848)(247924648384137)(148574349560750);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(2017060910075)(8121501046)(5005006)(93006095)(93001095)(10201501046)(100000703101)(100105400095)(3002001)(6055026)(6041248)(20161123558100)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123555025)(20161123564025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR05MB2419; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR05MB2419;
x-forefront-prvs: 03648EFF89
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39840400002)(39450400003)(39400400002)(39850400002)(39860400002)(13464003)(377424004)(377454003)(24454002)(99286003)(74316002)(305945005)(77096006)(53936002)(102836003)(38730400002)(2950100002)(6116002)(3846002)(50986999)(6306002)(9686003)(2906002)(230783001)(5660300001)(6436002)(55016002)(6506006)(76176999)(54356999)(86362001)(229853002)(93886004)(7696004)(966005)(25786009)(33656002)(8676002)(53546010)(81166006)(4326008)(189998001)(2900100001)(14454004)(8936002)(7736002)(478600001)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2419;; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2017 04:52:11.4931 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2419
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: Mon, 10 Jul 2017 04:52:16 -0000


Link-local flooding was added as an optimization for use-cases that do not need area level flooding on request from Acee.
I agree flooding area level in all cases is a reasonable way forward as the overhead isn't much.

If anyone has objections to removing Link-local scope advertisement, do let me know.


-----Original Message-----
From: Acee Lindem (acee) [] 
Sent: Thursday, July 6, 2017 2:55 PM
To: Peter Psenak (ppsenak) <>; Ketan Talaulikar (ketant) <>; Shraddha Hegde <>
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-07.txt

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 of.
>> 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 plane  post adjacency establishment. 
>>The link-overload information typically needs to be processed  after 
>>adjacency establishment, it introduces unnecessary complexity in hello 
>> 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:
>> 7
>> 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