Hi Dirk,
On 18/02/2019 09:31 , Goethals, Dirk (Nokia - BE/Antwerp) wrote:
support +1
1 question:
When S1 in another area receives such LSA, it then can learn that
prefix Lt1 is associated with node T1, check the ELC, ERLD, or MSD
value according to its necessity, and construct the right label stack
at the ingress node S1 for the traffic destined to Lt1.
How is S1 going to know the "ELC, ERLD, or MSD" of node T1?
I guess, T1 will need to send an AS-scoped router info LSA?
yes, that is a possibility.
If so, should T1 be ASBR as to be able to send this AS-scoped LSA?
I would not think so.
I guess it was needed before as to enforce the ABR to create the T4 LSAs,
so that others can learn which ABR to use to reach T4, but I guess
it's not needed anymore when this draft is implemented.
not sure how you reached the above conclusion. Can you please clarify?
thanks,
Peter
Regards,
Dirk
On 2/13/2019 14:25, Acee Lindem (acee) wrote:
This begins a two week adoption poll for the subject draft. Please
send your comments to this list before 12:00 AM UTC on Thursday,
February 28^th , 2019.
All authors have responded to the IPR poll and there is one
<https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-wang-lsr-ospf-prefix-originator-ext>
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-wang-lsr-ospf-prefix-originator-ext
It is listed multiple times but references the same CN201810650141.
Thanks,
Acee
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
