Return to Index

2. Connecting to JANET


>>

JANET is funded by public money and was established to serve the requirements of the education and research community in the UK. As such, there are rules about who can connect to the network. Under the connection policy set by JISC, three types of connection are permitted: Primary, Sponsored and Proxy. This policy can be found at:

/documents/publications/policy/connection-policy.pdf

Further information on both Sponsored and Proxy connections, along with a link to the current tariffs and terms and conditions for each of the two licence types, can be found at:

/support/connections/types-of-connection.html

and in Section 9 of this manual.

Another type of connection, Interconnect, is also available.

Primary Connections

All FE and HE organisations in the UK are entitled to a Primary Connection to JANET. Research Council establishments may choose to have a Primary, Sponsored or Proxy Connection. Primary Connections provide access to the full range of network services and support at levels specified in the SLA between JISC and JANET(UK). The SLA can be found at:
/support/publications/policy-documents/service-level-agreements.html

Other organisations may connect to JANET, provided they fulfil the eligibility requirements detailed in the JANET Connection Policy.

New Connections

Overview of the Connection Process

The connection process is complex and involves many different parties at JANET(UK), the JANET NOC, the RNOs, the connection point on the network and, in the case of FE and specialist colleges, JISC RSCs. The main point of contact during this process is the JANET Service Desk. The following paragraphs provide a brief overview of the connection process, which is more fully described at:
/support/connections/types-of-connection.html

A contract in the form of a declaration letter will be sent to each organisation requiring a connection, along with login details for completing the web-based JCUR. A comprehensive information pack is also provided, including a leaflet about the process.

The completed JCUR is submitted online and the signed declaration returned to the JANET Service Desk. Since the JISC RSCs play an important role in assisting with the connection of FE and specialist colleges, these organisations should enlist their help in completing the JCUR. All other organisations should contact the JANET Service Desk for advice and assistance.

In signing up to JANET, an organisation is also signing up to the Terms and Conditions for provision of a JANET service. These can be found at:
/documents/publications/policy/service-terms.pdf

The connection process is illustrated by this flowchart:

connection process flowchart

The Connection Process

As part of the connection process each organisation is assigned IP addresses from the JANET address range and a domain name under one of the .uk domains, at no charge (for further information see Sections 3 and 4 of this manual). The JANET Service Desk provides customers with information about the delivery of their circuit and deals with any queries that arise.

In the case of FE and specialist colleges and PCDL centres, the JISC RSCs will assist by providing technical advice on setting up a LAN and configuring the site router attached to the access circuit. The staff at the RNO also have a role to play in setting up the connection and bringing it into service. The JISC RSCs will liaise with the relevant contacts at the RNO and JANET(UK). All other organisations should contact the JANET Service Desk if they are experiencing problems with setting up their connection to JANET.

Making a Connection Ready for Use

A connection is considered to be ready for use after:

  • the circuit has been delivered
  • IP addresses have been assigned
  • all the cabling from the router to the NTU at both the connecting organisation and RNO are in place
  • the organisation's router has been configured
  • the backbone routing is in place
  • a new domain name, if required, has been approved and delegated, and the customer has supplied the nameserver names and IP addresses.

However, it is recognised that the customer may not be using the circuit at this point if there are still unresolved issues or testing is required. The JANET Service Desk will therefore contact the customer and ask for confirmation that the connection is in use. Once this is received, a date is agreed for invoicing purposes (for those organisations that pay for connection to JANET).

Once the circuit has been delivered, the JANET Service Desk sends a Fault Reporting letter to the technical and management contacts at the organisation which provides information about the fault reporting process and includes details of the user name and password for the Netsight traffic monitoring system. Fault reporting is covered in more detail in Section 1 of this manual and traffic monitoring is described in Appendix 9.

If the organisation is required to pay for the connection, an invoice for the charges agreed at the beginning of the process is sent after the JANET Service Desk has checked that the customer is satisfied with the connection.

Further information about DNS, IP addresses, routers and e-mail is available in more detail elsewhere in this manual.

Multihoming

All organisations connecting to JANET must discuss any plans to retain or install an additional Internet connection through a commercial ISP with JANET(UK). There are a number of implications and technical issues associated with multi-homing arrangements of which an organisation should be fully aware before an agreement is made with another ISP. JANET customers rarely require this type of arrangement and JANET(UK) will make a charge for the increased amount of central administration and technical effort required (e.g. effective filters, aggregation rules) if a multihoming facility is provided.

Please contact the JANET Service Desk for further information.

If an organisation connecting to JANET does not wish to set up a web server, it may be permitted to maintain an existing domain name and web site through a commercial ISP, subject to the preceding provisos about multihoming. FE and specialist colleges may also approach their JISC RSC for advice. All other customers should contact the JANET Service Desk.

Responsibilities of JANET-Connected Organisations

Once a site is connected to JANET it is expected to take responsibility for the following:

  • ensuring that users accessing JANET through the organisation's connection are aware of the JANET AUP and Security Policy
  • providing a secure environment for the JANET equipment installed on site
  • providing technical staff with access to the JANET equipment on site
  • monitoring the performance of its connection and reporting suspected faults promptly through the agreed channels
  • providing assistance to JANET(UK) and law enforcement agencies in tracking down criminal activity
  • appointing listed contacts (and where possible, deputies) for liaison functions and advising the JANET Service Desk when these change.

Acceptable Use of the Network

All organisations connected to JANET are subject to the JANET AUP. This permits JANET to be used for any purpose that is legal, that is socially acceptable to the community JANET serves, and that does not cause degradation of the performance of the network beyond that which might reasonably be expected. All use of the network does, of course, have an impact on performance; the intent is to prevent reckless or inconsiderate activities by users at one organisation causing inconvenience to others. It is important that all users of the network are aware of the AUP. Connected organisations are therefore encouraged to set up a local AUP and require users to sign up to it. Some pointers on how to set up an AUP are provided in Section 9.

Further information about the JANET AUP is provided in Section 9 and at:
/documents/publications/policy/aup.pdf

Recording Essential Information

It is recommended that all organisations maintain a record of information that is essential to running their JANET connection. The Record of Network Information and Contacts form at Appendix 3 can be used to record information such as IP addresses and domain names. This record will not only be a quick reference source for the member of staff who is responsible for the day-to-day running of the site network, but will also provide vital background information for new or temporary staff.

Contacts at JANET-Connected Organisations

The JANET Service Desk should be advised of any changes to site contact names or addresses. JANET(UK) cannot ensure that important information about the network reaches each organisation if contact details are not kept up to date. For example, changes to the fault reporting information may not reach management and operational/technical contacts, or information about security threats might not be passed to the security contact.

The JANET Service Desk sends JANET customers a Contacts form to amend each year but ideally sites should provide details of changes as they occur. Customers may wish to consider using generic e-mail addresses for the roles, e.g. technical@customer.ac.uk.

Responsibilities of JANET Contacts

At least one named contact must be provided for the technical, management and security roles, even if the same person is covering each one. The following notes explain what is generally expected of each contact.

Management Contact

The management contact must be able to make decisions relating to, and have the authority to contract for, the JANET connection. This contact is also required to sign the declaration of compliance with the JANET AUP and Security Policy (the declaration letter). JANET(UK) usually passes this contact's details to RIPE, the Internet registry for Europe, as the 'owner' of the IP addresses that are being requested, because this is normally the person in overall charge of IP address assignment for the organisation. However, you can specify an alternative RIPE contact on the JCUR if this is not appropriate. The management contact will normally be added to the mailing list for JANET News and similar publications, and to e-mail lists for news and support items.

Technical Contact

The technical contact is usually responsible for day-to-day decision making on technical issues concerning the organisation's network and the JANET connection. This contact will be added to the mailing list for JANET News and similar publications, and to e-mail lists for news and support items. The name of this contact will normally be passed to RIPE, unless you provide an alternative contact on the JCUR.

Computer Security Contact

The JANET Security Policy requires organisations with Primary Connections to nominate one or more people to be the first point of contact in dealing with any security incident that affects the organisation. The nominated contact is expected to be someone with technical knowledge and also with management authority since they may be asked to disconnect a computer from the network as a matter of urgency. Since it may be necessary to speak to a security contact at short notice, organisations may wish to nominate more than one person. However, in these circumstances they are expected to share information about current incidents. Ideally, an out-of-hours telephone number should be provided for these contacts.

When a message relating to an incident is sent, it is important that the security contact acknowledges that it has been received and that the problem is being investigated. If JANET CSIRT does not hear from the security contact that progress is being made to contain and resolve the incident then they are likely to escalate the problem through management to protect the operation of the network. The security contact will also receive general security information from JANET CSIRT relating to the prevention of security incidents. The contact is expected to pass these to appropriate people within their organisation and ensure that appropriate preventive action is taken.

Security contacts are also responsible for the activities of any Sponsored and Proxy Connections hosted by their organisation, and need to ensure that they are able to communicate quickly with those sites in case of problems. Security contacts are added to the UK Security JISCmail list and the mailing list for JANET News. Names and phone numbers of security contacts may also be given to law enforcement agencies if their investigations involve a JANET site.

Out-of-hours Contact

Technical, operational or security problems may arise outside normal working hours. It is therefore essential that the out-of-hours contact is available and has sufficient authority to take the appropriate action when such problems occur, such as JANET CSIRT needing to make an organisation aware of a security threat. If it is not possible to contact an organisation when necessary then JANET(UK) will take whatever action is needed to protect the JANET network, even if this involves disrupting the service to an individual organisation.

Upgrading a JANET Connection

All enquiries about upgrading a Primary Connection (irrespective of the method of connection) must be directed to the JANET Service Desk. They will be able to advise on the procedure and funding arrangements for the upgrade. Note that the cost of the upgrade might be the responsibility of the site requesting the increase in bandwidth. In these instances the JANET Service Desk can also provide details of the tariff that applies.

Overview of the Process

The upgrade procedure has many similarities with the standard connection process. In each case a formal written request for an upgrade should be sent by e-mail to the JANET Service Desk. The JANET Service Desk will acknowledge the enquiry, and confirm the arrangements and, if appropriate, the charges. Some upgrades require the installation of a new circuit whereas others can be achieved by the circuit supplier making a few adjustments to the existing access circuit. The organisation will be asked to confirm acceptance of the offer by e-mail and will also be required to complete the appropriate paperwork.

The JANET Service Desk advises the nominated installation contact of the progress of the order at each stage of the upgrade process and deals with any queries. When the upgrade is complete, steps will be taken to cancel the redundant circuit (if appropriate). The customer is then sent an invoice for the cost of the upgrade, if a charge is to be made.

Moving a JANET Access Link

If it becomes necessary for a customer to relocate the equipment connected to its access circuit to another building, or to another part of the building in which it is housed, the JANET Service Desk must be advised. In many cases the access circuit is leased by JANET(UK) and the supplier will not take any action unless the arrangements for the relocation are made through JANET(UK). If there is no record of who leases the access circuit, the customer should contact the JANET Service Desk for clarification.

The customer will be required to meet the charges levied by the circuit supplier, if the move is made at the customer's request. In these circumstances the JANET Service Desk will obtain a quote for the cost of the work and ask the customer to accept responsibility for the charges in writing, or by e-mail, before the work is carried out.

Disconnection from JANET

An organisation may cancel its connection to JANET at any stage. However, if the notice of cancellation is received during the first year of service, a charge may be made equal to the residual rental (from the circuit supplier) of the access circuit for the remainder of the year, plus a charge to cover administrative costs. After a year, subscription may be cancelled upon two months' notice being given. Notice of cancellation must be made in writing to the JANET Service Desk on the organisation's headed paper, or by e-mail to connect@ja.net.

The letter must be signed by, or the e-mail must come from, the management contact.

The organisation cancelling the connection must also make arrangements to return the IP addresses originally assigned from the JANET allocation, at the time of disconnection. All queries regarding the return of IP addresses should be sent to:
ipaddress@ja.net

Sponsored Connections

Organisations with a Primary Connection to JANET and JANET RNOs may host third-party connections under the sponsored licensing scheme. Note however that hosts may only connect organisations that meet the eligibility requirements laid out in the JANET Connection Policy and the arrangements must be agreed with JANET(UK). Sponsored Connections do not receive any of the JANET services besides the IP service and are not subject to the SLA or supported by JANET(UK). Organisations with Sponsored Connections cannot offer further Sponsored, Proxy or Interconnect Connections.

The JANET Connection Policy may be found at:
/documents/publications/policy/connection-policy.pdf

Hosting a Sponsored Connection

An organisation with a Primary Connection to JANET is entitled to 'sell' part of its bandwidth, under licence, to provide a network connection for a third party with whom it has a close working relationship, e.g. a local school. The only proviso is that the activities of the third party must support the organisation's teaching, learning, research or business aims. The benefits that can be offered include:

  • full Internet access
  • e-mail
  • mailing list facility
  • web page on the host's server
  • Usenet News Service (subject to the host's agreement)
  • local support
  • one free domain name registration under .uk.

In hosting a Sponsored Connection, care must be taken that there is no cross subsidy of the use of the JANET backbone.

The final decision as to whether a Sponsored Connection should be offered rests with the potential host, unless there is pressure on the amount of available bandwidth when JANET(UK) or the RNO may reject the application. The connection will be for an individual organisation, or possibly for only a certain part of that organisation (e.g. the research laboratory network of a large company may be eligible for a Sponsored Connection, whereas the rest of the company would not). Please note that this means that a science or technology park cannot be covered by a single licence. In such a case, if multiple organisations on a science or technology park were eligible to connect to JANET then the sponsoring organisation would need to take out a Sponsored Connection licence for each eligible organisation.

Responsibilities of the Host

The host site is expected to manage and support the Sponsored Connection. The level of support provided and any associated charges should be agreed with the third party before the connection is set up. Organisations that are new to hosting should contact the JANET Technical Administration Group for assistance if practical advice is required about the arrangements.

The host site also takes on the responsibilities of a network operator when it agrees to act as a host, and must therefore ensure that the third party is aware of and agrees to abide by the JANET AUP and Security Policy.

It is recommended that an SLA is set up between the host and sponsored site once the terms under which the connection is to be offered have been agreed.

Applying for a Sponsored Connection Licence

Once a primary site or RNO has decided to host a Sponsored Connection, the operational/technical or management contact should contact the JANET Technical Administration Group for a copy of the licence application form, or download one from Appendix 5.

The JANET Technical Administration Group will be able to confirm whether the third party is eligible for a Sponsored Connection if this is not clear, and provide details of the current cost of a licence. Once the host has completed the application form, it must be returned to the JANET Technical Administration Group for processing. The licence is sent to the host site by post.

Obtaining IP Addresses for the Sponsored Site

Each Sponsored Connection requires IP addresses from the JANET allocation. The host must not, however, use IP addresses from within their own address range for this purpose unless the required addresses fall in the /30 range. Application for IP addresses is contained within the Sponsored Licence application form.

DNS

The JANET Technical Administration Group will contact the host site about the domain name request detailed on the licence application form and will submit the requested domain name to the naming committee for consideration.  A decision on acceptance or rejection of the requested domain name will be made by the naming committee within five working days.

Invoicing Arrangements

The first invoice may be calculated on a pro-rata basis. Please note that the JANET Technical Administration Group issues invoices to the primary hosting organisation; invoices are not sent to the organisations or individuals covered by the host's licences.

Proxy Connections

If a third party that is not part of the JANET community uses the facilities of a Primary Connection site or RNO on a regular basis to access the network, a proxy licence may be required. A licence is required if, for instance, a contractor is given access to JANET. Such access is only permitted via a computer system that belongs to the licensed organisation and is located at its premises (e.g. by provision of a mailbox or a user account), and either or both:

  • via a communications server belonging to the licensed organisation and located at its premises, for the provision of dial-up access
  • by provision of space on an information server belonging to the licensed organisation and located at its premises (e.g. pages on a web server).

The licensed organisation is also permitted to provide JANET access to participants at any conference, seminar or similar event being run by a third-party organisation on its own behalf, provided that the event is of benefit to the learning, teaching or research aims of the licensed organisation. (If the event is being run by, or on behalf of, the hosting organisation then there is no requirement for a licence.)

One proxy licence covers all uses of the system, e.g. the provision of electronic mail facilities via the host's mail server, an account on a host system that provides JANET access, or space on an organisation's web server for third-party information. However, third-party networks or systems are not permitted to connect under this type of licence, except for the connection of individual computers via a dial-up facility.

Applying for a Proxy Connection Licence

Both primary sites and RNOs may host Proxy Connections. The request for a proxy licence must be submitted to the JANET Technical Administration Group via the hosting organisation. The licence application form should also be returned to the JANET Technical Administration Group via the host. A single proxy licence covers all use of the host's systems by any number of third parties. Details of the cost of a proxy licence can be obtained from the JANET Technical Administration Group.

A proxy licence form may be downloaded from Appendix 6 or from.

Invoicing Arrangements

The first invoice may be calculated on a pro-rata basis. Please note that the JANET Technical Administration Group issues invoices to the primary hosting organisation; invoices are not sent to the organisations or individuals covered by the host's licence.

Interconnect Connections

These are available to organisations responsible for the operation of a network, to connect that network to JANET subject to JANET(UK) and JISC's agreement. The network will normally be supporting the broader education and/or research community or be delivering educational services to communities that are not directly connected to JANET, such as schools. These are not subject to the JANET SLA. Only an IP service is normally available — other JANET services are subject to further agreement.

Further information about Interconnect Connections can be obtained from the JANET Service Desk.

 

<<
nonenone Foreword
  1. Fault Reporting
  2. Connecting to JANET
  3. Domain Name System
  4. IP Addresses
  5. Routers
  6. E-mail
  7. Security
  8. JANET Services
  9. JANET Policies and Legal Requirements
  Appendices

Return to Index