The MPLS WG Archive

[Peter Willis <pjw@ip-engineering.bt.com>]

If we don't document OAM issues with MPLS in the OAM framework document where 
do they get documented? 

I think the precedent for discussing Issues with MPLS in MPLS WG framework
 documents is established in RFC3353.

Regards the "*practical*" point I can see why the MPLS WG has problems with 
the top down nature of draft-allan-mpls-oam-frmwk-05.txt. Perhaps the usual 
modus operandi of documenting implementations and waiting for customers to
request features to fix operational problems works much better?

Peter.

> 
> Hi Dave,
> 
> >
> > BTW, would be nice to get some other opinions, IMHO this is rather
> > fundamental....
> >
> 
> To reiterate what has already been said on this thread. A MPLS OAM
> framework document must a) Follow the MPLS architecture and b) Discuss
> an OAM framework that concerns *practical* problems seen in MPLS deployments.
> 
> If folks have issues with MPLS architecture/usage, it should be documented
> elsewhere, not in the OAM framework document.
> 
> Regards,
> rahul
> 
> 
> > cheers
> > Dave
> >
> >
>