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

Clarifications about AS interfaces and peering #17

Closed nicorusti closed 2 months ago

nicorusti commented 3 months ago

From: Joel Halpern There is no description of how an A control service knows the existence of the many AS interfaces, whether they are core, up, down, or peering interfaces, and what AS they go to.

There is also no information about how the needed properties of peering adjacencies are made available to the control service.

Also, somewhere (not sure if it is a data plane or control plane mechanism), there needs to be a mechanism to translate neighbor interface identifiers to underlay addresses.

Most if this is pre-configured by the AS, in the OS implementation in the topology file, we should indeed add something about this to the draft.

Also, Eliot commented about peering ASe: We use the expression in the introduction. We say that peering links can cross ISDs. We need to define what is a peering AS (especially WRT to case outside an ISD). Important to make it clear that peering is possible across ISDs.

jiceatscion commented 3 months ago

I tried to address all three points by I probably failed at least one. PTAL.

nicorusti commented 3 months ago

I think this is addressed