Commercial Connect , LLC.


September 30, 2000






1418 South Third Street

Louisville, KY  40208-2117

(502) 635-7979 – (502) 636-9157



Jeffrey S. Smith, President




















1.0 Introduction_ 4

1.1 Positioning for the Future 6

1.2 Design Overview_ 8

2.0 Network Architecture 11

3.0 Network Cabling Infrastructure 13

3.1 Local Distribution Design and Installation_ 14

3.2 Fiber Optic Backbone Design and Installation_ 19

3.3 Other Network Cabling Infrastructure Specifications 25

4.0 Network Hardware 27

4.1 Network Switch/Concentrator Selection Criteria_ 27

4.2 3Com SuperStack II 3300 Concentrators/Switches 30

4.3 Cisco 3600 Routers 33

4.4 IBM Servers 36

4.4.1 RS/6000 Model F80_ 36

4.4.2 IBM Netfinity 7600_ 38

4.5 Hardware Configuration Summary 40

5.0 Wide Area Network Connectivity 40

5.1 User Site Models 41

5.2 Corporate Backbone WAN_ 43

5.3 Remote Offices 46

5.4 Remote Communication Server 46

5.5 Individual/Home Remote Access 47

6.0 Network Management 48

6.1 Distributed Network Management 48

6.2 Enterprise Applications Management System_ 49

6.3 Facility Network Management System_ 50

6.4 Network Server Management 52

7.0 Network Host and Server Integration_ 52

7.1 Microsoft Windows 2000 Advanced Server and Oracle Database Application Integration  53

7.2 Netware Server Integration_ 55

8.0 Enterprise Applications:  Corporate Electronic Mail and Scheduling_ 56

9.0 Project Implementation_ 58

9.1 Project Management 58

9.1.1 Certification Testing_ 59

9.1.2 Documentation_ 61

Appendix A Hardware Configuration_ 68

Appendix B  CORE BCP-1_ 73


Commercial Connect, LLC.

Technical Capabilities and Plan



1.0 Introduction


D15.1 Detailed description of the registry operator’s capabilities.


Commercial Connect, LLC. has the full resources of an Internet Service, an accredited ICANN Registrar, and a full service computer consulting firm located at the same location and all are co-owned by one of the principals of Commercial Connect, LLC..  In addition, Commercial Connect, LLC. can pull resources from the other principal’s resources, Simon Properties with their full time staff of thirty five permanent IS employees and an additional sixty contract IS employees. 


Currently Commercial Connect, LLC. is connected to a redundant ATM network through a Sprint backbone, then to the MerchantWired extranet utilizing its DS3 connections to Intermedia.  With Simon Property Group’s extensive real estate all over the world, we will also be co-locating equipment strategically placed around the globe to ensure reliability and efficient accessibility.


MerchantWired, a majority owned entity of Simon Property Group is in the process of wiring every mall property of Simon Property Group for Internet and e-commerce.  Commercial Connect, LLC. has commitments from MerchantWired and from Simon Properties to establish co-locations around the world.


Press Release – Indianapolis, IN – May 9, 2000


Media Contact

Adam Castellani

Alexander Oglivy Public Relations Worldwide

(404) 881-2329

MerchantWired goes live with first Coast-to-Coast retail infrastructure network

Consortium of the Nation’s Largest mall Owners Creates Retail Extranet Standard

MerchantWired Partners with Cisco Systems, IBM and Intermedia Communications to Establish the Infrastructure Standard

MerchantWired (, a full-service infrastructure that connects the physical and virtual worlds in the retail industry, announced the launch of its nationwide service.  Leading a consortium of property owners and infrastructure partners, MerchantWired will change the retailers communicate with each other and their customers.  Dedicated to establishing the standard for retail networks, MerchantWired provides retailers in any property across the country with the infrastructure to met their specific needs.  Through strategic partnerships with Cisco Sysems, Inc., IBM and Intermedia Communications, MerchantWired works with leading property owners including the Macerich Company (NYSE: MAC), The Rose Company (NYSE: RSE), Simon Property Group (NYSE: SPG), Taubman Centers, Inc. (NYSE: TCO), Urban Shopping Centers, Inc. (NYSE: URB) and Westfield America, Inc. (NYSE: WEA) to wire over 380 retail properties nationwide…”


At present there are ten employees employed by Computer Analytical Systems, Inc. dba hereinafter referred to as  These employees possess the technical capabilities to create and provide consultation services to companies starting an Internet Service Provider, an Internet Registrar service and/or e-commerce solutions.  This experience includes Information Systems Planning, Management/Cost Analysis Consulting, Systems Analysis, Procedural Analysis, Systems Implementation and Operations Management as well as Database Engineering and Design.  In addition to the above abilities, they possess the technical expertise of planning world-wide networking including Virtual Private Networking and integrating telecommunications and data using technologies such as Voice over IP.


The above combined with Simon Property Group’s, hereinafter referred to as Simon, information systems department of over eighty employees is a solid foundation to build a new joint company which will take key personnel from the companies as its employees. through a newly formed corporation in 1996, incorporated in 1997, (CASDNS, Inc.) was the second entity to begin registering  .com .net and .org in competition with Network Solutions during the initial testbed period through CORE.  This makes us one of the oldest functioning registrars in business with the exception of Network Solutions.  We were included in the initial approval process of CORE and later one of the first accredited by ICANN.


The President and CEO of and CASDNS, Inc., has been involved in these same group of companies for the past twelve (12) years.  During that time he has been involved in consulting for major organizations including AT&T, National  Medical Enterprises, Humana, Various State Transportation Cabinets, Bahamas Telco, CORE, Catholic Health Initiatives  and University of Kentucky.  Consulting services include data/telecommunications integration, Database design and strategies, Wide-Area Networking, E-Commerce implementations and strategies, and Internet Service Provider Startups.


D15.2  Technical plan for the proposed registry operations.


D15.2.1  General Description of proposed facilities and systems

Commercial Connect, LLC. will use eleven scalable IBM Servers located in Louisville, KY,  Atlanta, GA, Chicago, IL, Indianapolis, IN,  Dallas, TX,  and London, UK.  The primary site will be 1418 South Third Street, Louisville, Kentucky where a redundant ATM fiber Sprint link is located.  The primary registry database server in Louisville will be an IBM RS/6000 F80 450mhz  with 4gb RAM and 36.4gb hard disk storage.  The additional servers will be IBM Netfinity 7600 Xeon/700 with 2gb RAM and 18.2gb storage Of these, two each will be located in Louisville, Atlanta and Chicago to function as replica  database servers and name servers respectively, and one each in Indianapolis, Dallas and London to function as name servers.   They will be configured to automatically transfer and keep current vital information and serve geographical locations based on backbone configurations.


The primary site at 1418 South Third Street has a redundant ATM Fiber sprint backbones with controlled facilities including complete customizable climate control, video surveillance, controlled access with active heat and smoke sensoring alarm system.  It is manned twenty-four hour a day with multiple technicians living within the same block of the company. 


The server computers will utilize a Compaq 15 Tape DLT Array Backup System.


The database will be an Oracle based custom programmed system to be discussed later in this document.


D15.2.2  Registry-Registrar model and protocol


The Registry-Registrar model will abide by the protocol requirements outlined in the IETF Internet specification for gRRP and will follow Section 10 of RFC2026.


It is essential that in order to maintain an orderly reliable Internet standards must be in place to provide basic services.  We fully intend to adhere to these standards.  We will provide a similar functioning Registry-Registrar Model that will respond identical to the requests that are in place at Network Solutions/Verisign Registry Services.  We will diverge slightly as we are proposing a heavier registry model with additional information in order to aid in the stability of the internet.  Our model will keep aside from the current information, additional vital information needed to provide for any lapse in business activity of registrars.  There will be a need to enhance the RRP for additional commands and information.  All needs will be addressed through IETF and an enhance form of the RRP.


Full observation and participation in IETF processes are essential.  Commercial Connect, LLC. will have staff dedicated to keep up with all RFC’s, proposals and standards to ensure that we are consistent to the operation and fast changing need of a stable Internet.  In addition security will be of highest priority.  All transactions will take place on secured servers transmitting secured transmissions, virtual private networking and secured DNS to ensure a secure Internet system.


1.1 Positioning for the Future


A strategic vision that recognizes a need to adapt the information architecture to meet the challenges and goals of the future is essential.  The direction of today’s Internet environment is rapidly changing to incorporate new ideas and relationships among the registries, registrars, Internet service provides and finally the end user.  One of the keys to the ability of Commercial Connect, LLC. to take advantage of this environment is to develop and implement a strategic information plan that is capable of supporting both the current and long term business goals of the internet.

In today's information world, the enterprise network is the infrastructure over which all applications and platforms operate. Because of its importance, the planning and implementation of the network must be approached with a broad perspective. This requires that all aspects of the use and requirements of the network be carefully considered before actually installing hardware and software.

Today's information environment offers many challenges. One of the major challenges lies in the determination of the types of applications that may be selected for use in the institution in the future. As various applications offer their own unique requirements, the information system must anticipate, and have some provisions for, multiple applications that may be used on the system. The varying demands of these applications dictate that the strategic plan be based on open systems, standards based architectures, capable of supporting not only these applications, but of evolving to new technologies to meet the demands of tomorrow's applications.

Another issue impacting the information environment is the increased complexity of systems (hardware, software, and communications). Unfortunately, as system complexity increases, IS staffing is not keeping pace. In order to offset this difference, newer, more efficient methods of maintaining and managing the systems must be incorporated into the plan.  In addition to the basic management requirements of the system, the training of the current IS staff is paramount in enhancing their ability to evolve into the newer networked environment.

Faced with the possibility of new government regulations, increased competition, and the need to maintain a healthy bottom line, administrators are looking at many new and different ways to meet these challenges. One method of leveraging the influence is to enter into new group relationships with other members of the internet and computer systems community. The strategic plan must incorporate the ability to extend beyond the traditional corporate campus to reach these remotely connected entities.

Other complex issues also must be addressed in the strategic plan, such as system security, user interfaces, the incorporation of existing systems, and long term growth.

While all of these changes are occurring at a rapid rate, the changes in communications technology are happening at a rate that may be even faster. In order to meet the needs and challenges, the strategic plan must also anticipate the changes in communications technology.  By understanding and incorporating the most current technology into the plan, Commercial Connect, LLC. will be able to take advantage of the benefits that newer technologies offer.

By having entities such as Computer Analytical Systems, Inc., (CASDNS, Inc.), Simon Property Group, CAS-Com Internet Services, Inc. and MerchantWired as partners in developing and implementing the network solutions necessary to achieve the long range vision, Commercial Connect, LLC. will be well prepared to deal with the revolutionary changes facing information systems today. Commercial Connect, LLC. will create an environment that addresses the full scope of networking requirements in today's environment.

The following must be performed:

·        Define and install a campus network infrastructure that meets both the
immediate and long term needs.

·        Provide and install network hardware that is capable of supporting
both current and future technologies.

·        Plan network software and workstation configuration to support
multiple environments that are currently implemented or may be
implemented in the future.

·        Develop a migration path so that "fork lift" changes are not necessary
in the future only what's cost effective now with a plan to incorporate
the remainder later.

·        Develop and implement a network management plan that aids the staff in identifying and correcting problems.

·        Develop a wide area networking plan that is capable of supporting various user types (i.e. Registrars, Resellers, ISP’s, and end users, etc.).

Upon completion of the network, users attached anywhere in the system will have access to any resource in an open, shared but secured environment. This powerful feature is the primary basis for open systems architecture used in networking today.

1.2 Design Overview


The design is composed of three major parts:

The network design provides the infrastructure necessary to install and implement an enterprise network. The design includes solutions for a number of functional areas:

·        Network Architecture

·        Network Cabling Infrastructure

·        Network Hardware

·        Wide Area Network Connectivity

·        Network Management

·        Host and Server Integration

·        Enterprise Applications

The solution for each of these functional areas is discussed in corporate-wide terms in the section of the same name. Following the solutions discussion, the Detailed Design portion of this document provides the specific infrastructure design details necessary to implement the project. The Project Costs section includes a detailed Bill of Materials and costs for implementing the network. The following paragraphs provide an overview of the functional area solutions.

The Network Architecture section provides a foundation for the follow-on sections. It defines the three network infrastructure components (fiber optic backbone, local distribution, and wide area connectivity) discussed in this design and provides a graphical illustration of how these three components combine to form the Enterprise Network. It also describes the logical connectivity of the network hardware as a preface to the discussion in the Network Hardware section.

The next section of the design is the Network Cabling Infrastructure. The proposed solution is based on a hierarchical star wiring topology which is capable of supporting existing and future networking technologies. The solution proposed is compliant with the EIA/TIA 568 standards for structured building wiring. This guarantees that the network infrastructure will fully meet the current and long term information needs. The baseline design provides for the following:

·        Engineering design to ensure that the infrastructure fully meets the
EIA/TIA 568 structured building wiring requirements.

·        Labor and materials to install enhanced Category 5 outlets in locations
throughout the facility.

·        Labor and materials to install a fiber optic backbone to serve all
locations in the buildings.

·        Equipment racks, patch panels, device jumper cables, and other
components necessary to fully implement the cabling infrastructure.

·        CADD drafted maps indicating fiber optic cable routing, network
concentrator locations, device locations, and wire numbers.

·        Complete testing of each system component to ensure operability
within the designed standards.

The Network Hardware portion of the design offers a solution from 3Com as the recommended network concentrator manufacturer. We have based our selection on several factors which are explained in detail later in this design. The network design provides for the following:

·        Concentrator chassis and modules that are capable of supporting Ethernet, Token Ring, or FDDI.

·        Ethernet 100BaseTconnectivity for PC workstations and network attached printers.

·        Network management modules for configuration and control of all network host modules.

·        Network integration support to install, configure, and test the hardware and software components proposed.

·        Component testing to guarantee complete operation of all system ports, power supplies, and fault tolerant features offered.

The Wide Area Network section describes the solution for connectivity and remote connectivity to the Shared Registry System (SRS) server. The WAN connectivity discussion is divided into three functional areas:

·        The Corporate Backbone WAN section describes network connections between the major sites and to the SRS. A union of redundant T-1 circuits and the MerchantWired DS3 network product provides a flexible approach to intersite data and voice connectivity. This design specifies Cisco Systems routers as a backbone network hardware solution. Through the use of Coastcom T-1 channel banks, the design provides a capability to support voice as well as data connections between the major sites.

·        The Remote Branch Office section implements redundant T-1 circuits between the branch office and the corporate backbone site.

·        The Remote Access capability described in the final section of the WAN discussion provides both remote control and remote node access to those administrators who require periodic access to all network functionality.

This design provides all of the network hardware, software, and network integration effort to implement Wide Area Network connectivity. Leased circuit fees and facility cable access costs are addressed in the accompanying Financial Plan.

In the Network Management section, we propose two levels of network management functionality: Enterprise-wide and Facility Management.

·        The Enterprise Network Management solution provides a platform and application software functionality with the power to configure, monitor, and troubleshoot any network concentrator or router throughout the network. This solution is designed to facilitate centralized day-to-day management and monitoring of the network.

·        The Facility Management capability provides a scaled-down capability for local network configuration and complete desktop management functionality within the facility. The facility management package permits the local network administrator to perform complete configuration of network concentrators (such as port assignments) and management of user applications, workstation configuration, and applications metering on network servers.

The Network Host and Server Integration section provides solutions for each of the network hosts and servers defined in the near-term IS applications plan.

·        SRS applications will be accessed either through a secured Https connection or through RRP.

·        The majority of the SRS application will be consolidated onto one at the Louisville, Kentucky host location then replicated on two additional servers across the country.

The Enterprise Applications section of the design outlines a solution utilizing Microsoft’s Exchange Server for Electronic Mail, Scheduling, and Task Management. Each workstation user on the network will have access to these applications. The design specifies active server directory architecture for effectively implementing these applications corporate wide.

2.0 Network Architecture

This paragraph begins our discussion of a networking platform designed to support complete integration of applications and data communications requirements. Our goal - to build a networking environment that provides users access to distributed computing resources from a single desktop platform, while at the same time making network complexities transparent to them.

The enterprise network infrastructure can be viewed as having three components:

·        A local distribution network providing connectivity from the user to the network,

·        A backbone network interconnecting segments of the local distribution networks throughout a facility, and

·        Wide Area Network (WAN) connectivity between the main sites and to remote locations.

Layering the network in this manner permits more effective use of technology designed to support communications at each level. It also provides a structured approach for simplified network management.

The use of standard protocols and interfaces permits seamless integration of the components. Ethernet (IEEE 802.3 standard) was selected as the primary media access protocol throughout the network. Although the network will be implemented using Ethernet, the structured technique can also support FDDI, Token Ring, and ATM protocols.

The following paragraphs provide the details of each of these components. The Logical Network Design figure illustrates how these components are brought together to form the network.

The function of the local distribution network is to connect users on a floor or within a department to network concentrators, or hubs. The hubs provide communications between users and local servers as well as access to the backbone network in the facility. The local distribution network is a physical star topology using unshielded twisted pair (UTP) cabling. The combination of these two approaches yields cost effective connection to the desktop while maintaining flexibility and simplified troubleshooting.

The fiber optic backbone network interconnects departmental concentrators with each other and the network computing resources within a facility. It also provides access between buildings on the campus. The fiber optic backbone design is a star topology, originating from a Main Distribution Facility (MDF) in each of the three main sites. From the MDF, fiber optic cables radiate out to Intermediate Distribution Facilities (IDFs) which serve as the hubs of segments of the local distribution network. The Structured Wiring Diagram depicts the tiered architecture implemented in this design.

The wide area network (WAN) provides connectivity between enterprise/facility networks over extended distances using commercial carrier provided services. In the initial implementation of the enterprise network, the inter-site links will consist of full period digital links between the three main sites; the network hardware specified in this design will support voice and video as well as data traffic between the sites. (In some cases additional modules are required).

The logical architecture of the network components implements an approach known as the "Collapsed Backbone" on each campus. In this approach, the physical star arrangement of the fiber optic backbone connects intelligent wiring hubs located throughout the facility to a central intelligent hub. The backplane of the central hub serves as the network's physical focal point, interconnecting network segments to the switches and routers that segment and distribute the network traffic. The collapsed backbone design offers several advantages:

·        Improved performance over other backbone designs. Implementation of today's high-speed router and switch technology in conjunction with the central hub will eliminate network bottlenecks that plague other architectures.

·        Simplified network management. From the central hub, protocol analyzers can diagnose problems throughout the enterprise network without the need for access to each of the hub communications closets.

·        Easy access to WAN links through the central router. This architecture minimizes the complexity of integrating WAN links into the enterprise network.

The use of a switch or router for network segmentation on each campus network will vary depending on the size of the campus internetworking requirements. At a site with a large number of departmental concentrators and users, an ethernet switch is used for cost effective network segmentation. At a site such as this, a backbone router provides WAN access and network layer protocol segmentation.

For sites with a smaller number of segments and hosts, sufficient ports are available on the backbone router for complete network connectivity.

The Collapsed Backbone Architecture figure portrays this concept.

3.0 Network Cabling Infrastructure

This section describes the network cabling infrastructure design and installation as it is implemented across the enterprise network. The specifics of the cable infrastructure at each campus are described in the Network Design Details section.

This section provides information on the fiber optic backbone and the Enhanced Category 5 distribution system proposed which entails the following:

·        A local distribution network extending from each IDF to user device locations. The local distribution network will support a large variety of devices, including any combination of user PC workstations, terminals, and printers. The design utilizes Enhanced Category 5 Unshielded Twisted Pair (UTP) cabling, providing high-quality, reliable data communications for today's networking technologies. In addition, use of this type of system positions the company for a smooth transition to the technologies of tomorrow.

·        A fiber optic backbone cable plant extending from Main Distribution Facilities (MDFs) to Intermediate Distribution Facilities (IDFs) located throughout the building. This cable plant is designed in accordance with the EIA/TIA 568 and 569 standards for structured building wiring. In addition, the fiber optic infrastructure design is completely compliant with IEEE 802.3 Ethernet, IEEE 802.5 Token Ring, and ANSI X3T9.5 FDDI specifications.


Upon completion of the project proposed CommerConnect will be able to utilize the network for communications between all data devices throughout each campus and the host processors or servers. The network infrastructure designed and constructed will be capable of supporting any current or projected technology such as Ethernet, Token Ring, FDDI, ATM, Fast Ethernet, or Fiber Channel, to name a few.

Our engineering, installation, and technical staffs have extensive experience in mixed media networking, and an intimate knowledge of the unique requirements of large Internet and corporate institutions.


3.1 Local Distribution Design and Installation



The IDFs are the hubs of each segment of the local distribution network. Each local distribution cable terminates on an Enhanced Category 5 modular patch panel mounted in the equipment cabinets or racks. This design provides a flexible, easily managed capability for patching data network circuits from the hubs and terminal servers using modular patch cords.

Telecommunications closets are intermediate distribution points for the local distribution network. In the event that a number of UTP cables are required on a building floor not supported by an IDF, telecommunications closets are established to serve as cross connect points between the vertical UTP cabling (risers) and the horizontal distribution cabling on the floor.

This architecture provides flexibility for future adds, moves, and changes, eliminating the need to re-run distribution cabling the entire path from the user location to the IDF, which may be several floors above or below. Only the horizontal portion of the cabling will be rerun and cross-connected to the existing vertical cable run. The cross connect hardware will be AT&T 110 style cross connect blocks, mounted on a plywood backboard.

This proposal specifies 4 pair, 24 AWG, Plenum Grade cable, permitting overhead cable runs to user locations to be concealed in the plenum ceilings without additional conduit. All distribution termination hardware is rated at Enhanced Category 5 in accordance with EIA TSB-40. Terminations will utilize the EIA/TIA 568B pin-out standard to ensure compliance with IEEE lOBaseT, IEEE Token Ring, and ANSI X3T9.5 TP/PMD standards.

The installation specification paragraph below specifies the installation methods and requirements to maintain the structural integrity of the system. This will include the cable management hardware for supporting the cable in the ceilings, installation, and termination methods and requirements for properly installing a Enhanced Category 5 system. This data can be used for future moves, additions, or changes that will be encountered in the future.

Jumper cables from the wall plate to the user device are specified to be 4 pair, stranded, UTP, terminated with male RJ-45 connectors at both ends. The terminations will follow the EIA/TIA 568B pin-out standard. The standard length for these device cables for purposes of this proposal is ten feet, although customized lengths can be substituted with minimal incremental cost.


This section covers the material specifications for horizontal distribution cabling to be run from the IDF wiring closet locations to the user outlet locations as shown on the associated plans and drawings.

All horizontal distribution cabling and hardware shall be verified UL Level V (EIA/TIA Enhanced Category 5) compliant materials, produced by a manufacturer that has had the Level V product tested by Underwriter's Laboratories.

Horizontal Distribution Data Cable:

·        All horizontal distribution cables shall be Enhanced Category 5, plenum rated, 4 pair, unshielded twisted pair. This cable is rated at over 100 Mb/s operation in conformance with ANSI X3T9.5 FDDI TP/PMD specifications. Additionally, the ATM Forum has stated that Enhanced Category 5 compliant cables will be specified for 155 Mb/s ATM operation. The following electrical specifications are provided as a reference for the horizontal UTP cabling.

·        All UTP cabling must conform to the specifications detailed in the EIA/TIA 568 and EIA/TIA TSB36 standards documents for structured wiring systems.

Outlet Termination Hardware:

All outlet termination hardware is compliant with EIA/TIA TSB40 specifications for Enhanced Category 5 hardware. All outlet jacks are Hubbell modular data jacks.

·        The modular jack meets or exceeds all requirements set forth in the EIA/TIA 568 Telecommunications Outlet Connector Specification.

·        The modular jack meets or exceeds all requirements set forth in the EIA/TIA TSB40 Telecommunications Systems Bulletin - Additional Specifications for Unshielded Twisted Pair Connection Hardware.

·        The modular jacks have an insulation resistance of 500 Mohms maximum.

·        All Near End Crosstalk (NEXT) and Attenuation exceed the EIA/TIA requirements set forth in the TSB40 specifications.

·        The modular jacks employ an insulation displacement termination method which accepts 22 or 24 gauge AWG solid conductor wire.

·        The modular jacks use SO micro-inches of lubricated gold plating over 100 micro-inches nickel plating for superior connectivity or the jack pins.

·        The modular jacks are wired to meet EIA 568B specifications.

Outlet Face Plates:

Single and Duplex outlet face plates specified for use are manufactured to support the modular jacks specified above.

Patch Panels:

Patch panels specified for use are Hubbell Enhanced Category 5 110 Patch Panels which are fully compliant with EIA/TIA 568 and TSB40 specifications.

·        All jacks panels are 19" rack mountable for use in the IDF locations.

·        The 24 port jack panel is the Hubbell MCC58031 10A19, which is 1.75" High.

·        The 48 port jack panel is the Hubbell MCC58061 10A19, which is 3.50" High.

·        The 96 port jack panel is the Hubbell MCC58121 10A19, which is 7.00" High.

Patch Cables:

In order to maintain 100 Mb/s operation, the patch cords specified for use for workstation connectivity will be tested per TIA SP2840 draft standards.

The user patch cords will provide RJ45 - RJ 45 style connectivity to interface the outlet jacks to the workstation NIC's and adapters.



This section covers the installation specifications for horizontal distribution cabling to be run from the IDF wiring closet locations to the user outlet locations as shown on the associated plans and drawings.

Cable Installation:

All station cabling will be installed in a neat and workman like manner and in accordance with manufacturer's specifications with respect to maximum pulling tension and bending radius.

The project manager will determine the cable path for each distribution cable based on a thorough survey of the facility. All station cabling shall be run in a star fashion from the 1DF / Telecommunications closet location to the user outlet location. Cable runs will be routed in the most direct manner possible so as not to exceed the total cable distance limitations of 90 meters maximum.

All installed UTP cables will be supported in the ceilings using steel cable management rings placed at regular intervals to maintain the cabling in a neat and organized manner.

When installing high speed LAN cabling, care will be taken to avoid high energy electrical sources that may interfere with data transmission. Some sources to avoid are as follows:

·        Fluorescent Light Fixtures (no closer than 6")

·        Motor Generators (no closer than 36")

·        Electrical Transformers (no closer than 24")

·        MRI Equipment (no closer than 12')

The following table provides minimum separation distances between cable runs and power wiring of 480 volts or less.

Separation of Telecommunications Pathways from 480V Power Lines

Minimum Separation Distance
<2 WA 2-5 WA >5 WA

Unshielded power lines or electrical  - 127 mm 305 mm 610 mm
equipment in proximity to open or  - (5 in)
(12 in) (24 in)
nonmetal pathways.

Unshielded power lines or electrical -
64 mm 152 mm 305 mm
equipment in proximity to a -
(2.5 in) (6 in) (12 in)
grounded metal conduit pathway.

Power lines enclosed in a grounded - 76 mm
152 mm
metal conduit (or equivalent - (3 in)
(6 in)
shielding) in proximity to a grounded metal conduit pathway.

10.4-1 from EIAlTIA Standard 569)

Other sources may exist along the wire path that are not included here. In most cases, general telecommunications practice will provide adequate electrical isolation.

Vertical and Horizontal Penetrations:

Commercial Connect, LLC. will perform all horizontal penetrations less than 1.5" diameter necessary for installation of the horizontal distribution system. These penetrations will typically consist of a sleeve through a firewall or side wall of a hallway into an office area. Following completion of cable installation, all penetrations will be sealed in accordance with NEC and NFPA requirements, using an approved fire sealant.

Commercial Connect, LLC. will perform all vertical penetrations greater than 1.5" diameter necessary for installation of the horizontal distribution system. These penetrations will typically consist of a sleeve through the floor area in a riser area. The recommended sleeve size is 4" diameter with at least 50mm of the sleeve protruding above and below the floor. Following completion of cable installation, we will seal all penetrations used for local distribution cabling in accordance with NEC and NFPA requirements, using an approved fire sealant.

Cable Termination:

All cables will be terminated using the EIA/TIA 5688 pin-out specifications.

All cables will be labeled on either end with a unique wire number for identification. Additionally, each device outlet will be labeled with its unique logical number.

All station cabling shall be fully tested for length, attenuation, and near end crosstalk at 100 Mb/s. Test results will be submitted with the final system documentation. See the certification section of this document for test details.

Finally, a database created for review and verification indicating wire number, termination location, CARD map grid location, and IDF patch panel location.

3.2 Fiber Optic Backbone Design and Installation


The fiber optic design proposed is based on a physical star topology that connects various areas of the campus to a central network location. The use of a star topology provides unlimited flexibility in implementing multiple architectures such as:

·        Point-to-Point Systems,

·        Physical Star Systems such as Ethernet lOBaseFL and lOBaseFB,

·        Ring Systems such as Token Ring and FDDI, and

·        Switched Architectures such as ATM.

The hub of the fiber optic star backbone in each building is the Main Distribution Facility (11DF). The MDFs will utilize AT&T 72-port rackmount Distribution Shelves (LDS). Each MDF will have one or more of the 72-port shelves, providing sufficient capacity to terminate the current fiber optic cable installation as well as provide growth for anticipated terminations.

From these MDFs, fiber optic cables radiate out to Intermediate Distribution Frames (IDFs) which serve as the hubs of segments of the local distribution network (the Enhanced Category 5 UTP system). Each IDF supports all devices in a section of the building. This is the next level in the hierarchical star. Each IDF will have the capacity for 24 fiber terminations in its fiber patch termination housing, either in a rackmount Lightguide Shelf Combination (LSC) or in a wall mount Lightguide Interconnection Unit (LIU).

All IDFs in the main building are connected to the MDF using a primary and redundant 12-strand, 62.5/125 micron, multimode fiber optic cable. This fiber optic cable will support the highest networking speeds anticipated over the next several years for the physical distances encountered.

The initial installation requires two fiber strands for each hub-to-hub link. Additional fiber strands in the cable are available for growth in the event that additional network segmentation is required in any of the IDFs or for point-to-point fiber applications (i.e. high speed diagnostic imaging systems).

The redundant, twelve-strand fiber optic cable offered is included in the design for several reasons. The first and most important is' system fault tolerance.

Redundant fiber-optic paths, when combined with the fault tolerance that the proposed 3Com equipment provides, prevent potential system failures due to mechanical or electrical problems. A secondary reason is that it is more cost effective to install cabling which meets the long term anticipated needs during the initial installation phase, than to install additional cables to meet network growth requirements later in the life of the network. the primary and redundant provide a total of 24 fiber strands to each IDF.

A backbone cable in protective EMT conduit will be installed in ceilings and risers within the building. The conduit containing the fiber optic cable will be clearly labeled at appropriate intervals (approximately 15 feet) with "Warning Fiber Optic Cable" labels for easy identification.

We feel strongly about protecting the backbone system to the greatest extent possible. This view is primarily based on the frequency and extent of physical renovation and construction that is a principle part of the day-to-day operation in a business. Without this protection, the fiber optic backbone could be damaged or completely cut accidentally by construction workers performing activity around the fiber cable. This situation could result in unnecessary downtime while the damaged cable is being repaired.


This section covers the materials specifications for the fiber optic cabling to be used to connect the various IDF equipment hub locations.

Fiber Optic Cable:

The fiber optic will be 12 strand, 62.5/125 micron, multimode fiber rated for use in riser applications. Optical Cable Ultra Fox tight-buffered cable, (part number DX12-065D-W35B/14C-9U0-OFNR) has been specified for use in this application. This cable is specially constructed for use in both indoor and outdoor applications and provides improved strength and flexibility over other fiber optic cable types available.

Individual fibers will be color coded using a PVC buffer for ease of identification. The following color code will be adhered to for 12 strand fiber:

1. Blue
2. Orange
3. Green
4. Brown
5. Slate
6. White
7. Red
8. Black
9. Yellow
11. Rose
12. Aqua

The fiber optic cable will have the following properties, ensuring that it meets and exceeds industry standards such as FDDI and EIA/TIA 568:

·        Operating wavelength of the fiber will be at 850 and 1300 nanometers. Maximum attenuation at 860 nm is 3.75 dB/km. Maximum attenuation at 1300 nm is 1.0 dB/km.

·        Minimum bandwidth at 850 nm is 160 Mhz-km. Minimum bandwidth at 1300 run is 500 Mhz-km.

·        Fiber optic cable will be rated OFNR per 1993 National Electrical Code specifications.

Fiber Connectors:

All fiber connectors are specified to be AT&T Multimode ST II. All fiber connectors are ceramic tipped, ST style connectors. The connector is properly sized for 125 micron fiber. All connectors will employ an epoxy termination method.

Fiber Couplings:

ST fiber couplings will be used to support the installed ST connectors in the termination housings. The ST couplings specified are AT&T Bayonet/Threaded style.

Fiber Termination Housings:

In accordance with EIA/TIA Standard 568, the optical fiber cross-connect hardware shall be designed to provide:

·        Means to cross-connect cabling runs with patch cords;

·        Means to interconnect premises equipment to the optical fiber network;

·        Means to identify circuits for administration in accordance with ANS1/TIA/EIA-606;

·        Means to use standard colors to functionally identify termination groups per ANSI/TIA/EIA-606;

·        Means of handling optical fiber cable and patch cords and to permit orderly patch cord management;

·        Means of access to monitor or test optical fiber cabling and premises equipment;

·        An insulating barrier, such as a cover or a door, for protecting connectors and adapters on the cabling side from accidental contact with foreign objects that may disturb optical continuity.

To meet these requirements, AT&T fiber termination housings will be used at all specified equipment MDF and IDF hub locations for the protection and termination of the fiber optic cable. The termination housings will be rack mounted or wall mounted as indicated on the associated plans and diagrams.

AT&T Lightguide Distribution Shelf (LDS) LSTIU-072/7 will be used to terminate the fiber optic cables in MDFs, providing a 72 port capacity. The LDS units will be populated with 12, AT&T 1000ST coupling panels to support the ST couplings.

AT&T Lightguide Shelf Combination (LSC) LSC2U-024/5 will be used to terminate the fiber optic cables in IDFs with racks or cabinets, providing a 24 port capacity. The LSC units will be populated with 4, AT&T 1000ST coupling panels to support the ST couplings.

AT&T Lightguide Interconnect Unit (LIU) IOOA2 LILT, a wallmount fiber termination shelf, will be used to terminate the fiber optic cables in IDFs without racks or cabinets, providing a 24 port capacity. The LIU units will be populated with 4, AT&T wall mount ST coupling panels to support the ST couplings.

In those few cases where only a 12-port capacity is required, the 200A LILT will be used.


This section covers the installation procedure specifications for the fiber optic backbone network.

Fiber Optic Cable Installation:

The fiber optic cabling will be installed in accordance with manufacturer's specifications and recommended guidelines. Attention will be paid to maximum loading, minimum bending radius, and anchoring on all vertical runs.

·        Minimum bending radius for the 12 strand fiber during installation (under tension) is 20 times the cable diameter or 5.2 inches.

·        Minimum bending radius for the 12 strand fiber after installation is 10 times the cable diameter or 2.6 inches.

·        Minimum bending radius for the buffered fiber strands is.75 inches.


Each fiber will be terminated using the ceramic ST type connectors specified. The terminated connector will be attached to the proper ST coupling and labeled.

Fiber Optic Cable Testing:

Pre-installation testing of the fiber while it is still on the reel will be required to insure that it was not damaged during shipment. Tests will be accomplished by using an Optical Time Domain Reflectometer (OTDR) and the records will be retained as part of the final system documentation. All OTDR tests will show that no micro bends or other abnormal defects are present in the fiber prior to installation.

OTDR post termination testing of each fiber will be required. The tests results will be submitted as part of the final system "asbuilt" documentation. All OTDR tests will show that no micro bends or other abnormal defects are present in the fiber.

Post termination testing of each fiber will be required for maximum attenuation at both 850 and 1300 nm wavelengths. All fiber strands will be tested after installation and termination using fiber optic power meters. Maximum allowable attenuation for any fiber link will be 4 dB. All tests will be documented and submitted as part of the final system "as-built" documentation.

Conduit Installation:

The fiber optic cabling will be installed in EMT conduit that connects the equipment hub locations throughout the facility as shown on the associated plans and diagrams. All EMT conduit will be installed in accordance with all national, state, and local requirements. Installers will pay particular attention to minimum bend radius and conduit fill ratios during the installation.

Minimum requirements for installed conduit, such as support, end protection, and continuity, are found in appropriate electrical codes. All fire wall penetrations will be sealed in accordance with NEC and NFPA requirements, using an approved fire sealant.

In accordance with EIA/TIA Specification 569, the following guidelines will be followed:

·        No section of conduit shall be longer than 30 m (100 ft) or contain more than two 90° bends between pull points or pull boxes.

·        The inside radius of a bend in conduit shall be at least 6 times the internal diameter. When the conduit size is greater than 50 mm (2 in), the inside radius shall be at least 10 times the internal diameter of the conduit. For fiber optic cable, the inside radius of a bend shall always be at least 10 times the internal diameter of the conduit.

·        A fish tape or pullcord shall be placed in installed conduit.

·        Any single conduit run extending from a telecommunications closet shall not serve more than three outlets. Conduit shall be sized per the following table and be incrementally increased in size from the furthest outlet toward the telecommunications closet.

·        Conduit shall be reamed to eliminate sharp edges and terminated with an insulated bushing. Conduit protruding through the floor shall be terminated 25-50 mm (1-2 in) above the floor surface.

·        Pull boxes shall be used for the following purposes:

o       Fishing the conduit run.

o       Pulling the cable to the box and then looping the cable to be pulled into the next length of conduit. This is usually done only with the smaller cables and not with cables of 64 mm (2.5 in) diameter or greater.

·        Pull boxes shall not be used for splicing cable.

·        Pull or splice boxes shall be placed in an exposed manner and location, and readily accessible. Pull or splice boxes shall not be placed in a fixed false ceiling space unless immediately above a suitably marked, hinged panel.

·        A pull or splice box shall be placed in a conduit run where:

o       The length is over 30,000 mm (100 ft);

o       There are more than two 90° bends; or,

o       If there is a reverse bend in the run.

·        Boxes shall be placed in a straight section of conduit and not used in lieu of a bend. The corresponding conduit ends should be aligned with each other. Conduit fittings shall not be used in place of pull boxes.

Vertical and Horizontal Penetrations:

All penetrations necessary for installation of the fiber optic backbone will be performed by in-house staff. These penetrations will typically consist of a sleeve through a firewall or riser floor. Following completion of cable installation, all penetrations will be sealed in accordance with NEC and NFPA requirements, using an approved fire sealant.

Fiber Termination Housings:

Fiber termination housings will be installed in the equipment racks in the IDF locations as indicated on the associated plans and diagrams.


3.3 Other Network Cabling Infrastructure Specifications



All communications equipment closets (MDFs and IDFs) will be fed with dedicated 110/120 volt power feeds, provided by Commercial Connect, LLC.. Outlets should be quad receptacles and located immediately behind or beside the communications racks / cabinets in a position so as not to cause the equipment power cables to traverse free space.

The power requirements for each communications closet are provided in the Network Design Details.

In closets where the network electronics are provided with redundant power supplies, two dedicated feeds will be provided.


The majority of the network electronics installation will not generate sufficient heat to warrant changes to the existing communications closet HVAC environment. The MDFs, where equipment density is the greatest, are the most likely locations to require changes. The Network Design Details section provides a worst case heat generation load for each closet.


This section covers the specifications and installation requirements for the communications racks to be placed at the IDF closet locations as indicated on the associated plans and drawings. Communications racks are specified in all areas where security and esthetic considerations do not dictate the use of cabinets.

All 19" communications racks specified are manufactured by Chatsworth. Three types of communications racks are specified in this design:

Rack Installation:

All free standing racks will be anchored to the floor using the specified anchoring kit using manufacturer's recommended guidelines for installation. The standard distance from the face of the rack to the wall is 30".

All free standing racks shall be supported at the top to the back wall using 12" wire raceway. The cable runway will be supported to the back wall using the wall angle support kit. The cable runway will be attached to the top of the rack using the J-Bolt assemblies.

Wall mounted racks will be mounted to a 3/4" plywood backboard, 3/8" lag screws should be used to secure the rack to the backboard.

All equipment racks must be properly grounded to the building structure in accordance with 1993 National Electrical Code specifications.


This design specifies Rittal Series VR Cabinets in areas that require security of network electronics and cabling or concealing the network components for esthetic reasons, such as in an open computer room.

Cabinets will have front and rear locking doors and have a ventilated top for heat dissipation. The cabinets that have extensive heat generating electronics will have a 2-fan blower unit mounted just below the top of the cabinet.

Two models of the cabinets are specified:

· Model VR 3825 - 79" H x 24" W x 34" D
· Model VR3810-40"Hx24"Wx26"D

All cabinets will be properly grounded to the building structure in accordance with 1993 National Electrical Code specifications.

4.0 Network Hardware

In this design, Commercial Connect, LLC. will employ the 3Com line of intelligent network switches/concentrators.  The 3Com solution provides a unique set of offerings that make it the best choice for networking hardware in our opinion.  In addition, Cisco Routers and IBM Server/Workstations will be used in our design.

This section describes the reasoning and the benefits offered in the equipment line proposed, as well as some of the features and functions that make this selection the best solution for the network infrastructure.


4.1 Network Switch/Concentrator Selection Criteria

The system hardware proposed is primarily intended to provide a communications infrastructure for multiple IS platforms operating with several different network protocols. Towards this end, we feel that using Ethernet for connectivity is the best option. This is due to several reasons:

These factors drive the initial decision to implement Ethernet; however, the equipment chosen for use must be capable of supporting other technologies as well. This flexibility will enable us to select any application and platform in the fixture with the assurance that the network infrastructure has means to support the selection. This is critical in that some application vendors will not support their systems on anything but their chosen, "native mode" environment (such as Ethernet or Token Ring).

In order to achieve the desired flexibility, it becomes necessary to look at the intelligent hub market for solutions. The intelligent hub offers several other features that work well in the registry environment:

The combined effect of having the architectural flexibility to select any applications in the future, and the numerous registry specific benefits outlined above, make the choice of an intelligent hub as the network hardware platform a natural one. In examining the intelligent hub market, there are numerous vendors who provide the basic features common in most intelligent hubs.

The selected vendor must demonstrate a migration path to the future of networking technology. In order to ensure that a particular manufacturer can do this, it is necessary to look at three major factors:

·        The long range plan of the 'manufacturer to migrate its intelligent hub line to the future technologies,

·        The viability of the manufacturer to survive in the highly competitive market of networking hub vendors, and

·        The track record of the manufacturer to provide successful, high level technological products.

If these factors can be met, then it becomes a matter of selecting which vendor offers the features and functions that provide a superior solution for the near and long term needs.

In today's intelligent hub market, several vendors can meet the criteria outlined above. Some of the major players in this market are,

This list is not intended to be complete, however, it does represent the majority of manufacturers actively involved in networking today. It should be noted that the manufacturer's listed above all meet the basic criteria necessary for an intelligent hub selection. It should also be noted that each manufacturer has particular strengths and weaknesses when evaluated against the three decision factors listed above.


The first factor, the long-range plan of the manufacturer to migrate to future technologies, is addressed in several different ways by all of the vendors.

The method used by several vendors is to produce a separate product line that addresses the future technology needs of the networking environment. This method ensures that the hub architecture can take advantage of the latest in technology, and not be restricted by having to carry forward any of the older architectures used in the current product line.

With some vendors, it is necessary to completely upgrade all components when migrating to the new technologies (replacing all Ethernet modules, management modules, etc.). This can be an expensive proposition when the investment is already made to connect the current environment.

3Com however, has a different approach. The new generation intelligent hub from 3Com supports the modules from the current generation hub. This means that we could upgrade the hub chassis to the next generation technology, without losing the investment in connectivity hardware (the Ethernet 100BaseT modules and management modules for example).


The second factor, the long term viability of the vendor, is more difficult to gauge. There are no crystal balls that will enable anyone to clearly determine the long term viability of a particular vendor. It is therefore necessary to look at the current market status, company history, and other factors to make a best guess call with respect to viability.

3Com represents the third largest intelligent hub manufacturer in the world today. With a long history dating back to the early eighties, the current financial stability and growth (3Com is the fastest growing hub vendor in the market today), and a large Fortune 1000 client base, 3Com should also be assured of an excellent long term future.


The third factor, the past track record of the vendor to provide successful, technological solutions to the industry, is important when assessing the value of the future technological solutions provided by each vendor. In this industry, the manufacturers generally approach the issue of technological solutions in one of two manners; either through acquisition of another vendors product, or, through internal research and development.

3Com remains committed to a strong research and development effort to improve and enhance their product line.

3Com is also acquiring technologies from other high-technology companies to round-out their networking infrastructure product line. 3Com's strategic partnerships with Cisco Systems and IBM make the 3Com product line one of the most diverse and comprehensive available today, all the while maintaining 3Com's commitment to quality and complete fault tolerance.

Based on the three factors, we feel that 3Com offers the most robust solutions for enterprise networking in the networking environment. This reasoning is based on several factors offered by 3Com that are unavailable through other vendors:

Based on the criteria detailed above, we are proposing the 3Com networking product line for use. Following is a more in-depth look at the 3Com products specified for use.


4.2 3Com SuperStack II 3300 Concentrators/Switches

In order to address the current network connectivity needs and plan for the integration of future high speed technologies into the system, it is necessary to select a network hardware platform that offers the flexibility and architecture to achieve both goals. Towards this end, we have selected the 3Com SuperStack system to use as the central network hardware component in each MDF. In using the SuperStackII hub at the center of the network, we are assured of a migration path from the initial multi-segmented Ethernet environment, to switched architectures, such as ATM, that we may require in the future.

The SuperStack hub is a 24-slot platform which offers over gigabit Ethernet connectivity capacity in a fully passive backplane design. This platform is capable of integrating with shared network technologies such as Ethernet, Token Ring, and FDDI, as welt as switched technologies such as switched Ethernet and ATM.

Features and Specifications:

·        Cost effective. The 3Com® SuperStack® II Switch 3300, with one of the optional Gigabit Ethernet modules, reduces the cost of migrating to Gigabit Ethernet, so any size business can enjoy high-speed technology

·        Investment protection. This switch works with your existing SuperStack II Switch 1100 and SuperStack II Switch 3300 switches, so you can mix and match any SuperStack II Switch 3300 in one stack

·        The ability to stack any two switches together through an integrated matrix port; up to four switches can be stacked together using a SuperStack II switch with the optional matrix module, or by using the new SuperStack II Switch 3300 MM with its integrated Matrix Module

·        Lifetime warranty. Register online for a lifetime warranty on all hardware, including fans and power supplies

·        Easy management. 3Com® Transcend® Network Supervisor is included with every unit. This powerful application lets you discover, map, and monitor your network with ease.

·        Policy enforcement with FastIP, IGMP snooping, IEEE 802.1D (incorporating 802.1p prioritization), and IEEE 802.1Q standards-based VLANs

·        Dual queues to help prioritize multimedia traffic

·        Multicast filtering using IGMP snooping/GMRP for more efficient bandwidth utilization for handling video traffic.

·        Elastic port buffering for on-the-fly port buffer memory allocation, enabling automatic performance optimization based on network traffic

·        Flow control to maximize performance and minimize packet loss under heavy network loading

·        Trunking support to aggregate links into a single high-speed connection to other switches or backbone networks

·        Automatic detection of full- or half-duplex operation on all ports to maximize performance without manual configuration

·        Available with 12 or 24 autosensing 10/100 ports.

·        Expansion slot allows you to add optional modules for Layer 3 switching, Gigabit Ethernet connectivity, and matrix connections to other SuperStack II Switch 1100 and Switch 3300 switches

·        Embedded web-based monitoring and control system. Remote Monitoring (RMON) and Transcend Network Supervisor software enables authorized administrators to troubleshoot and configure a switching stack from any location

·        Support for resilient links and spanning tree, as well as optional redundant power supplies


Physical Dimensions
Height: 7 cm (2 3/4 in) x width: 44cm (17 1/4 in) x depth: 30cm (12 in)
Weight: 4.4kg (9 2/3lbs)

Environmental Requirements
Operating temperature: 0° to 50°C (32° to 122°F)
Storage temperature: -10° to +70°C (14° to 158°F)
Operating humidity: 10% to 95% relative humidity, noncondensing
Standards: EN60068 (IEC68)—various parts

Agency Certifications: UL 1950, EN60950, CSA 22.2 No. 950, IEC 60950

Emissions: EN55022 Class A, FCC Part 15 subpart B Class A, ICES-003 Class A, VCCI Class A, AS/NZS 3548 Class A, CNS 13438 Class A
Immunity: EN50082-1

Heat Dissipation
75 watts maximum

Power Supply
AC line frequency: 50/60 Hz
Input voltage options: 90 to 240 VAC
Current rating: 3 amps maximum

Standards Supported
SNMP protocol (RFC 1157)
MIB-II (RFC 1213)
Bridge MIB (RFC 1493)
Repeater MIB (RFC 1516)

Terminal emulation:
Telnet (RFC 854)

Protocols used for administration:
UDP (RFC 768)
IP (RFC 791)
ICMP (RFC 792)
TCP (RFC 793)
ARP (RFC 826)
TFTP (RFC 783)


Facility Locations of Concentrators

Model 3C16980

Commercial Connect, LLC., LLC
MDF Louisville 2 24-slot
Computer Room

Simon Properties Group MDF2 Indianapolis 1 24-slot
Computer Room

Simon Properties Group MDF3 Chicago 1 24-slot
Computer Room

Simon Properties Group MDF4 Atlanta 1 24-slot
Computer Room

Simon Properties Group MDF5 Dallas 1 24-slot
Computer Room

Simon Properties Group MDF6 London 1 24-slot
Computer Room

4.3 Cisco 3600 Routers

The Cisco 3600 Series is a family of modular, multiservice access. With over 70 modular interface options, the Cisco 3600 family provides solutions for data, voice video, hybrid dial access, virtual private networks (VPNs), and multiprotocol data routing. The high-performance, modular architecture protects customers' investment in network technology and integrates the functions of several devices into a single, manageable solution.

Cisco extended the successful Cisco 3600 Series with the Cisco 3660 multiservice access platform. The Cisco 3660 provides higher densities, greater performance, and more expansion capabilities. The additional power and performance of the Cisco 3660 platform enables new applications, such as packetized voice aggregation and branch office ATM access ranging from T1/E1 IMA to OC-3.

The Cisco 2600 and 3600 series of multiservice platforms has been greatly enhanced with many voice capabilities: added support for Voice over Frame relay (VoFR) and Voice over ATM (VoATM-AALS) on the digital voice interfaces (T1 and E1). QSIG is also now supported on all digital interfaces, including T1/E1 and BRI. Other enhancements include Off Premise Extension (OPX), VoIP over Frame Relay, and enhanced queueing functionality. In addition, a feature that works with an upcoming version of Call Manager softwars makes these products perfect gateways for the PBX and PSTN for IP telephony, enabling applications like call transfers, holds, and conferencing.

This design specifies the Cisco 3600 Router as the key components of the Wide Area Network. Each of the main campuses will utilize a Cisco 3600 router for WAN access; two of the campuses (Louisville, KY and Simon Indianapolis, IN) will also rely on the router for network segmentation.

The Cisco 3600 series of multiprotocol routers combine Cisco Systems' proven software technology with exceptional reliability, availability, serviceability, and performance features to meet the requirements of today's most mission - critical internetworks. The Cisco 3600 series provides information system professionals with the flexibility they need to meet the constantly changing requirements at the core and distribution points of the internetwork, and provides a clear migration path to tomorrow's technologies.

The Cisco 3600 is Cisco's premier high-end platform, supporting more network interfaces and media types than any other Cisco platform and including support for dual power supplies.

Network interfaces reside on modular interface processors, which provide a direct connection between the high-speed Cisco Extended Bus (CxBus) and the external network. Distributed processing is accomplished by the Route Processor (RP) and Switch Processor (SP).

The Cisco 3600 runs the Internetworking Operating System (IOS), Cisco's industry leading networking software. IOS assures robust, reliable internetworks by supporting both LAN and WAN protocols, optimizing WAN services, and controlling internetwork access. In addition, IOS allows centralized, integrated, and automated installation and management of internetworks.

The Cisco 3600 provides multiple slots for interface processors. Following are the interface processor types:

·        Ethernet interface processor (EIP)

·        Token Ring interface processor (TRIP)

·        FDDI interface processor (FIP)

·        HSSI interface processor (HIP)

·        Fast serial interface processor (FSIP)

·        Asynchronous Transfer Mode (ATM) interface processor (AIP)

·        Multichannel interface processor (MIP)

The reliability, availability, and serviceability features of the Cisco 3600 series include the following:

·        Online software reconfiguration: Enables software configuration changes to occur without rebooting or interrupting network applications and services.

·        Online insertion and removal: Allows seamless upgrades to higher density and new interface processors without rebooting or taking the system offonline. Reduces operator intervention, because like interface processors are automatically reconfigured.

·        Fast boot: Enables the system to come online quickly (35 seconds is typical) after software upgrades, minimizing impact on the network.

·        Environmental monitoring: Alerts the operator to fluctuations before critical conditions occur, allowing proactive resolution while the system stays online.

·        Self-diagnostics and tools: Ensures that modules are operational before going online, eliminating potential network problems.

·        Optional dual power supply systems (Cisco 3600 only): Extends individual power supply life through load sharing. Allows users to implement dual sources of prime power. Each supply has its own power cord, eliminating the risks associated with failure of uninterruptable power supply systems (UPS) or building power.

·        Flash erasable programmable read-only memory (EPROM): Enables fast, reliable software and microcode upgrades. Allows single centralized point of administration, obviating the need to visit each routes site when upgrading software or microcode.


The network design specifies three of the Cisco 3600 interface modules: the Ethernet Interface Processor (EIP), the Fast Serial Interface Processor (FSIP), and the Multichannel Multiplexes Interface Processor (MIP).

·        EIP: The EIP provides two, four, or six high-speed (10-Mbps) Ethernet ports. Each port requires an 802.3 transceiver. In the Commercial Connect, LLC. design, the EIP provides connectivity for ethernet user network segments and hosts to the wide area network.

·        FSIP: The FSIP provides four or eight high-speed serial ports (up to 8 Mbps). The FSIP provides the interface between the carrier provided circuit and the routes.

MIP: The MIP provides a multichannel multiplexer that allows aggregate multiple channels at Nx64 and/or Nx56 on the same 1.5-Mbps T1 or 2-Mbps E1 line. Two models, CX-MIP-ICT1 and CX-MIP-2CT1 provide one or two ports. In the Commercial Connect, LLC. design, the MIP provides the ISDN primary rate interface.


4.4 IBM Servers


4.4.1 RS/6000 Model F80

The IBM RS/6000 F80 was selected as the primary server for the Registry Database.  It is a powerful enterprise server with excellent performance and expandability.  The Model F80 is a compact, deskside UNIX server with the performance, reliability, availability and serviceability demanded by today's e-business applications.

The Model F80 features significant reliability and availability innovations designed to allow the system to identify problems often before they interfere with operations. These features help the system remain operational while components such as disk storage or communications adapters are added or replaced. New to the F80 are hot-plug PCI slots, a hot-plug redundant power option, and hot-plug redundant cooling fans.

At the heart of the F80 is a service processor that is designed to constantly monitor the system's vital signs. It can determine and recommend actions often before a problem arises. If desired, a service call may be automatically placed.

The F80 also has an IBM-unique feature, Dynamic CPU Deallocation, that monitors the processors. In the event a processor displays indications of an impending failure, this feature working with AIX 4.3.3 gracefully takes the faulty processor offline. Work from the failing processor is automatically reassigned to other processors and replacement of the failing processor can be scheduled for a convenient time.

The hot-plug PCI slots make it possible to keep applications running while I/O adapters are added or replaced. Individual adapters can be enabled or disabled as needed, while operations not dependent on that adapter continue to run. There is usually no need to power-down and restart the system. Hot-swappable disk disk drives may be added or removed to meet unexpected demands without interrupting operations.

For near continuous operations, industry-leading High Availability Cluster Multiprocessing (HACMP) disaster recovery software packaged with dual F80s is available. This cluster solution, HA-F80, when combined with applications that meet IBM's ClusterProven™ standards, provides a superior base for high availability.

An unlimited user license of IBM's industry leading version of UNIX, AIX 4.3.3, is included. Providing real value in reliability, availability and security, AIX is tuned for performance and is widely recognized as state-of-the-art in systems and network management.

AIX 4.3.3 delivers Java™ technology, Web performance and scalability enhancements, and is an excellent choice for managing complex installations. It offers Web-based remote management tools to control the system and monitor key resources such as adapter and network availability, file system status and processor workload.

Specifications and Configuration

Standard features

System expansion

RAS features

Operating system


4.4.2 IBM Netfinity 7600


For the replication servers of the registry database in Chicago and Atlanta, as well as the name servers for all locations, we have chosen the IBM Netfinity 7600.  Besides these eight servers, the headquarters offices in Louisville will secure additional units to serve as web server, backup server and test server.

Netfinity employs X-architecture, a design blueprint that leverages existing IBM technologies to build some of the most powerful, scalable and reliable Intel processor-based servers available, capable of supporting tens of thousands of users.

Configuration and Specifications


Form factor Rack

Orientations allowed  Horizontal

Bus type/architecturePCI

Slots x bays total (free) 6(5) x 14(12)

Expansion bus type  PCI


Processor (CPU)      Pentium III Xeon

Processor internal clock speed   700 MHz (Pentium III Xeon)

Planar clock speed   100 MHz

SMP processors std   1

SMP processors max 4

Processor manufacturer Intel

Math co-processor  Built-in

L1 internal CPU cache 32 KB

Processor upgrade options  Faster Pentium III Xeon

SMP capable (multiple processors) Yes

L2 cache std             2048KB

L2 cache max           2048KB

L2 external CPU cache type Full speed ECC

BIOS type Flash


Memory (RAM)   2 GB

Memory (RAM) max 16384 MB

RAM speed 100MHz

RAM type ECC Chipkill

RAM slots total 16 RDIMM

RAM slots available 12 RDIMM

Hard disk

HArd disk size 18.2 GB

Hot swappable drive bays 10/10

Hard disk controller   Integrated Dual Channel Ultra2 SCSI LVD

Hard disk type Open bay

Max Hard Drive Capacity 364 GB

Graphics subsystem

Graphics type  SVGA

Graphics chipset      S3 Trio3D

Graphics data width 16

Video RAM type SGRAM

Video RAM std 4 MB

Video RAM max 4 MB

Max resolution (with std video RAM) 1600x1200 65536 colors

Max resolution (with max video RAM) 1600x1200 65536 colors

Max colors (with max video RAM) 16777216

Max colors (with std video RAM) 16777216

Graphics bus interface PCI


CD-ROM speed 40Xmax-17Xmin

CD-ROM interface type EIDE

CD-ROM data transfer rate 2550, 6000 KBps

CD-ROM average access time 90 ms

CD-ROM transport type Front tray loading


Communications features Dial-in for control/monitoring/remote management, Dial-out for alert notifications, MoST Connect, Remote POST Control, Temperature and voltage monitoring


Power management

Power supply 750(3x250)

Power supply type 100-127VAC (50/60Hz), AC 200-240V (50/60Hz)

Cooling system 4 fans

Power management features Auto restart


Security features Boot sequence control, Mechanical locks, Power on password, Privileged access password, Unattended startup

VPD support CPU Board, Hot swap disk backplane identifier, Processor card identifier, Power backplane identifier, Power supply identifier



4.5 Hardware Configuration Summary


A detailed hardware summary by installed location follows in the Appendix A at the end of this document.



5.0 Wide Area Network Connectivity

This section describes the Wide Area Network design solution for the Commercial Connect, LLC. network. The design was developed in concert with MerchantWired.

 The design of the Wide Area Network has three objectives:

·        Provide users throughout the enterprise with seamless, timely access to the IS hosts and servers,

·        Provide a scaleable architecture supporting future growth and implementation of high-bandwidth technologies emerging on the near horizon, and

·        Provide a platform for multi-media communications (voice, video, and data) within the corporation and to off-net users.

In order to address the connectivity needs of the modern internet marketplace, information and communications access must be extended throughout the entire system. The WAN design must take into account users located at the main facilities, those at smaller facilities that nonetheless require continuous access to the network, and remote users with periodic requirements to exchange information with users and databases on the corporate network.

The WAN must also support promising technological developments on the registry frontier. One of the fastest emerging technologies, and one that will receive more and more attention in the marketplace, is video. We are just now in the beginnings of a video age that could revolutionize the way in which business is practiced. Maintenance operations could be monitored by other administrators located in different states or countries, or administrators could connect via teleconferencing links as needs dictate. This technology is just beginning to make it's way into the operational framework of the organization.

In order to provide the connectivity that is required to enable the technologies and applications mentioned above to work, a communications highway must be built that ties all component sites of the network together. Like any highway, the WAN highway must be capable of supporting the traffic, voice, video, and data, that would eventually be required to travel over it. This is the object of the design, to create a system that can fully support the needs and requirements of the company both now and into the future.

5.1 User Site Models

In order to develop a usable plan for extending the network beyond the traditional boundaries (the main campus), it is necessary to address multiple methods of access for each different type of site that will be a part of the final system. This is because the method used to connect a single office to the network will be substantially different than that used to connect a large corporation to the system. Therefore, the WAN design focuses on defining several basic methods of connecting potential sites to the network, each corresponding to a specific user site model.

The user site models used in the WAN design describe the general connectivity requirements of a particular size or type of remote data communications requirement. For example, an administrator requiring access to network applications and services from his or her home, will require quite a different class of connectivity than will an large corporation with fifty to one hundred employee encounters per day. Recognizing this, the design starts by classifying three types of user site classes that will be used to describe the WAN system design.

Without using the model concept, each potential site would need a requirements analysis and a separate design for that specific site. As the network grows, the administrative task of keeping up with the connectivity requests could rapidly become unmanageable. By having models to choose from, when a request is made, the connectivity solution is simply selected from a range of solutions that would meet the needs of the site. This method also reduces the number of different types of equipment and connections required to provide WAN connectivity, thus improving the manageability of the overall system.

Below is a listing of the classes of user sites used in the design and the descriptive criteria for each.


The first class can be described as a large corporate site. A typical site of this class would be a corporate headquarters. In order to qualify as a Backbone WAN site, the following requirements are defined:

1) The site must have one or more local area networks,

2) The site could have either a substantial number of users requiring access to the enterprise network or high-speed connection requirements.

3) The Backbone WAN connected site requires full time connection to the enterprise network on a 24 hour a day basis.


The second class of WAN access is generally suited to a smaller site than that defined above. Typical sites of this class are the satellite offices and redundancy locations across the country. The criteria for this class site would be the following:

1) A limited number of user devices requiring access to the system from a local networked environment,

2) Over 99% required connectivity time to corporate site is essential.

3) A user in this class would be transferring limited amounts of data information for redundancy. 


The third class of WAN access would be representative of a single user accessing the system from a remote location such as his or her home or office. A typical example of a user in this class is the network Programmers and Administrators at the corporate office who must access the network from their home after hours or temporary work area. The criteria for this class user consists of the following:

I) Single user PC requiring access to the system resources,

2) Limited use access time requirements.

The following sections address the solution for each of these classes of WAN access.


5.2 Corporate Backbone WAN

Commercial Connect, LLC. has several major sites with a broad mixture of user applications requiring high bandwidth and Wide Area Network interconnectivity solutions. In developing a WAN solution, we considered a number of WAN alternatives in seeking to obtain the following objectives:

·        Communications channels for voice and data applications. Although video is of a lower priority, channels should nevertheless be in place.

·        Cost effective and efficient utilization of alternative solution elements,

·        Extremely high reliability of service to users with proven solutions and centralized network services management,

·        Flexibility to expand with anticipated growth of bandwidth and application requirements,

·        State-of-the-alt solutions, where available,

·        Compatibility with future developments of services and equipment,

·        Currently available services for a relatively near term implementation time frame.

The WAN Backbone is focused on providing wide area connectivity to the six major sites:



A number of alternative WAN technologies could potentially meet the requirements. In selecting a solution, the following alternatives and considerations must be addressed:

·        Geography - Inter-LATA or Intra-LATA locations,

·        Services - Dedicated fixed bandwidth leased lines and/or value added public network switched services,

·        Access - Integrated access circuits and/or separate access circuits to each site,

·        Topology - Integrated and/or separate trunk circuits between sites; Mesh, star, etc. interconnection,

·        PBX trunking requirements for intra-corporate voice communications, offnet intra-LATA voice communications, and long distance communications.

·        Video Teleconferencing requirements within and outside of the major corporate sites.

Commercial Connect, LLC., in conjunction with MerchantWired identified three alternatives for backbone WAN connectivity.


Native Mode LAN (NMI.) is a service available within the LATA which provides Ethernet, Token Ring, or FDDI connectivity within the metropolitan area. Redundant 100MB FDDI rings throughout the Louisville area carry this service. The customer is provided an ethernet interface to the earner network.

Native Mode LAN has two primary disadvantages: first, it is not designed to support integrated video and voice, and second, since it relies on a fiber ring topology.


T-1 typically service provides dedicated digital service between two locations. The digital circuit can be broken down on the customer premises into 24 discrete channels (DSO channels), each of which can be allocated to voice or data traffic.

MerchantConnect provides a capability to route multiple T-1 circuits through the digital cross-connect switch and dynamically reconfigure the individual DSO channel connection assignments. This permits a very flexible method of allocating bandwidth for multiple types of traffic between corporate sites. This is particularly beneficial in the early stages of the network implementation when the network will have to be fine tuned for the appropriate mix of voice and data bandwidth across the wide area network.

The switch also has access to local carrier central offices, long distance carrier central offices, and to a recently connected video conferencing switch.


As a final alternative, Frame Relay, implemented over the T-I/Flexserve architecture described above, was considered for the data networking requirements. Frame Relay is a packet transmission technology based on permanent virtual circuits (PVCs) between customer locations, routed through a carrier's Frame Relay packet switching network. Multiple PVCs can share a single carrier access circuit, often reducing carrier access costs. Frame Relay is ideally suited for access between multiple sites where the nature of the traffic is bursty.

With the current requirement limited to interconnecting six major sites, and the additional service cost and administrative overhead incurred with Frame Relay, there is not sufficient justification for implementing Frame Relay today. Frame Relay does, however, offer an excellent migration path to ATM as the Commercial Connect, LLC. network grows to encompass additional sites or as requirements for data communications to agencies outside of the corporation surface.


From the feasible alternatives, the following carrier-provided services were selected for implementing the Wide Area Network. The Wide Area Network Connectivity diagram depicts how these services are employed.  (See Attached Graphs)

T-1 Service: This is the primary communications channel for inter-corporate voice, data, and video traffic. Specifically, the applications recommended for consideration are:

·        PBX to PBX voice trunks

·        LAN to LAN, LAN to host, or host to host 56 KBPS data circuits.

·        Intra-corporate video teleconferencing, using an inverse mux for rates higher than 112 KBPS.

·        Long distance video teleconferencing to non-corporate sites and shared IXC MCU services.

·        Long distance voice calls to the IXC C.O.

The network manager can establish a logical network between the major corporate locations, as depicted in the WAN Connectivity Diagram for data traffic. This logical network will consist of router to router LAN connections, PBX to PBX voice connections, and CODEC to CODEC video conferencing links.

This approach is scaleable; additional T-1 circuits can be added as the demand increases. Channel assignments and digital cross connects can be made at the DSO level. The level of access for the initial configuration must be determined after a detailed requirements analysis.

The T-1 circuit termination device will be a Coastcom DI/MUX III T-1 channel bank with integrated CSU. Connections between the router and the Coastcom channel bank will be a V.35 interface. In addition to the router, the Coastcom channel bank will attach to the PBX through digital DSX channels to permit intra-corporate trunking and access to the Interexchange Carrier (IXC) central office.


The network design provides sufficient circuit termination equipment for two redundant circuits to the Internet. Based on anticipated usage, Commercial Connect, LLC. will specify the circuit capacity. These circuits will be terminated on routers in-house.


Redundancy has been built into this WAN design in several ways:

Diverse Cable Routing: The hardware included in this design will support diverse cable routing into each main corporate site. Circuit outages due to cable damage from construction or disaster are a significant source of WAN downtime. By specifying diverse routing of multiple T-1 s into each site, Commercial Connect, LLC. can reduce the probability of a catastrophic loss of data communications to any of the six major sites.

Redundant Backbone Connectivity: The triangular form of the backbone connections provides an alternate route between any two sites if one of the backbone links should fail. The Cisco routers specified in this design will sense the circuit outage and intelligently route traffic around the failed link.

Redundant WAN Termination Hardware: Coastcom channel banks are provided for each site, each terminating one of the diverse routed T-1 circuits. Each Coastcom channel bank can accept a second T-1 circuit as well.

Redundant Internet for SRS Host Connections: As specified below in more detail, two circuits to the SRS/Internet provide a backup or overflow capability in the event that one fails. Once again, the Cisco routers will dynamically route the traffic around the failed link.


5.3 Remote Offices


Employees have at least ISDN Connection in their homes to the services offered by the corporate office.  In the case of an emergency, employees are directly connected to the corporate offices and can manage the network from their homes.  Certain key employees are on call twenty-four hours a day, seven days a week for such emergencies.  This is in addition to our 24 hour staffed offices.


5.4 Remote Communication Server


Commercial Connect, LLC. will connect to its remote locations via redundant T-1’s through the MerchantWired extranet.  MerchantWired uses a combination of services through Intermedia and UUNet.

The design includes the following functionality at each remote site:


Data drops and associated hardware for the number of users specified in the network access requirements listing.


5.5 Individual/Home Remote Access


Commercial Connect, LLC. has designed a solution utilizing Integrated Services Digital Network (ISDN) connections to provide network connectivity to employee homes. ISDN provides an end-to-end digital connection between two customer sites through a dial-up switched digital network. The connection can be used to transmit a variety of services, including data, voice, and video.

Individual/Home sites will be provided with a Basic Rate Interface (BRI) ISDN connection, supporting up to 2 "B" data channels at 64 KBPS and one "D" signaling channel.

A total data rate of 128 KBPS can be achieved on this connection, sufficient for single user access to the backbone network.

Four ISDN Primary Rate Interface (PRI) connections will provide access into the corporate backbone network. Multichannel PRI modules in the 3Com Total Control  system will terminate the circuits and provide bridging between the ISDN network and the backbone WAN.

Each bridge is capable of providing up to 23 64 ICBPS ISDN B channels. The interface with the local carrier will be a PRI circuit with ISDN network access. The bridges function as any remote bridge, providing remote users direct access to all functionality of the enterprise network. Remote users with ISDN Basic Rate Interfaces (BRI) can call the bridge on demand and establish a direct network connection. If the bandwidth of one 64 KBPS channel is insufficient, an additional channel can be added to the connection for a total of 128 KBPS channel bandwidth. Up to 23 separate connections can be established with each bridge.

The bridges will also support connections with other primary rate interfaces, permitting scaleable access of up to 23 64 KBPS channels.

6.0 Network Management


6.1 Distributed Network Management


The complexity and wide area nature of the enterprise network dictate a network management approach which is both flexible enough to deal with the myriad of issues and changes that a network manager faces on a daily basis and powerful enough to manage a network spanning our six major facilities and numerous minor ones as the need arises. Our approach to network management for this network is a distributed architecture, with network management workstations located at each site for local changes and monitoring and a powerful, UNIX based platform, for enterprise wide monitoring and control.


Critical to the implementation of a distributed management architecture is definition of the roles and responsibilities of each manager in the system. Commercial Connect, LLC. will appoint an enterprise network manager, responsible for overall network oversight and day-to-day monitoring of the system. Responsibilities of the enterprise network manager are listed below:




·        Manage the wide area network connections: monitor the circuit and traffic status, perform system troubleshooting in the event of circuit failure or traffic overload.

·        Manage the facilities backbone network within each location: make user/concentrator assignments to the network segments and manage host / server connections to the network.

·        Manage network servers that support the enterprise.

·        Monitor the status of traffic on the facilities network and alert the facilities manager of users workstations that might be causing network troubles.

·        Manage the user connections to the network: install and configure network interface cards and configure the concentrator ports for user access.

·        Manage user accounts on local servers.

·        Manage user application software and desktop configurations.


Today's networking equipment has powerful management functionality built into the hardware in a standards based environment. The management standard that is utilized by the majority of networking equipment is the Simple Network Management Protocol (SNMP) which offers a rich suite of services and control functions that will enhance the job of managing the network.

While the equipment proposed includes network management built into the hardware, the ability to access and control the equipment requires the use of separate management applications. These applications offer the ability to view, control, and analyze the data collected by the equipment hardware, from a single, localized workstation.

In order to fully enhance the network offering, we are proposing two levels of network management capability. The first system is a feature rich UNIX based system that represents the state of the art in network management systems for managing the wide area network. The second system is a Windows 2000 server based package that meets the needs of the facility network manager.

6.2 Enterprise Applications Management System

In order to achieve the processing power necessary for managing a network of the magnitude of the enterprise network, we are recommending a UNIX based system for the enterprise network manager.

The platform for the enterprise management system will be an IBM RS/6000 with the following specifications:

IBM RS/6000 Power PC Model F80:

The server will be configured with IBM AIX. This platform will provide a comprehensive system that will be capable of supporting the future growth of the management system.

The primary applications initially running on the enterprise management system will be:

·        Cisco System's Ciscoworks for Netview for AIX.

·        Oracle Database application server

CiscoWorks Router Management Software provides both a series of applications that simplify day-to-day router monitoring and administration and a series of management applications for offline analysis of network traffic patterns and trends. It is an advanced internetwork node management application that enables Cisco routers to be controlled over the network from local an/or remote locations. Ciscoworks provides a comprehensive set of router management capabilities accessible through a point-and click, windows based, user interface. It performs:

·        Centralized configuration management to ease network set-up and expansion

·        Real-time performance and error analysis to enhance network tuning

·        Real-time event and fault monitoring to simplify problem identification and isolation.

The management system proposed will provide a comprehensive management tool for use in controlling and maintaining the entire enterprise network. we will install, configure, and provide on-site training in the use and understanding of the operation of the management system.


6.3 Facility Network Management System


The package that is proposed for use at the facility level is based on a Windows Platform. It includes Intel's LANDesk Manager for desktop management.

The platform for the facility management system will be the IBM Netfinity 7600 with the following specifications:

IBM Netfinity 7600:

We have included Intel's LANDesk Management Suite for management of user workstations. LANDesk manager provides a central view of the network and the capability to manage everything from desktop systems, to servers. LANDesk Manager puts a completely integrated suite of solutions at the network manager's command, permitting seamless movement from one application to another.

LANDesk manager simplifies network administration by permitting the network administrator to manage down to the desktop platform level from the management workstation. The administrator can take control of a user's workstation, obtain an inventory of the hardware and software resources on the LAN, and forward alerts to electronic mail and even pagers.

LANDesk manager monitors network health indicators such as packet rates, utilization, and error levels. Its graphic, real time summaries provide application related traffic information and provide extensive printer management capabilities.

Applications included with LANDesk Manager include:

The network management station will include:

·        Workstation, modem, and UPS installation

·        Network map development

·        Intel LANdesk Management Suite

6.4 Network Server Management


The facility management workstation at the corporate offices will also provide enterprise server management functionality. This platform will host the remote console, and Exchange management applications.

The following table depicts the applications provided for the facility management workstation at each campus:



LANDesk Management Suite

7.0 Network Host and Server Integration

This section of the network design describes the solution for host and server integration throughout the Commercial Connect, LLC. corporate network. The principle objective is to define the methods for users throughout the network to access computing resources regardless of their location in the enterprise. The solution can be divided into three host classes:

·        Access to the Shared Registry Systems (SRS) Windows 2000 Server

·        Access to Netware based applications

·        Access to the UNIX based applications and other hosts


7.1 Microsoft Windows 2000 Advanced Server and Oracle Database Application Integration

Windows 2000 Advanced Server

Microsoft’s Windows 2000 Advanced Server promises the best of all worlds for companies and Internet Service Providers.  Since it is a relatively new product, we can not depend on its promised abilities to run the SRS database.  Therefore, we will purchase this server environment and included applications but rely on Oracle’s proven ability for reliable and efficient database manipulation.  Should Windows 2000 DataCenter Server proves its worth, a combination of both systems will allow for the best of all worlds.

Reasons for Windows 2000 are as follows:

·        Reliability. An essential requirement for business users is a personal computer they can count on. That's why Windows 2000 includes fundamental improvements—such as modifications to the operating system core to prevent crashes and the ability for the operating system to repair itself —that make it most reliable desktop operating system Microsoft has ever produced. On comparative reliability tests conducted by ZD Labs, the average system uptime of Windows 2000 Professional was over 50 times that of Windows 98 and 17 times that of Windows NT Workstation 4.0.

·        Mobility. Mobile computing is simpler and more efficient with Windows 2000. This means you can work anywhere, anytime while also saving time and increasing productivity. As described in these articles, “Finally, a Notebook OS” Offsite Link and “Mobile Users In Love with Win2K” Offsite Link, Windows 2000 offers mobile users key features such as improved power management, the ability to hibernate and restart the system without a reboot, and the ability to take files/folders offline.

·        Manageability. Windows 2000 is easier to deploy, manage, and support. Centralized management utilities, troubleshooting tools, and support for self-healing applications all make it simpler for administrators and users to deploy and manage desktop and laptop computers. These improvements pay off in reduced costs, as shown by the Giga TCO/ROI study Offsite Link.

·        Performance. The advancements made throughout Windows 2000 are accentuated by the operating system's speed. As shown in ZD Labs tests running the most popular business applications, with 64 MB of RAM, Windows 2000 was 32 percent faster than Windows 95 and 27 percent faster than Windows 98. It is also significantly faster than Windows NT 4.0 on configurations with 32 MB.

·        Security. Windows 2000 provides comprehensive security features to protect sensitive business data, both locally on the desktop computer and as it is transmitted over the local area network, phone lines, or the Internet. With its support for Internet-standard security features such as IP Security, Layer 2 Tunneling Protocol, and Virtual Private Networking, Windows 2000 is so secure that banks, such as Credit Suisse First Boston, use it. For some organizations, such as the law firm Dorsey & Whitney LLP, security is a key reason for moving to Windows 2000.

·        Internet. Using the Internet and a local desktop is a single unified user experience with Windows 2000, as described by PC Magazine Offsite Link. This common user interface, in addition to improved search capabilities, makes it much easier to find and use information locally and on the Web.

·        Data Access. Windows 2000 Server takes advantage of IntelliMirror technologies. By allowing storage of important information and desktop settings on a central computer, IntelliMirror makes it possible to work on any computer attached to a network as if at one’s own desk. The centralized management savings made possible by Windows 2000 IntelliMirror technologies are one of the reasons WFofR, Inc. is using Windows 2000.

·        Hardware. Windows 2000 allows the user to take advantage of new hardware devices, such as those with universal serial bus (USB) and IEEE 1394 (Firewire) connections. In addition, support for existing hardware makes Windows 2000 ideal for companies, such as Panasonic, that want to standardize on a single operating system across their organizations.

Some of the above information was obtained from Microsoft’s Web Site located at


Database Component

Oracle 8i with Oracle JVM along with Oracle Internet Application server will be utilized for the database component to house the SRS Registry system.

Oracle8i is the only database specifically designed as an Internet development and deployment platform, extending Oracle's long-standing technology leadership in the areas of data management, transaction processing and data warehousing to the new medium of the Internet. Built directly inside the database, breakthrough Internet features help companies and developers build Internet-savvy applications that lower costs, enhance customer and supplier interaction, and provide global information access across platforms and across the enterprise.

Oracle8i JVM
Oracle8i JVM is a server side Java engine for the Oracle8i database. It includes a Java Virtual Machine with a native compiler, a CORBA 2.0 ORB, an EJB server, an embedded server side JDBC driver, and a SQLJ translator. The Oracle8i JVM constitutes the heart of Oracle8i's support for Java. Developed by Oracle, the VM is 100% JDK compliant and leverages Oracle8i's multithreaded and highly scalable parallel server architectures with excellent performance on SMP and MPP architectures. It enjoys an advanced memory model for exceptional scalability to thousands of simultaneous connections over the Internet for an entire enterprise.

Some information above was obtained from Oracle’s Website located at


7.2 Netware Server Integration

As Commercial Connect, LLC. moves into a full networking environment, most general applications will reside on network servers. In the current business market place, many third-party systems as well as office automation applications such as E-Mail, word processors, and spreadsheets, will be server based.

In situations with a limited number of application or users, high end PC's can be used as the server platform. This works well in small office environments where a limited number of users are connected to the system. In major facilities many such machines are often employed to handle the large number of users and applications.

In these large environments, it is quickly becoming apparent that the task of maintaining and servicing a large number of critical servers is inefficient, due to the need to maintain large volumes of data, track applications and network licensing, maintain numerous disk drives and system memory on each machine, and many other aspects.

Another critical problem not addressed with PC based servers was the issue of fault tolerance. With a PC system, if memory, disk drives, disk controllers, or any other system component failed, the system crashed ...disconnecting all users until a technician could correct the problem. While the use of techniques such as disk duplexing or mirroring alleviated some of the problem, the networks that used the PC based servers still remained vulnerable.

The concerns and needs of the larger network systems created a new class of network server ...the super server. These new machines possessed the power, fault tolerance, and management features found in the older mainframe computer environment. With these systems in place, network mangers found themselves free of the headaches of managing and maintaining multiple PC systems. Additionally, system growth was handled through the greater data handling capacity and user support (1,000 users per server is common) of the super servers. 

In summation, the scalable high performance PC based network super servers such as the RS/6000 and Netfinity 7600 should meet and exceed all requirements of Commercial Connect, LLC. both now and into the future. With the base capacity, and the ability to expand to support many additional users, applications and data, these servers are the best solution for the network server requirements in the dynamic environment envisioned by Commercial Connect, LLC..


8.0 Enterprise Applications:  Corporate Electronic Mail and Scheduling


With SNMP and the onset of e-commerce, email is a crucial element in today’s Internet business.  Event notifications, notices of sales, pending orders, requests for information and much more are all carried through this single application.  The selection of a suitable productivity application must be based on careful considerations including ease of use, security, stability, reputation and capabilities.  With these and other issues in mind, Commercial Connect, LLC. has chosen Microsoft Exchange 2000 for its email/productivity application

Microsoft Exchange 2000 Server, seamlessly integrated with the Microsoft Windows® 2000 operating system, is designed to meet the messaging and collaboration needs for businesses of all sizes, from small organizations to large distributed enterprises. Exchange 2000 Server incorporates two years of customer feedback for its design. Customers outlined three broad requirements that they want to see in the next generation of their messaging and collaboration infrastructure:

The system proposed for enterprise wide messaging and scheduling system is Microsoft Exchange Server. This system provides the following features:

Worldwide Email Service, Group Calendaring and Scheduling

The multi-user calendar feature will permit various scheduling departments to retrieve and view several calendars side by side on the same screen, while maintaining the confidentiality of each calendar. With the built-in security of the system the local system administrator or the enterprise administrator can specify who has access to view or modify personal calendars. They can schedule meetings by listing attendees and the length of the meeting. Exchange Server will retrieve information from each individual's calendar, allowing you to choose a block of unscheduled time and send out a meeting request.

Task Management

Microsoft Exchange lets you schedule to-do items or tasks, indicate the tasks' priorities and when they should be completed. If a person accepts a to-do item, the task is added to that person's list with the priority you assigned. Users can postpone their responses, or accept, reject, or delegate a scheduling request. If a request is delegated, the request is forwarded to the next user, who has the same option. The original sender will know where a scheduled item was delegated, and when it was delivered, opened, and completed.


Ordered distribution lets a user send a message through a specific group of people one by one. This feature is particularly helpful when you need to have an electronic form signed or approved in a particular order.

Out Box

The Out Box lets the sender view the status of messages they send. The sender will know when messages are delivered, opened and deleted, even if they are deleted without being opened. This feature is helpful when the sender needs to track scheduled tasks or routed forms using ordered distribution. If desired, the sender can also retract unopened messages if they need to modify or delete a message.

Message Management

The system can be personalized to the individual's own taste and work habits. If desired, the user can create any number of folders and subfolders to organize their messages, and store any combination of e-mail messages, scheduled items, appointments, to-do items and notes in any folder. A message can be stored in one folder and linked to other folders.


The rules feature in Exchange Server automatically performs actions on messages depending on certain criteria. For example, the administrator or the individual user can apply a rule that files all messages from a certain person in a folder. Multiple actions can be performed on a single message.

System Administration

Exchange Server 2000 offers a new, fully distributed, active service database architecture. The administrative program -- the front end to the directory services database -- simplifies the setup, configuration, and maintenance of your system regardless of size. Using a star architecture, the central point of administration will be at the data center (or central site for network administration) and local administration will be performed by the local administrators. While the central or (Hub) site will be able to implement changes globally, the local (satellite) site will be able to perform administrative tasks that will be transmitted to the hub where all of the databases will be updated at one time.

Remote Capabilities

Using the Exchange Server via the Web included with the system, users can run the E-mail system from a remote location.

Gateway Support

The following gateways are currently available: X.400, X.25, NGM/MHS, SMTP, Fax/Print, OfficeVisionfVM, Groupwise, cc:Mail, VMS Mail, Message Router, Async, and API. The Async and API gateways are included in the Message Server Pack. All other gateways are available separately. Additionally, these gateways will permit the Commercial Connect, LLC. user to access and send messages to foreign systems such as the Internet, CompuServe, MCI Mail, INS Customer Service, etc.


9.0 Project Implementation


The main foundation of the proposed systems is in place.  A detailed list of completed components and project to be completed follows:



9.1 Project Management


Project Management will be the responsibility of the Chief Information Officer.  Within a two week period he will provide a detailed timeline to complete the project indicating the key personnel needed.




The following individuals on the staff will have key roles in the management of this project:

Chief Information Officer (CIO) - Develops the Project Plan (in coordination with the project manager in the field) and allocates resources to ensure on-schedule completion of the project. Responsible for installation of cable plant, coordination with the Integration, Services, and Network Engineers. Ensures overall project quality assurance and completion of the project documentation.

Senior Network Engineer – Acts as Project Manager. Oversees the installation and configuration of network servers, network operating systems, and user applications. Documents the system configuration as part of the project documentation and provides training to the network managers on network management as it relates to the network operating system. Coordinates for user application training.


·        Ensures that the project is completed on-schedule and in accordance with established standards.

·        Maintains open communications with the CIO to ensure timely resolution of issues relating to any aspect of the project.

·        Enforces on-site documentation standards for the project.

·        Contributes to the development of the Project Plan which defines the tasks and responsibilities for performance of the Statement of Work.

·        Measures and evaluates progress against the Project Plan and resolves deviations the plan.

·        Prepares and submits Weekly Status Reports to the Director of Operations.

·        Administers Project Change Control procedures in coordination with the CIO.

·        Coordinates and manages the technical activities of project personnel.

·        Ensures that the professional environment of the facility is maintained.


9.1.1 Certification Testing


Certification is the testing of the completed network and is generally accomplished in two phases. The first is in conjunction with system activation, and prior to the commencement of LAN usage. This testing phase targets the physical infrastructure and network equipment. The second testing phase will be implemented after the network integration efforts are completed and are designed to ensure systems connectivity. The second testing phase calls for a close coordination between to clearly define the scope and duration of the tests. Occasionally there are circumstances in which the testing process dictates that the network not be in use, at which times the work will be scheduled after business hours if users are actively using the system.

The results of both testing phases will be clearly documented and for review and acceptance.

Phase I

Fiber Optic Backbone Tests

·        Pre-installation testing of the fiber while it is still on the reel will be performed to insure that it was not damaged during shipment. Tests will be accomplished by using an Optical Time Domain Reflectometer (OTDR) and the records will be retained as part of the final system documentation. All OTDR tests will show that no micro bends or other abnormal defects are  present in the fiber prior to installation.

·        OTDR post termination testing of each fiber will be performed. The test results will be submitted as part of the final system "as-built" documentation. All OTDR tests will show that no micro bends or other abnormal defects are present in the fiber.

·        Fiber Cable Power Meter Test: A power meter test will be performed on all fiber cable after termination. An AT&T power meter set will be used to perform the test. This test will be performed at 850 and 1300 run to ensure operation at FDDI specified frequencies in accordance with ANSI X3T9.5 requirements. All results will be documented and inserted into the final documentation package.

UTP Installation Tests

INS will certify that the Enhanced Category 5 horizontal UTP meets or exceeds the proposed EIA/TIA SP-2840 draft specifications for link performance. In order to ensure this compliance, INS will perform the following tests:

·        Cable Length: All installed horizontal UTP wiring will be tested for length using a Time Domain Reflectometer (TDR). All UTP wiring must be validated to be within the 90 meter length specified by the EIA/TIA 568 specifications.

·        Attenuation: All installed UTP wiring will be tested for maximum attenuation at 100 MHz in accordance with the EIA SP-2840 draft specifications for Enhanced Category 5 attenuation link performance of 23.6 dB. For proper results, it is necessary to perform the attenuation tests in a one-way manner.

·        Near End CrosstalkMXT): All installed horizontal UTP wiring will be tested for NEXT from 0.772 MHz to 100 MHz in 200 ICHz increments in accordance with the Underwriters Laboratories LAN Cable Certification Program document. The test results will support that the horizontal UTP wiring does not exceed maximum NEXT in accordance with the specifications (using the formula [ NEXT (test frequency in Mhz) > NEXT (0.772) - 15 Iog10 (test frequency in Mhz / 0.772)]).

·        Electrical Noise: All installed horizontal UTP wiring will be tested for electrical noise. The test results are designed to measure and record both ambient and impulse noise in the low, medium, and high frequency ranges on each UTP cable installed. This test insures that noise from such sources as AC lines, florescent lights, motors, radios, or other co-existing system will not adversely effect system performance.

·        Capacitance: All installed horizontal UTP wiring will be tested for maximum capacitance on each cable pair in accordance with EIA/TIA Enhanced Category 5 specifications of 17pF per foot maximum. This test is performed to ensure that no unusual physical damage or anomalies exist in the horizontal UTP wiring.

·        Characteristic Impedance: All installed horizontal UTP wiring will be tested for characteristic impedance for each cable pair in accordance with EIA/TIA Enhanced Category 5 specifications of 100 ohms +/- 15%. This test will ensure that all punch downs, terminations, and patch cables are in good working order.

·        DC Resistance: All installed horizontal UTP wiring will be tested for DC resistance for each cable pair in accordance with EIA/TIA Enhanced Category 5 specifications. This test will ensure that the installed cable meets or exceeds the specifications detailed in EIA TSB 36.

·        Continuity and Polarity: All installed horizontal UTP wiring will be tested for the continuity and polarity of each cable pair in accordance with EIA/TIA 5688 specifications. This test will ensure that all punch downs, terminations, and patch cables are properly terminated and pinned in the correct sequence as defined by the EIA/TIA 568E specifications.

Phase II - Connectivity Tests

Phase II tests will be designed to test systems connectivity between specified user locations and their respective hosts. We will test lOBase-T connectivity from selected network ports to the host computers.

The number and locations of the test sites will be determined by engineering staff personnel prior to the beginning of the testing phase.

9.1.2 Documentation

A final documentation package will be presented within thirty days following project completion. The final documentation package will consist of a short description of the test performed and the following documents:

1. Data Base identifying each data outlet and wire number.
2. Fiber meter test results.
3. Cable pin-out configuration.
4. UTP test results.
5. Performance Test Results.
6. Connectivity test results.
7. Network hardware configuration
8. Network server and application configuration

D15.2.2  Registry-Registrar model and protocol.

The Registry-Registrar model will abide by the protocol requirements outlined in the IETF Internet specification for gRRP and will follow Section 10 of RFC2026.


It is essential that in order to maintain an orderly reliable internet standards must be in place to provide basic services.  We fully intend to adhere to these standards.  We will provide a similar functioning Registry-Registrar Model that will respond identical to the requests that are in place at Network Solutions/Verisign Registry Services.  We will diverge slightly as we are proposing a heavier registry model with additional information in order to aid in the stability of the internet.  Our model will keep in additional to the current information, additional vital information needed should the registrar go out of business or business cease from unknown reasons.  There will be a need to enhance the RRP for additional commands and information.  All needs will be addressed through IETF and an enhance form of the RRP.


·        Full observation and participation in IETF processes are essential.  Commercial Connect, LLC. will have staff dedicated to keep up with all RFC’s, proposals and standards to ensure that we are consistent to the operation and fast changing need of a stable internet.  In addition security will be of highest priority.  All transactions will take place on secured servers transmitting secured transmissions, virtual private networking and secured DNS to ensure a secure internet system.



D15.2.3 Database Capabilities

Commercial Connect, LLC. will run Oracle iFS utilizing Oracle8i relational database will serve as the data application foundation for a customized Registry system.  Oracle is the world’s leading supplier of software for the Internet and business worlds.  It is the second largest independent software company.  The availability of supporting programs, Internet integration and technicians familiar with Oracle makes it the obvious choice to base a registry service on.


The scalable Oracle server will be allowed up to 30 Gig of storage space. It has the ability to notify on space restrictions, security issues and throughput.  In addition, several security level enhancements have been made to allow for “virtual private database” which will allow for varied security on certain domain name components at the user level.  In addition the database will keep certain chronological data and transactional data to be able to trace the history behind the transactions.


The database will consist of key component files including Registrar Database, Domain Name Database, Client Database, Name Server Database, invoicing, billing operations and reporting,


With over two years experience as an active ICANN accredited CORE Registrar, and with additional experience in the years-long extensive preparation for the role of Registrar, Computer Analytical Systems, Inc. is thoroughly familiar with the Basic Command Protocols, Payload Specifications, Registry rules and procedures and database requirements of the current Shared Registry System (SRS) for the existing .com, .net and org Top Level Domains.  Commercial Connect, LLC. will adhere closely to the current CORE models in implementation of the new TLDs.  The detailed command protocol (CORE-BCP-1) is included as Appendix B.


D15.2.4 Zone File Generation

The Registry will maintain the authoritative zone file for each TLD it sponsors.  There will be separate zone files for each TLD supported.  The Registrar will request a zone file update, it will be submitted to the Registry via RRP to Registrar. Registrar will record such change and at ascertained times not to be less than once every 12 hours will issue zone file updates.


RFCs 1034 and 1035 will be followed.



D15.2.5  Zone File distribution and publication

In order to provide maximum security and efficiency, Commercial Connect, LLC. will locate six name servers (additional can be apportioned should need arise) at diverse locations across the world.  Louisville, KY ,Chicago, IL, Atlanta, GA, Dallas, TX, Indianapolis, IN, and London, UK  would be the initial preferred sites for the Name Servers. 


Systems there will be utilizing the more efficient/stable BIND as well as technologies that are in place to provide for data corruption protection and dynamic updates.  All efforts will be made to ensure that the information being published is consistent in content to the object it is updating. 


D15.2.6  Billing and collection systems

Our billing will be based on an existing billing system utilized for the Registrar services.  It will be incorporated into the Oracle database which will ensure its integrity and security. 


In addition, a secured web presence will be made available to the Registrars to inquire on their account, their status and account history.

Registrars may only apply to resell the TLDs if they are ICANN accredited.  A minor application process will be needed to get vital information on the registrar and verify their ICANN accreditation and financial abilities.  Once accreditation is verified and financial arrangements have been made for payments, and the Registrar has signed all policy agreements, a Registrar will be allowed to register the TLD’s.  There will be a $2000 USD application fee to apply for registering the TLDs in addition each registrar will be billed $1000 per year to remain an active registrar.


We will provide several technical support staff to provide assistance to the new Registrar in getting started reselling the TLDs.  For the most part secured web pages will provide a web based interactive tool to allow the registrar the ability to complete most all transactions.  In addition, the RRP can be followed to accomplish the same tasks.  There will be no software licensing fees associated with registering the new TLD’s.


The accounting system will adhere to a standard double entry system in most of today’s businesses.  There will be security issued to employees based on their job function. 


Deletions will not be allowed.  If mistakes are made, then adjusting entries must be made to correct items with detailed information supplied on the mistake.


With the use of Oracle’s relational database, several pricing structures can occur and at the same time several TLDs can be supported.  The billing system will look at a company for pricing as well as what TLDs they may register and base price on a number of other items if deemed necessary such as quantity of domain names purchased, etc.  At present all TLDs will cost the same to every Registrar.  It is essential that procedures be built in should this change.


Commercial Connect, LLC. will charge $6 per tld to be registered.  This amount must be prepaid by the registrar.  The prepayment will be kept in an escrow account and email notification will be sent once the amount has decreased to a certain amount as designated by that customer.  Payment accepted will be by check or wire transfer.  All banking fees for payment sent are the responsibility of the Registrar.


Registration, Renewals and transfers will act the same as through NSI Registry/Verisign Registry. 



Renewal notices will be the responsibility of each Registrar.  The Registrar may contract with Commercial Connect, LLC. for customized renewal options such as an automatic renewal of one year if the Registrar so desires.


Billing procedures are discussed further in the Business Plan.


D15.2.7  Data Escrow and backup

There will be no need for Data Escrow since the authoritative Whois will be kept at the registry.  This will ensure for a centralized Whois and make updates more efficient and effective.  Since there will be three database servers located worldwide and they will have load balancing and active clustering and automatic failover/failback the physical servers should prove quite reliable.  In addition a daily automatic DLT tape library system will be performed.


D15.2.8  Publicly accessible look up/Whois

Great consideration must be made in regards to the security, integrity and speed of the Whois system.  Because of this, Commercial Connect, LLC. has decided to maintain a centralized Whois service.  It is essential that this system be available at all times, it can not get incorrect information and must be monitored against abuse.  In addition there are several concerns in regards to countries that protect information regarding ownership of domains.


Since the Whois database will be kept at the Registry level almost immediate, real-time updates can be achieved.  This will be the best possible solution to the need for accurate information.


Consistency should also be preserved.  The standardized Whois protocols and functionality will be maintained.


D15.2.9  System Security

The primary data center has a 24 hour 7 day manned support staff.  In addition, there are video surveillance and active alarm system in place with controlled access.


Remote facilities will be controlled by secured remote operations.  These facilities also will have limited access and controlled access.


The Computer Operating System and Network Operating System will have usernames and passwords assigned with careful consideration of functionality assigned to the user.  The job function will dictate the level of security.


In addition the database application will have yet another set of username and security protocols to pass through again with rights assigned through job function.


In addition to the physical staff the systems will be protected by various types of firewall software and hardware that will intelligently record transactions and provide a high level of internet security.  In addition Secured Socket Layer transactions will be processed over the internet.  This allows for data encryption and verification of who a user actually is and only allow them to access database functions assigned to them.


D15.2.10  Peak Capacities

During the initial Sunrise period procedures will be put into place to test the capacitance of the system.  Commercial Connect, LLC. will take requests and force a large upload to test system capacity and speed.  This will be done one month prior to going live.  We will then take that information and apply appropriate measures to ensure that the systems can handle a large influx of requests.


Additional employees can be provided by or CAS-Com Internet Services, Inc. which are sister companies working in the same location during peak times.


D15.2.11  System Reliability

With system redundancy, Clustering, Load balancing and failover/failback services combined with real backups will result in a 99.98% up time. 


D15.2.12  System outage prevention

Several methonds will be employed to ensure that all backup and redundancy systems are in force. 


There are set procedures for technicians to manually verify functionality in addition software such as What’s Up Gold will constantly monitor and page appropriate staff in cases of slow networks or outages.  Since also sells and services equipment, it has replacement parts on site for fast repairs. 


All Software and redundancy is currently operation and has provided up times over the 99.98% with the exception of purposeful testing for over one year.


D15.2.13  System Recovery procedures

Since there will be three servers with clustering operating on them the network will automatically sense a downed server and automatically switch to another system, once that initial system is back on line it will discover the authoritative server is opted and switch back to it.  Otherwise it will cluster and mirror existing and become redundant once more.  In addition Computer Associates’ ArcServe will provide for imaging a drive back to it original backed up state the previous night.


All Backup systems and redundancies are currently being utilized and have proven quite effective.


D15.2.14  Technical and other support

Support for Registrars will be provided via phone support, email and web based self-help.  Internet Users and Registrants will also be allowed to phone support but in most situations they will be referred back to their Registrars unless they are having difficulties with their existing Registrars.


Our Technical Support will be available from 8:00 a.m. EST through 6:00 p.m. EST and we have automated receptionist after hours that will page a technician in case of an emergency for callback within 30 minutes.  This service will be available 24/7.  During regular support hours we can accept calls in English, Spanish, French, Japanese and German.  Once we have established relationships with additional countries we will provide a means of communication and expand our support.


D15.3  Subcontractors

Commercial Connect, LLC. will be doing all of the design, implementation and support of the registry service.  We will be taking key personnel from various existing companies while forming this new joint venture.  Key personnel such as CEO, Jeffrey Smith, CRO, Daniel Kalef and key programmers and technicians have already been placed on retainers and will be joining the LLC when the application is approved.







Name:  Jeffrey S Smith


Title:  President/CEO



Appendix A Hardware Configuration
















Model/Part No.





Cisco Router




Cisco 3600 Modular Router Base Unit




8-port Serial Interface Processor




6-port Ethernet Interface Processor




2-port Ethernet Interface Processor




Redundant Power Supply





Male DTE V.35 Cable 10 Foot




Allied Telesis AUI to RJ45 Transceiver



DeskPorte V.Fast Modem




Serial Cable






Router Installation / Configuration








Coastcom T-1 Channel Bank




24-slot DI-MUX Chassis w/ 120v Pwr. Supply




Synchronous Data Control Unit- 64xN with




v.35 Interface




Tandem T-1 Unit (TTU) -DSX Interface




DB15 to RJ48 cable for connection to




 incoming T-1 jack





DB25M Shelf Data Conn. To V.35 Centron




Female Cable (5 Foot)




Channel Bank Installation / Configuration








Remote Communications Server




3Com Total Control HiperDsp Chassis



Remote Control Concurrent Users




Remote Node Concurrent Users




Fax Server Concurrent Users




Total Chassis Segments



Appendix A
Hardware Configuration













Communications Cabinet



79" Cabinet with lock





79x24x34 enclosure, 19" rack, viewing door, vented roof




and rear door






Ergoform Handle






Pushbutton / Keylock insert




19" Blower, 110v, 2 fans





DK 8 socket 110/115v power strip




M6 Fixing Screws





M6 Captive Nuts




Solderless Ground Lug




Ground Clamp




#6 Insulated Copper Ground Wire

50 ft



3/8" Lug and Anchor




System Switch Box









Corporate Wiring and MDF Installation



Wiring and cabling Per Port




Communications Room Installation/Wiring













24-port Stackable 10 Base-T Managed Hub




Allied Telesis AUI to RJ45 Transceiver


Appendix A
Hardware Configuration









IBM RS / 6000





IBM RS / 6000 Power PC Model F80





(4GB RAM, floppy drive, 2 media bays)




(4MC Slots, integrated SCS12 Adapter)




(36.4GB SCS12 Disk, 12 HH Drive Bays)











8mm Tape Backup(2.3GB)





C10 Serial Port Converter Cable





C10 HH Drive Mounting Kit





Ethernet Adapter





Ethernet 10BaseT Transceiver





Power Display 17" color monitor





Graphics Display Cable





GXT150M 2D Graphics Adapter (all)





101 Keyboard





3 Button Mouse





AIX Media (8mm)






AIX Diagnostics Diskette





AIX 3.2.x (1-2 user) D5 (2xx/C10/41x)




DeskPorte V.Fast Modem









Additional Servers






Netfinity 7600 - Web Server





Netfinity 7600 - Name Server





Netfinity 7600 - Backup Server





Netfinity 7600 - Test Server
















Intellistation Mpro 2D














Network Management Applications




Ciscoworks 2.1 for Netview for AIX





Ciscoworks Smartnet (1 year extended)



Appendix A
Hardware Configuration




Network Management





IBM Intellistation MPro 933 MH


















17"SVGA Monitor, .288mm





APC Smart UPS 600






Desk Porte V.Fast Modem





Network Management System Installation























Network Management Applications











LANDesk Openview V1.51





Remote Access Software


























Databse Environment





Oracle 8iv







Oracle Applications Server


























Windows 2000 Advanced Server




Windows 2000 Advanced Server





Client Licenses





















Installation / Configuration Includes:




*Workstation, modem, UPS installation




*Intel LANDesk manager on server and Network Management Station




*Netware remote console configuration




*Network archive software configuration


Appendix A
Hardware Configuration











Remote Offices





Netfinity 7600 - Name Server





Netfinity 7600 - Redundant DB Server





APC Smart UPS 600





Cisco 2632





24-slot DI-MUX Chassis w/ 120v Pwr. Supply





Synchronous Data Control Unit- 64xN with




v.35 Interface





Tandem T-1 Unit (TTU) -DSX Interface




DB15 to RJ48 cable for connection to




 incoming T-1 jack






DB25M Shelf Data Conn. To V.35 Centron




Female Cable (5 Foot)





Channel Bank Installation / Configuration




SuperStack II 3300





Intellistation Mpro 2D




Appendix B  CORE BCP-1


Rick H. Wesson

October 19, 1999 Version 0.2


This BCP is designed to give a general overview of the current state of the art in CORE Registration Practices. This document describes the processes necessary to complete successful registrations of Contact, Host, and Domain objects in the CORE Shared Registry System. This is a work in progress it is not complete.

1. Overview

This Document describes 3 main objects used in CORE's SRS. The Contact, NameServer and Domain objects are described at length with example SRS request to process Create, Modify, Delete and Inquiry requests.

1.1 Definitions



(see Registrar)


The separator of SLDs from TLDs, commonly known as a period.


Fully Qualified Domain Name


A unique identifier in the CORE SRS. Each handle is prefixed by 'CORE-' handles are created for Contacts, and NameServers, Domains uniquely reference themselves by their TLD and SLD combination.


an IPv4 address in the form of where xxx is a number between 0 and 255 inclusive.


Network Solutions


Responsible Person


CORE Member Company


Second Level Domain, the part following the TLD up until the next DOT '.'

Appendix B




Top Level Domain (eg. .com .net .org)


A fully qualified DNS domain that contains DNS information (this is not a good definition look at BUG)

1.2 Error Codes

Errors greater than (>) 8000 are errors from the NSI SRS, errors less than 8000 are from the CORE SRS.

2. Contact Objects

Contacts are objects in CORE's SRS and requests to create/modify/delete them are not forwarded to NSI. Contacts are used to represent the Responsible Person (RP) or group that is responsible in some way for a domain and/or NameServer.

Contact objects are owned by the registrar that the contact is created by. Contacts can not be transfered to other registrars. A contact can only be updated by the registrar that owns it, however contacts can be referenced by any registrar, see Contact Permissions.

2.1 Attributes



create contact


A printable string (may include whitespace). The first name of the contact. This field is not mandatory. [ a-z0-9._-]+


A printable string (may include whitespace). The last name of the contact. This field is mandatory. [ a-z0-9._-]+


A printable string (may include whitespace). The organization to which the contact belongs. This field is optional. (In particular, it is clearly inapplicable to the nominative domain.) [ &,+a-z0-9._-]+


Appendix B




A printable string (may include whitespace). The contacts title. This field is optional. [ a-z0-9._-]+












All of these fields are printable strings (may include whitespace). These contain the contacts postal address information. No checking is performed to ensure correctness or completeness of the address; specification of an accurate address is strongly encouraged, for obvious reasons. In particular, unspecified country fields may not be assumed to be the United States. All of these fields are optional.


A printable string. The contacts email address. This field is mandatory.


A printable string (may include whitespace). The contact's international fax number. No checking will be performed to ensure its validity. Specification of a complete telephone number, including country code, is strongly encouraged; telephone numbers may not be assumed to be in the United States. This field is optional.


A printable string (may include whitespace). The contact's international telephone number. No checking will be performed to ensure its validity. Specification of a complete telephone number, including country code, is strongly encouraged; telephone numbers may not be assumed to be in the United States. This field is optional.


[ YN]


Appendix B


Types of Contacts 


The owner contact is a special contact within a domain object. the owner_c "owns" the domain. If this contact is updated, all domains which point to this owner are changed.


The admin_c is the administrative contact for the domain.


The tech_c is the technical contact for a domain


The Zone contact is the contact responsible for the NameServer object.

Contact creation is important because all other objects contained in the CORE SRS reference contact objects via their unique Handle. The registrar should record the contact's handle for subsequent use.








Appendix B

2.2 Example Contact Requests

Create Contact




request-type:create contact

address-1:Sample Street 12345

address-2:Rathausufer 16



fax:+49 211 8676710


lname:Dummy Lastname

organization:Dummy Organization

phone:+49 211 123456788






Delete Contact

There is no 'Delete Contact'


Appendix B



Modify Contact

To Modify a contact, include a 'handle: <contact handle> attribute and the contents of the contact will be replaced. this operation is only available to the registrar that 'owns' the contact.





request-type:modify contact

address-1:Sample Street 12345

address-2:Rathausufer 16



fax:+49 211 8676710




lname:Dummy Lastname

organization:Dummy Organization

phone:+49 211 123456788






Appendix B


Inquire Contact




request-type:inquire contact



Currently the 'Inquire Contact' command only supports looking up contacts via a handle. Use WHOIS to find a contact by name or e-mail address.

3. Name Server (Hosts) Objects

Name Servers are computers that run a process to service DNS queries. The primary function of NameServer is to resolve requests of a name to an IP Address. All Hosts in the CORE SRS have an associated Zone Contact. The Zone contact is the technical administrator responsible for managing the machine(s) responsible for servicing DNS queries for a specific Zone.

3.1 Attributes



create ns


A FQDN, this attribute is required.


An IPv4 Address (dotted quad) in the form of, this attribute is required


The handle of the Responsible Person to associate with this NameServer, this attribute is required. This contact is know as the 'zone contact'


this creates the NameServer only in CORE's database, not in NSI. this attribute is useful for working around several bugs in the RRP protocol version 1.0.4

Appendix B

3.2 Creating NameServer Objects

When a CORE Registrar attempts to register a new NameServer the Registrar must first check to ensure the following are true, or the create request will fail.


  1. The Server is not already registered by another registrar. this is performed by issuing a 'inquire ns' request.
  2. That the NameServer is not already registered within the registrars own database.
  3. The registrar has a correct, and valid Contact Handle for the new NameServer.
  4. The NameServer's FQDN and IP-Address are not already in DNS.
  5. The NameServer's IP address is not listed in the output of the following command

whois -h IANA


  1. Note: there are no more implicit contact creates, the registrar must first lookup to see if there is an appropriate contact already registered within CORE's system and that contact is owned by the registrar.

A potential times aver is to look the name and or the IP address of the new NameServer up in DNS, it the server is not already in the registrars own database. if the name and ip address can not be resolved it is more likely that the SRS will successfully register the NameServer.

Checking availability.

Please check to see that the name server is available before attempting to use it by issuing a status command with the FQDN of the name server in the handle field of the request. An authorization denied error will be raised when a name server is available in NSI's database but is not currently allocate in CORE's. This problem will be rectified in a future release for the RRP protocol.

NameServers in ccTLD name spaces.

To make delegations to Name Servers that are not in gTLD (.com, .net, .org) and the NameServer does not already exists in CORE's databases, create the name server with out an IP address. Creating NameServers with out IP Addresses is allowed if the NameServer exits in a ccTLD, please note that no checks are made to establish the validity of the ccTLD or that the NameServer actually exists in the ccTLD's name space.

Appendix B


Illegal IPv4 Addresses

There is a list of Illegal IPv4 addresses for NameServers maintained by IANA. Registrars should check to make sure that the NameServer they wish to create or modify is not attempting to use any of these addressed. The list of illegal addresses can be obtained by issuing the following command to the whois server located at ''


whois -h IANA


NameServers ending in .COM, .NET, or .ORG

To verify that a NameServer is not already in the database first see if a forward and reverse are in DNS. Query [a-j], if the IP-Address and/or FQDN are resolved then the NameServer is already in NSI's database.

NameServers ending in ccTLD's

If you need to reference a NameServer that is in a CCTLD domain (.de, .uk, .au) Create a NameServer with no IP-Address, this will create the appropriate dedications in NSI's database.

Special Circumstances

If a NameServer is already created by another register in NSI's database, a 'inquire ns' request will fail due to an 'Access Denied' error generated when the CORE SRS issues the request to NSI. This is a bug in NSI's software, a fix has been requested. To work around this problem create the name server setting the 'local-only' attribute to one (1.) This will create the NameServer object in CORE's Database and allow anyone to link to it using the newly created handle.

If you need to create a NameServer that is under a new domain, a domain that does not currently exists, the following is the procedure:


  1. Create the Domain with out any NameServers.
  2. Create the NameServers
  3. Modify the Domain, adding the new NameServers.







Appendix B

3.3 Example NS Requests

Create NS





request-type:create ns

local-only:  0





Inquire NS


registrar-id: CORE-100

payload-version: 1.0

transaction-id: registrars-internal-transaction-id

request-type: inquire ns



The 'ns-handle' attribute can contain any of the following to query.


Delete NS

Currently there is no method to delete a NameServer.


Appendix B


Modify NS





request-type:modify ns

ns-handle: CORE-10034-NS



4. Domain Objects

Domains are the heart of the CORE SRS. The domain Object contains three contacts, an administrative contact, a technical contact and an owner contact. The Domain Object also contains at least 2 NameServers, a primary and a secondary. Domains can be created in several ways to work around using the SRS to manage domains in NSI's SRS. There are several flavors of Domain Creation due to the way NameServers interact with Domains.

4.1 Attributes



create domain


This field specifies the top-level domain in which the domain should be created. All values of this field will be stored and treated as lower case. This field must match one of the top-level domains being managed by this SRS; otherwise, the operation fails. This field is mandatory.


A valid second-level domain name, as defined in RFC-1034 et seq. This field is not case-sensitive, and will be mapped to lower case for storage in the database. If both the TLD and SLD fields match those attributes of a pre-existing domain record, the operation will fail. This field is mandatory.


Appendix B



Status can be one of the following, this field is mandatory. 



The name of the Entity or Organization registering the domain. This field is mandatory.


The handle of the contact that will 'own' the Domain. This field is mandatory.


The handle of the Administrative contact for the domain. This attribute is mandatory.


The handle of the Technical Contact for the Domain. This attribute is mandatory.


The handle of the Zone Contact for the Domain.

Each domain has no fewer than two and no more than twelve host records associated with it. These hosts are expected to act as the domain's NameServers. This protocol supports both the use of pre-existing hosts by handle and the implicit creation of hosts by the specification of host creation information in a domain creation operation. The NameServer for a domain are numbered sequentially, starting from 1. Each of the NameServer for the domain may be a pre-existing host, referenced by handle



The handle of the Primary NameServer for the domain.


The handle of the Secondary NameServer for the domain.


Additional Secondary NameServers

4.2 Creating Domains with New NameServers

When Creating new Domains first check to see if the Domain is not already allocated in NSI's database by issuing a 'inquire domain' with the "check" attribute set to one (1.)

Appendix B

4.3 Sample Requests

Create Domain with NameServers

Create Domain w/o Name Servers





request-type:create domain




organization:Dummy Organization


tld: com







Appendix B


Inquire Domain

Inquire for Availability

Before creating new domains it is wise to check with the SRS at NSI to see if the domain is available. The 'inquire domain' request has been extended to support such a check, by adding the attribute 'check: 1' to the request. This request will inspect the current database at NSI to see if the domain is allocated within the SRS at NSI.





request-type:inquire domain

check: 1





Modify Domain




request-type:modify domain




organization:Dummy Organization









Appendix B


Delete Domain

registrar-id:CORE-100 payload-version:1.0 transaction-id:registrars-internal-transaction-id

request-type:delete domain sld:example tld:com

5. CORE Registrar Transfer Policy for com/net/org domains

This section describes procedures and rules related to transferring a domain between registrars without changing the name or address of the registrant. Separate documents describe the rules governing changes to the registrant name or address and transfers between CORE members.

5.1 CORE is the Gaining Registrar

Written Instructions from Registrant

The CORE member obtains written instructions on paper for the domain to be transferred to CORE by the respective CORE member. An authorization message on e-mail is not sufficient. The authorization must be on the registrants company letterhead if it can reasonably be expected that the company normally uses letterhead and must be signed by an authorized person on behalf of the registrant. The admin contact as per the whois is automatically considered to be an authorized signatory. The signatory's name must be also be printed next to the signature. The name of the company on the letterhead must match the name of the company in the whois. A template for a valid registrar transfer instruction attached in Appendix A. A single transfer instruction can be used for several domains, however, all domains must be listed in the document or unequivocally referred to.

Obligation to keep the registrant document on file.

The CORE member must keep the transfer request on file at least until the next renewal.

Initiate SRS Transfer Request

Appendix B


After making sure it is in possession of proper documentation, the CORE member initiates a registrar transfer-request on the CORE SRS. The transaction will cause a two-year registration fee to be deducted from the CORE member's RCU account. The CORE SRS automatically forwards that request to the com/net/org registry. The CORE SRS can be configured to inhibit the transfer request command for a given member. The CORE SRS support team or the CORE Secretariat can set the transfer request to forbidden for

any given member in case of danger or urgency that could affect CORE or its reputation, or upon instruction by the Executive Committee.

Random checks by CORE Secretariat

The CORE Secretariat performs random checks to ensure that proper documentation has been provided and kept by the registrant. If a member receives a request from the Secretariat to provide the documents while the transfer request is pending, these must be sent by fax within two working days. The Secretariat may also request the documents after the transfer request has been completed, in which case the member must fax the document within 5 working days.

Information on Pending Transfers 

  1. As soon as the transfer request has been initiated, NSIregistry sends a message to the gaining and the losing registrar. When CORE as the gaining registrar receives a notice with respect to a transfer request, this message is forwarded to the appropriate CM (email address recorded as reg-admin-c in the CORE SRS).
  2. In order to complete the request, or in order to find out if the transfer request has been acknowledged (ACK) by loosing registrar, the CORE member sends a transfer-complete-request (positive) to CORE-SRS. If that request is refused, the transfer has not yet been allowed by the loosing registrar who has 5 days to respond. Please do not send repetitive transfer-complete-requests in short intervals as once per day should be enough.
  3. If CORE receives a confirmation from NSI-RegistryTransfer or from the losing registrar, this message is forwarded to the respective CORE member (same address as in

Rejection of Transfer Request by Loosing Registrar

If the transfer request is rejected, CORE will get an email from the loosing registrar explaining why. That email will be forwarded to the CORE member (same address as in The CORE member then has to send a transfer-complete-request (negative) to CORE-SRS so that the RCU charged upon initiating the transfer request can be credited back.

Appendix B


Completion of Transfer 

  1. As soon as a transfer-complete-request (positive) is issued by the CORE member after the transfer has been approved by the loosing registrar, the CORE SRS will copy the domain-data from NSI-RegistrY and add a new domain at CORE-SRS. If the CORE member fails to complete the transfer with a transfer-complete-request (positive), the RegistrY may show the partial old data while CORE would not recognize the domain in whois queries. It is the responsibility of the CORE member to make sure that no transfer requests remain incomplete.
  2. The CORE member has to update the name server entries as appropriate using the modify-domain command.

Undocumented Authorization for Transfer Request or other Inappropriate Use 

  1. Duty to Inform and take Immediate Action to Limit Damage If a CORE member discovers that it has issued a transfer request has been issued without proper documentation (e.g. because of an error), it has to inform the CORE secretariat immediately by email. It also has the responsibility to take whatever immediate action necessary to avoid prejudice for the domain name holder or CORE, e.g. to reverse the transfer request if it is still pending and to inform affected parties of the issue.
  2. Reporting and Penalties Cases of unauthorized or undocumented use of the transfer request will be reported to the Executive Committee. If, within the specified deadlines, a member fails to produce copies of valid customer instructions upon request by the secretariat, it is deemed to have used the transfer request without proper documentation. In such a case, a penalty fee of USD 200 per case is levied addition to legal regress that CORE may take against the member. If three or more cases arise within six months for a given member, the member's ability to initiate the transfer requests is suspended two months or until such time, as the Executive Committee is satisfied that the member has put appropriate internal procedures in place.

5.2 CORE is the Loosing Registrar

Message from NSIregistry

CORE is informed of the transfer request initiated by another registrar through and email message from NSIregistry. This email message received by an email robot at the CORE SRS which will identify the appropriate CORE member and forward the message to the reg-admin-c address.

Appendix B


Message from CORE to Domain Holder

At the same time as it forward the NSIregistry message to the CORE member, CORE generates an email to the to owner-c of the domain as registered in the CORE whois database.

Acceptance ACE/NAK

The CORE member must either accept (ACK) or reject (NACK) the transfer request using the CORE-SRS message. If no response is provided within five calendar days, the NSIregistry system automatically assumes that the loosing registrar (CORE in this case) transfer has been accepted by CORE, and CORE automatically assumes that the CORE member has approved the transfer. CORE can require a CORE member to reject a transfer request, or reject it directly, if the domain is subject to litigation or if the CORE dispute policy has been invoked.

Rejection by CORE Member

If the CORE member rejects that transfer, it has to send a message to the CORE secretariat explaining the reasons. This message will be forwarded to the gaining registrar. The CORE member must also initiate the transfer-request-NAK on the CORE SRS, which then automatically sends the NACK to the NSIregistry system. A transfer should be rejected if any of the following conditions apply: bankruptcy of registrant; existence of a dispute concerning the domain name; litigation involving the domain name; refusal by domain holder or contradictory instructions from various contacts associated with the domain.

Acceptance by CORE member

If the CORE accepts the transfer (for which purpose it should consult the domain holder), it must also initiate the transfer-request-ACK on the CORE SRS, which then automatically sends the ACK to the NSIregistry system.

Appendix B

5.3 Transfer Requests

New Attributes for Transfers

There are several new attributes for managing transfers.









Initiate a Transfer






request-type:transfer domain






Appendix B


Complete a Transfer






request-type:complete transfer






organization:Dummy Organization








Appendix B


6. Appendix - A Error Codes



request was successful


it-id not found in request


command is not implemented yet


errors between -3 and -99 are internal errors which should not occur.


empty request


transaction id not found


registrar id not found or invalid


request-type not found or invalid


no permission to manage this request


field payload version not found or invalid


not enough credits for this request


Duplicate Field identifier in request


No registrar-contact record found for registrar-id and PGP keyid



No registrar-handle record found or registrar-handle is invalid



value not found or invalid


mandatory field not found


field value exceeds maximum field length


mandatory field can not be empty on in modification request.


Appendix B



invalid toplevel domain name for this srs


missing field for ns creation


order for nameservers must be ascending


field value is not a valid Timestamp Format:YYYYMMDD [hh:mm:ss]



ns-handles must be unique for each domain


ns-domain-name is already registered.


ns-ip-address is already registered.


you must be the owner of the contact to create a reference to it.


you must be the owner of the ns to create a reference to it.


ns cant be deleted because of references to existing domains.


contact cant be deleted because of references to existing objects.


domain [$dn] cant be deleted cause of existing NS for that domain.


NS already registered at NSI, use local-only flag to create link in SRS.


ns-ip-address missing in create ns Request for com/net/org TLD.


registrar not owner of this contact


illegal flag


domain name is already registered.


not owner of this domain


not owner of this domain, permission denied


this domain may not be modified, denied

Appendix B



time to cancel domain registration has expired, too late now ... :-(


auth_key could not be added, maybe wrong format or invalid


PGP-KeyID is already in use for that registrar


illegal status value for modify registrar request


reg-admin fields not completely described (contact,auth-type,auth-key)


order of agent-contacts must be ascending


fields not completely described (contact,auth-type,auth-key)


No request found until now ...


illegal query request, none of submitted-since, submitted-before, completed-since, completed-before found


illegal query request, field request-state:[pending in-process succeeded failed] not found


illegal query request, Value for submitted-since, submitted-before, completed-since, completed-before is illegal date or time


ns-handle not found or invalid


not owner of this handle, permission denied


NS neither found at NSI nor at SRS.


NS found at NSI BUT NOT at SRS, use create ns request with local-only flag for using.


Domain not found in SRS


Domain is not scheduled for transfer


not owner of this transfer, permission denied


Domain is already in the CORE SRS

Appendix B



Transfer for that domain is already in progress


Transfer is unimplemented yet, domain is still owned by NSI


Could not perform transfer from nsi cause domain is not owned by NSI


Domain is already at cores database use req-core to transfer


Domain is not ready for transfer to core cause loosing registrar did not ACKs this transfer


illegal action only [req-nsi] is allowed


Could not perform transfer from CORE cause domain is not owned by CORE


Owner of the domain has sent NACK to your request


You need an registrar-admin-contact with a valid responsible email address to do this request


Ownership of Domain could not be changed until policy rules for this are clear

7. Document History





Added Transfer section on com/net/org transfers.


Added Appendix A-Error Codes