idnits 2.17.1 draft-wenzel-nsrc-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1384 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. ** There are 211 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 482 has weird spacing: '...mpleted form ...' == Line 492 has weird spacing: '...t). If you a...' == Line 650 has weird spacing: '...mpleted form ...' == Line 790 has weird spacing: '...most of the I...' == Line 938 has weird spacing: '...shed by your ...' == (1 more instance...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 2000) is 8747 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 1018 looks like a reference -- Missing reference section? '2' on line 1021 looks like a reference -- Missing reference section? '3' on line 1025 looks like a reference -- Missing reference section? '4' on line 1029 looks like a reference -- Missing reference section? '5' on line 1034 looks like a reference -- Missing reference section? '6' on line 1038 looks like a reference -- Missing reference section? '7' on line 1041 looks like a reference -- Missing reference section? '8' on line 1046 looks like a reference -- Missing reference section? '9' on line 1049 looks like a reference -- Missing reference section? '10' on line 1052 looks like a reference -- Missing reference section? '11' on line 1055 looks like a reference -- Missing reference section? '12' on line 1058 looks like a reference -- Missing reference section? '13' on line 1062 looks like a reference -- Missing reference section? '14' on line 1066 looks like a reference -- Missing reference section? '15' on line 1070 looks like a reference -- Missing reference section? '16' on line 1073 looks like a reference -- Missing reference section? '17' on line 1075 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 9 warnings (==), 20 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Z. Wenzel 2 draft-wenzel-nsrc-03.txt J. Klensin 3 expires 11/01/00 R. Bush 4 S. Huter 5 Network Startup Resource Center 6 May 2000 8 This document is an Internet-Draft and is in full conformance with all 9 provisions of Section 10 of RFC2026. 11 Internet-Drafts are working documents of the Internet Engineering Task 12 Force (IETF) , its areas, and its working groups. Note that other 13 groups may also distribute working documents as Internet-Drafts. 15 Internet-Drafts are draft documents valid for a maximum of six months 16 and may be updated, replaced, or rendered obsolete by other documents 17 at any time. It is inappropriate to use Internet-Drafts as reference 18 material or to cite them other than as "work in progress." 20 The list of current Internet-Drafts can be accessed at 21 http://www.ietf.org/ietf/1id-abstracts.txt. 23 The list of Internet-Draft Shadow Directories can be accessed at 24 http://www.ietf.org/shadow.html. 26 Guide to Administrative Procedures of the Internet Infrastructure 28 Table of Contents 29 Abstract 30 Who Should Read This Document 31 Checklist 32 Prerequisites 33 I. Preparation of Systems and Network Planning 34 A. What do I need to connect to the Internet? 35 B. What connectivity medium should I choose? 36 C. What else do I need to do? 37 D. How do I get the documents referred to in this guide? 38 E. Section References 39 II. Address Space Allocation 40 A. Who is my upstream provider? 41 B. How much address space should I ask for? 42 C. What is CIDR? 43 D. How do I request and register address space? 44 E. Section References 45 III. Autonomous Systems (AS) 46 A. What is an ASN and do I need one? 47 B. How do I register an ASN? 48 C. Section References 49 IV. Routing and Exchange Points 50 A. Do I need to register with a routing database? 51 B. What about CIDR and routing? 52 C. How do I choose a routing database? 53 D. How do I register in the RADB (The Americas)? 54 E. Section References 55 V. Domain Name Registration 56 A. What is a country domain? 57 B. How do I register as a country domain? 58 C. What if my country is already registered? 59 D. How do I resolve a country domain name dispute? 60 E. Section References 61 VI. IN-ADDR.ARPA Domain Delegation 62 A. What is an IN-ADDR.ARPA domain and do I need one? 63 B. How do I register an IN-ADDR.ARPA domain? 64 VII. Security 65 A. Is there a way to prevent unauthorized changes to my 66 objects? 67 VIII. Network Optimization and Management 68 A. How do I optimize traffic on my network? 69 Acknowledgements 70 References 71 Authors' Addresses 72 Appendix A: The Internet Agencies 73 Appendix B: Documentation 74 Appendix C: Country Codes 75 Appendix D: Acronyms 77 Abstract 79 This document describes the administrative procedures for networks 80 seeking to connect to the global Internet. This includes the steps and 81 operations necessary for address space allocation and registration, 82 routing database registration, and domain name registration. The 83 document also contains information about the required forms and how to 84 obtain them. 86 Who Should Read This Document 88 This document is intended for system engineers and technical managers 89 of networks who want to make a connection to the Internet. It assumes 90 a basic knowledge of the Internet and networking. 92 This information is intended to help new or expanding networks 93 understand and follow the Internet administrative procedures, and to 94 provide assistance in filling out the various templates and 95 registration forms. Appendix D is a glossary of acronyms. 97 Checklist 99 This document will explain the following procedures: 101 o Determine your organization type and current status. 102 o Determine your administrative and technical contacts. 103 o Determine your budget (and chargeback system) and choice of 104 carriers. 105 o Determine to whom you will connect. 106 o Predict your current and projected address space needs. 107 o Set-up your system to connect. 108 o Request and register your address space allocation. 109 o Request and register an autonomous system number, if needed. 110 o Register with a routing database, if needed. 111 o Register your country's domain name, if needed. 112 o Request and register your IN-ADDR.ARPA domain name, if needed. 114 Prerequisites 116 This document assumes that you have examined different alternatives for 117 physical connectivity and will assist you in navigating the Internet 118 infrastructure so that you can use that connectivity. In choosing your 119 upstream provider, you should consider their ability to deal with the 120 Internet infrastructure. 122 What will you be doing and what role will you play? 124 o If you are interested in connecting yourself (or a small 125 organization), you are an Internet end user. You will probably want to 126 contact an Internet Service Provider (ISP) for most of your needs. 127 Read section I and the first part of section II. 129 o If you are interested in connecting your organization and in 130 having address space to distribute within your network, you are an 131 Internet high volume end user. You will need more address space, but 132 still may chose to work with an Internet Service Provider (ISP) for 133 most of your needs. Read sections I and II. 135 o If you are interested in connecting your organization, and in 136 distributing addresses to your clients (who are end users), you are an 137 Internet Service Provider (ISP). You will need to contact a Local 138 Internet Registry (if one is available, or your upstream provider). 139 Read section I and continue reading the rest of this document. 141 o If you are interested in distributing addresses to your clients 142 and your clients are in turn distributing addresses, you are a Local 143 Internet Registry or large ISP. You will probably need to contact the 144 Regional Internet Registry in your geographical area. Read section I 145 and continue reading the rest of this document. 147 I. Preparation of Systems and Network Planning 149 STEP ONE: PREPARE INFORMATION, ORGANIZE HARDWARE, FIGURE OUT TO WHOM 150 YOU WILL CONNECT, AND TEST IN-COUNTRY SYSTEMS. 152 A. What do I need to connect to the Internet? 154 You can connect using dial-up or dedicated lines, and you can choose 155 UUCP or IP. It is preferable to be running the UNIX operating system 156 with TCP/IP over a dedicated line, although you can begin by using UUCP 157 over a dial-up line. Although there are alternatives to UNIX, for 158 historical reasons and robustness UNIX is better prepared to handle 159 Internet connectivity. It is best to use TCP/IP inside your network 160 even if you use another method for your external connectivity. 162 You will need to obtain an Internet Protocol (IP) address, or block of 163 addresses, and a domain name. You may also need an Autonomous System 164 Number (ASN) and an IN-ADDR.ARPA (reverse addressing) domain name. 165 However, you may begin by having dial-up connectivity to another 166 organization that supports one or more mail exchange (MX) record(s) for 167 your site. This would allow you to receive email at your own domain 168 name without requiring you to invest as much initially. 170 B. What connectivity medium should I choose? 172 You may be constrained by telecommunications regulations in your 173 country as to your choice of dial-up, digital phone lines, fiber optic 174 cable, or satellite suppliers. If not, cost, bandwidth, and 175 reliability will determine your choice. 177 C. What else do I need to do? 179 Before you do anything else: 181 1. Designate an administrative contact person and a technical 182 contact person. 184 Choose one person to be the administrative contact and another person 185 to be the technical contact. Write down their full names, email and 186 postal addresses, and telephone and fax numbers (with country prefixes 187 in the form + country code (e.g., +011), city code, and local telephone 188 number). The administrative contact should be a member of your 189 organization and must reside in the country. The technical contact 190 should be the key network support person and may be represented 191 initially by someone outside of the country. Note that the technical 192 contact must transition to a network support person residing in the 193 country. The Internet Registries will request this information in the 194 form of database entries called objects. For example, on the RIPE 195 template, the administrative contact should be listed in the admin-c 196 field in the database objects, and the technical contact in the tech-c 197 field in the database objects (more information on database objects 198 follows in section II D below). 200 2. Determine your cost-recovery charging scheme, if needed, so that you 201 can sustain operations. 203 No form or record will specifically request this, but it is important 204 that you project your costs adequately so that you can assess fees to 205 cover them and ensure stability of operations. 207 3. Diagram your network topology. 209 Determine the number of groups and end users. Describe the size and 210 shape of your current network. Design your addressing plan based on 211 this information. It may be helpful to consider your organization 212 chart when doing this, if you anticipate it to be fairly stable. 214 If you are restricted to using the local telecommunications company's 215 telephone circuit, choose your circuit carrier based on capacity and 216 where it lands geographically. Consider an asymmetric circuit, e.g. 217 128kbps in and 64kbps out, if you expect to have more incoming traffic 218 than outgoing (e.g., if most of the traffic is expected to originate 219 from web servers outside your network). 221 4. Determine to whom you will connect. 223 See the prerequisites section for types of connection providers that 224 might be appropriate for your situation. Determine which ISP or 225 telecommunications company best fits your connectivity needs. 227 5. Predict your address space and bandwidth requirements from end 228 user needs. 230 Since address space is finite and must be conserved, end users are not 231 permitted to reserve address space. Address space is based on what 232 your needs are and how you justify those needs. Evaluation of IP 233 address space requests is usually based on the documentation you 234 provide for the following 24 months (as per RFC 2050), as specified in 235 the address space usage template and in the addressing plan you 236 submit. Once you have used your assigned address space, you can 237 request additional space based on an updated estimate of growth in your 238 network. This usually includes detailed documentation, updating the 239 appropriate regional registry database with details of your end user 240 assignments, and assigning address space both conservatively and 241 efficiently. 243 You will need to justify your needs for address space by communicating 244 your network design and should be prepared to clearly present your plan 245 for effective use of the request. Determine your current and future 246 user needs. If you are offering virtual web services, it is no longer 247 necessary to assign one IP address per domain. HTTP/1.1 defines the 248 "host" header to allow vanity names without the use of an IP address. 249 Allocations for points of presence (POP) throughout your region should 250 also be determined. Predictions of user behavior can be based on 251 analysis of published rates, interviews with individual and 252 institutional subscribers, and case histories of other countries (see 253 "History of the Internet in Thailand"). For example, 255 Area1 256 10 dialup modems 257 10 leased lines to organization's LANs (size of the LANs) 258 Area2 259 5 dialup modems 260 Main POP 261 5 servers: mail, WWW, DNS, FTP, etc. 263 When you design your plan, you should do it for what you need now, what 264 you believe you will need six months from now, and then one year and 265 two years from now. 267 6. Set up, connect, and test your hardware and software. 269 It is important to ensure that you have enough representative systems 270 set up and their connectivity tested using temporary addresses before 271 contacting the appropriate agency for address space. 273 D. How do I get the documents referred to in this guide? 275 See Appendix B for details on obtaining the documents referred to in 276 this guide. 278 E. Section References 280 For more information on TCP/IP, see RFC 2151, "A Primer on Internet and 281 TCP/IP Tools and Utilities." 283 II. Address Space Allocation 285 STEP TWO: OBTAIN ADDRESS SPACE ALLOCATION AND REGISTRATION FROM THE ISP 286 YOU ARE CONNECTING TO, OR (AS A LAST RESORT) YOUR REGIONAL REGISTRY. 288 Internet Protocol (IP) addresses (under the current version 4) are 289 32-bit numbers usually expressed as 4 octets in dotted decimal notation 290 (for example, 128.223.162.27, which is the IP address for the Network 291 Startup Resource Center (NSRC) web server at the time of this 292 writing). Public IP addresses make up the Internet address space. 293 Addresses are allocated in a hierarchical manner and are designed to be 294 unique. 296 The Internet Assigned Numbers Authority (IANA) allocates large address 297 blocks to the three current Regional Internet Registries (IRs): ARIN, 298 APNIC, and RIPE NCC which, in turn, allocate smaller blocks to Local 299 Internet Registries or large ISPs. Local Internet Registries, which 300 are typically ISPs or collections of ISPs represented at a country 301 level, and large ISPs process the vast majority of address space 302 assignments to ISPs and end users 304 Contact the Internet service provider from whom you are getting your 305 connectivity services (your upstream provider) with an address 306 allocation request. It is important and required that you contact your 307 upstream provider first, and not the Regional IR automatically. The 308 first question the Regional Registry will ask you is why you cannot get 309 address space from your upstream provider. 311 A. Who is my upstream provider? 313 If there is an ISP already functioning in your country, contact them 314 directly. If you are to be the first connection in your country, you 315 may need to contact your Regional IR in your geographic region, but you 316 should always contact your upstream provider first for assistance and 317 guidance. Since address allocation is hierarchical, the administrative 318 organizations and procedures also represent this hierarchical 319 structure. It is important not to skip a step in the hierarchy. 320 Current Regional Registries include ARIN (the Americas, Caribbean, and 321 Africa), RIPE (Europe, Africa, and the Middle East), and APNIC (the 322 Pacific Rim and Asia). Contact information for these organizations is 323 listed in Appendix A. 325 You should contact your Regional Internet Registry if 1) the ISP you 326 are connecting to is unable or unwilling to provide address space, or 327 2) your particular connectivity requirements will result in non-local 328 data to your customers possibly taking a different route over the 329 Internet than data destined for your upstream provider's customers, or 330 3) you anticipate a quick growth rate that may require changing your 331 current upstream provider to a larger one and you wish to avoid the 332 renumbering that such a move would require. 334 B. How much address space should I ask for? 336 Regional IRs typically assign address blocks on the basis of an 337 immediate need and projected utilization rate within one year. (If you 338 are in the ARIN region, it is one year for end user organizations and 339 three months for ISPs.) Calculate your address space request 340 accordingly. It is recommended to include the organization chart and 341 network topology diagram referred to in section I.C, number 3 (above). 342 Note that address space is allocated based on CIDR bit boundaries (see 343 next section). The registries will need to understand your network 344 engineering and deployment plans in significant detail before they can 345 allocate address space. Therefore, the more detailed information you 346 can provide, the more likely your request will be processed quickly. 348 If you obtain address space from your ISP, it is very likely that you 349 will need to renumber should you decide to change upstream providers 350 and/or if you grow considerably. As this renumbering may affect your 351 customers (and their customers, etc.) if they are using dedicated 352 lines, you should carefully weigh the cost/benefit involved in 353 obtaining address space from your upstream provider. 355 If you are singly homed, you should obtain your address space from your 356 upstream ISP. If you plan on enlarging but remaining singly homed, you 357 should continue to obtain space this way as it promotes aggregation. 358 If, however, you plan to be multi-homed as part of your growth plan, it 359 would make sense to become a member of an appropriate Regional IR (or, 360 if one exists in your region, a national Network Information Center 361 (NIC) and obtain a /19 or "provider aggregatable" address space. 363 The minimum routable block is often a /19, so if you plan on enlarging, 364 it is better to pay the fees to the Regional IR now and obtain a /19 365 block so that you will not have to renumber later. Note that if you 366 are an ISP in the ARIN region, ARIN has special requirements before 367 you can do this in terms of the amount of address space you have 368 previously used, which must be a /21. The current policy is that you 369 must have used a /19 previously from your upstream ISP before going to 370 ARIN. Or you must be multi-homed and show you have used a /21 and be 371 willing to renumber and ARIN will issue a /20 from a reserved /19. 373 As of February 8, 1999, ARIN lowered the minimum allocation size for IP 374 addresses from a /19 to a /20. ARIN will issue initial allocations of 375 prefixes no longer than /20. If allocations smaller than /20 are 376 needed, ISPs and end users should request address space from their 377 upstream provider. ARIN does not guarantee that addresses will be 378 globally routable. 380 APNIC and RIPE NCC do not have these requirements. For APNIC, new 381 allocations to members will be a /19. 383 Remember that your upstream provider should route you if you ask them. 384 You are a customer of the ISP, so if the service is not what you need 385 you should change ISPs. 387 IF YOU ARE CONNECTED TO ONLY ONE PROVIDER, AND ARE NOT VERY LARGE YET, 388 GET AN ADDRESS RANGE FROM YOUR PROVIDER. SKIP THE REST OF THIS SECTION 389 AND ALL OF SECTION V. 391 C. What is CIDR? 393 CIDR stands for Classless Inter-Domain Routing. Historically, IP 394 addresses were assigned within classes: Class A (8 bits of network 395 address, 24 bits of host address), Class B (16 bits of network address, 396 16 bits of host address), or Class C (24 bits of network address, 8 397 bits of host address). With the advent of CIDR, address space is now 398 allocated and assigned on bit boundaries. Using CIDR means you are 399 able to assign addresses corresponding with the number of hosts on the 400 network, thereby conserving address space. 402 The following table illustrates this: 404 Addrs Bits Pref Class Mask 406 1 0 /32 255.255.255.255 407 2 1 /31 255.255.255.254 408 4 2 /30 255.255.255.252 409 8 3 /29 255.255.255.248 410 16 4 /28 255.255.255.240 411 32 5 /27 255.255.255.224 412 64 6 /26 255.255.255.192 413 128 7 /25 255.255.255.128 414 256 8 /24 1C 255.255.255.0 415 512 9 /23 2C 255.255.254.0 416 1K 10 /22 4C 255.255.252.0 417 2K 11 /21 8C 255.255.248.0 418 4K 12 /20 16C 255.255.240.0 419 8K 13 /19 32C 255.255.224.0 421 Addrs 422 Number of addresses available; note that the number of 423 addressable hosts normally is 2 less than this number 424 because the host parts with all equal bits 425 (all 0s, all 1s) are reserved. 426 Bits 427 Size of the allocation/assignment in bits of address 428 space. 429 Pref 430 Length of the prefix covering this address space. This 431 is sometimes used to indicate the size of an 432 allocation/assignment. 433 Class 434 Size of the address space in terms of class C network 435 numbers. 436 Mask 437 The network mask defining the routing prefix in dotted 438 quad notation. 440 (From http://www.ibm.net.il/~hank/cidr.html) 442 D. How do I request and register address space? 444 You will need to send a database object to the appropriate registry to 445 request and register address space. The registration databases are 446 composed of records that are a series of fields separated by one or 447 more blank lines; each field consists of two parts, the tag and the 448 value. Do not modify the tags in the templates or errors will occur. 449 Values for particular fields are specified in the templates; be careful 450 to enter appropriate information. 452 The first line of a template denotes the record type. For example, an 453 IP address template's first line is inetnum, therefore the record is 454 known as an inetnum object. This first line is also used as the 455 primary key for the record, therefore if you want to modify the first 456 field of the record, the only way to do so is to delete the record 457 entirely and add a new record with the corrected information. 459 For illustration, here is the RIPE inetnum object. 461 inetnum: [IP address range that will be assigned] 462 netname: Network-Name 463 descr: Network-Name Communications Company, Town 464 admin-c: NIC-handle of administrative contact 465 tech-c: NIC-handle of technical contact 466 country: ISO 3166-country-code 467 rev-srv: ns.someserver.net 468 rev-srv: ns.otherserver.net 469 status: assigned pa (provider aggregatable) 470 or assigned pi (provider independent) 471 changed: email@address.net 960731 472 source: RIPE 474 For Countries in the APNIC Region 476 In order to obtain services from APNIC, you will need to become a 477 member. APNIC-070 is the APNIC Membership Application. It is located 478 at: 480 ftp://ftp.apnic.net/apnic/docs/membership-application 482 Send the completed form via email to APNIC at: 484 member-apply@apnic.net 486 APNIC Address Allocation Requests: 488 Once you have become a member, you can request IP address space using 489 one of the three IP address request forms. If you are an organization 490 that will use address space internally only (e.g., large enterprises 491 such as universities, government ministries, large corporations, etc.), 492 choose #1 (End User Address Request). If you are an organization that 493 plans to sub-delegate address space to customers (e.g., you are an 494 ISP), choose #2 (ISP Address Request). If you are a confederation of 495 ISPs (e.g., national NICs, etc.), choose #3 (Confederation Address 496 Request). 498 1. APNIC-074 is the APNIC End User Internet Address Request Form. 500 2. APNIC-065 is the APNIC Internet Services Provider Internet 501 Address Request Form. 503 3. Confederations are a means by which service providers can group 504 together to provide resource allocation and registration services 505 tailored to their specific local language and cultural requirements. 506 For details on how to become an APNIC recognized confederation, please 507 see APNIC Confederation Concepts and Requirements located at: 509 ftp://ftp.apnic.net/apnic/docs/confed-requirements 511 APNIC-074 is the APNIC Confederation Internet Address Request Form. 513 Copies of all forms can be found in the following directory: 515 ftp://ftp.apnic.net/apnic/docs 516 or 517 http://www.apnic.net/reg.html 519 All completed forms should be sent to: 521 hostmaster@apnic.net 523 If there are strong reasons why you cannot obtain address space from 524 your upstream ISP, and you require address space as a one-time 525 allocation only, you can obtain address space as a "non member." For 526 more details, see APNIC-071: 528 http://ftp.apnic.net/apnic/docs/non-member-application 530 and send the completed form to: 532 billing@apnic.net 534 For Countries in the ARIN Region 536 Membership in ARIN is optional and not a requirement for requesting IP 537 address space from the registry or from your Internet service 538 provider. If you are a large end user organization, choose #1. If you 539 are an ISP, choose #2. 541 1. The form for network number assignments is located at: 543 ftp://rs.arin.net/templates/networktemplate.txt 544 or 545 http://www.arin.net/templates/networktemplate.txt 547 2. The form for ISPs to obtain a CIDR block of IP network numbers is 548 located at: 550 ftp://rs.arin.net/templates/isptemplate.txt 551 or 552 http://www.arin.net/templates/isptemplate.txt 554 Send either completed form via email to ARIN at: 556 hostmaster@arin.net 558 with "IP request" (if you chose #1) or "ISP CIDR request" (if you chose 559 #2) in the subject field, as appropriate. 561 For Countries in the RIPE Region 563 RIPE NCC provides IP address space allocation only to contributing 564 local Internet registries. For a description of the European Internet 565 Registry policies and procedures, see RIPE-159, "European Internet 566 Registry Policies and Procedures." It is located at: 568 ftp://ftp.ripe.net/ripe/docs/ripe-159.txt 570 RIPE-160 is Guidelines for Setting up a Local Internet Registry. It is 571 located at: 573 ftp://ftp.ripe.net/docs/ripe-160.txt 575 If you have questions regarding setting up a new local IR, please 576 contact the RIPE NCC at: 578 new-lir@ripe.net 580 Once your local IR is established, you will get detailed information on 581 how to submit requests to the RIPE NCC hostmaster. 583 Send the completed form via email to RIPE NCC at: 585 ncc@ripe.net 587 If you have general queries, please contact RIPE NCC at: 589 ncc@ripe.net 591 E. Section References 593 For more information on IP addresses, see RFC 1518, "An Architecture 594 for IP Address Allocation with CIDR" and RFC 2050, "Internet Registry 595 IP Allocation Guidelines." 597 III. Autonomous Systems (AS) 599 STEP THREE: IF NEEDED, OBTAIN AN AUTONOMOUS SYSTEM NUMBER. 601 A. What is an ASN and do I need one? 603 Autonomous System Numbers (ASNs) are used to facilitate routing in 604 multi-homed environments. They are allocated when your routing policy 605 is different from your provider's. This generally means your site is 606 multi-homed. In nearly all cases, unless you are multi-homed to more 607 than one ISP, you will not need an ASN. If your routing policy does 608 not differ from your service provider's, you should use the service 609 provider's ASN. If there is constant traffic between you and a point 610 in another country, you may want to connect to a second ISP in that 611 country. Note that the resultant multi-homing generally makes the 612 system more robust and may also change registry (and therefore request) 613 relationships. It also increases costs greatly. 615 You may have to reduce traffic on your international lines by choosing 616 to connect to a local exchange point. This allows traffic to stay 617 within your country and off of expensive international links. If you 618 implement this plan, you will be multi-homed and will need to read the 619 autonomous systems and routing 621 sections of this document. 623 B. How do I register an ASN? 625 Since the ASN space is quite limited, request only what you really need 626 when you need it. 628 For Countries in the APNIC Region 630 APNIC-066 is the ASN Request Form. The form is located at: 632 http://ftp.apnic.net/apnic/docs/asn-request 634 Send the completed form via email to APNIC at: 636 hostmaster@apnic.net 638 For Countries in the ARIN Region 640 A complete listing of assigned ASNs is located at: 642 ftp://rs.arin.net/netinfo/asn.txt 644 The ASN registration form is located at: 646 ftp://rs.arin.net/templates/asntemplate.txt 647 or 648 http://www.arin.net/templates/asntemplate.txt 650 Send the completed form via email to ARIN at: 652 hostmaster@arin.net 654 with "ASN request" in the subject field. 656 For Countries in the RIPE Region 658 The European Autonomous System Number Application Form and Supporting 659 Notes form (RIPE-147) is located at: 661 ftp://ftp.ripe.net/ripe/docs/ripe-147.txt 663 Local IRs can send the completed form via email to RIPE at: 665 hostmaster@ripe.net 667 C. Section References 669 For more information on ASNs, see RFC 1930, "Autonomous Systems (AS)." 671 IV. Routing and Exchange Points 673 STEP FOUR: IF NEEDED, REGISTER WITH A ROUTING DATABASE. 675 A. Do I need to register with a routing database? 677 You do not need to register with a routing database if you are simply 678 carrying default routes to your (single) ISP. If you get your address 679 space from an ISP, the ISP will register you. If you are connected to 680 more than one ISP, then you should register with a routing database. 682 The more multi-homed you are, the larger your routing tables need to 683 be. If you are connected to public exchange points (see examples 684 below), or to more than one backbone ISP, you need to carry full 685 routing tables and run without a default route. 687 Example European Exchange Points: 689 LINX London Internet Exchange 690 M9-IX Moscow Internet Exchange 691 NIX.CZ Neutral Internet Exchange, Czech Republic 693 Example Asia/Pacific Exchange Points: 695 AUIX Australia Internet Exchange 696 HKIX Hong Kong Internet Exchange 697 JPIX Japan Internet Exchange 699 Example Americas Exchange Points: 701 MAE-EAST Metropolitan Area Ethernet - East 702 MAE-WEST Metropolitan Area Ethernet - West 703 PAIX Palo Alto Internet Exchange 705 Depending on the requirements of your international ISP, you may be 706 able to have only a default route to them and specific routes to other 707 suppliers if you have an in-country exchange point. Or they may 708 require that you carry a full set of routes, treating your connection 709 to the in-country exchange point as if it were a multi-homed 710 connection. 712 B. What about CIDR and routing? 714 All registries use CIDR. All major router vendors (Cisco, 3Com, Nortel, 715 Proteon, IBM, etc) support CIDR. CIDR Internet routers use only the 716 prefix of the destination address to route traffic to a subnetted 717 environment. 719 C. How do I choose a routing database? 721 The Internet Routing Registry (IRR) describes registries maintained by 722 several national and international networking organizations. These 723 currently include the RIPE Network Coordination Centre (NCC), ANS 724 (Advanced Network Solutions, Inc.), Bell Canada (formerly CA*net), 725 Cable and Wireless (CW), and the Routing Arbiter Database (RADB). The 726 IRR is a way for ASNs to publicize their own intended routing policies 727 without having to request a change from a go-between. 729 WHOIS queries to "whois.ra.net" return data that they gather from the 730 entire IRR set of routing registries. Tools such as "peval" and 731 "rtconfig" return data only from the RADB. Thus, when running those 732 tools and desiring data from a set of registries, one must enumerate 733 them as in the following example. WHOIS queries to the client 734 configure the precedence of routing databases. For example: 736 @RtConfig set sources = "TEST, RADB, RIPE, ANS, BELL, CW" 738 There are several other registries, such as ALTDB. A list, and other 739 information on RADB, is available at: 741 http://www.radb.net/ 743 As of January 1, 2000, the transition to the Routing Policy 744 Specification is Language (RPSL) complete. RIPE-181 object submissions 745 are no longer accepted. For more information, see: 747 http://www.merit.edu/radb/announce.html 749 With the exception of the Routing Arbiter Database, each registry 750 serves a limited customer base. ANS, Cable and Wireless, and Bell 751 Canada accept routing registrations for their customers alone, and the 752 RIPE NCC oversees European registrations. The Routing Arbiter Database 753 is unique in that it handles registrations for networking organizations 754 not covered by the other routing registries. The Routing Arbiter also 755 provides coordination among all the registries to ensure consistent 756 representation of routing policies. 758 All Regional IRs need to register with one (only one) of the routing 759 databases in the IRR. If you are announcing routes via BGP4, you need 760 to register your routes in the Routing Registry in only one of the 761 IRR's. Logically, this will be the "closest" IRR to you. However, 762 note that some ISPs do not use the regional registries or RADB. 764 D. How do I register in the RADB (The Americas)? 766 You need to submit three types of database records to the RADB: one or 767 more maintainer objects, an AS object, and one or more route objects. 769 To specify the individuals who are allowed to update your records in 770 the RADB, fill out one or more maintainer objects and send them via 771 email to: 773 db-admin@radb.net 775 You need to submit a maintainer object before you can register any AS 776 or route objects. 778 To describe the autonomous system that announces your routes, fill out 779 an AS object and submit it via email to: 781 auto-dbm@radb.net 783 AS objects are also called aut-num objects. 785 To register your routes, fill out one or more route objects, and send 786 them to RADB via email to: 788 auto-dbm@radb.net 790 Note that most of the IRR participants have the auto-dbm@xx.net email 791 address function for accepting updates to the IRR automatically. 793 E. Section References 795 For more information on routers, see RFC 1812, "Requirements for IP 796 Version 4 Routers." See also RFC 1786, "Representation of IP Routing 797 Policies in a Routing Registry (ripe-181++)." 799 For more information on CIDR and routing, see RFC 1817, "CIDR and 800 Classful Routing." 802 V. Domain Name Registration 804 STEP FIVE: REGISTER YOUR DOMAIN NAME. 806 A. What is a country domain? 808 The Domain Name System (DNS) specifies the naming of computers within a 809 hierarchy. Top-Level Domain (TLD) names include generic TLDs (gTLDs) 810 and two-letter country codes (ccTLDs). Examples of gTLDs include .com 811 (commercial), .net (network), and .org (organization). Examples of 812 two-letter country codes are .id for Indonesia, .ca for Canada, and .fr 813 for France. ISO 3166 is used as a basis for country code top-level 814 domain names. Country codes are assigned by the International 815 Organization for Standardization (ISO) in cooperation with the United 816 Nations. The Internet Assigned Numbers Authority (IANA) directly 817 registers all country-code top-level domains, however it is not 818 involved in the allocation of codes to countries. IANA is a function 819 pf the Internet Corporation for Assigned Names and Numbers (ICANN, see 820 Appendix A). See ISO 3166 for more information and a current listing 821 of country codes (Appendix C). 823 A hierarchy of names may, and normally should be, created under each 824 TLD. There is a wide variation in the structure of country domains. 825 In some countries there is a substantial hierarchy, while in others the 826 structure is flat. In some country domains the second levels are 827 generic categories, while in others they are based on geography, and in 828 still others, organization names are listed directly under the country 829 code. Examples of second level generic categories are ac or edu 830 (academic or education), co or com (corporate or commercial), and go or 831 gov (government). 833 B. How do I register as a country domain? 835 First check that: (1) the domain is still available, few are, (2) you 836 have someone in your country as the administrative contact, and (3) 837 your name servers are prepared (see RFC 1912 for information on common 838 errors in preparing name servers). 840 The whois master database is the authoritative source of information on 841 .com, .net, .org, and .edu domain name registrations. It is currently 842 maintained by Network Solutions, Inc. and holds referal pointers to 843 which whois database contains the record for the domain name. 845 To apply to manage a country code top-level domain you should: 847 1. First, if you are on a UNIX host, use the whois command to see 848 if the domain is already registered: 850 whois = 852 2. If the domain does not already have an administrative contact, 853 request a Domain Name Agreement template from IANA by sending email 854 to: 856 iana@iana.org 858 C. What if my country is already registered? 860 If your country is already registered, contact the country-code 861 administrator to register a new second-level domain name. 863 Please note that ARIN, RIPE, and APNIC do not handle domain names 864 (other than IN-ADDR.ARPA). If you want to register a domain name 865 directly under a top-level domain (TLD), please contact the appropriate 866 TLD administrator. 868 D. How do I resolve a country domain name dispute? 870 See RFC 1591 for domain name dispute information. Note that you will 871 need to resolve the dispute within your country before you contact 872 IANA. 874 E. Section References 876 For more information on domain names, see RFC 1591, "Domain Name System 877 Structure and Delegation"; RFC 1713, "Tools for DNS Debugging"; and RFC 878 1912, "Common DNS Operational and Configuration Errors." 880 VI. IN-ADDR.ARPA Domain Delegation 882 STEP SIX: IF NEEDED, REGISTER YOUR IN-ADDR.ARPA DOMAIN. 884 A. What is an IN-ADDR.ARPA domain and do I need one? 886 An IN-ADDR.ARPA domain allows for mapping of IP addresses into domain 887 names. This is often referred to as "inverse addressing" because it is 888 the opposite of the domain name to IP address resolution. IN-ADDR 889 domains are represented using the network number in reverse. For 890 example, the IN-ADDR domain for network 123.45.67.0 is represented as 891 67.45.123.in-addr.arpa. 893 You almost always need reverse resolution. 895 B. How do I register an IN-ADDR.ARPA domain? 897 You should ask your upstream provider about registering your 898 IN-ADDR.ARPA domains. If you are working directly with a regional 899 registry, see below. 901 For Countries in the APNIC Region 903 The IN-ADDR.ARPA Delegation Form is APNIC-064 and is located at: 905 ftp://ftp.apnic.net/apnic/docs/in-addr-request 907 CAUTION: You must set-up your name server to accept the delegation 908 prior to submission of this form. 910 Send the completed form via email to APNIC at: 912 domreg@rs.apnic.net 914 For Countries in the ARIN Region 916 How IN-ADDR.ARPA is registered is dependent on the registration of the 917 block needing reverse entries. For example, all blocks that have been 918 registered directly from the Regional IR may have IN-ADDR.ARPA 919 delegation established by ARIN. In this case, IN-ADDR.ARPA delegations 920 are registered using the ARIN modify template. This template can be 921 found at: 923 ftp://ftp.arin.net/templates/modifytemplate.txt 925 or 926 http://www.arin.net/templates/modifytemplate.txt 928 Instructions for completing the template can be found at the bottom of 929 the template. 931 CAUTION: Do not list your network number in reverse on the template. 933 Send the completed form via email to ARIN at: 935 hostmaster@arin.net 937 All blocks that have been reassigned to your organization by an ISP 938 will have IN-ADDR.ARPA established by your provider. In this case, 939 contact the ISP that reassigned IP address space to your organization 940 and coordinate IN-ADDR.ARPA delegation. 942 For Countries in the RIPE Region 944 The domain object needs to be entered in the RIPE database before 945 requesting reverse delegation. 947 domain: 0.194.in-addr.arpa 948 descr: Our organization allocation 949 admin-c: NIC-handle of administrative contact (e.g., JLC-2RIPE) 950 tech-c: NIC-handle of technical contact 951 zone-c: NIC-handle of zone contact 952 nserver: Name server (e.g., ns.someserver.net) 953 nserver: ns.otherserver.net 954 nserver: ns.ripe.net 955 changed: email@address.net 960731 956 source: RIPE 958 NOTE: One of the name servers has to be ns.ripe.net 960 The domain object described above should be included in the request, as 961 well as zone file entries for the zone above the one requested. For 962 example, if a reverse delegation is requested for 1.193.in-addr.arpa, 963 the relevant zone file entries should be included for 193.in-addr.arpa; 964 whereas if a reverse delegation is requested for 2.2.193.in-addr.arpa, 965 the zone file entries should be included for 2.193.in-addr.arpa. 967 Send the completed object(s) via email to RIPE at: 969 auto-inaddr@ripe.net 971 VII. Security 973 A. Is there a way to prevent unauthorized changes to my objects? 975 Registries provide various security measures to prevent unauthorized 976 changes to your database entries. Contact your regional IR for more 977 information. Note that the contact information you provide in the 978 database object registrations is not private. 980 VIII. Network Optimization and Management 982 A. How do I optimize traffic on my network? 984 Contact the Cooperative Association for Internet Data Analysis 985 (CAIDA). CAIDA is a collaborative undertaking to promote greater 986 cooperation in the engineering and maintenance of a robust, scalable 987 global Internet infrastructure. CAIDA provides a neutral framework to 988 support these cooperative endeavors. 990 The CAIDA web-site is located at: 992 http://www.caida.org/ 994 Send email with questions or comments to: 996 info@caida.org 998 Acknowledgements 1000 Thanks to Brian Candler, David Conrad, John Heasley, Kim Hubbard, 1001 Daniel Karrenberg, Anne Lord, Dawn Martin, Charles Musisi, Jon Postel, 1002 and April Marine and the IETF User Services Working Group for reviewing 1003 various versions of this document; and to Hank Nussbacher for 1004 permission to reprint his table on CIDR. 1006 Special thanks are also due to Dr. Steven Goldstein of the National 1007 Science Foundation for his contributions and suggestions, and to the 1008 National Science Foundation for partial funding of this work. 1010 This material is based upon work supported by the National Science 1011 Foundation under Grant No. NCR-961657. Any opinions, findings, and 1012 conclusions or recommendations expressed in this material are those of 1013 the author(s) and do not necessarily reflect the views of the National 1014 Science Foundation. 1016 References 1018 [1] Malkin, G., LaQuey Parker, T., "Internet Users' Glossaary", RFC 1019 1392, Xylogics, Inc and U. Texas, January 1993. 1021 [2] Hinden, R., Editor, "Applicability Statement for the 1022 Implementation of Classless Inter-Domain Routing (CIDR)", RFC 1517, 1023 Internet Engineering Steering Group, September 1993. 1025 [3] Rekhter, Y. and Li, T. "An Architecture for IP Address 1026 Allocation with CIDR", RFC 1518, T.J. Watson Research Center, IBM Corp, 1027 Cisco Systems, September 1993. 1029 [4] Fuller, V., Li, T., Yu, J., and Varadhan, K. "Classless 1030 Inter-Domain Routing (CIDR): an Address Assignment and Aggregation 1031 Strategy", RFC 1519, BARRNet, Cisco Systems, MERIT, OARnet, September 1032 1993. 1034 [5] Rekhter, Y. and Topolcic, C. "Exchanging Routing Information 1035 Across Provider Boundaries in the CIDR Environment", RFC 1520, T.J. 1036 Watson Research Center, IBM Corp., CNRI, September 1993. 1038 [6] Postel, J. "Domain Name System Structure and Delegation", RFC 1039 1591, USC/Information Systems Institute, March 1994. 1041 [7] Wijnen, B., Carpenter, G., Curran, K., Sehgal, A. & Waters, G., 1042 "Simple Network Management Protocol Distributed Protocol Interface 1043 Version 2.0", RFC 1592, T.J. Watson Research Center, IBM Corp. and Bell 1044 Northern Research, Ltd., March 1994. 1046 [8] Ramao, A. "Tools for DNS debugging", RFC 1713, FCCN, November 1047 1994. 1049 [9] Baker, F. "Requirements for IP Version 4 Routers", RFC 1812, 1050 Cisco Systems, June 1995. 1052 [10] Rekhter, Y. "CIDR and Classful Routing", RFC 1817, Cisco 1053 Systems, August 1995. 1055 [11] Barr, D. "Common DNS Operational and Configuration Errors", 1056 RFC 1912, The Pennsylvania State University, February 1996. 1058 [12] Hawkinson, J. and Bates, T. "Guidelines for Creation, 1059 Selection, and Registration of an Autonomous System", RFC 1930, BBN 1060 Planet Corporation, MCI, March 1996. 1062 [13] Freed, N. and Borenstein, N. "Multipurpose Internet Mail 1063 Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 1064 2045, Innosoft and First Virtual, November 1996. 1066 [14] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and 1067 Postel, J. "Internet Registry IP Allocation Guidelines", RFC 2050, 1068 InterNIC, APNIC, RIPE, ISI, November 1996. 1070 [15] Kessler, G. and Shepard, S. "A Primer On Internet and TCP/IP 1071 Tools and Utilities", RFC 2151, June 1997. 1073 [16] ISO 3166: "Codes for the Representation of Names of Countries" 1075 [17] Palasri, S., Huter, S., and Wenzel, Z. "The History of the 1076 Internet in Thailand", by University of Oregon Books, 1999. 1078 Authors' Addresses 1080 Zita Wenzel, Ph.D. 1081 Network Startup Resource Center (NSRC) 1082 1225 Kincaid Street 1083 1212-University of Oregon 1084 Eugene, OR 97403-1212 USA 1085 zita@nsrc.org 1087 John C. Klensin, Ph.D. 1088 Network Startup Resource Center (NSRC) 1089 1225 Kincaid Street 1090 1212-University of Oregon 1091 Eugene, OR 97403-1212 USA 1092 klensin@nsrc.org 1094 Randy Bush 1095 Network Startup Resource Center (NSRC) 1096 1225 Kincaid Street 1097 1212-University of Oregon 1098 Eugene, OR 97403-1212 USA 1099 randy@nsrc.org 1101 Steven Huter 1102 Network Startup Resource Center (NSRC) 1103 1225 Kincaid Street 1104 1212-University of Oregon 1105 Eugene, OR 97403-1212 USA 1106 sghuter@nsrc.org 1108 Appendix A: The Internet Agencies 1110 o The Internet Assigned Numbers Authority (IANA) 1112 IANA is the central coordinator for the assignment of unique parameter 1113 values for Internet protocols and for all address space and name space 1114 used in the Internet. IANA allocates parts of the Internet address 1115 space to Regional Internet Registries (IRs) for distribution to Local 1116 IRs and ISPs. IANA is also responsible for the coordination and 1117 management of the Domain Name System (DNS). 1119 Note that as of 1999, IANA is a function of the Internet Corporation 1120 for Assigned Names and Numbers (ICANN), the non-profit corporation that 1121 is the top-level administration authority of the global Internet. 1123 Email: iana@iana.org 1124 Postal: P. O. Box 12607 1125 Marina del Rey, CA 90295-3607 1126 Telephone: +1-310-822-1511 1127 Fax: +1-310-823-6714 1128 Internet: http://www.iana.org/ 1130 o Internet Corporation for Assigned Names and Numbers (ICANN) 1132 >From the ICANN web site: 1134 The Internet Corporation for Assigned Names and Numbers (ICANN) is a 1135 technical coordination body for the Internet. Created in October 1998 1136 by a broad coalition of the Internet's business, technical, academic, 1137 and user communities, ICANN is assuming responsibility for a set of 1138 technical functions previously performed under U.S. Government 1139 contract by IANA and other groups. 1141 Specifically, ICANN coordinates the assignment of the following 1142 identifiers that must be globally unique for the Internet to function: 1143 Internet domain names, IP address numbers, protocol parameter and port 1144 numbers. In addition, ICANN coordinates the stable operation of the 1145 Internet's root server system. 1147 As a non-profit, private-sector corporation, ICANN is dedicated to 1148 preserving the operational stability of the Internet; to promoting 1149 competition; to achieving broad representation of global Internet 1150 communities; and to developing policy through private-sector, 1151 bottom-up, consensus-based means. ICANN welcomes the participation of 1152 any interested Internet user, business, or organization. 1154 Email: icann@icann.org 1155 Postal: Internet Corporation for Assigned Names and Numbers 1156 (ICANN) 1157 4676 Admiralty Way, Suite 330 1158 Marina del Rey, CA 90292 1159 USA 1160 Telehone: +1-310-823-9358 1161 Fax: +1-310-823-8649 1162 Internet: http://www.icann.org/ 1164 o InterNIC 1166 The InterNIC was a cooperative activity between the National Science 1167 Foundation, General Atomics, AT&T, and Network Solutions, Inc. The 1168 joint activity InterNIC no longer exists. 1170 Currently, Network Solutions runs the central registry according to the 1171 shared registry model specified by ICANN for registration of 1172 second-level domain names under the generic top-level domains .com, 1173 .net, and .org. 1175 For information on accredited registrars for .com, .net, and .org, 1176 please see: 1178 http://www.icann.org/registrars/accredited-list.html 1180 (note that Network Solutions is an accredited registrar as well as the 1181 entity running the registry). 1183 Email: hostmaster@netsol.com 1184 Postal: Network Solutions, Inc. 1185 505 Huntmar Park Dr. 1186 Herndon, VA 20170 US 1187 Telephone: +1-703-742-4777 1188 Fax: +1-703-742-9552 1189 Internet: http://www.networksolutions.com/ 1191 Regional Internet Registries (IRs) 1193 Regional IRs operate in large geopolitical regions such as continents. 1194 Currently, there are three Regional IRs: ARIN for the Americas, the 1195 Caribbean, and Africa; RIPE NCC for Europe, Africa, and the Middle 1196 East; and APNIC for the Asia Pacific region. The specific duties of 1197 the Regional IRs include coordination and representation of all local 1198 Internet Registries in their respective region. 1200 o APNIC 1202 Asia Pacific Network Information Center (APNIC) is a non-profit 1203 Internet registry for the Asia Pacific region. APNIC provides IP 1204 address allocation, Autonomous System Number (ASN) assignment, and 1205 IN-ADDR.ARPA registration. 1207 Email: hostmaster@apnic.net 1208 Postal: APNIC Box 2131 1209 Milton Queensland 4064 1210 Australia 1211 Telephone: +61-7-3367-0490 1212 Fax: +61-7-3367-0482 1213 Internet: http://www.apnic.net/ 1215 o ARIN 1217 The American Registry for Internet Numbers (ARIN) is a non-profit 1218 Internet registry that was established for the purpose of 1219 administration and registration of Internet Protocol (IP) numbers to 1220 the geographical areas that were previously managed by Network 1221 Solutions, Inc. These areas include, but are not limited to, North 1222 America, South America, Africa, and the Caribbean region. ARIN 1223 provides IP address allocation, Autonomous System Number (ASN) 1224 assignment, and IN-ADDR.ARPA registration. 1226 Email: hostmaster@arin.net 1227 Postal: 4506 Daly Drive 1228 Suite 200 1229 Chantilly, VA 20151 1230 Telephone: +1-703-227-0660 1231 Fax +1-703-227-0676 1232 Internet: http://www.arin.net/ 1234 o RIPE NCC 1236 Reseaux IP Europens Network Coordination Centre (RIPE NCC) is a 1237 non-profit Internet registry for the European, North African, and 1238 Middle East regions. RIPE NCC provides IP address allocation, 1239 Autonomous System Number (ASN) assignment, and IN-ADDR.ARPA 1240 registration. 1242 Email: ncc@ripe.net 1243 Postal: Singel 258 1244 1016 AB Amsterdam 1245 The Netherlands 1246 Phone: +31-20-535-4444 1247 Fax: +31-20-535-4445 1248 Internet: http://www.ripe.net/ 1250 Appendix B: Documentation 1252 Internet Documentation 1254 For general Internet documentation, ftp to rfc-editor.org and cd to the 1255 /rfc subdirectory for Request for Comments documents. 1257 Details on obtaining these documents via ftp or email may be obtained 1258 by sending 1259 an email message to: 1261 rfc-info@rfc-editor.org 1263 with the message body help: ways_to_get_rfcs. For example: 1265 To: rfc-info@isi.edu 1266 Subject: getting rfcs 1268 help: ways_to_get_rfcs 1270 Documents, Templates, and Forms 1272 The documents, templates, and forms referenced in this guide are 1273 available from the document stores in the directories listed in the 1274 URLs (Uniform Resource Locators). Organizations without connectivity 1275 wishing to obtain copies of the referenced documents should contact 1276 their Local IR to arrange postal delivery of one or more of the 1277 documents. Note that fees may be associated with the delivery of 1278 hardcopy versions of documents. 1280 The document stores can be accessed in two ways: 1282 1. Via anonymous FTP (File Transfer Protocol). 1284 Using your ftp program, connect to the appropriate host computer shown 1285 below using your email address as the password. Use the cd (change 1286 directory) command to connect to the appropriate subdirectory, then use 1287 the get command to retrieve 1288 the specific file. For example: 1290 ftp rs.apnic.net (for countries in the Asia/Pacific region) 1291 ftp rs.arin.net (for countries in the Americas) 1292 ftp rs.ripe.net (for countries in Europe or North Africa) 1294 login: anonymous 1295 password: your_email_address 1297 cd netinfo 1299 get _info.txt 1301 2. Via electronic mail, ftp, or the World Wide Web 1303 Send email to the appropriate address shown below with the message body as 1304 specified. 1306 APNIC Documentation 1308 For APNIC documents and templates, connect to ftp.apnic.net and cd to 1309 /apnic/docs. APNIC no longer has an electronic mail method of form 1310 retrieval. Many of APNIC's request forms are also available on the web 1311 site at: 1313 http://www.apnic.net/reg.html 1315 ARIN Documentation 1317 For ARIN templates, connect to rs.arin.net and cd to /templates. 1319 You can also obtain templates via the web site at: 1321 http://www.arin.net/templates.html 1323 Other ARIN documentation is available at: 1325 http://www.arin.net/docs.html 1327 Or send email to: 1329 hostmaster@arin.net 1331 RIPE Documentation 1333 For RIPE documents and forms, connect to ftp.ripe.net/ripe and cd to 1334 /docs or cd to /forms. 1336 Or send email to: 1338 mail-server@ripe.net 1340 with send help in the body of the message. 1342 Appendix C: Country Codes 1344 The International Organization for Standardization (ISO) 3166 1345 Maintenance Agency and ISO 3166 current list of two-letter country 1346 codes is available via: 1348 http://www.iso.ch/infoe/agency/3166-1.htm 1350 Appendix D: Acronyms 1352 ANS Advanced Network Services, Inc. 1353 ASN Autonomous System Number 1354 APNIC Asia Pacific Network Information Center 1355 ARIN American Registry for Internet Numbers 1356 AS Autonomous System 1357 CANET Canada Net 1358 CIDR Classless Inter-Domain Routing 1359 DNS Domain Name System 1360 gTLD Generic Top-Level Domain 1361 IANA Internet Assigned Numbers Authority 1362 InterNIC Internet Network Information Center 1363 IP Internet Protocol 1364 IR Internet Registry 1365 IRR Internet Routing Registry 1366 ISO International Organization for Standardization 1367 ISP Internet Service Provider 1368 LINX London Internet Exchange 1369 NCC Network Coordination Centre 1370 NIC Network Information Center 1371 NSRC Network Startup Resource Center 1372 POP Point of Presence 1373 RADB Routing Arbiter Data Base 1374 RFC Request for Comments 1375 RIPE Reseaux IP Europ�ens 1376 TCP/IP Transmission Control Protocol/Internet Protocol 1377 TLD Top-Level Domain 1379 draft-wenzel-nsrc-04.txt 1380 expires 11/01/00