IETF Logo Mail Archive

[Lsr] Question about draft-ppsenak-lsr-igp-ureach-prefix-announce

Huzhibo <huzhibo@huawei.com> Sat, 30 July 2022 00:49 UTC

Return-Path: <huzhibo@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7994BC14F727 for <lsr@ietfa.amsl.com>; Fri, 29 Jul 2022 17:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q2GvCXWXTO2t for <lsr@ietfa.amsl.com>; Fri, 29 Jul 2022 17:49:52 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AE3CC14F613 for <lsr@ietf.org>; Fri, 29 Jul 2022 17:49:52 -0700 (PDT)
Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Lvm0058Jhz67XLX for <lsr@ietf.org>; Sat, 30 Jul 2022 08:45:52 +0800 (CST)
Received: from canpemm100009.china.huawei.com (7.192.105.213) by fraeml703-chm.china.huawei.com (10.206.15.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Sat, 30 Jul 2022 02:49:48 +0200
Received: from canpemm500009.china.huawei.com (7.192.105.203) by canpemm100009.china.huawei.com (7.192.105.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Sat, 30 Jul 2022 08:49:46 +0800
Received: from canpemm500009.china.huawei.com ([7.192.105.203]) by canpemm500009.china.huawei.com ([7.192.105.203]) with mapi id 15.01.2375.024; Sat, 30 Jul 2022 08:49:46 +0800
From: Huzhibo <huzhibo@huawei.com>
To: Peter Psenak <ppsenak@cisco.com>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Question about draft-ppsenak-lsr-igp-ureach-prefix-announce
Thread-Index: AdijreEA3Q1LCCoqRDWqpmJY3HnyxgAABFMw
Date: Sat, 30 Jul 2022 00:49:46 +0000
Message-ID: <0e6a36e81cdf48feae0c7508732f4059@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.45]
Content-Type: multipart/alternative; boundary="_000_0e6a36e81cdf48feae0c7508732f4059huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/LrYtSKe7Ch_wY2l6u0_KCh7jiJw>
Subject: [Lsr] Question about draft-ppsenak-lsr-igp-ureach-prefix-announce
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2022 00:49:57 -0000

Hi Peter:
Supplement to yesterday's online questions, If a node that does not support IP Flexalgo, which has a default route, should the node process the IP Flexalgo prefix as a UPA?


Thanks

Zhibo

v2.23.0 | Report a Bug | By Email