Dear Huub, Nabil, et al., IEEE 802.1ag interprets MEP and MIP as: - Maintenance association End Point - Maintenance domain Intermediate Point
Y.1731 interprets them as: - Maintenance entity group (MEG) End Point - MEG Intermediate Point The reference to MD Level implies reference to IEEE 802.1ag, at least as use of terminology, since Y.1731 doesn't have Maintenance Domain construct and refers to the same value as MEG Level. I'd suggest to follow one model, IEEE 802.1ag or Y.1731, terminology throughout the document so that there's no need for re-mapping. I think that it is easier to follow Y.1731. Regards, Greg On Fri, Jan 4, 2013 at 8:30 AM, Huub van Helvoort <[email protected]>wrote: > All, > > Some nits that need to be fixed: > > > > ME Maintenance Entity >> >> MEG Maintenance Entity Group >> >> MEP Maintenance End Point >> > > MEP "ME End Point" or "Maintenance Entity End Point" > >> >> MIP Maintenance End Point >> > > MIP "ME Intermediate Point" or "Maintenance Entity Intermediate Point" > > > > 3.2. Terminology >> > > - MEP: Maintenance End Point is responsible for origination and >> termination of OAM frames for a given MEG. >> > > - MEP: Maintenance Entity End Point is responsible for origination > > > - MIP: Maintenance Intermediate Point is located between peer MEPs and >> can process OAM frames but does not initiate or terminate them. >> > > - MIP: Maintenance Entity Intermediate Point is located between > > > Regards, Huub. > ______________________________**_________________ > pwe3 mailing list > [email protected] > https://www.ietf.org/mailman/**listinfo/pwe3<https://www.ietf.org/mailman/listinfo/pwe3> >
