GOpenCNR enterprise terms and order form

These terms

These terms are between Gelhaus Solutions and a business that orders GOpenCNR's enterprise services, the customer. They apply to every order form signed under them, together with the GOpenCNR terms, the acceptable use policy and, for every router the customer connects, the network participation agreement. The customer's accounts and its organisation are held in GOpenCSR under the GOpenCSR terms. Warranty, the limits of liability and everything else that is not particular to GOpenCNR are in the general terms of service. Personal data we process on the customer's behalf is covered by the enterprise data processing agreement, which is part of every order form.

The free core stays free. Membership, allocations at the default sizes, closed prefixes, the RPKI, the registry and every network service of GOpenCNR are free for an enterprise customer as for every member, under the GOpenCNR terms. These terms add only what the customer pays for, and take nothing away from the GOpenCNR documents.

Where an order form and these terms differ, the order form wins, except on the points under "What money never buys", which no order form can change.

Who may order

Enterprise services are for businesses only:

• entrepreneurs within the meaning of Section 14 BGB;
• legal persons under public law and special funds under public law;
• associations, where they order in the course of their trade, business or profession.

They are not offered to consumers. Because no consumer can order, the consumer right of withdrawal and the rules on ordering buttons (Sections 312g and 312j BGB) do not apply. Whoever signs the order form for the customer confirms that the customer is one of the above and that they may bind it.

The customer holds its resources as a verified organisation under the organisation verification terms. Like every holder, it is screened against the EU consolidated financial sanctions list by its verified name and country, when it becomes a holder and every day, and a match places the holds the GOpenCSR terms describe. An order neither lifts nor shortens them. If its verification lapses, its holdings keep working, but it obtains no new resources, ordered ones included, until it is verified again.

What may be ordered

An order form may include these services, and no others:

• Dedicated hubs: a hub reserved for the customer's organisation, run only by Tier 0, on its own servers.
• Larger pools and organisation sub-pools: address space above the default sizes, and space the customer's organisation holds and divides among its own sub-holders.
• Managed edge routers: a virtual machine or appliance image that runs the GOpenCNR agent and that Tier 0 manages remotely for the customer.

Each is described below.

What money never buys

Money buys capacity and service. It never buys safety, and it never buys an exception.

• Closed prefixes are free for every member. The customer requests them as anybody does, and Tier 0 approves them under the four-eyes principle as it approves anybody's. No order makes a closed prefix cheaper, quicker or more likely to be approved, and a member without an order gets exactly the same protection.
• No exemption from the rules. The GOpenCNR terms, the acceptable use policy, the network participation agreement, the routing policy (generated filters, RPKI and ASPA validation, max-prefix, anti-spoofing, no exit), GOpenCNR's policies, the abuse and sanctions policy with its sanctions ladder, and emergency suspension apply to the customer and to every ordered service exactly as they apply to everyone else. A case about the customer runs like any other case.
• No response time. No order buys a service level or a support response target.
• No addresses. Address space and ASNs are allocated, never owned and never sold. The price pays for capacity and its administration, the space stays the registry's, and a transfer is never made for payment.
• No standing. An order gives no council seat, no vote and no say in any decision. The customer takes part in GOpenCNR's governance as any holder does.

No service level, and no support response target

No service level is offered, and no order form can create one. No availability, uptime, throughput, latency, response time or restoration time is owed or implied, whatever an order form, the status page, the network map, the looking glass or anybody says. Routers keep running on their last signed bundle while the control plane is unavailable, and hubs keep routing while GOpenCSR or GOpenCDR is down. Neither is a commitment.

Questions and faults go to contact@gplatform.org. They are answered as soon as we can, and no response or resolution time is owed for them. Abuse goes to abuse@gplatform.org and is handled under the abuse and sanctions policy.

How the contract is made

• The contract is concluded when both sides sign an order form, on paper or electronically. Publishing these terms and the form below is not an offer, and neither is a quote.
• The order form names the parties, the services with their quantities, the prices, the term and the start date, the billing and the contacts. The form at the end of these terms is its template.
• An order form changes only through a new or amended order form signed by both sides. Adding a service is a new order form under these terms.
• Every order form names the versions of these terms and of the enterprise data processing agreement it was signed under, by their identifiers in the document archive.

Prices, invoicing and payment

• Prices and the term are those in the order form. These terms contain none.
• We invoice as the order form says: for the period it names, in advance or in arrears, and by the method it names. Invoices are payable as the order form says.
• No VAT is charged. Gelhaus Solutions is a small business under Section 19 UStG, and while that applies, invoices carry no VAT. If it stops applying, we tell the customer before the first invoice it affects, and the order form says whether its prices then include VAT or have it added.
• If an invoice is not paid when due, the statutory rules on default apply. After a reminder that sets a reasonable deadline and warns of it, we may suspend the ordered services until the invoice is paid. The free core is never suspended for non-payment: the customer's membership, its allocations at the default sizes and its closed prefixes stay as they are.

Dedicated hubs

• What it is. A hub reserved for the customer: only routers of the customer and of the sub-holders it names in the order form connect to it.
• Who runs it. Only Tier 0, on its own servers. Certified hub operators run hubs only in the shared network, for free, and never a dedicated hub. A dedicated hub keeps the same rules on forwarding and records as Tier 0's own hub: it forwards only and keeps no traffic records.
• It is a hub like every other. Its configuration is generated from the registry, and nothing on it is configured by hand. It applies the same import filters, RPKI and ASPA validation, max-prefix limits, anti-spoofing per tunnel and no-exit forwarding as every hub, carries closed routes only to their audience, and cuts a leak at once. It forwards the traffic between agents as ciphertext and keeps counters, not traffic records. Flows are sampled only inside an open case, as the GOpenCNR privacy notice describes. Every step of the sanctions ladder takes effect on it as on any hub.
• Capacity. The capacity of a dedicated hub, and any fair-use limit above the default of 100 Mbit/s sustained per member per hub with a 200 Mbit/s burst cap, are those the order form names.
• What the customer sees. Its own sessions, latency and drops, as every member sees its own. The customer gets no access to the hub's configuration, to its keys or to the traffic it forwards.

Larger pools and organisation sub-pools

• What it is. Space above the default sizes, which are a /48 of IPv6 for an organisation and a /29 of IPv4 on request, and organisation sub-pools: space the customer holds and divides among its own sub-holders by delegation.
• Space is allocated, never sold. The price pays for the capacity and its administration. The space stays subject to the allocation policy like any allocation: yearly reconfirmation, reclaim of space that has not been announced for 12 months (after a warning, 90 days later), and transfers only with both holders' consent and Tier 0's review, never for payment.
• The ordinary review still decides. Space above the default sizes is allocated only on written justification and on Tier 0's review under the four-eyes principle, as for every member. An order does not replace that review. Where the review refuses space an order form names, that part of the order does not take effect and is not charged.
• An order does not create a pool. Pools are created only by a motion of the GOpenCNR Community Council, and ordered space comes from pools that exist.
• Sub-holders. Each sub-holder is a holder in its own right, with its own account, bound by the GOpenCSR and GOpenCNR terms. Delegated space is shown as delegated in the registry, and the roles the customer gives are inherited down the allocation tree and shown on every object. The customer answers for whom it delegates space to. Delegating space to others for payment is reselling GOpenCNR, which needs Tier 0's agreement in writing; an order form may record it.
• What is public. An allocation, and every delegation from it, is published as the registry data policy sets out.

Managed edge routers

• What it is. A virtual machine or appliance image that runs the GOpenCNR agent on a host the customer provides, and that Tier 0 manages remotely for the customer. It is an agent router: its traffic to other agents is encrypted end to end, it reaches the closed prefixes whose audience includes the customer, and its keys are made on it and never leave it.
• What Tier 0 manages. What the order form names, out of what managed networking covers: subnets, DHCP and router advertisements, firewall zones and rules, port forwards and NAT, routing and BGP, devices, WAN settings, VLANs, Wi-Fi, local DNS and firmware. Changes reach the router as signed bundles. A change that could cut the router off applies commit-confirmed, and it rolls back unless the router reports healthy within 5 minutes. Traffic from GOpenCNR is denied unless a declared service opens it.
• On whose word. Tier 0 configures what the technical contacts named in the order form ask for, within the GOpenCNR terms and policies. It refuses what those rules forbid and says which rule stands in the way and what would fix it. Beyond the customer's requests, Tier 0 changes a managed edge router only to install updates, to apply GOpenCNR's rules and policies, and as a step of the sanctions ladder or an emergency suspension.
• Updates. Tier 0 installs signed releases as part of the management, security releases within 14 days. The customer does not hold them back.
• Access. The customer gives the management what it needs: a host or hypervisor with the resources the order form names, power and an uplink, and the enrolment of the agent with a single-use token, which is valid for 24 hours. After enrolment, the agent signs every request with its own key. Managing the router gives Tier 0 no access to the customer's other systems, and Tier 0 seeks none.
• What Tier 0 sees. The router's configuration, its health reports and telemetry, and its traffic counters. Not the content of the traffic it carries.
• The customer's duties. It keeps the host or hypervisor running, patched and physically secure; leaves the image and the agent unmodified; makes no change to the router outside the management, since the next bundle may overwrite it or it may break the management; and tells Tier 0 in advance of changes to the uplink or to the network the router depends on.
• Whose router it is. The customer's. The network participation agreement binds the customer for it, and the customer answers for the traffic it sends, as for any of its routers.
• Data. The configuration can name people and their devices. We process it on the customer's behalf under the enterprise data processing agreement.

What the customer is responsible for

• People and roles. Whom it admits to its organisation, the roles it gives them (owner, admin, tech, abuse, read-only) and the keys they sign with. Every change to its resources is signed with a passkey or with an automation key registered under one, and the customer keeps them safe.
• Abuse. Its public abuse relay address reaches somebody who acts, and it acts on reports within 48 hours, or within 12 hours for an active attack, as the abuse and sanctions policy requires of every holder.
• Lawful use. It answers for what its people, its sub-holders and its routers do. The acceptable use policy binds the customer and each of them.
• Its own copies. It keeps its own copies of its configuration, as the general terms require for all data.
• Contacts. It keeps the contacts in the order form current.

Data protection

What we process about the customer's accounts, its registry objects, its cases and the transparency log, we process as controller, as the GOpenCSR privacy notice and the GOpenCNR privacy notice describe. What we process on the customer's behalf in its managed edge routers, its dedicated hubs and the administration of its sub-pools is covered by the enterprise data processing agreement. Personal data is processed in the EU, on servers in Germany, as the data processing agreement sets out.

Term and ending

• Term. An order runs from the start date for the term the order form states. Renewal, and the notice for ending it, are as the order form states. Where it states no renewal, the order ends with its term.
• For cause. Either side may end an order for good cause, in particular for a material breach that is not remedied within a reasonable deadline after notice.
• Suspension. We may suspend an ordered service on the grounds and in the way the general terms of service set out for restrictions: at once only in the cases where they let us act first, such as an attack on GOpenCNR or on others, including under an emergency suspension; otherwise after telling the customer and hearing it. The statement of reasons reaches the customer no later than when the suspension takes effect, unless the law forbids telling it. A suspension is lifted when its cause ends.

When an order ends:

• A dedicated hub is taken out of service for the customer, and the customer's routers carry on through the other hubs they connect to.
• A managed edge router is no longer managed by Tier 0. The customer may keep it in the network as an agent router it manages itself, under the network participation agreement, or retire it, which revokes its keys in the registry.
• Address space: the customer keeps an allocation of the default size. Everything above it goes through grace (30 days, in which its routes stay), redemption (30 days, in which they are refused) and then 3 months of quarantine. The customer and its sub-holders are told before each step.
• Personal data is returned or deleted as the enterprise data processing agreement provides.
• What we keep as controller about the customer's accounts, registry objects and cases afterwards, and for how long, is in the GOpenCSR privacy notice and the GOpenCNR privacy notice.

Confidentiality

Each side keeps confidential what the other discloses as confidential, or what is evidently confidential, for the term and for three years after, and uses it only for the order. This does not apply to what is public without breach, was already known, is independently developed or must be disclosed by law. What GOpenCNR publishes by design, such as registry data, the transparency log, the looking glass and the network map, is not confidential.

Everything else

Warranty and liability between the customer and us are as the general terms of service set them out for businesses. The services the customer pays for are not given away, so the limitation to intent and gross negligence under Section 521 BGB applies to the free core the customer uses alongside its order, as the GOpenCNR terms say, and not to them. German law applies, and the place of jurisdiction is as the general terms set it out.

A material change to these terms is emailed to the customer at least six weeks before it takes effect, and at its next sign-in the customer is asked to accept the new version, which is shown in full and linked in the document archive, without a list of what changed. A new version applies to an order only once the customer accepts it, and an ordered service is never restricted because the customer has not. Until then, each order stays on the version it was signed under. If the customer does not accept, we may end the order at its next ordinary end date under its order form, and only then. Every version stays in the document archive.

Annex: order form

Each order is made with this form, signed by both sides. Everything in square brackets is filled in; a part that does not apply says "none".

1. Parties

Provider: Gelhaus Solutions, a sole proprietorship of Enno Gelhaus, Eichenwald 3, 49624 Löningen, Germany, contact@gplatform.org. Not entered in the commercial register. Small business under Section 19 UStG.

Customer:

• Name: [legal name]
• Legal form: [legal form]
• Address: [street, postcode, town, country]
• Register: [register court and number, or "not registered"]
• VAT identification number: [number, or "none"]
• The customer is: [an entrepreneur under Section 14 BGB / a legal person or special fund under public law / an association ordering in the course of its trade, business or profession]
• GOpenCSR organisation: [handle of the verified organisation]

2. The order

• Order number: [number]
• Order date: [date]
• Signed under: GOpenCNR enterprise terms, version [identifier from the document archive]; GOpenCNR enterprise data processing agreement, version [identifier from the document archive]

3. Services

| Service | Details | Quantity | Price | |---|---|---|---| | Dedicated hub | Run by Tier 0 on its own servers; capacity [figure]; fair-use limit [figure, or "default"]; routers that may connect [the customer's / the customer's and these sub-holders': handles] | [number] | [amount] per [period] | | Larger pool | IPv6 [prefix length, or "none"]; IPv4 [prefix length, or "none"]; from pool [pool]; justification [reference of the request under review] | [number] | [amount] per [period] | | Organisation sub-pool | Size [prefix length]; sub-holders [handles, or "as the customer delegates"] | [number] | [amount] per [period] | | Managed edge router | [virtual machine image / appliance image]; site [location]; host resources [processor, memory, storage, network]; managed [subnets, DHCP and router advertisements, firewall, port forwards and NAT, routing and BGP, devices, WAN, VLANs, Wi-Fi, local DNS, firmware: as chosen] | [number] | [amount] per [period] | | One-time items | [description, or "none"] | [number] | [amount] |

4. Prices and VAT

• Recurring total: [amount] per [period]
• One-time total: [amount, or "none"]
• No VAT is charged: Gelhaus Solutions is a small business under Section 19 UStG.
• Should VAT become chargeable, the prices above [are net, and VAT is added at the statutory rate / include VAT].

5. Term

• Start date: [date]
• Term: [length, or end date]
• Renewal: [none / renews for [period] at a time]
• Notice for ending at the end of a term: [period, or "none"]

6. Billing

• Invoiced: [in advance / in arrears], per [month / quarter / year]
• Payment due: [number] days after the invoice date
• Payment by: [bank transfer to the account on the invoice / other: method]
• Invoice address: [address]
• Invoices by email to: [address]
• Customer's order reference: [reference, or "none"]

7. Contacts

| Role | Customer | Gelhaus Solutions | |---|---|---| | Commercial | [name, email, telephone] | contact@gplatform.org | | Technical, and instructions for managed edge routers and under the data processing agreement | [names, emails, telephones] | contact@gplatform.org | | Billing | [name, email] | contact@gplatform.org | | Abuse | [internal contact for Tier 0: name, email, telephone]; public reports reach the customer through its abuse relay address | abuse@gplatform.org | | Data protection | [name, email] | contact@gplatform.org |

8. Further agreements

• Reselling: [none / Tier 0 agrees that the customer may delegate space to others for payment as follows: description]
• Other: [none / text]

No further agreement can create a service level or change what money never buys under the enterprise terms.

9. Signatures

| | For Gelhaus Solutions | For the customer | |---|---|---| | Place and date | [place, date] | [place, date] | | Name and position | Enno Gelhaus, proprietor | [name, position] | | Signature | [signature] | [signature] |