[Nsi-wg] STPs in NSI v2.0
Henrik Thostrup Jensen
htj at nordu.net
Wed Jul 11 05:09:34 EDT 2012
On Tue, 10 Jul 2012, Freek Dijkstra wrote:
> Attached are a couple of examples with what I think is slightly better
> syntax.
Thanks for providing these. They clear up a lot on how the whole thing is
supposed to go together with topology in general.
> In my opinion it eliminates some of the quirkiness of the current
> unidirectional/bidirectional constructs. Basically every endpoint is an
> STP, which can have a source, a sink or both. The result is that you can
> easily define bidirectional path requests, unidirectional path requests,
> multipoint-to-multipoint path requests, and point-to-multipoint path
> requests.
I think I like this. It took a bit of time for the sink concept to sink in
(pun very much intended). The switch suggestion (I forgot who came up with
it, sorry) also has its merits, but it is tricky for me to see full
implications of each.
Setting up the multipoint link will be interesting, but rejecting them is
always an option.
> I heard some critique about the query part in URNs. Hence, I put the
> VLAN specification in a XML subelement, and gave some example where it
> is included or not.
I'm not really sure either. In some aspect VLAN is part of the data we
move around so it shouldn't really be touched, however they are so used
that it is something we have to support with the quirks that come with it.
What I like most about the suggestion is that it is now fairly concrete,
well-specified and integrated into NSI. Something we haven't really had
before.
Best regards, Henrik
Henrik Thostrup Jensen <htj at nordu.net>
Software Developer, NORDUnet
More information about the nsi-wg
mailing list