Re: Working Group Last Call draft-ietf-ccamp-loose-path-reopt-

[Arthi Ayyangar <arthi@juniper.net>]

Adrian, all,

Just a few comments on this draft.

Section 2 and elsewhere: there are repeated statements & notes as to "CSPF
or any other PCE-based path computation method"
--> I don't think it is relevant to this document whether the path
computation is local or remote or done by a PCE or not. IMO, it would be
enough to just say "path computation".

Paragraph 4 in Section 3, Section 4.2, and 2nd and 3rd paragraphs in 5.3.2
----> This draft not only refers to another draft (and it is *not* a
normative reference) draft-ali-ccamp-mpls-graceful-shutdown-00.txt, but
also seems to introduce error codes and subcodes (subcode 7 & 8) which are
actually relevant to GR-SHUTDOWN draft rather than this document. IMO, if
graceful-shutdown procedures need new error codes/subcodes, they must be
introduced in the graceful-shutdown draft and not in this re-optimization
draft. Otherwise, what is the point of having the other draft if the
codes are being standardized here ?

thanks,
-arthi

So the
> This email starts a two week last call on
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-loose-path-reopt-00.txt
>
> Please send your comments to the list or to the chairs by noon GMT on 20th
> January 2005.
>
> Thanks,
> Adrian and Kireeti
>
>