First draft of the European Template for IP number requests

Dear All, Below are two documents which comprise the RIPE NCC's first draft of the European IP network number request form. The first comprises the bare bones of the template, which will be completed and returned to the local registry. The second document gives guidelines on how to correctly complete the template. The idea is that it is this second document which can be translated for local use, but that the basic template is to remain in English, in case the it needs to be forwarded to another country. In drafting the document, sections from both the the templates of JANET NIC and the Norwegian NIC were incorporated. Comments on this draft are welcome and appreciated. Please send your comments to the list (or to me if they are minor comments). Many thanks, Anne. -----------------------cut here-------------------------------- DRAFT December 1992 RIPE NCC EUROPEAN IP NUMBER REQUEST FORM ------------------------------- It is *essential* that you read the supporting documentation before completing the form below. There are 3 documents which you should receive and read: a) the IP number request form - this document b) guidelines on how to complete the IP number request form c) what you should know before applying for IP network numbers (draft is being prepared by Bob Day) This form is the basic template which you should complete and return to us. The more complete the information you supply to us now, the quicker we will process your request. Further related documentation is available from: <xyz etc> rfc's etc. PLEASE RETURN THIS DOCUMENT TO: local ir-registry name <email of local ir-registry> <phone of local ir-registry> <fax no of local ir-registry> <address of local ir-registry> Part A ------ The information supplied for this section together with the assigned network numbers will be entered into a database of European network numbers and their contact information which is accessible by the whole Internet community. netname: descr: descr: country: admin-c: tech-c: changed: source: RIPE person: address: address: address: address: phone: fax-no: e-mail: changed: source: RIPE person: address: address: address: address: phone: fax-no: e-mail: changed: source: RIPE Part B ------ Information supplied below helps us to evaluate and process your request. It will be kept in strict CONFIDENCE and NOT entered into the RIPE Network Management Database. req-typ: provider: inet-con: cust-ip host-0: host-1: host-2: sub-0: sub-1: sub-2: ip-prov: use-net: iso-net: Part C ------ Complete the section below *ONLY IF* you are making an application on behalf of another organisation. app-by: org-by: add-by: ph-by: fax-by: app-for: org-for: add-for: ph-for: fax-for: Part D ------ If you are applying for more than 2 Class C network numbers then on a separate page, please submit a description of your network plans. The more numbers you are requesting, the more detailed your technical description will need to be. Furthermore, the more detail you provide, the quicker we will be able to process your application. Please ensure that you have read all the supporting documentation before completing this section (currently under preparation). This is important whatever class of network number you are applying for, but especially important if you are applying for a class B, as it contains a number of helpful hints. Furthermore if you are applying for a class B, your application may be referred to the RIPE Network Coordination Centre in Amsterdam for adjudication. Current network layout: Future network plans: --------------------------------cut here------------------------ DRAFT December 1992 RIPE NCC GUIDELINES ON HOW TO COMPLETE THE IP NUMBER REQUEST FORM -------------------------------------------------------- It is *essential* that you read ALL supporting documentation before applying for your network numbers. There are 3 documents which you should receive and read: a) the IP number request form b) guidelines on how to complete the IP number request form - this document c) what you should know before applying for IP network numbers (draft is being prepared by Bob Day) This document will guide you in how to complete the IP number request form correctly. The more complete the information you supply to us now, the quicker we will be able to process your application. Further related documentation is available from: <xyz etc.> rfc's etc PLEASE RETURN THIS DOCUMENT TO: local ir-registry name <email of local ir-registry> <phone of local ir-registry> <fax no of local ir-registry> <address of local ir-registry> Part A: ------ The information supplied for this section together with the assigned network numbers will be entered into a database of European network numbers and their contact information which is accessible by the whole Internet community. netname: Please complete with an appropriate network name for the network to be numbered which is short and meaningful. This name is not related to any host name. It is used mainly for administrative purposes like consistency checking of the Internet Registry. You will very likely not see this name appear anywhere, but on forms like this. Format: Please complete only with capital letters. Network names should NOT start with anything other than a capital letter. Dashes can be used as shown below. A "-NET" suffix is quite a common naming format. example - netname: TBIT-NET descr: Please complete with a short description of the organisation, including the location. The full postal address is not needed as this is required and will be specified in the person template. Format: free text, one line per entry, multiple lines in sequence. example - descr: Terabit Labs Inc. descr: Network Bugs Feeding Facility descr: Northtown country: Please give the ISO 3166 two letter country code which is appropriate for the organisation. We know this gives problems for networks crossing national boundaries, so choose the most appropriate country, based on the location of the admin contact. If you do not know the ISO code for your country, please complete with the full name of the country. Format: ISO 3166 two letter country code in CAPITAL LETTERS Example - country: IE admin-c: Please complete with the name or NIC handle of the person who is the administrative contact for the network. The NIC handle (if known) is preferred. Format: <firstname> <initials> <lastname> or the NIC handle if known. Example - admin-c: John E Doe tech-c: Please give the name of technical contact person. There can be multiple technical contacts names. NOTE: both the admin-c: and tech-c: fields MUST be completed. If two different names for each function are not applicable, then please use the same name for both contacts. Format: as in admin-c. changed: Email address of the person who is completing the template, followed by the current date. If you do not have email connectivity please leave blank and we will complete it. Format: <email-address> YYMMDD. Example - changed: johndoe@terabit-labs.nn 900401 source: Source of the information. This will always be RIPE. Example - source: RIPE PERSON TEMPLATE NOTES Please ensure that you complete as many person templates as there are different persons specified in the network template unless the data about those persons is already in the RIPE database. person: Please give the full name of either the admin-c contact or the tech-c contact. There must be a person template completed for each person. The names must be identical to those given above in the "admin-c:" and "tech-c:" attributes (but must not be the NIC handle). Format: <firstname> <initials> <lastname> Example - person: John E Doe address: Please complete with the full postal address. Include everything necessary for paper mail to be delivered. Format: multiple lines of text. City and post code on a single line. Country on the last line. Example - address: Terabit Labs Inc. address: Industrial Estate North address: North Perpendicular Road 12 address: NN-1234 Northtown address: Repubic of Northern Nowhere phone: Please give the work telephone number of the person (or NIC handle) specified above. Multiple telephone numbers are acceptable. Each telephone number should be put on a separate line, one line per number in order of the most appropriate number for the contact person first. Format: International +<country-code> <city> <subscriber>. If no direct inward dialling is available, please append "ext." and extension number. Example - phone: +31 20 12334676 phone: +44 123 987654 ext. 4711 fax-no: Please complete with the telefax number of the person (or NIC handle) specified above. Format: the same as for the telephone number above. Example - fax-no: +31 20 12334677 e-mail: Please supply the appropriate electronic mail address for the contact. If you DO NOT have e-mail connectivity, please insert <none>. Format: Valid domain address please. (If possible please do not include the following characters in the address !, %, ::). Example - e-mail: johndoe@terabit-labs.nn or e-mail: <none> nic-hdl: This refers to a NIC handle which is a unique identifier assigned and used by the US NIC to unambiguously refer to Internet people. If you do not have a NIC handle, then please leave blank. Format: NIC format. Example - nic-hdl: JD0401 changed: Who and when changed this last. Please complete with your e-mail address followed by the current date in the format specified below. If you do not have e-mail connectivity, please leave blank and we will complete this on your behalf. Format: <email-address> YYMMDD: Example - changed: johndoe@terabit-labs.nn 920913 source: Source of the information. This should always be RIPE. Example - source: RIPE PART B ------ Information supplied below helps us to evaluate and process your request. It will be kept in strict CONFIDENCE and NOT entered into the RIPE Network Management Database. req-typ: This refers to the "request type". Please specify the quantity and class of your request for network numbers. Format: quantity of numbers requested followed by class of request. Example - req-typ: 1 class C In making the application, please be guided by the following EXAMPLES of number of hosts which relate to the quantity of network numbers requested: 1 class C number (up to 255 hosts) 2 class C numbers (up to 510 hosts) 4 class C numbers (up to 1020 hosts) 8 class C numbers (up to 2040 hosts) 16 class C numbers (up to 4080 hosts) 32 class C numbers (up to 8160 hosts) a single class B number (class B requests may be referred to the RIPE NCC for adjudication) other (please specify) provider: Please state whether you have an IP service provider. An "IP service provider" is an organisation which can provide you with connectivity external to your network. Format: please answer with the name of your provider or if you do not have an IP service provider answer with a "no". Example: - provider: Connections Company, Northern Nowhere inet-con: Please state whether you plan to connect to the Internet. Format: please answer with whichever of the following options most closely describes the position of your organisation. - will never connect - already connected <through whom> - plan to connect <date> If you are "already connected" to the Internet, please state through whom you are connected and to which network. If you answer with "plan to connect" then please make an estimation on the date that you hope to connect, specifying the month and the year (if possible). Example - inet-con: already connected JANET in the UK or Example - inet-con: plan to connect December 1993 host-0: Please state the number of machines in your organisation that currently require a unique IP network number (hosts). Format: complete with a number. Example - host-0: 100 host-1: Estimate the number of machines requiring a unique IP network number (hosts) in one years time. Format: as above. Example - host-1: 134 host-2: Estimate the number of machines requiring a unique IP network number (hosts) in two years time. Format: as above. Example - Host-2: 250 sub-0: Please state the number of subnets required for the current network. A subnet refers to the physical parts of the network which need a unique (sub)net number. Format: complete with a number. Example - sub-0: 10 sub-1: Estimate the number of subnets in one years time. Format: as above. sub-2: Estimate the number of subnets in two years time. Format: as above. ip-prov: Please answer the question - Does your organisation provide IP services to other organisations? Format: complete with Yes or No. Example - ip-prov: No or Example - ip-prov: Yes use-net: Please answer the question - has your organisation already obtained an IP network number or numbers? If so, please give the network number(s). If not, then please complete with <no>. Format: complete with the network number only - four numbers separated by dots, as shown below. Example - use-net: 193.87.45.0 or Example - use-net: <no> iso-net: Please give the ISO 3166 country code which describes where the network will be located. If more than one country applies, then give the name of the country "responsible" for the network, using the country of the admin-c: contact given in Part A. Format: complete with country name using ISO 3166 country code. Example - iso-net: NL Part C: ------ Complete this section *ONLY IF* you are completing this template on behalf of another organisation. If you are not, please leave this section blank because contact and organisational details have been given in Part A. app-by: Who is this application being made by? Please give a contact name. Format: <First name> <Surname> Example - app-by: Joe Bloggs org-by: Format: name of your organisation. Example - org-by: Bloggs Software Consultancy add-by: Address of the organisation responsible for this request. Format should follow the example in the "address" object in Part A. ph-by: Telephone number for the above organisation. Format should follow the example given for the "phone" object in part A. fax-by: Fax number for the above organisation. Format should follow the example given in the "fax" object in Part A. app-for: Who is this application being made for? Format: <first name> <surname>. Example - app-by: Mrs E Smith org-for: Name of organsation FOR whom the application is being made. Format and example should follow the example in the "org-by" object given above. add-for: Address of organisation FOR whom the application is being made. Format should follow the example given for the "address" object in Part A. ph-for: Telephone number of organisation in "add-for" object above. Format should follow the example given for the "phone" object in Part A. fax-for: Fax number of organisation in "add-for" object above. Format should follow the example given for the "fax" object in Part A. Part D: ------ If you are applying for more than 2 Class C network numbers then on a separate page, please submit a description of your network plans. The more numbers you are requesting, the more detailed your technical description will need to be. Furthermore, the more detail you provide, the quicker we will be able to process your application. Please read the supporting documentation (currently under preparation) which will guide you. It is particularly important to read this document if you are applying for a class B network number, as it provides a number of helpful hints. It is available from: <supporting-ipdocs@wherever.net> Please consider the following in your description: Current network layout: Future network plans:

Anne,
Comments on this draft are welcome and appreciated. Please send your comments to the list (or to me if they are minor comments).
DRAFT December 1992 RIPE NCC
GUIDELINES ON HOW TO COMPLETE THE IP NUMBER REQUEST FORM -------------------------------------------------------- [...]
Part A: ------
The information supplied for this section together with the assigned network numbers will be entered into a database of European network numbers and their contact information which is accessible by the whole Internet community.
netname: Please complete with an appropriate network name for the network to be numbered which is short and meaningful. This name is not related to any host name. It is used mainly for administrative purposes like consistency checking of the Internet Registry. You will very likely not see this name appear anywhere, but on forms like this.
One problem that often arises is confusion with the DNS. A sentence explaining that both naming schemes have absolutely nothing in common should be added. Just telling them about hostnames is not enough (tm) .
Format: Please complete only with capital letters. Network names should NOT start with anything other than a capital letter. Dashes can be used as shown below. A "-NET" suffix is quite a common naming format.
... and is totally redundant. In fact, we would discourage people to have some kind of 'LAN' or 'NET' in their network names. This is mainly because - as to my knowledge - there is a restriction on the length of these names which allows them to be only up to 12 characters long. If we no longer have to cope with this - as I don't see it mentioned here - some sort of suffix may be ok.
example - netname: TBIT-NET
descr:
[...]
country: Please give the ISO 3166 two letter country code which is appropriate for the organisation. We know this gives problems for networks crossing national boundaries, so choose the most appropriate country, based on the location of the admin contact. If you do not know the ISO code for your country, please complete with the full name of the country.
The local IR could mention the local ISO3166 code here, or we could attach a list of all (European) codes to the explanatory section.
Format: ISO 3166 two letter country code in CAPITAL LETTERS
Example - country: IE
admin-c: Please complete with the name or NIC handle of the person who is the administrative contact for the network. The NIC handle (if known) is preferred.
Format: <firstname> <initials> <lastname> or the NIC handle if known.
Example - admin-c: John E Doe
This is a very detail and may better be discussed elsewhere, but if you prefer "John E Doe" to "John E. Doe", this should more clearly be pointed out. The requestor should be guided to leave out titles like 'Dr.' here, too.
tech-c: [...]
PERSON TEMPLATE NOTES
Please ensure that you complete as many person templates as there are different persons specified in the network template unless the data about those persons is already in the RIPE database.
[...]
address: Please complete with the full postal address. Include everything necessary for paper mail to be delivered.
Format: multiple lines of text. City and post code on a single line. Country on the last line.
Example - address: Terabit Labs Inc. address: Industrial Estate North address: North Perpendicular Road 12 address: NN-1234 Northtown address: Repubic of Northern Nowhere
This may also be more appropriate on the db-wg list, but I remember some rumors, that the 'country' attribute would be added to the person object ...
phone:
[...]
PART B ------
Information supplied below helps us to evaluate and process your request. It will be kept in strict CONFIDENCE and NOT entered into the RIPE Network Management Database.
req-typ: This refers to the "request type". Please specify the quantity and
class of your request for network numbers.
Format: quantity of numbers requested followed by class of request.
Example - req-typ: 1 class C
In making the application, please be guided by the following EXAMPLES of number of hosts which relate to the quantity of network numbers requested:
1 class C number (up to 255 hosts) 2 class C numbers (up to 510 hosts) 4 class C numbers (up to 1020 hosts) 8 class C numbers (up to 2040 hosts) 16 class C numbers (up to 4080 hosts) 32 class C numbers (up to 8160 hosts)
The numbers should read 254 * n and the info-sheet should explain why. Nice to see this 32-C-block here ...
a single class B number (class B requests may be referred to the RIPE NCC for adjudication) other (please specify)
This could make requestors switch over to contacting RIPE NCC direct for class B requests. I think we do not want this happen, so better say it unambigously.
provider: [...]
host-0: Please state the number of machines in your organisation that currently require a unique IP network number (hosts).
The term 'host' often causes confusion here, which may be a local language problem. Hosts are often thought of as > x m^3 big :-) An explanatory text should explicitly tell people to take also into account PCs (terminal servers ...) and the like.
Format: complete with a number.
Example - host-0: 100
host-1:
[...]
sub-0: Please state the number of subnets required for the current network. A subnet refers to the physical parts of the network which need a unique (sub)net number.
It is a very good idea to ask for this information, as it is really missing to date and we have to call the requestor for it every now and then. It could also prevent people from just copying the host numbers from the req-typ field into the host-? fields, which may happen if the host number seems to be the only figure of interest. ["How many hosts do I need to have for receiving a class B address?"]
Format: complete with a number.
Example - sub-0: 10
sub-1: Estimate the number of subnets in one years time.
Format: as above.
sub-2: Estimate the number of subnets in two years time.
Format: as above.
Somewhere in the information package (here or in (c)) requestors should be guided to not forget transit networks when calculating their needs. And, in close relation with that, people should be asked to give an overview of the size of the different subnets, e.g. 17 subnets, 10 with < 20 hosts, the rest with up to 120 machines. This is often the case when large companies (e.g. insurance comp.) have some central administration and a number of regional offices.
ip-prov: [...]
use-net: Please answer the question - has your organisation already obtained an IP network number or numbers? If so, please give the network number(s). If not, then please complete with <no>.
Format: complete with the network number only - four numbers separated by dots, as shown below.
Example - use-net: 193.87.45.0 or Example - use-net: <no>
For easier error detection/consistency checking the network name could additionally be mentioned, if possible, i.e. if known.
iso-net:
[...]
Part D: ------
If you are applying for more than 2 Class C network numbers then on a separate page, please submit a description of your network plans. The more numbers you are requesting, the more detailed your technical description will need to be. Furthermore, the more detail you provide, the quicker we will be able to process your application.
Please read the supporting documentation (currently under preparation) which will guide you. It is particularly important to read this document if you are applying for a class B network number, as it provides a number of helpful hints. It is available from: <supporting-ipdocs@wherever.net>
Please consider the following in your description:
It is always a good idea to ask requestors for B addresses what subnet mask they want to apply.
Current network layout: Future network plans:
just my 2 cents ... regards, Peter

"Peter Koch" <pmk@deins.informatik.uni-dortmund.de> writes:
The information supplied for this section together with the assigned netw
ork
numbers will be entered into a database of European network numbers and t heir contact information which is accessible by the whole Internet community.
netname: Please complete with an appropriate network name for the network to be numbered which is short and meaningful. This name is not related to any host name. It is used mainly for administrative purposes like consistency checking of the Internet Registry. You will very likely not see this name appear anywhere, but on forms like this.
One problem that often arises is confusion with the DNS. A sentence explain ing that both naming schemes have absolutely nothing in common should be added. Just telling them about hostnames is not enough (tm) .
Good point. Done.
Format: Please complete only with capital letters. Network name
s
should NOT start with anything other than a capital letter. Dashes can be used as shown below. A "-NET" suffix is quite a common naming format.
... and is totally redundant. In fact, we would discourage people to have s ome kind of 'LAN' or 'NET' in their network names. This is mainly because - as to my knowledge - there is a restriction on the length of these names which allows them to be only up to 12 characters long. If we no longer have to co pe with this - as I don't see it mentioned here - some sort of suffix may be o k.
example - netname: TBIT-NET
Ditto.
descr:
[...]
country: Please give the ISO 3166 two letter country code which is appropriate for the organisation. We know this gives problems for networks crossing national boundaries, so choose the most appropriate country, based on the location of the admin contact. If you do not know the ISO code for your country, please complete with the full name of the country.
The local IR could mention the local ISO3166 code here, or we could attach
This is a good idea - I am not sure about adding the whole list of ISO codes to the package going out to people as it is quite long and from the requests I see, people get it right nearly all the time.
a list of all (European) codes to the explanatory section.
Format: ISO 3166 two letter country code in CAPITAL LETTERS
Example - country: IE
admin-c: Please complete with the name or NIC handle of the person who is the administrative contact for the network. The NIC handle (if known) is preferred.
Format: <firstname> <initials> <lastname> or the NIC handle if known.
Example - admin-c: John E Doe
This is a very detail and may better be discussed elsewhere, but if you pre fer "John E Doe" to "John E. Doe", this should more clearly be pointed out. The requestor should be guided to leave out titles like 'Dr.' here, too.
Also incoporated.
tech-c: [...]
PERSON TEMPLATE NOTES
Please ensure that you complete as many person templates as there are different persons specified in the network template unless the data about those persons is already in the RIPE database.
[...]
address: Please complete with the full postal address. Include everything necessary for paper mail to be delivered.
Format: multiple lines of text. City and post code on a single line. Country on the last line.
Example - address: Terabit Labs Inc. address: Industrial Estate North address: North Perpendicular Road 12 address: NN-1234 Northtown address: Repubic of Northern Nowhere
This may also be more appropriate on the db-wg list, but I remember some rumors, that the 'country' attribute would be added to the person object .. .
This is not yet fully agreed right? In which case it is probably best left until a consensus has been reached on this in the db-wg.
phone:
[...]
PART B ------
Information supplied below helps us to evaluate and process your request.
It will be kept in strict CONFIDENCE and NOT entered into the RIPE Networ k Management Database.
req-typ: This refers to the "request type". Please specify the quantity and
class of your request for network numbers.
Format: quantity of numbers requested followed by class of request.
Example - req-typ: 1 class C
In making the application, please be guided by the following EXAMPLES of number of hosts which relate to the quantity of network numbers requested:
1 class C number (up to 255 hosts) 2 class C numbers (up to 510 hosts) 4 class C numbers (up to 1020 hosts) 8 class C numbers (up to 2040 hosts) 16 class C numbers (up to 4080 hosts) 32 class C numbers (up to 8160 hosts)
The numbers should read 254 * n and the info-sheet should explain why.
Done.
Nice to see this 32-C-block here ...
a single class B number (class B requests may be referred to the RIPE NCC for adjudication) other (please specify)
This could make requestors switch over to contacting RIPE NCC direct for class B requests. I think we do not want this happen, so better say it unambigously.
I have added the following which I hope will make this clear.. "a single class B number (class B requests may be referred to the RIPE NCC for adjudication. Please do NOT make your application direct to the RIPE NCC as it will only be forwarded to the local registry)."
provider: [...]
host-0: Please state the number of machines in your organisation that currently require a unique IP network number (hosts).
The term 'host' often causes confusion here, which may be a local language problem. Hosts are often thought of as > x m^3 big :-) An explanatory text should explicitly tell people to take also into account PCs (terminal servers ...) and the like.
I think you are right - the term "host" does cause confusion. Maybe it is better simply to drop the term and use something like "machine-0" instead. So then we have machine-0: Please state the number of machines in your organisation that currently require a unique IP network number including terminal servers.. Mentioning PC's should could also be confusing as people also might think that *every* PC on the network should be counted...
Format: complete with a number.
Example - host-0: 100
host-1:
[...]
sub-0: Please state the number of subnets required for the current network. A subnet refers to the physical parts of the network which need a unique (sub)net number.
It is a very good idea to ask for this information, as it is really missing to date and we have to call the requestor for it every now and then. It could also prevent people from just copying the host numbers from the re q-typ field into the host-? fields, which may happen if the host number seems to be the only figure of interest. ["How many hosts do I need to have for receivi ng a class B address?"]
Format: complete with a number.
Example - sub-0: 10
sub-1: Estimate the number of subnets in one years time.
Format: as above.
sub-2: Estimate the number of subnets in two years time.
Format: as above.
Somewhere in the information package (here or in (c)) requestors should be guided to not forget transit networks when calculating their needs. And, in close relation with that, people should be asked to give an overvie w of the size of the different subnets, e.g. 17 subnets, 10 with < 20 hosts, the rest with up to 120 machines. This is often the case when large companies (e.g. insurance comp.) have some central administration and a num ber of regional offices.
This is a good point and if incorporated could eliminate quite a lot of the further clarification we often require when large blocks are requested - it would help us ascertain whether the address space is being used efficiently. We could incorporate it into the Section D where people are asked to give a description of their network plans. Equally we could point out in the preamble of Section D not to forget their transit networks when calculating their needs.
ip-prov:
[...]
use-net: Please answer the question - has your organisation already obtained an IP network number or numbers? If so, please give the network number(s). If not, then please complete with <no>.
Format: complete with the network number only - four numbers separated by dots, as shown below.
Example - use-net: 193.87.45.0 or Example - use-net: <no>
For easier error detection/consistency checking the network name could additionally be mentioned, if possible, i.e. if known.
This could work - providing people specify exactly the same network name as they have in the database. Otherwise it is not really of much use. Again, it must not be confused with the DNS names. I have incorporated it for the time being. See what other people think.
iso-net:
[...]
Part D: ------
If you are applying for more than 2 Class C network numbers then on a separate page, please submit a description of your network plans. The more numbers you are requesting, the more detailed your technical description will need to be. Furthermore, the more detail you provide, the quicker we will be able to process your application.
Please read the supporting documentation (currently under preparation) which will guide you. It is particularly important to read this document
if you are applying for a class B network number, as it provides a number
of helpful hints. It is available from: <supporting-ipdocs@wherever.net>
Please consider the following in your description:
It is always a good idea to ask requestors for B addresses what subnet mask they want to apply.
Current network layout: Future network plans:
just my 2 cents ...
Many thanks for your useful comments. I'll put a second draft out soon. Regards, Anne.
regards, Peter
participants (2)
-
Anne Lord
-
Peter Koch