Robert –

From: Robert Raszuk <[email protected]>
Sent: Monday, August 23, 2021 10:44 AM
To: Les Ginsberg (ginsberg) <[email protected]>
Cc: Shraddha Hegde <[email protected]>; Tony Przygienda 
<[email protected]>; Ron Bonica <[email protected]>; [email protected]
Subject: Re: [Lsr] New Version Notification for 
draft-hegde-lsr-asla-any-app-00.txt


You continue to confuse Flex and ASLA.

I don't think so ... This thread is about ASLA encoding for Flex-Algo.
[LES:] Noooo --- please read your own draft. 😊]
The work “Flex” does not appear anywhere in the draft – nor should it.

ASLA is an architecture that supports multiple applications – of which Flex is 
just one of the supported applications.

Care to elaborate why ASLA SABM allows only 64 applications ? Even MT allowed 
4K topologies.

[LES:] Application != topology
As you see, a single application (Flex) can support multiple “topologies” – but 
that is orthogonal.
The real issue here is you continue to not fully understand the distinction 
between an “application” and the capabilities of a given application – one of 
which may be to support multiple “topologies”.
Flex is a specific application which supports multiple “sets of constraints” – 
AKA algorithms.

With that definition everything is Flex. Topologies differ one from another by 
running SPT on a different sets of links with different "sets of constraints"

[LES:] Nooo…the bits in the SABM mask are assigned in 
https://www.iana.org/assignments/igp-parameters/igp-parameters.xhtml#link-attribute-application-identifiers
(Note that Flex has a bit assignment which is not yet reflected there.)
You need to allow that a new application might have completely semantics.
And, Flex is doing just fine as it is – one of the indicators of which I 
believe is your enthusiasm for it. 😊

Let's see if the reverse works :)

[LES:] Sorry – standing the hierarchy on its head does not make sense – no 
matter how many times you suggest it.

   Les

Best,
R,
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to