[Idr] Mail regarding draft-ietf-idr-bgp-open-policy

Zhuangshunwan <zhuangshunwan@huawei.com> Wed, 31 July 2019 02:50 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E57CB12008A for <idr@ietfa.amsl.com>; Tue, 30 Jul 2019 19:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ceje9q19sL9I for <idr@ietfa.amsl.com>; Tue, 30 Jul 2019 19:50:09 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF45E12004E for <idr@ietf.org>; Tue, 30 Jul 2019 19:50:08 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 2AA5DC13F76B7A012B41 for <idr@ietf.org>; Wed, 31 Jul 2019 03:50:07 +0100 (IST)
Received: from NKGEML412-HUB.china.huawei.com ( by lhreml704-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 31 Jul 2019 03:50:06 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([]) with mapi id 14.03.0439.000; Wed, 31 Jul 2019 10:50:02 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Mail regarding draft-ietf-idr-bgp-open-policy
Thread-Index: AdVHR1EkgZPrSTpORC6WGZSBPLIlfg==
Date: Wed, 31 Jul 2019 02:50:01 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858E5C64D30@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858E5C64D30NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/bTlplIPcRrTDkY-OG9HlxOv2_Ho>
Subject: [Idr] Mail regarding draft-ietf-idr-bgp-open-policy
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 02:50:11 -0000

Hi guys,

Section 9 of draft-ietf-idr-bgp-open-policy-06 says:
   This document defines a new optional, transitive BGP Path Attributes
   option, named "Only To Customer", assigned value <TBD3> [To be
   removed upon publication: http://www.iana.org/assignments/bgp-
   parameters/bgp-parameters.xhtml#bgp-parameters-2] [RFC4271].  The
   length of this attribute is 0.

[Comment]  The length of this attribute should be 4 per the description of section 6.
Type 35 with the name "Internal Only To Customer" has been assigned to previous version of draft-ietf-idr-bgp-open-policy. Can we simply use Type 35 for "Only To Customer" attribute, or apply a new one?