The Title of Your Article - Never Mind if It Is Tentative for Now
Amelie Author
Helsinki University of Technology
Telecommunications Software and Multimedia Laboratory
http://www.tml.hut.fi/Studies/T-110.501/contact.html
Abstract
The text of your abstract goes here. Note that a NetSec ab- stract must not contain any empty lines, i.e. you should not force any vertical whitespace between the paragraphs. See section 3 for details on creating and avoiding different types of whitespaces.
KEYWORDS: first keyword, second keyword which is very long and forces a line break,
third keyword, ...
1 Introduction
The text of your introduction (your section 1) goes here.
2 Section heading for the second sec- tion: basic article body structure
The introductory text for your second section (if an introduc- tory part for this section is needed) goes here.
2.1 Subsection heading for first subsection of second section
The text of the first subsection of your second section goes here.
2.2 Subsection heading for second subsection of second section
The text of the second subsection of your second section goes here.
2.2.1 Subsubsection heading
The text of the first subsubsection of the second subsection of your second section goes here (if a subsubsection is needed).
3 Section heading for the third sec- tion: paragraph and sentence sep- arations
The structural “tools” presented in the previous section should be used throughout your article. In this section we
present two of the most common “tricks” that may be useful to know.
To clarify what was said in the abstract: even though para- graphs are always separated by an empty line in the LaTeX mark-up (source code), the paragraphs may be visually sep- arated in any number of ways in the final lay-out and type- setting of the PostScript (PS) file, the Portable Document Format (PDF) file and when printed on paper. What a para- graph separation ends up looking like in PS/PDF/print is en- tirely dependent on which LaTeX control rules are used. In the case on NetSec proceedings the controlling rules are pro- vided by the LaTeX class file ’netsec2004.cls’. You MUST use the correct class file (or risk low grades, because your article looks different from the other articles and causes the seminar teacher extra work).
You should also note, that LaTeX puts extra space between sentences, which you must suppress after a period that does not end a sentence, e.g. after this acronym.
4 Section heading: how to make your writing scientific and more finely structured
4.1 Citing literature
Always remember to give pointers to the literature you have used. This is such a pointer: a citation (also called a refer- ence) [3]. One more citation here, this time a multiple one [4, 5, 3].
Testing some more citations: K-Kaupat [7]. Or two ver- sions of the same article: AbaNee94 [1] and AbaNee96 [2].
Or the organization-as-an-author workaround: [8, 6].
Note that in the NetSec seminar you use a BibTeX database (file) and the bibtex command to typeset your bibliography automatically. In the long run, this will save you a lot of time and effort compared to manually compiling separate reference lists for every article you write.
Should we put also here the rules about how to place the brackets that show the citation? Ronja thinks so...
4.2 Simple structures first
In this section, we give some simple examples of LaTeX mark-up. Section 4.2.1 shows how to emphasize important points in your text, 4.2.2 demonstrates lists and 4.2.3 shows how to cross-reference.
Protocol Year RFC
TCP 1981 793
ISAKMP 1998 2408 Photuris 1999 2522 Table 1: A table with some protocols
4.2.1 Emphasizing text
Italics is a good way to emphasize printed text. However, boldface looks better if the text ever needs to be converted to HTML (unlikely, but still...).
4.2.2 Making a list
List items can be identified either by bullets (itemized list) or by numbers (enumerated list).
• one item
• another item, which is an exceptionally long one for an item and consequently continues on the next line Lists can have several levels. Item 1 below contains an- other list.
1. the fist item
(a) the first subitem (b) the second subitem 2. the second item
4.2.3 Cross-referencing inside the article
Cross-references to figures (Fig. 1), tables (Table 1) and other sections (Sec. 4.2.1) are easy to create, once you know how to do it.
5 More complex structures and other useful things
This section provides examples of more complex things one can do with LaTeX. Section 5.1 shows how to build tables for data, sec. 5.2 presents how to insert (embed) pictures into your article and finally, sec. 5.2.1 gives examples of mathe- matic formulas.
5.1 Data served on a table
Table 1 presents some data in tabular form. Note that LaTeX places the tables and pictures before the text that cites them (if possible), and by default at the beginning of a column.
Do not try to force LaTeX to change this behavior, unless you really know what you are doing (or are prepared to use quite many hours in “fighting” LaTeX). At any rate, do not try to change table or picture positioning before you have reached your almost-final camera ready (and remember to take a back up copy of your article before you start to adjust your tables or pictures!).
Security
Insecurity
Figure 1: An embedded EPS picture
5.2 Embedded pictures
Fig. 1 is an embedded EPS picture. LaTeX only accepts EPS pictures, so if you have other types of pictures, they must be converted to EPS (embedded Postscript).
5.2.1 Mathematics
If you write about cryptography or other areas of security where mathematical formulas are needed, you will likey use some of the following specialized LaTeX mark-up.
In the LaTeX mathematics mode, you can have subscripts such asKmaster and superscripts like2x. Longer formulas may be put on a separate line:
∅ ∈ ∅ ⇒ E 6=mc2.
You may also want to number the formulas like Eqn. 1 below.
C=EK
public(P) =Pe P =DK
private(C) =Cd (1)
6 Results
The text, tables, graphs etc. describing your results go here.
7 Discussion
The text of your discussion goes here.
8 Conclusions
The text of your conclusions goes here.
References
[1] M. Abadi and R. Needham. Prudent engineering prac- tice for cryptographic protocols. In R. T. CHECKED- ITORASAP and H. MAINLIBRARY, editors, Proceed- ings of the 1994 IEEE Computer Society Symposium on
Research in Security and Privacy, pages 122–136, USA, 1994. IEEE.
[2] M. Abadi and R. Needham. Prudent engineering prac- tice for cryptographic protocols. IEEE Transactions on Software Engineering, 22:6–15, 1 1996.
[3] E. Amoroso. Fundamentals of Computer Security Tech- nology. Prentice Hall, USA, 1994.
[4] W. Diffie and M. E. Hellman. New directions in cryp- tography. IEEE Transactions on Information Theory, 22:644–654, 1976.
[5] D. Harkins and D. Carrel. The Internet Key Exchange (IKE), 1998. RFC 2409.
[6] Microsoft-Corporation. Sender ID Framework at a Glance. At http://www.microsoft.com/
mscorp/twc/privacy/spam_senderid.
mspx, 2004. Referenced 2.10.2004.
[7] J. Rahkonen. K-kaupat kasvattivat markkinaosu- uttaan Keski-Suomessa. At http://lehti.
keskisuomalainen.fi/sl/1998-05/26/
tal/kxkaupat.htm, 1998. Referenced 14.10.2004.
[8] Symbian-Software-Ltd. Security guide. At http://www.symbian.com/developer/
techlib/v70docs/sdl_v7.0/doc_source/
De%vGuides/, 2002. Referenced 1.10.2004.