[CCAMP] Signaling extensions for FA-LSPs (comment on draft-ietf-ccamp-gmpls-signaling-g709v3-01)

[Ben Wright <[e-mail]>]

Hi Fatai et al,

We have been thinking about function we will need to add to draft-ietf-ccamp-gmpls-signaling-g709v3-01 to fully support automatically provisioned FA-LSPs.   I wanted to see whether you agree with our analysis.

We think that the RSVP-TE signalling should be extended to carry more information in order to allow other nodes on the signalling path to set up the correct FA-LSP.    For example, in the network in http://tools.ietf.org/html/draft-ietf-ccamp-gmpls-signaling-g709v3-01#section-7, we believe that N1 should be able to prescribe to N2 the set of hops that it should use to set up the ODU2 FA-LSP, and the signal type of the FA-LSP it should set up, and (probably) the multiplexing hierarchy to be used at either end.   Typically, we'd expect N1 would want to explicitly prevent N2 from querying routing to set up the FA-LSP  - otherwise, a routing calculation triggered by N2 could compute a path for the FA-LSP inconsistent with N1's intentions (e.g. which could break some SRLG diversity requirement).

What do you think?   Is this an issue that you anticipate addressing in the text for section 7.1 (alluded to as being for future study)?

Thanks,

Ben Wright and Steve Balls