Comments on draft-bookham-rtgwg-nfix-arch-01

Lizhenbin <lizhenbin@huawei.com> Mon, 27 July 2020 15:13 UTC

Return-Path: <lizhenbin@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 C8D5C3A0F1C for <rtgwg@ietfa.amsl.com>; Mon, 27 Jul 2020 08:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 7oel-a8jHBqo for <rtgwg@ietfa.amsl.com>; Mon, 27 Jul 2020 08:13:23 -0700 (PDT)
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 4ECD43A0F0C for <rtgwg@ietf.org>; Mon, 27 Jul 2020 08:13:23 -0700 (PDT)
Received: from lhreml715-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id BE320767EE3AA7E8FE4E; Mon, 27 Jul 2020 16:13:21 +0100 (IST)
Received: from lhreml715-chm.china.huawei.com (10.201.108.66) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 27 Jul 2020 16:13:21 +0100
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Mon, 27 Jul 2020 16:13:21 +0100
Received: from DGGEMM512-MBS.china.huawei.com ([169.254.4.82]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0487.000; Mon, 27 Jul 2020 23:13:17 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Wim Henderickx <wim.henderickx@nokia.com>
CC: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Comments on draft-bookham-rtgwg-nfix-arch-01
Thread-Topic: Comments on draft-bookham-rtgwg-nfix-arch-01
Thread-Index: AQHWZCf5ZcQokk6YPU+pHvUNBby6eQ==
Date: Mon, 27 Jul 2020 15:13:17 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D937F3C2D@dggemm512-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.171.19]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D937F3C2Ddggemm512mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/3GEIWxFfCiy7FyKhGx7YGjd3Ppc>
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: Mon, 27 Jul 2020 15:13:25 -0000

Hi Wim,

I have the following comments for draft-bookham-rtgwg-nfix-arch-01:

1. Dose VNFs support SR-MPLS? Is it just involved as the VAS using for SFC? Can you provide some clarification?



2. If the controller is introduced to set up the SR paths, scalability may be challenging since there may be more network devices in one network domain. Is there some way to cope with the issue?





Best Regards,

Zhenbin (Robin)