Re: [mpls] R: RE: Last Call: (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile) to Proposed Standard

2011-07-15 Thread Kevin P. Fleming
On 07/13/2011 09:57 PM, Greg Mirsky wrote: Dear Erminio, I'd point that the scope of G.8113.1, a.k.a G.tpoam in regard to CCM is even more narrow then of the document being discussed. The G.8113.1 addresses only bi-directional co-routed LSP and has no model to handle bi-directional associated LSP

Re: [mpls] R: RE: Last Call: (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile) to Proposed Standard

2011-07-14 Thread Greg Mirsky
ications, allows each > >>pear to identify Tx problems. > >>This OAM simplicity is the key for reliable fail finger pointing, > performance reports and protection. Also to allow scaling, more > implementation > opportunities/manufacturers, which is valuable for > >

RE: [mpls] R: Re: Last Call: (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile) to Proposed Standard

2011-07-07 Thread David Allan I
Hi Erminio: >Several service providers regarded this draft as not meeting their >transport networks' needs. E> This is a true statement: the solution in this draft is useless for many MPLS- TP deployments. The two statements do not necessarily follow. What we established during discuss

RE: [mpls] R: Re: Last Call: (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile) to Proposed Standard

2011-07-07 Thread David Allan I
Hi Erminio: Two of the three document editors were present at SG15 plenary in February where the comments originated. The revised meeting schedule resulted in a day spent going through the document with the editors. IMO there were lots of discussion and legitimate issues with the document ident