Write, autoreview, editor, reviewer
3,129
edits
Submissions: Difference between revisions
Jump to navigation
Jump to search
→Protocol File
| Line 28: | Line 28: | ||
*'''Introductory paragraph''' gives a link to the functionality page, article on the example protocol and justify how the | *'''Introductory paragraph''' gives a link to the functionality page, article on the example protocol and justify how the | ||
protocol is different from other protocol drafts for the concerned functionality. | protocol is different from other protocol drafts for the concerned functionality. | ||
**No new terms should be used unless explained in the same paragraph. If the term is complex | **No new terms should be used unless explained in the same paragraph. If the term is complex and needs further explanation one can also provide a link for the same to the supplementary information page. e.g. fidelity (measure of how close two quantum states are), and the link would direct one to a mathematical formulae of the same in the supplementary page. | ||
and needs further explanation one can also provide a link for the same to the supplementary | **No fictional names to be used. The parties should be called according to their roles. E.g. Client-Server instead of Alice-Bob is preferred. | ||
information page. e.g. fidelity (measure of how close two quantum states are), and the link | |||
would direct one to a mathematical formulae of the same in the supplementary page. | |||
**No fictional names to be used. The parties should be called according to their roles. E.g. Client- | |||
Server instead of Alice-Bob is preferred. | |||
**Avoid mathematical equations or notations. | **Avoid mathematical equations or notations. | ||
**Try to provide a real life use case for the protocol example signing documents etc.. | **Try to provide a real life use case for the protocol example signing documents etc.. | ||
| Line 44: | Line 40: | ||
**Bullet points are preferred. | **Bullet points are preferred. | ||
**It should be lucid, and one is free to make this section lengthy (yet avoid redundancy) such that it gives a rough picture of the protocol without any specific details like number of qubits used or threshold value if any. | **It should be lucid, and one is free to make this section lengthy (yet avoid redundancy) such that it gives a rough picture of the protocol without any specific details like number of qubits used or threshold value if any. | ||
*'''Notations''' The following sections on properties and pseudo code contain mathematical equations and hence | *'''Notations''' The following sections on properties and pseudo code contain mathematical equations and hence to connect it with the wordy outline this section displays all notations used. | ||
to connect it with the wordy outline this section displays all notations used. | |||
*'''Requirements''' Mentions implementation details like benchmark values, network stage, required parameters and accommodates a figure on the decomposition of the protocol into various components required for implementation. | *'''Requirements''' Mentions implementation details like benchmark values, network stage, required parameters and accommodates a figure on the decomposition of the protocol into various components required for implementation. | ||
*'''Properties''' This section is a list of all important details which were not given in the | *'''Properties''' This section is a list of all important details which were not given in the wordy outline. One could list all that one thinks is important for the reader to know and can be extracted from the protocol. e.g: | ||
wordy outline. One could list all that one thinks is important for the reader to know | |||
and can be extracted from the protocol. e.g: | |||
# List of parameters used e.g. threshold value etc. | # List of parameters used e.g. threshold value etc. | ||
# Security Claims and other theorems used for the protocol e.g. correctness, verifiability, blindness, universality | # Security Claims and other theorems used for the protocol e.g. correctness, verifiability, blindness, universality | ||
| Line 56: | Line 49: | ||
# Mathematical equations or inequalities for security claims and other items mentioned above can | # Mathematical equations or inequalities for security claims and other items mentioned above can | ||
be accommodated here. | be accommodated here. | ||
#If using new term for any of the above, please explain it here itself and if needed, provide a link to | #If using new term for any of the above, please explain it here itself and if needed, provide a link to supplementary information page for a detailed explanation. E.g. Any property not defined in the functionality description already could be defined here. | ||
supplementary information page for a detailed explanation. E.g. Any property not defined in the | |||
functionality description already could be defined here. | |||
*'''Pseudo Code'''This section contains an algorithm/ pseudo code of the protocol. | *'''Pseudo Code'''This section contains an algorithm/ pseudo code of the protocol. | ||
**Should be step-wise description of the protocol with mathematical equations. Avoid words as much as possible. | **Should be step-wise description of the protocol with mathematical equations. Avoid words as much as possible. | ||