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

Wojciech Kozlowski <W.Kozlowski@tudelft.nl> Mon, 24 February 2020 12:38 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 D83C43A09D5 for <qirg@ietfa.amsl.com>; Mon, 24 Feb 2020 04:38:07 -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 A2aibh1vjkvI for <qirg@ietfa.amsl.com>; Mon, 24 Feb 2020 04:38:05 -0800 (PST)
Received: from mailservice.tudelft.nl (mailservice.tudelft.nl [130.161.131.5]) (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 67EFF3A09D3 for <Qirg@irtf.org>; Mon, 24 Feb 2020 04:38:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by amavis (Postfix) with ESMTP id 960C124007D; Mon, 24 Feb 2020 13:37:59 +0100 (CET)
X-Virus-Scanned: amavisd-new at tudelft.nl
Received: from mailservice.tudelft.nl ([130.161.131.71]) by localhost (tudelft.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rC1GjDSQDXHf; Mon, 24 Feb 2020 13:37:58 +0100 (CET)
Received: from SRV222.tudelft.net (mailboxcluster.tudelft.net [131.180.6.22]) (using TLSv1.2 with cipher AES256-SHA256 (256/256 bits)) (No client certificate requested) by mx4.tudelft.nl (Postfix) with ESMTPS id E67862400AE; Mon, 24 Feb 2020 13:37:55 +0100 (CET)
Received: from SRV220.tudelft.net (131.180.6.20) by SRV222.tudelft.net (131.180.6.22) 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 13:37:51 +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 13:37:51 +0100
From: Wojciech Kozlowski <W.Kozlowski@tudelft.nl>
To: Rodney Van Meter <rdv@sfc.wide.ad.jp>
CC: "Qirg@irtf.org" <Qirg@irtf.org>
Thread-Topic: [Qirg] Update to draft-irtf-qirg-principles
Thread-Index: AQHV5Xt24vkv66rV1k+6Pob/xtiN5KgktgEAgAWZ/h0=
Date: Mon, 24 Feb 2020 12:37:51 +0000
Message-ID: <7411da65cd694de7aa407795c05ff6aa@tudelft.nl>
References: <76c05be1e9dedc091f23cef1e0d0eb3361bdbe31.camel@tudelft.nl>, <51161650-93DD-422E-851D-B333021B83D3@sfc.wide.ad.jp>
In-Reply-To: <51161650-93DD-422E-851D-B333021B83D3@sfc.wide.ad.jp>
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_7411da65cd694de7aa407795c05ff6aatudelftnl_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/tL1mmTUlQS4PSpLBE38YsU8Zd-o>
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 12:38:08 -0000

> For an architecture doc, I’d say one of the things we need to do is substantially raise the # of references, in context, of course.


This is something I was wondering about and it came up when I was working with Sara on the elementary link generation. What is the right number of references? As an IRTF document (as opposed to an IETF doc) we have flexibility to define what is suitable. Here are some of my thoughts on this:


  1.  I kept the number of references light, because the intended audience who will benefit the most from this doc (IETF folk) will probably not benefit much from dense physics-heavy quantum networking academic literature.
  2.  This is an intro document to set the stage for further discussion, not an academic review of the field.
  3.  Academics for understandable reasons care about being cited, but RFCs don't go into a citation count anyway (I think).
  4.  Nevertheless, adding references means that the interested reader knows where to look and acknowledges the fields' origin.

There is likely a meaningful compromise between my spartan reference list and a full blown review reference list which will cite a 100 papers before the end of the first paragraph. Thoughts, citation suggestions, and PRs all welcome on this topic.

Opinions from readers on the list who are not physicists or academics particularly welcome.

> For link-layer architectures with memory, there are three major ways you can organize:

I believe this has been included now in the elementary link generation section..

Thanks,
Wojtek
________________________________
From: Rodney Van Meter <rdv@sfc.wide.ad.jp>
Sent: 21 February 2020 00:52:54
To: Wojciech Kozlowski
Cc: Rodney Van Meter; Qirg@irtf.org
Subject: Re: [Qirg] Update to draft-irtf-qirg-principles

For an architecture doc, I’d say one of the things we need to do is substantially raise the # of references, in context, of course.

For link-layer architectures with memory, there are three major ways you can organize:

* memory-to-memory (M—>M)
* midpoint interference, which we call M—>I<—M and Cody calls meet-in-the-middle
* midpoint source, which we call M<—S—>M

Best reference on these is
https://iopscience.iop.org/article/10.1088/1367-2630/18/8/083015/meta<https://urldefense.proofpoint.com/v2/url?u=https-3A__iopscience.iop.org_article_10.1088_1367-2D2630_18_8_083015_meta&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=9oGH87PwWnOQaZwYFdfDUQYApf4nsDV8Q_-j1B3JBwo&s=ZQsgkvPhFyR8dh5MzPsi7hluRSVQ6-5Yu2mKaLvm6bM&e=>
which, blessedly, is open access.

I saw a message about a presentation — have we restarted telecons on this doc?  If so, my apologies on missing that announcement.

Rodney Van Meter
Professor, Faculty of Environment and Information Studies
Keio University, Japan
rdv@sfc.wide.ad.jp<mailto:rdv@sfc.wide.ad.jp>



On Feb 17, 2020, at 19:17, 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=9oGH87PwWnOQaZwYFdfDUQYApf4nsDV8Q_-j1B3JBwo&s=h8UTII244xcn9ku-GQ1u1c--qrLT2IQb_IJrj_IRk00&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=DwQFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=9oGH87PwWnOQaZwYFdfDUQYApf4nsDV8Q_-j1B3JBwo&s=Fja4CVs6SXH5qSbkXF680Wx7RdABeTNEERA0i8uRiPs&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
https://www.irtf.org/mailman/listinfo/qirg<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.irtf.org_mailman_listinfo_qirg&d=DwQFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m=9oGH87PwWnOQaZwYFdfDUQYApf4nsDV8Q_-j1B3JBwo&s=CtiWk0MpzuFjuCfRQP0wmd1MZnFQPOkQHnseUuJRiwo&e=>