please see inline
<cut>
3) Association control : the PCC and any PCE can create associations:
> this diverge from the existing mechanism from the statefull document.
> In my opinion this aspect makes the control and state maintenance more
> complicated. The use cases behind this multiple-controller model is not
> very clear.
>
> If the association is under the control a single entity (PCC or PCE), as
> in the stateful document, the association state then become part of the PCE
> state and the rules described in the stateful document applies (it up to
> the PCE who as delegation to set the association.
>
> This would also allow to get rid of the R bit, as mentioned by adrian (to
> remove an association: simply not send it)
>
### I disagree, the ability to have either create an association and
allocate an identifier was a key requirement (you may recall that version
00 only allowed the PCE to create such associations, and we received a lot
of feedback asking to lift this limitation).
[MC] I mixed different things here, some of them were clarified during the
discussion:
-a) Multiple-controller : I meant multiple PCE at the same time, the
authors clarified that only one PCE can set the association, the one having
the delegation.
This is implicit because only PCUpd and PCInitiate can change the
association, Additional text could make it more clear, that address the "This
diverge from the existing mechanism from the statefull document."
b) I agree that the ability to have either create an association and
allocate an identifier is a key requirement, this should be kept.
Do you mean that the R bit is required to do that? I did not find
this in the document. I have the view as Lou on it.
c) Cleanup-procedure : this is addressed by the comment "3) to change the
association source to be the same as 6780" from Lou: as the state is not
per association source/PCE and point a), then the Associations is another
PCE-create parameter, so the draft-ietf-pce-stateful-pce
<http://tools.ietf.org/wg/pce/draft-ietf-pce-stateful-pce/> and
draft-ietf-pce-pce-initiated-lsp
<http://tools.ietf.org/wg/pce/draft-ietf-pce-pce-initiated-lsp/> do apply
and are sufficient to do the cleanup.
BR,
Cyril
>
>
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
