Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

"Bitar, Nabil N" <nabil.n.bitar@verizon.com> Mon, 14 January 2013 16:06 UTC

Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F2721F87C8; Mon, 14 Jan 2013 08:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level:
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MorTbH8CPV7Z; Mon, 14 Jan 2013 08:06:54 -0800 (PST)
Received: from fldsmtpe03.verizon.com (fldsmtpe03.verizon.com [140.108.26.142]) by ietfa.amsl.com (Postfix) with ESMTP id C085821F87BA; Mon, 14 Jan 2013 08:06:51 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by fldsmtpe03.verizon.com with ESMTP; 14 Jan 2013 16:06:51 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208";a="400863067"
Received: from fldp1lumxc7hb03.verizon.com (HELO FLDP1LUMXC7HB03.us.one.verizon.com) ([166.68.75.86]) by fldsmtpi01.verizon.com with ESMTP; 14 Jan 2013 16:06:51 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB03.us.one.verizon.com ([166.68.75.86]) with mapi; Mon, 14 Jan 2013 11:06:50 -0500
To: "huubatwork@gmail.com" <huubatwork@gmail.com>, Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 14 Jan 2013 11:06:36 -0500
Thread-Topic: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3ycSlEEGtuEo7BSHS7loLqQ9sTwQ==
Message-ID: <CD198238.75766%nabil.n.bitar@verizon.com>
In-Reply-To: <50EBF245.1020602@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 16:06:54 -0000

Hi,
In agreement with below definitions in 802.1ag and Y.1731  and their
mappings.Will align the terminology definition in the draft with that of
802.1ag. Y.1731 has the terminology mapping to 802.1ag's as well.

Thanks,
Nabil


On 1/8/13 5:17 AM, "Huub van Helvoort" <huubatwork@gmail.com> wrote:

>Dear Greg,
>
>You responded:
>
> > IEEE 802.1ag interprets MEP and MIP as:
> >
> >   * Maintenance association End Point
> >   * Maintenance domain Intermediate Point
>
>Indeed, and MA == MEG, MD == ME.
>
> > Y.1731 interprets them as:
> >
> >   * Maintenance entity group (MEG) End Point
> >   * MEG Intermediate Point
>
>Correct.
>
> > 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.
>
>I agree that this is the best.
>These are the abbreviations used for MPLS-TP too.
>
>Best regards, Huub.
>
>
> > On Fri, Jan 4, 2013 at 8:30 AM, Huub van Helvoort <huubatwork@gmail.com
> > <mailto:huubatwork@gmail.com>> 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.