draft-lang-ccamp-gmpls-recovery-e2e-signaling-01.txt

["Adrian Farrel" <afarrel@movaz.com>]

Hi,

I've been re-reading this draft.

a. Could you make a text clarifiaction around 'primary' and 'secondary'?
    The concepts you cover are useful, but there is some overlap in
    terminology since "primary" is ususally used in protection as a
    synonym for "working" as "secondary" is a synonym for "backup" or
    "protection". I think a text clarification should address my concern.

b. Can you add some explanation of why the PPRO is added and how
    it is used. (Hint: each time I read this section I ask the same
    question and have to have it patiently explained by the authors!)

    Something to cover...
    - Why is the secondary path interested in the primary paths it is
       protecting?
    - How does this knowledge enable it to share resources?
    Answer, it enables a secondary LSP to share resources WITH
    ANOTHER secondary LSP if the protected primary paths are diverse.

c. Need to explicitly state that the use of the "Associated LSP Id"
    field limits the protection schemes supported to 1:1 and 1+1.
    That is no 1:n or m:n support is covered in this draft.

Cheers,
Adrian