IETF Logo Mail Archive

Re: [GROW] draft-ietf-grow-bmp-local-rib terminology edits

Paolo Lucente <paolo@ntt.net> Sat, 20 July 2019 12:29 UTC

Return-Path: <paolo@us.ntt.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD176120A9C for <grow@ietfa.amsl.com>; Sat, 20 Jul 2019 05:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level:
X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gino365.onmicrosoft.com
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 mXFS4bz22kKY for <grow@ietfa.amsl.com>; Sat, 20 Jul 2019 05:29:54 -0700 (PDT)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700085.outbound.protection.outlook.com [40.107.70.85]) (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 76379120AA2 for <grow@ietf.org>; Sat, 20 Jul 2019 05:29:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kO0nfBeQ9TrVEuBII8fC6j9pINSLxESHoYjeM+8JPFmnG7AqntYsFI3Zp9W3TeIzS/un1g+DhXHmiZJut0lxAjp1jx/XpcqwYrYAREpleifwzeS7N1HKoFYagSjZBvg2sBf7sZcMaTuVBPThgb+A3ykwBM/xK/oSurpiap20pplXg2NBwIFcRpYSIButXjbN2rJExAqxjERTeyqzoInqH8A8X3GwrC4mBgrUXlCIKnEHs8/a34FL+5sB5PcgvPuJWQbKtyDUvWmL4Pj47vG5USPZ66oIdmWFvtduBvwNW30gzi4twzALBOf0jtPgjUU+s/jfuNN6m/WT1Nb9H+3Irw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Q7deX1BimuDOFrdDtIBounGFuXQeaQsApay1lRO8BaQ=; b=Y4BuDcpdpGIGWKcYFSVCx79g1UfWnAS5d+OrmWOf/cJLwbqWfSYe1v0di+ulUrAhG9qZOrkM0QDqt0sqMC8twLkzmJCNiD9tZk2eqKiqusV3ZuRSX50HNTAQ6j2FXbnaeozkcfV9GwMzp1TxpBdJvIlAoVV1SjswExys/PNzfrlcGVPThVjB1mT9Fgta2DViht8pHKEDD4nbUL594zuYqSzd2S8B+OzOwcs0NWmho3Z6onlVXw3VnvhVSgnsXD8gplIk/eIyarlxttczs/HWHoLZLG+lPmTcJwXho6C9PRHuucpgByRZrku4Yrx2PWt/y/ranQJinjVDIsQfarmfTg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=us.ntt.net; dmarc=pass action=none header.from=ntt.net; dkim=pass header.d=ntt.net;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gino365.onmicrosoft.com; s=selector2-gino365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Q7deX1BimuDOFrdDtIBounGFuXQeaQsApay1lRO8BaQ=; b=GDu8pM+wXAqtP+OEPFr5kvtZUg9DjT9Z5hmVPU8yjBaQZJhC46VeQ+gDyc4IAeaUp/0gxnkBQg59Q7zcsgHKFcnv3PpypO94EKPcJW3/5pPY7o/DtTrK9A9e2IKr2+eU5l8lMYugjz2zR9ylUwR0k/LHI9a5dVjDgHwIUrIws98=
Received: from BYAPR06MB5974.namprd06.prod.outlook.com (20.179.158.79) by BYAPR06MB5445.namprd06.prod.outlook.com (20.178.54.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.12; Sat, 20 Jul 2019 12:29:52 +0000
Received: from BYAPR06MB5974.namprd06.prod.outlook.com ([fe80::70a0:34bf:974a:613]) by BYAPR06MB5974.namprd06.prod.outlook.com ([fe80::70a0:34bf:974a:613%7]) with mapi id 15.20.2094.013; Sat, 20 Jul 2019 12:29:52 +0000
From: Paolo Lucente <paolo@ntt.net>
To: Zhuangshunwan <zhuangshunwan@huawei.com>
CC: Jeffrey Haas <jhaas@pfrc.org>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] draft-ietf-grow-bmp-local-rib terminology edits
Thread-Index: AQHVIWXKvfA1ejTnREayVuQAbJJArqbFhiKAgAsHH4CAADnBAIACIP+AgADC0gA=
Date: Sat, 20 Jul 2019 12:29:51 +0000
Message-ID: <A6C536AB-8057-4F45-AB84-D56CB47A102D@ntt.net>
References: <20190612212909.GA32258@pfrc.org> <0F0E18A1-E9B3-403C-9ABA-F8ED632C93AF@ntt.net> <20190718125507.GA21401@pfrc.org> <D1C1EDFD-5221-4263-B845-14D85F5329D9@ntt.net> <19AB2A007F56DB4E8257F949A2FB9858E5C19A0C@NKGEML515-MBS.china.huawei.com>
In-Reply-To: <19AB2A007F56DB4E8257F949A2FB9858E5C19A0C@NKGEML515-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: VI1PR08CA0136.eurprd08.prod.outlook.com (2603:10a6:800:d5::14) To BYAPR06MB5974.namprd06.prod.outlook.com (2603:10b6:a03:15b::15)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=paolo@us.ntt.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Apple Mail (2.3445.104.11)
x-originating-ip: [88.128.80.45]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2559f73b-5545-49fc-ed41-08d70d0df674
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(7168020)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR06MB5445;
x-ms-traffictypediagnostic: BYAPR06MB5445:
x-microsoft-antispam-prvs: <BYAPR06MB54458E0D402FFAFF31A63D2C90CA0@BYAPR06MB5445.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0104247462
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(376002)(346002)(39830400003)(136003)(189003)(199004)(51914003)(33656002)(14454004)(229853002)(6246003)(66066001)(102836004)(53936002)(64756008)(186003)(66446008)(66556008)(26005)(99286004)(50226002)(6116002)(8936002)(3846002)(52116002)(81156014)(5660300002)(25786009)(54906003)(36756003)(7736002)(68736007)(305945005)(81166006)(486006)(66476007)(57306001)(508600001)(71200400001)(71190400001)(76176011)(55236004)(6506007)(4326008)(53546011)(316002)(386003)(4744005)(11346002)(446003)(476003)(6916009)(2616005)(6436002)(6486002)(256004)(2906002)(66946007)(8676002)(6512007); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR06MB5445; H:BYAPR06MB5974.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: us.ntt.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: /9yqieEwzlcStb5ayxOOVf9EtLV4Ak81AV293AgcBkfs9zA+uAFpMy/zqBW1vePqEq7HHMJ1tcIbrlEUuEt4RhL3iDDxwr1zC+1I/8LPXZPQ/VXUlzD9kH0qHeMvVdzR+5vxTcXIJISo0uQznDhpYPW9Ic7TFM1gum6Q8dwe2OsPEKz3RmtPgvcwAvIWCcPKkmyIChjTFqyZYGNbmJsHjNTbofHiXgzXBZP2JLkv+tdMgHW005AR38jV7748g/9TuOwQIvYktUwDdjuErN+VYiXZ5RlO1oBShB77QzMLhcGCcoWCFy26ks57FolZymEoIQjWeors2vO5OsRgtVDUQLR9bcpfGvpAB2+yzKV3pPWvQnNTcM/DiGJnCmJsvkeiEphHqPl8se1Ih1EKqamjbfR7E23mL/z06IJXIfyNk5Y=
Content-Type: text/plain; charset="utf-8"
Content-ID: <072854ECFB1DEB4180034B4BB52E8FCC@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ntt.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 2559f73b-5545-49fc-ed41-08d70d0df674
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jul 2019 12:29:51.9776 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e65ee3d8-fd64-47ab-92bb-590b1c59945b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: paolo@us.ntt.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR06MB5445
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/j7QXpYyKEtnVVLHg8o_rfMIkf10>
Subject: Re: [GROW] draft-ietf-grow-bmp-local-rib terminology edits
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jul 2019 12:29:56 -0000

Hi Shunwan,

Thanks for your comments, inline:

> On 20 Jul 2019, at 02:52, Zhuangshunwan <zhuangshunwan@huawei.com> wrote:
> 
> Regarding VRF/Table Name TLV:
> Based on my understanding of RFC7854, I think the processing of VRF/Table Name TLV can be the same as Type 0 String TLV of BMP Initiation Message in RFC7854:
> The VRF/Table Name TLV MAY be included multiple times.
> If multiple strings are included, their ordering MUST be preserved when they are reported.

Thanks for the pointer.

> At the same time, this spec can also support processing multiple String Information into one composite String and then putting it into one TLV.

Totally, agree. It’s just probably not worth specifying it as part of the document.

Paolo

v2.23.0 | Report a Bug | By Email