Example MoU between the RIPE NCC and hosts - K-root

 <ACME LOGO
PLACE HOLDER>
Memorandum of Understanding on
Enhanced Cooperation
Between
<ACME>
And
Réseaux IP Europeens Network Coordination Centre (RIPE NCC)
Preamble
I.
II.
<ACME> and the RIPE NCC have a common interest in improving public
Internet infrastructure in their service regions.
<ACME> and the RIPE NCC have plans to improve the reachability and
reliability of Internet services in their service regions.
Scope of the MoU
The parties agree to work collaboratively to enhance their coordination and
cooperation with regard to activities in which they have a common interest. Such
activities may include:
•
•
•
Internet measurements; hosting a RIPE Atlas anchor
Collection and provisioning of routing information; hosting a RIS data
collector
Root DNS server deployment, hosting a K-root node
Details of these activities shall be specified in Project Documents (in the form of
the attached) setting out the parties’ goals, resource commitments, time lines and
other information, in relation to each activity, according to the acceptance of both
parties’ service terms and conditions. These Project Documents constitute part of
this MoU. Each Project Document may be established, amended, or
supplemented upon agreement by both parties. Such establishment, amendment
or supplement shall come into effect without the resigning of this MoU being
necessary.
Status of this MoU
The parties hereby acknowledge and agree that this MoU is non-binding and
does not create any obligations under law.
Duration of and amendments to the MoU
The MoU shall enter into force when signed by both parties and shall run until the
end of the calendar year. After this date, the MoU shall be automatically
extended by one year at a time, unless one of the parties gives notice to the
other party at least six months before the scheduled termination date, of its
intention not to extend the MoU. Such notice must be given by means of a written
notice sent to the other party.
The MoU may be amended by agreement by both parties at any time.
<ACME>
RIPE NCC
Place:
Place:
Date:
Date:
<NAME>
Kaveh Ranjbar,
Chief Information Officer
Project No 1
Activity
Activity Name
Details of the activity
Goals of the activity
Timeline
K-root instance
RIPE NCC K-root local server to be installed at a
ACME colo facility.
To provide an operationally stable environment for a
K-root service node, incl. reliable colocation
facilities, rack space, power, upstream routing and
connectivity for administrative and out-of-band
access.
Within 3 months after the agreement
Contacts
Owner at ACME
Owner at RIPE NCC
Other staff involved by
ACME
Other staff involved by
RIPE NCC
Resource Commitment
Contribution by ACME
Contribution by RIPE NCC
- To purchase one Dell server according to the RIPE
NCC detailed specification
- To host the server at the peering location.
- To provide network connectivity according to the
RIPE NCC detailed specification.
- To provide a local BGP peering and upstream
routing advertisement of the K-root anycast prefix.
- To separately provide upstream connectivity for
system management and console access.
- To provide occasional ‘remote hands’ support to
the RIPE NCC network team.
- To remotely install/manage, monitor and maintain
the K-root node as part of RIPE NCC Root DNS (Kroot) services.
Note:
RIPE NCC monitors the health of the K-root servers and the proper functioning of
the K-root service as a whole. At RIPE NCC’s discretion, any K-root node can be
removed from the service at all times when there is any sign of malfunctioning of
the node or any negative impact to the service. Traffic towards K-root will then
automatically be rerouted to other instances of the K-root Anycast service.