Peering Policy for AS3257


All peering requests shall be sent by email to peering@tinet.net.
Peering requests shall not be sent more than once in 3 months.
Applicants not matching this policy may apply for a Paid Peering.

The following minumum criteria must be met for any peering connection

Violation of these terms may result in immediate de-peering and other attention-getting mechanism
  • Applicant must operate a 24x7 fully staffed Network Operation Center.
  • Applicant's announcements within Europe must be consistent, i.e. Applicant must announce the same set
    of routes on all peering sessions
  • Applicant's announcements within the US must be consistent
  • Applicant must use the peering connection for all Traffic destined towards the Tinet network
  • Applicant must sell (native) Internet connectivity to third parties and/or end users
  • Applicant must meet a minimum traffic ratio of 1:3
  • There will be only one peering relationship per corporate (i.e. only one peering relationship -with a single
    AS - for corporate companies)
  • Applicant or Applicants's entities must not have any transit or peering relationship with Tinet or any other
    Tinet entity or have had such a relationship in the 6 months prior to application.
  • Applicant must not sell or give next-hop to any 3rd party (i.e. peer must not re-advertise Tinet routes to
    any peer)
  • Applicant agrees to peer in all markets where Peer and Tinet share a presence
  • Tinet reserves the right to terminate the peering at any time with 30 days notice
  • Applicant agrees in writing to Tinet's peering policy

  • This policy is a guideline. Meeting all the requirements stated in here does not guarantee that Tinet will
    enter into a settlement-free relationship with the applicant. Tinet reserves the right not to grant settle-
    ment-free peering to an applicant based on business reasons.
  • Tinet may honor legacy peers not entirely matching requirements outlined in here at it's sole discretion.
  • Any exceptions to this policy will be granted at the sole discretion of Tinet.

Opsec

  • Applicant must use prefix-list filters on customer links
  • Applicant must respond to all operational issues within 24 hours


Interconnection Requirements

  • Tinet AS3257 is not entering new PUBLIC peering relationships in Europe currently.
  • All new peerings must be over private links. A minimum of two links interconnecting independent node-sets
    is required. Substantial domestic traffic is expected to justify a link.

  • Applicant has a minimum traffic from the Tinet Network of 1 Gbit/sec - judged on 95th percentile over
    1 (one) month (this may be proofed with a test peering). This is a mandatory requirement.

  • Applicant announces a minimum of 1,000 fully aggregated routes or equivalent of 50,000 Class-C networks
    and
  • Applicant's network must share a presence with Tinet in at least four regions in Europe and two regions
    in the US, out of the regions below. These regions must be linked with redundant dedicated IP backbone
    capacity of OC192 or higher. Applicants are expected to have a significant customer base in any of the
    regions and thus carry significant domestic traffic in these regions to match this criterion.

    European regions
  • Belgium, Netherlands, Luxemburg
  • Germany, Austria, Switzerland
  • France
  • UK
  • Italy, Greece
  • Spain
  • Sweden, Norway, Denmark
  • Czech Republic
    US regions
  • East Coast (New York, Washington Area)
  • West Coast (Bay Area, Los Angeles)
  • Mid-West (Chicago, Dallas)
  • Asian regions
  • Hong Kong
  • Singapore


(Last modified Fri Jun 05, 2009)