Re: [trill] WG Last Call - draft-ietf-trill-oam-fm

"Xialiang (Frank)" <frank.xialiang@huawei.com> Thu, 13 March 2014 07:19 UTC

Return-Path: <frank.xialiang@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3BD61A0155 for <trill@ietfa.amsl.com>; Thu, 13 Mar 2014 00:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qvT0DCwTvqg for <trill@ietfa.amsl.com>; Thu, 13 Mar 2014 00:19:50 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E23001A035C for <trill@ietf.org>; Thu, 13 Mar 2014 00:19:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEN20357; Thu, 13 Mar 2014 07:19:41 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 13 Mar 2014 07:18:50 +0000
Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 13 Mar 2014 07:19:40 +0000
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.203]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0158.001; Thu, 13 Mar 2014 15:19:37 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Thread-Topic: [trill] WG Last Call - draft-ietf-trill-oam-fm
Thread-Index: AQHPOjNr1ILWnQFjrUWrg8zEpIRha5repI+g
Date: Thu, 13 Mar 2014 07:19:37 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F10F3DF424@SZXEMA502-MBS.china.huawei.com>
References: <CAF4+nEEa58e=Q8w3znDaEvP0CSqHZEKp7--b+3TH=LSPE4zaQw@mail.gmail.com>
In-Reply-To: <CAF4+nEEa58e=Q8w3znDaEvP0CSqHZEKp7--b+3TH=LSPE4zaQw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.42.220]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/trill/1a8apLwXNKvkcazDo6livTFK0Wg
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] WG Last Call - draft-ietf-trill-oam-fm
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Mar 2014 07:19:52 -0000

Hi draft authors,
After reviewing this draft, I think it's a very important framework draft and organized well. I support it with several comments below:
1. Several typos:
1) header format of section 8, section 9.2 are not correct. Similar problem also exists other place in the draft;
2) Suggest to change the order between section 8 and section 9;
3) TRILL OAM Specific TLVs names in section 8.4.2 are not consistent with the following draft;
4) In section 9.2.1, "The TRILL OAM Version TLV" should be "The TRILL OAM Application Identifier TLV"?

2. In section 1, is reference to [TRLOAMFRM] ok because it's not a WG draft or RFC?

3. In section 12:
1) what's is the main goal of it? Detecting flow fault or path fault of multi-path (e.g. ECMP)? 
2) What's the reason MEP transmits 4 CCM messages per each flow?
3) The numbered CCM messages possibly arrive remote MEP out of order because the multi-path characteristics of TRILL;
4) Even if CCM messages can arrive remote MEP in order, the fault detecting scheme seems to be not correct totally and will give fault judgement. For example, when  MEP-B does not receive CCM messages of 3,4,5,6.

B.R.
Frank

> -----Original Message-----
> From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Donald Eastlake
> Sent: Saturday, March 08, 2014 2:31 AM
> To: trill@ietf.org
> Subject: [trill] WG Last Call - draft-ietf-trill-oam-fm
> 
> Hi,
> 
> As announced at the TRILL WG meeting today, this starts a WG Last Call on
> draft-ietf-trill-oam-fm-02.txt running through March 24th.
> 
> Thanks,
> Donald and Jon
> 
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill