Re: [OSPF] Regarding draft-ppsenak-ospf-te-link-attr-reuse-00

Chris Bowers <> Wed, 21 October 2015 17:20 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5EF341B2AEA for <>; Wed, 21 Oct 2015 10:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 25a9Yin8iwTW for <>; Wed, 21 Oct 2015 10:20:48 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fc10::1:725]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 08EC31B2AFC for <>; Wed, 21 Oct 2015 10:20:43 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.300.14; Wed, 21 Oct 2015 17:20:24 +0000
Received: from ([]) by ([]) with mapi id 15.01.0300.010; Wed, 21 Oct 2015 17:20:23 +0000
From: Chris Bowers <>
To: "Acee Lindem (acee)" <>, Shraddha Hegde <>, OSPF WG List <>
Thread-Topic: [OSPF] Regarding draft-ppsenak-ospf-te-link-attr-reuse-00
Thread-Index: AQHRC/ZPFuY7qCnGR1+q4c+BrPcEhJ519m0A
Date: Wed, 21 Oct 2015 17:20:23 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; DM2PR0501MB1389; 5:J7aO2Nd2VLRUtVobV2HLwUFGrorjoZjgcDphgP8QmmgTfqNpGa26oZWQCgPRDLP4CiLm4CQLHWDhgktlut5835a3Z9KB4mHUrx82Ylyhbmw39Io5ZJe+QgBsMg2txDSRWQiC66psqvTjmGNFXjdBbg==; 24:5XtxBx7pXtohjWTh4DFYcv05kgbgozcsqrEV0mBXSLnHhIUfImvP0yha9RdnkjV7uPIT84r8xxjxvQNW0w8lgq6lddtcO6JPVeM9iiMqKUc=; 20:1KGNRRU8Ci5AFG6/XVYhpVTGwG0KY/JQU7qRS4qx5fXUHnM0u8uVZPHw8XM1s0whQ5uGk6k94k72bzH6wyoS7g==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0501MB1389;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(138986009662008)(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(520078)(8121501046)(5005006)(3002001)(102115026); SRVR:DM2PR0501MB1389; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB1389;
x-forefront-prvs: 073631BD3D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(37854004)(199003)(51444003)(164054003)(53754006)(377454003)(189002)(561944003)(107886002)(2950100001)(2900100001)(5001960100002)(19625215002)(50986999)(76576001)(54356999)(33656002)(76176999)(15975445007)(77096005)(16236675004)(5004730100002)(46102003)(64706001)(19609705001)(87936001)(102836002)(86362001)(5003600100002)(92566002)(5007970100001)(66066001)(19580405001)(19580395003)(10400500002)(122556002)(5001920100001)(101416001)(81156007)(5001770100001)(97736004)(230783001)(5002640100001)(189998001)(99286002)(106116001)(105586002)(74316001)(5008740100001)(40100003)(1941001)(19300405004)(106356001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0501MB1389;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
Content-Type: multipart/alternative; boundary="_000_BLUPR05MB292E9628E4172C733C59BA8A9380BLUPR05MB292namprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Oct 2015 17:20:23.7295 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0501MB1389
Archived-At: <>
Subject: Re: [OSPF] Regarding draft-ppsenak-ospf-te-link-attr-reuse-00
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: Wed, 21 Oct 2015 17:20:53 -0000

In my opinion the backwards compatibility problems introduced by this proposal outweigh potential gains.

As a concrete example, there is at least one existing implementation of remote LFA where policy is used to select a backup tunnel that does not share an SRLG with the failed link.  This SRLG information is carried in the TE Opaque LSA.

As it currently reads, I think the proposal in  draft-ppsenak-ospf-te-link-attr-reuse has the potential to break existing standards-compliant implementations.

I might be OK with having the proposal only apply to sub-TLVs  that get defined in the future.  However, I think that taking TLVs that were  standardized over ten years ago, and selectively moving them or copying them to a different LSA based on a set of rules that is subject to interpretation is going to create confusion and interoperability headaches.


From: OSPF [] On Behalf Of Acee Lindem (acee)
Sent: Wednesday, October 21, 2015 6:48 AM
To: Shraddha Hegde <>; OSPF WG List <>
Subject: Re: [OSPF] Regarding draft-ppsenak-ospf-te-link-attr-reuse-00

Hi Shraddha,

From: OSPF <<>> on behalf of Shraddha Hegde <<>>
Date: Wednesday, October 21, 2015 at 1:20 AM
To: OSPF WG List <<>>
Subject: [OSPF] Regarding draft-ppsenak-ospf-te-link-attr-reuse-00

Hi All,

draft-ppsenak-ospf-te-link-attr-reuse-00 proposes moving and/or copying TLVs from the TE Opaque LSA to the Extended Link Opaque LSA. The draft lists the problems that the draft is trying to solve.  I have reproduced that list of problems below, with each problem followed by what I believe to be a better and simpler solution.

   1.  Whenever the link is advertised in a TE Opaque LSA, the link
       becomes a part of the TE topology, which may not match IP routed
       topology.  By making the link part of the TE topology, remote
       nodes may mistakenly believe that the link is available for MPLS
       TE or GMPLS, when, in fact, MPLS is not enabled on the link.

To address this issue, we simply need to define a new sub-TLV in the TE Link LSAto say whether MPLS/GMPLS/RSVP is enabled on the link instead of moving the TLVs around into different LSAs.

   2.  The TE Opaque LSA carries link attributes that are not used or
       required by MPLS TE or GMPLS.  There is no mechanism in TE Opaque
       LSA to indicate which of the link attributes should be passed to
       MPLS TE application and which should be used by OSPFv2 and other

OSPF database is a container and OSPF can use any of the LSAS for its own use including the TE LSAs.  As far as the TE database goes, it contains data from TE LSAs as well as non-TE LSAs (Network LSA) today so the reasoning described here doesn’t make sense.

   3.  Link attributes used for non-TE purposes is partitioned across
       multiple LSAs - the TE Opaque LSA and the Extended Link Opaque
       LSA.  This partitioning will require implementations to lookup
       multiple LSAs to extract link attributes for a single link,
       bringing needless complexity to the OSPFv2 implementations.

There will be nodes in the network which will run older software which send these attributes via TE LSAs so the problem of looking into the TE LSAs for TE relatedinformation doesn’t get solved with this draft.  Rather it makes it more complicated. With this draft, the multiple LSA lookup will only increase.  An implementation will first have to find if Extended link LSA contains the required info, if not it will need to look up the info in TE.LSA.

The applications using the TE parameters for non-TE use-cases will use the OSPF Prefix/Link attributes for these use cases. Hence, there is no requirement to lookup the LSAs in multiple places. Backward compatibility will be covered in the specifications of these applications.


Looking up multiple LSAs for information is an implementation issue and I am sure there will be implementations that will handle this  gracefully so that it doesn’t cause
delays in critical paths. It doesn’t seem reasonable to come up with protocol extensions to solve implementation issues.