Bruno -
The intent of the RFC 8919 language is to say:
1)If there are ASLA advertisements w non-zero SABM/UABM matching the
application, these MUST be used
2)If there are no matching ASLA advertisements as per #1, then ASLA
advertisements w zero length SABM/UABM (if present) MUST be used
From: Robert Raszuk [mailto:rob...@raszuk.net]
Sent: Friday, June 4, 2021 4:50 PM
To: DECRAENE Bruno INNOV/NET
Cc: draft-ietf-lsr-flex-a...@ietf.org; lsr@ietf.org
Subject: Re: [Lsr] draft-ietf-lsr-flex-algo
To me this "permitted" is only about applying ASLA to all apps (no bit mask)
except
To me this "permitted" is only about applying ASLA to all apps (no bit
mask) except specific apps IDs matching their ID if present in the bit
mask.
It is not about applying ASLA itself or not applying it at all.
If link attributes are advertised associated with zero-length
Application
From: Robert Raszuk [mailto:rob...@raszuk.net]
Sent: Friday, June 4, 2021 3:35 PM
To: DECRAENE Bruno INNOV/NET
Cc: draft-ietf-lsr-flex-a...@ietf.org; lsr@ietf.org
Subject: Re: [Lsr] draft-ietf-lsr-flex-algo
Ok you meant domain wide not locally ... but there is already strong normative
MUST
Ok you meant domain wide not locally ... but there is already strong
normative MUST in Flex Algo as the user of ASLA so no loop will happen.
The "permitted" from ASLA RFC is just to indicate what applications may use
such attribute with zero-length
Application Identifier Bit Masks as opposed
Hi Robert,
From: Robert Raszuk [mailto:rob...@raszuk.net]
Hi Bruno,
> I think it’s self-evident that we would end up with a permanent routing loop.
Is that so ? Wouldn't it just result in unidirectional link for a given app ?
Maybe intentional ?
It seems that what you described may cause
Hi Bruno,
> I think it’s self-evident that we would end up with a permanent routing
loop.
Is that so ? Wouldn't it just result in unidirectional link for a given app
? Maybe intentional ?
It seems that what you described may cause asymmetric routing but not a
routing loop. After all packets
Hi all,
I think that I may have an issue with the way FlexAlgo [2] uses ASLA [1]
FlexAlgo is distributed routing computation so it's required that all routers
use exactly the same data to compute the routes/SPF.
FlexAlgo is clear that ASLA MUST be used:
"Link attribute advertisements that are
