﻿<?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-02">
  <?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="2020" month="September" day="18"/>

    <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.  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.
      </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.  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 Digital Subscriber Lines (DSLs), fiber optics, coax cable and wireless that include Bluetooth, WiFi, 
		cellular (e.g., 3G, 4G, 5G), and satellite, etc. Bits are transmitted across the Classical Internet in packets.
      </t>
      <t>
        Research and experimentation have picked up over the last few years for developing a Quantum Internet  <xref target="Wehner" />.
		It is anticipated that the Quantum Internet will provide intrinsic benefits such as better end-to-end and network security.
		The Quantum Internet will also have end-nodes, termed quantum end-nodes. Quantum end-nodes 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 optics.  
		Photonic connections are particularly useful because light (photons) is very suitable for physically encoding qubits. 
		Unlike the Classical Internet, qubits (and not classical bits or packets) are expected to be transmitted across the Quantum 
		Internet due to the underlying physics.  The Quantum Internet will operate according to unique
		 physical principles such as quantum superposition, entanglement and teleportation <xref target="I-D.irtf-qirg-principles" />.
	  </t>

	  <t>
		The Quantum Internet is not anticipated to replace the Classical Internet. For instance, Local Operations and Classical Communication (LOCC) 
		tasks <xref target="Chitambar"/> rely on classical communications. Instead 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>



    </section>


	<section anchor="convention" title="Conventions used in this document">
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
		and "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119" />.
        </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 here for clarity:
      </t> 


		<t>
          <list style="symbols">
		 	<t>Bit - Binary Digit (i.e., fundamental unit of information in a classical computer).</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>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: 1) local quantum operations (e.g., quantum measurement) are performed 
			at one quantum node A; 2) the quantum operation result is sent to another quantum node B via classical communications; 3) the quantum node B may also perform 
			some local quantum operations dependent on the received operation result from the quantum node A. For example, LOCC can be used to transform entangled 
			states into other entangled states.</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 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>OSI - Open System Interconnect</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.</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 Subnetwork (i.e, is a quantum end-node), it must be able to
			generate/transmit and/or 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 Subnetwork	- A new type of Subnetwork 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 Subnetwork will use both quantum channels, and classical channels provided 
			by the Classical Internet.</t>
						
			<t>Quantum Internet	- A network of Quantum Subnetworks. The Quantum Internet will 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 a quantum computer).  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 |0> or |1>.  However, the qubit is different than a classic bit in that 
			the qubit is 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 extremely beneficial for a subset of existing and new applications.
			The expected applications using 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.			
			<!--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 also be grouped by the usage that they serve into a tripartite classification.  Specifically,
		applications may be classified according to the following usages:
          <list style="symbols">
			<t>Quantum cryptography applications - Refers to the use of quantum information technology to ensure secure communications (e.g., QKD).</t>
			<t>Quantum sensors applications - Refers to the use of quantum information technology for supporting
			distributed sensors or Internet of Things (IoT) devices (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 is a useful classification scheme as it can be easily understood by both a technical and non-technical audience.  
			Following are some more details.</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" />.</t>
				
					<t>Fast Byzantine negotiation - Refers to a Quantum Subnetwork based method for fast agreement in Byzantine negotiations <xref target="Fitzi" />.
					This can be used for the popular financial blockchain feature as well as other distributed computing features which use
					Byzantine negotiations.</t>	
				</list>	
				</t>
			</section>	
			
			<section anchor="sec:typeofquantumsensor" title="Quantum Sensor Applications">
				<t> Example of quantum sensor applications include network clock synchronization, radio frequency measurement, etc. These applications mainly
					leveage a network of entangled quantun sensors (i.e. quantum sensor networks) for high-precision multi-parameter estimation <xref target="Proctor" /> <xref target="Zhuang" />. 					
				<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" />.</t>
					<t>Radio frequency sensing - Refers to leverage connected quantum sensors to measure a broad range of radio frequencies with arbitrary frequency resolution. <xref target="Zhuang" /><xref target="Fan" /></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. 
				<list style="numbers">			
					<t>Distributed quantum computing - Refers to a collection of remote small capacity quantum computers (i.e., each supporting a few 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 encoding (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 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 Subnetwork (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. 
			But looking at 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. 			
			</t>

<t>
				<?rfc needLines="16" ?>
				<figure anchor="fig:controldataplane" title="Examples of Control vs Data Plane Classification">
				<artwork align="center">
  <![CDATA[    
+----------+-----------+----------------+----------------------+
|          |           |   Standalone   |                      |
|          | Classical |    Quantum     |       Quantum        |
|          | Internet  |   Subnetwork   |       Internet       |
|          | Examples  |    Examples    |       Examples       |
+----------+-----------+----------------+----------------------+
|  Control | ICMP,     | Signalling for | QKD-based secure     |
|  Plane   | DNS       | controlling    | communication        | 
|          |           | entanglement   | setup; Quantum ping  |
|          |           | distribution   |                      |
---------------------------------------------------------------|
|  Data    | Web       | Entanglement   | Video conference     |
|  Plane   | Browsing  | distribution   | using QKD-based      |
|          |           |                | secure communication |
|          |           |                | setup                |
+--------------------------------------------------------------+
   ]]>                  
				</artwork>
				</figure>
</t>					
			
		</section>	    
	  
	  
		<!--section anchor="sec:exceptions" title="Exceptions">
	  
		<t>It is also important to understand which applications will not be supported on the Quantum Internet.  Many
		existing applications have no clear advantage if transmitted over the Quantum Internet and so are not expected
		to be migrated there. Key examples are Voice over IP (VoIP) calls, streaming video sessions, and web browsing sessions.
		These applications usually have a real-time human end-user and/or involve high bandwidth content transmission.  These
		applications are better suited to remain on the Classical Internet.</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 send a classic secret key to 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" />. QKD
			can securely establish a secret key between two quantum nodes, without physically transmitting it through
			the network and thus achieving the required security.  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 (e.g. Alice) transforms the secret key to qubits. Basically, for each classical bit in the secret key, 
				the source quantum node A randomly selects one quantum computational basis and uses it to prepare/generate a qubit for the classical bit.</t>
				<t> The source quantum node A sends qubits to the destination quantum node B (e.g. Bob) via quantum channel.</t>
				<t> The destination quantum node receives qubits and measures them based on its random quantum basis.</t>				
				<t> The destination node informs the source node of its random quantum basis.</t>
				<t> The source node informs the destination node which random quantum basis is correct.</t>
				<t> Both nodes discard any measurement bit under different quantum basis and store all remaining bits as the secret key.</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 Alice and Bob, are not normally considered "prepare-and-measure" as defined in <xref target="Wehner"/>; other entanglement-based schemes, where entanglement is 
					 generated within Alice 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 Alice before being sent to Bob 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="ZhangPeiyu"/>. 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="QinHao"/>. 
				     One or multiple trusted QKD relays <xref target="ZhangQiang"/> 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>
				 <t> In general, there are 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. The end-to-end 
					 security relies on some trusted nodes, which however could be attacked; 2) E2E QKD: In this case, 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, QKD leverages entanglement distribution to achieve the end-to-end security. 
				 </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., Banking |
|  Application) |
+---------------+
      ^
      | 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.</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" />, the client node could be a virtual voice-controlled home assistant device like Amazon's Alexa product.
				The remote computation node could be a quantum computer in the cloud. A resident as an end-user uses voice to control
				the home device. The home device captures voice-based commands from the end-user. Then, the home device interfaces to a home
				quantum terminal node (e.g., a home gateway), which interacts with the remote computation node to perform computation over
				the captured voice-based commands. The home quantum terminal could be either a bare-bone quantum end-node or a full-fledged quantum computer.
			</t>
				
				
			<t>
				In this particular case, there is no privacy concern since the source data (i.e., captured voice-based commands) will not be sent
				to the remote computation node which could be compromised. Protocols <xref target="Fitzsimons" /> for delegated quantum
				computing or blind quantum computation can be leveraged to realize secure delegated computation and guarantee 
				privacy preservation simultaneously. Using delegated quantum computing protocols, the client node does not need send
				the source data but qubits with some measurement instructions to the remote computation node (e.g., a quantum computer).				
			</t>
				
				
			<t>
				After receiving qubits and measurement instructions, the remote computation node performs the following actions: 
				<list style="numbers">
					<t> It first performs certain quantum operations on received qubits and measure them according to received measurement 
					instructions to generate computation results (in classic bits).</t> 
					<t> Then it sends the computation results back to the client node via classical channel.</t> 
					<t> In this process, the source data is not disclosed to the remote computation node and the privacy is preserved.</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[
    
+----------------+
|   End-User     |
|(e.g., Resident)|
+----------------+
        ^
        | User Interface
        | (e.g., voice commands)
        V
+----------------+
|   Home Device  |		
+----------------+
        ^
        | Classic 
        | Channel
        V
+----------------+     /--------\     +----------------+         
|                |--->( Quantum  )--->|                |
|   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>
			In this scenario, 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. 
			</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 (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. Qubits from one NISQ computer to another NISQ computer
			are very sensitive and cannot 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. 
			</t>
			
			<t>
			Specifically, 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).</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 in order to enable quantum teleportation, entanglement distribution or quantum connection 
				setup <xref target="I-D.van-meter-qirg-quantum-connection-setup"/> in order to support long-distance 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-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 (sub)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.</t>
		
		<t>In Stage-2, E2E QKD without relying on trusted nodes is possible to support secure communication setup too and the
		primary requirement is long-distance qubit transmission.</t>
		
		<t>In Stage-3, Advanced E2E QKD can be enabled based on quantum repeater and entanglement distribution to support the
		same secure communication setup application.</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 relaying 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         |
|         | with Basic QKD            |                        | 
|--------------------------------------------------------------|
| Stage-2 | Secure Comm Setup         |  Long-distance qubit   |
|         | with E2E QKD              |  transmission          |
|--------------------------------------------------------------|
| Stage-3 | Secure Comm Setup         |  Entanglement          |
|         | with Advanced E2E QKD     |  distribution          |
|--------------------------------------------------------------|
| 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 neccessary. 
				The resources of a quantum node may include quantum memory, quantum channels, qubits, established quantum connecctions, 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 then 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 persons 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 specific Quantum Internet functionality required to implement the  applications and uses cases described herein.
	  To this end, a few key requirements for the Quantum Internet are specified.
	  </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 useful observations
	   can be made regarding security as follows.
     </t>

      <t>
         It has been clearly identified that once large-scale quantum computing becomes reality it will be able to theoretically
		 break many of the public-key (i.e., asymmetric) cryptosystems currently in use because of the exponential increase of
		 computing power with quantum computing.  This would negatively affect many of the security mechanisms currently in use
		 on the classic Internet.  This has given strong impetus for starting development of new cryptographic systems that are
		 secure against quantum computing attacks <xref target="NISTIR8240" />.
     </t>
	 
	  <t>
         Paradoxically, development of a Quantum Internet will also mitigate the threats posed by quantum computing attacks against
		 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 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>Once again, the secure communication setup feature of the Quantum Internet as described in <xref target="sec:usecase1" />
	    will be strongly resistant to pervasive monitoring.  In addition, <xref target="sec:usecase2" /> provides a method to
		perform remote quantum computing while preserving the privacy of the source data.
     </t>



    </section>



    <section anchor="Acknowledgments" title="Acknowledgments">

      <t>The authors want to thank Mathias Van Den Bossche, Xavier de Foy, Patrick Gelard, Wojciech Kozlowski, Rodney Van Meter, and
	  Joseph Touch 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="ZhangQiang" 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="ZhangPeiyu" 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="QinHao" 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="2019"/>
       </front>
	   <seriesInfo name="IEEE Network," value="(Early Access)" />
     </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://arxiv.org/abs/1907.06197">
       <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="Zhuang" target="https://journals.aps.org/prx/abstract/10.1103/PhysRevX.9.041023">
       <front>
         <title>Physical-Layer Supervised Learning Assisted by an Entangled Sensor Network</title>
         <author initials="Q." surname="Zhuang">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2019"/>
       </front>	   
	   <seriesInfo name="Physical Review Letters," value="American Physical Society" />
     </reference>
	 
	 <reference anchor="Fan" target="https://advances.sciencemag.org/content/4/8/eaar4994.short">
       <front>
         <title>Superconducting Cavity Electro-Optics: A Platform for Coherent Photon Conversion between Superconducting and Photonic Circuits</title>
         <author initials="L." surname="Fan">
           <organization></organization>
         </author>
		 <author initials="et" surname="al.">
           <organization></organization>
         </author>
		 <date year="2018"/>
       </front>	   
	   <seriesInfo name="Science Advances," value="AAAS" />
      </reference>
	 
    </references>
		

		
	
  </back>
  
</rfc>