The separation-approach can represent multiple paths by allowing a path-cost
to be an array of arrays of ANEs. Eg, to indicate that PID1 -> PID2 can use
either ane1a & ane1b, or else ane2a & ane2b, we could use:
{"PID1": {"PID2": [["ane1a", "ane1b"], ["ane2a", "ane2b"]]}
- Wendy Roome
From: "Scharf, Michael (Michael)" <[email protected]>
Date: Thu, February 26, 2015 at 05:14
To: "Y. Richard Yang" <[email protected]>
Cc: Wendy Roome <[email protected]>, "[email protected]"
<[email protected]>
Subject: RE: [alto] ALTO topology design: separation design
Richard,
I¹d like to understand a simpler question first; I don¹t recall whether we
have already discussed this basic scenario so far: Assume we have PID1 and
PID2 and the ALTO server operator wants to announce that there are two
entirely disjoint paths between those PIDs. The path vector would probably
just include ANE1 and ANE2 as alternatives. Is there a way to encode this
simple scenario in path vector without using the ³general flow² model?
If we go for general flow, could we make the weight parameter optional?
Michael
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
