Here is my summary of our thoughts regarding a Path Object. 1. A Path Object consists of an ordered list of "Path Elements" that describe a tour through a topology. These elements are [initially] either a) an STP, or b) a "subpath" in the form of named Path Object. A Path Object does not carry any connection related information, just the stepping stones through the topology. 2. A Path Object is unidirectional. 2.5 At a minimum, a Path Object must contain two STPs: a beginning STP and a terminating STP. (Note for discussion: Can these be the same STP? i.e. can a path have zero hops? Is this even possible in a directed graph topology?) 3. A "Connection" object contains the set of constraints associated with a connection, including the path object, scheduled start and duration, authorization, and other technical specs (e.g. capacity, framing, BER, etc.) We asserted that a Connection is a uni-directional construct as well. 4. A "Service Instance" contains one or more Connections. This would allow for a bidirectional circuit to be established by bonding a connection with its reverse into a single service instance. This would also allow for constructs such as protection circuits. (Note: we need to discuss this further as I think a Svc Instance construct and a Connection construct may not be so different.) 5. We discussed breifly the necessity (or not) for a strict vs loose indicator bit associated with each element. This bit would indicate if this element is/must be strictly adjacent to the prior element in the topology. (I think this needs further discussion - does Issues for further discussion: What form does the name of a "named Object" take? I.e. How do we name STPs, or how do we name Connection Objects or Path Objects Instance Objects??? Any thing I missed? Jerry