Hi again, Here is the second missed email. Thoughts in line. Cheers, Adrian From: [email protected] [mailto:[email protected]] On Behalf Of Dhruv Dhody Sent: 06 February 2014 12:22 To: Farrel Adrian Cc: [email protected] Subject: Re: [Pce] I-D Action: draft-ietf-pce-questions-02.txt Hi Adrian, There are a few comments that i made during the WG adoption call. [http://www.ietf.org/mail-archive/web/pce/current/msg03168.html]. Most of them have been handled in -01 version. I have listed some that i would like your opinion on. * Sec 3. How Is Topology Information Gathered? Another issue faced when using IGP to fed TED is the area-scope issue. Since IGP-TE flooding scope is per area, an multi-area or AS-scope PCE must have an IGP peer for all the areas. I'm pretty sure I disagree or agree. You are saying that a PCE that has multi-domain visibility must be able to build its TED from multiple sources (i.e. from each domain). Isn't this obvious? But I am adding a simple note at the end of Section 3 to cover this case. Also I think we can augment this section to include 'How PCE learn about Boundary Nodes?'. Hmmmm. And sigh :-) How does a non-PCE system learn about boundary nodes? It's in the IGP and the EGP. * Sec 5. How Do I Select Between PCEs? Along with capability, you can also mention the PCE's preference for each computation scope as carried in the PATH-SCOPE subtlv. You are going to have to remind me, I'm afraid. Where is the PATH-SCOPE subtlv defined? I suppose I was considering that a PCC is only going to choose a PCE in its own domain, but I can add a note. * Sec 13. What are Sticky Resources? OLD: This can result in LSP setup failures are there is contention for resources. NEW: This can result in LSP setup failures if there is contention for resources. Ack * Sec 20. Comparison of Stateless and Stateful PCE Can you have a re look at this wrt draft-ietf-pce-pce-initiated-lsp-00 is now a WG draft. Mutter! Which document is right? What specific issue are you raising? Thanks, Adrian (who hates html email, but can't be bothered to convert this one to plain text).
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
