Re: [OSPF] OSPF Link Overload - draft-hegde-ospf-link-overload-01

Pushpasis Sarkar <> Tue, 29 September 2015 14:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3B2E81B41D4 for <>; Tue, 29 Sep 2015 07:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id b4rnlPMbx5eN for <>; Tue, 29 Sep 2015 07:24:00 -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 061F01B41D1 for <>; Tue, 29 Sep 2015 07:23:59 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 29 Sep 2015 14:23:57 +0000
Received: from ([]) by ([]) with mapi id 15.01.0280.017; Tue, 29 Sep 2015 14:23:57 +0000
From: Pushpasis Sarkar <>
To: "Acee Lindem (acee)" <>, Shraddha Hegde <>, OSPF WG List <>
Thread-Topic: OSPF Link Overload - draft-hegde-ospf-link-overload-01
Thread-Index: AQHQ+rHmcRhLA+ujBk6ruiEe/oRn0A==
Date: Tue, 29 Sep 2015 14:23:57 +0000
Message-ID: <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
authentication-results: spf=none (sender IP is );
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; BY1PR0501MB1381; 5:lmfMc3zdt0LlDaBJJxy040BdZZYpnYv4QxvGFJZONOCcdnSVk1o+c/eo8W36iBQ4CY5jzkfwuYikh5XLLomksslgovEtRRcWhnCvf0CbC9TxcgQ6hQBCswAAHp7V4GUZoSVzdAgy0xFjKCWqlCFzWQ==; 24:HkHgH2+YEZSTYPFUV2S2AHVgReQsPleP1wgd/VH09q6GupMnMjQTdXA+ks+SqYVIeCC52n0ZIBcR731caNwIP/x/R0B5q8Gcqo9hrmpp19c=; 20:8OlgPJqDiaoyELpE9WHUhrkhH9+pIMeqwWv//pyN2Y+98aZWWKnxJL6wAtMYS21pV3uaOTkUeJg6UojEFwY9SA==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1381;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(138986009662008)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(520078)(5005006)(3002001); SRVR:BY1PR0501MB1381; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1381;
x-forefront-prvs: 0714841678
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(377454003)(24454002)(479174004)(164054003)(5001960100002)(5001770100001)(2900100001)(5004730100002)(11100500001)(5002640100001)(5007970100001)(4001540100001)(77096005)(19580395003)(81156007)(102836002)(19580405001)(68736005)(189998001)(10400500002)(87936001)(97736004)(77156002)(2950100001)(5001860100001)(4001350100001)(92566002)(46102003)(1941001)(5008740100001)(93886004)(62966003)(86362001)(99286002)(5001830100001)(50986999)(106116001)(40100003)(230783001)(33656002)(122556002)(106356001)(76176999)(101416001)(105586002)(64706001)(54356999)(83506001)(66066001)(82746002)(83716003)(36756003)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1381;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Sep 2015 14:23:57.0596 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1381
Archived-At: <>
Cc: Hannes Gredler <>, 'Mohan Nanduri' <>, "Jalil, Luay" <>
Subject: Re: [OSPF] OSPF Link Overload - draft-hegde-ospf-link-overload-01
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: Tue, 29 Sep 2015 14:24:02 -0000

Hi Acee,

On 9/29/15, 6:07 PM, "Acee Lindem (acee)" <> wrote:

>Speaking as a WG participant:
>Hi Pushpasis, 
>We seem to be a having a failure to communicate.
[Pushpasis] I am very sorry if I have really broken the communication channel here. But I thought we were communicating well so far :)

>On 9/29/15, 8:25 AM, "Pushpasis Sarkar" <> wrote:
>>On 9/29/15, 5:17 PM, "Acee Lindem (acee)" <> wrote:
>So, to sum up #1 and #2, you feel this approach is more “logical”. This is
>a subjective argument.
[Pushpasis] Offcourse, all the points here is my personal opinion. I don’t claim that they are anyone else’. Others may or may not agree with them.

>The alternative is using link-local signaling to tell the neighbor that
>the link is going down for maintenance. Hence, the metric and TE metric
>are set in both directions. I thought we already established that there is
>no debate on this issue. Hopefully, we can refrain from any more lengthy
>explanations on setting the metrics or how TE works.
[Pushpasis] But the alternative you are suggesting does not seem to be specified in any document so far. I maybe wrong, but I thought this way of signaling to the neighbor about the link is going down on this side and asking neighbor to take down at his end was being proposed for the first-time in this document. You can correct me if my knowledge / understanding is wrong, and I shall take back statement immediately.

>Which bring us back to my original question that is still unanswered, why
>would the controller action of diverting traffic be any different for an
>LSP on which one of the component links has max metric?
[Pushpasis] Like mentioned already, and again in my opinion, this will help the controller deal with scenarios where it needs to distinguish between situations in which a link has been administratively put into ‘out-of-order’ from situations where the link has degraded to a ‘malfunctioning’ state and needs attention. Unfortunately I cannot come up with a use-cases how this distinction can be used (other than diverting service traffics away from the links). Perhaps some of the operators may throw more light. 

Hoping I have not failed to communicate once more. If you still feel so, please let me know. And I will refrain myself from answering on this thread further.

Thanks once again and regards.