AS60474 - 4b42 Autonomous System

Policy

  1. Introduction
  2. Requirements
  3. Connectivity
  4. Routing
  5. Traffic
  6. Contact
  7. Additional Information
  8. Important Information

Introduction

This Guide is used by 4b42 to evaluate requests from Network Providers for the purpose of directly exchanging internet prtocol traffic with Autonomous System 60474 (AS60474) operated by 4b42 UG.

4b42 currently accepts public peering and private peering by mutual agreement in Canada, France, Germany and Switzerland. The requesting peer network must fulfil the following conditions and requirements in order to qualify for a Peering Agreement with AS60474.

Requirements

  1. The Requesting Network shall have a fully redundant backbone network with enough capacity to exchange traffic without congestion.
  2. The requesting network should operate a fully staffed, 24/7 and 365 day network operations centre (NOC).
  3. Each Network must be responsive to routing and security issues, providing a knowledgeable technical response within a 24 hour period after notice for network and operational issues and a 2 hour period for security related issues.
  4. Peers are expected to keep and maintain at all times a record in the peering database at peeringdb.com.

Connectivity

  1. The requesting networks must be able to interconnect with 4b42 at a minimum of three geographically dispersed points of interconnection (in different countries) or from two of the following locations: Zurich, Frankfurt and New York.
  2. Where multiple locations are not feasable 4b42 may accept an interconnect as a regional peer (where only local country routes are exchanged) solely at the discretion of 4b42 where mutual benefit to both parties exists.

Routing

  1. The requesting network should be able to provide and maintain a consistent route announcement at all peering points with AS60474 unless otherwise agreed in advance.
  2. Hosting and Content providers may receive inconsistent route announcements from 4b42 in order to reduce inbound traffic load where asymmetric routing occurs and 4b42 infrastructure is being used to carry large amounts of return traffic different from the originating country.
  3. The requesting network must be registered as a Local Internet registry (LIR) with the appropriate Regional Internet Registry (RIR) e.g. RIPE, ARIN, APNIC. Only routes specified by the appropriate RIR are accepted from peers.
  4. The requesting network will not use a route of last resort (i.e. default route) or static routing of any of 4b42's address space directed at AS60474.
  5. No third party routes that allow direct traffic exchange (in either direction) between AS60474 and the third party should be used by the requesting network unless mutually agreed. For example, 4b42 routes should not be advertised to another peer.
  6. Routes should be aggregated as much as possible by the requesting network. AS60474 does not accept route announcements smaller than a /24 for IPv4 and /48 for IPv6.
  7. We are filtering prefixes which are listed as bogon space [IPv4] [IPv6].

Traffic

  1. The amount of traffic to be sent and received between 4b42 and the requesting network should be in approximate parity.
  2. The amount of traffic exchanged in either direction over all interconnection links between the requesting network and 4b42 shall equal or exceed 100 Mbps on average (measured as a total of all interconnect points).

Contact

  1. A contact point (real person, or role account) for abuse/security issues, and a real person escalation contact should be provided, complete with phone numbers by the requesting network and 4b42 should be notified of any changes to these details.
  2. A contact point for network related issues, outages and operational issues (A NOC and peering contact) should be provided by the requesting network and 4b42 should be notified of any changes to these details.

Additional Information

These criteria are only guidelines and are not exhaustive. Any final peering executed by 4b42 and a potential peer may contain additional terms and conditions. 4b42 reserves the right to decline to enter into a Peering Agreement even if the above criteria are nominally met by a potential peering partner.

If a network fulfils all of the requirements outlined above and wishes to proceed with an Internet Peering Agreement with 4b42, please contact peering@4b42.com including a list of exchange points, your AS, company name and contact information as outlined above.

A peer is expected to continually fulfil 4b42's peering policy for the duration of the peering. If a peer no longer meets 4b42's peering policy then 4b42 reserve the right to remove the peering without notice.

Important Information

This Peering Guide is made available for informational purposes only. It does not constitute an offer to enter into a Peering Agreement. In the event your network enters into a Peering Arrangement with 4b42 that peering shall be on an as is basis and 4b42 reserves the right to remove temporarily or indefinitely that peering without notice.

4b42 reserves the right to revise or change this document at any given time and without notice. This guide will be updated as necessary to enhance and / or expand the information contained herein.