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

"Les Ginsberg (ginsberg)" <> Mon, 28 September 2015 23:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 932FA1A0423 for <>; Mon, 28 Sep 2015 16:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 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, 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 pnQzvmvH03vS for <>; Mon, 28 Sep 2015 16:09:05 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E2E8C1A03E1 for <>; Mon, 28 Sep 2015 16:09:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1777; q=dns/txt; s=iport; t=1443481745; x=1444691345; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=0tWF2HKA7InNS/Bw8tjhueFj429Pld5sf5xlL1uTQG4=; b=TFKFuOP4obXZ9pNgTYKbLPlvxiS+9zQpyl3s3J65v6rSlW8uhT2g92KL H636ee0N+9Hwi7fGYPID5/FOtSKjoPrpm7LocsMS6081dZUsDPpExRiEF AqgBO+CtTmMOm+O42quD9X7jQWWVucpTFQd47D3tkpq30b89TneYn8veb E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.17,605,1437436800"; d="scan'208";a="36248085"
Received: from ([]) by with ESMTP; 28 Sep 2015 23:09:04 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t8SN934w004519 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <>; Mon, 28 Sep 2015 23:09:03 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 28 Sep 2015 18:09:03 -0500
Received: from ([]) by ([]) with mapi id 15.00.1104.000; Mon, 28 Sep 2015 18:09:03 -0500
From: "Les Ginsberg (ginsberg)" <>
To: "Acee Lindem (acee)" <>, OSPF WG List <>
Thread-Topic: OSPF Link Overload - draft-hegde-ospf-link-overload-01
Thread-Index: AQHQ9/MdJMB0YsR7d0CkMD6XMtCYyZ5Sklfg
Date: Mon, 28 Sep 2015 23:09:03 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
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: Mon, 28 Sep 2015 23:09:06 -0000

In the discussion of this document thus far two major concerns have been expressed:

1)Advertising information which is of use only to the neighbor in an advertisement which is area scoped is wrong

2)The scope of the problem to be addressed is not yet well defined. In particular whether TE attributes also need to be modified and if so how this would relate to the link overload signaling approach.

I can believe that there is work here that is of interest to the WG and there may be a solution that is ultimately judged to be of value to deployments, but I would like to see a version of the draft that gets some greater degree of consensus before taking this on as a WG item. Right now I feel there is considerable doubt as to whether the draft is headed in the right direction.

I encourage the authors to consider the significant feedback received in Prague and reassess what problems need to be solved and how best to do so.


> -----Original Message-----
> From: OSPF [] On Behalf Of Acee Lindem
> (acee)
> Sent: Friday, September 25, 2015 5:35 PM
> To: OSPF WG List
> Subject: [OSPF] OSPF Link Overload - draft-hegde-ospf-link-overload-01
> In Prague, there was consensus in the room that this use case was not
> covered by existing mechanisms and that it was a problem the WG should
> solve. There were differing opinions as to the exact solution but that should
> not preclude OSPF WG adoption.
> Please indicate your support (or concerns) for adopting this as a WG
> Document.
> Thanks,
> Acee
> _______________________________________________
> OSPF mailing list