1. NSI Topology Wishes OGF Lyon Sep 2011 Jerry Sobieski

2. NSI Topology requirements (a non-exhaustive and general set of observations…) Must support the existing NSI model Inter-domain Data plane: NSI Networks, NSI Endpoints (STPs), NSI Peerings (SDPs) Inter-domain to intra-domain mapping (abstraction?) Control plane: NSA-Network mappings, Must support path finding Two stage PF: “select path, confirm path” process. Data plane topology and transfer functions Control plane (service tree) topology (?) Must support distributed [autonomous] management of topology Each domain must be able to decide what information it is willing to announce, and Each domain must be able to decide with whom it is willing to exchange topology The processes must scale globally. Must support summarization and abstraction Multi-layer data plane path summarization – Switching (Transfer function) abstraction/generalization Must support non-congruent topology views Differnent agents have different views – all should be valid views We need a “grouping” capability within an NSI topology Groups can combine, e.g. VLAN sets on different ports – perhaps on deiffnert nodes – into a single object that has a shared constraint.

3. NSI preferences The topology description: Simple grammar – easily understood Common and easily processed syntax/format Should support virtualization of topology… Details/specifics tbd… – Clarity of terminalogy wrt physical, logical,