search

scionassociation / scion-cp_I-D

Specification of the SCION control plane.
https://scionassociation.github.io/scion-cp_I-D/
Other
1 stars 0 forks source link

Clarify PCB selection policies and endpoint's needs #33

Closed matzf closed 2 months ago

matzf commented 3 months ago

Fixes #16.

From: Joel Halpern There seems to be a philosophical contradiction in section 2.3.1 (Selection of PCBs to propagate) of the control plane document. Given the philosophy of SCION, the goal should be to propagate PCBs with the highest probability of collectively meeting the needs of the end hosts that will perform path construction. Of course, this AS doesn't know that. But the text ignores this distinction.

Tis also relates to rfc9217 section-2.8:

how can the incentives of network operators and end users be aligned to realize the vision of path-aware networking, ..

Very good phrasing from reviewer, paraphrased in the text. Tried to clarify the incentives by explaining it as a two stage process. First the AS removes anything that doesn't seem "viable"; among the remaining PCBs, the incentives of AS and endpoints are aligned.