draft-ietf-rtgwg-ni-model-12 : Query about NI Types and Mount points

Rohit R Ranade <rohitrranade@huawei.com> Tue, 18 December 2018 10:59 UTC

Return-Path: <rohitrranade@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAFC1310FE for <rtgwg@ietfa.amsl.com>; Tue, 18 Dec 2018 02:59:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 WF5MVFM4v6MB for <rtgwg@ietfa.amsl.com>; Tue, 18 Dec 2018 02:59:53 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 79878128BCC for <rtgwg@ietf.org>; Tue, 18 Dec 2018 02:59:53 -0800 (PST)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 07E24D29BDB52 for <rtgwg@ietf.org>; Tue, 18 Dec 2018 10:59:49 +0000 (GMT)
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 18 Dec 2018 10:59:49 +0000
Received: from DGGEML530-MBS.china.huawei.com ([169.254.8.165]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0415.000; Tue, 18 Dec 2018 18:59:37 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: draft-ietf-rtgwg-ni-model-12 : Query about NI Types and Mount points
Thread-Topic: draft-ietf-rtgwg-ni-model-12 : Query about NI Types and Mount points
Thread-Index: AdSWwBSCDDhFBwwnRqOIgjRb+OIhmw==
Date: Tue, 18 Dec 2018 10:59:36 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BCB2188@dggeml530-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.150.121]
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6BCB2188dggeml530mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/Le8fxPkhx-yVgpMrCctnx38k3no>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2018 10:59:55 -0000

Hi All,

Since there is a possibility that new ni-types (both standard and private) will be added in future and they may either choose to re-use the well-known mount-points or augment new ones, how can the client map the mount-point to use for query and configuration for a given ni-type ?

Should this be hard-coded on the client-side ?
Or whether we can define a list which can provide this mapping, as this list will be available on the Server implementation ?

With Regards,
Rohit