|
Hi Shiomoto and I study through this draft and appreciate that you specify
many necessary MLN scenarios that LSP can be used for. Some of them can apply
to CTG (composite transport group) scenario. Here are some clarification and
questions: 1) When LSP is used for Client/Server Network: the server
network sets LSP as private link with one or more client IGP instances; When
LSP is used as routing adjacency: the network sets LSP as non-private link with
routing adjacency. Is this correct? 2) Should section 2.2 add one more categories: -LSP is used
as a component link in a link bundle? The doc. is described it but not considers
it as category. 3) A component link in a link bundle has component link identifier.
This identifier is the link ID that is advertised in LSA. Is that correct? 4) In section 3.3, it states: If the B-flag in the Actions field of the
LSP_TUNNEL_INTERFACE_ID object is set, the other fields of the object
apply to the link bundle itself. That is, the interface
identifiers (numbered or unnumbered) and the other flags in the Actions
field apply to the link bundle and not to the component link that
the LSP will form. Furthermore, the IGP Instance Identifier TLV
(if present) also applies to the link bundle and not to the component
link. It seems odd way to set actions for link bundle. Should we
first set the link bundle with the action, then add component link to the link
bundle without action? 5) LSA should not advertise LSP used as private link. Should
this be explicitly stated in section 3.4? 6) For CTG scenarios, we create a set of LSPs to form a
single composite link to client/server network. We can first create a composite
link as a private link with one or more client IGP instances with (at least one
component link); then individual component link can be added to and removed
from the composite link. Component links are also private link (different from
component link in link bundle) and have different TE properties. We can also
create composite link for routing adjacency (single IGP case). We need some extension
to cover these scenarios. Could we consider adding this into the document? Cheers, Lucy |