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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 

Hi Greg,
Please, see my other email I just sent.

Thanks,
Nabil

From: Gregory Mirsky <gregory.mirsky@xxxxxxxxxxxx>
Date: Tuesday, January 8, 2013 11:45 AM
To: Loa Andersson <loa@xxxxx>
Cc: "pwe3@xxxxxxxx" <pwe3@xxxxxxxx>, "gen-art@xxxxxxxx" <gen-art@xxxxxxxx>, "dinmohan@xxxxxxxxxxx" <dinmohan@xxxxxxxxxxx>, Sagessi <sajassi@xxxxxxxxx>, "ietf@xxxxxxxx" <ietf@xxxxxxxx>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

Dear Huub and Loa,
my brain did s/Reverese/Remote/ by itself. Indeed, 802.1ag and Y.1731 use RDI for Remote Defect Indication, and nothing in Reverse. And that how draft-ietf-pwe3-mpls-eth-oam-iwk-06 should expand RDI as well.
 
        Regards,
                Greg
 
-----Original Message-----
From: pwe3-bounces@xxxxxxxx [mailto:pwe3-bounces@xxxxxxxx] On Behalf Of Loa Andersson
Sent: Tuesday, January 08, 2013 3:02 AM
To: Greg Mirsky
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
 
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
>
>     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@xxxxxxxxxxxxxxx
>     Date: Wednesday, January 2, 2013 11:28 AM
>     To: "Black, David" <david.black@xxxxxxx
>     <mailto:dinmohan@xxxxxxxxxxx>>, "Bitar, Nabil N"
>     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@xxxxxxx <mailto:david.black@xxxxxxx>>
>     Date: Monday, August 20, 2012 8:57 PM
>     Cc: "Black, David" <david.black@xxxxxxx
>     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
>
>     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@xxxxxxx <mailto:david.black@xxxxxxx>        Mobile: +1
>     (978) 394-7754 <tel:%2B1%20%28978%29%20394-7754>
>     ----------------------------------------------------
>
>     _______________________________________________
>     pwe3 mailing list
>
>
>
>
> _______________________________________________
> pwe3 mailing list
>
 
--
 
 
Loa Andersson                         email: loa.andersson@xxxxxxxxxxxx
Sr Strategy and Standards Manager            loa@xxxxx
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13 _______________________________________________
pwe3 mailing list
 
[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]