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

Shraddha Hegde <> Wed, 19 April 2017 13:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 21E0C129543 for <>; Wed, 19 Apr 2017 06:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Status: No, score=-2.021 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 pwzKgdnUAZEI for <>; Wed, 19 Apr 2017 06:08:56 -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 C576D129418 for <>; Wed, 19 Apr 2017 06:08:55 -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=75qip6Bf4xp966UbMDPNn5yy4W9AS4WMaLwhgIaUbk8=; b=OIfFHdHW5h6a8if8MBjSDBVy/iV9/pDMh6qN3bIuviH/ICsLyLTi1490TaD2tzIUrNQREi+PK13yxR0NoJzuuETjsGrQKwLb1C152pNacXg5TU6DS8QYC20gn7vkoRWlM5fsYZV0LlS1mqUfgVlCD4C/Nwm6MKYwPG0Syl0qCQ0=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.6; Wed, 19 Apr 2017 13:08:54 +0000
Received: from ([]) by ([]) with mapi id 15.01.1047.008; Wed, 19 Apr 2017 13:08:53 +0000
From: Shraddha Hegde <>
To: "Acee Lindem (acee)" <>
CC: "" <>
Thread-Topic: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Thread-Index: AQHSjfBr/zBnN6RWkkuWtTeurnw/t6GZplOAgDNYtkA=
Date: Wed, 19 Apr 2017 13:08:53 +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; BN3PR05MB2708; 7:8nqI25Qhe73BssXI/D9YS/HDC/laZ7FB+iqCrxFkgbFoWyxXQyvccC3OeF7Zmh9gmqXdOFyEdfnsgU8wtJZT9CFyLlAdvGblCnNsGDLFTg69Ei4s03ebHeXdr/JLTFCwIh1NGW0gUfmhm5tWgVpm/mbO/quJG78hmYd2UW8uKXpStlR638Zw3u/YPhr4g7JSV9JI4+EqGXmpQEHNVdJL1ITK6ioQLywZZnw9u346YVhFcmfc6OWj5T82ETJQs1I2MvVfScqbibCLR7sAoSSYxPXSB4E+bzjZmvPyo+RbXjAaHekwCCEavDOPo0mVL8Hwu2HlDhQ/lve7hkMkh7eOUA==
x-ms-office365-filtering-correlation-id: 7defdc2f-2573-49ee-d9ef-08d487253ac7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:BN3PR05MB2708;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123562025)(20161123555025)(6072148); SRVR:BN3PR05MB2708; BCL:0; PCL:0; RULEID:; SRVR:BN3PR05MB2708;
x-forefront-prvs: 028256169F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(39400400002)(39410400002)(39850400002)(39840400002)(39450400003)(377424004)(377454003)(24454002)(13464003)(33656002)(102836003)(3846002)(5660300001)(122556002)(6116002)(189998001)(74316002)(2900100001)(230783001)(305945005)(7736002)(3660700001)(53936002)(3280700002)(7696004)(2950100002)(86362001)(6506006)(6916009)(76176999)(54356999)(50986999)(53546009)(2906002)(77096006)(25786009)(8936002)(229853002)(38730400002)(81166006)(4326008)(6306002)(8676002)(110136004)(55016002)(6436002)(99286003)(9686003)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2708;; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Apr 2017 13:08:53.3576 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2708
Archived-At: <>
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.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: Wed, 19 Apr 2017 13:08:58 -0000

Hi Acee,

New version draft-ietf-ospf-link-overload-06 is posted where the remote-ipv4 addr is moved to a new sub-TLV.
Pls review.

The authors of the draft believe that draft has undergone multiple revisions/reviews and is ready for WG last call.


-----Original Message-----
From: OSPF [] On Behalf Of Acee Lindem (acee)
Sent: Saturday, March 18, 2017 2:28 AM
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt

Hi Shraddha, et al,

With respect to section 4.1, I agree that matching link endpoints in
OSPFv2 requires more information. However, this is a general problem and the remote address should be a separate OSPFv2 Link Attribute LSA TLV rather than overloading the link overload TLV ;^)


On 2/23/17, 11:18 AM, "OSPF on behalf of"
< on behalf of> wrote:

>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 IETF.
>        Title           : OSPF Link Overload
>        Authors         : Shraddha Hegde
>                          Pushpasis Sarkar
>                          Hannes Gredler
>                          Mohan Nanduri
>                          Luay Jalil
>	Filename        : draft-ietf-ospf-link-overload-05.txt
>	Pages           : 13
>	Date            : 2017-02-23
>   When a link is being prepared to be taken out of service, the traffic
>   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's also a htmlized version 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