Hi John, Snip to the only open point..
(snip) > > >(2) A reference to PCE should also be added along with the mention > of > > >ALTO server. See > > >http://datatracker.ietf.org/doc/draft-ietf-pce-pcep-service-aware/ > > >In fact the steps mentioned for the ingress in section 3 are > > >applicable for a stateful PCE as well. > > [JD] Why? > I feel just the following minor change should be fine in the introduction section. OLD: The data distributed by OSPF TE Metric Extensions is meant to be used as part of the operation of the routing protocol (e.g. by replacing cost with latency or considering bandwidth as well as cost), by enhancing CSPF, or for other uses such as supplementing the data used by an Alto server [Alto]. With respect to CSPF, the data distributed by OSPF TE Metric Extensions can be used to setup, fail over, and fail back data paths using protocols such as RSVP-TE [RFC3209].[ Draft-ietf-mpls-te-express-path] describes some methods for using this information to compute Label Switched Paths (LSPs) at the LSP ingress. NEW: The data distributed by OSPF TE Metric Extensions is meant to be used as part of the operation of the routing protocol (e.g. by replacing cost with latency or considering bandwidth as well as cost), by enhancing CSPF, or for other uses such as supplementing the data used by a PCE [RFC4655] or an Alto server [Alto]. With respect to CSPF, the data distributed by OSPF TE Metric Extensions can be used to setup, fail over, and fail back data paths using protocols such as RSVP-TE [RFC3209].[ Draft-ietf-mpls-te-express-path] and [draft-ietf-pce-pcep-service-aware] describes some methods for using this information to compute Label Switched Paths (LSPs) at the LSP ingress and PCE respectively. This would let the reader know that PCE can also use this information along with the Ingress/ALTO server. (snip) Regards, Dhruv _______________________________________________ OSPF mailing list [email protected] https://www.ietf.org/mailman/listinfo/ospf
