Re: [Qirg] Update to draft-irtf-qirg-principles

Wojciech Kozlowski <W.Kozlowski@tudelft.nl> Mon, 24 February 2020 13:13 UTC

Return-Path: <W.Kozlowski@tudelft.nl>
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 805E73A0AAC for <qirg@ietfa.amsl.com>; Mon, 24 Feb 2020 05:13:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Level:
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 CLUTZrv_4oEu for <qirg@ietfa.amsl.com>; Mon, 24 Feb 2020 05:13:17 -0800 (PST)
Received: from mailservice.tudelft.nl (mailservice.tudelft.nl [130.161.131.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3BD83A0AAA for <Qirg@irtf.org>; Mon, 24 Feb 2020 05:13:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by amavis (Postfix) with ESMTP id B8B5BCC0112; Mon, 24 Feb 2020 14:13:14 +0100 (CET)
X-Virus-Scanned: amavisd-new at tudelft.nl
Received: from mailservice.tudelft.nl ([130.161.131.74]) by localhost (tudelft.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id unvRDNqSHzob; Mon, 24 Feb 2020 14:13:10 +0100 (CET)
Received: from SRV223.tudelft.net (srv223.tudelft.net [131.180.6.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx3.tudelft.nl (Postfix) with ESMTPS id 7C239CC0094; Mon, 24 Feb 2020 14:13:10 +0100 (CET)
Received: from SRV220.tudelft.net (131.180.6.20) by SRV223.tudelft.net (131.180.6.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.1847.3; Mon, 24 Feb 2020 14:13:04 +0100
Received: from SRV220.tudelft.net ([fe80::dc7a:a6b8:8bb9:2210]) by SRV220.tudelft.net ([fe80::dc7a:a6b8:8bb9:2210%13]) with mapi id 15.01.1847.005; Mon, 24 Feb 2020 14:13:04 +0100
From: Wojciech Kozlowski <W.Kozlowski@tudelft.nl>
To: Shota NAGAYAMA <shota.nagayama@mercari.com>
CC: "Qirg@irtf.org" <Qirg@irtf.org>
Thread-Topic: [Qirg] Update to draft-irtf-qirg-principles
Thread-Index: AQHV5Xt24vkv66rV1k+6Pob/xtiN5KglhvoAgATPUs0=
Date: Mon, 24 Feb 2020 13:13:03 +0000
Message-ID: <c3fbae43d6d24dc4abce1c7ffe759216@tudelft.nl>
References: <76c05be1e9dedc091f23cef1e0d0eb3361bdbe31.camel@tudelft.nl>, <CAG_2Tb8AgOSOLnx3yjrUyG41EvUWFG-tSrYe_xvawR_Eop+qFg@mail.gmail.com>
In-Reply-To: <CAG_2Tb8AgOSOLnx3yjrUyG41EvUWFG-tSrYe_xvawR_Eop+qFg@mail.gmail.com>
Accept-Language: en-GB, nl-NL, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_c3fbae43d6d24dc4abce1c7ffe759216tudelftnl_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/k7J_ZC7VhgKHl36zilsJzKySJy0>
Subject: Re: [Qirg] Update to draft-irtf-qirg-principles
X-BeenThere: qirg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Quantum Internet \(proposed\) RG" <qirg.irtf.org>
List-Unsubscribe: <https://www.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://www.irtf.org/mailman/listinfo/qirg>, <mailto:qirg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2020 13:13:20 -0000

There's a lot of good points here.


> I think this document should explicitly explains that quantum networks may and may not execute forwarding (data) in Subsec. 5.1.


I think it's already mentioned somewhere, but worth reiterating if it's not clear.


> quantum networks execute routing and swapping, instead of forwarding


This is correct, but ultimately I would put swapping and forwarding under the umbrella of "data plane". It is definitely worth clarifying that the first generations of quantum networks will swap generic pairs as opposed to forward user-data, but beyond that I'm not sure how much more needs to be done. First, we must be careful to drop the word "forwarding" in case it does appear somewhere in the draft. Second, define in much clearer text what is expected from the data plane - however, given that this definition may shift as these networks get built over the coming years this shouldn't be too restrictive.


> "Routing and swapping" might have to be "routing and measuring". "Routing and measuring" can intuitively cover broader ideas, such as graph state-based routing and surface code quantum communication, that don't execute forwarding and don't execute even entanglement swapping, but execute measurements. (Of course, entanglement swapping has measurements)


Perhaps, going back to my previous point - put it all under data plane action and explain what action that might be.


> suppose store and forward system


This also raises a good point - whilst this problem is explained indirectly as swapping and decoherence in the draft at no point does it say explicitly that  neither the store nor forward concepts of store-and-forward work very well in the first generation networks.


> The current document implies that there are generations of quantum networks (Subsec. 4.2 Direct transmission mentions "generation"), but no section summarizes generations. The new explanation would solve the wonder of readers raised by the implication.


Very good point. The draft basically only explains enough concepts for the first generation and it is probably worth sticking to it given that these are in the process of actually being built in labs. But it would be worth explaining in some moderate detail what the road ahead might look like.


> I'm going to make a pull request. Please see that.


This would be welcome.


Thanks,

Wojtek

________________________________
From: Shota NAGAYAMA <shota.nagayama@mercari.com>
Sent: 21 February 2020 13:20:50
To: Wojciech Kozlowski
Cc: Qirg@irtf.org
Subject: Re: [Qirg] Update to draft-irtf-qirg-principles

Hi,

I think this document should explicitly explains that quantum networks may and may not execute forwarding (data) in Subsec. 5.1.
Routing and forwarding are different functionalities. Routing decides which way to go, forwarding executes the transfer obeying the decision.
The 1st and the 2nd generation (Muralidharan's definition) quantum networks execute routing and swapping, instead of forwarding.
The 3rd generation does routing and forwarding.

"Routing and swapping" might have to be "routing and measuring". "Routing and measuring" can intuitively cover broader ideas, such as graph state-based routing and surface code quantum communication, that don't execute forwarding and don't execute even entanglement swapping, but execute measurements. (Of course, entanglement swapping has measurements)

Muralidharan's three generations should not be explicitly mentioned in the document since more types (generations) of quantum networks would appear in the future.
However, I would believe that any types of quantum networking belong to the roughly divided two types of quantum networks, "routing and measuring" and "routing and forwarding". Hence those two types would be worth writing. At least, it is worth writing that forwarding may not exist, as the unique distinction of quantum networking.

Such a new section will help network-backgrounded people who may unconsciously suppose store and forward system.

The current document implies that there are generations of quantum networks (Subsec. 4.2 Direct transmission mentions "generation"), but no section summarizes generations. The new explanation would solve the wonder of readers raised by the implication.

How do you think?

I'm going to make a pull request. Please see that.
------------------------------------------------
永山翔太 Shota Nagayama
shota.nagayama@mercari.com<mailto:shota.nagayama@mercari.com>
https://shota.io/<https://urldefense.proofpoint.com/v2/url?u=https-3A__shota.io_&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=mdcx9G2TAEosKgcW5QzHKwoLNFc53LUlK0mwjFBU33M&s=vBNOZMRv6Rsz36pvi3DzvnfM58WIB5lNgmbAC1G20v4&e=>
https://qitf.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__qitf.org_&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=mdcx9G2TAEosKgcW5QzHKwoLNFc53LUlK0mwjFBU33M&s=alX2gr-JJ062fMsN2j9xVs0DeoMBBXfb-3a2F_9n5ms&e=>
https://r4d.mercari.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__r4d.mercari.com&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=mdcx9G2TAEosKgcW5QzHKwoLNFc53LUlK0mwjFBU33M&s=GTb2pgBmlBAsixMFOa_67p4p1LqYMW0rdanfD0ATZs8&e=>


On Mon, Feb 17, 2020 at 7:17 PM Wojciech Kozlowski <W.Kozlowski@tudelft.nl<mailto:W.Kozlowski@tudelft.nl>> wrote:
Dear QIRG,

I have just added a contribution to the elementary link generation section.
Thank you Sara and Marcello.

Latest version:
https://github.com/Wojtek242/draft-irtf-qirg-principles/blob/master/draft-irtf-qirg-principles-03.txt<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Wojtek242_draft-2Dirtf-2Dqirg-2Dprinciples_blob_master_draft-2Dirtf-2Dqirg-2Dprinciples-2D03.txt&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=mdcx9G2TAEosKgcW5QzHKwoLNFc53LUlK0mwjFBU33M&s=PB6R4ikTK78IeWosVGptAhTva9qeCNukIULIvP9OACk&e=>

Diff:
https://github.com/Wojtek242/draft-irtf-qirg-principles/commit/3952b2f15f3720325ce42c61c8857a2ede1a0f2e<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Wojtek242_draft-2Dirtf-2Dqirg-2Dprinciples_commit_3952b2f15f3720325ce42c61c8857a2ede1a0f2e&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=mdcx9G2TAEosKgcW5QzHKwoLNFc53LUlK0mwjFBU33M&s=Kqr3cIYos22_BE1c6wneixG8jDXvAfFbwUO3I57y5iw&e=>

Moving forward: my plan is now to finalise the principles/goals sections. Some
feedback has already been given on this subject and I will try to make sure I
take it all into account.

I propose that for this part, I first write the update myself based on feedback
received so far. If you have something to add with regards to this section,
please share on the mailing list as soon as you can. I will then upload an
update some time next week so that I can incorporate any feedback (deadline for
drafts for this IETF is 9 March).

Unless these last updates lead to much debate, I'd think this will mark the
last few updates to the draft (+ pending PRs). In this case, I would aim to
start finalising it after Vancouver. If there are any contentious issue, I will
aim to resolve them on the mailing list before the next meeting.

Thanks,
Wojtek
_______________________________________________
Qirg mailing list
Qirg@irtf.org<mailto:Qirg@irtf.org>
https://www.irtf.org/mailman/listinfo/qirg<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.irtf.org_mailman_listinfo_qirg&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=mdcx9G2TAEosKgcW5QzHKwoLNFc53LUlK0mwjFBU33M&s=y2AfhD-2kk1yhLSKQve-89EhZhBX-4mX4OxCRsf31zs&e=>