﻿<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [


<!ENTITY rfc7498 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7498.xml'>
<!ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
<!ENTITY rfc7258 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7258.xml'>

<!ENTITY I-D.irtf-qirg-principles SYSTEM 'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.irtf-qirg-principles.xml'>
<!ENTITY I-D.dahlberg-ll-quantum SYSTEM 'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.dahlberg-ll-quantum.xml'>
<!ENTITY I-D.van-meter-qirg-quantum-connection-setup SYSTEM 'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.van-meter-qirg-quantum-connection-setup.xml'>

]>

<rfc ipr="trust200902" category="info" docName="draft-irtf-qirg-quantum-internet-use-cases-05">
  <?rfc toc="yes"?>
  <?rfc symrefs="yes"?>
  <?rfc sortrefs="yes"?>
  <?rfc compact="yes"?>
  <?rfc subcompact="no"?>
  <?rfc private=""?>
  <?rfc topblock="yes"?>
  <?rfc comments="no"?>
  
  <front>
    <title abbrev=" Quantum Internet Use Cases">Applications and Use Cases for the Quantum Internet</title>
	
	<author initials="C." surname="Wang" fullname="Chonggang Wang">
      <organization>InterDigital Communications, LLC</organization>
      <address>
        <postal>
          <street>1001 E Hector St</street>
          <city>Conshohocken</city>
          <code>19428</code>
          <country>USA</country>
          <region></region>
        </postal>
        <phone></phone>
        <email>Chonggang.Wang@InterDigital.com</email>
        <uri></uri>
      </address>
    </author>
	
    <author initials="A." surname="Rahman" fullname="Akbar Rahman">
      <organization>InterDigital Communications, LLC</organization>
      <address>
        <postal>
          <street>1000 Sherbrooke Street West</street>
          <city>Montreal</city>
          <code>H3A 3G4</code>
          <country>Canada</country>
          <region></region>
        </postal>
        <phone></phone>
        <email>rahmansakbar@yahoo.com</email>
        <uri></uri>
      </address>
    </author>

    <author initials="R." surname="Li" fullname="Ruidong Li">
      <organization>NICT</organization>
      <address>
        <postal>
          <street>4-2-1 Nukui-Kitamachi</street>
          <city>Koganei, Tokyo</city>
          <code>184-8795</code>
          <country>Japan</country>
          <region></region>
        </postal>
        <phone></phone>
        <email>lrd@nict.go.jp</email>
        <uri></uri>
      </address>
    </author>
	
	<author initials="M." surname="Aelmans" fullname="Melchior Aelmans">
      <organization>Juniper Networks</organization>
      <address>
        <postal>
          <street>Boeing Avenue 240</street>
          <city>Schiphol-Rijk</city>
          <code>1119 PZ</code>
          <country>The Netherlands</country>
          <region></region>
        </postal>
        <phone></phone>
        <email>maelmans@juniper.net</email>
        <uri></uri>
      </address>
    </author>
	
    <date year="2021" month="March" day="29"/>

    <area>Internet Research Task Force (IRTF)</area>
    <workgroup>QIRG</workgroup>


    <abstract>
      <t>
		The Quantum Internet has the potential to improve application functionality by incorporating quantum information
		technology into the infrastructure of the overall Internet.  This document provides an overview of some applications
		expected to be used on the Quantum Internet, and then categorizes them using various classification schemes. Some general
		requirements for the Quantum Internet are also discussed. The intent of this document is to describe a
		framework for applications, and describe use cases for the Quantum Internet.  This document is a product of the Quantum Internet
	    Research Group (QIRG).
      </t>
    </abstract>
 

  </front>




  <middle>

    <section anchor="sec:introduction" title="Introduction">
   
	  <t>
	    The Classical Internet has been constantly growing since it first became commercially popular in the early 1990's.  It essentially consists
		of a large number of end-nodes (e.g., laptops, smart phones, network servers) connected by routers and clustered in Autonomous Systems.  
		The end-nodes may run applications that provide service for the end-users such as processing and transmission of voice, video or data.
		The connections between the various nodes in the Internet include backbone links (e.g., fiber optics) and access
		links (e.g., WiFi, cellular wireless, Digital Subscriber Lines (DSLs)). Bits are transmitted across the Classical Internet in packets.
      </t>
      <t>
        Research and experiments have picked up over the last few years for developing the Quantum Internet  <xref target="Wehner" />.
		End-nodes will also be part of the Quantum Internet, in that case called quantum end-nodes that may be connected by quantum repeaters/routers.
		These quantum end-nodes will also run value-added applications which will be discussed later.
		</t>
		
	   <t>
		The connections between the various nodes in the Quantum Internet are expected to be primarily fiber optics and free-space optical lasers.  
		Photonic connections are particularly useful because light (photons) is very suitable for physically realizing qubits. 
		Unlike the Classical Internet, qubits (and not classical bits or packets) are expected to be transmitted across the Quantum 
		Internet.  The Quantum Internet will operate according to quantum physical principles such as quantum superposition and
		entanglement <xref target="I-D.irtf-qirg-principles" />.
	  </t>

	  <t>
		The Quantum Internet is not anticipated to replace, but rather to enhance the Classical Internet. For instance,   
		quantum key distribution can improve the security of the Classical Internet; the powerful computation capability of quantum computing
		can expedite and optimize computation-intensive tasks (e.g., routing modelling) in the Classical Internet. The Quantum Internet will run in 
		conjunction with the Classical Internet to form a new Hybrid Internet. The process of integrating the Quantum Internet with the Classical 
		Internet is similar to, but with more profound implications, as the process of introducing any new communication and networking
		paradigm into the existing Internet.  The intent of this document is to provide a common understanding and framework of applications
		and use cases for the Quantum Internet.
      </t>


	  <t>This document represents the consensus of the Quantum Internet Research Group (QIRG).  It has been reviewed extensively 
	     by Research Group (RG) members with expertise in both quantum physics and Classical Internet operation.
         </t>

    </section>




	<section anchor="sec:acronyms" title="Terms and Acronyms List">
	  <t>
		This document assumes that the reader is familiar with the quantum information technology related terms and concepts that are
		described in <xref target="I-D.irtf-qirg-principles" />.  In addition, the following terms and acronyms are defined herein for clarity:
      </t> 


		<t>
          <list style="symbols">
		 	<t>Bit - Binary Digit (i.e., fundamental unit of information in classical communications and classical computing).</t>
			
			<t>Classical Internet - The existing, deployed Internet (circa 2020) where bits are transmitted in packets between nodes to convey information.
			   The Classical Internet supports applications which may be enhanced by the Quantum Internet.  For example, the end-to-end security of a
			   Classical Internet application may be improved by secure communication setup using a quantum application.</t>
			
			<!--<t>DSL - Digital Subscriber Line</t>-->
			<!--<t>GUI - Graphical User Interface</t>-->
			
			<t>Fast Byzantine Negotiation - A Quantum-based method for fast agreement in Byzantine negotiations <xref target="Fitzi" />.  </t>
			<t>Hybrid Internet - The "new" or evolved Internet to be formed due to a merger of the Classical Internet and the Quantum Internet.</t>
			
			<t> Local Operations and Classical Communication (LOCC) - A method where nodes communicate in rounds, in which (1) they can send any classical 
			    information to each other; (2) they can perform local quantum operations individually; and (3) the actions performed in each round can depend 
				on the results from previous rounds. 			
			</t>
			
			<t>Noisy Intermediate-Scale Quantum (NISQ) - NISQ was defined in <xref target="Preskill"/> to represent a near-term era in quantum technology. 
			According to this definition, NISQ computers have two salient features: (1) The size of NISQ computers range from 50 to a few hundred physical qubits
			(i.e., intermediate-scale); and (2) Qubits in NISQ computers have inherent errors and the control over them is imperfect (i.e., noisy).</t>

			
			<t>Packet - Formatted unit of multiple related bits. The bits contained in a packet may be classical bits, or the measured state of qubits expressed in classical bits.</t>
			<t>Prepare-and-Measure - A set of Quantum Internet scenarios where quantum nodes only support simple quantum functionalities (i.e., prepare qubits and measure qubits). 
			For example, BB84 <xref target="BB84"/> is a prepare-and-measure quantum key distribution protocol. 
			</t>
			<t>Quantum End-node - An end-node hosts user applications and interfaces with the rest of the Internet.  Typically, an end-node may serve in a client,
			server, or peer-to-peer role as part of the application.  If the end-node is part of a Quantum Network (i.e, is a quantum end-node), it must be able to
			generate/transmit and receive/process qubits.  A quantum end-node must also be able to interface to the Classical Internet for control
			purposes and thus also be able to receive, process, and transmit classical bits/packets.</t>
			
			<t>Quantum Computer (QC) - A quantum end-node that also has quantum memory and quantum computing capabilities is regarded as a full-fledged quantum
			computer.</t>
			
			<t>Quantum Key Distribution (QKD) - A method that leverages quantum mechanics such as no-cloning theorem to let two parties (e.g., a sender and a receiver) securely establish/agree on a key.</t>
			
			<t>Quantum Network	- A new type of network enabled by quantum information technology where qubits are transmitted between nodes to convey information.
			(Note: qubits must be sent individually and not in packets). The Quantum Network will use both quantum channels, and classical channels provided 
			by the Classical Internet.</t>
						
			<t>Quantum Internet	- A network of Quantum Networks. The Quantum Internet is expected to be merged into the Classical Internet to form a new Hybrid Internet.
			 The Quantum Internet may either improve classical applications or may enable new quantum applications.</t>	
			
			<t>Qubit - Quantum Bit (i.e., fundamental unit of information in quantum communication and quantum computing).  It is similar to a classic bit in that the state of a qubit
			is either "0" or "1" after it is measured, and is denoted as its basis state vector |0> or |1>.  However, the qubit is different than a classic bit in that 
			the qubit can be in a linear combination of both states before it is measured and termed to be in superposition.  The Degrees of Freedom (DOF) of a photon 
			(e.g., polarization) or an electron (e.g., spin) can be used to encode a qubit.</t>	
			<!--<t>VoIP - Voice Over IP</t>-->
         </list>
		 </t>
			 
		 
    </section>



    <section anchor="sec:applications" title="Quantum Internet Applications">

		<section anchor="sec:overview" title="Overview">
			<t>
			The Quantum Internet is expected to be beneficial for a subset of existing and new applications.
			The expected applications for the Quantum Internet are still being developed as we are in the formative stages 
			of the Quantum Internet	<xref target="Castelvecchi" /> <xref target="Wehner" />.  However, an initial 
			(and non-exhaustive) list of the applications to be supported on the Quantum Internet can be identified and 
			classified using two different schemes. Note, this document does not include quantum computing applications that are purely 
			local to a given node (e.g., quantum random number generator).			
			<!--We use "applications" in the widest sense of the word and include functionality typically contained in Layers 4 
			(Transport) to Layers 7 (Application) of the Open System Interconnect (OSI) model. -->
			</t>				
	    </section>	
		
		
		<section anchor="sec:main_classifictions" title="Classification by Application Usage">
	  
		<t>Applications may be grouped by the usage that they serve.  Specifically,
		applications may be grouped according to the following categories:
          <list style="symbols">
			<t>Quantum cryptography applications - Refers to the use of quantum information technology for cryptographic tasks such as quantum key distribution and quantum commitment.</t>
			<t>Quantum sensors applications - Refers to the use of quantum information technology for supporting
			distributed sensors (e.g., clock synchronization).</t>
			<t>Quantum computing applications - Refers to the use of quantum information technology for
			supporting remote quantum computing facilities (e.g., distributed quantum computing).</t>			  			

		   </list>
		   
			This scheme can be easily understood by both a technical and non-technical audience.  
			The next sections describe the scheme in more detail.</t> 
			<section anchor="sec:typeofquantumcrypto" title="Quantum Cryptography Applications">
				<t> Examples of quantum cryptography applications include quantum-based secure communication setup and fast Byzantine negotiation.
				<list style="numbers">			
					<t>Secure communication setup - Refers to secure cryptographic key distribution between two or more end-nodes.  
					The most well-known method is referred to as Quantum Key Distribution (QKD) <xref target="Renner" />, which has been
					mathematically proven to be unbreakable.</t>
				
					<t>Fast Byzantine negotiation - Refers to a Quantum-based method for fast agreement in Byzantine negotiations <xref target="Fitzi" />, for example, 
					to reduce the number of expected communication rounds and in turn achieve faster agreement, in contrast to classical Byzantine negotiations. This can be 
					used for improving consensus protocols such as practical Byzantine 
					Fault Tolerance(pBFT), as well as other distributed computing features which use Byzantine negotiations.</t>	
				</list>	
				</t>
			</section>	
			
			<section anchor="sec:typeofquantumsensor" title="Quantum Sensor Applications">
				<t> Examples of quantum sensor applications include network clock synchronization, high sensitivity sensing, etc. These applications mainly
					leverage a network of entangled quantum sensors (i.e. quantum sensor networks) for high-precision multi-parameter estimation <xref target="Proctor" />. 					
				<list style="numbers">
					<t>Network clock synchronization - Refers to a world wide set of atomic clocks connected by the Quantum Internet to achieve an ultra 
					precise clock signal <xref target="Komar" /> with fundamental precision limits set by quantum theory.</t>
					<t>High sensitivity sensing - Refers to applications that leverage quantum phenomena to achieve reliable nanoscale sensing of 
					physical magnitudes. For example, <xref target="Guo" /> uses an entangled quantum network for measuring the average phase shift among multiple 
					distributed nodes, to achieve high-sensitivity and distributed quantum sensing.</t>										
				</list>	
				</t>
			</section>
			
			<section anchor="sec:typeofquantumcomputing" title="Quantum Computing Applications">
				<t> Examples of quantum computing include distributed quantum computing and secure quantum computing with privacy preservation, which can
				    enable new types of cloud computing. 
				<list style="numbers">			
					<t>Distributed quantum computing - Refers to a collection of remote small capacity quantum computers (i.e., each supporting a relatively small number of qubits) 
					that are connected and working together in a coordinated fashion so as to simulate a virtual large capacity
					quantum computer <xref target="Wehner" />.</t>
				
					<t>Secure quantum computing with privacy preservation - Refers to private, or blind, quantum computation, 
					which provides a way for a client to delegate a computation task to one or more remote quantum computers without disclosing the source data
					to be computed over <xref target="Fitzsimons"/>.</t>
				</list>	
				</t>
			</section>

		</section>
		
		
		
		<section anchor="sec:classification" title="Control vs Data Plane Classification">
			
			<t>The majority of routers currently used in the Classical Internet separate control plane functionality and data plane functionality for, 
			amongst other reasons, stability, capacity and security. In order to classify applications for the Quantum Internet, a somewhat similar
			distinction can be made.  Specifically some applications can be classified as being responsible for initiating sessions and performing other 
			control plane functionality.  Other applications carry application or user data and can be classified as data plane functionality.
			</t>
			
			<t>Some examples of what may be called control plane applications in the Classical Internet are Domain Name Server (DNS), 
			Session Information Protocol (SIP), and Internet Control Message Protocol (ICMP). Furthermore, examples of data plane
			applications are E-mail, web browsing, and video streaming.  Note that some applications may require both control plane
			and data plane functionality. For example, a Voice over IP (VoIP) application may use SIP to set up the call and then 
			transmit the VoIP user packets over the data plane to the other party.			
			</t>
						
			<t>Similarly, nodes in the Quantum Internet applications may also use the classification paradigm of control plane functionality
			versus data plane functionality where:
			<list style="symbols">
				<t>Control Plane - Network functions and processes that operate on (1) control bits/packets or qubits (e.g., to setup up end-user 
				encryption); or (2) management bits/packets or qubits (e.g., to configure nodes). For example, a quantum ping could be implemented 
				as a control plane application to test and verify if there is a quantum connection between two quantum nodes.
				Another example is quantum superdense coding (which is used to transmit two classical bits by sending only one qubit).  This
				approach does not need classical channels.  Quantum superdense coding can be leveraged to implement a secret sharing application
				to share secrets between two parties. This secret sharing application based on quantum superdense encoding can be classified 
				as control plane functionality.</t>
			
			
				<t>Data Plane - Network functions and processes that operate on end-user application bits/packets or qubits (e.g., voice, video, 
				data). Sometimes also referred to as the user plane. For example, a data plane application can be video conferencing, which
				uses QKD-based secure communication setup (which is a control plane function) to share a classical secret key for encrypting
				and decrypting video frames.</t>
			</list>	
				
			</t>	

			<t> As shown in the table in <xref target="fig:controldataplane" />, control and data plane applications vary for different types of networks.
			For a standalone Quantum Network (i.e., that is not integrated into the Internet), entangled qubits are its "data" and thus entanglement distribution can be
			regarded as its data plane application, while the signalling for controlling entanglement distribution be considered as control plane. 
			However, looking at the Quantum Internet, QKD-based secure communication setup, which may be based on and leverage entanglement distribution, is 
			in fact a control plane application, while video conference using QKD-based secure communication setup is a data plane application. 
			In the future, two data planes may exist, respectively for Quantum Internet and Classical Internet, while one control plane can be leveraged for 
			both Quantum Internet and Classical Internet. 
			</t>

<t>
				<?rfc needLines="16" ?>
				<figure anchor="fig:controldataplane" title="Examples of Control vs Data Plane Classification">
				<artwork align="center">
  <![CDATA[    
+----------+-----------+----------------+----------------------+
|          |           |                |                      |
|          | Classical |    Quantum     |      Hybrid          |
|          | Internet  |    Internet    |      Internet        |
|          | Examples  |    Examples    |      Examples        |
+----------+-----------+----------------+----------------------+
|  Control | ICMP;     | Quantum ping;  | QKD-based secure     |
|  Plane   | DNS       | Signalling for | communication        | 
|          |           | controlling    | setup                |
|          |           | entanglement   |                      |
|          |           | distribution;  |                      |
---------------------------------------------------------------|
|  Data    | Video     | QKD;           | Video conference     |
|  Plane   | conference| Entanglement   | using QKD-based      |
|          |           | distribution   | secure communication |
|          |           |                | setup                |
+--------------------------------------------------------------+
   ]]>                  
				</artwork>
				</figure>
</t>					
			
		</section>	    
	  
	  
	  
    </section>



	<section anchor="sec:usecases" title="Selected Quantum Internet Use Cases">

		<t>The Quantum Internet will support a variety of applications and deployment configurations.  This section details
		   a few key use cases which illustrates the benefits of the Quantum Internet.  In system engineering, a use case
		   is typically made up of a set of possible sequences of interactions between nodes and users in a particular
		   environment and related to a particular goal.  This will be the definition that we use in this section. 
		</t>
		
		
		<section anchor="sec:usecase1" title="Secure Communication Setup">		
			<t>
			In this scenario, two banks (i.e., Bank #1 and Bank #2) need to have secure
			communications for transmitting important financial transaction records (see <xref target="fig:securecom" />). 
			For this purpose, they first need to securely exchange a classic secret cryptographic key (i.e., a sequence of classical bits),
			which is triggered by an end-user banker at Bank #1.  This results in a source quantum node A
			at Bank #1 to securely establish a classical secret key with a destination quantum node B at Bank #2.
			This is referred to as a secure communication setup. Note that the quantum node A and B may be either
			a bare-bone quantum end-node or a full-fledged quantum computer. This use case shows that the Quantum Internet
			can be leveraged to improve the security of Classical Internet applications of which the financial application
			shown in <xref target="fig:securecom" /> is an example. 
			</t>
			
			<t>
			One requirement for this secure communication setup process is that it should not be vulnerable to any
			classical or quantum computing attack.  This can be realized using QKD <xref target="ETSI-QKD-Interfaces" />
			which has been mathematically proven to be unbreakable. QKD can securely establish a secret key between two
			quantum nodes, without physically transmitting the key through the network and thus achieving the required security.
			However, care must be taken to ensure that the QKD system is safe against physical attacks which can compromise the
			system.  An example of a physical attack is when an attacker is able to surreptitiously inject additional light
			into the optical devices used in QKD to learn side information about the system such as the polarization.
			Other specialized physical attacks against QKD have also been developed such as the phase-remapping attack, 
			photon number splitting attack, and decoy state attack <xref target="Zhao" />.
			</t>
						
			<t>
			QKD is the most mature feature of the quantum information technology, and has been commercially deployed in
			small-scale and short-distance deployments. More QKD use cases are described in ETSI documents <xref target="ETSI-QKD-UseCases" />.
			</t>
			
			<t>		
			In general,	QKD (e.g., <xref target="BB84"/>) without using entanglement works as follows: 
			  <list style="numbers">
				<t> The source quantum node A transforms classical bits to qubits. Basically, for each classical bit, 
				the source quantum node A randomly selects one out of two basis and uses the selected basis to prepare/generate a qubit for the classical bit.</t>
				<t> The source quantum node A sends qubits to the destination quantum node B via quantum channel.</t>
				<t> The destination quantum node receives qubits and measures each of them in one of the two basis at random. </t>								
				<t> The destination quantum node informs the source node of its choice of basis for each qubit.</t>
				<t> The source quantum node informs the destination node which random quantum basis is correct.</t>
				<t> Both nodes discard any measurement bit under different quantum basis and remaining bits could be used as the secret key. 
				Before generating the final secret key, there is a post-processing procedure over classical channels. For example, both nodes usually employ a part of 
				the remaining bits to check if there were any errors and/or if there were an eavesdrop; another part of the remaining bits could be taken as the secret key.   
				Basically, if an eavesdropper tries to intercept and read qubits sent from node A to node B, the eavesdropper will be detected due to 
				the no-cloning theorem of quantum mechanics. As a part of the post-processing procedure, both nodes usually also perform information reconciliation <xref target="Elkouss"/>
				for efficient error correction and/or conduct privacy amplification <xref target="BTang"/> for generating the final information-theoretical secure keys. </t>
				<t> The post-processing procedure needs to be performed over an authenticated classical channel. In other words, the source quantum node and the destination quantum node need
				to authenticate the classical channel to make sure there is no eavesdroppers or man-in-the-middle attacks, according to certain authentication protocols such as <xref target=" Kiktenko"/>.
				In <xref target=" Kiktenko"/>, the authenticity of the classical channel is checked at the very end of the post-processing procedure instead of doing it for each classical message exchanged 
				between the quantum source node and the quantum destination node. 
				</t>				
			  </list>
			</t>
			
			<t> 
			It is worth noting that:
			   <list style="numbers">			     
				 <t> There are some entanglement-based QKD protocols such as <xref target="Treiber"/>, which work differently than above steps. The entanglement-based schemes, where entangled states are 
				     prepared externally to the source quantum node and the destination quantum node, are not normally considered "prepare-and-measure" as defined in <xref target="Wehner"/>; 
					 other entanglement-based schemes, where entanglement is 
					 generated within the source quantum node can still be considered "prepare-and-measure"; send-and-return schemes can still be "prepare-and-measure", if the information content, from which keys will be 
					 derived, is prepared within the source quantum node the source quantum node before being sent to the destination quantum node for measurement.
			     </t> 
				 <t> There are many enhanced QKD protocols based on <xref target="BB84"/>. For example, a series of loopholes have been identified due to the imperfections of measurement devices; 
				     there are several solutions to take into account these attacks such as measurement-device-independent QKD <xref target="PZhang"/>. These enhanced QKD protocol can work differently than the steps 
					 of BB84 protocol <xref target="BB84"/>.				   
				 </t>
				 <t> For large-scale QKD, QKD Networks (QKDN) are required, which can be regarded as a subset of a Quantum  Internet. A QKDN may consist of a QKD application layer, a QKD network layer, and a QKD link layer <xref target="Qin"/>. 
				     One or multiple trusted QKD relays <xref target="QZhang"/> may exist between the source quantum node A and the destination quantum node B, which are connected by a QKDN. Alternatively, a QKDN may rely on 
					 entanglement distribution and entanglement-based QKD protocols; as a result, quantum-repeaters/routers instead of trusted QKD relays are needed for large-scale QKD.
				 </t>
				 
				 <!-- In general, there could be three types of QKD solutions: 1) Basic QKD: In this case, QKD only works for two directly connected quantum nodes within a short distance or a network segment; 
				     If both nodes are long-distanced, trusted nodes will be needed for relaying multiple basic QKDs between two faraway quantum nodes; 2) E2E QKD: In this case, based on long-distance qubit transmission, 
					 QKD works for two faraway quantum nodes to provide the end-to-end security without relying on trusted nodes; and 3) Advanced E2E QKD: In this case, 
					 two quantum nodes are far away from each other but long-distance qubit transmission may not be available. Instead, QKD leverages entanglement distribution 
					 or quantum repeaters (not trusted nodes) to achieve the end-to-end security. 
				 -->
				 
				 <t> Although the addresses of Source Quantum Node A and Destination Quantum Node B could be identified and exposed, the identity of users, who will use
                     the secret cryptographic key for secure communications, will not necessarily be exposed during QKD process. In other words, there is no direct mapping 
					 from the addresses of quantum nodes to the user identity; as a result, QKD protocols do not disclose user identities.   				 
				 </t>
			   </list>
			</t>
			<t> As a result, the Quantum Internet in <xref target="fig:securecom" /> contains quantum channels. And in order to support secure communication setup especially in large-scale deployment, it also requires entanglement generation 
			and entanglement distribution <xref target="I-D.van-meter-qirg-quantum-connection-setup"/>, quantum repeaters/routers, and/or trusted QKD relays.
			</t>
			
			
			<t>
				<?rfc needLines="16" ?>
				<figure anchor="fig:securecom" title="Secure Communication Setup">
				<artwork align="center">
  <![CDATA[
    
+---------------+
|   End User    |
|(e.g., Banker) |
+---------------+
      ^
      | User Interface
      | (e.g., GUI)    
      V                
+-----------------+     /--------\     +-----------------+         
|                 |--->( Quantum  )--->|                 |
|     Source      |    ( Internet )    |  Destination    |
|     Quantum     |     \--------/     |    Quantum      |
|     Node A      |                    |     Node B      |
| (e.g., Bank #1) |     /--------\     | (e.g., Bank #2) |
|                 |    ( Classical)    |                 |                            
|                 |<-->( Internet )<-->|                 |
+-----------------+     \--------/     +-----------------+
   ]]>                  
				</artwork>
				</figure>
			</t>
			
		</section>
		 		
		<section anchor="sec:usecase2" title="Secure Quantum Computing with Privacy Preservation">
			<t>
				Secure computation with privacy preservation refers to the following scenario: 		
			   <list style="numbers">
					<t>A client node with source data delegates the computation of the source data to a remote computation node (i.e. a server).</t> 
					<t>Furthermore, the client node does not want to disclose any source data to the remote computation node and thus preserve the source data privacy.</t>
					<t>Note that there is no assumption or guarantee that the remote computation node is a trusted entity from the source data privacy perspective.</t>
				</list>	
			</t>			
								
			<t>
				As an example illustrated in <xref target="fig:bqcom" />, a terminal node such as a home gateway has collected lots of data and needs
				to perform computation on the data. The terminal node could be a classical node without any quantum capability, a bare-bone 
				quantum end-node or a full-fledged quantum computer. The terminal node has insufficient computing power and needs to offload data 
				computation to some remote nodes. Although the terminal node can upload the data to the cloud to leverage cloud computing without
				introducing local computing overhead, to upload the data to the cloud can cause privacy concerns.		
				In this particular case, there is no privacy concern since the source data will not be sent
				to the remote computation node which could be compromised. Many protocols as described in <xref target="Fitzsimons" /> for delegated quantum
				computing or Blind Quantum Computation (BQC) can be leveraged to realize secure delegated computation and guarantee 
				privacy preservation simultaneously.				
			</t>
			<t>
				As a new client/server computation model, BQC generally enables: 1) The client delegates a computation
				function to the server; 2) The client does not send original qubits to the server, but send transformed qubits to the server; 3) The computation
				function is performed at the server on the transformed qubits to generate temporary result qubits, which could be quantum-circuit-based 
				computation or measurement-based quantum computation. The server sends the temporary result qubits to the client; 4) The client receives the 
				temporary result qubits and transform them to the final result qubits. During this process, the server can not figure out the original qubits from 
				the transformed qubits. Also, it will not take too much efforts on the client side to transform the original qubits to the transformed qubits, or transform
				the temporary result qubits to the final result qubits. One of the very first BQC protocols such as <xref target="Childs"/> follows this process, although the client needs some 
				basic quantum features such as quantum memory, qubit preparation and measurement, and qubit transmission. Measurement-based quantum computation is 
				out of the scope of this document and more details about it can be found in <xref target="Jozsa"/>. 
			</t>
				
			<t> 
			It is worth noting that:
			   <list style="numbers">
					<t> The BQC protocol in <xref target="Childs"/> is a circuit-based BQC model, where the client only performs simple quantum circuit for 
						qubit transformation, while the server performs a sequence of quantum logic gates. Qubits are transmitted back and forth between the client
						and the server.
					</t>
					<t> Universal BQC in <xref target="Broadbent"/> is a measurement-based BQC model, which is based on measurement-based quantum computing leveraging 
						entangled states. The principle in UBQC is based on the fact the quantum teleportation plus a rotated Bell measurement realizes a quantum computation,
						which can be repeated multiple times to realize a sequence of quantum computation. In this approach, the client first prepares transformed qubits 
						and send them to the server and the server needs first to prepare entangled states from all received qubits. Then, multiple interaction and measurement
						rounds happen between the client and the server. For each round, the client computes and sends new measurement instructions or measurement adaptations 
						to the server; then, the server performs the measurement according to the received measurement instructions to generate measurement results (qubits or in classic bits); 
						the client receives the measurement results and transform them to the final results. 						
					</t>
					<t> A hybrid universal BQC is proposed in <xref target="XZhang"/>, where the server performs both quantum circuits like <xref target="Childs"/> and quantum 
						measurements like <xref target="Broadbent"/> to reduce the number of required entangled states in <xref target="Broadbent"/>. Also, the client is much simpler than 
						the client in <xref target="Childs"/>. This hybrid BQC is a combination of circuit-based BQC model and measurement-based BQC model.
					</t>
					<t> It will be ideal if the client in BQC is a purely classical client, which only needs to interact with the server using classical channel and communications. 
						<xref target="HHuang"/> demonstrates such an approach, where a classical client leverages two entangled servers to perform BQC, with the assumption that 
						both servers can not communicate with each other; otherwise, the blindness or privacy of the client can not be guaranteed. The scenario as demonstrated 
						in <xref target="HHuang"/> is essentially an example of BQC with multiple servers. 
					</t> 
					<t> How to verify that the server will perform what the client requests or expects is an important issue in many BQC protocols, referred to as verifiable BQC.
						<xref target="Fitzsimons"/> discusses this issue and compares it in various BQC protocols. 
					</t>
					<t> Measurement-based quantum computation is out of the scope of this document. <xref target="Jozsa"/> provides a good introduction of 
						measurement-based quantum computation. 					
					</t>
					
			   </list>
			</t>   				
			
			<t> In <xref target="fig:bqcom" />, the Quantum Internet contains quantum channels and quantum repeaters/routers for long-distance qubits transmission 
			<xref target="I-D.irtf-qirg-principles" />.</t>
			
			<t>
				<?rfc needLines="16" ?>
				<figure anchor="fig:bqcom" title="Secure Quantum Computing with Privacy Preservation">
				<artwork align="center">
  <![CDATA[

+----------------+     /--------\     +----------------+         
|                |--->( Quantum  )--->|                |
|                |    ( Internet )    |   Remote       |
|   Terminal     |     \--------/     |   Computation  |
|   Node         |                    |   Node         |
|  (e.g., Home   |     /--------\     |   (e.g., QC    |
|   Gateway)     |    ( Classical)    |   in Cloud)    |                            
|                |<-->( Internet )<-->|                |
+----------------+     \--------/     +----------------+                            
   ]]>                  
				</artwork>
				</figure>
			</t>
			
		</section>	 
		
		<section anchor="sec:usecase3" title="Distributed Quantum Computing">
			
			<t>There can be two types of distributed quantum computing <xref target="Denchev" />:					
				<list style="numbers">
					<t>Leverage quantum mechanics to enhance classical distributed computing problems. For example, entangled quantum states can be 
					exploited to improve leader election in classical distributed computing, by simply measuring the entangled quantum states at each
					party (e.g., a node or a device) without introducing any classical communications among distributed parties <xref target="Pal" />. Normally, pre-shared entanglement needs first be 
					established among distributed parties, followed by LOCC operations at each party. And it generally does not need to transmit qubits
					among distributed parties. 
					</t>
					<t>Distribute quantum computing functions to distributed quantum computers. A quantum computing task or function (e.g., quantum
					gates) is split and distributed to multiple physically separate quantum computers. And it may or may not need to transmit 
					qubits (either inputs or outputs) among those distributed quantum computers. Pre-shared entangled states may be needed to transmit quantum 
					states among distributed quantum computers without using quantum communications, similar to quantum teleportation. 
					For example, <xref target="Yimsiriwattana" /> has proved that a CNOT gate can be realized jointly by and 
					distributed to multiple quantum computers. The rest of this section focuses on this type of distributed quantum computing.  					
					</t>
				</list>
			</t>
			
			<t>
			As a scenario for the second type of distributed quantum computing, Noisy Intermediate-Scale Quantum (NISQ) computers distributed in
			different locations are available for sharing. According to the definition in <xref target="Preskill" />, a NISQ computer
			can only realize a small number of qubits and has limited quantum error correction. 		
			In order to gain higher computation power before fully-fledged quantum computers become available,
			NISQ computers can be connected via classic and quantum channels. This scenario is referred to as distributed quantum 
			computing <xref target="Caleffi"/> <xref target="Cacciapuoti01"/> <xref target="Cacciapuoti02"/>. This use case reflects 
			the vastly increased computing power which quantum computers as a part of the Quantum Internet can bring, in contrast to classical
			computers in the Classical Internet, in the context of distributed quantum computing ecosystem <xref target="Cuomo"/>. According to 
			<xref target="Cuomo"/>, quantum teleportation enables a new communication paradigm, referred to as teledata <xref target="VanMeter01"/>, which moves quantum states
			among qubits to distributed quantum computers. In addition, distributed quantum computation also needs the capability of remotely performing
			quantum computation on qubits on distributed quantum computers, which can be enabled by the technique called telegate <xref target="VanMeter02"/>. 
			</t>
			
			<t>As an example, scientists can leverage these connected NISQ computer to solve highly complex scientific computation
			problems such as analysis of chemical interactions for medical drug development <xref target="Cao"/> (see <xref target="fig:dqcom" />). In this case,
			qubits will be transmitted among connected quantum
			computers via quantum channels, while classic control messages will be transmitted among them via classical channels
			for coordination and control purpose. Another example of distributed quantum computing is secure Multi-Party Quantum Computation (MPQC) <xref target="Crepeau"/>,
			which can be regarded as a quantum version of classical secure Multi-Party Computing (MPC). In secure MPQC, multiple participants jointly 
			perform quantum computation on a set of input quantum states, which are prepared and provided by different participants. One of primary aims of secure 
			MPQC is to guarantee that each participant will not know input quantum states provided by other participants. Secure MPQC relies on verifiable 
			quantum secret sharing <xref target="Lipinska" />.
			</t>
			
			<t>
			For the example shown in <xref target="fig:dqcom"/>, qubits from one NISQ computer to another NISQ computer are very sensitive and should not be lost. For this purpose, quantum teleportation can be 
			leveraged to teleport sensitive data qubits from one quantum computer A to another quantum computer B. 
			Note that <xref target="fig:dqcom" /> does not cover measurement-based distributed quantum computing, where quantum teleportation may not be required. 
			When quantum teleportation is employed, the following steps happen between A and B. In fact, LOCC <xref target="Chitambar"/> operations are conducted at the quantum 
			computer A and B in order to achieve quantum teleportation as illustrated in <xref target="fig:dqcom" />. 
				<list style="numbers">
					<t> The quantum computer A locally generates some sensitive data qubits to be teleported to the quantum computer B. </t>
					<t>	A shared entanglement is established between the quantum computer A and the quantum computer B (i.e., there are two entangled qubits: |q1> at A and |q2> at B).
						For example, the quantum computer A can generate two entangled qubits (i.e., |q1> and |q2>) and sends |q2> to the quantum computer B via quantum communications. </t>
					<t>	Then, the quantum computer A performs a Bell measurement of the entangled qubit |q1> and the sensitive data qubit.</t>
					<t>	The result from this Bell measurement will be encoded in two classical bits, which will be physically transmitted via a classical channel to the quantum computer B.</t>
					<t> Based on the received two classical bits, the quantum computer B modifies the state of the entangled qubit |q2> in the way to generate a new qubit identical to 
					    the sensitive data qubit at the quantum computer A.</t>
			    </list>
			</t>
			
			<t> In <xref target="fig:dqcom" />, the Quantum Internet contains quantum channels and quantum repeaters/routers <xref target="I-D.irtf-qirg-principles" />. 
			    This use case needs to support entanglement generation and entanglement distribution (or quantum connection) 
				setup <xref target="I-D.van-meter-qirg-quantum-connection-setup"/> in order to support quantum teleportation.  
			</t>
			
			<t>
				<?rfc needLines="16" ?>
				<figure anchor="fig:dqcom" title="Distributed Quantum Computing">
				<artwork align="center">
  <![CDATA[
    
                  +-----------------+
                  |     End-User    |
                  |(e.g., Scientist)|
                  +-----------------+
                           ^
                           |User Interface (e.g. GUI)
                           |
        +------------------+-------------------+
        |                                      |
        |                                      |
        V                                      V              
+----------------+     /--------\     +----------------+         
|                |--->( Quantum  )--->|                |
|                |    ( Internet )    |                |
|   Quantum      |     \--------/     |   Quantum      |
|   Computer A   |                    |   Computer B   |
| (e.g., Site #1)|     /--------\     | (e.g., Site #2)|
|                |    ( Classical)    |                |                            
|                |<-->( Internet )<-->|                |
+----------------+     \--------/     +----------------+                            
   ]]>                  
				</artwork>
				</figure>
			</t>
	
		</section>
		
    </section>
	
	
	<section anchor="sec:generalrequirements" title="General Requirements">
	
	 <section anchor="sec:reqbackground" title="Background">
		<t>Quantum technologies are steadily evolving and improving. Therefore, it is hard to predict the timeline and future milestones
		of quantum technologies as pointed out in <xref target="Grumbling"/> for quantum computing. Currently, a NISQ computer can achieve
		fifty to hundreds of qubits with some given error rate. In fact, the error rates of two-qubit quantum gates have decreased nearly
		in half every 1.5 years (for trapped ion gates) to 2 years (for superconducting gates).  The error rate also increases as the
		number of qubits increases. For example, a current 20-physical-qubit machine has a total error rate which is close to the total error rate
		of a 7 year old two-qubit machine <xref target="Grumbling"/>.			
		</t>
		
		<t>On the network level, six stages of Quantum Internet development are described in <xref target="Wehner"/> as follows:		
			<list style="numbers">
				<t>Trusted repeater networks (Stage-1)</t>
				<t>Prepare and measure networks (Stage-2)</t>
				<t>Entanglement distribution networks (Stage-3)</t>
				<t>Quantum memory networks (Stage-4)</t>
				<t>Fault-tolerant few qubit networks (Stage-5)</t>
				<t>Quantum computing networks (Stage-6)</t>		
			</list>
		</t>
		
		
		<t>The first stage are simple trusted repeater networks, while the final stage are quantum computing networks where the full-blown
		Quantum Internet will be achieved. Each intermediate stage brings with it new functionality, new applications,
		and new characteristics.  <xref target="fig:appsinstages"/> illustrates Quantum Internet use cases as described in this document mapped to
		the Quantum Internet stages described in <xref target="Wehner"/>.  For example, secure communication setup can be supported in
		Stage-1, Stage-2, or Stage-3, but with different QKD solutions.  More specifically:</t>
		
		<t>In Stage-1, basic QKD is possible and can be leveraged to support secure communication setup but trusted nodes are
		required to provide end-to-end security. The primary requirement is trusted nodes. </t>
		
		<t>In Stage-2, end-to-end security without relying on trusted nodes is possible to support secure communication setup too. The
		primary requirement is prepare-and-measure capability.</t>
		
		<t>In Stage-3, end-to-end security can be enabled based on quantum repeaters and entanglement distribution, to support the
		same secure communication setup application. The primary requirement is entanglement distribution to enable long-distance QKD. </t>
				
		<t>In Stage-4, Secure quantum computing with privacy-preservation can be enabled since it needs quantum memory
		for multiple rounds of quantum computation.</t>
		
		<t>Finally, in Stage-6, distributed quantum computing relying on more qubits can be supported.</t>
		

<t>
				<?rfc needLines="16" ?>
				<figure anchor="fig:appsinstages" title="Example Use Cases in Different Quantum Internet Stages">
				<artwork align="center">
  <![CDATA[    
+---------+----------------------------+------------------------+
| Quantum |     Example Quantum        |                        |
| Internet|      Internet Use          |   Characteristic       |
| Stage   |         Cases              |                        |
+---------+----------------------------+------------------------+
| Stage-1 | Secure comm setup 	       |  Trusted nodes         |
|         | using basic QKD            |                        | 
|---------------------------------------------------------------|
| Stage-2 | Secure comm setup          |  Prepare-and-measure   |
|         | using the QKD with         |       capability       |
|         | end-to-end security        |                        |
|---------------------------------------------------------------|
| Stage-3 | Secure comm setup          |  Entanglement          |
|         | using entanglement-enabled |  distribution          |
|         | QKD                        |                        |          
|---------------------------------------------------------------|
| Stage-4 | Secure/blind quantum       |  Quantum memory        |
|         | computing                  |                        |
|---------------------------------------------------------------|
| Stage-5 | Higher-Accuracy Clock      |  Fault tolerance       |
|         | synchronization            |                        |
|---------------------------------------------------------------|
| Stage-6 | Distributed quantum        |  More qubits           |
|         | computing                  |                        |
+---------------------------------------------------------------+
   ]]>                  
				</artwork>
				</figure>
</t>

    </section>
		
	<section anchor="sec:requirements" title="Requirements">
		<t>Some general and functional requirements on the Quantum Internet from the networking perspective, based on the above
		applications and use cases, are identified as follows:
			<list style="numbers">										
				<t> Methods for facilitating quantum applications to interact efficiently with entanglement qubits are necessary in
				order for them to trigger distribution of designated entangled qubits to potentially any other quantum node residing
				in the Quantum Internet.  To accomplish this specific operations must be performed on entangled qubits 
				(e.g., entanglement swapping, entanglement distillation).  Quantum nodes may be quantum end-nodes, 
				quantum repeaters/routers, and/or quantum computers.</t>
				
				<t> Quantum repeaters/routers should support robust and efficient entanglement distribution in order to extend and establish 
				entanglement connection between two quantum nodes. For achieving this, it is required to first generate an entangled pair on 
				each hop of the path between these two nodes. </t>
				
				<t> Quantum end-nodes must send additional information on classical channels to aid in transmission of qubits across
				quantum repeaters/receivers.  This is because qubits are transmitted individually and do not have any associated packet overhead
				which can help in transmission of the qubit.  Any extra information to aid in routing, identification, etc., of the qubit(s)
				must be sent via classical channels.</t>	
				
				<t> Methods for managing and controlling the Quantum Internet including quantum nodes and their quantum resources are necessary. 
				The resources of a quantum node may include quantum memory, quantum channels, qubits, established quantum connections, etc. Such 
				management methods can be used to monitor network status of the Quantum Internet, diagnose and identify potential issues 
				(e.g. quantum connections), and configure quantum nodes with new actions and/or policies (e.g. to perform a new entanglement 
				swapping operation). New management information model for the Quantum Internet may need to be developed.  
			
				</t>
			</list>	
		</t> 
				
	  </section>
	  
	</section>	
	
	
    <section anchor="sec:conclusion" title="Conclusion">


	  <t>
	  This document provides an overview of some expected applications for the Quantum Internet, and then details selected use cases. 
	  The applications are first grouped by their usage which is a natural and easy to understand classification scheme.
	  The applications are also classified as either control plane or data plane functionality as typical for the Classical Internet.
	  This set of applications may, of course, naturally expand over time as the Quantum Internet matures.  Finally, some
	  general requirements for the Quantum Internet are also provided. 
		
	  </t>
	  
	 <t>
	  This document can also serve as an introductory text to readers interested in learning about the practical uses
	  of the Quantum Internet.  Finally, it is hoped that this document will help guide further research and development
	  of the Quantum Internet functionality required to implement the applications and uses cases described herein.
	  </t>

    </section>
	
	
	
	<section anchor="IANA" title="IANA Considerations">

      <t>This document requests no IANA actions.
      </t>

    </section>



    <section anchor="sec:security" title="Security Considerations">

	   <t> This document does not define an architecture nor a specific protocol for the Quantum Internet.  It focuses instead on 
	   detailing use cases, requirements, and describing typical Quantum Internet applications. However, some salient observations
	   can be made regarding security of the Quantum Internet as follows.
     </t>

      <t>
         It has been identified in <xref target="NISTIR8240" /> that once large-scale quantum computing becomes
		 reality that it will be able to break many of the public-key (i.e., asymmetric) cryptosystems 
		 currently in use.  This is because of the increase in computing ability with quantum computers for certain classes
		 of problems (e.g., prime factorization, optimizations).  This would negatively affect many of the security
		 mechanisms currently in use on the Classical Internet which are based on public-key (Diffie-Hellman) encryption.
		 This has given strong impetus for starting development of new cryptographic systems that are secure against
		 quantum computing attacks <xref target="NISTIR8240" />.
     </t>
	 
	 
	  <t>
         Interestingly, development of the Quantum Internet will also mitigate the threats posed by quantum computing attacks against
		 Diffie-Hellman based public-key cryptosystems. Specifically, the secure communication setup feature of the Quantum Internet as
		 described in <xref target="sec:usecase1" /> will be strongly resistant to both classical and quantum computing attacks 
		 against Diffie-Hellman based public-key cryptosystems.
     </t>
	 
	 
	 <t>A key additional threat consideration for the Quantum Internet is pointed to by <xref target="RFC7258" />, 
		which warns of the dangers of pervasive monitoring as a widespread attack on privacy.  Pervasive monitoring
		is defined as a widespread, and usually covert, surveillance through intrusive gathering of application content
		or protocol metadata such as headers.  This can be accomplished through active or passive wiretaps, traffic
		analysis, or subverting the cryptographic keys used to secure communications.
     </t>

	 
	 <t>The secure communication setup feature of the Quantum Internet as described in <xref target="sec:usecase1" />
	    will be strongly resistant to pervasive monitoring based on directly attacking (Diffie-Hellman) encryption keys.  
		Also, <xref target="sec:usecase2" /> describes a method to perform remote quantum computing while preserving the
		privacy of the source data.    Finally, the intrinsic property of qubits to decohere if they are observed, albeit
		covertly, will theoretically allow detection of unwanted monitoring in some future solutions.
     </t>



    </section>



    <section anchor="Acknowledgments" title="Acknowledgments">

      <t>The authors want to thank Mathias Van Den Bossche, Xavier de Foy, Patrick Gelard, Álvaro Gómez Iñesta, Wojciech Kozlowski, John Mattsson, 
	  Rodney Van Meter, Joey Salazar, and Joseph Touch, and the rest of the QIRG community as a whole for their very useful reviews
	  and comments to the document.</t>
	  
    </section>


  </middle>





  
  <back>
  
    <references title="Informative References">
	  
	  &rfc2119;
	  &rfc7258;
      &I-D.irtf-qirg-principles;
      &I-D.dahlberg-ll-quantum;
      &I-D.van-meter-qirg-quantum-connection-setup;
 
 

 
      <reference anchor="Castelvecchi" target="https://www.nature.com/articles/d41586-018-01835-3">
       <front>
         <title>The Quantum Internet has arrived (and it hasn't)</title>

         <author initials="D" surname="Castelvecchi" />

         <date year="2018" />
       </front>
       <seriesInfo name="Nature" value="554, 289-292" />
     </reference>
 
 
      <reference anchor="Wehner" target="http://science.sciencemag.org/content/362/6412/eaam9288.full">
       <front>
         <title>Quantum internet: A vision for the road ahead </title>
         <author initials="S." surname="Wehner">
           <organization></organization>
         </author>
         <author initials="D." surname="Elkouss">
           <organization></organization>
         </author>
         <author initials="R." surname="Hanson">
           <organization></organization>
         </author>
         <date year="2018" />
       </front>
       <seriesInfo name="Science" value="362" />
     </reference>


      <reference anchor="NISTIR8240" target="https://nvlpubs.nist.gov/nistpubs/ir/2019/NIST.IR.8240.pdf">
       <front>
         <title>Status Report on the First Round of the NIST Post-Quantum Cryptography Standardization Process</title>
         <author initials="G." surname="Alagic">
           <organization></organization>
         </author>
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
         <date year="2019" />
       </front>
       <seriesInfo name="NISTIR" value="8240" />
     </reference>


      <reference anchor="Komar" target="https://arxiv.org/pdf/1310.6045.pdf">
       <front>
         <title>A Quantum Network of Clocks</title>
         <author initials="P." surname="Komar">
           <organization></organization>
         </author>
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
         <date year="2013" />
       </front>
     </reference>
	 
	  <reference anchor="Fitzi" target="https://arxiv.org/pdf/quant-ph/0107127.pdf">
       <front>
         <title>A Quantum Solution to the Byzantine Agreement Problem</title>
         <author initials="M." surname="Fitzi">
           <organization></organization>
         </author>
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
         <date year="2001" />
       </front>
     </reference>
	 
	  <reference anchor="Renner" target="https://arxiv.org/pdf/quant-ph/0512258.pdf">
       <front>
         <title>Security of Quantum Key Distribution</title>
         <author initials="R." surname="Renner">
           <organization></organization>
         </author>
         <date year="2006" />
       </front>
     </reference>
	 
	 <!--
	 <reference anchor="Unruh" target="https://link.springer.com/content/pdf/10.1007/978-3-662-44381-1_1.pdf">
       <front>
         <title>Quantum Position Verification in the Random Oracle Model</title>
         <author initials="D." surname="Unruh">
           <organization></organization>
         </author>
         <date year="2014" />
       </front>
     </reference>	
	 -->
	 
	 <reference anchor="Fitzsimons" target="https://www.nature.com/articles/s41534-017-0025-3.pdf">
       <front>
         <title>Private Quantum Computation: An Introduction to Blind Quantum Computing and Related Protocols</title>
         <author initials="J. F." surname="Fitzsimons">
           <organization></organization>
         </author>
         <date year="2017"/>
       </front>
     </reference>	
	 
	  <reference anchor="BB84" target="http://researcher.watson.ibm.com/researcher/files/us-bennetc/BB84highest.pdf">
       <front>
         <title>Quantum Cryptography: Public Key Distribution and Coin Tossing</title>
         <author initials="C. H." surname="Bennett">
           <organization></organization>
         </author>
		 <author initials="G." surname="Brassard">
           <organization></organization>
         </author>
         <date year="1984"/>
       </front>
     </reference>	
	
	 <reference anchor="Preskill" target="https://arxiv.org/pdf/1801.00862">
       <front>
         <title>Quantum Computing in the NISQ Era and Beyond</title>
         <author initials="J." surname="Preskill">
           <organization></organization>
         </author>
		 <date year="2018"/>
       </front>
     </reference>
	 
	 <reference anchor="QZhang" target="https://doi.org/10.1364/OE.26.024260">
       <front>
         <title>Large Scale Quantum Key Distribution: Challenges and Solutions</title>
         <author initials="Q." surname="Zhang">
           <organization></organization>
         </author>
		 <author initials="F." surname="Hu">
           <organization></organization>
         </author>
		 <author initials="Y." surname="Chen">
           <organization></organization>
         </author>
		 <author initials="C." surname="Peng">
           <organization></organization>
         </author>
		 <author initials="J." surname="Pan">
           <organization></organization>
         </author>
		 <date year="2018"/>
       </front>
	   <seriesInfo name="Optical Express," value="OSA" />
     </reference>
	 
	 <reference anchor="Treiber" target="https://doi.org/10.1364/OE.26.024260">
       <front>
         <title>A Fully Automated Entanglement-based Quantum Cyptography System for Telecom Fiber Networks</title>
         <author initials="A." surname="Treiber">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>		 
		 <date year="2009"/>
       </front>
	   <seriesInfo name="New Journal of Physics," value="11, 045013" />
     </reference>
	 
	  <reference anchor="ETSI-QKD-Interfaces" target="https://www.etsi.org/deliver/etsi_gr/QKD/001_099/003/02.01.01_60/gr_QKD003v020101p.pdf">
       <front>
         <title>Quantum Key Distribution (QKD); Components and Internal Interfaces </title>
		 <author initials="" surname="ETSI GR QKD 003 V2.1.1">
           <organization></organization>
         </author>	
         <date year="2018" />
       </front>      
     </reference>
	 
	 <reference anchor="ETSI-QKD-UseCases" target="https://www.etsi.org/deliver/etsi_gs/qkd/001_099/002/01.01.01_60/gs_qkd002v010101p.pdf">
       <front>
         <title>Quantum Key Distribution (QKD); Use Cases </title>
		 <author initials="" surname="ETSI GR QKD 002 V1.1.1">
           <organization></organization>
         </author>	
         <date year="2010" />
       </front>      
     </reference>
	 
	 <reference anchor="PZhang" target="https://arxiv.org/abs/1912.09642">
       <front>
         <title>Integrated Relay Server for Measurement-Device-Independent Quantum Key Distribution</title>
         <author initials="P." surname="Zhang">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2019"/>
       </front>
     </reference>
	 
	 <reference anchor="Qin" target="https://www.itu.int/en/ITU-T/Workshops-and-Seminars/2019060507/Documents/Hao_Qin_Presentation.pdf">
       <front>
         <title>Towards Large-Scale Quantum Key Distribution Network and Its Applications</title>
         <author initials="H." surname="Qin">
           <organization></organization>
         </author>
		 <date year="2019"/>
       </front>
     </reference>
	 
	 <reference anchor="Cacciapuoti01" target="https://ieeexplore.ieee.org/document/8910635">
       <front>
         <title>Quantum Internet: Networking Challenges in Distributed Quantum Computing</title>
         <author initials="A.S." surname="Cacciapuoti">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2020"/>
       </front>
	   <seriesInfo name="IEEE Network," value="January 2020" />
     </reference>
	 
	 <reference anchor="Cacciapuoti02" target="https://arxiv.org/abs/1907.06197">
       <front>
         <title>When Entanglement meets Classical Communications: Quantum Teleportation for the Quantum Internet</title>
         <author initials="A.S." surname="Cacciapuoti">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2019"/>
       </front>	   
     </reference>
	 
	 <reference anchor="Caleffi" target="https://dl.acm.org/doi/10.1145/3233188.3233224">
       <front>
         <title>Quantum internet: From Communication to Distributed Computing!</title>
         <author initials="M." surname="Caleffi">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2018"/>
       </front>	   
	   <seriesInfo name="NANOCOM," value="ACM" />
     </reference>
	 
	  <reference anchor="Chitambar" target="https://link.springer.com/article/10.1007/s00220-014-1953-9">
       <front>
         <title>Everything You Always Wanted to Know About LOCC (But Were Afraid to Ask)</title>
         <author initials="E." surname="Chitambar">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2014"/>
       </front>	   
	   <seriesInfo name="Communications in Mathematical Physics," value="Springer" />
     </reference>
	 
	 <reference anchor="Grumbling" target="https://doi.org/10.17226/25196">
       <front>
         <title>Quantum Computing: Progress and Prospects</title>
         <author initials="E." surname="Grumbling">
           <organization></organization>
         </author>
		 <author initials="M." surname="Horowitz">
           <organization></organization>
         </author>
		 <date year="2019"/>
       </front>	   
	   <seriesInfo name="National Academies of Sciences, Engineering, and Medicine," value="The National Academies Press" />
     </reference>
	 
	 <reference anchor="Proctor" target="https://journals.aps.org/prl/abstract/10.1103/PhysRevLett.120.080501">
       <front>
         <title>Multiparameter Estimation in Networked Quantum Sensors</title>
         <author initials="T.J." surname="Proctor">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2018"/>
       </front>	   
	   <seriesInfo name="Physical Review Letters," value="American Physical Society" />
     </reference>
	
	 <reference anchor="Childs" target="https://arxiv.org/pdf/quant-ph/0111046.pdf">
       <front>
         <title>Secure Assisted Quantum Computation</title>
         <author initials="A. M." surname="Childs">
           <organization></organization>
         </author>		          
		 <date year="2005"/>
       </front>	   	   
     </reference>	

	 <reference anchor="Broadbent" target="https://arxiv.org/pdf/0807.4154.pdf">
       <front>
         <title>Universal Blind Quantum Computation</title>
         <author initials="A." surname="Broadbent">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2009"/>
       </front>
       <seriesInfo name="50th Annual Symposium on Foundations of Computer Science," value="IEEE" />	   
     </reference>	

	 <reference anchor="XZhang" target="https://www.sciencedirect.com/science/article/abs/pii/S002002551930458X">
       <front>
         <title>A Hybrid Universal Blind Quantum Computation</title>
         <author initials="X." surname="Zhang">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2009"/>
       </front>
       <seriesInfo name="Information Sciences," value="Elsevier" />	   
     </reference>
	 
	 <reference anchor="HHuang" target="https://arxiv.org/pdf/1707.00400.pdf">
       <front>
         <title>Experimental Blind Quantum Computing for a Classical Client</title>
         <author initials="H." surname="Huang">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2017"/>
       </front>          
     </reference>
	 
	  <reference anchor="Jozsa" target="https://arxiv.org/pdf/quant-ph/0508124.pdf">
       <front>
         <title>An Introduction to Measurement based Quantum Computation</title>
         <author initials="R." surname="Josza">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2005"/>
       </front>          
     </reference>
	 
	 <reference anchor="Cao" target="https://doi.org/10.1147/JRD.2018.2888987">
       <front>
         <title>Potential of Quantum Computing for Drug Discovery</title>
         <author initials="Y." surname="Cao">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2018"/>
       </front>          
	   <seriesInfo name="Journal of Research and Development," value="IBM" />	
     </reference>
	 
	 <reference anchor="Crepeau" target="https://doi.org/10.1145/509907.510000">
       <front>
         <title>Secure Multi-party Quantum Computation</title>
         <author initials="C." surname="Crepeau">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2002"/>
       </front>          
	   <seriesInfo name="34th Symposium on Theory of Computing (STOC)," value="ACM" />	
     </reference> 
	 
	 <reference anchor="Lipinska" target="https://doi.org/10.1103/PhysRevA.101.032332">
       <front>
         <title>Verifiable Hybrid Secret Sharing with Few Qubits</title>
         <author initials="V." surname="Lipinska">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2020"/>
       </front>          
	   <seriesInfo name="Physical Review A," value="American Physical Society" />	
     </reference> 
	 
	 <reference anchor="Cuomo" target="http://dx.doi.org/10.1049/iet-qtc.2020.0002">
       <front>
         <title>Towards a Distributed Quantum Computing Ecosystem</title>
         <author initials="D." surname="Cuomo">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2020"/>
       </front>          
	   <seriesInfo name="Quantum Communication," value="IET" />	
     </reference> 
	 
	 <reference anchor="VanMeter01" target="https://doi.org/10.1109/ISCA.2006.19">
       <front>
         <title>Distributed Arithmetic on a Quantum Multicomputer</title>
         <author initials="R." surname="Van Meter">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2006"/>
       </front>          
	   <seriesInfo name="33rd International Symposium on Computer Architecture (ISCA)" value="IEEE" />	
     </reference> 
	 
	 <reference anchor="VanMeter02" target="https://arxiv.org/pdf/quant-ph/0607065.pdf">
       <front>
         <title>Architecture of a Quantum Multicompuer Optimized for Shor's Factoring Algorithm</title>
         <author initials="R." surname="Van Meter">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2006"/>
       </front>          	   
     </reference>
	 
	 <reference anchor="Elkouss" target="https://arxiv.org/pdf/1007.1616.pdf">
       <front>
         <title>Information Reconciliation for Quantum Key Distribution</title>
         <author initials="D." surname="Elkouss">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2011"/>
       </front>          	   
     </reference>	  

	 <reference anchor="BTang" target="https://doi.org/10.1038/s41598-019-50290-1">
       <front>
         <title>High-speed and Large-scale Privacy Amplification Scheme for Quantum Key Distribution</title>
         <author initials="B." surname="Tang">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2019"/>
       </front>   
	   <seriesInfo name="Scientific Reports," value="Nature Research" />	   
     </reference>
		 
	 <reference anchor="Denchev" target="https://doi.org/10.1145/1412700.1412718">
       <front>
         <title>Distributed Quantum Computing: A New Frontier in Distributed Systems or Science Fiction?</title>
         <author initials="V.S." surname="Denchev">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2018"/>
       </front>   
	   <seriesInfo name="SIGACT News" value="ACM" />	   
     </reference>
	 
	 <reference anchor="Pal" target="https://arxiv.org/pdf/quant-ph/0306195.pdf">
       <front>
         <title>Multi-partite Quantum Entanglement versus Randomization: Fair and Unbiased Leader Election in Networks</title>
         <author initials="S.P." surname="Pal">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2003"/>
       </front>   	   
     </reference>	 
	 
	 <reference anchor="Yimsiriwattana" target="https://arxiv.org/pdf/quant-ph/0402148.pdf">
       <front>
         <title>Generalized GHZ States and Distributed Quantum Computing</title>
         <author initials="A." surname="Yimsiriwattana">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2004"/>
       </front>   	   	   
     </reference>

	 <reference anchor="Guo" target="https://www.nature.com/articles/s41567-019-0743-x">
       <front>
         <title>Distributed Quantum Sensing in a Continuous-Variable Entangled Network</title>
         <author initials="X." surname="Guo">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2020"/>
       </front>          
	   <seriesInfo name="Nature Physics," value="Nature" />	
      </reference> 	
	 
	 <reference anchor="Zhao" target="https://iopscience.iop.org/article/10.1088/1742-6596/1087/4/042028">
       <front>
         <title>Development of Quantum Key Distribution and Attacks against it</title>
         <author initials="Y." surname="Zhao">
           <organization></organization>
         </author>		 
		 <date year="2018"/>
       </front>          
	   <seriesInfo name="Journal of Physics," value="J. Phys" />	
      </reference> 	
	  
	  <reference anchor="Kiktenko" target="https://arxiv.org/pdf/1903.10237.pdf">
       <front>
         <title>Lightweight Authentication for Quantum Key Distribution</title>
         <author initials="E.O." surname="Kiktenko">
           <organization></organization>
         </author>		 
         <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2020"/>
       </front>   	   	   
     </reference> 
	 
    </references>		
	
  </back>
  
</rfc>