Hello friends,

According to the RFC8345, links are point-to-point and unidirectional. But I 
can’t find too much information in the document about the reason why they 
should be unidirectional.
It would be very appreciated if someone can give me some hints?

A possible reason I think is maybe the authors considered bandwidth could be 
different in uplink and downlink, so the links should be unidirectional.
And we can also find in RFC8795 TE topology model provides lots of augmentation 
towards link object, including bandwidth, label-restriction .etc.

In the transport domain, I think people would prefer to manage bandwidth and 
tributary slot information based on port rather than link. And there is not a 
uplink or downlink neither. So the previous assumption is not valid.
If we remove the restriction that links are unidirectional, then the links 
managed by the domain controller will be reduced by half. It will relief quite 
a lot of pressure when managing a large scale of networks.
For the bandwidth and label-restriction information, maybe we can move it to 
TP, or define a RPC to let the servers retrieve by TP directly. They don’t need 
to find its corresponding link at first and then find those information, which 
is time consuming.

It is just my simple consideration, please feel free to give your comments. 
Thanks!

B.R.
Chaode
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to