Re: [mpls] MPLS-RT review of draft-farbryantrel-mpls-retire-ach-tlv

"Hejia (Jia)" <hejia@huawei.com> Thu, 23 May 2013 11:52 UTC

Return-Path: <hejia@huawei.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A288D21F92EB for <mpls@ietfa.amsl.com>; Thu, 23 May 2013 04:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.057
X-Spam-Level:
X-Spam-Status: No, score=-2.057 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAK9LNQi1mFj for <mpls@ietfa.amsl.com>; Thu, 23 May 2013 04:52:23 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F3BD921F9424 for <mpls@ietf.org>; Thu, 23 May 2013 04:52:09 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARQ86883; Thu, 23 May 2013 11:52:00 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 23 May 2013 12:51:47 +0100
Received: from SZXEML417-HUB.china.huawei.com (10.82.67.156) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 23 May 2013 12:51:59 +0100
Received: from SZXEML505-MBX.china.huawei.com ([169.254.1.213]) by szxeml417-hub.china.huawei.com ([10.82.67.156]) with mapi id 14.01.0323.007; Thu, 23 May 2013 19:51:56 +0800
From: "Hejia (Jia)" <hejia@huawei.com>
To: Loa Andersson <loa@pi.nu>, Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>, "draft-farbryantrel-mpls-retire-ach-tlv@tools.ietf.org" <draft-farbryantrel-mpls-retire-ach-tlv@tools.ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>
Thread-Topic: MPLS-RT review of draft-farbryantrel-mpls-retire-ach-tlv
Thread-Index: AQHOS8JMSi4lzPf5Dki5qykaXc/xG5kSvnnw
Date: Thu, 23 May 2013 11:51:56 +0000
Message-ID: <735916399E11684EAF4EB4FB376B71952C6CCBDA@SZXEML505-MBX.china.huawei.com>
References: <518A064C.7090006@pi.nu>
In-Reply-To: <518A064C.7090006@pi.nu>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.76.169]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] MPLS-RT review of draft-farbryantrel-mpls-retire-ach-tlv
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 11:52:36 -0000

Hi,

I noticed a 01 version of draft-farbryantrel-mpls-retire-ach-tlv is available. So I based my MPLS RT review on that version. I think the document is coherent, useful, technically sound and ready to be adopted as a WG draft. Just one comment:

1) In the Abstract part, it is written as

   No Associated Channel Type yet defined uses a TLV. Furthermore, it
   is believed that handling TLVs in hardware introduces significant
   problems to the fast-path, and since G-ACh messages are intended to
   be processed substantially in hardware, the use of TLVs in
   undesirable.

The whole paragraph seems talking generally about TLVs for G-ACh messages, not specifically an ACH TLV. This might not be so accurate since we have some G-ACh channel type using TLVs in its message, e.g. RFC 6428 defines a source MEP-ID TLV for the MPLS-TP CV type which also requires hardware processing. I think it might be better to simply say ACH TLV is not used and may cause additional processing which is not desirable. Or some better wording...

Thanks!


B.R.
Jia


-----邮件原件-----
发件人: Loa Andersson [mailto:loa@pi.nu] 
发送时间: 2013年5月8日 16:01
收件人: Lizhong Jin; Hejia (Jia); Gregory Mirsky; Eric Osborne (eosborne); Martin Vigoureux
抄送: draft-farbryantrel-mpls-retire-ach-tlv@tools.ietf.org; mpls-chairs@tools.ietf.org
主题: MPLS-RT review of draft-farbryantrel-mpls-retire-ach-tlv

Jia, Lizhong, Greg and Eric,

You have been selected as an MPLS Review team reviewers for
draft-farbryantrel-mpls-retire-ach-tlv-00.

Note to authors: You have been CC'd on this email so that you can know
that this review is going on. However, please do not review your own
document.

Reviews should comment on whether the document is coherent, is it
useful (ie, is it likely to be actually useful in operational
networks), and is the document technically sound?  We are interested
in knowing whether the document is ready to be considered for WG
adoption (ie, it doesn't have to be perfect at this point, but should be
a good start).

Reviews should be sent to the document authors, WG co-chairs and
WG secretary, and CC'd to the MPLS WG email list. If necessary, comments
may be sent privately to only the WG chairs.

Are you able to review this draft by Mat 24, 2013?

Thanks, Loa
(as MPLS WG chair)
-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64