Tony –
You ask very important questions – but – as Acee has answered in a subsequent
email – all of these questions were openly debated in the WG during the work on
what became RFC8919/8920. This debate was contentious, took years, and the WG
eventually reached consensus on what became the two RFCs.
If every time a new attribute is defined we reopen the original debate, then we
will never move forward and we will have great difficulty in deploying
interoperable implementations.
I can respect that you might have preferred a different conclusion on the part
of the WG – but I hope you will also acknowledge that this is now a resolved
issue and we need to move forward following the existing RFCs.
Parenthetically, I do believe that answers to your questions can be found in
the RFCs. The answers may not satisfy you – but we did attempt to include the
context which drove the ASLA solution.
Thanx.
Les
From: Lsr <[email protected]> On Behalf Of Tony Li
Sent: Wednesday, July 28, 2021 1:06 PM
To: Les Ginsberg (ginsberg) <[email protected]>
Cc: [email protected]; Shraddha Hegde <[email protected]>
Subject: Re: [Lsr] Generic metric: application-specific vs
application-independent
Les,
ASLA exists to support the advertisement of attributes which can be used in
application specific ways.
Why do we need separate and different copies of attributes for different
applications?
The SRLG tries to capture the risk relationships between multiple links. Those
relationships don’t change depending on the application.
Link attributes don’t require the variability that ASLA provides, and the
overhead is high. How does this cost/benefit ratio make sense?
In any particular deployment case, a given attribute advertisement might be
used by one app, multiple apps, or all apps.
ASLA allows to unambiguously support all of these cases with a single
advertisement encoding format.
The correct question to be resolving here is indeed the question which has been
discussed in an earlier thread: Is Generic Metric a link attribute which can
have application specific use cases? I think the question to that is
unquestionably “yes”.
That should be enough (IMO of course) to close the discussion.
Well, one nice thing is that there is an entire space of metrics available. If
application A wants to use metric 16 and application B wants to use metric 122,
that’s already doable.
Why do we need a separate space per application????
Tony
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
