Hi Young,
Thanks for the work.
See in-line for my comment. I met almost all of your comments in the
updated
version (04) except the following:
- on the name of GCO: I'd rather want to keep the current name --it's a
bit
too late to change now. Also "global" is definitely a good part of what
this
draft is about. I hope people would read the definition of GCO in the
glossary which makes the definition very clear.
OK. Well let's see what other reviewers think. This was not a requirement
from me, just a suggestion to smooth the review by others.
- on error 15/2 --- I think you are right. If a legacy PCE does not
understand the lingo "GCO" then it cannot properly generate an appropriate
error message back to PCC. However, we have defined a new error-value (5)
in
the current error-type (5) to handle policy error associated with GCO in
the
PCEP. The current texts read:
To indicate an error associated with policy violation, a new error
value "global concurrent optimization not allowed" should be added to
an existing error code for policy violation (Error-Type=5) as defined
in [PCEP].
Error-Type=5; Error-Value=5: if a PCE receives a global concurrent
path optimization request which is not compliant with administrative
privileges (i.e., the PCE policy does not support global concurrent
optimization), the PCE sends a PCErr message with a PCEP-ERROR Object
(Error-Type=5) and an Error-Value (Error-Value=5). The PCE stops the
processing the request. The corresponding global concurrent path
computation MUST be cancelled at the PCC.
Do you think this can be used for indicating "GCO incapable" error?
I think there are three cases...
1. I understand GCO but I don't want to do it
2. I understand GCO but you are not allowed to request it
3. I don't understand GCO
It is the third case that interests me. I think this should generate either
an "unknown OF" error, or an "unknown object" error.
I haven't officially published 04 version yet. But it is enclosed here for
JP's review.
Thanks.
Adrian
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
