Re: [Qirg] I-D Action: draft-irtf-qirg-quantum-internet-use-cases-02.txt

[Chonggang Wang <[e-mail]>]

Hello Patrick, Wojtek,

Thank you very much for your feedback and comments on the use case document.

I provide you below with some responses beginning with [CW].

Best regards,
Chonggang

-----Original Message-----
From: Gelard Patrick <[e-mail]>
Sent: Friday, October 9, 2020 4:41 AM
To: Wojciech Kozlowski <[e-mail]>; Chonggang Wang <[e-mail]>; [e-mail]
Subject: RE: [Qirg] I-D Action: draft-irtf-qirg-quantum-internet-use-cases-02.txt

Answer in the text [PG]

Best regards
Patrick

-----Message d'origine-----
De : Wojciech Kozlowski <[e-mail]> Envoyé : jeudi 8 octobre 2020 10:34 À : Gelard Patrick <[e-mail]>; Chonggang Wang <[e-mail]>; [e-mail] Objet : RE: [Qirg] I-D Action: draft-irtf-qirg-quantum-internet-use-cases-02.txt

Hi all,

I started going through the new draft and I have some questions that would help me before I progress further:
* I am struggling to understand the difference between Quantum Subnetwork and Quantum Internet. Is the difference the same as between a classical subnetwork and the classical Internet? The definitions in the text are too vague for me.
* Additionally, some further comments in-line below in response to Patrick's comments.

> -----Original Message-----
> From: Qirg <[e-mail]> On Behalf Of Gelard Patrick
> Sent: 07 October 2020 16:18
> To: Chonggang Wang <[e-mail]>; [e-mail]
> Subject: Re: [Qirg] I-D Action:
> draft-irtf-qirg-quantum-internet-use-cases-
> 02.txt
>
> Dear Chonggang,
>
> Somes feedback
>
> 1/ 4.3.  Control vs Data Plane Classification  The internet draft
> "Principles for a Quantum Internet" doesn't seem to mention a native
> quantum control plan (i.e based on quantum communication, E.g quatum ping) :
>
> Control plane protocols for quantum networks will have  responsibilities
> similar to their classical counterparts, namely   drawing the network topology,
> resource management, populating data   plane tables, etc.  They will not
> manipulate quantum data themselves   and they operate by exchanging
> classical messages only.  Therefore   there is no separate quantum and
> classical control plane.  There is   only one network control plane.
>
> Should we not make these two documents consistent?
>

[WK] Patrick is right. It would be beneficial to get these two documents consistent and he is also right that with the latest changes I made I seem to exclude a quantum ping from the control plane. This is worth picking up on. As a start, a question to everybody: is the definition in the principles draft too strict then?
[PG] This probably requires more work to identify more precisely what could be native quantum network control services.
[CW] Fully agree to have both documents consistent. Will update "Use Case" document based on the feedback from QIRG and news changes to "Principles for a Quantum Internet".

> 2/ 6.2.  Requirements
> In coherence with "Quantum internet: A vision for the road ahead" and
> "Principles for a Quantum Internet" should it not be necessary to
> define system metrics making it possible to express the quality of
> service requirements expected by the quantum applications I.e expected
> entanglement fidelity,  loss tolerance, error tolerance, Bell pair
> rate, Bell pair traffic profil (i.e bursty profil. For example if we
> use satellite LEO to generate Bell pair we may be interested in
> wanting to know what would be the impact on applications of Bell pair
> transmission breaks during phases of non-visibility of the satellite
> by ground stations), latence, time synchronization of nodes, ...  ?
>

[WK] I think these numbers would be great, but really hard to come up with without a more detailed analysis. However, identifying which stage an application requires is already quite informative in terms of requirements. For example, identifying whether we only need a "quantum memory" stage network vs "fault-tolerant" already tells us a lot.
[PG] The objective is to start identifying the relevant metrics for the QoS expected by the applications of a quantum network.
Then targeting orders of magnitude of these metrics for given classes of applications will require extensive statistical testing, off course.  For classical communications it is aimed intervals, bounds, but not precise values.
http://wiki.martin.lncc.br/ziviani-cursos-ga-redes-2010-2/file/internet2apps-qo-s-needs.pdf
https://www.jaist.ac.jp/~razvan/publications/qos_measurement.pdf
...
Concerning the QBER metric it seems to me that for the QKD service we are beginning to have orders of magnitude.
In the document "Principles for a Quantum Internet" it is mentioned "Interestingly, quantum applications do not need perfect fidelity to   be able to execute -- as long as the fidelity is above some   application-specific threshold, they will simply operate at lower   rates.  Therefore, rather than trying to ensure that we always   deliver perfect states (a technologically challenging task)   applications will specify a minimum threshold for the fidelity and   the network will try its best to deliver it."  It would be nice to have orders of magnitude of the threshold for different class of application.

[CW] I have the same feeling as Wojtek. Figure 5 "Example Use Cases in Different Quantum Internet Stages" presents "each stage vs application requires".

Now it may indeed be a whole document to be done on the QoS metrics of a quantum network.
[CW] Yes, better to have a separate document covering QoS aspects of a quantum network.

> Best Regards
> Patrick
>
> -----Message d'origine-----
> De : Qirg <[e-mail]> De la part de Chonggang Wang Envoyé :
> mercredi 30 septembre 2020 16:06 À : [e-mail] Objet : Re: [Qirg]
> I-D
> Action: draft-irtf-qirg-quantum-internet-use-cases-02.txt
>
> Dear QIRG,
>
> Quantum internet use cases have been updated to address the comments
> received during IETF July meeting. Please refer to
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.org_doc_draft-2Dirtf-2Dqirg-2Dquantum-2Dinternet-
> 2Duse-2Dcases_&d=DwIFAw&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=ScCiYNV0YHMuwv
> Q9EO9Pg2DpMUILknHf77NGTuuu24Q&e= .
>
> We would like to get your feedback on this new version and if the use
> case draft can be considered for next steps.
>
> Best regards,
> Chonggang
>
> -----Original Message-----
> From: Qirg <[e-mail]> On Behalf Of
> [e-mail]
> Sent: Friday, September 18, 2020 7:46 AM
> To: [e-mail]
> Cc: [e-mail]
> Subject: [Qirg] I-D Action:
> draft-irtf-qirg-quantum-internet-use-cases-02.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Quantum Internet Research Group RG of
> the IRTF.
>
>         Title           : Applications and Use Cases for the Quantum Internet
>         Authors         : Chonggang Wang
>                           Akbar Rahman
>                           Ruidong Li
>                           Melchior Aelmans
> Filename        : draft-irtf-qirg-quantum-internet-use-cases-02.txt
> Pages           : 23
> Date            : 2020-09-18
>
> Abstract:
>    The Quantum Internet has the potential to improve application
>    functionality by incorporating quantum information technology into
>    the infrastructure of the overall Internet.  In this document, we
>    provide an overview of some applications expected to be used on the
>    Quantum Internet, and then categorize them using various
>    classification schemes.  Some general requirements for the Quantum
>    Internet are also discussed.  The intent of this document is to
>    provide a common understanding and framework of applications and use
>    cases for the Quantum Internet.
>
>
> The IETF datatracker status page for this draft is:
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.org_doc_draft-2Dirtf-2Dqirg-2Dquantum-2Dinternet-
> 2Duse-2Dcases_&d=DwIFAw&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=ScCiYNV0YHMuwv
> Q9EO9Pg2DpMUILknHf77NGTuuu24Q&e=
>
> There are also htmlized versions available at:
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_html_draft-2Dirtf-2Dqirg-2Dquantum-2Dinternet-2Duse
> -
> 2Dcases-2D02&d=DwIFAw&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=KSHcjW7jCfeh3ws
> S75EyRdWTPdm6wox1tKWCh0i_EoU&e=
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.org_doc_html_draft-2Dirtf-2Dqirg-2Dquantum-
> 2Dinternet-2Duse-2Dcases-2D02&d=DwIFAw&c=XYzUhXBD2cD-
> CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=PqYaD-
> P1uYemX5KMDp67_mL8sz6KYBE_pwkE869Nhgs&e=
>
> A diff from the previous version is available at:
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dirtf-2Dqirg-2Dquantum-
> 2Dinternet-2Duse-2Dcases-2D02&d=DwIFAw&c=XYzUhXBD2cD-
> CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=V3FasdcOnxQiM6s
> yp-OClMyL9y9IsvAr0m4m2DTaY2g&e=
>
>
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_intern
> et-
> 2Ddrafts_&d=DwIFAw&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=Hwq4UCag4XW_1
> UFXZM-cw47xdeFD55h3U9TQqMHx4Yg&e=
>
>
> _______________________________________________
> Qirg mailing list
> [e-mail]
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.irtf.org_mailman_listinfo_qirg&d=DwIFAw&c=XYzUhXBD2cD-
> CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=4T2oNNxQRVdPId
> CTJVle2wo1tQ3JooBoUm9HX3Yl1nA&e=
> [Banner]
>
> [Banner]<https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.6gsymposium.com_-3Futm-5Fsource-3Dinterdigital-26utm-
> 5Fmedium-3Dsignature-26utm-5Fcampaign-
> 3D6gsymposium2020&d=DwIFAw&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=NxCbRqWTfZnM2
> MBvewu6-h-h_BGyflCmCjOze2xJrYs&e= >
>
> Join us at the First Annual 6G Symposium Virtual
> Event<https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.6gsymposium.com_-3Futm-5Fsource-3Dinterdigital-26utm-
> 5Fmedium-3Dsignature-26utm-5Fcampaign-
> 3D6gsymposium2020&d=DwIFAw&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=NxCbRqWTfZnM2
> MBvewu6-h-h_BGyflCmCjOze2xJrYs&e= > This e-mail is intended only for
> the use of the individual or entity to which it is addressed, and may
> contain information that is privileged, confidential and/or otherwise
> protected from disclosure to anyone other than its intended recipient.
> Unintended transmission shall not constitute waiver of any privilege
> or confidentiality obligation. If you received this communication in
> error, please do not review, copy or distribute it, notify me
> immediately by email, and delete the original message and any
> attachments. Unless expressly stated in this e-mail, nothing in this
> message or any attachment should be construed as a digital or electronic signature.
>
> _______________________________________________
> Qirg mailing list
> [e-mail]
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.irtf.org_mailman_listinfo_qirg&d=DwIFAw&c=XYzUhXBD2cD-
> CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=4T2oNNxQRVdPId
> CTJVle2wo1tQ3JooBoUm9HX3Yl1nA&e=
>
> _______________________________________________
> Qirg mailing list
> [e-mail]
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.irtf.org_mailman_listinfo_qirg&d=DwIFAw&c=XYzUhXBD2cD-
> CornpT4QE19xOJBbRy-
> TBPLK0X9U2o8&r=xRe3k8UnFVGCjuC7RWUARpslGfYlRaP7D3dVZXHUEVc&m
> =vRyl9_Ww9DdYXXeBUp6F4AhPhy7qC0fH2FLcbGIntTI&s=4T2oNNxQRVdPId
> CTJVle2wo1tQ3JooBoUm9HX3Yl1nA&e=
[Banner]

[Banner]<https://www.6gsymposium.com/?utm_source=interdigital&utm_medium=signature&utm_campaign=6gsymposium2020>

Join us at the First Annual 6G Symposium Virtual Event<https://www.6gsymposium.com/?utm_source=interdigital&utm_medium=signature&utm_campaign=6gsymposium2020>
This e-mail is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise protected from disclosure to anyone other than its intended recipient. Unintended transmission shall not constitute waiver of any privilege or confidentiality obligation. If you received this communication in error, please do not review, copy or distribute it, notify me immediately by email, and delete the original message and any attachments. Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.