Re: [Isis-wg] WG Last Call for draft-ietf-isis-reverse-metric-07

"Naiming Shen (naiming)" <> Sat, 30 December 2017 19:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D7B19126DC2; Sat, 30 Dec 2017 11:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 zvJTERdic6vq; Sat, 30 Dec 2017 11:58:59 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 475901205F1; Sat, 30 Dec 2017 11:58:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=37452; q=dns/txt; s=iport; t=1514663939; x=1515873539; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=hZnsPQFmpU/QMqalS8HL9EJYPU8WIXDLl997GeVoDp4=; b=DWX1zludn4msUANFOL3DcDtZBkTOGAKc/WoO6MGLnNZBUNlsw+cqeh/E MVgfoBZ3HXfDgb4EkLoMbQxfYA7AFX/ufReQdagk2/KdEFa2cXaNWg/3i 1ZkkiqCSMOykjpAy9X1o/IEpT/45RxxHb9RNUrEq6bFyBVA4EAzvhmKpS s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.45,482,1508803200"; d="scan'208,217"; a="50694561"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Dec 2017 19:58:57 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id vBUJwuTp028118 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 30 Dec 2017 19:58:57 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 30 Dec 2017 13:58:56 -0600
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Sat, 30 Dec 2017 13:58:56 -0600
From: "Naiming Shen (naiming)" <>
To: Alexander Okonnikov <>
CC: "Ketan Talaulikar (ketant)" <>, Christian Hopps <>, "" <>, "" <>
Thread-Topic: [Isis-wg] WG Last Call for draft-ietf-isis-reverse-metric-07
Thread-Index: AQHTXmMvIlsDCkaUj0W5jcon0L55haMrdnkAgAD5RwCAFzjKAIAWpEsAgAEWT4CAAZXigA==
Date: Sat, 30 Dec 2017 19:58:56 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_DB2AF03053B04566BF77D1CE161406D4ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Isis-wg] WG Last Call for draft-ietf-isis-reverse-metric-07
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 30 Dec 2017 19:59:03 -0000

Hi Alex,

Ok. We’ll add a bit to the flag (the 2nd bit) of the ‘reverse-metric TLV’, to indicate
the originator requesting the inbound direction of the link not to be used and the
metric should be raised by the peer to (2^24 - 1) regardless the value of the ‘offset metric’
value in the TLV.

- Naiming

On Dec 29, 2017, at 11:46 AM, Alexander Okonnikov <<>> wrote:

Hi Naiming,

29 дек. 2017 г., в 6:10, Naiming Shen (naiming) <<>> написал(а):

Hi Alexander,

Thanks for the comments, see more replies inline.

On Dec 14, 2017, at 9:24 AM, Alexander Okonnikov <<>> wrote:

Hi authors,

I have some comments below regarding the draft:

1) Section 2: "There is currently only two Flag bits defined." Per -07 only one flag is defined. S flag was deprecated since version -06 (implicit signaling of presence of Sub-TLVs is used via "Sub-TLV Len" field non-zero value. Text in the beginning of the chapter 2 about flag S is to be removed as well.

NS> will fix.

2) Section 3.1: "In order to ensure that an individual TE link is used as a link of last resort during SPF computation, ..." I guess that you meant regular link rather than TE link.

3) For the same section: Per my understanding, this section assumes that overloaded link will always be considered as last-resort link. I.e. it cannot be excluded from topology (as link with metric 2^24-1), unless originator of the TLV sets appropriate bit in corresponding Link Attributes Sub-TLV (RFC 5029) AND receiving ISs support that Sub-TLV. As alternative it could be done by allowing for originator to specify reverse metric special value 2^24-1 which would indicate to receivers that the link is to be excluded from topology completely rather than used as last resort. If reverse metric value is between 0 - 2^24-2 then link could be used in path calculation. The same rules for TE metric.

NS> I don’t see there is much difference between not used or last resort in the use cases we mentioned.
also, this metric value is an ‘offset metric’ being added on top of the existing local metric. It would not
be always feasible to make the reverse-metric off by one to mean two completely different operations.

One use case when unusable link vs last resort one makes sense is for IGP-LDP sync. Let's assume we have two-level IS-IS domain. There are three ISs in the domain: R1 and R2 are L1/L2 ISs, and R3 is L1-only. R1 and R2 are connected to each other via L2 circuit, and R3 is connected to R1 and R2 via L1 circuits. The link between R2 and R3 was broken and now is being restored. While adjacency has not been established on failed link, R3 has inter-area route towards R2's loopback. Once adjacency has been established, but LDP session has not yet, R3 and R2 maximize metric (2^24-2) on corresponding link. But now R2 and R3 have routes to each other as L1 intra-area, though with max metric. Because L1 intra-area route wins, R2 and R3 replace inter-area routes to each other by intra-area ones. As a result, LDP LSPs are blackholed. On the other hand, if two routers mark corresponding link as unusable (with metric 2^24-1), they would use inter-area routes until IGP-LDP sync will be completed.

An IS can make decision on whether to mark link as unusable or as last resort, using the same principle as proposed in RFC 6138.

4) For the same section: The draft says that if originator uses narrow metric-type, it should use value 63 as max-metric. But on receiving reverse metric with such value receivers have no idea whether this is "narrow" max-metric or offset 63 for "wide" metric. I.e. the draft assumes that all ISs use the same type of metric, and using of two metric types at the same time is not covered. May be it would be appropriate to define two Reverse Metric TLVs, like IS Neighbors TLV and Extended IS Reachability TLV. Or to specify new flag to mark type of the reverse metric.

NS> to be simple, we have to assume a network is either run wide or narrow. It can not be fixed. The
document is trying to be complete to mention the ‘narrow’ case.

5) For the same section: It is not clear for me why DIS should use min(63, (Metric + Reverse Metric)) while composing pseudonode LSP. If DIS is configured for using "wide" metric-type, it will use Extended IS Reachability TLVs for describing its neighbors. Moreover, in this case DIS is not obligated to still insert IS Neighbors TLVs in its Pseudonode LSP (in addition to Extended IS Reachability TLVs) when it is configured for "wide-only" mode.

NS> agreed. will remove this, to keep the same goal as above, to be simple. Not to mix them.

6) For the same section: It is not clear for me why in case when TE metric offset is not advertised in Reverse Metric TLV, receiving IS must modify its TE metric by adding IGP reverse metric value. In my mind, it would be straightforward to use follow rule: if originator doesn't include TE metric part then it doesn't wish to overload TE link, but only IGP link. For example, originator advertises Reverse metric TLV as part of IGP-LDP synchronization procedure (section 3.5). It is not reason to impact TE properties (metric in this case) of the link. Hence, originator could advertise Reverse metric TLV without TE metric Sub-TLV, in order to signal that "TE metric is left intact”.

NS> sounds resonable. Will change this to say if the sub-TLV of TE is not received, the TE properties will not change
by receiving this ‘reverse-metric’ TLV.

7) Section 3.3: The draft is not clear about handling of TE metric by DIS. Usually DIS implementations don't insert TE Sub-TLVs into Extended IS Reachability TLVs in Pseudonode LSP. May be it would be better to add explicit text that: if DIS receives TE metric Sub-TLV in Reverse Metric TLV it should update TE Default Metric Sub-TLV value of corresponding Extended IS Reachability TLV OR insert new one if it was not present there.

NS> To me, there is not much difference between DIS and other nodes. Will try to add some words to that.

- Naiming


30.11.2017 01:47, Naiming Shen (naiming) пишет:
Hi Ketan,

thanks for the support and comments. some clarification inline,

On Nov 28, 2017, at 11:54 PM, Ketan Talaulikar (ketant) <<>> wrote:


I support this draft, however would like the following aspect/scenario clarified.

Consider the scenario where both the neighbours on a p2p link initiate the reverse metric procedure (i.e. include the TLV in their hellos concurrently). How are implementations supposed to handle this? Normally the choice of metric conveyed via this TLV is based on a particular condition (which need not just be "overload") on the local router which requires the neighbour to use shift to using the reverse metric supplied. So when both neighbours initiate this process, it would be good to have the specification provide a deterministic behaviour since the reverse metric values provided may conflict in certain "non-overload" conditions. If both routers simply accept the value supplied by their neighbour, it may not achieve the original purpose/design of this triggering this mechanism?
When you say if both sides initiated this ‘reverse metric’, you implied
there is a timing issue with this procedure in the draft.

The value of this ‘metric offset’ (or whatever will be called) of this TLV,
is just a number. The draft does not say this number is equal to the
configured ‘metric’ value plus the received ‘reverse metrc’ value, that
would be non-deterministic and both sides would keep going up until it’s

Each side of IS-IS link decides if it needs to send a ‘reverse metric’ over the link,
either in link-overloading case, or other cases. It’s a static number, it does not
depend on the other side sending a ‘reverse metric’ or not. This both sides
sending a ‘reverse-metric’ over a link is equivalent to an operator provisions
new metric (say both plus 10 to the old metric) on both sides of the link at
the same time, there is no non-determinitic thing in this.

- Naiming

Following options come to my mind:
a) when this condition is detected, none of the routers actually apply the reverse metric procedure
b) when this condition is detected, the router with higher/lower system-id value (or some such tiebreaker) wins and the other withdraws its reverse metric (until then (a) applies)
c) some mechanism/rule that is based on the value of metric offset specified perhaps (made harder since the actual metric is not signalled but the offset) which determines the "winner" so the other withdraws their TLV.

Since the mechanism is not specific to overload conditions (where this is not an issue), it may be necessary for the specification to clarify this behaviour to ensure interoperability.


-----Original Message-----
From: Isis-wg [] On Behalf Of Christian Hopps
Sent: 16 November 2017 04:13
Subject: [Isis-wg] WG Last Call for draft-ietf-isis-reverse-metric-07

The authors have asked for and we are starting a WG Last Call on

which will last an extended 3 weeks to allow for IETF100.


Isis-wg mailing list

Isis-wg mailing list
Isis-wg mailing list<>