[Qirg] QI multiplane draft
Rod Van Meter <rdv@sfc.wide.ad.jp> Sun, 05 November 2023 10:09 UTC
Return-Path: <rdv@sfc.wide.ad.jp>
X-Original-To: qirg@ietfa.amsl.com
Delivered-To: qirg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E96DC152573 for <qirg@ietfa.amsl.com>; Sun, 5 Nov 2023 02:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.307
X-Spam-Level:
X-Spam-Status: No, score=-4.307 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sfc.wide.ad.jp
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 5v2rsiS1yfU2 for <qirg@ietfa.amsl.com>; Sun, 5 Nov 2023 02:09:08 -0800 (PST)
Received: from mail1.sfc.wide.ad.jp (mail1.sfc.wide.ad.jp [203.178.142.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6FA2C258104 for <qirg@irtf.org>; Sun, 5 Nov 2023 02:09:06 -0800 (PST)
Received: from [IPV6:2001:67c:370:128:3c10:c142:1ea3:7707] (unknown [IPv6:2001:67c:370:128:3c10:c142:1ea3:7707]) (Authenticated sender: rdv) by mail1.sfc.wide.ad.jp (Postfix) with ESMTPSA id 5AA494607F; Sun, 5 Nov 2023 19:09:01 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sfc.wide.ad.jp; s=mail1; t=1699178943; bh=ifNoXPlNVfcVnr6ofRql1Q4rTheVmMNymZ8+QrYFmk8=; h=Date:To:From:Subject:From; b=WzUpo5RQF+zCK0IJoImaQeoHT1btzZfsFZozhTSdW1eFc9BO+wL1VVoxYJ4VwcGha YqOyH++PDwK1K15gYctmmVzWHuirNn1yIYiWZQfVjvULuZK2bXCRXZyUiGuBZCXIiS OKT/cGFHkvX3vkzCFql2xpyAU6+yvRUIzhmIL9kHWJzyDuAVgH6mWWT1MRVg4hf9j7 mTT0n58fjPN7yDVDhylL4UWHa1IyctIZqGx6HCN8VieCvR73Nm7H5I4zlFE6lt20vo 6pXEdn3tmQlnWb2cQ16czYym5Qh/z7JGzxW8t+ey5R/5chKU/B6OGAXsY604p7BQzg tM9W2hdvvVdmw==
Message-ID: <6570f8b4-b04c-4986-9470-b62e07eca78a@sfc.wide.ad.jp>
Date: Sun, 05 Nov 2023 19:08:59 +0900
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "qirg@irtf.org" <qirg@irtf.org>, diego.r.lopez@telefonica.com
Content-Language: en-US
From: Rod Van Meter <rdv@sfc.wide.ad.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/k-ceak6qkD6JSQ0Jn-NFZuy6AqA>
Subject: [Qirg] QI multiplane draft
X-BeenThere: qirg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Quantum Internet RG <qirg.irtf.org>
List-Unsubscribe: <https://mailman.irtf.org/mailman/options/qirg>, <mailto:qirg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/qirg/>
List-Post: <mailto:qirg@irtf.org>
List-Help: <mailto:qirg-request@irtf.org?subject=help>
List-Subscribe: <https://mailman.irtf.org/mailman/listinfo/qirg>, <mailto:qirg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2023 10:09:12 -0000
https://datatracker.ietf.org/doc/draft-lopez-qirg-qi-multiplane-arch/ Hi Diego et al., I have a series of questions about this I-D. First off, of course, thanks for taking the time to write and submit it! The multiplane management and operation of the network is definitely a necessary approach. Let's see... 1. I know it's heavily informed by your QKD work, but can you say a little (here on the list, no need put it in the document yet) on your view of the relevance of this document to more general-purpose, entangled quantum networks? 2. Likewise, what about the relationship with <whisper> ITU </whisper>? You have cited (and probably worked on) a number of those QKD-specific documents; how do you see the IETF role v. the ITU role? 3. My _impression_ of the ITU work is that it is strongest at the physical layer and above the application layer, at the key management functionality. This leaves a big gap in the middle layers -- L3-4 ish, give or take. Does that match your experience? 4. "Quantum forwarding plane" is probably the wrong name. For entangled networks, there really is no forwarding; the service provided by the network is creation of E2E entanglement to be consumed by applications. That is very much a distributed process, nothing at all like the Internet's store-and-forward of packets. (Actually, I would expect this aspect to be true for multihop, trusted intermediate node QKD, as well.) 5. Going back to point 1, how will this architecture support the stages of evolution of a Quantum Internet as outlined by Wehner, Hanson, Elkouss (Science)?
- [Qirg] QI multiplane draft Rod Van Meter