Write, autoreview, editor, reviewer
3,129
edits
Main Page: Difference between revisions
Jump to navigation
Jump to search
→Figure
(→Figure) |
|||
| Line 29: | Line 29: | ||
This section is a simple wordy outline of the protocol. It should tell you what the protocol is, but not the minute details of the protocol. As far as possible, one must refrain from using mathematical notations or variables. It should be kept as a general outline of the Procedure. It should not contain any new terminology that has not been explained before or here itself. If one does, it should be linked to a Wikipedia page or a supplementary draft, whichever preferred. This part should be self-consistent, precise but self-explanatory. If we use bullet points and give steps/levels some name, one should aim at describing the target of the step in the first line and then proceed with the ’what’ and ’how’ of the step. A key point to be noted, we do not aim at answering the ’why’ for different steps nor do we provide with the security proof. That would just make the description as long as the paper. It is redundant and not the aim of this formal description. The reader may refer to the specific paper in order to understand any such detail. | This section is a simple wordy outline of the protocol. It should tell you what the protocol is, but not the minute details of the protocol. As far as possible, one must refrain from using mathematical notations or variables. It should be kept as a general outline of the Procedure. It should not contain any new terminology that has not been explained before or here itself. If one does, it should be linked to a Wikipedia page or a supplementary draft, whichever preferred. This part should be self-consistent, precise but self-explanatory. If we use bullet points and give steps/levels some name, one should aim at describing the target of the step in the first line and then proceed with the ’what’ and ’how’ of the step. A key point to be noted, we do not aim at answering the ’why’ for different steps nor do we provide with the security proof. That would just make the description as long as the paper. It is redundant and not the aim of this formal description. The reader may refer to the specific paper in order to understand any such detail. | ||
===Figure=== | ===Figure=== | ||
A figure of the protocol in jpeg format could be used. A pdf file of the image drawn using tikz or cryptopackage would also suffice. | |||
===Notations=== | ===Notations=== | ||
Any mathematical notations or variables used in the Pseudo code can be listed here in order to make the picture clear. It serves the purpose of connecting the wordy outline and the mathematical pseudo code. | Any mathematical notations or variables used in the Pseudo code can be listed here in order to make the picture clear. It serves the purpose of connecting the wordy outline and the mathematical pseudo code. | ||