Hi, My opinion is that we're talking about slightly different things. Path in the sense Freek defines it seems to represent a "finalized" object while the way John describes it is closer to an "unfinished" object that we would find in a service request. I think both approaches have value, and are in fact very close but maybe we would like to to differentiate between them? On Jul 1, 2008, at 8:44 AM, John Vollbrecht wrote:
On Jul 1, 2008, at 9:09 AM, Freek Dijkstra wrote:
John Vollbrecht wrote:
Attached is a DCN glossary which is part of DCN architecture and DCN reservation documents.
Thanks John!
path - a connection between a source and destination. A path is a sequence of hops.
I would argue that a path is a sequence of edges/links rather than hops. That way I can distinguish between two links between the same hops, and can more easily between different types of relations between hops (link, cross connect, adaptation, de-adaptation)
I think of a path a a sequence of hops because a requested path may contain some but not all intermediate hops, and hops may be domains rather than links. A strict path is a sequence of links.
There may be multiple paths between hops but paths may be "potential" or requested as well as confirmed and strict.