That's what I thought for mpls inside a single provider network, but I wasn't clear in the case of ter-provider MPLS. However, I am by no means an MPLS expert, so I'll believe the feedback.
John >-----Original Message----- >From: ext Brian E Carpenter [mailto:[EMAIL PROTECTED] >Sent: 16 March, 2006 14:11 >To: Loughney John (Nokia-NRC/Helsinki) >Cc: [EMAIL PROTECTED]; [email protected] >Subject: Re: [Gen-art] review of draft-ietf-pce-architecture-04.txt > >The feedback I got was that for MPLS these issues don't really >arise in the same way they do for datagram routing protocols. > > Brian > >[EMAIL PROTECTED] wrote: >> Noticed Brian already commented: >> >> Brian Carpenter: >> >> Comment [2006-03-15]: >> I'm slightly surprised that this has only one rather casual mention >> of the word "loop". I'd have expected some discussion of loop >> avoidance. Similarly, the assumption that QoS enters into path >> computation seems very casual given the history of >QoS-based routing. >> >> I'd agree with this, loop detection and avoidence probably should be >> in their somewhere. >> I guess it would be good to check with the authors if this >is relevant. >> >> otherwise, I didn't find anything else to really object to, >so I think >> it should be no-obj, but with Brian's comment. >> >> John >> >> _______________________________________________ >> Gen-art mailing list >> [email protected] >> https://www1.ietf.org/mailman/listinfo/gen-art >> > > _______________________________________________ Gen-art mailing list [email protected] https://www1.ietf.org/mailman/listinfo/gen-art
