# File Naming and Conventions
# Thierry Ernst
# 1st version 040531
# Updated: 040713



# Sub-directories in this directory:

- drafts			IETF drafts

- motivations			HTML slides to introduce the Nautilus Project
  				DON'T PUT ANYTHING HERE

- nautilus			HTML slides to present the Nautilus Project
  				DON'T PUT ANYTHING HERE

- nemo				HTML slides to introduce NEMO
  				DON'T PUT ANYTHING HERE

- paper				Published Papers

# Naming convention and classification for our documents

1. Types of document:
  -- draft (IETF)
  -- paper
  -- meeting (meeting-log and slides) 
  -- tr (technical-report, of any type) 
  -- ir (implementation-report of any type) 
  -- misc for doc which cannot be put under the above-cited types  

2. Directories: 
   We have several possibilities, and tradeoff for each.
   2a. having different directorires for each type of document:
   2b. having a single directory, with a relevant prefix
 
   So far, we are in 2a:
   - drafts	: IETF drafts
   - paper	: published papers
   - .		: everything else until further notice
 
3. File name

  It should contain a list of fields so that it is easy to spot the most
  up to date one for a given category:
  - IETF drafts have a special naming convention
  - Published Papers: 
    It's important to spot what the paper is about, and where it was pubished:

    -- 1st field = activity ( nemo / mip / secuaaa / demo / application )
    -- 2nd field = conference name
    -- 3th field = authorYYMM
    -- file type 
    
    Example:
    -- nemo-SAINT-montavont0401.pdf 
 
  - Meeting Logs and Slides
    It's more important to spot the date easily:

    Example:
    -- meeting-20040530-widemeeting.txt
    -- meeting-20040530-slides.pdf
    -- meeting-20040530.txt
 
  - Other Types (tc / ir / misc):
    It's more important to spot the keyword first, then the date:

    -- 1st field: type 
    -- 2nd field: activity ( nemo / mip / secuaaa / demo / application )
    -- 3th field: protocol or item specific ( BS / FMIP / .... )
    -- date ( YYYYMMDD )
    -- option (like author name [Surname + initiall: ErnstT] or place, or whatever useful)
    -- file type extension (optional)

    Example:
    -- ir-seamless-fmip-20040530
    -- tc-application-adaptive-20040530-LeiberF.pdf