Hello,
donning the implementer (as opposed to co-author) hat, I have comments
pertaining to draft-ietf-pce-pce-initiated-lsp, specifically to Section
6. In general it seems to contradict the general outline of the
extension as stated in section 3.2 paragraph 4.
The first paragraph clearly forbids the use of PCRpt D=0 for
PCE-initiated LSPs. It is not clear whether this restriction applies to
all PCRpts, or only the PCRpt solicited by the PCInitiate message.
Section 3.2 paragraph 4 seems to indicate this applies to solicited
PCRpts only, which is what makes sense. A clarification is definitely
needed.
The third paragraph seems to be replacing the normal delegation
mechanics with a PCInitiate-driven exchange. It does not specify whether
it is legal for a PCE to send PCUpd(D=1) after a session flap or not. It
feels like it is not legal and PCInitiate is intended to fully replace
it, but that would contradict section 3.2 paragraph 4. This needs to be
clarified.
My preference would be to remove pretty much all of this paragraph,
bringing the mechanics to what section 3.2 outlines. Unfortunately there
are already some implementations deployed, so we need to factor in the
compatiblity with the installed base. Can we perhaps allocate another
bit in the Stateful PCE Capability TLV and mark the current one as
reserved/deprecated?
Thanks,
Robert
On 12/01/2014 06:18 PM, [email protected] wrote:
Dear all,
As planned, this message ignites a 3-week WG Last Call on both
draft-ietf-pce-pce-initiated-lsp-02 and
draft-ietf-pce-stateful-sync-optimizations-01. It will end on Monday
December 22 at 11:59 PM, HST.
Please send your comments to the PCE mailing list.
Thanks,
JP & Julien
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les
messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere,
deforme ou falsifie. Merci.
This message and its attachments may contain confidential or
privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have
been modified, changed or falsified.
Thank you.
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
