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

Loa Andersson <loa@pi.nu> Tue, 08 January 2013 11:01 UTC

Return-Path: <loa@pi.nu>
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 7278121F8E3C; Tue, 8 Jan 2013 03:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level:
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 vVp-ecWg1HSk; Tue, 8 Jan 2013 03:01:54 -0800 (PST)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 6918121F8E1C; Tue, 8 Jan 2013 03:01:54 -0800 (PST)
Received: from [192.168.1.103] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 768027FE07; Tue, 8 Jan 2013 12:01:51 +0100 (CET)
Message-ID: <50EBFCA0.3060307@pi.nu>
Date: Tue, 08 Jan 2013 12:01:52 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com> <CD0C3AE6.6E673%nabil.n.bitar@verizon.com> <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
In-Reply-To: <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Tue, 08 Jan 2013 11:01:55 -0000

Greg,

RFC 6428 expands RDI as:

    RDI: Remote Defect Indication

/Loa

On 2013-01-07 21:51, Greg Mirsky wrote:
> Dear Nabil,
> can we avoid different interpretation of the same abbreviation (RDI):
>
>     RDI   Remote Defect Indication for Continuity Check Message
>
>     RDI   Reverse Defect Indication
>
> AFAIK, the latter form is the interpretation used by both IEEE 802.1ag
> and Y.1731. How useful is the first form?
>
> Regards,
>
> Greg
>
>
>
> On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N
> <nabil.n.bitar@verizon.com <mailto:nabil.n.bitar@verizon.com>> wrote:
>
>     Hi Dave,
>     Related to abbreviations comment below and to be clearer, I renamed
>     the original terminology section to "Abbreviations and Terminology".
>     I also created a subsection called "Abbreviations" ,and
>     "Terminology" became the second subsection.  Here iis how the edits look
>
>
>       3. Abbreviations and Terminology____
>
>
>         3.1. Abbreviations____
>
>     AISAlarm Indication Signal____
>
>     ACAttachment Circuit____
>
>     BFDBidirectional Forwarding Detection____
>
>     CCContinuity Check____
>
>     CCMContinuity Check Message____
>
>     CECustomer Equipment____
>
>     CVConnectivity Verification____
>
>     E-LMI Ethernet Local Management Interface____
>
>     EVCEthernet Virtual Circuit____
>
>     LDPLabel Distribution Protocol____
>
>     LoSLoss of Signal____
>
>     MAMaintenance Association____
>
>     MDMaintenance Domain____
>
>     MEMaintenance Entity____
>
>     MEGMaintenance Entity Group____
>
>     MEPMaintenance End Point____
>
>     MIPMaintenance End Point____
>
>     MPLSMultiprotocol Label Switching____
>
>     MS-PW Multi-Segment Pseudowire____
>
>     NSNative Service____
>
>     OAMOperations, Administration, and Maintenance____
>
>     PEProvider Edge____
>
>     PSNPacket Switched Network____
>
>     PWPseudowire____
>
>     RDIRemote Defect Indication for Continuity Check Message____
>
>         RDI   Reverse Defect Indication
>
>     S-PESwitching Provider Edge____
>
>     TLVType Length Value____
>
>     T-PETerminating Provider Edge____
>
>     __ __
>
>
>         3.2. Terminology____
>
>     This document uses the following terms with corresponding
>     definitions: ____
>
>     - MD Level:Maintenance Domain (MD) Level which identifies a value in
>     the range of 0-7 associated with Ethernet OAM frame. MD Level
>     identifies the span of the Ethernet OAM frame.____
>
>     - MEP:Maintenance End Point is responsible for origination and
>     termination of OAM frames for a given MEG.____
>
>     - MIP: Maintenance Intermediate Point is located between peer MEPs
>     and can process OAM frames but does not initiate or terminate them.____
>
>     Further, this document also uses the terminology and conventions
>     used in [RFC6310].____
>
>
>
>     Thanks,
>
>     Nabil
>
>
>     From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>
>     Date: Wednesday, January 2, 2013 11:28 AM
>     To: "Black, David" <david.black@emc.com
>     <mailto:david.black@emc.com>>, "dinmohan@hotmail.com
>     <mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.com
>     <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N"
>     <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org <mailto:gen-art@ietf.org>>
>     Cc: "pwe3@ietf.org <mailto:pwe3@ietf.org>" <pwe3@ietf.org
>     <mailto:pwe3@ietf.org>>, "ietf@ietf.org <mailto:ietf@ietf.org>"
>     <ietf@ietf.org <mailto:ietf@ietf.org>>
>     Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     Hi Dave,
>     Sorry for a late reply addressing your comments. Please, see inline.
>
>     Thanks,
>     Nabil
>
>     From: "Black, David" <david.black@emc.com <mailto:david.black@emc.com>>
>     Date: Monday, August 20, 2012 8:57 PM
>     To: "dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>"
>     <dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil
>     N" <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org <mailto:gen-art@ietf.org>>
>     Cc: "Black, David" <david.black@emc.com
>     <mailto:david.black@emc.com>>, "pwe3@ietf.org
>     <mailto:pwe3@ietf.org>" <pwe3@ietf.org <mailto:pwe3@ietf.org>>,
>     "ietf@ietf.org <mailto:ietf@ietf.org>" <ietf@ietf.org
>     <mailto:ietf@ietf.org>>
>     Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     I am the assigned Gen-ART reviewer for this draft. For background on
>     Gen-ART, please
>     see the FAQ at
>     <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>     Please resolve these comments along with any other Last Call
>     comments you may receive.
>
>     Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
>     Reviewer: David L. Black
>     Review Date: August 20, 2012
>     IETF LC End Date: August 20, 2012
>
>     Summary:
>     This draft is basically ready for publication, but has nits that
>     should be fixed before publication.
>
>     <NB> Thanks.
>
>     This draft covers defect behavior for Ethernet pseudowires,
>
>     including defect state mapping and PE defect reporting behavior.
>
>     The draft is generally in good shape.  I found a few minor nits.
>
>     1) The draft uses a lot of acronyms - while each acronym appears to
>
>     be expanded on first use, an additional section near the start of the
>
>     draft listing all of them would be helpful.
>
>
>     <NB> Done.
>
>     2) There's a typo in the first paragraph of section 2:
>
>           covers the following Ethernet OAM (Opertaions, Administration and
>
>     Opertaions -> Operations.
>
>
>     <NB> Thanks. Done.
>
>     3) The following normative reference is incomplete - please add
>     additional
>
>     information that will enable a reader to locate the referenced document:
>
>           [MEF16] "Ethernet Local Management Interface", MEF16, January
>     2006.
>
>
>     [MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum
>     Technical Specification MEF16, January 2006.
>
>     <NB> changed it to :
>
>     4) idnits2.12.13 did not like the pagination:
>
>        == The page length should not exceed 58 lines per page, but there
>     was 22
>           longer pages, the longest (page 1) being 61 lines
>
>     <NB> That will be fixed.
>     Thanks,
>     --David
>     ----------------------------------------------------
>     David L. Black, Distinguished Engineer
>     EMC Corporation, 176 South St., Hopkinton, MA  01748
>     +1 (508) 293-7953 <tel:%2B1%20%28508%29%20293-7953>             FAX:
>     +1 (508) 293-7786 <tel:%2B1%20%28508%29%20293-7786>
>     david.black@emc.com <mailto:david.black@emc.com>        Mobile: +1
>     (978) 394-7754 <tel:%2B1%20%28978%29%20394-7754>
>     ----------------------------------------------------
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pwe3
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13