IETF Logo Mail Archive

[Sidrops] Re: WG Adoption call for draft-sriram-sidrops-spl-verification - ENDS 06/03/2024 (June 3 2024)

junzhang <junzhang1@huawei.com> Thu, 30 May 2024 13:43 UTC

Return-Path: <junzhang1@huawei.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A40BC151073 for <sidrops@ietfa.amsl.com>; Thu, 30 May 2024 06:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.893
X-Spam-Level:
X-Spam-Status: No, score=-6.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 8Wbkr3LDCjvE for <sidrops@ietfa.amsl.com>; Thu, 30 May 2024 06:43:39 -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 B7980C14F68F for <sidrops@ietf.org>; Thu, 30 May 2024 06:43:38 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VqnRT5PMBz67KPR for <sidrops@ietf.org>; Thu, 30 May 2024 21:39:33 +0800 (CST)
Received: from lhrpeml500004.china.huawei.com (unknown [7.191.163.9]) by mail.maildlp.com (Postfix) with ESMTPS id BB035140B3C for <sidrops@ietf.org>; Thu, 30 May 2024 21:43:35 +0800 (CST)
Received: from lhrpeml500005.china.huawei.com (7.191.163.240) by lhrpeml500004.china.huawei.com (7.191.163.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 30 May 2024 14:43:35 +0100
Received: from lhrpeml500005.china.huawei.com ([7.191.163.240]) by lhrpeml500005.china.huawei.com ([7.191.163.240]) with mapi id 15.01.2507.039; Thu, 30 May 2024 14:43:35 +0100
From: junzhang <junzhang1@huawei.com>
To: "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: WG Adoption call for draft-sriram-sidrops-spl-verification - ENDS 06/03/2024 (June 3 2024)
Thread-Index: AQHaqm7YngWOUGzeEUmaVQKZf+T99bGv1aUw
Date: Thu, 30 May 2024 13:43:35 +0000
Message-ID: <e8ee0a0f38a44a7985ec8133672f75de@huawei.com>
References: <D20B81DD-3BAB-41F2-A1B5-5EE9553820E7@arrcus.com>
In-Reply-To: <D20B81DD-3BAB-41F2-A1B5-5EE9553820E7@arrcus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.52.119]
Content-Type: multipart/alternative; boundary="_000_e8ee0a0f38a44a7985ec8133672f75dehuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: INQ72UUUMRI4HZVOVDHD7BPMPL547MVM
X-Message-ID-Hash: INQ72UUUMRI4HZVOVDHD7BPMPL547MVM
X-MailFrom: junzhang1@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Sidrops] Re: WG Adoption call for draft-sriram-sidrops-spl-verification - ENDS 06/03/2024 (June 3 2024)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/vsetMHwJnti-hY0Noe3IGDdn-QQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Dear Sriram,
In Table 1 of the draft,  the “valid” state and the “NotFound” state for both ROA-ROV-state and SPL-ROV-state are equivalent, that is, as long as any of the two states is invalid, the route selection is ineligible. So is it necessary to distinguish “valid” with “NotFound”, or we can just use two states, “Invalid” and “NotInvalid”?

Yours,
  Jun Zhang

From: Keyur Patel <keyur@arrcus.com>
Sent: Monday, May 20, 2024 6:33 AM
To: sidrops@ietf.org
Subject: [Sidrops] Re: WG Adoption call for draft-sriram-sidrops-spl-verification - ENDS 06/03/2024 (June 3 2024)

Apologies. The call will end on June 3rd, 2024.

Best Regards,
Chris, Russ & Keyur

From: Keyur Patel <keyur@arrcus.com<mailto:keyur@arrcus.com>>
Date: Sunday, May 19, 2024 at 9:30 PM
To: "sidrops@ietf.org<mailto:sidrops@ietf.org>" <sidrops@ietf.org<mailto:sidrops@ietf.org>>
Subject: WG Adoption call for draft-sriram-sidrops-spl-verification - ENDS 05/03/2024 (May 3 2024)

Hi Folks,

The authors have requested SIDROPS working group adoption call of  “Signed Prefix List (SPL) Based Route Origin Verification and Operational Considerations” https://datatracker.ietf.org/doc/html/draft-sriram-sidrops-spl-verification-00.

Please send your comments to the list. The adoption call will end on May 3rd, 2024.

Best Regards,
Chris, Russ & Keyur

v2.29.0 | Report a Bug | By Email | System Status