Re: [CCAMP] WG Last Call: WSON documents - rwa-info, general-constraint-encode, rwa-wson-encode, gmpls-general-constraints-ospf-te, wson-signal-compatibility-ospf, wson-signaling

["Giovanni Martinelli (giomarti)" <[e-mail]>]

Hi Cyril,

pls see inline 

On Oct 22, 2013, at 12:53 , "Margaria, Cyril (Coriant - DE/Munich)" <[e-mail]> wrote:

> http://tools.ietf.org/html/draft-ietf-ccamp-wson-signaling-06 
> I've reviewed this document and I have the following comments:
> - section 4.3 : "If more than two objects are encountered,
>   two MUST be processed and the rest SHOULD be ignored."
> 	This is ambiguous : the section refers to the RB information sub tlv, does this refers to the WSON_signaling object or RBInformation?

GM> it refer ti RB information does this change is acceptable to you
old:
" If more than two objects are encountered,
two MUST be processed and the rest SHOULD be ignored."

new:
"If more than two RB Information objects are encountered,
two MUST be processed and the rest SHOULD be ignored."


> - section 4.3 : http://trac.tools.ietf.org/wg/ccamp/trac/ticket/52, please remove this paragraph, the restriction is strong and would not allow a node to choose one RB per local policy /sharing.. etc

GM>  Current change you propose is to remove this sentence

"RB Set Field MAY contain more than one RB Indetifier. Only the first
one MUST be processed, the others SHOULD be ignored.
"

I'm ok I'd like to know if anyone else have concern in remving. Simply we become liberal in in using the RB Identifiers in signaling. 



> - section 7 : the section assume a LSP_REQUIRED_ATTRIBUTE, but this is a targeted information as described in section 4.2, or should it be distinguished between targeted attribute (to be assigned in the ERO HOP_attribut, this depends on the space choosen by the draft-ietf-ccamp-lsp-attribute-ro) and e2e attribute (WA)?.

GM> Sounds to me this draft follow the draft-ietf-ccamp-lsp-attribute-ro as it was one of the use case. 

Cheers
G