draft IP request template

  > 
  > I have only one remark which I already made in Prague, I think.
  > iso-cc is not a good name for the network location tag, it is far too
  >        criptic. I propose net-country.
accepted and changed.
  > I have a comment on:
  > > This document is valid until <expiry date>.  An updated document can be
  > We need to define a revision schedule to be able to specify an expiry date,
  > I think. I would try to avoid different expiry dates for different countrie
  > s
  > or different service providers. We all need to know which is the right
  > version of template to be given to requestors at a certain date.

Well i would be responsible for sending out to all local registries via
the local-ir list, the updated copy both .lpr and .ps versions at say 3 
monthly intervals (just after RIPE meetings I propose).  I would also of 
course ensure that the most up to date document is in the document store.  
It would be up to each local registry to maintain their local language
versions.  

However, the NCC version of the template will be slightly 
different from the one that will be used by local registries (it is more
verbose), so either we maintain two documents : the RIPE NCC template
and one for local registries OR local registries delete the parts that
dont apply.  It would probably be less confusing to have 2 separate documents.
But you will in any case have to add your own contact details to the template.
  > 
  > 
  > Then, I found some typos; look below for replacement lines beginning with $
  > $
corrected all the typos.

Many thanks for your comments.

Anne.