rfc9340xml2.original.xml | rfc9340.xml | |||
---|---|---|---|---|
<?xml version="1.0" encoding="US-ASCII"?> | <?xml version="1.0" encoding="UTF-8"?> | |||
<!-- This template is for creating an Internet Draft using xml2rfc, | <!DOCTYPE rfc [ | |||
which is available here: http://xml.resource.org. --> | <!ENTITY nbsp " "> | |||
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ | <!ENTITY zwsp "​"> | |||
<!-- One method to get references from the online citation libraries. | <!ENTITY nbhy "‑"> | |||
There has to be one entity for each item to be referenced. | <!ENTITY wj "⁠"> | |||
An alternate method (rfc include) is described in the references. --> | ||||
<!ENTITY rfc1958 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference. | ||||
RFC.1958.xml'> | ||||
<!ENTITY I-D.irtf-qirg-quantum-internet-use-cases SYSTEM 'http://xml.resource.or | ||||
g/public/rfc/bibxml3/reference.I-D.irtf-qirg-quantum-internet-use-cases.xml'> | ||||
]> | ]> | |||
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> | <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IRTF" | |||
<!-- used by XSLT processors --> | category="info" consensus="true" docName="draft-irtf-qirg-principles-11" number= | |||
<!-- For a complete list and description of processing instructions (PIs), | "9340" ipr="trust200902" obsoletes="" updates="" xml:lang="en" tocInclude="true" | |||
please see http://xml.resource.org/authoring/README.html. --> | tocDepth="3" symRefs="true" sortRefs="true" version="3"> | |||
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds | ||||
might want to use. | ||||
(Here they are set differently than their defaults in xml2rfc v1.32) --> | ||||
<?rfc strict="yes" ?> | ||||
<!-- give errors regarding ID-nits and DTD validation --> | ||||
<!-- control the table of contents (ToC) --> | ||||
<?rfc toc="yes"?> | ||||
<!-- generate a ToC --> | ||||
<?rfc tocdepth="3"?> | ||||
<!-- the number of levels of subsections in ToC. default: 3 --> | ||||
<!-- control references --> | ||||
<?rfc symrefs="yes"?> | ||||
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] --> | ||||
<?rfc sortrefs="yes" ?> | ||||
<!-- sort the reference entries alphabetically --> | ||||
<!-- control vertical white space | ||||
(using these PIs as follows is recommended by the RFC Editor) --> | ||||
<?rfc compact="yes" ?> | ||||
<!-- do not start each main section on a new page --> | ||||
<?rfc subcompact="no" ?> | ||||
<!-- keep one blank line between list items --> | ||||
<!-- end of list of popular I-D processing instructions --> | ||||
<rfc category="info" docName="draft-irtf-qirg-principles-11" ipr="trust200902"> | ||||
<!-- category values: std, bcp, info, exp, and historic | ||||
ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902 | ||||
, | ||||
or pre5378Trust200902 | ||||
you can add the attributes updates="NNNN" and obsoletes="NNNN" | ||||
they will automatically be output with "(if approved)" --> | ||||
<!-- ***** FRONT MATTER ***** --> | <!-- xml2rfc v2v3 conversion 3.15.0 --> | |||
<front> | <front> | |||
<!-- The abbreviated title is used in the page header - it is only necessary | ||||
if the | ||||
full title is longer than 39 characters --> | ||||
<title abbrev="Principles for a Quantum Internet">Architectural Principles | <title abbrev="Principles for a Quantum Internet">Architectural Principles | |||
for a Quantum Internet</title> | for a Quantum Internet</title> | |||
<seriesInfo name="RFC" value="9340"/> | ||||
<!-- add 'role="editor"' below for the editors if appropriate --> | ||||
<!-- Another author who claims to be an editor --> | ||||
<author fullname="Wojciech Kozlowski" initials="W" surname="Kozlowski"> | <author fullname="Wojciech Kozlowski" initials="W" surname="Kozlowski"> | |||
<organization>QuTech</organization> | <organization>QuTech</organization> | |||
<address> | ||||
<address> | <postal> | |||
<postal> | <extaddr>Building 22</extaddr> | |||
<street>Building 22</street> | <street>Lorentzweg 1</street> | |||
<street>Lorentzweg 1</street> | ||||
<!-- Reorder these if your country does things differently --> | ||||
<code>2628 CJ</code> | <code>2628 CJ</code> | |||
<city>Delft</city> | <city>Delft</city> | |||
<region></region> | <country>Netherlands</country> | |||
<country>Netherlands</country> | </postal> | |||
</postal> | <email>w.kozlowski@tudelft.nl</email> | |||
<email>w.kozlowski@tudelft.nl</email> | ||||
<!-- uri and facsimile elements may also be added --> | ||||
</address> | </address> | |||
</author> | </author> | |||
<author fullname="Stephanie Wehner" initials="S" surname="Wehner"> | ||||
<author fullname="Stephanie Wehner" initials="S" surname="Wehner"> | <organization>QuTech</organization> | |||
<organization>QuTech</organization> | <address> | |||
<postal> | ||||
<address> | <extaddr>Building 22</extaddr> | |||
<postal> | <street>Lorentzweg 1</street> | |||
<street>Building 22</street> | ||||
<street>Lorentzweg 1</street> | ||||
<!-- Reorder these if your country does things differently --> | ||||
<code>2628 CJ</code> | <code>2628 CJ</code> | |||
<city>Delft</city> | <city>Delft</city> | |||
<region></region> | <country>Netherlands</country> | |||
<country>Netherlands</country> | </postal> | |||
</postal> | <email>s.d.c.wehner@tudelft.nl</email> | |||
<email>s.d.c.wehner@tudelft.nl</email> | ||||
<!-- uri and facsimile elements may also be added --> | ||||
</address> | ||||
</author> | ||||
<author fullname="Rodney Van Meter" initials="R" surname="Van Meter"> | ||||
<organization>Keio University</organization> | ||||
<address> | ||||
<postal> | ||||
<street>5322 Endo</street> | ||||
<!-- Reorder these if your country does things differently --> | ||||
<city>Fujisawa</city> | ||||
<region>Kanagawa</region> | ||||
<code>252-0882</code> | ||||
<country>Japan</country> | ||||
</postal> | ||||
<email>rdv@sfc.wide.ad.jp</email> | ||||
<!-- uri and facsimile elements may also be added --> | ||||
</address> | </address> | |||
</author> | </author> | |||
<author fullname="Rodney Van Meter" initials="R" surname="Van Meter"> | ||||
<author fullname="Bruno Rijsman" initials="B" surname="Rijsman"> | <organization>Keio University</organization> | |||
<organization>Individual</organization> | <address> | |||
<address> | <postal> | |||
<email>brunorijsman@gmail.com</email> | <street>5322 Endo, Fujisawa</street> | |||
<region>Kanagawa</region> | ||||
<code>252-0882</code> | ||||
<country>Japan</country> | ||||
</postal> | ||||
<email>rdv@sfc.wide.ad.jp</email> | ||||
</address> | </address> | |||
</author> | </author> | |||
<author fullname="Bruno Rijsman" initials="B" surname="Rijsman"> | ||||
<author fullname="Angela Sara Cacciapuoti" initials="A" surname="S. Cacciapuo | <organization>Individual</organization> | |||
ti"> | <address> | |||
<organization>University of Naples Federico II</organization> | <email>brunorijsman@gmail.com</email> | |||
</address> | ||||
<address> | </author> | |||
<postal> | <author fullname="Angela Sara Cacciapuoti" initials="A" surname="S. Cacciapu | |||
<street>Department of Electrical Engineering and Information Technologi | oti"> | |||
es</street> | <organization>University of Naples Federico II</organization> | |||
<street>Claudio 21</street> | <address> | |||
<postal> | ||||
<!-- Reorder these if your country does things differently --> | <extaddr>Department of Electrical Engineering and Information Technolog | |||
ies</extaddr> | ||||
<street>Claudio 21</street> | ||||
<code>80125</code> | <code>80125</code> | |||
<city>Naples</city> | <city>Naples</city> | |||
<country>Italy</country> | <country>Italy</country> | |||
</postal> | </postal> | |||
<email>angelasara.cacciapuoti@unina.it</email> | ||||
<email>angelasara.cacciapuoti@unina.it</email> | ||||
<!-- uri and facsimile elements may also be added --> | ||||
</address> | </address> | |||
</author> | </author> | |||
<author fullname="Marcello Caleffi" initials="M" surname="Caleffi"> | ||||
<author fullname="Marcello Caleffi" initials="M" surname="Caleffi"> | <organization>University of Naples Federico II</organization> | |||
<organization>University of Naples Federico II</organization> | <address> | |||
<postal> | ||||
<address> | <extaddr>Department of Electrical Engineering and Information Technolog | |||
<postal> | ies</extaddr> | |||
<street>Department of Electrical Engineering and Information Technologi | <street>Claudio 21</street> | |||
es</street> | ||||
<street>Claudio 21</street> | ||||
<!-- Reorder these if your country does things differently --> | ||||
<code>80125</code> | <code>80125</code> | |||
<city>Naples</city> | <city>Naples</city> | |||
<country>Italy</country> | <country>Italy</country> | |||
</postal> | </postal> | |||
<email>marcello.caleffi@unina.it</email> | ||||
<email>marcello.caleffi@unina.it</email> | ||||
<!-- uri and facsimile elements may also be added --> | ||||
</address> | </address> | |||
</author> | </author> | |||
<author fullname="Shota Nagayama" initials="S" surname="Nagayama"> | ||||
<author fullname="Shota Nagayama" initials="S" surname="Nagayama"> | <organization>Mercari, Inc.</organization> | |||
<organization>Mercari, Inc.</organization> | <address> | |||
<postal> | ||||
<address> | <extaddr>Roppongi Hills Mori Tower 18F</extaddr> | |||
<postal> | <street>6-10-1 Roppongi, Minato-ku</street> | |||
<street>Roppongi Hills Mori Tower 18F</street> | ||||
<street>6-10-1 Roppongi, Minato-ku</street> | ||||
<!-- Reorder these if your country does things differently --> | ||||
<code>106-6118</code> | <code>106-6118</code> | |||
<city>Tokyo</city> | <region>Tokyo</region> | |||
<country>Japan</country> | <country>Japan</country> | |||
</postal> | </postal> | |||
<email>shota.nagayama@mercari.com</email> | ||||
<email>shota.nagayama@mercari.com</email> | ||||
<!-- uri and facsimile elements may also be added --> | ||||
</address> | </address> | |||
</author> | </author> | |||
<date year="2023" month="February" /> | ||||
<date year="2022" /> | <workgroup>Quantum Internet</workgroup> | |||
<!-- If the month and year are both specified and are the current ones, xml2r | ||||
fc will fill | ||||
in the current day for you. If only the current year is specified, xml2r | ||||
fc will fill | ||||
in the current day and month for you. If the year is not the current on | ||||
e, it is | ||||
necessary to specify at least a month (xml2rfc assumes day="1" if not s | ||||
pecified for the | ||||
purpose of calculating the expiry date). With drafts it is normally su | ||||
fficient to | ||||
specify just the year. --> | ||||
<!-- Meta-data Declarations --> | ||||
<area>General</area> | ||||
<workgroup>Quantum Internet Research Group</workgroup> | ||||
<!-- WG name at the upperleft corner of the doc, | ||||
IETF is fine for individual submissions. | ||||
If this element is not present, the default is "Network Working Group", | ||||
which is used by the RFC Editor as a nod to the history of the IETF. --> | ||||
<keyword>Quantum Internet</keyword> | ||||
<keyword>Architecture</keyword> | ||||
<keyword>Repeater</keyword> | ||||
<keyword>Bell Pair</keyword> | ||||
<keyword>EPR Pair</keyword> | ||||
<!-- Keywords will be incorporated into HTML output | <keyword>Quantum Internet</keyword> | |||
files in a meta tag but they have no effect on text or nroff | <keyword>Architecture</keyword> | |||
output. If you submit your draft to the RFC Editor, the | <keyword>Repeater</keyword> | |||
keywords will be used for the search engine. --> | <keyword>Bell Pair</keyword> | |||
<keyword>EPR Pair</keyword> | ||||
<abstract> | <abstract> | |||
<t>The vision of a quantum internet is to enhance existing Internet | <t>The vision of a quantum internet is to enhance existing Internet | |||
technology by enabling quantum communication between any two points on | technology by enabling quantum communication between any two points on | |||
Earth. To achieve this goal, a quantum network stack should be built from | Earth. To achieve this goal, a quantum network stack should be built from | |||
the ground up to account for the fundamentally new properties of quantum | the ground up to account for the fundamentally new properties of quantum | |||
entanglement. The first quantum entanglement networks have been realised | entanglement. The first quantum entanglement networks have been realised, | |||
<xref target="Pompili21.1" />, but there is no practical proposal for how t | but there is no practical proposal for how to | |||
o | organise, utilise, and manage such networks. In this document, we attempt t | |||
organise, utilise, and manage such networks. In this draft, we attempt to | o | |||
lay down the framework and introduce some basic architectural principles | lay down the framework and introduce some basic architectural principles | |||
for a quantum internet. This is intended for general guidance and general | for a quantum internet. This is intended for general guidance and general | |||
interest, but also to provide a foundation for discussion between | interest. It is also intended to provide a foundation for discussion betwe en | |||
physicists and network specialists. This document is a product of the | physicists and network specialists. This document is a product of the | |||
Quantum Internet Research Group (QIRG).</t> | Quantum Internet Research Group (QIRG).</t> | |||
</abstract> | </abstract> | |||
</front> | </front> | |||
<middle> | ||||
<middle> | <section numbered="true" toc="default"> | |||
<section title="Introduction"> | <name>Introduction</name> | |||
<t>Quantum networks are distributed systems of quantum devices that | <t>Quantum networks are distributed systems of quantum devices that | |||
utilise fundamental quantum mechanical phenomena such as superposition, | utilise fundamental quantum mechanical phenomena such as superposition, | |||
entanglement, and quantum measurement to achieve capabilities beyond what | entanglement, and quantum measurement to achieve capabilities beyond what | |||
is possible with non-quantum (classical) networks <xref target="Kimble08" | is possible with non-quantum (classical) networks <xref target="Kimble08" f | |||
/>. Depending on the stage of a quantum network <xref target="Wehner18" /> | ormat="default"/>. Depending on the stage of a quantum network <xref target="Weh | |||
ner18" format="default"/>, | ||||
such devices may range from simple photonic devices capable of preparing | such devices may range from simple photonic devices capable of preparing | |||
and measuring only one quantum bit (qubit) at a time all the way to | and measuring only one quantum bit (qubit) at a time all the way to | |||
large-scale quantum computers of the future. A quantum network is not | large-scale quantum computers of the future. A quantum network is not | |||
meant to replace classical networks, but rather form an overall hybrid | meant to replace classical networks but rather to form an overall hybrid | |||
classical-quantum network supporting new capabilities which are otherwise | classical-quantum network supporting new capabilities that are otherwise | |||
impossible to realise <xref target="VanMeterBook" />. For example, the | impossible to realise <xref target="VanMeterBook" format="default"/>. For e | |||
most well-known application of quantum communication, quantum key | xample, the | |||
distribution (QKD), can create and distribute a pair of symmetric | most well-known application of quantum communication, Quantum Key | |||
Distribution (QKD) <xref target="QKD" format="default"/>, can create and di | ||||
stribute a pair of symmetric | ||||
encryption keys in such a way that the security of the entire process | encryption keys in such a way that the security of the entire process | |||
relies on the laws of physics (and thus can be mathematically proven to be | relies on the laws of physics (and thus can be mathematically proven to be | |||
unbreakable) rather than the intractability of certain mathematical | unbreakable) rather than the intractability of certain mathematical | |||
problems <xref target="Bennett14" /> <xref target="Ekert91" />. Small | problems <xref target="Bennett14" format="default"/> <xref target="Ekert91" format="default"/>. Small | |||
networks capable of QKD have even already been deployed at short (roughly | networks capable of QKD have even already been deployed at short (roughly | |||
100km) distances <xref target="Elliott03" /> <xref target="Peev09" /> | 100-kilometre) distances <xref target="Elliott03" format="default"/> <xref | |||
<xref target="Aguado19" /> <xref target="Joshi20" />.</t> | target="Peev09" format="default"/> | |||
<xref target="Aguado19" format="default"/> <xref target="Joshi20" format | ||||
<t>The quantum networking paradigm also offers promise for a range of new | ="default"/>.</t> | |||
<t>The quantum networking paradigm also offers promise for a range of new | ||||
applications beyond quantum cryptography, such as distributed quantum | applications beyond quantum cryptography, such as distributed quantum | |||
computation <xref target="Cirac99" /> <xref target="Crepeau02" />, secure | computation <xref target="Cirac99" format="default"/> <xref target="Crepeau | |||
quantum computing in the cloud <xref target="Fitzsimons17" />, | 02" format="default"/>; secure | |||
quantum-enhanced measurement networks <xref target="Giovanetti04" />, or | quantum computing in the cloud <xref target="Fitzsimons17" format="default" | |||
higher-precision, long-baseline telescopes <xref target="Gottesman12" />. | />; | |||
These applications are much more demanding than QKD and networks capable | quantum-enhanced measurement networks <xref target="Giovannetti04" format=" | |||
default"/>; or | ||||
higher-precision, long-baseline telescopes <xref target="Gottesman12" forma | ||||
t="default"/>. | ||||
These applications are much more demanding than QKD, and networks capable | ||||
of executing them are in their infancy. The first fully quantum, multinode | of executing them are in their infancy. The first fully quantum, multinode | |||
network capable of sending, receiving, and manipulating distributed | network capable of sending, receiving, and manipulating distributed | |||
quantum information has only recently been realized <xref | quantum information has only recently been realised <xref target="Pompili21 | |||
target="Pompili21.1" /></t> | .1" format="default"/>.</t> | |||
<t>Whilst a lot of effort has gone into physically realising and | ||||
<t>Whilst a lot of effort has gone into physically realising and | ||||
connecting such devices, and making improvements to their speed and error | connecting such devices, and making improvements to their speed and error | |||
tolerance, there are no worked out proposals for how to run these | tolerance, no proposals for how to run these networks have been worked out | |||
networks. To draw an analogy with a classical network, we are at a stage | at the time of this writing. To draw an analogy with a classical network, we are | |||
at a stage | ||||
where we can start to physically connect our devices and send data, but | where we can start to physically connect our devices and send data, but | |||
all sending, receiving, buffer management, connection synchronisation, and | all sending, receiving, buffer management, connection synchronisation, and | |||
so on, must be managed by the application directly by using low-level, | so on must be managed by the application directly by using low-level, | |||
custom-built, and hardware-specific interfaces, rather than being managed | custom-built, and hardware-specific interfaces, rather than being managed | |||
by a network stack that exposes a convenient high-level interface, such as | by a network stack that exposes a convenient high-level interface, such as | |||
sockets. Only recently, was the first ever attempt at such a network stack | sockets. Only recently was the first-ever attempt at such a network stack | |||
experimentally demonstrated in a laboratory setting <xref | experimentally demonstrated in a laboratory setting <xref target="Pompili21 | |||
target="Pompili21.2" />. Furthermore, whilst physical mechanisms for | .2" format="default"/>. Furthermore, whilst physical mechanisms for | |||
transmitting quantum information exist, there are no robust protocols for | transmitting quantum information exist, there are no robust protocols for | |||
managing such transmissions.</t> | managing such transmissions.</t> | |||
<t>This document, produced by the Quantum Internet Research Group (QIRG), | ||||
<t>This document, produced by the Quantum Internet Research Group (QIRG), | ||||
introduces quantum networks and presents general guidelines for the design | introduces quantum networks and presents general guidelines for the design | |||
and construction of such networks. Overall, it is intended as an | and construction of such networks. Overall, it is intended as an | |||
introduction to the subject for network engineers and researchers. It | introduction to the subject for network engineers and researchers. It | |||
should not be considered as a conclusive statement on how quantum network | should not be considered as a conclusive statement on how quantum networks | |||
should or will be implemented. This document was discussed on the QIRG | should or will be implemented. This document was discussed on the QIRG | |||
mailing list and several IETF meetings and represents the consensus of the | mailing list and several IETF meetings. It represents the consensus of the | |||
QIRG members, both of experts in the subject matter (from the quantum as | QIRG members, of both experts in the subject matter (from the quantum and | |||
well networking domain) as well as newcomers who are the target | networking domains) and newcomers who are the target | |||
audience.</t> | audience.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Quantum Information</name> | ||||
<section title="Quantum information"> | <t>In order to understand the framework for quantum networking, a basic | |||
<t>In order to understand the framework for quantum networking, a basic | ||||
understanding of quantum information theory is necessary. The following | understanding of quantum information theory is necessary. The following | |||
sections aim to introduce the minimum amount of knowledge necessary to | sections aim to introduce the minimum amount of knowledge necessary to | |||
understand the principles of operation of a quantum network. This | understand the principles of operation of a quantum network. This | |||
exposition was written with a classical networking audience in mind. It is | exposition was written with a classical networking audience in mind. It is | |||
assumed that the reader has never before been exposed to any quantum | assumed that the reader has never before been exposed to any quantum | |||
physics. We refer the reader to <xref target="SutorBook" /> and <xref | physics. We refer the reader to <xref target="SutorBook" format="default"/> | |||
target="NielsenChuang"/> for an in-depth introduction to quantum | and <xref target="NielsenChuang" format="default"/> for an in-depth introductio | |||
n to quantum | ||||
information systems.</t> | information systems.</t> | |||
<section numbered="true" toc="default"> | ||||
<section title="Quantum state"> | <name>Quantum State</name> | |||
<t>A quantum mechanical system is described by its quantum state. A | ||||
<t>A quantum mechanical system is described by its quantum state. A | ||||
quantum state is an abstract object that provides a complete description | quantum state is an abstract object that provides a complete description | |||
of the system at that particular moment. When combined with the rules of | of the system at that particular moment. When combined with the rules of | |||
the system's evolution in time, such as a quantum circuit, it also then | the system's evolution in time, such as a quantum circuit, it also then | |||
provides a complete description of the system at all times. For the | provides a complete description of the system at all times. For the | |||
purposes of computing and networking, the classical equivalent of a | purposes of computing and networking, the classical equivalent of a | |||
quantum state would be a string or stream of logical bit values. These | quantum state would be a string or stream of logical bit values. These | |||
bits provide a complete description of what values we can read out from | bits provide a complete description of what values we can read out from | |||
that string at that particular moment and when combined with its rules | that string at that particular moment, and when combined with its rules | |||
for evolution in time, such as a logical circuit, we will also know its | for evolution in time, such as a logical circuit, we will also know its | |||
value at any other time.</t> | value at any other time.</t> | |||
<t>Just like a single classical bit, a quantum mechanical system can be | ||||
<t>Just like a single classical bit, a quantum mechanical system can be | simple and consist of a single particle, e.g., an atom or a photon of | |||
simple and consist of a single particle, e.g. an atom or a photon of | ||||
light. In this case, the quantum state provides the complete description | light. In this case, the quantum state provides the complete description | |||
of that one particle. Similarly, just like a string of bits consists of | of that one particle. Similarly, just like a string of bits consists of | |||
multiple bits, a single quantum state can be used to also describe an | multiple bits, a single quantum state can be used to also describe an | |||
ensemble of many particles. However, because quantum states are governed | ensemble of many particles. However, because quantum states are governed | |||
by the laws of quantum mechanics their behaviour is significantly | by the laws of quantum mechanics, their behaviour is significantly | |||
different to that of a string of bits. In this section we will summarise | different to that of a string of bits. In this section, we will summarise | |||
the key concepts to understand these differences and the we will explain | the key concepts to understand these differences. We will then explain | |||
their consequences for networking in the rest of the draft.</t> | their consequences for networking in the rest of this document.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Qubit</name> | ||||
<section title="Qubit"> | <t>The differences between quantum computation and classical computation | |||
<t>The differences between quantum computation and classical computation | begin at the bit level. A classical computer operates on the binary | |||
begin at the bit-level. A classical computer operates on the binary | alphabet { 0, 1 }. A quantum bit, called a qubit, exists over the s | |||
alphabet { 0, 1 }. A quantum bit, called a qubit, exists over the same | ame | |||
binary space, but unlike the classical bit, its state can exist in a | binary space, but unlike the classical bit, its state can exist in a | |||
superposition of the two possibilities:</t> | superposition of the two possibilities:</t> | |||
<t>|qubit⟩ = a |0⟩ + b |1⟩,</t> | ||||
<t>|qubit> = a |0> + b |1>,</t> | <t>where |X⟩ is Dirac's ket notation for a quantum state (the value that | |||
a qubit holds) -- here, the binary 0 and 1 -- and the coefficients a and | ||||
<t>where |X> is Dirac's ket notation for a quantum state (the value that | b | |||
a qubit holds), here the binary 0 and 1, and the coefficients a and b | ||||
are complex numbers called probability amplitudes. Physically, such a | are complex numbers called probability amplitudes. Physically, such a | |||
state can be realised using a variety of different technologies such as | state can be realised using a variety of different technologies such as | |||
electron spin, photon polarisation, atomic energy levels, and so on.</t> | electron spin, photon polarisation, atomic energy levels, and so on.</t> | |||
<t>Upon measurement, the qubit loses its superposition and irreversibly | ||||
<t>Upon measurement, the qubit loses its superposition and irreversibly | collapses into one of the two basis states, either |0⟩ or |1⟩. Which of | |||
collapses into one of the two basis states, either |0> or |1>. Which of | the two states it ends up in may not be deterministic but can be | |||
the two states it ends up in may not be deterministic, but can be | ||||
determined from the readout of the measurement. The measurement result | determined from the readout of the measurement. The measurement result | |||
is a classical bit, 0 or 1, corresponding to |0> and |1> respectively. | is a classical bit, 0 or 1, corresponding to |0⟩ and |1⟩, respectively. | |||
The probability of measuring the state in the |0> state is |a|^2 and | The probability of measuring the state in the |0⟩ state is |a|<sup>2</sup | |||
similarly the probability of measuring the state in the |1> state is | >; | |||
|b|^2, where |a|^2 + |b|^2 = 1. This randomness is not due to our | similarly, the probability of measuring the state in the |1⟩ state is | |||
ignorance of the underlying mechanisms, but rather is a fundamental | |&wj;b&wj;|&wj;<sup>2</sup>, where |a|<sup>2</sup> + |b|<sup>2</sup> = 1. | |||
feature of a quantum mechanical system <xref target="Aspect81" />.</t> | This randomness is not due to our | |||
ignorance of the underlying mechanisms but rather is a fundamental | ||||
<t>The superposition property plays an important role in fundamental | feature of a quantum mechanical system <xref target="Aspect81" format="de | |||
fault"/>.</t> | ||||
<t>The superposition property plays an important role in fundamental | ||||
gate operations on qubits. Since a qubit can exist in a superposition of | gate operations on qubits. Since a qubit can exist in a superposition of | |||
its basis states, the elementary quantum gates are able to act on all | its basis states, the elementary quantum gates are able to act on all | |||
states of the superposition at the same time. For example, consider the | states of the superposition at the same time. For example, consider the | |||
NOT gate:</t> | NOT gate:</t> | |||
<t>NOT (a |0⟩ + b |1⟩) ➔ a |1⟩ + b |0⟩.</t> | ||||
<t>NOT (a |0> + b |1>) -> a |1> + b |0>.</t> | <t>It is important to note that "qubit" can have two meanings. In the | |||
first meaning, "qubit" refers to a physical quantum <strong>system</stron | ||||
<t>It is important to note that "qubit" can have two meanings. In the | g> whose | |||
first meaning, "qubit" refers to a physical quantum *system* whose | ||||
quantum state can be expressed as a superposition of two basis states, | quantum state can be expressed as a superposition of two basis states, | |||
which we often label |0> and |1>. Here, "qubit" refers to a physical | which we often label |0⟩ and |1⟩. Here, "qubit" refers to a physical | |||
implementation akin to what a flip-flop, switch, voltage, or current | implementation akin to what a flip-flop, switch, voltage, or current | |||
would be for a classical bit. In the second meaning, "qubit" refers to | would be for a classical bit. In the second meaning, "qubit" refers to | |||
the abstract quantum *state* of a quantum system with such two basis | the abstract quantum <strong>state</strong> of a quantum system with such two basis | |||
states. In this case, the meaning of "qubit" is akin to the logical | states. In this case, the meaning of "qubit" is akin to the logical | |||
value of a bit, from classical computing, i.e. "logical 0" or "logical | value of a bit, from classical computing, i.e., "logical 0" or "logical | |||
1". The two concepts are related, because a physical "qubit" (first | 1". The two concepts are related, because a physical "qubit" (first | |||
meaning) can be used to store the abstract "qubit" (second meaning). | meaning) can be used to store the abstract "qubit" (second meaning). | |||
Both meanings are used interchangeably in literature and the meaning is | Both meanings are used interchangeably in literature, and the meaning is | |||
generally clear from the context.</t> | generally clear from the context.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Multiple Qubits</name> | ||||
<section title="Multiple qubits"> | <t>When multiple qubits are combined in a single quantum state, the spac | |||
e | ||||
<t>When multiple qubits are combined in a single quantum state the space | ||||
of possible states grows exponentially and all these states can coexist | of possible states grows exponentially and all these states can coexist | |||
in a superposition. For example, the general form of a two-qubit | in a superposition. For example, the general form of a two-qubit | |||
register is</t> | register is</t> | |||
<t>a |00⟩ + b |01⟩ + c |10⟩ + d |11⟩,</t> | ||||
<t>a |00> + b |01> + c |10> + d |11></t> | <t>where the coefficients have the same probability amplitude | |||
interpretation as for the single-qubit state. Each state represents a | ||||
<t>where the coefficients have the same probability amplitude | ||||
interpretation as for the single qubit state. Each state represents a | ||||
possible outcome of a measurement of the two-qubit register. For | possible outcome of a measurement of the two-qubit register. For | |||
example, |01> denotes a state in which the first qubit is in the state | example, |01⟩ denotes a state in which the first qubit is in the state | |||
|0> and the second is in the state |1>.</t> | |0⟩ and the second is in the state |1⟩.</t> | |||
<t>Performing single-qubit gates affects the relevant qubit in each of | ||||
<t>Performing single qubit gates affects the relevant qubit in each of | ||||
the superposition states. Similarly, two-qubit gates also act on all the | the superposition states. Similarly, two-qubit gates also act on all the | |||
relevant superposition states, but their outcome is far more | relevant superposition states, but their outcome is far more | |||
interesting.</t> | interesting.</t> | |||
<t>Consider a two-qubit register where the first qubit is in the | ||||
<t>Consider a two-qubit register where the first qubit is in the | superposed state (|0⟩ + |1⟩)/sqrt(2) and the other is in the state |0⟩. | |||
superposed state (|0> + |1>)/sqrt(2) and the other is in the state |0>. | This combined state can be written as</t> | |||
This combined state can be written as:</t> | <t>(|0⟩ + |1⟩)/sqrt(2) x |0⟩ = (|00⟩ + |10⟩)/sqrt(2),</t> | |||
<t>where x denotes a tensor product (the mathematical mechanism for | ||||
<t>(|0> + |1>)/sqrt(2) x |0> = (|00> + |10>)/sqrt(2),</t> | ||||
<t>where x denotes a tensor product (the mathematical mechanism for | ||||
combining quantum states together).</t> | combining quantum states together).</t> | |||
<t>The constant 1/sqrt(2) is called the normalisation factor and | ||||
<t>The constant 1/sqrt(2) is called the normalisation factor and | reflects the fact that the probabilities of measuring either a |0⟩ or a | |||
reflects the fact that the probabilities of measuring either a |0> or a | |1⟩ for the first qubit add up to one.</t> | |||
|1> for the first qubit add up to one.</t> | <t>Let us now consider the two-qubit Controlled NOT, or CNOT, gate. The | |||
CNOT gate takes as input two qubits -- a control and a target -- and appl | ||||
<t>Let us now consider the two-qubit controlled-NOT, or CNOT, gate. The | ies | |||
CNOT gate takes as input two qubits, a control and target, and applies | ||||
the NOT gate to the target if the control qubit is set. The truth table | the NOT gate to the target if the control qubit is set. The truth table | |||
looks like</t> | looks like</t> | |||
<table align="center"> | ||||
<name>CNOT Truth Table</name> | ||||
<thead> | ||||
<tr> | ||||
<th align="center">IN</th> | ||||
<th align="center">OUT</th> | ||||
</tr> | ||||
</thead> | ||||
<tbody> | ||||
<tr> | ||||
<td align="center">00</td> | ||||
<td align="center">00</td> | ||||
</tr> | ||||
<tr> | ||||
<td align="center">01</td> | ||||
<td align="center">01</td> | ||||
</tr> | ||||
<tr> | ||||
<td align="center">10</td> | ||||
<td align="center">11</td> | ||||
</tr> | ||||
<tr> | ||||
<td align="center">11</td> | ||||
<td align="center">10</td> | ||||
</tr> | ||||
</tbody> | ||||
</table> | ||||
<texttable> | <t>Now, consider performing a CNOT gate on the state with the first | |||
<ttcol align="center">IN</ttcol> | ||||
<ttcol align="center">OUT</ttcol> | ||||
<c>00</c><c>00</c> | ||||
<c>01</c><c>01</c> | ||||
<c>10</c><c>11</c> | ||||
<c>11</c><c>10</c> | ||||
</texttable> | ||||
<t>Now, consider performing a CNOT gate on the state with the first | ||||
qubit being the control. We apply a two-qubit gate on all the | qubit being the control. We apply a two-qubit gate on all the | |||
superposition states:</t> | superposition states:</t> | |||
<t>CNOT (|00⟩ + |10⟩)/sqrt(2) ➔ (|00⟩ + |11⟩)/sqrt(2).</t> | ||||
<t>CNOT (|00> + |10>)/sqrt(2) -> (|00> + |11>)/sqrt(2).</t> | <t>What is so interesting about this two-qubit gate operation? The final | |||
state is <strong>entangled</strong>. There is no possible way of re | ||||
<t>What is so interesting about this two-qubit gate operation? The final | presenting that | |||
state is *entangled*. There is no possible way of representing that | ||||
quantum state as a product of two individual qubits; they are no longer | quantum state as a product of two individual qubits; they are no longer | |||
independent. That is, it is not possible to describe the quantum state | independent. That is, it is not possible to describe the quantum state | |||
of either of the individual qubits in a way that is independent of the | of either of the individual qubits in a way that is independent of the | |||
other qubit. Only the quantum state of the system that consists of both | other qubit. Only the quantum state of the system that consists of both | |||
qubits provides a physically complete description of the two-qubit | qubits provides a physically complete description of the two-qubit | |||
system. The states of the two individual qubits are now correlated | system. The states of the two individual qubits are now correlated | |||
beyond what is possible to achieve classically. Neither qubit is in a | beyond what is possible to achieve classically. Neither qubit is in a | |||
definite |0> or |1> state, but if we perform a measurement on either | definite |0⟩ or |1⟩ state, but if we perform a measurement on either | |||
one, the outcome of the partner qubit will *always* yield the exact same | one, the outcome of the partner qubit will <strong>always</strong> yield | |||
outcome. The final state, whether it's |00> or |11>, is fundamentally | the exact same | |||
outcome. The final state, whether it's |00⟩ or |11⟩, is fundamentally | ||||
random as before, but the states of the two qubits following a | random as before, but the states of the two qubits following a | |||
measurement will always be identical. One can think of this as flipping | measurement will always be identical. One can think of this as flipping | |||
two coins, but the coins always both land on "heads" or both land on | two coins, but both coins always land on "heads" or both land on | |||
"tails" together. Something that we know is impossible classically.</t> | "tails" together -- something that we know is impossible classically.</t> | |||
<t>Once a measurement is performed, the two qubits are once again | ||||
<t>Once a measurement is performed, the two qubits are once again | independent. The final state is either |00⟩ or |11⟩, and both of these | |||
independent. The final state is either |00> or |11> and both of these | ||||
states can be trivially decomposed into a product of two individual | states can be trivially decomposed into a product of two individual | |||
qubits. The entanglement has been consumed and the entangled state must | qubits. The entanglement has been consumed, and the entangled state must | |||
be prepared again.</t> | be prepared again.</t> | |||
</section> | ||||
</section> | </section> | |||
<section anchor="entanglement" numbered="true" toc="default"> | ||||
</section> | <name>Entanglement as the Fundamental Resource</name> | |||
<t>Entanglement is the fundamental building block of quantum networks. | ||||
<section anchor="entanglement" title="Entanglement as the fundamental resourc | ||||
e"> | ||||
<t>Entanglement is the fundamental building block of quantum networks. | ||||
Consider the state from the previous section:</t> | Consider the state from the previous section:</t> | |||
<t>(|00⟩ + |11⟩)/sqrt(2).</t> | ||||
<t>(|00> + |11>)/sqrt(2).</t> | <t>Neither of the two qubits is in a definite |0⟩ or |1⟩ state, and we nee | |||
d | ||||
<t>Neither of the two qubits is in a definite |0> or |1> state and we need | ||||
to know the state of the entire register to be able to fully describe the | to know the state of the entire register to be able to fully describe the | |||
behaviour of the two qubits.</t> | behaviour of the two qubits.</t> | |||
<t>Entangled qubits have interesting non-local properties. Consider | ||||
<t>Entangled qubits have interesting non-local properties. Consider | ||||
sending one of the qubits to another device. This device could in | sending one of the qubits to another device. This device could in | |||
principle be anywhere: on the other side of the room, in a different | principle be anywhere: on the other side of the room, in a different | |||
country, or even on a different planet. Provided negligible noise has been | country, or even on a different planet. Provided negligible noise has been | |||
introduced, the two qubits will forever remain in the entangled state | introduced, the two qubits will forever remain in the entangled state | |||
until a measurement is performed. The physical distance does not matter at | until a measurement is performed. The physical distance does not matter at | |||
all for entanglement.</t> | all for entanglement.</t> | |||
<t>This lies at the heart of quantum networking, because it is possible to | ||||
<t>This lies at the heart of quantum networking, because it is possible to | ||||
leverage the non-classical correlations provided by entanglement in order | leverage the non-classical correlations provided by entanglement in order | |||
to design completely new types of application protocols that are not | to design completely new types of application protocols that are not | |||
possible to achieve with just classical communication. Examples of such | possible to achieve with just classical communication. Examples of such | |||
applications are quantum cryptography <xref target="Bennett14" /> <xref | applications are quantum cryptography <xref target="Bennett14" format="defa | |||
target="Ekert91" />, blind quantum computation <xref target="Fitzsimons17" | ult"/> <xref target="Ekert91" format="default"/>, blind quantum computation <xre | |||
/>, or distributed quantum computation <xref target="Crepeau02" />.</t> | f target="Fitzsimons17" format="default"/>, or distributed quantum computation < | |||
xref target="Crepeau02" format="default"/>.</t> | ||||
<t>Entanglement has two very special features from which one can derive | <t>Entanglement has two very special features from which one can derive | |||
some intuition about the types of applications enabled by a quantum | some intuition about the types of applications enabled by a quantum | |||
network.</t> | network.</t> | |||
<t>The first stems from the fact that entanglement enables | ||||
<t>The first stems from the fact that entanglement enables stronger than | stronger-than-classical correlations, leading to opportunities for tasks th | |||
classical correlations, leading to opportunities for tasks that require | at require | |||
coordination. As a trivial example, consider the problem of consensus | coordination. As a trivial example, consider the problem of consensus | |||
between two nodes who want to agree on the value of a single bit. They can | between two nodes who want to agree on the value of a single bit. They can | |||
use the quantum network to prepare the state (|00> + |11>)/sqrt(2) with | use the quantum network to prepare the state (|00⟩ + |11⟩)/sqrt(2) with | |||
each node holding one of the two qubits. Once either of the two nodes | each node holding one of the two qubits. Once either of the two nodes | |||
performs a measurement, the state of the two qubits collapses to either | performs a measurement, the state of the two qubits collapses to either | |||
|00> or |11>, so whilst the outcome is random and does not exist before | |00⟩ or |11⟩, so whilst the outcome is random and does not exist before | |||
measurement, the two nodes will always measure the same value. We can also | measurement, the two nodes will always measure the same value. We can also | |||
build the more general multi-qubit state (|00...> + |11...>)/sqrt(2) and | build the more general multi-qubit state (|00...⟩ + |11...⟩)/sqrt(2) and | |||
perform the same algorithm between an arbitrary number of nodes. These | perform the same algorithm between an arbitrary number of nodes. These | |||
stronger than classical correlations generalise to more complicated | stronger-than-classical correlations generalise to measurement schemes that | |||
measurement schemes as well.</t> | are more complicated as well.</t> | |||
<t>The second feature of entanglement is that it cannot be shared, in the | ||||
<t>The second feature of entanglement is that it cannot be shared, in the | ||||
sense that if two qubits are maximally entangled with each other, then it | sense that if two qubits are maximally entangled with each other, then it | |||
is physically impossible for these two qubits to also be entangled with a | is physically impossible for these two qubits to also be entangled with a | |||
third qubit <xref target="Terhal04" />. Hence, entanglement forms a sort | third qubit <xref target="Terhal04" format="default"/>. Hence, entanglement forms a sort | |||
of private and inherently untappable connection between two nodes once | of private and inherently untappable connection between two nodes once | |||
established.</t> | established.</t> | |||
<t>Entanglement is created through local interactions between two qubits | ||||
<t>Entanglement is created through local interactions between two qubits | or as a product of the way the qubits were created (e.g., entangled photon | |||
or as a product of the way the qubits were created (e.g. entangled photon | ||||
pairs). To create a distributed entangled state, one can then physically | pairs). To create a distributed entangled state, one can then physically | |||
send one of the qubits to a remote node. It is also possible to directly | send one of the qubits to a remote node. It is also possible to directly | |||
entangle qubits that are physically separated, but this still requires | entangle qubits that are physically separated, but this still requires | |||
local interactions between some other qubits that the separated qubits are | local interactions between some other qubits that the separated qubits are | |||
initially entangled with. Therefore, it is the transmission of qubits that | initially entangled with. Therefore, it is the transmission of qubits that | |||
draws the line between a genuine quantum network and a collection of | draws the line between a genuine quantum network and a collection of | |||
quantum computers connected over a classical network.</t> | quantum computers connected over a classical network.</t> | |||
<t>A quantum network is defined as a collection of nodes that is able to | ||||
<t>A quantum network is defined as a collection of nodes that is able to | ||||
exchange qubits and distribute entangled states amongst themselves. A | exchange qubits and distribute entangled states amongst themselves. A | |||
quantum node that is able only to communicate classically with another | quantum node that is able only to communicate classically with another | |||
quantum node is not a member of a quantum network.</t> | quantum node is not a member of a quantum network.</t> | |||
<t>Services and applications that are more complex can be built on top of | ||||
<t>More complex services and applications can be built on top of entangled | entangled | |||
states distributed by the network, see e.g. <xref target="ZOO" /></t> | states distributed by the network; for example, see <xref target="ZOO" form | |||
at="default"/>.</t> | ||||
</section> | </section> | |||
<section numbered="true" toc="default"> | ||||
<section title="Achieving quantum connectivity"> | <name>Achieving Quantum Connectivity</name> | |||
<t>This section explains the meaning of quantum connectivity and the | ||||
<t>This section explains the meaning of quantum connectivity and the | ||||
necessary physical processes at an abstract level.</t> | necessary physical processes at an abstract level.</t> | |||
<section numbered="true" toc="default"> | ||||
<section title="Challenges"> | <name>Challenges</name> | |||
<t>A quantum network cannot be built by simply extrapolating all the | ||||
<t>A quantum network cannot be built by simply extrapolating all the | ||||
classical models to their quantum analogues. Sending qubits over a wire | classical models to their quantum analogues. Sending qubits over a wire | |||
like we send classical bits is simply not as easy to do. There are | like we send classical bits is simply not as easy to do. There are | |||
several technological as well as fundamental challenges that make | several technological as well as fundamental challenges that make | |||
classical approaches unsuitable in a quantum context.</t> | classical approaches unsuitable in a quantum context.</t> | |||
<section numbered="true" toc="default"> | ||||
<section title="The measurement problem"> | <name>The Measurement Problem</name> | |||
<t>In classical computers and networks, we can read out the bits store | ||||
<t>In classical computers and networks we can read out the bits stored | d | |||
in memory at any time. This is helpful for a variety of purposes such | in memory at any time. This is helpful for a variety of purposes such | |||
as copying, error detection and correction, and so on. This is not | as copying, error detection and correction, and so on. This is not | |||
possible with qubits.</t> | possible with qubits.</t> | |||
<t>A measurement of a qubit's state will destroy its superposition and | ||||
<t>A measurement of a qubit's state will destroy its superposition and | ||||
with it any entanglement it may have been part of. Once a qubit is | with it any entanglement it may have been part of. Once a qubit is | |||
being processed, it cannot be read out until a suitable point in the | being processed, it cannot be read out until a suitable point in the | |||
computation, determined by the protocol handling the qubit, has been | computation, determined by the protocol handling the qubit, has been | |||
reached. Therefore, we cannot use the same methods known from | reached. Therefore, we cannot use the same methods known from | |||
classical computing for the purposes of error detection and | classical computing for the purposes of error detection and | |||
correction. Nevertheless, quantum error detection and correction | correction. Nevertheless, quantum error detection and correction | |||
schemes exist that take this problem into account and how a network | schemes exist that take this problem into account, and how a network | |||
chooses to manage errors will have an impact on its architecture.</t> | chooses to manage errors will have an impact on its architecture.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>No-Cloning Theorem</name> | ||||
<section title="No-cloning theorem"> | <t>Since directly reading the state of a qubit is not possible, one | |||
<t>Since directly reading the state of a qubit is not possible, one | ||||
could ask if we can simply copy a qubit without looking at it. | could ask if we can simply copy a qubit without looking at it. | |||
Unfortunately, this is fundamentally not possible in quantum mechanics | Unfortunately, this is fundamentally not possible in quantum mechanics | |||
<xref target="Park70" /> <xref target="Wootters82" />.</t> | <xref target="Park70" format="default"/> <xref target="Wootters82" form | |||
at="default"/>.</t> | ||||
<t>The no-cloning theorem states that it is impossible to create an | <t>The no-cloning theorem states that it is impossible to create an | |||
identical copy of an arbitrary, unknown quantum state. Therefore, it | identical copy of an arbitrary, unknown quantum state. Therefore, it | |||
is also impossible to use the same mechanisms that worked for | is also impossible to use the same mechanisms that worked for | |||
classical networks for signal amplification, retransmission, and so on | classical networks for signal amplification, retransmission, and so on, | |||
as they all rely on the ability to copy the underlying data. Since any | as they all rely on the ability to copy the underlying data. Since any | |||
physical channel will always be lossy, connecting nodes within a | physical channel will always be lossy, connecting nodes within a | |||
quantum network is a challenging endeavour and its architecture must | quantum network is a challenging endeavour, and its architecture must | |||
at its core address this very issue.</t> | at its core address this very issue.</t> | |||
</section> | ||||
</section> | <section anchor="fidelity" numbered="true" toc="default"> | |||
<name>Fidelity</name> | ||||
<section anchor="fidelity" title="Fidelity"> | <t>In general, it is expected that a classical packet arrives at its | |||
<t>In general, it is expected that a classical packet arrives at its | ||||
destination without any errors introduced by hardware noise along the | destination without any errors introduced by hardware noise along the | |||
way. This is verified at various levels through a variety of error | way. This is verified at various levels through a variety of error | |||
detection and correction mechanisms. Since we cannot read or copy a | detection and correction mechanisms. Since we cannot read or copy a | |||
quantum state, error detection and correction is more involved.</t> | quantum state, error detection and correction are more involved.</t> | |||
<t>To describe the quality of a quantum state, a physical quantity | ||||
<t>To describe the quality of a quantum state, a physical quantity | called fidelity is used <xref target="NielsenChuang" format="default"/> | |||
called fidelity is used <xref target="NielsenChuang" />. Fidelity | . Fidelity | |||
takes a value between 0 and 1 -- higher is better, and less than 0.5 | takes a value between 0 and 1 -- higher is better, and less than 0.5 | |||
means the state is unusable. It measures how close a quantum state is | means the state is unusable. It measures how close a quantum state is | |||
to the state we have tried to create. It expresses the probability | to the state we have tried to create. It expresses the probability | |||
that the state will behave exactly the same as our desired state. | that the state will behave exactly the same as our desired state. | |||
Fidelity is an important property of a quantum system that allows us | Fidelity is an important property of a quantum system that allows us | |||
to quantify how much a particular state has been affected by noise | to quantify how much a particular state has been affected by noise | |||
from various sources (gate errors, channel losses, environment | from various sources (gate errors, channel losses, environment | |||
noise).</t> | noise).</t> | |||
<t>Interestingly, quantum applications do not need perfect fidelity to | ||||
<t>Interestingly, quantum applications do not need perfect fidelity to | ||||
be able to execute -- as long as the fidelity is above some | be able to execute -- as long as the fidelity is above some | |||
application-specific threshold, they will simply operate at lower | application-specific threshold, they will simply operate at lower | |||
rates. Therefore, rather than trying to ensure that we always deliver | rates. Therefore, rather than trying to ensure that we always deliver | |||
perfect states (a technologically challenging task) applications will | perfect states (a technologically challenging task), applications will | |||
specify a minimum threshold for the fidelity and the network will try | specify a minimum threshold for the fidelity, and the network will try | |||
its best to deliver it. A higher fidelity can be achieved by either | its best to deliver it. A higher fidelity can be achieved by either | |||
having hardware produce states of better fidelity (sometimes one can | having hardware produce states of better fidelity (sometimes one can | |||
sacrifice rate for higher fidelity) or by employing quantum error | sacrifice rate for higher fidelity) or employing quantum error | |||
detection and correction mechanisms (see <xref target="Mural16" /> and | detection and correction mechanisms (see <xref target="Mural16" format= | |||
<xref target="VanMeterBook" /> chapter 11).</t> | "default"/> and Chapter 11 of | |||
<xref target="VanMeterBook" format="default"/>).</t> | ||||
</section> | </section> | |||
<section anchor="dt" numbered="true" toc="default"> | ||||
<section anchor="dt" title="Inadequacy of direct transmission"> | <name>Inadequacy of Direct Transmission</name> | |||
<t>Conceptually, the most straightforward way to distribute an | ||||
<t>Conceptually, the most straightforward way to distribute an | ||||
entangled state is to simply transmit one of the qubits directly to | entangled state is to simply transmit one of the qubits directly to | |||
the other end across a series of nodes while performing sufficient | the other end across a series of nodes while performing sufficient | |||
forward quantum error correction (<xref target="qec" />) to bring | forward Quantum Error Correction (QEC) (<xref target="qec" format="defa ult"/>) to bring | |||
losses down to an acceptable level. Despite the no-cloning theorem and | losses down to an acceptable level. Despite the no-cloning theorem and | |||
the inability to directly measure a quantum state, error-correcting | the inability to directly measure a quantum state, error-correcting | |||
mechanisms for quantum communication exist <xref target="Jiang09" /> | mechanisms for quantum communication exist <xref target="Jiang09" forma | |||
<xref target="Fowler10" /> <xref target="Devitt13" /> <xref | t="default"/> | |||
target="Mural16" />. However, quantum error correction makes very high | <xref target="Fowler10" format="default"/> <xref target="Devitt13" f | |||
ormat="default"/> <xref target="Mural16" format="default"/>. However, QEC makes | ||||
very high | ||||
demands on both resources (physical qubits needed) and their initial | demands on both resources (physical qubits needed) and their initial | |||
fidelity. Implementation is very challenging and quantum error | fidelity. Implementation is very challenging, and QEC | |||
correction is not expected to be used until later generations of | is not expected to be used until later generations of | |||
quantum networks are possible (see <xref target="Mural16" /> figure 2 | quantum networks are possible (see Figure 2 of <xref target="Mural16" f | |||
and <xref target="generations" />). Until then, quantum networks rely | ormat="default"/> | |||
on entanglement swapping (<xref target="es" />) and teleportation | and <xref target="generations" format="default"/> of this document). Un | |||
(<xref target="teleportation" />). This alternative relies on the | til then, quantum networks rely | |||
on entanglement swapping (<xref target="es" format="default"/>) and tel | ||||
eportation | ||||
(<xref target="teleportation" format="default"/>). This alternative rel | ||||
ies on the | ||||
observation that we do not need to be able to distribute any arbitrary | observation that we do not need to be able to distribute any arbitrary | |||
entangled quantum state. We only need to be able to distribute any one | entangled quantum state. We only need to be able to distribute any one | |||
of what are known as the Bell pair states <xref target="Briegel98" | of what are known as the Bell pair states <xref target="Briegel98" form | |||
/>.</t> | at="default"/>.</t> | |||
</section> | ||||
</section> | </section> | |||
<section numbered="true" toc="default"> | ||||
</section> | <name>Bell Pairs</name> | |||
<t>Bell pair states are the entangled two-qubit states:</t> | ||||
<section title="Bell pairs"> | <artwork align="left" name="" type="" alt=""><![CDATA[ | |||
|00⟩ + |11⟩, | ||||
<t>Bell pair states are the entangled two-qubit states:</t> | |00⟩ - |11⟩, | |||
|01⟩ + |10⟩, | ||||
<t> | |01⟩ - |10⟩, | |||
|00> + |11>, | ]]></artwork> | |||
|00> - |11>, | ||||
|01> + |10>, | ||||
|01> - |10>, | ||||
</t> | ||||
<t>where the constant 1/sqrt(2) normalisation factor has been ignored | <t>where the constant 1/sqrt(2) normalisation factor has been ignored | |||
for clarity. Any of the four Bell pair states above will do, as it is | for clarity. Any of the four Bell pair states above will do, as it is | |||
possible to transform any Bell pair into another Bell pair with local | possible to transform any Bell pair into another Bell pair with local | |||
operations performed on only one of the qubits. When each qubit in a | operations performed on only one of the qubits. When each qubit in a | |||
Bell pair is held by a separate node, either node can apply a series of | Bell pair is held by a separate node, either node can apply a series of | |||
single qubit gates to their qubit alone in order to transform the state | single-qubit gates to their qubit alone in order to transform the state | |||
between the different variants.</t> | between the different variants.</t> | |||
<t>Distributing a Bell pair between two nodes is much easier than | ||||
<t>Distributing a Bell pair between two nodes is much easier than | ||||
transmitting an arbitrary quantum state over a network. Since the state | transmitting an arbitrary quantum state over a network. Since the state | |||
is known, handling errors becomes easier and small-scale | is known, handling errors becomes easier, and small-scale | |||
error-correction (such as entanglement distillation discussed in a later | error correction (such as entanglement distillation, as discussed in <xre | |||
section) combined with reattempts becomes a valid strategy.</t> | f target="ent-dis"/>), combined with reattempts, becomes a valid strategy.</t> | |||
<t>The reason for using Bell pairs specifically as opposed to any other | ||||
<t>The reason for using Bell pairs specifically as opposed to any other | ||||
two-qubit state is that they are the maximally entangled two-qubit set | two-qubit state is that they are the maximally entangled two-qubit set | |||
of basis states. Maximal entanglement means that these states have the | of basis states. Maximal entanglement means that these states have the | |||
strongest non-classical correlations of all possible two-qubit states. | strongest non-classical correlations of all possible two-qubit states. | |||
Furthermore, since single-qubit local operations can never increase | Furthermore, since single-qubit local operations can never increase | |||
entanglement, less entangled states would impose some constraints on | entanglement, states that are less entangled would impose some constraint s on | |||
distributed quantum algorithms. This makes Bell pairs particularly | distributed quantum algorithms. This makes Bell pairs particularly | |||
useful as a generic building block for distributed quantum | useful as a generic building block for distributed quantum | |||
applications.</t> | applications.</t> | |||
</section> | ||||
</section> | <section anchor="teleportation" numbered="true" toc="default"> | |||
<name>Teleportation</name> | ||||
<section anchor="teleportation" title="Teleportation"> | <t>The observation that we only need to be able to distribute Bell pairs | |||
<t>The observation that we only need to be able to distribute Bell pairs | ||||
relies on the fact that this enables the distribution of any other | relies on the fact that this enables the distribution of any other | |||
arbitrary entangled state. This can be achieved via quantum state | arbitrary entangled state. This can be achieved via quantum state | |||
teleportation <xref target="Bennett93" />. Quantum state teleportation | teleportation <xref target="Bennett93" format="default"/>. Quantum state teleportation | |||
consumes an unknown qubit state that we want to transmit and recreates | consumes an unknown qubit state that we want to transmit and recreates | |||
it at the desired destination. This does not violate the no-cloning | it at the desired destination. This does not violate the no-cloning | |||
theorem as the original state is destroyed in the process.</t> | theorem, as the original state is destroyed in the process.</t> | |||
<t>To achieve this, an entangled pair needs to be distributed between | ||||
<t>To achieve this, an entangled pair needs to be distributed between | ||||
the source and destination before teleportation commences. The source | the source and destination before teleportation commences. The source | |||
then entangles the transmission qubit with its end of the pair and | then entangles the transmission qubit with its end of the pair and | |||
performs a read out of the two qubits (the sum of these operations is | performs a readout of the two qubits (the sum of these operations is | |||
called a Bell state measurement). This consumes the Bell pair's | called a Bell state measurement). This consumes the Bell pair's | |||
entanglement, turning the source and destination qubits into independent | entanglement, turning the source and destination qubits into independent | |||
states. The measurements yields two classical bits which the source | states. The measurement yields two classical bits, which the source | |||
sends to the destination over a classical channel. Based on the value of | sends to the destination over a classical channel. Based on the value of | |||
the received two classical bits, the destination performs one of four | the received two classical bits, the destination performs one of four | |||
possible corrections (called the Pauli corrections) on its end of the | possible corrections (called the Pauli corrections) on its end of the | |||
pair, which turns it into the unknown qubit state that we wanted to | pair, which turns it into the unknown qubit state that we wanted to | |||
transmit. This requirement to communicate the measurement read out over | transmit. This requirement to communicate the measurement readout over | |||
a classical channel unfortunately means that entanglement cannot be used | a classical channel unfortunately means that entanglement cannot be used | |||
to transmit information faster than the speed of light.</t> | to transmit information faster than the speed of light.</t> | |||
<t>The unknown quantum state that was transmitted was never fed into the | ||||
<t>The unknown quantum state that was transmitted was never fed into the | ||||
network itself. Therefore, the network needs to only be able to reliably | network itself. Therefore, the network needs to only be able to reliably | |||
produce Bell pairs between any two nodes in the network. Thus, a key | produce Bell pairs between any two nodes in the network. Thus, a key | |||
difference between a classical and quantum data planes is that a | difference between a classical data plane and a quantum data plane is tha | |||
classical one carries user data, but a quantum data plane provides the | t a | |||
classical data plane carries user data but a quantum data plane provides | ||||
the | ||||
resources for the user to transmit user data themselves without further | resources for the user to transmit user data themselves without further | |||
involvement of the network.</t> | involvement of the network.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>The Life Cycle of Entanglement</name> | ||||
<section title="The life cycle of entanglement"> | <t>Reducing the problem of quantum connectivity to one of generating a | |||
Bell pair has reduced the problem to a simpler, more fundamental case, bu | ||||
<t>Reducing the problem of quantum connectivity to one of generating a | t it has not solved it. In this | |||
Bell pair has facilitated the problem, but it has not solved it. In this | ||||
section, we discuss how these entangled pairs are generated in the first | section, we discuss how these entangled pairs are generated in the first | |||
place, and how their two qubits are delivered to the end-points.</t> | place and how their two qubits are delivered to the end-points.</t> | |||
<section anchor="elg" numbered="true" toc="default"> | ||||
<section anchor="elg" title="Elementary link generation"> | <name>Elementary Link Generation</name> | |||
<t>In a quantum network, entanglement is always first generated | ||||
<t>In a quantum network, entanglement is always first generated | locally (at a node or an auxiliary element), followed by a movement of | |||
locally (at a node or an auxiliary element) followed by a movement of | ||||
one or both of the entangled qubits across the link through quantum | one or both of the entangled qubits across the link through quantum | |||
channels. In this context, photons (particles of light) are the | channels. In this context, photons (particles of light) are the | |||
natural candidate for entanglement carriers, called flying qubits. The | natural candidate for entanglement carriers. Because these photons carr y quantum states from place to place at high speed, we call them flying qubits. The | |||
rationale for this choice is related to the advantages provided by | rationale for this choice is related to the advantages provided by | |||
photons such as moderate interaction with the environment leading to | photons, such as moderate interaction with the environment leading to | |||
moderate decoherence, convenient control with standard optical | moderate decoherence; convenient control with standard optical | |||
components, and high-speed, low-loss transmissions. However, since | components; and high-speed, low-loss transmissions. However, since | |||
photons are hard to store, a transducer must transfer the flying | photons are hard to store, a transducer must transfer the flying | |||
qubit's state to a qubit suitable for information processing and/or | qubit's state to a qubit suitable for information processing and/or | |||
storage (often referred to as a matter qubit).</t> | storage (often referred to as a matter qubit).</t> | |||
<t>Since this process may fail, in order to generate and store | ||||
<t>Since this process may fail, in order to generate and store | ||||
entanglement efficiently, we must be able to distinguish successful | entanglement efficiently, we must be able to distinguish successful | |||
attempts from failures. Entanglement generation schemes that are able | attempts from failures. Entanglement generation schemes that are able | |||
to announce successful generation are called heralded entanglement | to announce successful generation are called heralded entanglement | |||
generation schemes.</t> | generation schemes.</t> | |||
<t>There exist three basic schemes for heralded entanglement | ||||
<t>There exist three basic schemes for heralded entanglement | ||||
generation on a link through coordinated action of the two nodes at | generation on a link through coordinated action of the two nodes at | |||
the two ends of the link <xref target="Cacciapuoti19" />:</t> | the two ends of the link <xref target="Cacciapuoti19" format="default"/ | |||
>:</t> | ||||
<t> | <dl spacing="normal"> | |||
<list style="symbols"> | <dt>"At mid-point":</dt><dd>In this scheme, an entangled photon pair | |||
source | ||||
<t>"At mid-point": in this scheme an entangled photon pair source | ||||
sitting midway between the two nodes with matter qubits sends an | sitting midway between the two nodes with matter qubits sends an | |||
entangled photon through a quantum channel to each of the nodes. | entangled photon through a quantum channel to each of the nodes. | |||
There, transducers are invoked to transfer the entanglement from | There, transducers are invoked to transfer the entanglement from | |||
the flying qubits to the matter qubits. In this scheme, the | the flying qubits to the matter qubits. In this scheme, the | |||
transducers know if the transfers succeeded and are able to herald | transducers know if the transfers succeeded and are able to herald | |||
successful entanglement generation via a message exchange over the | successful entanglement generation via a message exchange over the | |||
classical channel.</t> | classical channel.</dd> | |||
<dt>"At source":</dt><dd>In this scheme, one of the two nodes sends | ||||
<t>"At source": in this scheme one of the two nodes sends a flying | a flying | |||
qubit that is entangled with one of its matter qubits. A | qubit that is entangled with one of its matter qubits. A | |||
transducer at the other end of the link will transfer the | transducer at the other end of the link will transfer the | |||
entanglement from the flying qubit to one of its matter qubits. | entanglement from the flying qubit to one of its matter qubits. | |||
Just like in the previous scheme, the transducer knows if its | Just like in the previous scheme, the transducer knows if its | |||
transfer succeeded and is able to herald successful entanglement | transfer succeeded and is able to herald successful entanglement | |||
generation with a classical message sent to the other node.</t> | generation with a classical message sent to the other node.</dd> | |||
<dt>"At both end-points":</dt><dd>In this scheme, both nodes send a | ||||
<t>"At both end-points": in this scheme both nodes send a flying | flying | |||
qubit that is entangled with one of their matter qubits. A | qubit that is entangled with one of their matter qubits. A | |||
detector somewhere in between the nodes performs a joint | detector somewhere in between the nodes performs a joint | |||
measurement on the two qubits, which stochastically projects the | measurement on the flying qubits, which stochastically projects the | |||
remote matter qubits into an entangled quantum state. The detector | remote matter qubits into an entangled quantum state. The detector | |||
knows if the entanglement succeeded and is able to herald | knows if the entanglement succeeded and is able to herald | |||
successful entanglement generation by sending a message to each | successful entanglement generation by sending a message to each | |||
node over the classical channel.</t> | node over the classical channel.</dd> | |||
</dl> | ||||
</list> | <t>The "mid-point source" scheme is more robust to photon loss, but in | |||
</t> | the other schemes, the nodes retain greater control over the entangled | |||
<t>The "mid-point source" scheme is more robust to photon loss, but in | ||||
the other schemes the nodes retain greater control over the entangled | ||||
pair generation.</t> | pair generation.</t> | |||
<t> Note that whilst photons travel in a particular direction through | ||||
<t> Note that whilst photons travel in a particular direction through | ||||
the quantum channel the resulting entangled pair of qubits does not | the quantum channel the resulting entangled pair of qubits does not | |||
have a direction associated with it. Physically, there is no upstream | have a direction associated with it. Physically, there is no upstream | |||
or downstream end of the pair.</t> | or downstream end of the pair.</t> | |||
</section> | ||||
</section> | <section anchor="es" numbered="true" toc="default"> | |||
<name>Entanglement Swapping</name> | ||||
<section anchor="es" title="Entanglement swapping"> | <t>The problem with generating entangled pairs directly across a link | |||
is that efficiency decreases with channel length. Beyond a few tens of | ||||
<t>The problem with generating entangled pairs directly across a link | ||||
is that efficiency decreases with channel length. Beyond a few 10s of | ||||
kilometres in optical fibre or 1000 kilometres in free space (via | kilometres in optical fibre or 1000 kilometres in free space (via | |||
satellite) the rate is effectively zero and due to the no-cloning | satellite), the rate is effectively zero, and due to the no-cloning | |||
theorem we cannot simply amplify the signal. The solution is | theorem we cannot simply amplify the signal. The solution is | |||
entanglement swapping <xref target="Briegel98" />.</t> | entanglement swapping <xref target="Briegel98" format="default"/>.</t> | |||
<t>A Bell pair between any two nodes in the network can be constructed | ||||
<t>A Bell pair between any two nodes in the network can be constructed | ||||
by combining the pairs generated along each individual link on a path | by combining the pairs generated along each individual link on a path | |||
between the two end-points. Each node along the path can consume the | between the two end-points. Each node along the path can consume the | |||
two pairs on the two links that it is connected to in order to produce | two pairs on the two links to which it is connected, in order to produc e | |||
a new entangled pair between the two remote ends. This process is | a new entangled pair between the two remote ends. This process is | |||
known as entanglement swapping. Pictorially it can be represented as | known as entanglement swapping. It can be represented pictorially as | |||
follows:</t> | follows:</t> | |||
<artwork align="left" name="" type="" alt=""><![CDATA[ | ||||
<figure align="center"> | ||||
<artwork align="left"><![CDATA[ | ||||
+---------+ +---------+ +---------+ | +---------+ +---------+ +---------+ | |||
| A | | B | | C | | | A | | B | | C | | |||
| |------| |------| | | | |------| |------| | | |||
| X1~~~~~~~~~~X2 Y1~~~~~~~~~~Y2 | | | X1~~~~~~~~~~X2 Y1~~~~~~~~~~Y2 | | |||
+---------+ +---------+ +---------+ | +---------+ +---------+ +---------+ | |||
]]></artwork> | ]]></artwork> | |||
</figure> | <t>where X1 and X2 are the qubits of the entangled pair X and Y1 and | |||
<t>where X1 and X2 are the qubits of the entangled pair X and Y1 and | ||||
Y2 are the qubits of entangled pair Y. The entanglement is denoted | Y2 are the qubits of entangled pair Y. The entanglement is denoted | |||
with ~~. In the diagram above, nodes A and B share the pair X and | with ~~. In the diagram above, nodes A and B share the pair X and | |||
nodes B and C share the pair Y, but we want entanglement between A and | nodes B and C share the pair Y, but we want entanglement between A and | |||
C.</t> | C.</t> | |||
<t>To achieve this goal, we simply teleport the qubit X2 using the | ||||
<t>To achieve this goal, we simply teleport the qubit X2 using the | ||||
pair Y. This requires node B to perform a Bell state measurement on | pair Y. This requires node B to perform a Bell state measurement on | |||
the qubits X2 and Y1 which result in the destruction of the | the qubits X2 and Y1 that results in the destruction of the | |||
entanglement between Y1 and Y2. However, X2 is recreated in Y2's | entanglement between Y1 and Y2. However, X2 is recreated in Y2's | |||
place, carrying with it its entanglement with X1. The end-result is | place, carrying with it its entanglement with X1. The end result is | |||
shown below:</t> | shown below:</t> | |||
<artwork align="left" name="" type="" alt=""><![CDATA[ | ||||
<figure align="center"> | ||||
<artwork align="left"><![CDATA[ | ||||
+---------+ +---------+ +---------+ | +---------+ +---------+ +---------+ | |||
| A | | B | | C | | | A | | B | | C | | |||
| |------| |------| | | | |------| |------| | | |||
| X1~~~~~~~~~~~~~~~~~~~~~~~~~~~X2 | | | X1~~~~~~~~~~~~~~~~~~~~~~~~~~~X2 | | |||
+---------+ +---------+ +---------+ | +---------+ +---------+ +---------+ | |||
]]></artwork> | ]]></artwork> | |||
</figure> | <t>Depending on the needs of the network and/or application, a final | |||
Pauli correction at the recipient node may not be necessary, since the | ||||
<t>Depending on the needs of the network and/or application, a final | ||||
Pauli correction at the recipient node may not be necessary since the | ||||
result of this operation is also a Bell pair. However, the two | result of this operation is also a Bell pair. However, the two | |||
classical bits that form the read out from the measurement at node B | classical bits that form the readout from the measurement at node B | |||
must still be communicated, because they carry information about which | must still be communicated, because they carry information about which | |||
of the four Bell pairs was actually produced. If a correction is not | of the four Bell pairs was actually produced. If a correction is not | |||
performed, the recipient must be informed which Bell pair was | performed, the recipient must be informed which Bell pair was | |||
received.</t> | received.</t> | |||
<t>This process of teleporting Bell pairs using other entangled pairs | ||||
<t>This process of teleporting Bell pairs using other entangled pairs | ||||
is called entanglement swapping. Quantum nodes that create | is called entanglement swapping. Quantum nodes that create | |||
long-distance entangled pairs via entanglement swapping are called | long-distance entangled pairs via entanglement swapping are called | |||
quantum repeaters in academic literature <xref target="Briegel98" /> | quantum repeaters in academic literature <xref target="Briegel98" forma | |||
and we will use the same terminology in this draft.</t> | t="default"/>. We will use the same terminology in this document.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Error Management</name> | ||||
<section title="Error Management"> | <section anchor="ent-dis" numbered="true" toc="default"> | |||
<name>Distillation</name> | ||||
<section anchor="ent-dis" title="Distillation"> | <t>Neither the generation of Bell pairs nor the swapping operations | |||
are noiseless operations. Therefore, with each link and each swap, | ||||
<t>Neither the generation of Bell pairs nor the swapping operations | ||||
are noiseless operations. Therefore, with each link and each swap | ||||
the fidelity of the state degrades. However, it is possible to | the fidelity of the state degrades. However, it is possible to | |||
create higher fidelity Bell pair states from two or more lower | create higher-fidelity Bell pair states from two or more | |||
fidelity pairs through a process called distillation (sometimes also | lower-fidelity pairs through a process called distillation (sometimes | |||
referred to as purification) <xref target="Dur07" />.</t> | also | |||
referred to as purification) <xref target="Dur07" format="default"/>. | ||||
<t>To distil a quantum state, a second (and sometimes third) quantum | </t> | |||
<t>To distil a quantum state, a second (and sometimes third) quantum | ||||
state is used as a "test tool" to test a proposition about the first | state is used as a "test tool" to test a proposition about the first | |||
state, e.g., "the parity of the two qubits in the first state is | state, e.g., "the parity of the two qubits in the first state is | |||
even." When the test succeeds, confidence in the state is improved, | even." When the test succeeds, confidence in the state is improved, | |||
and thus the fidelity is improved. The test tool states are | and thus the fidelity is improved. The test tool states are | |||
destroyed in the process, so resource demands increase substantially | destroyed in the process, so resource demands increase substantially | |||
when distillation is used. When the test fails, the tested state | when distillation is used. When the test fails, the tested state | |||
must also be discarded. Distillation makes low demands on fidelity | must also be discarded. Distillation makes low demands on fidelity | |||
and resources compared to quantum error correction, but distributed | and resources compared to QEC, but distributed | |||
protocols incur round-trip delays due to classical communication | protocols incur round-trip delays due to classical communication | |||
<xref target="Bennett96" />.</t> | <xref target="Bennett96" format="default"/>.</t> | |||
</section> | ||||
</section> | <section anchor="qec" numbered="true" toc="default"> | |||
<name>Quantum Error Correction (QEC)</name> | ||||
<section anchor="qec" title="Quantum Error Correction"> | <t>Just like classical error correction, QEC | |||
encodes logical qubits using several physical (raw) qubits to | ||||
<t>Just like classical error correction, quantum error correction | protect them from the errors described in <xref target="fidelity" for | |||
(QEC) encodes logical qubits using several physical (raw) qubits to | mat="default"/> | |||
protect them from errors described in <xref target="fidelity" /> | <xref target="Jiang09" format="default"/> <xref target="Fowler10" | |||
<xref target="Jiang09" /> <xref target="Fowler10" /> <xref | format="default"/> <xref target="Devitt13" format="default"/> <xref target="Mura | |||
target="Devitt13" /> <xref target="Mural16" />. Furthermore, | l16" format="default"/>. Furthermore, | |||
similarly to its classical counterpart, QEC can not only correct | similarly to its classical counterpart, QEC can not only correct | |||
state errors but also account for lost qubits. Additionally, if all | state errors but also account for lost qubits. Additionally, if all | |||
physical qubits which encode a logical qubit are located at the same | physical qubits that encode a logical qubit are located at the same | |||
node, the correction procedure can be executed locally, even if the | node, the correction procedure can be executed locally, even if the | |||
logical qubit is entangled with remote qubits.</t> | logical qubit is entangled with remote qubits.</t> | |||
<t>Although QEC was originally a scheme proposed to protect a qubit | ||||
<t>Although QEC was originally a scheme proposed to protect a qubit | ||||
from noise, QEC can also be applied to entanglement distillation. | from noise, QEC can also be applied to entanglement distillation. | |||
Such QEC-applied distillation is cost-effective but requires a | Such QEC-applied distillation is cost effective but requires a | |||
higher base fidelity.</t> | higher base fidelity.</t> | |||
</section> | ||||
</section> | <section anchor="generations" numbered="true" toc="default"> | |||
<name>Error Management Schemes</name> | ||||
<section anchor="generations" title="Error management schemes"> | <t>Quantum networks have been categorised into three "generations" | |||
based on the error management scheme they employ <xref target="Mural1 | ||||
<t>Quantum networks have been categorized into three "generations" | 6" format="default"/>. Note that these "generations" are more like | |||
based on the error management scheme they employ <xref | ||||
target="Mural16" />. Note that these "generations" are more like | ||||
categories; they do not necessarily imply a time progression and do | categories; they do not necessarily imply a time progression and do | |||
not obsolete each other, though the later generations do require | not obsolete each other, though the later generations do require | |||
more advanced technologies. Which generation is used depends on the | technologies that are more advanced. Which generation is used depends on the | |||
hardware platform and network design choices.</t> | hardware platform and network design choices.</t> | |||
<t><xref target="gens" format="default"/> summarises the generations | ||||
<t><xref target="gens" /> summarises the generations.</t> | .</t> | |||
<texttable anchor="gens" title="Classical signaling and generations" | <table anchor="gens" align="center"> | |||
> | <name>Classical Signalling and Generations</name> | |||
<ttcol align="center"></ttcol> | <thead> | |||
<ttcol align="center">First generation</ttcol> | <tr> | |||
<ttcol align="center">Second generation</ttcol> | <th align="center"/> | |||
<ttcol align="center">Third generation</ttcol> | <th align="center">First generation</th> | |||
<th align="center">Second generation</th> | ||||
<c>Loss tolerance</c> | <th align="center">Third generation</th> | |||
<c>Heralded entanglement generation (bi-directional classical signa | </tr> | |||
ling)</c> | </thead> | |||
<c>Heralded entanglement generation (bi-directional classical signa | <tbody> | |||
ling)</c> | <tr> | |||
<c>Quantum Error Correction (no classical signaling)</c> | <td align="center">Loss tolerance</td> | |||
<td align="center">Heralded entanglement generation (bidirecti | ||||
<c></c> | onal classical signalling)</td> | |||
<c></c> | <td align="center">Heralded entanglement generation (bidirecti | |||
<c></c> | onal classical signalling)</td> | |||
<c></c> | <td align="center">QEC (no classical signalling)</td> | |||
</tr> | ||||
<c>Error tolerance</c> | <tr> | |||
<c>Entanglement distillation (bi-directional classical signaling)</ | <td align="center"/> | |||
c> | <td align="center"/> | |||
<c>Entanglement distillation (uni-directional classical signaling) | <td align="center"/> | |||
or | <td align="center"/> | |||
Quantum Error Correction (no classical signaling) </c> | </tr> | |||
<c>Quantum Error Correction (no classical signaling)</c> | <tr> | |||
</texttable> | <td align="center">Error tolerance</td> | |||
<td align="center">Entanglement distillation (bidirectional cl | ||||
<t>Generations are defined by the directions of classical signalling | assical signalling)</td> | |||
<td align="center">Entanglement distillation (unidirectional c | ||||
lassical signalling) or | ||||
QEC (no classical signalling) </td> | ||||
<td align="center">QEC (no classical signalling)</td> | ||||
</tr> | ||||
</tbody> | ||||
</table> | ||||
<t>Generations are defined by the directions of classical signalling | ||||
required in their distributed protocols for loss tolerance and error | required in their distributed protocols for loss tolerance and error | |||
tolerance. Classical signalling carries the classical bits and | tolerance. Classical signalling carries the classical bits, | |||
incurs round-trip delays described in <xref target="ent-dis" />, | incurring round-trip delays. As described in <xref target="ent-dis" f | |||
hence they affect the performance of quantum networks, especially as | ormat="default"/>, | |||
these delays affect the performance of quantum networks, especially a | ||||
s | ||||
the distance between the communicating nodes increases.</t> | the distance between the communicating nodes increases.</t> | |||
<t>Loss tolerance is about tolerating qubit transmission losses | ||||
<t>Loss tolerance is about tolerating qubit transmission losses | ||||
between nodes. Heralded entanglement generation, as described in | between nodes. Heralded entanglement generation, as described in | |||
<xref target="elg" />, confirms the receipt of an entangled qubit | <xref target="elg" format="default"/>, confirms the receipt of an ent angled qubit | |||
using a heralding signal. A pair of directly connected quantum nodes | using a heralding signal. A pair of directly connected quantum nodes | |||
repeatedly attempt to generate an entangled pair until the a | repeatedly attempt to generate an entangled pair until the | |||
heralding signal is received. As described in <xref target="qec" />, | heralding signal is received. As described in <xref target="qec" form | |||
QEC can be applied to complement lost qubits eliminating the need | at="default"/>, | |||
for re-attempts. Furthermore, since the correction procedure is | QEC can be applied to complement lost qubits, eliminating the need | |||
for reattempts. Furthermore, since the correction procedure is | ||||
composed of local operations, it does not require a heralding | composed of local operations, it does not require a heralding | |||
signal. However, it is possible only when the photon loss rate from | signal. However, it is possible only when the photon loss rate from | |||
transmission to measurement is less than 50%.</t> | transmission to measurement is less than 50%.</t> | |||
<t>Error tolerance is about tolerating quantum state errors. | ||||
<t>Error tolerance is about tolerating quantum state errors. | Entanglement distillation is the easiest mechanism to implement for i | |||
Entanglement distillation is the easiest mechanism for improved | mproved | |||
error tolerance to implement, but it incurs round-trip delays due | error tolerance, but it incurs round-trip delays due to | |||
the requirement for bi-directional classical signalling. The | the requirement for bidirectional classical signalling. The | |||
alternative, QEC, is able to correct state errors locally so that it | alternative, QEC, is able to correct state errors locally so that it | |||
does not need any classical signalling between the quantum nodes. In | does not need any classical signalling between the quantum nodes. In | |||
between these two extremes, there is also QEC-applied distillation, | between these two extremes, there is also QEC-applied distillation, | |||
which requires uni-directional classical signalling.</t> | which requires unidirectional classical signalling.</t> | |||
<t>The three "generations" summarised:</t> | ||||
<t>The three "generations" summarised:</t> | <ol spacing="normal" type="1"><li>First-generation quantum networks | |||
use heralding for loss | ||||
<t> | ||||
<list style="numbers"> | ||||
<t>First generation quantum networks use heralding for loss | ||||
tolerance and entanglement distillation for error tolerance. | tolerance and entanglement distillation for error tolerance. | |||
These networks can be implemented even with a limited set of | These networks can be implemented even with a limited set of | |||
available quantum gates.</t> | available quantum gates.</li> | |||
<li>Second-generation quantum networks improve upon the first | ||||
<t>Second generation quantum networks improve upon the first | ||||
generation with QEC codes for error tolerance (but not loss | generation with QEC codes for error tolerance (but not loss | |||
tolerance). At first, QEC will be applied to entanglement | tolerance). At first, QEC will be applied to entanglement | |||
distillation only which requires uni-directional classical | distillation only, which requires unidirectional classical | |||
signalling. Later, QEC codes will be used to create logical Bell | signalling. Later, QEC codes will be used to create logical Bell | |||
pairs which no longer require any classical signalling for the | pairs that no longer require any classical signalling for the | |||
purposes of error tolerance. Heralding is still used to | purposes of error tolerance. Heralding is still used to | |||
compensate for transmission losses.</t> | compensate for transmission losses.</li> | |||
<li>Third-generation quantum networks directly transmit QEC-encode | ||||
<t>Third generation quantum networks directly transmit QEC | d qubits to adjacent nodes, as discussed in <xref target="dt" format="default"/> | |||
encoded qubits to adjacent nodes, as discussed in <xref | . Elementary link Bell pairs can now be created | |||
target="dt" />. Elementary link Bell pairs can now be created | ||||
without heralding or any other classical signalling. | without heralding or any other classical signalling. | |||
Furthermore, this also enables direct transmission architectures | Furthermore, this also enables direct transmission architectures | |||
in which qubits are forwarded end-to-end like classical packets | in which qubits are forwarded end to end like classical packets | |||
rather than relying on Bell pairs and entanglement swapping.</t> | rather than relying on Bell pairs and entanglement swapping.</li> | |||
</ol> | ||||
</list> | <t>Despite the fact that there are important distinctions in how | |||
</t> | errors will be managed in the different generations, it is unlikely | |||
<t>Despite the fact that there are important distinctions in how | ||||
errors will be managed in the different generations it is unlikely | ||||
that all quantum networks will consistently use the same method. | that all quantum networks will consistently use the same method. | |||
This is due to different hardware requirements of the different | This is due to different hardware requirements of the different | |||
generations and the practical reality of network upgrades. | generations and the practical reality of network upgrades. | |||
Therefore, it is unavoidable that eventually boundaries between | Therefore, it is unavoidable that eventually boundaries between | |||
different error management schemes start forming. This will affect | different error management schemes start forming. This will affect | |||
the content and semantics of messages that must cross those | the content and semantics of messages that must cross those | |||
boundaries -- both for connection setup and real-time operation | boundaries -- for both connection setup and real-time operation | |||
<xref target="Nagayama16" />.</t> | <xref target="Nagayama16" format="default"/>.</t> | |||
</section> | ||||
</section> | </section> | |||
<section numbered="true" toc="default"> | ||||
</section> | <name>Delivery</name> | |||
<t>Eventually, the Bell pairs must be delivered to an application (or | ||||
<section title="Delivery"> | higher-layer protocol) at the two end nodes. A detailed list of such | |||
requirements is beyond the scope of this document. At minimum, the | ||||
<t>Eventually, the Bell pairs must be delivered to an application (or | end nodes require information to map a particular Bell pair to the | |||
higher layer protocol) at the two end-nodes. A detailed list of such | ||||
requirements is beyond the scope of this draft. At minimum, the | ||||
end-nodes require information to map a particular Bell pair to the | ||||
qubit in their local memory that is part of this entangled pair.</t> | qubit in their local memory that is part of this entangled pair.</t> | |||
</section> | ||||
</section> | </section> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Architecture of a Quantum Internet</name> | ||||
</section> | <t>It is evident from the previous sections that the fundamental service | |||
<section title="Architecture of a quantum internet"> | ||||
<t>It is evident from the previous sections that the fundamental service | ||||
provided by a quantum network significantly differs from that of a | provided by a quantum network significantly differs from that of a | |||
classical network. Therefore, it is not surprising that the architecture | classical network. Therefore, it is not surprising that the architecture | |||
of a quantum internet will itself be very different from that of the | of a quantum internet will itself be very different from that of the | |||
classical Internet.</t> | classical Internet.</t> | |||
<section numbered="true" toc="default"> | ||||
<section title="Challenges"> | <name>Challenges</name> | |||
<t>This subsection covers the major fundamental challenges involved in b | ||||
<t>This subsection covers the major fundamental challenges building | uilding | |||
quantum networks. Here, we only describe the fundamental differences. | quantum networks. Here, we only describe the fundamental differences. | |||
Technological limitations are described later.</t> | Technological limitations are described in <xref target="phys-constraints | |||
"/>.</t> | ||||
<t> | <ol spacing="normal" type="1"><li> | |||
<list style="numbers"> | <t>Bell pairs are not equivalent to packets that carry payload. | |||
<t>Bell pairs are not equivalent to payload carrying packets. | </t> | |||
<vspace blankLines="1" /> | <t> | |||
In most classical networks, including Ethernet, Internet Protocol | In most classical networks, including Ethernet, Internet Protocol | |||
(IP), and Multi-Protocol Label Switching (MPLS) networks, user data | (IP), and Multi-Protocol Label Switching (MPLS) networks, user data | |||
is grouped into packets. In addition to the user data, each packet | is grouped into packets. In addition to the user data, each packet | |||
also contains a series of headers which contain the control | also contains a series of headers that contain the control | |||
information that lets routers and switches forward it towards its | information that lets routers and switches forward it towards its | |||
destination. Packets are the fundamental unit in a classical | destination. Packets are the fundamental unit in a classical | |||
network. | network. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
In a quantum network, the entangled pairs of qubits are the basic | In a quantum network, the entangled pairs of qubits are the basic | |||
unit of networking. These qubits themselves do not carry any | unit of networking. These qubits themselves do not carry any | |||
headers. Therefore, quantum networks will have to send all control | headers. Therefore, quantum networks will have to send all control | |||
information via separate classical channels which the repeaters will | information via separate classical channels, which the repeaters will | |||
have to correlate with the qubits stored in their memory. | have to correlate with the qubits stored in their memory. | |||
Furthermore, a Bell pair consists of two qubits distributed across | Furthermore, unlike a classical packet, which is located at a single | |||
two nodes which is unlike a classical packet which is located at a | node, a Bell pair consists of two qubits distributed across two | |||
single node. This has a fundamental impact on how quantum networks | nodes. This has a fundamental impact on how quantum networks | |||
will be managed and how protocols need to be designed. To make | will be managed and how protocols need to be designed. To make | |||
long-distance Bell pairs, the nodes may have to keep their qubits in | long-distance Bell pairs, the nodes may have to keep their qubits in | |||
their quantum memories and wait until control information is | their quantum memories and wait until control information is | |||
exchanged before proceeding with the next operation. This signalling | exchanged before proceeding with the next operation. This signalling | |||
will result in additional latency which will depend on the distance | will result in additional latency, which will depend on the distance | |||
between the nodes holding the two ends of the Bell pair. Error | between the nodes holding the two ends of the Bell pair. Error | |||
management, such as entanglement distillation, is a typical example | management, such as entanglement distillation, is a typical example | |||
of such control information exchange <xref target="Nagayama21" /> | of such control information exchange <xref target="Nagayama21" format | |||
(see also <xref target="generations" />).</t> | ="default"/> | |||
(see also <xref target="generations" format="default"/>).</t> | ||||
<t>"Store and forward" vs "store and swap" quantum networks. | </li> | |||
<vspace blankLines="1" /> | <li> | |||
<t>"Store and forward" and "store and swap" quantum networks require | ||||
different state management techniques. | ||||
</t> | ||||
<t> | ||||
As described in <xref target="elg" />, quantum links provide Bell | As described in <xref target="elg" format="default"/>, quantum links provide Bell | |||
pairs that are undirected network resources, in contrast to directed | pairs that are undirected network resources, in contrast to directed | |||
frames of classical networks. This phenomenological distinction | frames of classical networks. This phenomenological distinction | |||
leads to architectural differences between quantum networks and | leads to architectural differences between quantum networks and | |||
classical networks. Quantum networks combine multiple elementary | classical networks. Quantum networks combine multiple elementary | |||
link Bell pairs together to create one end-to-end Bell pair, whereas | link Bell pairs together to create one end-to-end Bell pair, whereas | |||
classical networks deliver messages from one end to the other end | classical networks deliver messages from one end to the other end | |||
hop by hop. | hop by hop. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
Classical networks receive data on one interface, store it in local | Classical networks receive data on one interface, store it in local | |||
buffers, then forward the data to another appropriate interface. | buffers, and then forward the data to another appropriate interface. | |||
Quantum networks store Bell pairs and then execute entanglement | Quantum networks store Bell pairs and then execute entanglement | |||
swapping instead of forwarding in the data plane. Such quantum | swapping instead of forwarding in the data plane. Such quantum | |||
networks are "store and swap" networks. In "store and swap" | networks are "store and swap" networks. In "store and swap" | |||
networks, we do not need to care about the order in which the Bell | networks, we do not need to care about the order in which the Bell | |||
pairs were generated since they are undirected. However, whilst the | pairs were generated, since they are undirected. However, whilst the | |||
ordering does not matter, it is very important that the right | ordering does not matter, it is very important that the right | |||
entangled pairs get swapped, and that the intermediate measurement | entangled pairs get swapped, and that the intermediate measurement | |||
outcomes (see <xref target="es" />) are signalled to and correlated | outcomes (see <xref target="es" format="default"/>) are signalled to and correlated | |||
with the correct qubits at the other nodes. Otherwise, the final | with the correct qubits at the other nodes. Otherwise, the final | |||
end-to-end entangled pair will not be created between the expected | end-to-end entangled pair will not be created between the expected | |||
end-points or will be in a different quantum state than expected. | end-points or will be in a different quantum state than expected. | |||
For example, rather than Alice receiving a qubit that is entangled | For example, rather than Alice receiving a qubit that is entangled | |||
with Bob's qubit, her qubit is entangled with Charlie's qubit. This | with Bob's qubit, her qubit is entangled with Charlie's qubit. This | |||
distinction makes control algorithms and optimisation of quantum | distinction makes control algorithms and optimisation of quantum | |||
networks different from classical ones, in the sense that swapping | networks different from those for classical networks, in the sense th at swapping | |||
is stateful in contrast to stateless packet-by-packet forwarding. | is stateful in contrast to stateless packet-by-packet forwarding. | |||
Note that third generation quantum networks, as described in <xref | Note that, as described in <xref target="generations"/>, third-genera | |||
target="elg" />, will be able to support a "store and forward" | tion quantum networks will be able to support a "store and forward" | |||
architecture in addition to "store and swap".</t> | architecture in addition to "store and swap".</t> | |||
</li> | ||||
<t>An entangled pair is only useful if the locations of both qubits | <li> | |||
<t>An entangled pair is only useful if the locations of both qubits | ||||
are known. | are known. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
A classical network packet logically exists only at one location at | A classical network packet logically exists only at one location at | |||
any point in time. If a packet is modified in some way, whether | any point in time. If a packet is modified in some way, whether | |||
headers or payload, this information does not need to be conveyed to | headers or payload, this information does not need to be conveyed to | |||
anybody else in the network. The packet can be simply forwarded as | anybody else in the network. The packet can be simply forwarded as | |||
before. <vspace blankLines="1" /> | before. </t> | |||
<t> | ||||
In contrast, entanglement is a phenomenon in which two or more | In contrast, entanglement is a phenomenon in which two or more | |||
qubits exist in a physically distributed state. Operations on one of | qubits exist in a physically distributed state. Operations on one of | |||
the qubits change the mutual state of the pair. Since the owner of a | the qubits change the mutual state of the pair. Since the owner of a | |||
particular qubit cannot just read out its state, it must coordinate | particular qubit cannot just read out its state, it must coordinate | |||
all its actions with the owner of the pair's other qubit. Therefore, | all its actions with the owner of the pair's other qubit. Therefore, | |||
the owner of any qubit that is part of an entangled pair must know | the owner of any qubit that is part of an entangled pair must know | |||
the location of its counterpart. Location, in this context, need not | the location of its counterpart. Location, in this context, need not | |||
be the explicit spatial location. A relevant pair identifier, a | be the explicit spatial location. A relevant pair identifier, a | |||
means of communication between the pair owners, and an association | means of communication between the pair owners, and an association | |||
between the pair ID and the individual qubits is sufficient.</t> | between the pair ID and the individual qubits will be sufficient.</t> | |||
</li> | ||||
<t>Generating entanglement requires temporary state. | <li> | |||
<vspace blankLines="1" /> | <t>Generating entanglement requires temporary state. | |||
</t> | ||||
<t> | ||||
Packet forwarding in a classical network is largely a stateless | Packet forwarding in a classical network is largely a stateless | |||
operation. When a packet is received, the router does a lookup in | operation. When a packet is received, the router does a lookup in | |||
its forwarding table and sends the packet out of the appropriate | its forwarding table and sends the packet out of the appropriate | |||
output. There is no need to keep any memory of the packet any more. | output. There is no need to keep any memory of the packet any more. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
A quantum node must be able to make decisions about qubits that it | A quantum node must be able to make decisions about qubits that it | |||
receives and is holding in its memory. Since qubits do not carry | receives and is holding in its memory. Since qubits do not carry | |||
headers, the receipt of an entangled pair conveys no control | headers, the receipt of an entangled pair conveys no control | |||
information based on which the repeater can make a decision. The | information based on which the repeater can make a decision. The | |||
relevant control information will arrive separately over a classical | relevant control information will arrive separately over a classical | |||
channel. This implies that a repeater must store temporary state as | channel. This implies that a repeater must store temporary state, as | |||
the control information and the qubit it pertains to will, in | the control information and the qubit it pertains to will, in | |||
general, not arrive at the same time.</t> | general, not arrive at the same time.</t> | |||
</li> | ||||
</list> | </ol> | |||
</t> | </section> | |||
<section numbered="true" toc="default"> | ||||
</section> | <name>Classical Communication</name> | |||
<t>In this document, we have already covered two different roles that | ||||
<section title="Classical communication"> | classical communication must perform the following:</t> | |||
<ul spacing="normal"> | ||||
<t>In this draft we have already covered two different roles that | <li>Communicate classical bits of information as part of distributed | |||
classical communication must perform:</t> | protocols such as entanglement swapping and teleportation.</li> | |||
<li>Communicate control information within a network, including | ||||
<t> | background protocols such as routing, as well as signalling protocols | |||
<list style="symbols"> | to set up end-to-end entanglement generation.</li> | |||
</ul> | ||||
<t>communicate classical bits of information as part of distributed | <t>Classical communication is a crucial building block of any quantum | |||
protocols such as entanglement swapping and teleportation,</t> | ||||
<t>communicate control information within a network, including both | ||||
background protocols such as routing as well as signalling protocols | ||||
to set up end-to-end entanglement generation.</t> | ||||
</list> | ||||
</t> | ||||
<t>Classical communication is a crucial building block of any quantum | ||||
network. All nodes in a quantum network are assumed to have classical | network. All nodes in a quantum network are assumed to have classical | |||
connectivity with each other (within typical administrative domain | connectivity with each other (within typical administrative domain | |||
limits). Therefore, quantum nodes will need to manage two data planes in | limits). Therefore, quantum nodes will need to manage two data planes in | |||
parallel, a classical one and a quantum one. Additionally, a node must | parallel: a classical data plane and a quantum data plane. Additionally, a node must | |||
be able to correlate information between the two planes so that the | be able to correlate information between the two planes so that the | |||
control information received on a classical channel can be applied to | control information received on a classical channel can be applied to | |||
the qubits managed by the quantum data plane.</t> | the qubits managed by the quantum data plane.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Abstract Model of the Network</name> | ||||
<section title="Abstract model of the network"> | <section numbered="true" toc="default"> | |||
<name>The Control Plane and the Data Plane</name> | ||||
<section title="The control and data planes"> | <t>Control plane protocols for quantum networks will have many | |||
<t>Control plane protocols for quantum networks will have many | ||||
responsibilities similar to their classical counterparts, namely | responsibilities similar to their classical counterparts, namely | |||
discovering the network topology, resource management, populating data | discovering the network topology, resource management, populating data | |||
plane tables, etc. Most of these protocols do not require the | plane tables, etc. Most of these protocols do not require the | |||
manipulation of quantum data and can operate simply by exchanging | manipulation of quantum data and can operate simply by exchanging | |||
classical messages only. There may also be some control plane | classical messages only. There may also be some control plane | |||
functionality that does require the handling of quantum data, e.g. a | functionality that does require the handling of quantum data | |||
quantum ping <xref target="I-D.irtf-qirg-quantum-internet-use-cases" | <xref target="I-D.irtf-qirg-quantum-internet-use-cases" format="default | |||
/>. As it is not clear if there is much benefit in defining a separate | "/>. As it is not clear if there is much benefit in defining a separate | |||
quantum control plane given the significant overlap in | quantum control plane given the significant overlap in | |||
responsibilities with its classical counterpart, the question of | responsibilities with its classical counterpart, the question of | |||
whether there should be a separate quantum control plane is beyond the | whether there should be a separate quantum control plane is beyond the | |||
scope of this document.</t> | scope of this document.</t> | |||
<t>However, the data plane separation is much more distinct, and there | ||||
<t>However, the data plane separation is much more distinct and there | ||||
will be two data planes: a classical data plane and a quantum data | will be two data planes: a classical data plane and a quantum data | |||
plane. The classical data plane processes and forwards classical | plane. The classical data plane processes and forwards classical | |||
packets. The quantum data plane processes and swaps entangled pairs. | packets. The quantum data plane processes and swaps entangled pairs. | |||
Third generation quantum networks may also forward qubits in addition | Third-generation quantum networks may also forward qubits in addition | |||
to swapping Bell pairs.</t> | to swapping Bell pairs.</t> | |||
<t>In addition to control plane messages, there will also be control | ||||
<t>In addition to control plane messages, there will also be control | ||||
information messages that operate at the granularity of individual | information messages that operate at the granularity of individual | |||
entangled pairs, such as heralding messages used for elementary link | entangled pairs, such as heralding messages used for elementary link | |||
generation (<xref target="elg" />). In terms of functionality, these | generation (<xref target="elg" format="default"/>). In terms of functio nality, these | |||
messages are closer to classical packet headers than control plane | messages are closer to classical packet headers than control plane | |||
messages and thus we consider them to be part of the quantum data | messages, and thus we consider them to be part of the quantum data | |||
plane. Therefore, a quantum data plane also includes the exchange of | plane. Therefore, a quantum data plane also includes the exchange of | |||
classical control information at the granularity of individual qubits | classical control information at the granularity of individual qubits | |||
and entangled pairs.</t> | and entangled pairs.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Elements of a Quantum Network</name> | ||||
<section title="Elements of a quantum network"> | <t>We have identified quantum repeaters as the core building block of | |||
<t>We have identified quantum repeaters as the core building block of | ||||
a quantum network. However, a quantum repeater will have to do more | a quantum network. However, a quantum repeater will have to do more | |||
than just entanglement swapping in a functional quantum network. Its | than just entanglement swapping in a functional quantum network. Its | |||
key responsibilities will include:</t> | key responsibilities will include the following:</t> | |||
<ol spacing="normal" type="1"><li>Creating link-local entanglement bet | ||||
<t> | ween neighbouring | |||
<list style="numbers"> | nodes.</li> | |||
<li>Extending entanglement from link-local pairs to long-range | ||||
<t>Creating link-local entanglement between neighbouring | pairs through entanglement swapping.</li> | |||
nodes.</t> | <li>Performing distillation to manage the fidelity of the produced | |||
pairs.</li> | ||||
<t>Extending entanglement from link-local pairs to long-range | <li>Participating in the management of the network (routing, | |||
pairs through entanglement swapping.</t> | etc.).</li> | |||
</ol> | ||||
<t>Performing distillation to manage the fidelity of the produced | <t>Not all quantum repeaters in the network will be the same; here, we | |||
pairs.</t> | ||||
<t>Participating in the management of the network (routing, | ||||
etc.).</t> | ||||
</list> | ||||
</t> | ||||
<t>Not all quantum repeaters in the network will be the same; here we | ||||
break them down further:</t> | break them down further:</t> | |||
<dl spacing="normal"> | ||||
<t> | <dt>Quantum routers (controllable quantum nodes):</dt><dd>A quantum | |||
<list style="symbols"> | router | |||
<t>Quantum routers (controllable quantum nodes) - A quantum router | ||||
is a quantum repeater with a control plane that participates in | is a quantum repeater with a control plane that participates in | |||
the management of the network and will make decisions about which | the management of the network and will make decisions about which | |||
qubits to swap to generate the requested end-to-end pairs.</t> | qubits to swap to generate the requested end-to-end pairs.</dd> | |||
<dt>Automated quantum nodes:</dt><dd>An automated quantum node is a | ||||
<t>Automated quantum nodes - An automated quantum node is a data | data-plane-only quantum repeater that does not participate in the | |||
plane only quantum repeater that does not participate in the | ||||
network control plane. Since the no-cloning theorem precludes the | network control plane. Since the no-cloning theorem precludes the | |||
use of amplification, long-range links will be established by | use of amplification, long-range links will be established by | |||
chaining multiple such automated nodes together.</t> | chaining multiple such automated nodes together.</dd> | |||
<dt>End nodes:</dt><dd>End nodes in a quantum network must be able t | ||||
<t>End-nodes - End-nodes in a quantum network must be able to | o | |||
receive and handle an entangled pair, but they do not need to be | receive and handle an entangled pair, but they do not need to be | |||
able to perform an entanglement swap (and thus are not necessarily | able to perform an entanglement swap (and thus are not necessarily | |||
quantum repeaters). End-nodes are also not required to have any | quantum repeaters). End nodes are also not required to have any | |||
quantum memory as certain quantum applications can be realised by | quantum memory, as certain quantum applications can be realised by | |||
having the end-node measure its qubit as soon as it is | having the end node measure its qubit as soon as it is | |||
received.</t> | received.</dd> | |||
<dt>Non-quantum nodes:</dt><dd>Not all nodes in a quantum network ne | ||||
<t>Non-quantum nodes - Not all nodes in a quantum network need to | ed to | |||
have a quantum data plane. A non-quantum node is any device that | have a quantum data plane. A non-quantum node is any device that | |||
can handle classical network traffic.</t> | can handle classical network traffic.</dd> | |||
</dl> | ||||
</list> | <t>Additionally, we need to identify two kinds of links that will be | |||
</t> | ||||
<t>Additionally, we need to identify two kinds of links that will be | ||||
used in a quantum network:</t> | used in a quantum network:</t> | |||
<dl spacing="normal"> | ||||
<t> | <dt>Quantum links:</dt><dd>A quantum link is a link that can be used | |||
<list style="symbols"> | to | |||
<t>Quantum links - A quantum link is a link which can be used to | ||||
generate an entangled pair between two directly connected quantum | generate an entangled pair between two directly connected quantum | |||
repeaters. This may include additional mid-point elements | repeaters. This may include additional mid-point elements as | |||
described in <xref target="elg" />. It may also include a | described in <xref target="elg" format="default"/>. It may also inc | |||
lude a | ||||
dedicated classical channel that is to be used solely for the | dedicated classical channel that is to be used solely for the | |||
purpose of coordinating the entanglement generation on this | purpose of coordinating the entanglement generation on this | |||
quantum link.</t> | quantum link.</dd> | |||
<dt>Classical links:</dt><dd>A classical link is a link between any | ||||
<t>Classical links - A classical link is a link between any node | node | |||
in the network that is capable of carrying classical network | in the network that is capable of carrying classical network | |||
traffic.</t> | traffic.</dd> | |||
</dl> | ||||
</list> | <t>Note that passive elements, such as optical switches, do not | |||
</t> | ||||
<t>Note that passive elements, such as optical switches, do not | ||||
destroy the quantum state. Therefore, it is possible to connect | destroy the quantum state. Therefore, it is possible to connect | |||
multiple quantum nodes with each other over an optical network and | multiple quantum nodes with each other over an optical network and | |||
perform optical switching rather than routing via entanglement | perform optical switching rather than routing via entanglement | |||
swapping at quantum routers. This does require coordination with the | swapping at quantum routers. This does require coordination with the | |||
elementary link entanglement generation process and it still requires | elementary link entanglement generation process, and it still requires | |||
repeaters to overcome the short-distance limitations. However, this is | repeaters to overcome the short-distance limitations. However, this is | |||
a potentially feasible architecture for local area networks.</t> | a potentially feasible architecture for local area networks.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Putting It All Together</name> | ||||
<section title="Putting it all together"> | <t>A two-hop path in a generic quantum network can be represented | |||
as follows:</t> | ||||
<t>A two-hop path in a generic quantum network can be represented | <artwork align="left" name="" type="" alt=""><![CDATA[ | |||
as:</t> | ||||
<figure align="center"> | ||||
<artwork align="left"><![CDATA[ | ||||
+-----+ +-----+ | +-----+ +-----+ | |||
| App |- - - - - - - - - -CC- - - - - - - - - -| App | | | App |- - - - - - - - - -CC- - - - - - - - - -| App | | |||
+-----+ +------+ +-----+ | +-----+ +------+ +-----+ | |||
| EN |------ CL ------| QR |------ CL ------| EN | | | EN |------ CL ------| QR |------ CL ------| EN | | |||
| |------ QL ------| |------ QL ------| | | | |------ QL ------| |------ QL ------| | | |||
+-----+ +------+ +-----+ | +-----+ +------+ +-----+ | |||
App - user-level application | App - user-level application | |||
EN - end-node | EN - End Node | |||
QL - quantum link | QL - Quantum Link | |||
CL - classical link | CL - Classical Link | |||
CC - classical channel (traverses one or more CLs) | CC - Classical Channel (traverses one or more CLs) | |||
QR - quantum repeater | QR - Quantum Repeater | |||
]]></artwork> | ]]></artwork> | |||
</figure> | <t>An application (App) running on two End Nodes (ENs) attached to a | |||
<t>An application (App) running on two end-nodes (ENs) attached to a | ||||
network will at some point need the network to generate entangled | network will at some point need the network to generate entangled | |||
pairs for its use. This may require negotiation between the end-nodes | pairs for its use. This may require negotiation between the ENs | |||
(possibly ahead of time), because they must both open a communication | (possibly ahead of time), because they must both open a communication | |||
end-point which the network can use to identify the two ends of the | end-point that the network can use to identify the two ends of the | |||
connection. The two end-nodes use a classical channel (CC) available | connection. The two ENs use a Classical Channel (CC) available | |||
in the network to achieve this goal.</t> | in the network to achieve this goal.</t> | |||
<t>When the network receives a request to generate end-to-end | ||||
<t>When the network receives a request to generate end-to-end | entangled pairs, it uses the Classical Links (CLs) to | |||
entangled pairs it uses the classical communication links (CLs) to | ||||
coordinate and claim the resources necessary to fulfill this request. | coordinate and claim the resources necessary to fulfill this request. | |||
This may be some combination of prior control information (e.g. | This may be some combination of prior control information (e.g., | |||
routing tables) and signalling protocols, but the details of how this | routing tables) and signalling protocols, but the details of how this | |||
is achieved are an active research question. A thought experiment on | is achieved are an active research question. A thought experiment on | |||
what this might look like be can be found later in this draft in <xref | what this might look like be can be found in <xref target="gedankenexpe | |||
target="gedankenexperiment" />.</t> | riment" format="default"/>.</t> | |||
<t>During or after the distribution of control information, the | ||||
<t>During or after the distribution of control information, the | network performs the necessary quantum operations, such as generating | |||
network performs the necessary quantum operations such as generating | entanglement over individual Quantum Links (QLs), performing | |||
entanglement over individual quantum links (QLs), performing | entanglement swaps at Quantum Repeaters (QRs), and further signalling | |||
entanglement swaps at quantum repeaters (QRs), and further signalling | ||||
to transmit the swap outcomes and other control information. Since | to transmit the swap outcomes and other control information. Since | |||
Bell pairs do not carry any user data, some of these operations can be | Bell pairs do not carry any user data, some of these operations can be | |||
performed before the request is received in anticipation of the | performed before the request is received, in anticipation of the | |||
demand.</t> | demand.</t> | |||
<t>Note that here, "signalling" is used in a very broad sense and | ||||
<t>Note that here, "signalling" is used in a very broad sense and | ||||
covers many different types of messaging necessary for entanglement | covers many different types of messaging necessary for entanglement | |||
generation control. For example, heralded entanglement generation | generation control. For example, heralded entanglement generation | |||
requires very precise timing synchronisation between the neighbouring | requires very precise timing synchronisation between the neighbouring | |||
nodes and thus the triggering of entanglement generation and heralding | nodes, and thus the triggering of entanglement generation and heralding | |||
may happen over its own, perhaps physically separate CL, as was the | may happen over its own, perhaps physically separate, CL, as was the | |||
case in network stack demonstration in <xref target="Pompili21.2" />. | case in the network stack demonstration described in <xref target="Pomp | |||
Higher level signalling with less stringent timing requirements (e.g. | ili21.2" format="default"/>. | |||
Higher-level signalling with timing requirements that are less stringen | ||||
t (e.g., | ||||
control plane signalling) may then happen over its own CL.</t> | control plane signalling) may then happen over its own CL.</t> | |||
<t>The entangled pair is delivered to the application once it is | ||||
<t>The entangled pair is delivered to the application once it is | ||||
ready, together with the relevant pair identifier. However, being | ready, together with the relevant pair identifier. However, being | |||
ready does not necessarily mean that all link pairs and entanglement | ready does not necessarily mean that all link pairs and entanglement | |||
swaps are complete, as some applications can start executing on an | swaps are complete, as some applications can start executing on an | |||
incomplete pair. In this case the remaining entanglement swaps will | incomplete pair. In this case, the remaining entanglement swaps will | |||
propagate the actions across the network to the other end, sometimes | propagate the actions across the network to the other end, sometimes | |||
necessitating fixup operations at the end node.</t> | necessitating fixup operations at the EN.</t> | |||
</section> | ||||
</section> | </section> | |||
<section anchor="phys-constraints" numbered="true" toc="default"> | ||||
</section> | <name>Physical Constraints</name> | |||
<t>The model above has effectively abstracted away the particulars of | ||||
<section title="Physical constraints"> | ||||
<t>The model above has effectively abstracted away the particulars of | ||||
the hardware implementation. However, certain physical constraints need | the hardware implementation. However, certain physical constraints need | |||
to be considered in order to build a practical network. Some of these | to be considered in order to build a practical network. Some of these | |||
are fundamental constraints and no matter how much the technology | are fundamental constraints, and no matter how much the technology | |||
improves, they will always need to be addressed. Others are artifacts of | improves, they will always need to be addressed. Others are artifacts of | |||
the early stages of a new technology. Here, we consider a highly | the early stages of a new technology. Here, we consider a highly | |||
abstract scenario and refer to <xref target="Wehner18"/> for pointers to | abstract scenario and refer to <xref target="Wehner18" format="default"/> for pointers to | |||
the physics literature.</t> | the physics literature.</t> | |||
<section numbered="true" toc="default"> | ||||
<section title="Memory lifetimes"> | <name>Memory Lifetimes</name> | |||
<t>In addition to discrete operations being imperfect, storing a qubit | ||||
<t>In addition to discrete operations being imperfect, storing a qubit | ||||
in memory is also highly non-trivial. The main difficulty in achieving | in memory is also highly non-trivial. The main difficulty in achieving | |||
persistent storage is that it is extremely challenging to isolate a | persistent storage is that it is extremely challenging to isolate a | |||
quantum system from the environment. The environment introduces an | quantum system from the environment. The environment introduces an | |||
uncontrollable source of noise into the system which affects the | uncontrollable source of noise into the system, which affects the | |||
fidelity of the state. This process is known as decoherence. | fidelity of the state. This process is known as decoherence. | |||
Eventually, the state has to be discarded once its fidelity degrades | Eventually, the state has to be discarded once its fidelity degrades | |||
too much.</t> | too much.</t> | |||
<t>The memory lifetime depends on the particular physical setup, but | ||||
<t>The memory lifetime depends on the particular physical setup, but | the highest achievable values in quantum network hardware | |||
the highest achievable values in quantum network hardware currently | are, as of 2020, on the order of seconds <xref target="Abobeih18" forma | |||
are on the order of seconds <xref target="Abobeih18" /> although a | t="default"/>, although a | |||
lifetime of a minute has also been demonstrated for qubits not | lifetime of a minute has also been demonstrated for qubits not | |||
connected to a quantum network <xref target="Bradley19" /> (as of | connected to a quantum network <xref target="Bradley19" format="default | |||
2020). These values have increased tremendously over the lifetime of | "/>. These values have increased tremendously over the lifetime of | |||
the different technologies and are bound to keep increasing. However, | the different technologies and are bound to keep increasing. However, | |||
if quantum networks are to be realised in the near future, they need | if quantum networks are to be realised in the near future, they need | |||
to be able to handle short memory lifetimes, for example by reducing | to be able to handle short memory lifetimes -- for example, by reducing | |||
latency on critical paths.</t> | latency on critical paths.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Rates</name> | ||||
<section title="Rates"> | <t>Entanglement generation on a link between two connected nodes is | |||
not a very efficient process, and it requires many attempts to succeed | ||||
<t>Entanglement generation on a link between two connected nodes is | <xref target="Hensen15" format="default"/> <xref target="Dahlberg19" fo | |||
not a very efficient process and it requires many attempts to succeed | rmat="default"/>. For example, | |||
<xref target="Hensen15" /> <xref target="Dahlberg19" />. For example, | ||||
the highest achievable rates of success between nitrogen-vacancy | the highest achievable rates of success between nitrogen-vacancy | |||
center nodes, which in addition to entanglement generation are also | center nodes -- which, in addition to entanglement generation are also | |||
capable of storing and processing the resulting qubits, are on the | capable of storing and processing the resulting qubits -- are on the | |||
order of 10 Hz. Combined with short memory lifetimes this leads to | order of 10 Hz. Combined with short memory lifetimes, this leads to | |||
very tight timing windows to build up network-wide connectivity.</t> | very tight timing windows to build up network-wide connectivity.</t> | |||
<t>Other platforms have shown higher entanglement rates, but this | ||||
<t>Other platforms have shown higher entanglement rates, but this | ||||
usually comes at the cost of other hardware capabilities, such as no | usually comes at the cost of other hardware capabilities, such as no | |||
quantum memory and/or limited processing capabilities <xref | quantum memory and/or limited processing capabilities <xref target="Wei | |||
target="Wei22" />. Nevertheless, the current rates are not sufficient | 22" format="default"/>. Nevertheless, the current rates are not sufficient | |||
for practical applications beyond simple experimental proofs of | for practical applications beyond simple experimental proofs of | |||
concept. However, they are expected to improve over time as quantum | concept. However, they are expected to improve over time as quantum | |||
network technology evolves <xref target="Wei22" />.</t> | network technology evolves <xref target="Wei22" format="default"/>.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Communication Qubits</name> | ||||
<section title="Communication qubits"> | <t>Most physical architectures capable of storing qubits are only able | |||
<t>Most physical architectures capable of storing qubits are only able | ||||
to generate entanglement using only a subset of available qubits | to generate entanglement using only a subset of available qubits | |||
called communication qubits <xref target="Dahlberg19" />. Once a Bell | called communication qubits <xref target="Dahlberg19" format="default"/ >. Once a Bell | |||
pair has been generated using a communication qubit, its state can be | pair has been generated using a communication qubit, its state can be | |||
transferred into memory. This may impose additional limitations on the | transferred into memory. This may impose additional limitations on the | |||
network. In particular, if a given node has only one communication | network. In particular, if a given node has only one communication | |||
qubit it cannot simultaneously generate Bell pairs over two links. It | qubit, it cannot simultaneously generate Bell pairs over two links. It | |||
must generate entanglement over the links one at a time.</t> | must generate entanglement over the links one at a time.</t> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Homogeneity</name> | ||||
<section title="Homogeneity"> | <t>At present, all existing quantum network implementations are | |||
homogeneous, and they do not interface with each other. In general, it | ||||
<t>Currently all existing quantum network implementations are | ||||
homogeneous and they do not interface with each other. In general, it | ||||
is very challenging to combine different quantum information | is very challenging to combine different quantum information | |||
processing technologies.</t> | processing technologies.</t> | |||
<t>There are many different physical hardware platforms for | ||||
<t>There are many different physical hardware platforms for | ||||
implementing quantum networking hardware. The different technologies | implementing quantum networking hardware. The different technologies | |||
differ in how they store and manipulate qubits in memory and how they | differ in how they store and manipulate qubits in memory and how they | |||
generate entanglement across a link with their neighbours. For | generate entanglement across a link with their neighbours. For | |||
example, hardware based on optical elements and atomic ensembles <xref | example, hardware based on optical elements and atomic ensembles <xref | |||
target="Sangouard11" /> is very efficient at generating entanglement | target="Sangouard11" format="default"/> is very efficient at generating entangle | |||
at high rates, but provides limited processing capabilities once the | ment | |||
entanglement is generated. On the other hand, nitrogen-vacancy based | at high rates but provides limited processing capabilities once the | |||
<xref target="Hensen15" /> or trapped ion <xref target="Moehring07" /> | entanglement is generated. On the other hand, nitrogen-vacancy-based | |||
platforms offer a much greater degree of control over the qubits, but | platforms <xref target="Hensen15" format="default"/> or trapped ion pla | |||
tforms <xref target="Moehring07" format="default"/> | ||||
offer a much greater degree of control over the qubits but | ||||
have a harder time generating entanglement at high rates.</t> | have a harder time generating entanglement at high rates.</t> | |||
<t>In order to overcome the weaknesses of the different platforms, | ||||
<t>In order to overcome the weaknesses of the different platforms, | ||||
coupling the different technologies will help to build fully | coupling the different technologies will help to build fully | |||
functional networks. For example, end-nodes may be implemented using | functional networks. For example, end nodes may be implemented using | |||
technology with good qubit processing capabilities to enable complex | technology with good qubit processing capabilities to enable complex | |||
applications, but automated quantum nodes that that serve only to | applications, but automated quantum nodes that serve only to | |||
"repeat" along a linear chain, where the processing logic is much | "repeat" along a linear chain, where the processing logic is much | |||
simpler, can be implemented with technologies that sacrifice | simpler, can be implemented with technologies that sacrifice | |||
processing capabilities for higher entanglement rates at long | processing capabilities for higher entanglement rates at long | |||
distances <xref target="Askarani21" />.</t> | distances <xref target="Askarani21" format="default"/>.</t> | |||
<t>This point is further exacerbated by the fact that quantum | ||||
<t>This point is further exacerbated by the fact that quantum | computers (i.e., end nodes in a quantum network) are often based on | |||
computers (i.e. end-nodes in a quantum network) are often based on | different hardware platforms than quantum repeaters, thus requiring a | |||
different hardware platforms than quantum repeaters thus requiring a | ||||
coupling (transduction) between the two. This is especially true for | coupling (transduction) between the two. This is especially true for | |||
quantum computers based on superconducting technology which are | quantum computers based on superconducting technology, which are | |||
challenging to connect to optical networks. However, even trapped ion | challenging to connect to optical networks. However, even trapped ion | |||
quantum computers, which is a platform that has shown promise for | quantum computers, which make up a platform that has shown promise for | |||
quantum networking, will still need to connect to other platforms that | quantum networking, will still need to connect to other platforms that | |||
are better at creating entanglement at high rates over long distances | are better at creating entanglement at high rates over long distances | |||
(hundreds of kms).</t> | (hundreds of kilometres).</t> | |||
</section> | ||||
</section> | </section> | |||
</section> | ||||
</section> | <section numbered="true" toc="default"> | |||
<name>Architectural Principles</name> | ||||
</section> | <t>Given that the most practical way of realising quantum network | |||
connectivity is using Bell pair and entanglement-swapping repeater | ||||
<section title="Architectural principles"> | ||||
<t>Given that the most practical way of realising quantum network | ||||
connectivity is using Bell pair and entanglement swapping repeater | ||||
technology, what sort of principles should guide us in assembling such | technology, what sort of principles should guide us in assembling such | |||
networks such that they are functional, robust, efficient, and most | networks such that they are functional, robust, efficient, and, most | |||
importantly, do they work? Furthermore, how do we design networks so that | importantly, will work? Furthermore, how do we design networks so that | |||
they work under the constraints imposed by the hardware available today, | they work under the constraints imposed by the hardware available today | |||
but do not impose unnecessary burdens on future technology?</t> | but do not impose unnecessary burdens on future technology?</t> | |||
<t>As quantum networking is a completely new technology that is likely to | ||||
<t>As quantum networking is a completely new technology that is likely to | see many iterations over its lifetime, this document must not serve as a | |||
see many iterations over its lifetime, this draft must not serve as a | definitive set of rules but merely as a general set of recommended | |||
definitive set of rules, but merely as a general set of recommended | ||||
guidelines for the first generations of quantum networks based on | guidelines for the first generations of quantum networks based on | |||
principles and observations made by the community. The benefit of having a | principles and observations made by the community. The benefit of having a | |||
community built document at this early stage is that expertise in both | community-built document at this early stage is that expertise in both | |||
quantum information and network architecture is needed in order to | quantum information and network architecture is needed in order to | |||
successfully build a quantum internet.</t> | successfully build a quantum internet.</t> | |||
<section anchor="goals" numbered="true" toc="default"> | ||||
<section title="Goals of a quantum internet"> | <name>Goals of a Quantum Internet</name> | |||
<t>When outlining any set of principles, we must ask ourselves what goal | ||||
<t>When outlining any set of principles we must ask ourselves what goals | s | |||
do we want to achieve as inevitably trade-offs must be made. So what | we want to achieve, as inevitably trade-offs must be made. So, what | |||
sort of goals should drive a quantum network architecture? The following | sort of goals should drive a quantum network architecture? The following | |||
list has been inspired by the history of computer networking and thus it | list has been inspired by the history of computer networking, and thus it | |||
is inevitably very similar to one that could be produced for the | is inevitably very similar to one that could be produced for the | |||
classical Internet <xref target="Clark88" />. However, whilst the goals | classical Internet <xref target="Clark88" format="default"/>. However, wh | |||
may be similar the challenges involved are often fundamentally | ilst the goals | |||
may be similar, the challenges involved are often fundamentally | ||||
different. The list will also most likely evolve with time and the needs | different. The list will also most likely evolve with time and the needs | |||
of its users.</t> | of its users.</t> | |||
<ol spacing="normal" type="1"><li> | ||||
<t>Support distributed quantum applications. | ||||
</t> | ||||
<t> | ||||
<t> | This goal seems trivially obvious, but it makes a subtle, but importa | |||
<list style="numbers"> | nt, | |||
<t>Support distributed quantum applications | point that highlights a key difference between quantum and | |||
<vspace blankLines="1" /> | ||||
This goal seems trivially obvious, but makes a subtle, but important | ||||
point which highlights a key difference between quantum and | ||||
classical networks. Ultimately, quantum data transmission is not the | classical networks. Ultimately, quantum data transmission is not the | |||
goal of a quantum network - it is only one possible component of | goal of a quantum network -- it is only one possible component of | |||
more advanced quantum application protocols <xref target="Wehner18" | quantum application protocols that are more advanced <xref target="We | |||
/>. Whilst transmission certainly could be used as a building block | hner18" format="default"/>. Whilst transmission certainly could be used as a bui | |||
lding block | ||||
for all quantum applications, it is not the most basic one possible. | for all quantum applications, it is not the most basic one possible. | |||
For example, entanglement-based QKD, the most well known quantum | For example, entanglement-based QKD, the most well-known quantum | |||
application protocol, only relies on the stronger-than-classical | application protocol, only relies on the stronger-than-classical | |||
correlations and inherent secrecy of entangled Bell pairs and does | correlations and inherent secrecy of entangled Bell pairs and does | |||
not have to transmit arbitrary quantum states <xref target="Ekert91" | not have to transmit arbitrary quantum states <xref target="Ekert91" | |||
/>. | format="default"/>. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
The primary purpose of a quantum internet is to support distributed | The primary purpose of a quantum internet is to support distributed | |||
quantum application protocols and it is of utmost importance that | quantum application protocols, and it is of utmost importance that | |||
they can run well and efficiently. Thus, it is important to develop | they can run well and efficiently. Thus, it is important to develop | |||
performance metrics meaningful to application to drive the | performance metrics meaningful to applications to drive the | |||
development of quantum network protocols. For example, the Bell pair | development of quantum network protocols. For example, the Bell pair | |||
generation rate is meaningless if one does not also consider their | generation rate is meaningless if one does not also consider their | |||
fidelity. It is generally much easier to generate pairs of lower | fidelity. It is generally much easier to generate pairs of lower | |||
fidelity, but quantum applications may have to make multiple | fidelity, but quantum applications may have to make multiple | |||
re-attempts or even abort if the fidelity is too low. A review of | reattempts or even abort if the fidelity is too low. A review of | |||
the requirements for different known quantum applications can be | the requirements for different known quantum applications can be | |||
found in <xref target="Wehner18" /> and an overview of use-cases can | found in <xref target="Wehner18" format="default"/>, and an overview | |||
be found in <xref target="I-D.irtf-qirg-quantum-internet-use-cases" | of use cases can | |||
/>.</t> | be found in <xref target="I-D.irtf-qirg-quantum-internet-use-cases" f | |||
ormat="default"/>.</t> | ||||
<t>Support tomorrow's distributed quantum applications | </li> | |||
<vspace blankLines="1" /> | <li> | |||
<t>Support tomorrow's distributed quantum applications. | ||||
</t> | ||||
<t> | ||||
The only principle of the Internet that should survive indefinitely | The only principle of the Internet that should survive indefinitely | |||
is the principle of constant change <xref target="RFC1958" />. | is the principle of constant change <xref target="RFC1958" format="de | |||
Technical change is continuous and the size and capabilities of the | fault"/>. | |||
Technical change is continuous, and the size and capabilities of the | ||||
quantum internet will change by orders of magnitude. Therefore, it | quantum internet will change by orders of magnitude. Therefore, it | |||
is an explicit goal that a quantum internet architecture be able to | is an explicit goal that a quantum internet architecture be able to | |||
embrace this change. We have the benefit of having been witness to | embrace this change. We have the benefit of having been witness to | |||
the evolution of the classical Internet over several decades and | the evolution of the classical Internet over several decades, and we have | |||
seen what worked and what did not. It is vital for a quantum | seen what worked and what did not. It is vital for a quantum | |||
internet to avoid the need for flag days (e.g. NCP to TCP/IP) or | internet to avoid the need for flag days (e.g., NCP to TCP/IP) or | |||
upgrades that take decades to roll out (e.g. IPv4 to IPv6). | upgrades that take decades to roll out (e.g., IPv4 to IPv6). | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
Therefore, it is important that any proposed architecture for | Therefore, it is important that any proposed architecture for | |||
general purpose quantum repeater networks can integrate new devices | general-purpose quantum repeater networks can integrate new devices | |||
and solutions as they become available. The architecture should not | and solutions as they become available. The architecture should not | |||
be constrained due to considerations for early-stage hardware and | be constrained due to considerations for early-stage hardware and | |||
applications. For example, it is already possible to run QKD | applications. For example, it is already possible to run QKD | |||
efficiently on metropolitan scales and such networks are already | efficiently on metropolitan-scale networks, and such networks are alr eady | |||
commercially available. However, they are not based on quantum | commercially available. However, they are not based on quantum | |||
repeaters and thus will not be able to easily transition to more | repeaters and thus will not be able to easily transition to | |||
sophisticated applications.</t> | applications that are more sophisticated.</t> | |||
</li> | ||||
<t>Support heterogeneity | <li> | |||
<vspace blankLines="1" /> | <t>Support heterogeneity. | |||
</t> | ||||
<t> | ||||
There are multiple proposals for realising practical quantum | There are multiple proposals for realising practical quantum | |||
repeater hardware and they all have their advantages and | repeater hardware, and they all have their advantages and | |||
disadvantages. Some may offer higher Bell pair generation rates on | disadvantages. Some may offer higher Bell pair generation rates on | |||
individual links at the cost of more difficult entanglement swap | individual links at the cost of entanglement swap | |||
operations. Other platforms may be good all around, but are more | operations that are more difficult. Other platforms may be good all a | |||
round but are more | ||||
difficult to build. | difficult to build. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
In addition to physical boundaries, there may be distinctions in how | In addition to physical boundaries, there may be distinctions in how | |||
errors are managed (<xref target="generations" />). These difference | errors are managed (<xref target="generations" format="default"/>). T hese differences | |||
will affect the content and semantics of messages that cross these | will affect the content and semantics of messages that cross these | |||
boundaries -- both for connection setup and real-time operation. | boundaries -- for both connection setup and real-time operation. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
The optimal network configuration will likely leverage the | The optimal network configuration will likely leverage the | |||
advantages of multiple platforms to optimise the provided service. | advantages of multiple platforms to optimise the provided service. | |||
Therefore, it is an explicit goal to incorporate varied hardware and | Therefore, it is an explicit goal to incorporate varied hardware and | |||
technology support from the beginning.</t> | technology support from the beginning.</t> | |||
</li> | ||||
<t>Ensure security at the network level | <li> | |||
<vspace blankLines="1" /> | <t>Ensure security at the network level. | |||
</t> | ||||
<t> | ||||
The question of security in quantum networks is just as critical as | The question of security in quantum networks is just as critical as | |||
it is in the classical Internet, especially since enhanced security | it is in the classical Internet, especially since enhanced security | |||
offered by quantum entanglement is one of the key driving factors. | offered by quantum entanglement is one of the key driving factors. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
Fortunately, from an application's point of view, as long as the | Fortunately, from an application's point of view, as long as the | |||
underlying implementation corresponds to (or sufficiently | underlying implementation corresponds to (or sufficiently | |||
approximates) theoretical models of quantum cryptography, quantum | approximates) theoretical models of quantum cryptography, quantum | |||
cryptographic protocols do not need the network to provide any | cryptographic protocols do not need the network to provide any | |||
guarantees about the confidentiality or integrity of the transmitted | guarantees about the confidentiality or integrity of the transmitted | |||
qubits or the generated entanglement (though they may impose | qubits or the generated entanglement (though they may impose | |||
requirements on the classical channel, e.g to be authenticated <xref | requirements on the classical channel, e.g., to be authenticated <xre | |||
target="Wang21" />). Instead, applications will leverage the | f target="Wang21" format="default"/>). Instead, applications will leverage the | |||
classical networks to establish the end-to-end security of the | classical networks to establish the end-to-end security of the | |||
results obtained from the processing of entangled qubits. However, | results obtained from the processing of entangled qubits. However, | |||
it is important to note that whilst classical networks are necessary | it is important to note that whilst classical networks are necessary | |||
to establish these end-to-end guarantees, the security relies on the | to establish these end-to-end guarantees, the security relies on the | |||
properties of quantum entanglement. For example, QKD uses classical | properties of quantum entanglement. For example, QKD uses classical | |||
information reconciliation <xref target= "Tang19" /> for error | information reconciliation <xref target="Tang19" format="default"/> f | |||
correction and privacy amplification <xref target= "Elkouss11" /> | or error | |||
correction and privacy amplification <xref target="Elkouss11" format= | ||||
"default"/> | ||||
for generating the final secure key, but the raw bits that are fed | for generating the final secure key, but the raw bits that are fed | |||
into these protocols must come from measuring entangled qubits <xref | into these protocols must come from measuring entangled qubits <xref | |||
target="Ekert91" />. In another application, secure delegated | target="Ekert91" format="default"/>. In another application, secure delegated | |||
quantum computing, the client hides its computation from the server | quantum computing, the client hides its computation from the server | |||
by sending qubits to the server and then requesting it (in a | by sending qubits to the server and then requesting (in a | |||
classical message) to measure them in an encoded basis. The client | classical message) that the server measure them in an encoded basis. | |||
The client | ||||
then decodes the results it receives from the server to obtain the | then decodes the results it receives from the server to obtain the | |||
result of the computation <xref target= "Broadbent10" />. Once | result of the computation <xref target="Broadbent10" format="default" | |||
/>. | ||||
Once | ||||
again, whilst a classical network is used to achieve the goal of | again, whilst a classical network is used to achieve the goal of | |||
secure computation, the remote computation is strictly quantum. | secure computation, the remote computation is strictly quantum. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
Nevertheless, whilst applications can ensure their own end-to-end | Nevertheless, whilst applications can ensure their own end-to-end | |||
security, network protocols themselves should be security aware in | security, network protocols themselves should be security aware in | |||
order to protect the network itself and limit disruption. Whilst the | order to protect the network itself and limit disruption. Whilst the | |||
applications remain secure they are not necessarily operational or | applications remain secure, they are not necessarily operational or | |||
as efficient in the presence of an attacker. For example, if an | as efficient in the presence of an attacker. For example, if an | |||
attacker can measure every qubit between two parties trying to | attacker can measure every qubit between two parties trying to | |||
establish a key using QKD, no secret key can be generated. Security | establish a key using QKD, no secret key can be generated. Security | |||
concerns in quantum networks are described in more detail in <xref | concerns in quantum networks are described in more detail in <xref ta | |||
target="Satoh17" /> <xref target="Satoh20" />.</t> | rget="Satoh17" format="default"/> and <xref target="Satoh20" format="default"/>. | |||
</t> | ||||
<t>Make them easy to monitor | </li> | |||
<vspace blankLines="1" /> | <li> | |||
<t>Make them easy to monitor. | ||||
</t> | ||||
<t> | ||||
In order to manage, evaluate the performance of, or debug a network | In order to manage, evaluate the performance of, or debug a network, | |||
it is necessary to have the ability to monitor the network while | it is necessary to have the ability to monitor the network while | |||
ensuring there will be mechanisms in place to protect the | ensuring that there will be mechanisms in place to protect the | |||
confidentiality and integrity of the devices connected to it. | confidentiality and integrity of the devices connected to it. | |||
Quantum networks bring new challenges in this area so it should be a | Quantum networks bring new challenges in this area, so it should be a | |||
goal of a quantum network architecture to make this task easy. | goal of a quantum network architecture to make this task easy. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
The fundamental unit of quantum information, the qubit, cannot be | The fundamental unit of quantum information, the qubit, cannot be | |||
actively monitored as any readout irreversibly destroys its | actively monitored, as any readout irreversibly destroys its | |||
contents. One of the implications of this fact is that measuring an | contents. One of the implications of this fact is that measuring an | |||
individual pair's fidelity is impossible. Fidelity is meaningful | individual pair's fidelity is impossible. Fidelity is meaningful | |||
only as a statistical quantity which requires the constant | only as a statistical quantity that requires constant | |||
monitoring and the sacrifice of generated Bell pairs for tomography | monitoring of generated Bell pairs, achieved by sacrificing some Bell | |||
pairs for use in tomography | ||||
or other methods. | or other methods. | |||
<vspace blankLines="1" /> | </t> | |||
<t> | ||||
Furthermore, given one end of an entangled pair, it is impossible to | Furthermore, given one end of an entangled pair, it is impossible to | |||
tell where the other qubit is without any additional classical | tell where the other qubit is without any additional classical | |||
metadata. It is impossible to extract this information from the | metadata. It is impossible to extract this information from the | |||
qubits themselves. This implies that tracking entangled pairs | qubits themselves. This implies that tracking entangled pairs | |||
necessitates some exchange of classical information. This | necessitates some exchange of classical information. This | |||
information might include (i) a reference to the entangled pair that | information might include (i) a reference to the entangled pair that | |||
allows distributed applications to coordinate actions on qubits of | allows distributed applications to coordinate actions on qubits of | |||
the same pair, and (ii) the two bits from each entanglement swap | the same pair and (ii) the two bits from each entanglement swap | |||
necessary to identify the final state of the Bell pair (<xref | necessary to identify the final state of the Bell pair (<xref target= | |||
target="es" />).</t> | "es" format="default"/>).</t> | |||
</li> | ||||
<t>Ensure availability and resilience | <li> | |||
<vspace blankLines="1" /> | <t>Ensure availability and resilience. | |||
</t> | ||||
<t> | ||||
Any practical and usable network, classical or quantum, must be able | Any practical and usable network, classical or quantum, must be able | |||
to continue to operate despite losses and failures, and be robust to | to continue to operate despite losses and failures and be robust to | |||
malicious actors trying to disable connectivity. What differs in | malicious actors trying to disable connectivity. A difference between | |||
quantum networks as compared to classical networks in this regard is | quantum and classical networks is that quantum networks are composed | |||
that we now have two data planes and two types of channels to worry | of | |||
about: a quantum and a classical one. Therefore, availability and | two types of data planes (quantum and classical) and two types of | |||
channels (quantum and classical) that must be considered. | ||||
Therefore, availability and | ||||
resilience will most likely require a more advanced treatment than | resilience will most likely require a more advanced treatment than | |||
they do in classical networks.</t> | they do in classical networks.</t> | |||
</li> | ||||
</list> | </ol> | |||
</t> | <t>Note that privacy, whilst related to security, is not listed as an | |||
<t>Note that privacy, whilst related to security, is not listed as an | ||||
explicit goal, because the privacy benefits will depend on the use case. | explicit goal, because the privacy benefits will depend on the use case. | |||
For example, QKD only provides increased security for the distribution | For example, QKD only provides increased security for the distribution | |||
of symmetric keys <xref target="Bennett14" /> <xref target="Ekert91" />. | of symmetric keys <xref target="Bennett14" format="default"/> <xref targe t="Ekert91" format="default"/>. | |||
The handling, manipulation, sharing, encryption, and decryption of data | The handling, manipulation, sharing, encryption, and decryption of data | |||
will remain entirely classical limiting the benefits to privacy that can | will remain entirely classical, limiting the benefits to privacy that can | |||
be gained from using a quantum network. On the other hand, there are | be gained from using a quantum network. On the other hand, there are | |||
applications like blind quantum computation which provides the user with | applications like blind quantum computation, which provides the user with | |||
the ability to execute a quantum computation on a remote server without | the ability to execute a quantum computation on a remote server without | |||
the server knowing what the computation was or its input and output | the server knowing what the computation was or its input and output | |||
<xref target="Fitzsimons17" />. Therefore, privacy must be considered on | <xref target="Fitzsimons17" format="default"/>. Therefore, privacy must b e considered on | |||
a per-application basis. An overview of quantum network use cases can be | a per-application basis. An overview of quantum network use cases can be | |||
found in <xref target="I-D.irtf-qirg-quantum-internet-use-cases" />.</t> | found in <xref target="I-D.irtf-qirg-quantum-internet-use-cases" format=" | |||
default"/>.</t> | ||||
</section> | </section> | |||
<section numbered="true" toc="default"> | ||||
<section title="The principles of a quantum internet"> | <name>The Principles of a Quantum Internet</name> | |||
<t>The principles support the goals but are not goals themselves. The | ||||
<t>The principles support the goals, but are not goals themselves. The | goals define what we want to build, and the principles provide a | |||
goals define what we want to build and the principles provide a | guideline for how we might achieve this. The goals will also be the | |||
guideline in how we might achieve this. The goals will also be the | ||||
foundation for defining any metric of success for a network | foundation for defining any metric of success for a network | |||
architecture, whereas the principles in themselves do not distinguish | architecture, whereas the principles in themselves do not distinguish | |||
between success and failure. For more information about design | between success and failure. For more information about design | |||
considerations for quantum networks see <xref target="VanMeter13.1" /> | considerations for quantum networks, see <xref target="VanMeter13.1" form | |||
<xref target="Dahlberg19" />.</t> | at="default"/> and | |||
<xref target="Dahlberg19" format="default"/>.</t> | ||||
<t> | <ol spacing="normal" type="1"><li> | |||
<list style="numbers"> | <t>Entanglement is the fundamental service. | |||
<t>Entanglement is the fundamental service | </t> | |||
<vspace blankLines="1" /> | <t> | |||
The key service that a quantum network provides is the distribution | The key service that a quantum network provides is the distribution | |||
of entanglement between the nodes in a network. All distributed | of entanglement between the nodes in a network. All distributed | |||
quantum applications are built on top of this key resource. | quantum applications are built on top of this key resource. | |||
Applications such as clustered quantum computing, distributed | Applications such as clustered quantum computing, distributed | |||
quantum computing, distributed quantum sensing networks, and certain | quantum computing, distributed quantum sensing networks, and certain | |||
kinds of quantum secure networks all consume quantum entanglement as | kinds of quantum secure networks all consume quantum entanglement as | |||
a resource. Some applications (e.g. quantum key distribution) simply | a resource. Some applications (e.g., QKD) simply | |||
measure the entangled qubits to obtain a shared secret key <xref | measure the entangled qubits to obtain a shared secret key <xref targ | |||
target="QKD" />. Other applications (e.g. distributed quantum | et="QKD" format="default"/>. Other applications (e.g., distributed quantum | |||
computing) build more complex abstractions and operations on the | computing) build abstractions and operations that are | |||
entangled qubits, e.g., distributed CNOT gates <xref | more complex on the entangled qubits, e.g., distributed CNOT gates <x | |||
target="DistCNOT" /> or teleportation of arbitrary qubit states | ref target="DistCNOT" format="default"/> or teleportation of arbitrary qubit sta | |||
<xref target="Teleportation" />. | tes | |||
<vspace blankLines="1" /> | <xref target="Teleportation" format="default"/>. | |||
</t> | ||||
<t> | ||||
A quantum network may also distribute multipartite entangled states | A quantum network may also distribute multipartite entangled states | |||
(entangled states of three or more qubits) <xref target="Meignant19" | (entangled states of three or more qubits) <xref target="Meignant19" | |||
/> which are useful for applications such as conference key | format="default"/>, which are useful for applications such as conference key | |||
agreement <xref target="Murta20" />, distributed quantum computing | agreement <xref target="Murta20" format="default"/>, distributed quan | |||
<xref target="Cirac99" />, secret sharing <xref target="Qin17" />, | tum computing | |||
and clock synchronisation <xref target="Komar14" />. Though it was | <xref target="Cirac99" format="default"/>, secret sharing <xref targe | |||
t="Qin17" format="default"/>, | ||||
and clock synchronisation <xref target="Komar14" format="default"/>, | ||||
though it is | ||||
worth noting that multipartite entangled states can also be | worth noting that multipartite entangled states can also be | |||
constructed from multiple entangled pairs distributed between the | constructed from multiple entangled pairs distributed between the | |||
end-nodes.</t> | end nodes.</t> | |||
</li> | ||||
<t>Bell Pairs are indistinguishable | <li> | |||
<vspace blankLines="1" /> | <t>Bell pairs are indistinguishable. | |||
</t> | ||||
<t> | ||||
Any two Bell Pairs between the same two nodes are indistinguishable | Any two Bell pairs between the same two nodes are indistinguishable | |||
for the purposes of an application provided they both satisfy its | for the purposes of an application, provided they both satisfy its | |||
required fidelity threshold. This observation is likely to be key in | required fidelity threshold. This observation is likely to be key in | |||
enabling a more optimal allocation of resources in a network, e.g. | enabling a more optimal allocation of resources in a network, e.g., | |||
for the purposes of provisioning resources to meet application | for the purposes of provisioning resources to meet application | |||
demand. However, the qubits that make up the pair themselves are not | demand. However, the qubits that make up the pair themselves are not | |||
indistinguishable and the two nodes operating on a pair must | indistinguishable, and the two nodes operating on a pair must | |||
coordinate to make sure they are operating on qubits that belong to | coordinate to make sure they are operating on qubits that belong to | |||
the same Bell pair.</t> | the same Bell pair.</t> | |||
</li> | ||||
<t>Fidelity is part of the service | <li> | |||
<vspace blankLines="1" /> | <t>Fidelity is part of the service. | |||
</t> | ||||
<t> | ||||
In addition to being able to deliver Bell pairs to the communication | In addition to being able to deliver Bell pairs to the communication | |||
end-points, the Bell Pairs must be of sufficient fidelity. Unlike in | end-points, the Bell pairs must be of sufficient fidelity. Unlike in | |||
classical networks where most errors are effectively eliminated | classical networks, where most errors are effectively eliminated | |||
before reaching the application, many quantum applications only need | before reaching the application, many quantum applications only need | |||
imperfect entanglement to function. However, quantum applications | imperfect entanglement to function. However, quantum applications | |||
will generally have a threshold for Bell pair fidelity below which | will generally have a threshold for Bell pair fidelity below which | |||
they are no longer able to operate. Different applications will have | they are no longer able to operate. Different applications will have | |||
different requirements for what fidelity they can work with. It is | different requirements for what fidelity they can work with. It is | |||
the network's responsibility to balance the resource usage with | the network's responsibility to balance the resource usage with | |||
respect to the applications' requirements. It may be that it is | respect to the applications' requirements. It may be that it is | |||
cheaper for the network to provide lower fidelity pairs that are | cheaper for the network to provide lower-fidelity pairs that are | |||
just above the threshold required by the application than it is to | just above the threshold required by the application than it is to | |||
guarantee high fidelity pairs to all applications regardless of | guarantee high-fidelity pairs to all applications regardless of | |||
their requirements.</t> | their requirements.</t> | |||
</li> | ||||
<li> | ||||
<t>Time is an expensive resource. | ||||
</t> | ||||
<t> | ||||
<t>Time is an expensive resource | Time is not the only resource that is in short supply (communication | |||
<vspace blankLines="1" /> | qubits and memory are as well), but ultimately it is the lifetime | |||
Time is not the only resource that is in short supply (memory, and | ||||
communication qubits are as well), but ultimately it is the lifetime | ||||
of quantum memories that imposes some of the most difficult | of quantum memories that imposes some of the most difficult | |||
conditions for operating an extended network of quantum nodes. | conditions for operating an extended network of quantum nodes. | |||
Current hardware has low rates of Bell pair generation, short memory | Current hardware has low rates of Bell pair generation, short memory | |||
lifetimes, and access to a limited number of communication qubits. | lifetimes, and access to a limited number of communication qubits. | |||
All these factors combined mean that even a short waiting queue at | All these factors combined mean that even a short waiting queue at | |||
some node could be enough for a Bell pair to decohere or result in | some node could be enough for a Bell pair to decohere or result in | |||
an end-to-end pair below an application's fidelity threshold. | an end-to-end pair below an application's fidelity threshold. | |||
Therefore, managing the idle time of qubits holding live quantum | Therefore, managing the idle time of qubits holding live quantum | |||
states should be done carefully. Ideally by minimising the idle | states should be done carefully -- ideally by minimising the idle | |||
time, but potentially also by moving the quantum state for temporary | time, but potentially also by moving the quantum state for temporary | |||
storage to a quantum memory with a longer lifetime.</t> | storage to a quantum memory with a longer lifetime.</t> | |||
</li> | ||||
<li> | ||||
<t>Be flexible with regards to capabilities and limitations. | ||||
</t> | ||||
<t> | ||||
<t>Be flexible with regards to capabilities and limitations | This goal encompasses two important points:</t> | |||
<vspace blankLines="1" /> | ||||
This goal encompasses two important points. First, the architecture | <ul spacing="normal"> | |||
<li>First, the architecture | ||||
should be able to function under the physical constraints imposed by | should be able to function under the physical constraints imposed by | |||
the current generation hardware. Near-future hardware will have low | the current-generation hardware. Near-future hardware will have low | |||
entanglement generation rates, quantum memories able to hold a | entanglement generation rates, quantum memories able to hold a | |||
handful of qubits at best, and decoherence rates that will render | handful of qubits at best, and decoherence rates that will render | |||
many generated pairs unusable. | many generated pairs unusable.</li> | |||
<vspace blankLines="1" /> | ||||
Second, the architecture should not make it difficult to run the | <li>Second, the architecture should not make it difficult to run the | |||
network over any hardware that may come along in the future. The | network over any hardware that may come along in the future. The | |||
physical capabilities of repeaters will improve and redeploying a | physical capabilities of repeaters will improve, and redeploying a | |||
technology is extremely challenging.</t> | technology is extremely challenging.</li> | |||
</ul> | ||||
</list> | </li> | |||
</t> | </ol> | |||
</section> | ||||
</section> | </section> | |||
<section anchor="gedankenexperiment" numbered="true" toc="default"> | ||||
</section> | <name>A Thought Experiment Inspired by Classical Networks</name> | |||
<t>To conclude, we discuss a plausible quantum network architecture | ||||
<section title="A thought experiment inspired by classical networks" anchor=" | inspired by MPLS. This is not an architecture proposal but rather a | |||
gedankenexperiment"> | ||||
<t>To conclude, we discuss a plausible quantum network architecture | ||||
inspired by MPLS. This is not an architecture proposal, but rather a | ||||
thought experiment to give the reader an idea of what components are | thought experiment to give the reader an idea of what components are | |||
necessary for a functional quantum network. We use classical MPLS as a | necessary for a functional quantum network. We use classical MPLS as a | |||
basis as it is well known and understood in the networking community.</t> | basis, as it is well known and understood in the networking community.</t> | |||
<t>Creating end-to-end Bell pairs between remote end-points is a stateful | ||||
<t>Creating end-to-end Bell pairs between remote end-points is a stateful | distributed task that requires a lot of a priori coordination. Therefore, | |||
distributed task that requires a lot of a-priori coordination. Therefore, | ||||
a connection-oriented approach seems the most natural for quantum | a connection-oriented approach seems the most natural for quantum | |||
networks. In connection-oriented quantum networks, when two quantum | networks. In connection-oriented quantum networks, when two quantum | |||
application end-points wish to start creating end-to-end Bell pairs, they | application end-points wish to start creating end-to-end Bell pairs, they | |||
must first create a quantum virtual circuit (QVC). As an analogy, in MPLS | must first create a Quantum Virtual Circuit (QVC). As an analogy, in MPLS | |||
networks end-points must establish a label switched path (LSP) before | networks, end-points must establish a Label Switched Path (LSP) before | |||
exchanging traffic. Connection-oriented quantum networks may also support | exchanging traffic. Connection-oriented quantum networks may also support | |||
virtual circuits with multiple end-points for creating multipartite | virtual circuits with multiple end-points for creating multipartite | |||
entanglement. As an analogy, MPLS networks have the concept of multi-point | entanglement. As an analogy, MPLS networks have the concept of multipoint | |||
LSPs for multicast.</t> | LSPs for multicast.</t> | |||
<t>When a quantum application creates a QVC, it can | ||||
<t>When a quantum application creates a quantum virtual circuit, it can | indicate Quality of Service (QoS) parameters such as the required capacity | |||
indicate quality of service (QoS) parameters such as the required capacity | in end-to-end Bell Pairs Per Second (BPPS) and the required fidelity of | |||
in end-to-end Bell pairs per second (BPPS) and the required fidelity of | the Bell pairs. As an analogy, in MPLS networks, applications specify the | |||
the Bell pairs. As an analogy, in MPLS networks applications specify the | required bandwidth in Bits Per Second (BPS) and other constraints when | |||
required bandwidth in bits per second (BPS) and other constraints when | ||||
they create a new LSP.</t> | they create a new LSP.</t> | |||
<t>Different applications will have different QoS requirements. For | ||||
<t>Different applications will have different QoS requirements. For | example, applications such as QKD that don't need to process the | |||
example, applications such as QKD, that don't need to process the | entangled qubits, and only need measure them and store the resulting | |||
entangled qubits and only need measure them and store the resulting | outcome, may require a large volume of entanglement but will be tolerant | |||
outcome, may require a large volume of entanglement, but will be tolerant | ||||
of delay and jitter for individual pairs. On the other hand, | of delay and jitter for individual pairs. On the other hand, | |||
distributed/cloud quantum computing applications may need fewer entangled | distributed/cloud quantum computing applications may need fewer entangled | |||
pairs, but instead, may need all of them to be generated in one go so that | pairs but instead may need all of them to be generated in one go so that | |||
they can be processed all together before any of them decohere.</t> | they can all be processed together before any of them decohere.</t> | |||
<t>Quantum networks need a routing function to compute the optimal path | ||||
<t>Quantum networks need a routing function to compute the optimal path | (i.e., the best sequence of routers and links) for each new QVC. The routin | |||
(i.e. the best sequence of routers and links) for each new quantum virtual | g function may be centralised or distributed. In the | |||
circuit. The routing function may be centralized or distributed. In the | ||||
latter case, the quantum network needs a distributed routing protocol. As | latter case, the quantum network needs a distributed routing protocol. As | |||
an analogy, classical networks use routing protocols such as open shortest | an analogy, classical networks use routing protocols such as Open Shortest | |||
path first (OSPF) and intermediate-system to intermediate system (IS-IS). | Path First (OSPF) and Intermediate System to Intermediate System (IS-IS). | |||
However, note that the definition of "shortest-path"/"least-cost" may be | However, note that the definition of "shortest path" / "least cost" may be | |||
different in a quantum network to account for its non-classical features, | different in a quantum network to account for its non-classical features, | |||
such as fidelity <xref target="VanMeter13.2" />.</t> | such as fidelity <xref target="VanMeter13.2" format="default"/>.</t> | |||
<t>Given the very scarce availability of resources in early quantum | ||||
<t>Given the very scarce availability of resources in early quantum | networks, a Traffic Engineering (TE) function is likely to be beneficial. | |||
networks, a traffic engineering function is likely to be beneficial. | Without TE, QVCs always use the | |||
Without traffic engineering, quantum virtual circuits always use the | ||||
shortest path. In this case, the quantum network cannot guarantee that | shortest path. In this case, the quantum network cannot guarantee that | |||
each quantum end-point will get its Bell pairs at the required rate or | each quantum end-point will get its Bell pairs at the required rate or | |||
fidelity. This is analogous to "best effort" service in classical | fidelity. This is analogous to "best effort" service in classical | |||
networks.</t> | networks.</t> | |||
<t>With TE, QVCs choose a path that | ||||
<t>With traffic engineering, quantum virtual circuits choose a path that | is guaranteed to have the requested resources (e.g., bandwidth in BPPS) | |||
is guaranteed to have the requested resources (e.g. bandwidth in BPPS) | ||||
available, taking into account the capacity of the routers and links and | available, taking into account the capacity of the routers and links and | |||
taking into account the resources already consumed by other virtual | also taking into account the resources already consumed by other virtual | |||
circuits. As an analogy, both OSPF and IS-IS have traffic engineering (TE) | circuits. As an analogy, both OSPF and IS-IS have TE | |||
extensions to keep track of used and available resources, and can use | extensions to keep track of used and available resources and can use | |||
constrained shortest path first (CSPF) to take resource availability and | Constrained Shortest Path First (CSPF) to take resource availability and | |||
other constraints into account when computing the optimal path.</t> | other constraints into account when computing the optimal path.</t> | |||
<t>The use of TE implies the use of Call Admission | ||||
<t>The use of traffic engineering implies the use of call admission | Control (CAC): the network denies any virtual circuits for which it cannot | |||
control (CAC): the network denies any virtual circuits for which it cannot | guarantee the requested quality of service a priori. Alternatively, the | |||
guarantee the requested quality of service a-priori. Or alternatively, the | network preempts lower-priority circuits to make room for a new | |||
network pre-empts lower priority circuits to make room for the new | circuit.</t> | |||
one.</t> | <t>Quantum networks need a signalling function: once the path for a | |||
QVC has been computed, signalling is used to install the | ||||
<t>Quantum networks need a signaling function: once the path for a quantum | ||||
virtual circuit has been computed, signaling is used to install the | ||||
"forwarding rules" into the data plane of each quantum router on the path. | "forwarding rules" into the data plane of each quantum router on the path. | |||
The signaling may be distributed, analogous to the resource reservation | The signalling may be distributed, analogous to the Resource Reservation | |||
protocol (RSVP) in MPLS. Or the signaling may be centralized, similar to | Protocol (RSVP) in MPLS. Or, the signalling may be centralised, similar to | |||
OpenFlow.</t> | OpenFlow.</t> | |||
<t>Quantum networks need an abstraction of the hardware for specifying the | ||||
<t>Quantum networks need an abstraction of the hardware for specifying the | forwarding rules. This allows us to decouple the control plane (routing | |||
forwarding rules. This allows us to de-couple the control plane (routing | and signalling) from the data plane (actual creation of Bell pairs). The | |||
and signaling) from the data plane (actual creation of Bell pairs). The | ||||
forwarding rules are specified using abstract building blocks such as | forwarding rules are specified using abstract building blocks such as | |||
"creating local Bell pairs", "swapping Bell pairs", "distillation of Bell | "creating local Bell pairs", "swapping Bell pairs", or "distillation of Bel l | |||
pairs". As an analogy, classical networks use abstractions that are based | pairs". As an analogy, classical networks use abstractions that are based | |||
on match conditions (e.g. looking up header fields in tables) and actions | on match conditions (e.g., looking up header fields in tables) and actions | |||
(e.g. modifying fields or forwarding a packet to a specific interface). | (e.g., modifying fields or forwarding a packet to a specific interface). | |||
The data-plane abstractions in quantum networks will be very different | The data plane abstractions in quantum networks will be very different | |||
from those in classical networks due to the fundamental differences in | from those in classical networks due to the fundamental differences in | |||
technology and the stateful nature of quantum networks. In fact, choosing | technology and the stateful nature of quantum networks. In fact, choosing | |||
the right abstractions will be one of the biggest challenges when | the right abstractions will be one of the biggest challenges when | |||
designing interoperable quantum network protocols.</t> | designing interoperable quantum network protocols.</t> | |||
<t>In quantum networks, control plane traffic (routing and signalling | ||||
<t>In quantum networks, control plane traffic (routing and signaling | ||||
messages) is exchanged over a classical channel, whereas data plane | messages) is exchanged over a classical channel, whereas data plane | |||
traffic (the actual Bell pair qubits) is exchanged over a separate quantum | traffic (the actual Bell pair qubits) is exchanged over a separate quantum | |||
channel. This is in contrast to most classical networks, where control | channel. This is in contrast to most classical networks, where control | |||
plane traffic and data plane traffic share the same channel and where a | plane traffic and data plane traffic share the same channel and where a | |||
single packet contains both user fields and header fields. There is, | single packet contains both user fields and header fields. There is, | |||
however, a classical analogy to the way quantum networks work. Generalized | however, a classical analogy to the way quantum networks work: generalised | |||
MPLS (GMPLS) networks use separate channels for control plane traffic and | MPLS (GMPLS) networks use separate channels for control plane traffic and | |||
data plane traffic. Furthermore, GMPLS networks support data planes where | data plane traffic. Furthermore, GMPLS networks support data planes where | |||
there is no such thing as data plane headers (e.g. DWDM or TDM | there is no such thing as data plane headers (e.g., Dense Wavelength Divisi on Multiplexing (DWDM) or Time-Division Multiplexing (TDM) | |||
networks).</t> | networks).</t> | |||
</section> | ||||
</section> | <section anchor="Security" numbered="true" toc="default"> | |||
<name>Security Considerations</name> | ||||
<section anchor="Security" title="Security Considerations"> | <t>Security is listed as an explicit goal for the architecture; this | |||
<t>Security is listed as an explicit goal for the architecture and this | issue is addressed in <xref target="goals"/>. However, as this is an | |||
issue is addressed in the section on goals. However, as this is an | Informational document, it does not propose any concrete mechanisms to achi | |||
informational draft it does not propose any concrete mechanisms to achieve | eve | |||
these goals.</t> | these goals.</t> | |||
</section> | ||||
</section> | <section anchor="IANA" numbered="true" toc="default"> | |||
<name>IANA Considerations</name> | ||||
<section anchor="IANA" title="IANA Considerations"> | <t>This document has no IANA actions.</t> | |||
<t>This draft includes no request to IANA.</t> | </section> | |||
</section> | </middle> | |||
<!-- Possibly a 'Contributors' section ... --> | ||||
<section anchor="Acknowledgements" title="Acknowledgements"> | ||||
<t>The authors want to thank Carlo Delle Donne, Matthew Skrzypczyk, Axel | ||||
Dahlberg, Mathias van den Bossche, Patrick Gelard, Chonggang Wang, Scott | ||||
Fluhrer, Joey Salazar, Joseph Touch, and the rest of the QIRG community as | ||||
a whole for their very useful reviews and comments to the document.</t> | ||||
<!-- TODO: fill out acks appropriately to IETF rules --> | ||||
</section> | ||||
</middle> | ||||
<!-- *****BACK MATTER ***** --> | ||||
<back> | <back> | |||
<!-- References split into informative and normative --> | ||||
<!-- There are 2 ways to insert reference entries from the citation libraries | ||||
: | ||||
1. define an ENTITY at the top, and use "ampersand character"RFC2629; here ( | ||||
as shown) | ||||
2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml | ||||
"?> here | ||||
(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.x | ||||
ml") | ||||
Both are cited textually in the same manner: by using xref elements. | ||||
If you use the PI option, xml2rfc will, by default, try to find included fil | ||||
es in the same | ||||
directory as the including file. You can also define the XML_LIBRARY environ | ||||
ment variable | ||||
with a value containing a set of directories to search. These can be either | ||||
in the local | ||||
filing system or remote ones accessed by http (http://domain/dir/... ).--> | ||||
<references title="Informative References"> | ||||
<!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2 | ||||
119.xml"?--> | ||||
&rfc1958; | ||||
&I-D.irtf-qirg-quantum-internet-use-cases; | ||||
<reference anchor="Pompili21.1" target="https://arxiv.org/abs/2102.04471"> | ||||
<front> | ||||
<title>Realization of a multi-node quantum network of remote solid-stat | ||||
e qubits</title> | ||||
<author initials="M" surname="Pompili" /> | ||||
<author initials="S.L.N" surname="Hermans" /> | ||||
<author initials="S" surname="Baier" /> | ||||
<author initials="H.K.C" surname="Beukers" /> | ||||
<author initials="P.C" surname="Humphreys" /> | ||||
<author initials="R.N" surname="Schouten" /> | ||||
<author initials="R.F.L" surname="Vermeulen" /> | ||||
<author initials="M.J" surname="Tiggelman" /> | ||||
<author initials="L" surname="dos Santos Martins" /> | ||||
<author initials="B" surname="Dirkse" /> | ||||
<author initials="S" surname="Wehner" /> | ||||
<author initials="R" surname="Hanson" /> | ||||
<date year="2021" /> | ||||
</front> | ||||
<seriesInfo name="Science" value="Vol. 372, Iss. 6539, pp. 259-264" /> | ||||
</reference> | ||||
<reference anchor="Bennett14" target="https://arxiv.org/abs/2003.06557"> | ||||
<front> | ||||
<title>Quantum cryptography: Public key distribution and coin tossing</ | ||||
title> | ||||
<author initials="C.H" surname="Bennett" /> | ||||
<author initials="G" surname="Brassard" /> | ||||
<date year="2014" /> | ||||
</front> | ||||
<seriesInfo name="Theoretical Computer Science" value="Vol. 560 (Part 1), | ||||
pp. 7-11" /> | ||||
</reference> | ||||
<reference anchor="Ekert91" target="https://journals.aps.org/prl/abstract/1 | ||||
0.1103/PhysRevLett.67.661"> | ||||
<front> | ||||
<title>Quantum cryptography based on Bell's theorem</title> | ||||
<author initials="A.K" surname="Ekert" /> | ||||
<date year="1991" /> | ||||
</front> | ||||
<seriesInfo name="Physical Review Letters" value="Vol. 67, Iss. 6, pp. 66 | ||||
1-663" /> | ||||
</reference> | ||||
<reference anchor="Cirac99" target="https://arxiv.org/abs/quant-ph/9803017" | ||||
> | ||||
<front> | ||||
<title>Distributed quantum computation over noisy channels</title> | ||||
<author initials="J.I" surname="Cirac" /> | ||||
<author initials="A.K" surname="Ekert" /> | ||||
<author initials="S.F" surname="Huelga" /> | ||||
<author initials="C" surname="Macchiavello" /> | ||||
</front> | ||||
<seriesInfo name="Physical Review A" value="Vol. 59, Iss. 6, pp. 4249" /> | ||||
</reference> | ||||
<reference anchor="Crepeau02" target="https://arxiv.org/abs/quant-ph/020613 | ||||
8"> | ||||
<front> | ||||
<title>Secure multi-party quantum computation</title> | ||||
<author initials="C" surname="Crepeau" /> | ||||
<author initials="D" surname="Gottesman" /> | ||||
<author initials="A" surname="Smith" /> | ||||
<date year="2002" /> | ||||
</front> | ||||
<seriesInfo name="Proceedings of the thiry-fourth annual ACM symposium on | ||||
Theory of computing" value="pp. 643-652" /> | ||||
</reference> | ||||
<reference anchor="Giovanetti04" target="https://arxiv.org/abs/quant-ph/041 | ||||
2078"> | ||||
<front> | ||||
<title>Quantum-enhanced measurements: beating the standard quantum limi | ||||
t</title> | ||||
<author initials="V" surname="Giovanetti" /> | ||||
<author initials="S" surname="Lloyd" /> | ||||
<author initials="L" surname="Maccone" /> | ||||
<date year="2004" /> | ||||
</front> | ||||
<seriesInfo name="Science" value="Vol. 306, Iss. 5700, pp. 1330-1336" /> | ||||
</reference> | ||||
<reference anchor="Wehner18" 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" /> | ||||
<author initials="D" surname="Elkouss" /> | ||||
<author initials="R" surname="Hanson" /> | ||||
<date year="2018" /> | ||||
</front> | ||||
<seriesInfo name="Science" value="Vol. 362, Iss. 6412" /> | ||||
</reference> | ||||
<reference anchor="Aspect81" target="https://journals.aps.org/prl/abstract/ | ||||
10.1103/PhysRevLett.47.460"> | ||||
<front> | ||||
<title>Experimental tests of realistic local theories via Bell's theore | ||||
m</title> | ||||
<author initials="A" surname="Aspect" /> | ||||
<author initials="P" surname="Grangier" /> | ||||
<author initials="G" surname="Roger" /> | ||||
<date year="1981" /> | ||||
</front> | ||||
<seriesInfo name="Physical Review Letters" value="Vol. 47, Iss. 7, pp. 46 | ||||
0-463" /> | ||||
</reference> | ||||
<reference anchor="Mural16" target="https://www.nature.com/articles/srep204 | ||||
63"> | ||||
<front> | ||||
<title>Optimal architectures for long distance quantum communication</t | ||||
itle> | ||||
<author initials="S" surname="Muralidharan" /> | ||||
<author initials="L" surname="Li" /> | ||||
<author initials="J" surname="Kim" /> | ||||
<author initials="N" surname="Lutkenhaus" /> | ||||
<author initials="M" surname="Lukin" /> | ||||
<author initials="L" surname="Jiang" /> | ||||
<date year="2016" /> | ||||
</front> | ||||
<seriesInfo name="Scientific Reports" value="Vol. 6, Iss. 1, pp. 1-10" /> | ||||
</reference> | ||||
<reference anchor="VanMeter13.1" target="https://ieeexplore.ieee.org/docume | ||||
nt/6576340"> | ||||
<front> | ||||
<title>Designing quantum repeater networks</title> | ||||
<author initials="R" surname="Van Meter" /> | ||||
<author initials="J" surname="Touch" /> | ||||
<date year="2013" /> | ||||
</front> | ||||
<seriesInfo name="IEEE Communications Magazine" value="Vol. 51, Iss. 8, p | ||||
p. 64-71" /> | ||||
</reference> | ||||
<reference anchor="Satoh20" target="https://arxiv.org/abs/2005.04617"> | ||||
<front> | ||||
<title>Attacking the quantum internet</title> | ||||
<author initials="T" surname="Satoh" /> | ||||
<author initials="S" surname="Nagayama" /> | ||||
<author initials="S" surname="Suzuki" /> | ||||
<author initials="T" surname="Matsuo" /> | ||||
<author initials="R" surname="Van Meter" /> | ||||
<date year="2020" /> | ||||
</front> | ||||
<seriesInfo name="arXiv" value="2005.04617" /> | ||||
</reference> | ||||
<reference anchor="Satoh17" target="https://arxiv.org/abs/1701.04587"> | ||||
<front> | ||||
<title>The network impact of hijacking a quantum repeater</title> | ||||
<author initials="T" surname="Satoh" /> | ||||
<author initials="S" surname="Nagayama" /> | ||||
<author initials="R" surname="Van Meter" /> | ||||
<date year="2017" /> | ||||
</front> | ||||
<seriesInfo name="Quantum Science and Technology" value="Vol. 3, Iss. 3, | ||||
pp. 034008" /> | ||||
</reference> | ||||
<reference anchor="Dahlberg19" target="https://arxiv.org/abs/1903.09778"> | ||||
<front> | ||||
<title>A link layer protocol for quantum networks</title> | ||||
<author initials="A" surname="Dahlberg" /> | ||||
<author initials="M" surname="Skrzypczyk" /> | ||||
<author initials="T" surname="Coopmans" /> | ||||
<author initials="L" surname="Wubben" /> | ||||
<author initials="F" surname="Rozpedek" /> | ||||
<author initials="M" surname="Pompili" /> | ||||
<author initials="A" surname="Stolk" /> | ||||
<author initials="P" surname="Pawelczak" /> | ||||
<author initials="R" surname="Knegjens" /> | ||||
<author initials="J" surname="de Oliveira Filho" /> | ||||
<author initials="R" surname="Hanson" /> | ||||
<author initials="S" surname="Wehner" /> | ||||
<date year="2019" /> | ||||
</front> | ||||
<seriesInfo name="Proceedings of the ACM Special Interest Group on Data C | ||||
ommunication" value="pp. 159-173" /> | ||||
</reference> | ||||
<reference anchor="SutorBook"> | ||||
<front> | ||||
<title>Dancing with Qubits</title> | ||||
<author initials="R.S" surname="Sutor" /> | ||||
<date year="2019" /> | ||||
</front> | ||||
<seriesInfo name="Packt Publishing" value="" /> | ||||
</reference> | ||||
<reference anchor="NielsenChuang"> | ||||
<front> | ||||
<title>Quantum Computation and Quantum Information</title> | ||||
<author initials="M.A" surname="Nielsen" /> | ||||
<author initials="I.L" surname="Chuang" /> | ||||
<date year="2011" /> | ||||
</front> | ||||
<seriesInfo name="Cambridge University Press" value="" /> | ||||
</reference> | ||||
<reference anchor="Bennett96" target="https://arxiv.org/abs/quant-ph/960402 | ||||
4"> | ||||
<front> | ||||
<title>Mixed state entanglement and quantum error correction</title> | ||||
<author initials="C.H" surname="Bennett" /> | ||||
<author initials="D.P" surname="DiVincenzo" /> | ||||
<author initials="J.A" surname="Smolin" /> | ||||
<author initials="W.K" surname="Wootters" /> | ||||
<date year="1996" /> | ||||
</front> | ||||
<seriesInfo name="Physical Review A" value="Vol. 54, Iss. 5, pp. 3824-385 | ||||
1" /> | ||||
</reference> | ||||
<reference anchor="Bennett93" target="https://journals.aps.org/prl/abstract | ||||
/10.1103/PhysRevLett.70.1895"> | ||||
<front> | ||||
<title>Teleporting an unknown quantum state via dual classical and Eins | ||||
tein-Podolsky-Rosen channels</title> | ||||
<author initials="C.H" surname="Bennett" /> | ||||
<author initials="G" surname="Brassard" /> | ||||
<author initials="C" surname="Crepeau" /> | ||||
<author initials="R" surname="Jozsa" /> | ||||
<author initials="A" surname="Peres" /> | ||||
<author initials="W.K" surname="Wootters" /> | ||||
<date year="1993" /> | ||||
</front> | ||||
<seriesInfo name="Physical Review Letters" value="Vol. 70, Iss. 13, pp. 1 | ||||
895-1899" /> | ||||
</reference> | ||||
<reference anchor="Briegel98" target="https://arxiv.org/abs/quant-ph/980305 | ||||
6"> | ||||
<front> | ||||
<title>Quantum repeaters: The role of imperfect local operations in qua | ||||
ntum communication</title> | ||||
<author initials="H.-J" surname="Briegel" /> | ||||
<author initials="W" surname="Dur" /> | ||||
<author initials="J.I" surname="Cirac" /> | ||||
<author initials="P" surname="Zoller" /> | ||||
<date year="1998" /> | ||||
</front> | ||||
<seriesInfo name="Physical Review Letters" value="Vol. 81, Iss. 26, pp. 5 | ||||
932-5935" /> | ||||
</reference> | ||||
<reference anchor="Cacciapuoti19" target="https://arxiv.org/abs/1907.06197" | ||||
> | ||||
<front> | ||||
<title>When Entanglement meets Classical Communications: Quantum Telepo | ||||
rtation for the Quantum Internet</title> | ||||
<author initials="A.S" surname="Cacciapuoti" /> | ||||
<author initials="M" surname="Caleffi" /> | ||||
<author initials="R" surname="Van Meter" /> | ||||
<author initials="L" surname="Hanzo" /> | ||||
<date year="2019" /> | ||||
</front> | ||||
<seriesInfo name="IEEE Transactions on Communications" value="Vol. 68, Is | ||||
s. 6, pp. 3808-3833" /> | ||||
</reference> | ||||
<reference anchor="Meignant19" target="https://arxiv.org/abs/1811.05445"> | ||||
<front> | ||||
<title>Distributing graph states over arbitrary quantum networks</title | ||||
> | ||||
<author initials="C" surname="Meignant" /> | ||||
<author initials="D" surname="Markham" /> | ||||
<author initials="F" surname="Grosshans" /> | ||||
<date year="2019" /> | ||||
</front> | ||||
<seriesInfo name="Physical Review A" value="Vol. 100, Iss. 5, pp. 052333" | ||||
/> | ||||
</reference> | ||||
<reference anchor="VanMeter13.2" target="https://arxiv.org/abs/1206.5655"> | ||||
<front> | ||||
<title>Path selection for quantum repeater networks</title> | ||||
<author initials="R" surname="Van Meter" /> | ||||
<author initials="T" surname="Satoh" /> | ||||
<author initials="T.D" surname="Ladd" /> | ||||
<author initials="W.J" surname="Munro" /> | ||||
<author initials="K" surname="Nemoto" /> | ||||
<date year="2013" /> | ||||
</front> | ||||
<seriesInfo name="Networking Science" value="Vol. 3, Iss. 1-4, pp. 82-95" | ||||
/> | ||||
</reference> | ||||
<reference anchor="Clark88" target="https://dl.acm.org/doi/abs/10.1145/5232 | ||||
4.52336"> | ||||
<front> | ||||
<title>The design philosophy of the DARPA internet protocols</title> | ||||
<author initials="D" surname="Clark" /> | ||||
<date year="1988" /> | ||||
</front> | ||||
<seriesInfo name="Symposium proceedings on Communications architectures a | ||||
nd protocols" value="pp. 106-114" /> | ||||
</reference> | ||||
<reference anchor="VanMeterBook"> | ||||
<front> | ||||
<title>Quantum Networking</title> | ||||
<author initials="R" surname="Van Meter" /> | ||||
<date year="2014" /> | ||||
</front> | ||||
<seriesInfo name="ISTE Ltd/John Wiley and Sons Inc" value="978-1-84821-53 | ||||
7-5" /> | ||||
</reference> | ||||
<reference anchor="Aguado19" target="http://arxiv.org/abs/1907.00174"> | ||||
<front> | ||||
<title>The engineering of software-defined quantum key distribution net | ||||
works</title> | ||||
<author initials="A" surname="Aguado" /> | ||||
<author initials="V" surname="Lopez" /> | ||||
<author initials="D" surname="Diego" /> | ||||
<author initials="M" surname="Peev" /> | ||||
<author initials="A" surname="Poppe" /> | ||||
<author initials="A" surname="Pastor" /> | ||||
<author initials="J" surname="Folgueira" /> | ||||
<author initials="M" surname="Vicente" /> | ||||
<date year="2019" /> | ||||
</front> | ||||
<seriesInfo name="IEEE Communications Magazine" value="Vol. 57, Iss. 7, p | ||||
p. 20-26" /> | ||||
</reference> | ||||
<reference anchor="Peev09" target="http://stacks.iop.org/1367-2630/11/i=7/a | ||||
=075001"> | ||||
<front> | ||||
<title>The SECOQC quantum key distribution network in Vienna</title> | ||||
<author surname="Peev" initials="M" /> | ||||
<author surname="Pacher" initials="C" /> | ||||
<author surname="Alleaume" initials="R" /> | ||||
<author surname="Barreiro" initials="C" /> | ||||
<author surname="Bouda" initials="J" /> | ||||
<author surname="Boxleitner" initials="W" /> | ||||
<author surname="Debuisschert" initials="T" /> | ||||
<author surname="Diamanti" initials="E" /> | ||||
<author surname="Dianati" initials="M" /> | ||||
<author surname="Dynes" initials="J.F" /> | ||||
<author surname="Fasel" initials="S" /> | ||||
<author surname="Fossier" initials="S" /> | ||||
<author surname="Fuerst" initials="M" /> | ||||
<author surname="Gautier" initials="J.-D" /> | ||||
<author surname="Gay" initials="O" /> | ||||
<author surname="Gisin" initials="N" /> | ||||
<author surname="Grangier" initials="P" /> | ||||
<author surname="Happe" initials="A" /> | ||||
<author surname="Hasani" initials="Y" /> | ||||
<author surname="Hentschel" initials="M" /> | ||||
<author surname="Huebel" initials="H" /> | ||||
<author surname="Humer" initials="G" /> | ||||
<author surname="Laenger" initials="T" /> | ||||
<author surname="Legre" initials="M" /> | ||||
<author surname="Lieger" initials="R" /> | ||||
<author surname="Lodewyck" initials="J" /> | ||||
<author surname="Loruenser" initials="T" /> | ||||
<author surname="Luetkenhaus" initials="N" /> | ||||
<author surname="Marhold" initials="A" /> | ||||
<author surname="Matyus" initials="T" /> | ||||
<author surname="Maurhart" initials="O" /> | ||||
<author surname="Monat" initials="L" /> | ||||
<author surname="Nauerth" initials="S" /> | ||||
<author surname="Page" initials="J.-B" /> | ||||
<author surname="Poppe" initials="A" /> | ||||
<author surname="Querasser" initials="E" /> | ||||
<author surname="Ribordy" initials="G" /> | ||||
<author surname="Robyr" initials="S" /> | ||||
<author surname="Salvail" initials="L" /> | ||||
<author surname="Sharpe" initials="A.W" /> | ||||
<author surname="Shields" initials="A.J" /> | ||||
<author surname="Stucki" initials="D" /> | ||||
<author surname="Suda" initials="M" /> | ||||
<author surname="Tamas" initials="C" /> | ||||
<author surname="Themel" initials="T" /> | ||||
<author surname="Thew" initials="R.T" /> | ||||
<author surname="Thoma" initials="Y" /> | ||||
<author surname="Treiber" initials="A" /> | ||||
<author surname="Trinkler" initials="P" /> | ||||
<author surname="Tualle-Brouri" initials="R" /> | ||||
<author surname="Vannel" initials="F" /> | ||||
<author surname="Walenta" initials="N" /> | ||||
<author surname="Weier" initials="H" /> | ||||
<author surname="Weinfurter" initials="H" /> | ||||
<author surname="Wimberger" initials="I" /> | ||||
<author surname="Yuan" initials="Z.L" /> | ||||
<author surname="Zbinden" initials="H" /> | ||||
<author surname="Zeilinger" initials="A" /> | ||||
<date year="2009" /> | ||||
</front> | ||||
<seriesInfo name="New Journal of Physics" value="Vol. 11, Iss. 7, pp. 075 | ||||
001" /> | ||||
</reference> | ||||
<reference anchor="Hensen15" target="https://arxiv.org/abs/1508.05949"> | ||||
<front> | ||||
<title>Loophole-free Bell inequality violation using electron spins sep | ||||
arated by 1.3 kilometres</title> | ||||
<author surname="Hensen" initials="B" /> | ||||
<author surname="Bernien" initials="H" /> | ||||
<author surname="Dreau" initials="A.E" /> | ||||
<author surname="Reiserer" initials="A" /> | ||||
<author surname="Kalb" initials="N" /> | ||||
<author surname="Blok" initials="M.S" /> | ||||
<author surname="Ruitenberg" initials="J" /> | ||||
<author surname="Vermeulen" initials="R.F.L" /> | ||||
<author surname="Schouten" initials="R.N" /> | ||||
<author surname="Abellan" initials="C" /> | ||||
<author surname="Amaya" initials="W" /> | ||||
<author surname="Pruneri" initials="V" /> | ||||
<author surname="Mitchell" initials="M.W" /> | ||||
<author surname="Markham" initials="M" /> | ||||
<author surname="Twitchen" initials="D.J" /> | ||||
<author surname="Elkouss" initials="D" /> | ||||
<author surname="Wehner" initials="S" /> | ||||
<author surname="Taminiau" initials="T.H" /> | ||||
<author surname="Hanson" initials="R" /> | ||||
<date year="2015" /> | ||||
</front> | ||||
<seriesInfo name="Nature" value="Vol. 526, Iss. 7575, pp. 682-686" /> | ||||
</reference> | ||||
<reference anchor="Fitzsimons17" target="https://arxiv.org/abs/1203.5217"> | ||||
<front> | ||||
<title>Unconditionally verifiable blind quantum computation</title> | ||||
<author surname="Fitzsimons" initials="J.F" /> | ||||
<author surname="Kashefi" initials="E" /> | ||||
<date year="2017" /> | <displayreference target="I-D.irtf-qirg-quantum-internet-use-cases" to="QI-Scena | |||
</front> | rios"/> | |||
<seriesInfo name="Physical Review A" value="Vol. 96, Iss. 1, pp. 012303" | ||||
/> | ||||
</reference> | ||||
<reference anchor="Terhal04" target="https://ieeexplore.ieee.org/document/5 | <references> | |||
388928"> | <name>Informative References</name> | |||
<front> | ||||
<title>Is entanglement monogamous?</title> | ||||
<author surname="Terhal" initials="B.M" /> | <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.1958.xml" /> | |||
<date year="2004" /> | <!-- draft-irtf-qirg-quantum-internet-use-cases (I-D Exists) --> | |||
</front> | <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.i | |||
<seriesInfo name="IBM Journal of Research and Development" value="Vol. 48 | rtf-qirg-quantum-internet-use-cases.xml"/> | |||
, Iss. 1, pp. 71-78" /> | ||||
</reference> | ||||
<reference anchor="Park70" target="https://link.springer.com/content/pdf/10 | <reference anchor="Pompili21.1" target="https://www.science.org/doi/10.112 | |||
.1007/BF00708652.pdf"> | 6/science.abg1919"> | |||
<front> | <front> | |||
<title>The concept of transition in quantum mechanics</title> | <title>Realization of a multinode quantum network of remote solid-stat | |||
e qubits</title> | ||||
<author initials="M" surname="Pompili"/> | ||||
<author initials="S.L.N" surname="Hermans"/> | ||||
<author initials="S" surname="Baier"/> | ||||
<author initials="H.K.C" surname="Beukers"/> | ||||
<author initials="P.C" surname="Humphreys"/> | ||||
<author initials="R.N" surname="Schouten"/> | ||||
<author initials="R.F.L" surname="Vermeulen"/> | ||||
<author initials="M.J" surname="Tiggelman"/> | ||||
<author initials="L" surname="dos Santos Martins"/> | ||||
<author initials="B" surname="Dirkse"/> | ||||
<author initials="S" surname="Wehner"/> | ||||
<author initials="R" surname="Hanson"/> | ||||
<date month="April" year="2021"/> | ||||
</front> | ||||
<refcontent>Science Vol. 372, No. 6539, pp. 259-264</refcontent> | ||||
<seriesInfo name="DOI" value="10.1126/science.abg1919"/> | ||||
</reference> | ||||
<author surname="Park" initials="J.L" /> | <reference anchor="Bennett14" target="https://www.sciencedirect.com/scienc | |||
e/article/pii/S0304397514004241?via%3Dihub"> | ||||
<front> | ||||
<title>Quantum cryptography: Public key distribution and coin tossing< | ||||
/title> | ||||
<author initials="C.H" surname="Bennett"/> | ||||
<author initials="G" surname="Brassard"/> | ||||
<date month="December" year="2014"/> | ||||
</front> | ||||
<refcontent>Theoretical Computer Science Vol. 560 (Part 1), pp. 7-11</re | ||||
fcontent> | ||||
<seriesInfo name="DOI" value="10.1016/j.tcs.2014.05.025"/> | ||||
</reference> | ||||
<date year="1970" /> | <reference anchor="Ekert91" target="https://journals.aps.org/prl/abstract/ | |||
</front> | 10.1103/PhysRevLett.67.661"> | |||
<seriesInfo name="Foundations of Physics" value="Vol. 1, Iss. 1, pp. 23-3 | <front> | |||
3" /> | <title>Quantum cryptography based on Bell's theorem</title> | |||
</reference> | <author initials="A.K" surname="Ekert"/> | |||
<date month="August" year="1991"/> | ||||
</front> | ||||
<refcontent>Physical Review Letters Vol. 67, Iss. 6, pp. 661-663</refcon | ||||
tent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevLett.67.661"/> | ||||
</reference> | ||||
<reference anchor="Wootters82" target="https://www.nature.com/articles/2998 | <reference anchor="Cirac99" target="https://journals.aps.org/pra/abstract/ | |||
02a0"> | 10.1103/PhysRevA.59.4249"> | |||
<front> | <front> | |||
<title>A single quantum cannot be cloned</title> | <title>Distributed quantum computation over noisy channels</title> | |||
<author initials="J.I" surname="Cirac"/> | ||||
<author initials="A.K" surname="Ekert"/> | ||||
<author initials="S.F" surname="Huelga"/> | ||||
<author initials="C" surname="Macchiavello"/> | ||||
<date month="June" year="1999"/> | ||||
</front> | ||||
<refcontent>Physical Review A Vol. 59, Iss. 6, 4249</refcontent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevA.59.4249"/> | ||||
</reference> | ||||
<author surname="Wootters" initials="W.K" /> | <reference anchor="Crepeau02" target="https://dl.acm.org/doi/10.1145/50990 | |||
<author surname="Zurek" initials="W.H" /> | 7.510000"> | |||
<front> | ||||
<title>Secure multi-party quantum computation</title> | ||||
<author initials="C" surname="Crépeau"/> | ||||
<author initials="D" surname="Gottesman"/> | ||||
<author initials="A" surname="Smith"/> | ||||
<date month="May" year="2002"/> | ||||
</front> | ||||
<refcontent>STOC '02: Proceedings of the thiry-fourth [sic] annual ACM s | ||||
ymposium on Theory of computing, pp. 643-652</refcontent> | ||||
<seriesInfo name="DOI" value="10.1145/509907.510000"/> | ||||
</reference> | ||||
<date year="1982" /> | <reference anchor="Giovannetti04" target="https://www.science.org/doi/10.1 | |||
</front> | 126/science.1104149"> | |||
<seriesInfo name="Nature" value="Vol. 299, Iss. 5886, pp. 802-803" /> | <front> | |||
</reference> | <title>Quantum-Enhanced Measurements: Beating the Standard Quantum Lim | |||
it</title> | ||||
<author initials="V" surname="Giovannetti"/> | ||||
<author initials="S" surname="Lloyd"/> | ||||
<author initials="L" surname="Maccone"/> | ||||
<date month="November" year="2004"/> | ||||
</front> | ||||
<refcontent>Science Vol. 306, Iss. 5700, pp. 1330-1336</refcontent> | ||||
<seriesInfo name="DOI" value="10.1126/science.1104149"/> | ||||
</reference> | ||||
<reference anchor="Fowler10" target="https://arxiv.org/abs/0910.4074"> | <reference anchor="Wehner18" target="https://www.science.org/doi/full/10.1 | |||
<front> | 126/science.aam9288"> | |||
<title>Surface code quantum communication</title> | <front> | |||
<title>Quantum internet: A vision for the road ahead</title> | ||||
<author initials="S" surname="Wehner"/> | ||||
<author initials="D" surname="Elkouss"/> | ||||
<author initials="R" surname="Hanson"/> | ||||
<date month="October" year="2018"/> | ||||
</front> | ||||
<refcontent>Science Vol. 362, Iss. 6412</refcontent> | ||||
<seriesInfo name="DOI" value="10.1126/science.aam9288"/> | ||||
</reference> | ||||
<author surname="Fowler" initials="A.G" /> | <reference anchor="Aspect81" target="https://journals.aps.org/prl/abstract | |||
<author surname="Wang" initials="D.S" /> | /10.1103/PhysRevLett.47.460"> | |||
<author surname="Hill" initials="C.D" /> | <front> | |||
<author surname="Ladd" initials="T.D" /> | <title>Experimental Tests of Realistic local Theories via Bell's Theor | |||
<author surname="Van Meter" initials="R" /> | em</title> | |||
<author surname="Hollenberg" initials="L.C.L" /> | <author initials="A" surname="Aspect"/> | |||
<author initials="P" surname="Grangier"/> | ||||
<author initials="G" surname="Roger"/> | ||||
<date month="August" year="1981"/> | ||||
</front> | ||||
<refcontent>Physical Review Letters Vol. 47, Iss. 7, pp. 460-463</refcon | ||||
tent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevLett.47.460"/> | ||||
</reference> | ||||
<date year="2010" /> | <reference anchor="Mural16" target="https://www.nature.com/articles/srep20 | |||
</front> | 463"> | |||
<seriesInfo name="Physical Review Letters" value="Vol. 104, Iss. 18, pp. | <front> | |||
180503" /> | <title>Optimal architectures for long distance quantum communication</ | |||
</reference> | title> | |||
<author initials="S" surname="Muralidharan"/> | ||||
<author initials="L" surname="Li"/> | ||||
<author initials="J" surname="Kim"/> | ||||
<author initials="N" surname="Lütkenhaus"/> | ||||
<author initials="M.D" surname="Lukin"/> | ||||
<author initials="L" surname="Jiang"/> | ||||
<date month="February" year="2016"/> | ||||
</front> | ||||
<refcontent>Scientific Reports Vol. 6, pp. 1-10</refcontent> | ||||
<seriesInfo name="DOI" value="10.1038/srep20463"/> | ||||
</reference> | ||||
<reference anchor="Jiang09" target="https://arxiv.org/abs/0809.3629"> | <reference anchor="VanMeter13.1" target="https://ieeexplore.ieee.org/docum | |||
<front> | ent/6576340"> | |||
<title>Quantum repeater with encoding</title> | <front> | |||
<title>Designing quantum repeater networks</title> | ||||
<author initials="R" surname="Van Meter"/> | ||||
<author initials="J" surname="Touch"/> | ||||
<date month="August" year="2013"/> | ||||
</front> | ||||
<refcontent>IEEE Communications Magazine Vol. 51, Iss. 8, pp. 64-71</ref | ||||
content> | ||||
<seriesInfo name="DOI" value="10.1109/MCOM.2013.6576340"/> | ||||
</reference> | ||||
<author surname="Jiang" initials="L" /> | <reference anchor="Satoh20" target="https://ieeexplore.ieee.org/document/9 | |||
<author surname="Taylor" initials="J.M" /> | 477172"> | |||
<author surname="Nemoto" initials="K" /> | <front> | |||
<author surname="Munro" initials="W.J" /> | <title>Attacking the Quantum Internet</title> | |||
<author surname="Van Meter" initials="R" /> | <author initials="T" surname="Satoh"/> | |||
<author surname="Lukin" initials="M.D" /> | <author initials="S" surname="Nagayama"/> | |||
<author initials="S" surname="Suzuki"/> | ||||
<author initials="T" surname="Matsuo"/> | ||||
<author initials="M" surname="Hajdušek"/> | ||||
<author initials="R" surname="Van Meter"/> | ||||
<date month="September" year="2021"/> | ||||
</front> | ||||
<refcontent>IEEE Transactions on Quantum Engineering, vol. 2, pp. 1-17</ | ||||
refcontent> | ||||
<seriesInfo name="DOI" value="10.1109/TQE.2021.3094983"/> | ||||
</reference> | ||||
<date year="2009" /> | <reference anchor="Satoh17" target="https://iopscience.iop.org/article/10. | |||
</front> | 1088/2058-9565/aac11f"> | |||
<seriesInfo name="Physical Review A" value="Vol. 79, Iss. 3, pp. 032325" | <front> | |||
/> | <title>The network impact of hijacking a quantum repeater</title> | |||
</reference> | <author initials="T" surname="Satoh"/> | |||
<author initials="S" surname="Nagayama"/> | ||||
<author initials="T" surname="Oka"/> | ||||
<author initials="R" surname="Van Meter"/> | ||||
<date month="May" year="2018"/> | ||||
</front> | ||||
<refcontent>Quantum Science and Technology Vol. 3, Iss. 3, 034008 </refc | ||||
ontent> | ||||
<seriesInfo name="DOI" value="10.1088/2058-9565/aac11f"/> | ||||
</reference> | ||||
<reference anchor="Gottesman12" target="https://arxiv.org/abs/1107.2939"> | <reference anchor="Dahlberg19" target="https://dl.acm.org/doi/10.1145/3341 | |||
<front> | 302.3342070"> | |||
<title>Longer-baseline telescopes using quantum repeaters</title> | <front> | |||
<title>A link layer protocol for quantum networks</title> | ||||
<author initials="A" surname="Dahlberg"/> | ||||
<author initials="M" surname="Skrzypczyk"/> | ||||
<author initials="T" surname="Coopmans"/> | ||||
<author initials="L" surname="Wubben"/> | ||||
<author initials="F" surname="Rozpędek"/> | ||||
<author initials="M" surname="Pompili"/> | ||||
<author initials="A" surname="Stolk"/> | ||||
<author initials="P" surname="Pawełczak"/> | ||||
<author initials="R" surname="Knegjens"/> | ||||
<author initials="J" surname="de Oliveira Filho"/> | ||||
<author initials="R" surname="Hanson"/> | ||||
<author initials="S" surname="Wehner"/> | ||||
<date month="August" year="2019"/> | ||||
</front> | ||||
<refcontent>SIGCOMM '19 Proceedings of the ACM Special Interest Group on | ||||
Data Communication, pp. 159-173</refcontent> | ||||
<seriesInfo name="DOI" value="10.1145/3341302.3342070"/> | ||||
</reference> | ||||
<author surname="Gottesman" initials="D" /> | <reference anchor="SutorBook" target="https://www.packtpub.com/product/dan | |||
<author surname="Jennewein" initials="T" /> | cing-with-qubits/9781838827366"> | |||
<author surname="Croke" initials="S" /> | <front> | |||
<title>Dancing with Qubits</title> | ||||
<author initials="R.S" surname="Sutor"/> | ||||
<date month="November" year="2019"/> | ||||
</front> | ||||
<refcontent>Packt Publishing</refcontent> | ||||
</reference> | ||||
<date year="2012" /> | <reference anchor="NielsenChuang" target="http://mmrc.amss.cas.cn/tlb/2017 | |||
</front> | 02/W020170224608149940643.pdf"> | |||
<seriesInfo name="Physical Review Letters" value="Vol. 109, Iss. 7, pp. 0 | <front> | |||
70503" /> | <title>Quantum Computation and Quantum Information</title> | |||
</reference> | <author initials="M.A" surname="Nielsen"/> | |||
<author initials="I.L" surname="Chuang"/> | ||||
<date year="2010"/> | ||||
</front> | ||||
<refcontent>Cambridge University Press</refcontent> | ||||
</reference> | ||||
<reference anchor="ZOO" target="https://wiki.veriqloud.fr/"> | <reference anchor="Bennett96" target="https://journals.aps.org/pra/abstrac | |||
<front> | t/10.1103/PhysRevA.54.3824"> | |||
<title>The Quantum Protocol Zoo</title> | <front> | |||
<title>Mixed-state entanglement and quantum error correction</title> | ||||
<author initials="C.H" surname="Bennett"/> | ||||
<author initials="D.P" surname="DiVincenzo"/> | ||||
<author initials="J.A" surname="Smolin"/> | ||||
<author initials="W.K" surname="Wootters"/> | ||||
<date month="November" year="1996"/> | ||||
</front> | ||||
<refcontent>Physical Review A Vol. 54, Iss. 5, pp. 3824-3851</refcontent | ||||
> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevA.54.3824"/> | ||||
</reference> | ||||
<author /> | <reference anchor="Bennett93" target="https://journals.aps.org/prl/abstrac | |||
t/10.1103/PhysRevLett.70.1895"> | ||||
<front> | ||||
<title>Teleporting an unknown quantum state via dual classical and Ein | ||||
stein-Podolsky-Rosen channels</title> | ||||
<author initials="C.H" surname="Bennett"/> | ||||
<author initials="G" surname="Brassard"/> | ||||
<author initials="C" surname="Crépeau"/> | ||||
<author initials="R" surname="Jozsa"/> | ||||
<author initials="A" surname="Peres"/> | ||||
<author initials="W.K" surname="Wootters"/> | ||||
<date month="March" year="1993"/> | ||||
</front> | ||||
<refcontent>Physical Review Letters Vol. 70, Iss. 13, pp. 1895-1899</ref | ||||
content> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevLett.70.1895"/> | ||||
</reference> | ||||
<date year="" /> | <reference anchor="Briegel98" target="https://journals.aps.org/prl/abstrac | |||
t/10.1103/PhysRevLett.81.5932"> | ||||
<front> | ||||
<title>Quantum Repeaters: The Role of Imperfect Local Operations in Qu | ||||
antum Communication</title> | ||||
<author initials="H.-J" surname="Briegel"/> | ||||
<author initials="W" surname="Dür"/> | ||||
<author initials="J.I" surname="Cirac"/> | ||||
<author initials="P" surname="Zoller"/> | ||||
<date month="December" year="1998"/> | ||||
</front> | ||||
<refcontent>Physical Review Letters Vol. 81, Iss. 26, pp. 5932-5935</ref | ||||
content> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevLett.81.5932"/> | ||||
</reference> | ||||
</front> | <reference anchor="Cacciapuoti19" target="https://ieeexplore.ieee.org/docu | |||
</reference> | ment/9023997"> | |||
<front> | ||||
<title>When Entanglement Meets Classical Communications: Quantum Telep | ||||
ortation for the Quantum Internet</title> | ||||
<author initials="A.S" surname="Cacciapuoti"/> | ||||
<author initials="M" surname="Caleffi"/> | ||||
<author initials="R" surname="Van Meter"/> | ||||
<author initials="L" surname="Hanzo"/> | ||||
<date month="June" year="2020"/> | ||||
</front> | ||||
<refcontent>IEEE Transactions on Communications Vol. 68, Iss. 6, pp. 380 | ||||
8-3833</refcontent> | ||||
<seriesInfo name="DOI" value="10.1109/TCOMM.2020.2978071"/> | ||||
</reference> | ||||
<reference anchor="Dur07" target="https://arxiv.org/abs/0705.4165"> | <reference anchor="Meignant19" target="https://journals.aps.org/pra/abstra | |||
<front> | ct/10.1103/PhysRevA.100.052333"> | |||
<title>Entanglement purification and quantum error correction</title> | <front> | |||
<title>Distributing graph states over arbitrary quantum networks</titl | ||||
e> | ||||
<author initials="C" surname="Meignant"/> | ||||
<author initials="D" surname="Markham"/> | ||||
<author initials="F" surname="Grosshans"/> | ||||
<date month="November" year="2019"/> | ||||
</front> | ||||
<refcontent>Physical Review A Vol. 100, Iss. 5, 052333</refcontent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevA.100.052333"/> | ||||
</reference> | ||||
<author surname="Duer" initials="W" /> | <reference anchor="VanMeter13.2" target="https://link.springer.com/article | |||
<author surname="Briegel" initials="H.J" /> | /10.1007/s13119-013-0026-2"> | |||
<front> | ||||
<title>Path selection for quantum repeater networks</title> | ||||
<author initials="R" surname="Van Meter"/> | ||||
<author initials="T" surname="Satoh"/> | ||||
<author initials="T.D" surname="Ladd"/> | ||||
<author initials="W.J" surname="Munro"/> | ||||
<author initials="K" surname="Nemoto"/> | ||||
<date month="December" year="2013"/> | ||||
</front> | ||||
<refcontent>Networking Science Vol. 3, Iss. 1-4, pp. 82-95</refcontent> | ||||
<seriesInfo name="DOI" value="10.1007/s13119-013-0026-2"/> | ||||
</reference> | ||||
<date year="2007" /> | <reference anchor="Clark88" target="https://dl.acm.org/doi/abs/10.1145/523 | |||
</front> | 24.52336"> | |||
<seriesInfo name="Reports on Progress in Physics" value="Vol. 70, Iss. 8, | <front> | |||
pp. 1381-1424" /> | <title>The design philosophy of the DARPA internet protocols</title> | |||
</reference> | <author initials="D" surname="Clark"/> | |||
<date month="August" year="1988"/> | ||||
</front> | ||||
<refcontent>SIGCOMM '88: Symposium proceedings on Communications archite | ||||
ctures and protocols, pp. 106-114</refcontent> | ||||
<seriesInfo name="DOI" value="10.1145/52324.52336"/> | ||||
</reference> | ||||
<reference anchor="Kimble08" target="http://arxiv.org/abs/0806.4195"> | <reference anchor="VanMeterBook" target="https://onlinelibrary.wiley.com/d | |||
<front> | oi/book/10.1002/9781118648919"> | |||
<title>The Quantum Internet</title> | <front> | |||
<title>Quantum Networking</title> | ||||
<author initials="R" surname="Van Meter"/> | ||||
<date month="April" year="2014"/> | ||||
</front> | ||||
<refcontent>ISTE Ltd/John Wiley and Sons. Inc., Print ISBN 978-1-84821-5 | ||||
37-5</refcontent> | ||||
<seriesInfo name="DOI" value="10.1002/9781118648919"/> | ||||
</reference> | ||||
<author surname="Kimble" initials="H.J" /> | <reference anchor="Aguado19" target="https://ieeexplore.ieee.org/document/ | |||
8767074"> | ||||
<front> | ||||
<title>The Engineering of Software-Defined Quantum Key Distribution Ne | ||||
tworks</title> | ||||
<author initials="A" surname="Aguado"/> | ||||
<author initials="V" surname="Lopez"/> | ||||
<author initials="D" surname="Lopez"/> | ||||
<author initials="M" surname="Peev"/> | ||||
<author initials="A" surname="Poppe"/> | ||||
<author initials="A" surname="Pastor"/> | ||||
<author initials="J" surname="Folgueira"/> | ||||
<author initials="V" surname="Martin"/> | ||||
<date month="July" year="2019"/> | ||||
</front> | ||||
<refcontent>IEEE Communications Magazine Vol. 57, Iss. 7, pp. 20-26</ref | ||||
content> | ||||
<seriesInfo name="DOI" value="10.1109/MCOM.2019.1800763"/> | ||||
</reference> | ||||
<date year="2008" /> | <reference anchor="Peev09" target="https://iopscience.iop.org/article/10.1 | |||
</front> | 088/1367-2630/11/7/075001"> | |||
<seriesInfo name="Nature" value="Vol. 453, Iss. 7198, pp. 1023-1030" /> | <front> | |||
</reference> | <title>The SECOQC quantum key distribution network in Vienna</title> | |||
<author surname="Peev" initials="M"/> | ||||
<author surname="Pacher" initials="C"/> | ||||
<author surname="Alléaume" initials="R"/> | ||||
<author surname="Barreiro" initials="C"/> | ||||
<author surname="Bouda" initials="J"/> | ||||
<author surname="Boxleitner" initials="W"/> | ||||
<author surname="Debuisschert" initials="T"/> | ||||
<author surname="Diamanti" initials="E"/> | ||||
<author surname="Dianati" initials="M"/> | ||||
<author surname="Dynes" initials="J.F"/> | ||||
<author surname="Fasel" initials="S"/> | ||||
<author surname="Fossier" initials="S"/> | ||||
<author surname="Fürst" initials="M"/> | ||||
<author surname="Gautier" initials="J.-D"/> | ||||
<author surname="Gay" initials="O"/> | ||||
<author surname="Gisin" initials="N"/> | ||||
<author surname="Grangier" initials="P"/> | ||||
<author surname="Happe" initials="A"/> | ||||
<author surname="Hasani" initials="Y"/> | ||||
<author surname="Hentschel" initials="M"/> | ||||
<author surname="Hübel" initials="H"/> | ||||
<author surname="Humer" initials="G"/> | ||||
<author surname="Länger" initials="T"/> | ||||
<author surname="Legré" initials="M"/> | ||||
<author surname="Lieger" initials="R"/> | ||||
<author surname="Lodewyck" initials="J"/> | ||||
<author surname="Lorünser" initials="T"/> | ||||
<author surname="Lütkenhaus" initials="N"/> | ||||
<author surname="Marhold" initials="A"/> | ||||
<author surname="Matyus" initials="T"/> | ||||
<author surname="Maurhart" initials="O"/> | ||||
<author surname="Monat" initials="L"/> | ||||
<author surname="Nauerth" initials="S"/> | ||||
<author surname="Page" initials="J.-B"/> | ||||
<author surname="Poppe" initials="A"/> | ||||
<author surname="Querasser" initials="E"/> | ||||
<author surname="Ribordy" initials="G"/> | ||||
<author surname="Robyr" initials="S"/> | ||||
<author surname="Salvail" initials="L"/> | ||||
<author surname="Sharpe" initials="A.W"/> | ||||
<author surname="Shields" initials="A.J"/> | ||||
<author surname="Stucki" initials="D"/> | ||||
<author surname="Suda" initials="M"/> | ||||
<author surname="Tamas" initials="C"/> | ||||
<author surname="Themel" initials="T"/> | ||||
<author surname="Thew" initials="R.T"/> | ||||
<author surname="Thoma" initials="Y"/> | ||||
<author surname="Treiber" initials="A"/> | ||||
<author surname="Trinkler" initials="P"/> | ||||
<author surname="Tualle-Brouri" initials="R"/> | ||||
<author surname="Vannel" initials="F"/> | ||||
<author surname="Walenta" initials="N"/> | ||||
<author surname="Weier" initials="H"/> | ||||
<author surname="Weinfurter" initials="H"/> | ||||
<author surname="Wimberger" initials="I"/> | ||||
<author surname="Yuan" initials="Z.L"/> | ||||
<author surname="Zbinden" initials="H"/> | ||||
<author surname="Zeilinger" initials="A"/> | ||||
<date month="July" year="2009"/> | ||||
</front> | ||||
<refcontent>New Journal of Physics Vol. 11, Iss. 7, 075001</refcontent> | ||||
<seriesInfo name="DOI" value="10.1088/1367-2630/11/7/075001"/> | ||||
</reference> | ||||
<reference anchor="Devitt13" target="https://arxiv.org/abs/0905.2794"> | <reference anchor="Hensen15" target="https://www.nature.com/articles/natur | |||
<front> | e15759"> | |||
<title>Quantum error correction for beginners</title> | <front> | |||
<title>Loophole-free Bell inequality violation using electron spins se | ||||
parated by 1.3 kilometres</title> | ||||
<author surname="Hensen" initials="B"/> | ||||
<author surname="Bernien" initials="H"/> | ||||
<author surname="Dréau" initials="A.E"/> | ||||
<author surname="Reiserer" initials="A"/> | ||||
<author surname="Kalb" initials="N"/> | ||||
<author surname="Blok" initials="M.S"/> | ||||
<author surname="Ruitenberg" initials="J"/> | ||||
<author surname="Vermeulen" initials="R.F.L"/> | ||||
<author surname="Schouten" initials="R.N"/> | ||||
<author surname="Abellán" initials="C"/> | ||||
<author surname="Amaya" initials="W"/> | ||||
<author surname="Pruneri" initials="V"/> | ||||
<author surname="Mitchell" initials="M.W"/> | ||||
<author surname="Markham" initials="M"/> | ||||
<author surname="Twitchen" initials="D.J"/> | ||||
<author surname="Elkouss" initials="D"/> | ||||
<author surname="Wehner" initials="S"/> | ||||
<author surname="Taminiau" initials="T.H"/> | ||||
<author surname="Hanson" initials="R"/> | ||||
<date month="October" year="2015"/> | ||||
</front> | ||||
<refcontent>Nature Vol. 526, pp. 682-686</refcontent> | ||||
<seriesInfo name="DOI" value="10.1038/nature15759"/> | ||||
</reference> | ||||
<author surname="Devitt" initials="S.J" /> | <reference anchor="Fitzsimons17" target="https://journals.aps.org/pra/abst | |||
<author surname="Nemoto" initials="K" /> | ract/10.1103/PhysRevA.96.012303"> | |||
<author surname="Munro" initials="W.J" /> | <front> | |||
<title>Unconditionally verifiable blind quantum computation</title> | ||||
<author surname="Fitzsimons" initials="J.F"/> | ||||
<author surname="Kashefi" initials="E"/> | ||||
<date month="July" year="2017"/> | ||||
</front> | ||||
<refcontent>Physical Review A Vol. 96, Iss. 1, 012303</refcontent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevA.96.012303"/> | ||||
</reference> | ||||
<date year="2013" /> | <reference anchor="Terhal04" target="https://ieeexplore.ieee.org/document/ | |||
</front> | 5388928"> | |||
<seriesInfo name="Reports on Progress in Physics" value="Vol. 76, Iss. 7, | <front> | |||
pp. 076001" /> | <title>Is entanglement monogamous?</title> | |||
</reference> | <author surname="Terhal" initials="B.M"/> | |||
<date month="January" year="2004"/> | ||||
</front> | ||||
<refcontent>IBM Journal of Research and Development Vol. 48, Iss. 1, pp. | ||||
71-78</refcontent> | ||||
<seriesInfo name="DOI" value="10.1147/rd.481.0071"/> | ||||
</reference> | ||||
<reference anchor="Sangouard11" target="https://arxiv.org/abs/0906.2699"> | <reference anchor="Park70" target="https://link.springer.com/article/10.10 | |||
<front> | 07/BF00708652"> | |||
<title>Quantum repeaters based on atomic ensembles and linear optics</t | <front> | |||
itle> | <title>The concept of transition in quantum mechanics</title> | |||
<author surname="Park" initials="J.L"/> | ||||
<date month="March" year="1970"/> | ||||
</front> | ||||
<refcontent>Foundations of Physics Vol. 1, Iss. 1, pp. 23-33</refcontent | ||||
> | ||||
<seriesInfo name="DOI" value="10.1007/BF00708652"/> | ||||
</reference> | ||||
<author surname="Sangouard" initials="N" /> | <reference anchor="Wootters82" target="https://www.nature.com/articles/299 | |||
<author surname="Simon" initials="C" /> | 802a0"> | |||
<author surname="de Riedmatten" initials="H" /> | <front> | |||
<author surname="Gisin" initials="N" /> | <title>A single quantum cannot be cloned</title> | |||
<author surname="Wootters" initials="W.K"/> | ||||
<author surname="Zurek" initials="W.H"/> | ||||
<date month="October" year="1982"/> | ||||
</front> | ||||
<refcontent>Nature Vol. 299, Iss. 5886, pp. 802-803</refcontent> | ||||
<seriesInfo name="DOI" value="10.1038/299802a0"/> | ||||
</reference> | ||||
<date year="2011" /> | <reference anchor="Fowler10" target="https://journals.aps.org/prl/abstract | |||
</front> | /10.1103/PhysRevLett.104.180503"> | |||
<seriesInfo name="Reviews of Modern Physics" value="Vol. 83, Iss. 1, pp. | <front> | |||
33-80" /> | <title>Surface Code Quantum Communication</title> | |||
</reference> | <author surname="Fowler" initials="A.G"/> | |||
<author surname="Wang" initials="D.S"/> | ||||
<author surname="Hill" initials="C.D"/> | ||||
<author surname="Ladd" initials="T.D"/> | ||||
<author surname="Van Meter" initials="R"/> | ||||
<author surname="Hollenberg" initials="L.C.L"/> | ||||
<date month="May" year="2010"/> | ||||
</front> | ||||
<refcontent>Physical Review Letters Vol. 104, Iss. 18, 180503</refconten | ||||
t> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevLett.104.180503"/> | ||||
</reference> | ||||
<reference anchor="Abobeih18" target="https://arxiv.org/abs/1801.01196"> | <reference anchor="Jiang09" target="https://journals.aps.org/pra/abstract/ | |||
<front> | 10.1103/PhysRevA.79.032325"> | |||
<title>One-second coherence for a single electron spin coupled to a mul | <front> | |||
ti-qubit nuclear-spin environment</title> | <title>Quantum repeater with encoding</title> | |||
<author surname="Jiang" initials="L"/> | ||||
<author surname="Taylor" initials="J.M"/> | ||||
<author surname="Nemoto" initials="K"/> | ||||
<author surname="Munro" initials="W.J"/> | ||||
<author surname="Van Meter" initials="R"/> | ||||
<author surname="Lukin" initials="M.D"/> | ||||
<date month="March" year="2009"/> | ||||
</front> | ||||
<refcontent>Physical Review A Vol. 79, Iss. 3, 032325</refcontent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevA.79.032325"/> | ||||
</reference> | ||||
<author surname="Abobeih" initials="M.H" /> | <reference anchor="Gottesman12" target="https://journals.aps.org/prl/abstr | |||
<author surname="Cramer" initials="J" /> | act/10.1103/PhysRevLett.109.070503"> | |||
<author surname="Bakker" initials="M.A" /> | <front> | |||
<author surname="Kalb" initials="N" /> | <title>Longer-Baseline Telescopes Using Quantum Repeaters</title> | |||
<author surname="Markham" initials="M" /> | <author surname="Gottesman" initials="D"/> | |||
<author surname="Twitchen" initials="D.J" /> | <author surname="Jennewein" initials="T"/> | |||
<author surname="Taminiau" initials="T.H" /> | <author surname="Croke" initials="S"/> | |||
<date month="August" year="2012"/> | ||||
</front> | ||||
<refcontent>Physical Review Letters Vol. 109, Iss. 7, 070503</refcontent | ||||
> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevLett.109.070503"/> | ||||
</reference> | ||||
<date year="2018" /> | <reference anchor="ZOO" target="https://wiki.veriqloud.fr/"> | |||
</front> | <front> | |||
<seriesInfo name="Nature communications" value="Vol. 9, Iss. 1, pp. 1-8" | <title>The Quantum Protocol Zoo</title> | |||
/> | <author/> | |||
</reference> | <date month="November" year="2019"/> | |||
</front> | ||||
</reference> | ||||
<reference anchor="Bradley19" target="https://arxiv.org/abs/1905.02094"> | <reference anchor="Dur07" target="https://iopscience.iop.org/article/10.10 | |||
<front> | 88/0034-4885/70/8/R03"> | |||
<title>A 10-qubit solid-state spin register with quantum memory up to o | <front> | |||
ne minute</title> | <title>Entanglement purification and quantum error correction</title> | |||
<author surname="Dür" initials="W"/> | ||||
<author surname="Briegel" initials="H.J"/> | ||||
<date month="July" year="2007"/> | ||||
</front> | ||||
<refcontent>Reports on Progress in Physics Vol. 70, Iss. 8, pp. 1381-142 | ||||
4</refcontent> | ||||
<seriesInfo name="DOI" value="10.1088/0034-4885/70/8/R03"/> | ||||
</reference> | ||||
<author surname="Bradley" initials="C.E" /> | <reference anchor="Kimble08" target="https://www.nature.com/articles/natur | |||
<author surname="Randall" initials="J" /> | e07127"> | |||
<author surname="Abobeih" initials="M.H" /> | <front> | |||
<author surname="Berrevoets" initials="R.C" /> | <title>The quantum internet</title> | |||
<author surname="Degen" initials="M.J" /> | <author surname="Kimble" initials="H.J"/> | |||
<author surname="Bakker" initials="M.A" /> | <date month="June" year="2008"/> | |||
<author surname="Markham" initials="M" /> | </front> | |||
<author surname="Twitchen" initials="D.J" /> | <refcontent>Nature Vol. 453, Iss. 7198, pp. 1023-1030</refcontent> | |||
<author surname="Taminiau" initials="T.H" /> | <seriesInfo name="DOI" value="10.1038/nature07127"/> | |||
</reference> | ||||
<date year="2019" /> | <reference anchor="Devitt13" target="https://iopscience.iop.org/article/10 | |||
</front> | .1088/0034-4885/76/7/076001"> | |||
<seriesInfo name="Physical Review X" value="Vol. 9, Iss. 3, pp. 031045" / | <front> | |||
> | <title>Quantum error correction for beginners</title> | |||
</reference> | <author surname="Devitt" initials="S.J"/> | |||
<author surname="Munro" initials="W.J"/> | ||||
<author surname="Nemoto" initials="K"/> | ||||
<date month="June" year="2013"/> | ||||
</front> | ||||
<refcontent>Reports on Progress in Physics Vol. 76, Iss. 7, 076001</refc | ||||
ontent> | ||||
<seriesInfo name="DOI" value="10.1088/0034-4885/76/7/076001"/> | ||||
</reference> | ||||
<reference anchor="Nagayama16" target="https://arxiv.org/abs/1508.04599"> | <reference anchor="Sangouard11" target="https://journals.aps.org/rmp/abstr | |||
<front> | act/10.1103/RevModPhys.83.33"> | |||
<title>Interoperability in encoded quantum repeater networks</title> | <front> | |||
<title>Quantum repeaters based on atomic ensembles and linear optics</ | ||||
title> | ||||
<author surname="Sangouard" initials="N"/> | ||||
<author surname="Simon" initials="C"/> | ||||
<author surname="de Riedmatten" initials="H"/> | ||||
<author surname="Gisin" initials="N"/> | ||||
<date month="March" year="2011"/> | ||||
</front> | ||||
<refcontent>Reviews of Modern Physics Vol. 83, Iss. 1, pp. 33-80</refcon | ||||
tent> | ||||
<seriesInfo name="DOI" value="10.1103/RevModPhys.83.33"/> | ||||
</reference> | ||||
<author surname="Nagayama" initials="S" /> | <reference anchor="Abobeih18" target="https://www.nature.com/articles/s4146 | |||
<author surname="Choi" initials="B.-S" /> | 7-018-04916-z"> | |||
<author surname="Devitt" initials="S" /> | <front> | |||
<author surname="Suzuki" initials="S" /> | <title>One-second coherence for a single electron spin coupled to a mu | |||
<author surname="Van Meter" initials="R" /> | lti-qubit nuclear-spin environment</title> | |||
<author surname="Abobeih" initials="M.H"/> | ||||
<author surname="Cramer" initials="J"/> | ||||
<author surname="Bakker" initials="M.A"/> | ||||
<author surname="Kalb" initials="N"/> | ||||
<author surname="Markham" initials="M"/> | ||||
<author surname="Twitchen" initials="D.J"/> | ||||
<author surname="Taminiau" initials="T.H"/> | ||||
<date month="June" year="2018"/> | ||||
</front> | ||||
<refcontent>Nature communications Vol. 9, Iss. 1, pp. 1-8</refcontent> | ||||
<seriesInfo name="DOI" value="10.1038/s41467-018-04916-z"/> | ||||
</reference> | ||||
<date year="2016" /> | <reference anchor="Bradley19" target="https://journals.aps.org/prx/abstrac | |||
</front> | t/10.1103/PhysRevX.9.031045"> | |||
<seriesInfo name="Physical Review A" value="Vol. 93, Iss. 4, pp. 042338" | <front> | |||
/> | <title>A Ten-Qubit Solid-State Spin Register with Quantum Memory up to | |||
</reference> | One Minute</title> | |||
<author surname="Bradley" initials="C.E"/> | ||||
<author surname="Randall" initials="J"/> | ||||
<author surname="Abobeih" initials="M.H"/> | ||||
<author surname="Berrevoets" initials="R.C"/> | ||||
<author surname="Degen" initials="M.J"/> | ||||
<author surname="Bakker" initials="M.A"/> | ||||
<author surname="Markham" initials="M"/> | ||||
<author surname="Twitchen" initials="D.J"/> | ||||
<author surname="Taminiau" initials="T.H"/> | ||||
<date month="September" year="2019"/> | ||||
</front> | ||||
<refcontent>Physical Review X Vol. 9, Iss. 3, 031045</refcontent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevX.9.031045"/> | ||||
</reference> | ||||
<reference anchor="Elliott03" target="https://arxiv.org/abs/quant-ph/030704 | <reference anchor="Nagayama16" target="https://journals.aps.org/pra/abstra | |||
9"> | ct/10.1103/PhysRevA.93.042338"> | |||
<front> | <front> | |||
<title>Quantum cryptography in practice</title> | <title>Interoperability in encoded quantum repeater networks</title> | |||
<author surname="Nagayama" initials="S"/> | ||||
<author surname="Choi" initials="B.-S"/> | ||||
<author surname="Devitt" initials="S"/> | ||||
<author surname="Suzuki" initials="S"/> | ||||
<author surname="Van Meter" initials="R"/> | ||||
<date month="April" year="2016"/> | ||||
</front> | ||||
<refcontent>Physical Review A Vol. 93, Iss. 4, 042338</refcontent> | ||||
<seriesInfo name="DOI" value="10.1103/PhysRevA.93.042338"/> | ||||
</reference> | ||||
<author surname="Elliott" initials="C" /> | <reference anchor="Elliott03" target="https://dl.acm.org/doi/abs/10.1145/8 | |||
<author surname="Pearson" initials="D" /> | 63955.863982"> | |||
<author surname="Troxel" initials="G" /> | <front> | |||
<title>Quantum cryptography in practice</title> | ||||
<author surname="Elliott" initials="C"/> | ||||
<author surname="Pearson" initials="D"/> | ||||
<author surname="Troxel" initials="G"/> | ||||
<date month="August" year="2003"/> | ||||
</front> | ||||
<refcontent>SIGCOMM 2003: Proceedings of the 2003 conference on Applicat | ||||
ions, | ||||
technologies, architectures, and protocols for computer communications, pp. 227- | ||||
238</refcontent> | ||||
<seriesInfo name="DOI" value="10.1145/863955.863982"/> | ||||
</reference> | ||||
<date year="2003" /> | <reference anchor="QKD" target="https://www.quantum-network.com/applicatio | |||
</front> | ns/5/"> | |||
<seriesInfo name="Proceedings of the 2003 conference on Applications, tec | <front> | |||
hnologies, architectures, and protocols for computer communications" value="pp. | <title>Quantum Key Distribution</title> | |||
227-238" /> | <author/> | |||
</reference> | <date year="2023"/> | |||
</front> | ||||
<refcontent>Quantum Network Explorer by QuTech</refcontent> | ||||
</reference> | ||||
<reference anchor="QKD" target="https://www.quantum-network.com/application | <reference anchor="DistCNOT" target="https://www.quantum-network.com/appli | |||
s/qkd/"> | cations/7/"> | |||
<front> | <front> | |||
<title>Quantum Key Distribution</title> | <title>Distributed CNOT</title> | |||
<author> | <author/> | |||
<organization>Quantum Network Explorer by QuTech</organization> | <date year="2023"/> | |||
</author> | </front> | |||
<date year="2021" /> | <refcontent>Quantum Network Explorer by QuTech</refcontent> | |||
</front> | </reference> | |||
</reference> | ||||
<reference anchor="DistCNOT" target="https://www.quantum-network.com/applic | <reference anchor="Teleportation" target="https://www.quantum-network.com/ | |||
ations/distributed-cnot/"> | applications/1/"> | |||
<front> | <front> | |||
<title>Distributed CNOT</title> | <title>State teleportation</title> | |||
<author> | <author/> | |||
<organization>Quantum Network Explorer by QuTech</organization> | <date year="2023"/> | |||
</author> | </front> | |||
<date year="2021" /> | <refcontent>Quantum Network Explorer by QuTech</refcontent> | |||
</front> | </reference> | |||
</reference> | ||||
<reference anchor="Teleportation" target="https://www.quantum-network.com/a | <reference anchor="Moehring07" target="https://www.nature.com/articles/nat | |||
pplications/state-teleportation/"> | ure06118"> | |||
<front> | <front> | |||
<title>State teleportation</title> | <title>Entanglement of single-atom quantum bits at a distance</title> | |||
<author> | <author surname="Moehring" initials="D.L"/> | |||
<organization>Quantum Network Explorer by QuTech</organization> | <author surname="Maunz" initials="P"/> | |||
</author> | <author surname="Olmschenk" initials="S"/> | |||
<date year="2021" /> | <author surname="Younge" initials="K.C"/> | |||
</front> | <author surname="Matsukevich" initials="D.N"/> | |||
</reference> | <author surname="Duan" initials="L.-M"/> | |||
<author surname="Monroe" initials="C"/> | ||||
<date month="September" year="2007"/> | ||||
</front> | ||||
<refcontent>Nature Vol. 449, Iss. 7158, pp. 68-71</refcontent> | ||||
<seriesInfo name="DOI" value="10.1038/nature06118"/> | ||||
</reference> | ||||
<reference anchor="Moehring07" target="https://www.nature.com/articles/natu | <reference anchor="Joshi20" target="https://www.science.org/doi/10.1126/sc | |||
re06118"> | iadv.aba0959"> | |||
<front> | <front> | |||
<title>Entanglement of single-atom quantum bits at a distance</title> | <title>A trusted node–free eight-user metropolitan quantum communicati | |||
<author surname="Moehring" initials="D.L" /> | on network</title> | |||
<author surname="Maunz" initials="P" /> | <author surname="Joshi" initials="S.K"/> | |||
<author surname="Olmschenk" initials="S" /> | <author surname="Aktas" initials="D"/> | |||
<author surname="Younge" initials="K.C" /> | <author surname="Wengerowsky" initials="S"/> | |||
<author surname="Matsukevich" initials="D.N" /> | <author surname="Lončarić" initials="M"/> | |||
<author surname="Duan" initials="L.M" /> | <author surname="Neumann" initials="S.P"/> | |||
<author surname="Monroe" initials="C" /> | <author surname="Liu" initials="B"/> | |||
<date year="2007" /> | <author surname="Scheidl" initials="T"/> | |||
</front> | <author surname="Currás-Lorenzo" initials="G"/> | |||
<seriesInfo name="Nature" value="Iss. 449, pp. 68-71" /> | <author surname="Samec" initials="Z"/> | |||
</reference> | <author surname="Kling" initials="L"/> | |||
<author surname="Qiu" initials="A"/> | ||||
<author surname="Razavi" initials="M"/> | ||||
<author surname="Stipčević" initials="M"/> | ||||
<author surname="Rarity" initials="J.G"/> | ||||
<author surname="Ursin" initials="R"/> | ||||
<date month="September" year="2020"/> | ||||
</front> | ||||
<refcontent>Science Advances Vol. 6, no. 36, eaba0959</refcontent> | ||||
<seriesInfo name="DOI" value="10.1126/sciadv.aba0959"/> | ||||
</reference> | ||||
<reference anchor="Joshi20" target="https://arxiv.org/abs/1907.08229"> | <reference anchor="Askarani21" target="https://iopscience.iop.org/article/ | |||
<front> | 10.1088/1367-2630/ac0a35"> | |||
<title>A trusted-node-free eight-user metropolitan quantum communicatio | <front> | |||
n network</title> | <title>Entanglement distribution in multi-platform buffered-router-ass | |||
<author surname="Joshi" initials="S.K" /> | isted frequency-multiplexed automated repeater chains</title> | |||
<author surname="Aktas" initials="D" /> | <author surname="Askarani" initials="M.F"/> | |||
<author surname="Wengerowsky" initials="S" /> | <author surname="Chakraborty" initials="K"/> | |||
<author surname="Loncaric" initials="M" /> | <author surname="do Amaral" initials="G.C"/> | |||
<author surname="Neumann" initials="S.P" /> | <date month="June" year="2021"/> | |||
<author surname="Liu" initials="B" /> | </front> | |||
<author surname="Scheidl" initials="T" /> | <refcontent>New Journal of Physics Vol. 23, Iss. 6, 063078</refcontent> | |||
<author surname="Lorenzo" initials="G.C" /> | <seriesInfo name="DOI" value="10.1088/1367-2630/ac0a35"/> | |||
<author surname="Samec" initials="Z" /> | </reference> | |||
<author surname="Kling" initials="L" /> | ||||
<author surname="Qiu" initials="A" /> | ||||
<author surname="Razavi" initials="M" /> | ||||
<author surname="Stipcevic" initials="M" /> | ||||
<author surname="Rarity" initials="J.G" /> | ||||
<author surname="Ursin" initials="R" /> | ||||
<date year="2020" /> | ||||
</front> | ||||
<seriesInfo name="Science Advances" value="Vol. 6, no.36, pp. eaba0959" / | ||||
> | ||||
</reference> | ||||
<reference anchor="Askarani21" target="https://arxiv.org/abs/2106.04671"> | <reference anchor="Murta20" target="https://onlinelibrary.wiley.com/doi/10 | |||
<front> | .1002/qute.202000025"> | |||
<title>Entanglement Distribution in Multi-Platform Buffered-Router-Assi | <front> | |||
sted Frequency-Multiplexed Automated Repeater Chains</title> | <title>Quantum Conference Key Agreement: A Review</title> | |||
<author surname="Askarani" initials="M.F" /> | <author surname="Murta" initials="G"/> | |||
<author surname="Chakraborty" initials="K" /> | <author surname="Grasselli" initials="F"/> | |||
<author surname="do Amaral" initials="G.C" /> | <author surname="Kampermann" initials="H"/> | |||
<date year="2021" /> | <author surname="Bruß" initials="D"/> | |||
</front> | <date month="September" year="2020"/> | |||
<seriesInfo name="arXiv" value="2106.04671" /> | </front> | |||
</reference> | <refcontent>Advanced Quantum Technologies Vol. 3, Iss. 11, 2000025 </ref | |||
content> | ||||
<seriesInfo name="DOI" value="10.1002/qute.202000025"/> | ||||
</reference> | ||||
<reference anchor="Murta20" target="https://arxiv.org/abs/2003.10186"> | <reference anchor="Qin17" target="https://link.springer.com/article/10.100 | |||
<front> | 7/s11128-017-1525-y"> | |||
<title>Quantum conference key agreement: A review</title> | <front> | |||
<author surname="Murta" initials="G" /> | <title>Dynamic quantum secret sharing by using d-dimensional GHZ state | |||
<author surname="Grasselli" initials="F" /> | </title> | |||
<author surname="Kampermann" initials="H" /> | <author surname="Qin" initials="H"/> | |||
<author surname="Bruss" initials="D" /> | <author surname="Dai" initials="Y"/> | |||
<date year="2020" /> | <date month="January" year="2017"/> | |||
</front> | </front> | |||
<seriesInfo name="Advanced Quantum Technologies" value="Vol. 3, Iss. 11, | <refcontent>Quantum information processing Vol. 16, Iss. 3, 64</refconte | |||
pp. 2000025" /> | nt> | |||
</reference> | <seriesInfo name="DOI" value="10.1007/s11128-017-1525-y"/> | |||
</reference> | ||||
<reference anchor="Qin17" target="https://link.springer.com/content/pdf/10. | <reference anchor="Komar14" target="https://www.nature.com/articles/nphys3 | |||
1007/s11128-017-1525-y.pdf"> | 000"> | |||
<front> | <front> | |||
<title>Dynamic quantum secret sharing by using d-dimensional GHZ state< | <title>A quantum network of clocks</title> | |||
/title> | <author surname="Kómár" initials="P"/> | |||
<author surname="Qin" initials="H" /> | <author surname="Kessler" initials="E.M"/> | |||
<author surname="Dai" initials="Y" /> | <author surname="Bishof" initials="M"/> | |||
<date year="2017" /> | <author surname="Jiang" initials="L"/> | |||
</front> | <author surname="Sørensen" initials="A.S"/> | |||
<seriesInfo name="Quantum information processing" value="Vol. 16, Iss. 3, | <author surname="Ye" initials="J"/> | |||
pp. 64" /> | <author surname="Lukin" initials="M.D"/> | |||
</reference> | <date month="June" year="2014"/> | |||
</front> | ||||
<refcontent>Nature Physics Vol. 10, Iss. 8, pp. 582-587</refcontent> | ||||
<seriesInfo name="DOI" value="10.1038/nphys3000"/> | ||||
</reference> | ||||
<reference anchor="Komar14" target="https://arxiv.org/abs/1310.6045"> | <reference anchor="Wei22" target="https://onlinelibrary.wiley.com/doi/10.1 | |||
<front> | 002/lpor.202100219"> | |||
<title>A quantum network of clocks</title> | <front> | |||
<author surname="Komar" initials="P" /> | <title>Towards Real-World Quantum Networks: A Review</title> | |||
<author surname="Kessler" initials="E.M" /> | <author initials="S.-H" surname="Wei"/> | |||
<author surname="Bishof" initials="M" /> | <author initials="B" surname="Jing"/> | |||
<author surname="Jiang" initials="L" /> | <author initials="X.-Y" surname="Zhang"/> | |||
<author surname="Sorensen" initials="A.S" /> | <author initials="J.-Y" surname="Liao"/> | |||
<author surname="Ye" initials="J" /> | <author initials="C.-Z" surname="Yuan"/> | |||
<author surname="Lukin" initials="M.D" /> | <author initials="B.-Y" surname="Fan"/> | |||
<date year="2014" /> | <author initials="C" surname="Lyu"/> | |||
</front> | <author initials="D.-L" surname="Zhou"/> | |||
<seriesInfo name="Nature Physics" value="Vol. 10, Iss. 8, pp. 582-587" /> | <author initials="Y" surname="Wang"/> | |||
</reference> | <author initials="G.-W" surname="Deng"/> | |||
<author initials="H.-Z" surname="Song"/> | ||||
<author initials="D" surname="Oblak"/> | ||||
<author initials="G.-C" surname="Guo"/> | ||||
<author initials="Q" surname="Zhou"/> | ||||
<date month="January" year="2022"/> | ||||
</front> | ||||
<refcontent>Laser and Photonics Reviews Vol. 16, 2100219</refcontent> | ||||
<seriesInfo name="DOI" value="10.1002/lpor.202100219"/> | ||||
</reference> | ||||
<reference anchor="Wei22" target="https://arxiv.org/abs/2201.04802"> | <reference anchor="Pompili21.2" target="https://www.nature.com/articles/s4 | |||
<front> | 1534-022-00631-2"> | |||
<title>Towards real-world quantum networks: a review</title> | <front> | |||
<author initials="S.-H" surname="Wei" /> | <title>Experimental demonstration of entanglement delivery using a qua | |||
<author initials="B." surname="Jing" /> | ntum network stack</title> | |||
<author initials="X.-Y" surname="Zhang" /> | <author initials="M" surname="Pompili"/> | |||
<author initials="J.-Y" surname="Liao" /> | <author initials="C" surname="Delle Donne"/> | |||
<author initials="C.-Z" surname="Yuan" /> | <author initials="I" surname="te Raa"/> | |||
<author initials="B.-Y" surname="Fan" /> | <author initials="B" surname="van der Vecht"/> | |||
<author initials="C." surname="Lyu" /> | <author initials="M" surname="Skrzypczyk"/> | |||
<author initials="D.-L" surname="Zhou" /> | <author initials="G" surname="Ferreira"/> | |||
<author initials="Y." surname="Wang" /> | <author initials="L" surname="de Kluijver"/> | |||
<author initials="G.-W" surname="Deng" /> | <author initials="A.J" surname="Stolk"/> | |||
<author initials="H.-Z" surname="Song" /> | <author initials="S.L.N" surname="Hermans"/> | |||
<author initials="D" surname="Oblak" /> | <author initials="P" surname="Pawełczak"/> | |||
<author initials="G.-C" surname="Guo" /> | <author initials="W" surname="Kozlowski"/> | |||
<author initials="Q" surname="Zhou" /> | <author initials="R" surname="Hanson"/> | |||
<date year="2022" /> | <author initials="S" surname="Wehner"/> | |||
</front> | <date month="October" year="2022"/> | |||
<seriesInfo name="arXiv" value="2201.04802" /> | </front> | |||
</reference> | <refcontent>npj Quantum Information Vol. 8, 121</refcontent> | |||
<seriesInfo name="DOI" value="10.4121/16912522"/> | ||||
</reference> | ||||
<reference anchor="Pompili21.2" target="https://arxiv.org/abs/2111.11332"> | <reference anchor="Tang19" target="https://www.nature.com/articles/s41598- | |||
<front> | 019-50290-1"> | |||
<title>Experimental demonstration of entanglement delivery using a quan | <front> | |||
tum network stack</title> | <title>High-speed and Large-scale Privacy Amplification Scheme for Qua | |||
<author initials="M" surname="Pompili" /> | ntum Key Distribution</title> | |||
<author initials="C" surname="Delle Donne" /> | <author initials="B.-Y" surname="Tang"/> | |||
<author initials="I" surname="te Raa" /> | <author initials="B" surname="Liu"/> | |||
<author initials="B" surname="van der Vecht" /> | <author initials="Y.-P" surname="Zhai"/> | |||
<author initials="M" surname="Skrzypczyk" /> | <author initials="C.-Q" surname="Wu"/> | |||
<author initials="G" surname="Ferreira" /> | <author initials="W.-R" surname="Yu "/> | |||
<author initials="L" surname="de Kluijver" /> | <date month="October" year="2019"/> | |||
<author initials="A.J" surname="Stolk" /> | </front> | |||
<author initials="S.L.N" surname="Hermans" /> | <refcontent>Scientific Reports Vol. 9</refcontent> | |||
<author initials="P" surname="Pawelczak" /> | <seriesInfo name="DOI" value="10.1038/s41598-019-50290-1"/> | |||
<author initials="W" surname="Kozlowski" /> | </reference> | |||
<author initials="R" surname="Hanson" /> | ||||
<author initials="S" surname="Wehner" /> | ||||
<date year="2021" /> | ||||
</front> | ||||
<seriesInfo name="arXiv" value="2111.11332" /> | ||||
</reference> | ||||
<reference anchor="Tang19" target="https://www.nature.com/articles/s41598-0 | <reference anchor="Elkouss11" target="https://arxiv.org/abs/1007.1616"> | |||
19-50290-1"> | <front> | |||
<front> | <title>Information Reconciliation for Quantum Key Distribution</title> | |||
<title>High-speed and Large-scale Privacy Amplification Scheme for Quan | <author initials="D" surname="Elkouss"/> | |||
tum Key Distribution</title> | <author initials="J" surname="Martinez-Mateo"/> | |||
<author initials="B.-Y" surname="Tang" /> | <author initials="V" surname="Martin"/> | |||
<author initials="B." surname="Liu" /> | <date month="March" year="2011"/> | |||
<author initials="Y.-P" surname="Zhai" /> | </front> | |||
<author initials="C.-Q" surname="Wu" /> | <refcontent>Quantum Information and Computation Vol. 11, No. 3 and 4, pp | |||
<author initials="W.-R" surname="Yu " /> | . 0226-0238</refcontent> | |||
<date year="2019" /> | <seriesInfo name="DOI" value="10.48550/arXiv.1007.1616"/> | |||
</front> | </reference> | |||
<seriesInfo name="Scientific Reports" value="Vol. 9, Iss. 1, pp. 1-8" /> | ||||
</reference> | ||||
<reference anchor="Elkouss11" target="https://arxiv.org/abs/1007.1616"> | <reference anchor="Broadbent10" target="https://link.springer.com/chapter/ | |||
<front> | 10.1007/978-3-642-13678-8_2"> | |||
<title>Information Reconciliation for Quantum Key Distribution</title> | <front> | |||
<author initials="D" surname="Elkouss" /> | <title>Measurement-Based and Universal Blind Quantum Computation</titl | |||
<author initials="J" surname="Martinez-Mateo" /> | e> | |||
<author initials="V" surname="Martin" /> | <author initials="A" surname="Broadbent"/> | |||
<date year="2011" /> | <author initials="J" surname="Fitzsimons"/> | |||
</front> | <author initials="E" surname="Kashefi"/> | |||
<seriesInfo name="Quantum Information and Computation" value="Vol. 11, No | <date month="June" year="2010"/> | |||
. 3 and 4, pp. 0226-0238" /> | </front> | |||
</reference> | <refcontent>Springer-Verlag 978-3-642-13678-8</refcontent> | |||
<seriesInfo name="DOI" value="10.1007/978-3-642-13678-8_2"/> | ||||
</reference> | ||||
<reference anchor="Broadbent10" target="https://link.springer.com/chapter/1 | <reference anchor="Wang21" target="https://www.nature.com/articles/s41534- | |||
0.1007/978-3-642-13678-8_2"> | 021-00400-7"> | |||
<front> | <front> | |||
<title>Measurement-Based and Universal Blind Quantum Computation</title | <title>Experimental authentication of quantum key distribution with po | |||
> | st-quantum cryptography</title> | |||
<author initials="A" surname="Broadbent" /> | <author initials="L.-J" surname="Wang"/> | |||
<author initials="J" surname="Fitzsimons" /> | <author initials="K.-Y" surname="Zhang"/> | |||
<author initials="E" surname="Kashefi" /> | <author initials="J.-Y" surname="Wang"/> | |||
<date year="2010" /> | <author initials="J" surname="Cheng"/> | |||
</front> | <author initials="Y.-H" surname="Yang"/> | |||
<seriesInfo name="Springer-Verlag" value="978-3-642-13678-8" /> | <author initials="S.-B" surname="Tang"/> | |||
</reference> | <author initials="D" surname="Yan"/> | |||
<author initials="Y.-L" surname="Tang"/> | ||||
<author initials="Z" surname="Liu"/> | ||||
<author initials="Y" surname="Yu"/> | ||||
<author initials="Q" surname="Zhang"/> | ||||
<author initials="J.-W" surname="Pan"/> | ||||
<date month="May" year="2021"/> | ||||
</front> | ||||
<refcontent>npj Quantum Information Vol. 7, pp. 1-7</refcontent> | ||||
<seriesInfo name="DOI" value="10.1038/s41534-021-00400-7"/> | ||||
</reference> | ||||
<reference anchor="Wang21" target="https://www.nature.com/articles/s41534-0 | <reference anchor="Nagayama21" target="https://arxiv.org/abs/2112.07185"> | |||
21-00400-7"> | <front> | |||
<front> | <title>Towards End-to-End Error Management for a Quantum Internet</tit | |||
<title>Experimental authentication of quantum key distribution with pos | le> | |||
t-quantum cryptography</title> | <author initials="S" surname="Nagayama"/> | |||
<author initials="L.-J" surname="Wang" /> | <date month="December" year="2021"/> | |||
<author initials="K.-Y" surname="Zhang" /> | </front> | |||
<author initials="J.-Y" surname="Wang" /> | <refcontent>arXiv 2112.07185</refcontent> | |||
<author initials="J" surname="Cheng" /> | <seriesInfo name="DOI" value="10.48550/arXiv.2112.07185"/> | |||
<author initials="Y.-H" surname="Yang" /> | </reference> | |||
<author initials="S.-B" surname="Tang" /> | </references> | |||
<author initials="D" surname="Yan" /> | ||||
<author initials="Y.-L" surname="Tang" /> | ||||
<author initials="Z" surname="Liu" /> | ||||
<author initials="Y" surname="Yu" /> | ||||
<author initials="Q" surname="Zhang" /> | ||||
<author initials="J.-W" surname="Pan" /> | ||||
<date year="2021" /> | ||||
</front> | ||||
<seriesInfo name="npj Quantum Information" value="Vol. 7, no. 1, pp. 1-7" | ||||
/> | ||||
</reference> | ||||
<reference anchor="Nagayama21" target="https://arxiv.org/abs/2112.07185"> | <section anchor="Acknowledgements" numbered="false" toc="default"> | |||
<front> | <name>Acknowledgements</name> | |||
<title>Towards End-to-End Error Management for a Quantum Internet</titl | <t>The authors want to thank <contact fullname="Carlo Delle Donne"/>, <con | |||
e> | tact fullname="Matthew Skrzypczyk"/>, <contact fullname="Axel Dahlberg"/>, | |||
<author initials="S" surname="Nagayama" /> | <contact fullname="Mathias van den Bossche"/>, <contact fullname="Patrick Gelard | |||
<date year="2021" /> | "/>, <contact fullname="Chonggang Wang"/>, <contact fullname="Scott Fluhrer"/>, | |||
</front> | <contact fullname="Joey Salazar"/>, <contact fullname="Joseph Touch"/>, and the | |||
<seriesInfo name="arXiv" value="2112.07185" /> | rest of the QIRG community as | |||
</reference> | a whole for their very useful reviews and comments on this document.</t> | |||
</references> | <t>WK and SW acknowledge funding received from the EU Flagship on Quantum T | |||
echnologies, Quantum | ||||
Internet Alliance (No. 820445).</t> | ||||
</back> | <t>rdv acknowledges support by the Air Force Office of Scientific Research | |||
under award number FA2386-19-1-4038.</t> | ||||
</section> | ||||
</back> | ||||
</rfc> | </rfc> | |||
End of changes. 391 change blocks. | ||||
2193 lines changed or deleted | 1991 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |