Washington DC NAP Attachment Policy 1. Introduction The NSF has defined NAPs (Network Access Points) as high speed Level 2 interconnection points at which Network Service Providers (NSPs) may establish peering relationships for exchange of IP traffic. It is the expectation of the NSF, that Network Service Providers connected to the NAPs operate at 1.54 Mbps or more, be able to switch IP packets, and implement BGP or IDRP based procedures to interwork with the Routing Arbiter and other Service Providers. In accordance with the requirements of the NSF, Here are NAP attachment policies for the NSF sponsored Network Access Point in Washington DC, operated by MFS Datanet Inc. 2. Participation Any Network Service Provider (1) may connect to the Washington NAP at a minimum speed of 1.54 Mbps. Use of the Routing Registry and Route Server maintained and supported by Merit at the NAP is recommended but not mandated. It is the responsibility of the connecting NSPs to establish bi- lateral or multi-lateral agreements with other service providers on the NAP in order to interexchange traffic. Such agreements may include agreements to default routing. They may include exchange of traffic without settlements. While it is desirable for the interconnectivity of the Internet, that all participants exchange traffic, this is not a requirement of connection to the Washington NAP. 3. Policy Issues The purpose of administrative policy regarding NAP attachment is to maximize quality of service and to facilitate support. Key issues here include introduction of additional NAP participants, problem resolution, capacity management and new technology introduction. 3.1 Introduction of additional NAP participants. The Washington NAP is constructed around a high performance ATM backbone switch with access ports fully meshed via ATM PVCs. This is consistent with the Level 2 service definitions by NSF. It is the responsibility of NSPs connecting to the NAP to make interworking agreements with other participants, and then implement those agreements through establishment of routing policies in their NAP connected routers. In order to facilitate establishment of those interworking agreements, a mailing list will be established and maintained by MFS Datanet. All NAP connected NSPs are required to provide an administrative contact name to that list. This contact should be authorized to discuss interconnect arrangements with new or prospective NAP connected NSPs. MFS Datanet will install new NAP connections as requested by NSPs. No prior authorization by existing participants is required for this installation to occur. Installation involves connection of NSP equipment and establishment of ATM VCI's between the NSP port on the NAP ATM switch and other NAP ATM ports. However without interworking arrangements with one or more of the existing participants, this connection will be dysfunctional. It is the responsibility of the new NSP to make routing arrangements with the other participants, and the responsibility of the involved participants to implement agreed routing policies between themselves in order to make that new connection viable. 3.2 Problem Resolution. Trouble calls from NAP attached networks may reflect a number of problem scenarios. the NAP manager is responsible for assuring the appropriate functioning of NAP service elements, the RA for appropriate functioning of Routing Services, the attached NSP for appropriate functioning of their equipment. Close cooperative activity between all of these organizations will be essential to offering high quality service. To facilitate that objective, attachment to the Washington NAP requires that the attaching network provides MFS Datanet with their Network control contacts, hours of service, technical and routing policy contacts, and schedule for on- call support availability. Escalation procedures are requested. Use of the Route Registry, while not required, is strongly recommended. NAP attached NSPs agree to support, on a best effort basis, network operations problem resolution support in cooperation with other connected networks, the Routing Arbiter and the NAP Manager. MFS Datanet maintains and operates a 7 day/24 hour Network Operations and Control Center in San Jose CA, with backup in Oakbrook Terrace IL. This NOC will utilize the contact, escalation and support information provided by connected NSPs to address problem reports. An automated trouble ticket system with e-mail contact lists will be used to maintain coordinated visibility into problems until such time as they are resolved. 3.3 Capacity Management. Networks subscribing to NAP services purchase connections meeting their capacity needs. The NAP manager is responsible for assuring that the capacity of the NAP itself (switch fabric, adaptation equipment and transmission systems) is adequate to service all traffic transiting the NAP. This Capacity planning and engineering requires periodic data collection on traffic volume. In addition, metrics for NAP effectiveness must be reported to the NSF. 3.3.1 Statistics Reporting to the NSF MFS Datanet will collect and report to the NSF, the aggregate volume of transit ATM cells crossing the NAP switching fabric. This aggregate NAP transit cell report will NOT be differentiated by point to point ingress / egress pairs, nor will it include IP addresses. 3.3.2 Additional Statistics. MFS Datanet will collect additional statistical traffic data including point to point (per VCI/PVC) peak average and errored ATM Cell counts entering and existing the NAP switch fabric. This data will be used by MFS exclusively for network engineering purposes. The data collected will be provided (for their connection only) to an NSP on request to assist the NSP in capacity planning of their NAP connections. This data will not be released to any third party without specific authorization of the NSP. No other traffic analysis activities are planned nor will be performed without the prior explicit advise and consent of NAP connected networks. 3.4 New Technology Introduction New protocols are under development that will affect the NAP and attached Network Service providers. New technology will continue to be introduced in all components of the network. Frequent communication between service providers regarding upcoming or desirable technology changes will greatly facilitate smooth introduction of new capabilities into the NAP architecture. MFS Datanet encourages and supports cooperative certification / interoperability testing programs with NAP attached service providers. NSPs connected to the NAP are requested to notify the MFS Datanet NOC in advance of any testing or new product deployment activities which may impact service on the NAP. 3.5 Acceptable Use Use of NAP facilities for any illegal activities is prohibited. Illegal activities include tampering with computer hardware or software, unauthorized entry into computers, or knowledgeable vandalism or destruction of computer files. They also include eavesdropping or wiretaping of data transiting the NAP unless an appropriate legal court order is in force. It is the responsibility of NAP attached networks to ensure that their use of NAP facilities is appropriate, and conducive to maintenance of a high quality of service and high availability of NAP facilities for all participants on the NAP. NSPs considering development of their own acceptable use policies may wish to reference the draft-ietf-isn-aup-01.txt of 9/94 developed by B. Manning and D. Perkins. 4. Technical Attachment Options 4.1 Access protocols supported. Access protocols for connection to the Washington NAP include Ethernet, FDDI and ATM. 4.2 Attachment Options. There are three geographically defined attachment options to the Washington NAP for NSP connections. Attachment options include local and national "on-net" attachment, and "off-net" attachment. 4.2.1 Metro On-Net. This connection options applies to NSPs located in buildings served by MFS fiber plant in the greater Washington DC, Maryland and Northern Virginia Metropolitan area. For these NSPs, the demarcation point is located in their building, in MFS provided CPE equipment located either at their premises or in MFS conditioned secure leased facilities in their building. The NSP interface to the NAP is the standard, commonly used and available physical connector applicable to the selected protocol option (e.g. AUI, 10BASET, or MIC for LAN protocols). Metro On-Net pricing includes protected diverse local access from the NSP's building, dedicated, distance insensitive local access bandwidth, service and maintenance of all equipment on the NAP side of the demarcation point (LAN interface). 4.2.2 National On-Net. This attachment option applies to NSPs located in buildings served by MFS fiber in any other metropolitan area served by MFS Datanet. For these NSPs, the demarcation point is located in their building, in MFS provided CPE equipment located either at their premises or in MFS conditioned secure leased facilities in their building. The NSP interface to the NAP is the standard, commonly used and available physical connector applicable to the selected protocol option (e.g. AUI, 10BASET, or MIC for LAN protocols). National On-Net pricing includes protected diverse local access from the NSP's building to the MFS node site (Central office), dedicated, distance insensitive local access bandwidth, inter-city connectivity across MFS Datanet's diversely routed all fiber DS3 ATM network, service and maintenance of all equipment on the MFS side of the demarcation point e.g. the LAN interface in the NSP's building. 4.2.3 Off-net locations IXC and LEC central office facilities are connected to MFS networks with multiple (diverse) building connections. For those NSPs whose buildings are not yet served directly by MFS fiber, MFS Datanet orders circuits from the appropriate carrier, installs CPE equipment at the customer premises, and again provides a single demarcation point at the LAN connector to the NSP's router. Off net prices include CPE equipment (bridge and DSU/CSU), circuits from IXC or LEC, metro bandwidth from MFS at the Washington NAP, service and maintenance of all equipment on the NAP side of the demarcation point (LAN interface). 4.2.4 Collocation Options. Collocation facilities are available in all MFS cities including Washington. NSPs may choose to collocate their routers with the Washington NAP. The service and maintenance demarcation for the NAP is the LAN interface cable from the NSP router to the NAP. NSPs may choose to utilize collocation space to estabhlish their service hubs, terminating leased lines and dial-up circuits in rack space provided by MFS. MFS Datanet services may be used to bring NSP's customers to their MFS collocated routers. 5. Security 5.1 Datanet facilities MFS Datanet's focus of activity with regard to NAP security is to protect NAP switches and routers, physical plant, transmission systems, network operations and control systems and information, and to maintain the confidentiality of our own and our customer's data. MFS city networks are constructed as self healing fiber optic rings using fully redundant transport electronics providing diverse paths between customer buildings. Transmission equipment is contained in physically secured and conditioned facilities equipped with HALON, and UPS power backup. Two geographically diverse Network Operations and control centers are staffed 24 hours/day, 365 days per year. In addition to providing backup operation and control services, these facilities provide critical off-site disaster recovery storage of network management and operations data. 5.2 Access procedures for NSPs using collocation services. There are defined procedures and conditions under which customers who contract to collocate their equipment in our facilities may access this equipment. These conditions provide for access availability in non- emergency cases, where major service outage, personal injury or property damage is occurring or reasonably appears to be imminent, customers may obtain access at any time (24 hours per day, 7 days per week) on one hour notice or such other notice as may be responsible under the circumstances. Customers accessing our terminal facilities must be escorted by MFS personnel, and this access is subject to the customers adherence to the security rules and rules of conduct established by and for the facility. The purpose of these access procedures is two fold. First, they are necessary to assure the security and availability of MFS transmission and data communications services. Second, they are necessary to assure the safety of customer personnel. 5.3 Privacy and confidentiality. Every MFS employee signs a statement of understanding agreeing to hold in confidence information of a confidential, proprietary or trade secret nature relating to the business of the company, or any customer, supplier or vendor. 6. Pricing Contact MFS Datanet sales for both NAP and extension cord pricing. 7. Availability The Washington NAP is available for Beta trial testing effective Monday July 18, 1994. 8. Contact Information Sales: John Hardie Network Communications Consultant MFS Datanet, Inc. 8100 Boone Blvd., Suite 500 Vienna, VA 22182 phone: 703/506-2071 fax: 703/847-9426 hardie.john@mfsdatanet.com Principal Investigator: Steve Feldman Scientist MFS Datanet Inc. 55 South Market St., Suite 1250 San Jose CA 95113 phone: 408/975-2230 fax: 408/975-2210 feldman@mfsdatanet.com (1) For the purposes of NAP connection, an NSP is defined as any person, firm or corporation legally organized to provide TCP/IP or OSI internetworking data communications services to the public on one or more geographic areas. ------------------------------------------------------------------------- Washington DC NAP Pricing Monthly charges for connections to the Washington DC NAP depend on the connection type and length of commitment. In addition, there is a non-recurring initial setup fee of $1000 for all connections. Connection Connection 1 Year 3 Year 5 year Type Rate Commitment Commitment Commitment ========== ========== ========== ========== ========== Fractional 1.544 Mbps $1,680/mo $1,520/mo $1,400/mo Ethernet Native 10 Mbps $2,280/mo $2,050/mo $1,900/mo Ethernet Fractional 45 Mbps $4,080/mo $3,650/mo $3,400/mo FDDI Native 100 Mbps $8,400/mo $7,560/mo $7,000/mo FDDI DS3 ATM 45 Mbps $4,500/mo $4,050/mo $3,825/mo OC3c ATM 155 Mbps $7,500/mo $6,750/mo $6,375/mo In accordance with the requirements of the NSF, MFS Datanet is publishing these prices for connections to the Washington DC NAP. These prices do not necessarily apply to any other MFS Datanet services. -------------------------------------------------------------------------