Main Page: Difference between revisions

3,883 bytes removed ,  21 November 2019
no edit summary
No edit summary
No edit summary
Line 26: Line 26:
As a direct consequence of this effort, hosting and analysing the protocols in this fashion provides an underlying link between several protocols and would enable everyone to gain a deeper understanding of their working. With the rapid progress in quantum technologies and improvements in the current protocols, it is extremely beneficial to have a resource for all the quantum protocols in one place that can be regularly updated to keep track of the advancements, something that can not be achieved with the review articles or a book. We, therefore, invite everyone from the quantum information science community to join and contribute to this initiative in collectively making the quantum protocol zoo a crucial source for quantum protocols.
As a direct consequence of this effort, hosting and analysing the protocols in this fashion provides an underlying link between several protocols and would enable everyone to gain a deeper understanding of their working. With the rapid progress in quantum technologies and improvements in the current protocols, it is extremely beneficial to have a resource for all the quantum protocols in one place that can be regularly updated to keep track of the advancements, something that can not be achieved with the review articles or a book. We, therefore, invite everyone from the quantum information science community to join and contribute to this initiative in collectively making the quantum protocol zoo a crucial source for quantum protocols.


== Wonder what's the format for contribution? ==
== Submissions ==
We welcome contributions from various fields, here we give the format of the kinds of pages, the wiki is composed of. A more detailed set of guidelines for submissions can be found on the [[How to Submit]] page.
=== Functionality Page===
----
Functionality page describes a general task which can be realised in a quantum network (the "what"). It consists of the following sections.
</br>
<div style="background-color: white; border: solid thin black;padding:5px;title=Functionality Description;">
* '''Functionality Description''' A lucid definition of functionality in discussion.
----
* '''Tags''' Any related page or list of protocols is connected by this section
----
* '''Use Case''' (if available) analyses how practical the protocol is, for industry use when compared to other alternatives. It answers the following questions:
**Quantum or classical task?
**Any classical or post-quantum secure analogue?
**Benchmark values for key length, security parameters, threshold values, etc?
**Scalability in terms of time, key length etc..
**Real World Applications?
----
*'''Protocols''' List of different types of example protocol achieving the functionality (each protocol in this list is written in the format given below) depending on the task achieved or [[:Category: Network Stages|Network Stages]] required to achieve the same functionality


----
If you want to submit a new page to the moderation, you can do that by clicking on [[Submissions]] (here or in the sidebar) and click or create a new Protocol or a new Functionality.
*'''Properties''' All properties that should be satisfied by any protocol achieving the concerned functionality and other common terminologies used in all the protocols.
If you go on a page that doesn't have any content yet, you can create an article similarly, by clicking the right link.
A detailled template to follow will be preloaded.


----
__NOTOC__
*'''Further Information''' Any issue that could not be addressed or find a place in the above sections or any review paper discussing a feature of various types of protocols related to the functionality.
</div>


=== Protocol Page ===
__NOTITLE__
----
Protocol page describes a specific protocol implementing the defined functionality (the "how"). It consists of the following sections.
</br>
<div style="background-color: white; border: solid thin black;padding:5px;title=Functionality Description;">
*'''Link''' to the corresponding functionality together with a short description of the method used and properties satisfied by a protocol.
----
*'''Tags''' Any related page or list of protocols is connected by this section
----
*'''Assumptions''' It describes the setting in which the protocol will be successful. Any assumption on the setup for the protocol below is listed in this section.
----
*'''Outline''' A non-mathematical detailed outline which provides a rough idea of the concerned protocol. A figure is accommodated for most protocols.
----
*'''Notation''' Connects the non-mathematical outline with further sections.
----
*'''Requirements'''
**[[:Category: Network Stages|Network Stage]]
**Relevant network parameters
**Technology required by each party
**Available information from implementations like the order of digits related to threshold values, QBit Error Rate (QBER), parameters, etc..
It accommodates a figure on the '''decomposition of the protocol''' into various components required for implementation including the physical resources, nodal subroutines, and other protocols used.
'''Color Coding:'''
*** The protocols are shown in a blue rectangular box.
*** The nodal subroutines are shown in a green rounded rectangular box.
*** The physical resources are shown in red ovals.
----
*'''Properties''' A list of important information extracted from the protocol such as parameters (threshold values), security claim, success probability,  etc..
----
*'''Protocol Description''' Mathematical step-wise protocol algorithm helpful to write a subroutine.
----
*'''Further Information''' Any useful information that could not find its place in the above description goes here. Also, some pages on protocols might include a short description as below for a list of protocols in the same class of functionality and network stage that are easy to interpret after reading the concerned formal description (or are variants of the protocol discussed above):
*Theoretical Papers:
**How is it different from the above protocol
**Requirements
**Security
*Experimental Papers:
**Which paper or protocol does it implement
**Benchmark values for this demonstration
</div>
 
__NOTOC__ __NOTITLE__
299

edits