Re: [Lsr] Comments on Requested Codepoints for draft-li-lsr-isis-area-proxy

Hannes Gredler <> Thu, 25 June 2020 17:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 99DD53A0E0A; Thu, 25 Jun 2020 10:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oEtX5TdHgbCo; Thu, 25 Jun 2020 10:47:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A5D0F3A0E08; Thu, 25 Jun 2020 10:47:16 -0700 (PDT)
Received: from ([::ffff:]) (AUTH: PLAIN hannes, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by hirzer with ESMTPSA; Thu, 25 Jun 2020 19:47:13 +0200 id 00000000000BD8E4.000000005EF4E321.000034AD
From: Hannes Gredler <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9A70E53D-0982-4365-BE90-BFD96ECFA6ED"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Thu, 25 Jun 2020 19:47:12 +0200
In-Reply-To: <>
Cc: Les Ginsberg <>, "" <>, "" <>
References: <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Lsr] Comments on Requested Codepoints for draft-li-lsr-isis-area-proxy
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 25 Jun 2020 17:47:29 -0000

Hi Tony,

I do share Les’ concerns on burning top-level 8-bit code point space at this point.

At this point it is not me to judge wether CAP TLV or GENAPP TLV or something else should be a more appropriate place.
Please let's have a WG discussion on this.



> On 21.06.2020, at 18:50, wrote:
> Les,
>> We don’t have to resolve this now.
>> One of my motivations for sending this was related to Early Allocation of code points. Since you have already asked once, I am assuming that if WG adoption is achieved it will be swiftly followed by an early allocation request – and as one of the Designated Experts I wanted to share my concerns sooner rather than later.
> I appreciate that.  Do others share Les’ perspective on the relative tradeoffs?  Especially our other Desginated Experts?
>> Would this argue for advertising “this is a boundary circuit” in pseudo-node LSPs for boundary circuits rather than advertising “inside” on all inside pseudo-nodes?
>> You could do it that way.  It inverts the semantics and inverts the deployment.  Logically, it should have the same effect.  However, it then is seen by outside nodes.  Since they need not support Area Proxy, this seemed like a riskier approach, thus we opted for marking inside pseudonodes.
>> [Les:] My point was largely motivated by the statement in the draft:
>> “Area Proxy Boundary multi-access circuits (i.e.  Ethernets in LAN
>>    mode) with multiple Inside Edge Routers on them are not supported.”
>> So it seems advantageous to be able to prevent this from happening – which requires some signaling on the circuit in question.
> I think that the case that you’re concerned about is already easily detected.  Recall that an Inside Edge router will generate IIH’s onto a boundary circuit using the Proxy system ID.  Thus, if an Inside Edge router receives an IIH with a source address of it’s own proxy system id, then it has encountered this issue.
> Tony
> _______________________________________________
> Lsr mailing list