[RTG-DIR] RtgDir review: draft-ietf-idr-bgp-identifier-13.txt
Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp> Fri, 22 April 2011 05:22 UTC
Return-Path: <takeda.tomonori@lab.ntt.co.jp>
X-Original-To: rtg-dir@ietfc.amsl.com
Delivered-To: rtg-dir@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 10BE2E07B6 for <rtg-dir@ietfc.amsl.com>; Thu, 21 Apr 2011 22:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level:
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dpk5zqbTGj6o for <rtg-dir@ietfc.amsl.com>; Thu, 21 Apr 2011 22:22:51 -0700 (PDT)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148]) by ietfc.amsl.com (Postfix) with ESMTP id A1E6AE07CA for <rtg-dir@ietf.org>; Thu, 21 Apr 2011 22:22:50 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama500.ecl.ntt.co.jp (8.14.4/8.14.4) with ESMTP id p3M5MjY2016742; Fri, 22 Apr 2011 14:22:45 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id D81D065F1; Fri, 22 Apr 2011 14:22:44 +0900 (JST)
Received: from imail2.m.ecl.ntt.co.jp (imail2.m.ecl.ntt.co.jp [129.60.5.247]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id CFF3965EB; Fri, 22 Apr 2011 14:22:44 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.55]) by imail2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id p3M5MXEx023388; Fri, 22 Apr 2011 14:22:44 +0900
Message-ID: <4DB11061.4070809@lab.ntt.co.jp>
Date: Fri, 22 Apr 2011 14:21:37 +0900
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: rtg-ads@tools.ietf.org
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, draft-ietf-idr-bgp-identifier@tools.ietf.org
Subject: [RTG-DIR] RtgDir review: draft-ietf-idr-bgp-identifier-13.txt
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2011 05:22:52 -0000
Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see http://www.ietf.org/iesg/directorate/routing.html Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft. Document: draft-ietf-idr-bgp-identifier-13.txt Reviewer: Tomonori Takeda Review Date: 22 April 2011 IETF LC End Date: 18 April 2011 Intended Status: Standards Track Summary: I have some minor concerns about this document that I think should be resolved before publication. Comments: This document is short, clearly written and easy to understand. I have one minor comment that should be clarified. o Major Issues: No major issues found. o Minor Issues: Section 3: It says, In addition to the OPEN message, the BGP Identifier is currently also used in the following areas: ... o In the Route Reflection (in lieu of the Cluster-id) within an AS, where only the BGP Identifier of an internal neighbor may be propagated in the route reflection related attributes. I am a bit confused about "in lieu of the Cluster-id". My reading of this text is that the BGP Identifier is used in CLUSTER_ID attribute in the Route Reflection, which is not usually correct. I guess text should be (by removing "in lieu of the Cluster-id") : In addition to the OPEN message, the BGP Identifier is currently also used in the following areas: ... o In the Route Reflection within an AS, where only the BGP Identifier of an internal neighbor may be propagated in the route reflection related attributes. or something like this. o Nits: None. Thanks, Tomonori
- [RTG-DIR] RtgDir review: draft-ietf-idr-bgp-ident… Tomonori TAKEDA