Draft Paper for Presentation at EOF meeting

Here is a paper I plan to present at the EOF meeting on Friday.
Apologies for the rough-and-ready nature, it is a first cut at a
generic/template non-transit peering interworking agreement between
Internet Service Providers, for those cases where it is felt to be
necessary.

It is based on a generalisation of agreements we have drawn up in
the past with our UK competitors, and I'd like to acknowledge input
from Peter Houlder at EUnet GB, and Cliff Stanford at Demon into
these that has found its way modfied into what follows.

I hope this will at least get the discussion going, and and look
forward to your input.

Regards,

Keith Mitchell
PIPEX


In <CMM.0.90.0.774004868.roll@localhost>, roll@localhost wrote:

> 1. Traffic and Routing Exchange Models between Providers
> 
>    <This is about makeing template agreements about routing and traffic
>     exchanges between providers which may (but do not have to) be used when
>     providers connect to each other.>
> 
>    Keith Mitchell
>    Glenn Kowack


-------------------------------------------------------------------------------

	Non-Transit Interworking Agreement between Xnet and Ynet

1. Introduction

[Background Information about the parties involved - e.g.]

- Xnet is an operating division of UVWX Ltd.

- Ynet trades as ABC Ltd and is owned by DEF University

- Znet has been providing dial-up Internet services
  for 3 years.

- Relationship between Xnet and Znet

  Although Znet was one of Xnet's first re-seller customers, it now
  has its own arrangements for international Internet access, and Xnet
  and Znet now work as completely independent companies, and offers
  distinct Internet services targetted at different sectors of the
  market.  Both Xnet and Znet are members of the Commercial Internet
  Exchange, which obliges them to freely exchange customer IP traffic,
  until now via the US.

2. Physical Connectivity

[Lots of possibilities here - some alternatives: ]

- In order to improve connectivity within the inter/national Internet
  community, the named parties have arranged a non-transit IP
  interworking agreement, implemented by a NNN kbps leased line
  installed between Xnet's Xtown and Ynet's Ycity sites.
   
- The leased circuit to implement this has been paid for by
  Xnet/Ynet/both parties.

- The router port at the Xnet PoP has been provided free of charge
  by Xnet.

- Ynet will make no charge for use of bearer facilities or a router
  port for connecting this circuit at their PoP, this will be
  reviewed if Xnet have capacity problems at this PoP.

- Ynet have agreed to pay Xnet N amount for use of a router at Xnet's
  PoP.

- Both parties have agreed to split all costs associated with this
  connection equally.

- Xnet has agreed to house one of Ynet's routers at its PoP.

- Both parties will be locating routers at the Neutral Interconnect facility
  at Znet. Connection between them will be across the LAN at that site,
  each party will have an Nkbps capacity circuit back to their own PoP.

3. IP Connectivity

- Both parties agree to freely exchange IP traffic on a non-transit
  basis between their respective customer sites, via a directly
  connected national leased line.

- This connection means that all the direct customers, and the
  customers of the transit subscribers of both parties can freely
  exchange IP traffic.
   
- Note that even in the absence of this domestic link, traffic
  exchange would still be possible via the CIX (Commercial Internet
  Exchange), of which both parties are members. The presence of the
  direct line is purely to conserve international bandwidth and
  improve service.

- In the event of failure of this direct link, backup will take
  place via international service providers each party subscribes to
  transit or backup from, normally other CIX members.

- Routing between the networks will normally extend to exchange of
  traffic using other means of interconnection as they become
  available, such as networks with which both parties have an
  agreement to subscribe to transit from, for example the Ebone.

- While the packet exchange agreement permits exchange of traffic
  between users of both networks, transit of either network to a third
  party, for example international networks, by users of one network
  to another is not permitted.

- IP interworking between the parties named is not possible using
  third parties that either party may have other non-transit
  agreements with.

- Both parties reserve the right to restrict access to International
  links to only their direct customers, or customers of their
  transit subscribers.

- Some or all of the above restrictions may be removed if
  both parties agree to mutual backup at some future point.


4. E-Mail

- Both parties agree to agree to ensure e-mail connectivity between
  their customers and transit subscribers' customers by forwarding
  mail to and from any registered and accessible e-mail sites which
  is either originated by, or destined for, these customers.

- Destination sites must have an MX entry in the DNS, though an
  entry in other network directories, such as X.400/X.500
  directories, or UUCP maps, is a possible alternative.  Both
  parties will endeavour to maintain entries in all these
  directories for their customers, and attempt to ensure their
  customers and transit subscribers do so for their downstream sites
  and customers.

- Note that it is possible for any site connected to more than one
  network for e-mail to act as a mail gateway, and perform mail
  relaying without being named as an MX forwarder, for example by
  source routing of mail. Any site is entitled to refuse to forward
  such mail via access controls.  While both parties reserve the
  right to do this, in practice no restrictions will be placed on such
  forwarding, as a gesture of goodwill and in the interests of
  maintaining national e-mail connectivity.  This is partly to cope
  with the shortcomings of the e-mail software at some sites.

- No site should name another site as an MX forwarder or gateway
  without the explicit prior permission of that site. Failure to
  honour this basic courtesy may result in sites that would
  otherwise pass mail freely placing access controls on mail
  forwarding.

- Both parties agree to make no volume charges to their customers
  for forwarding national mail to or from customers of the other
  party, even though they may choose to make such charges to their
  own customers for forwarding of mail via international links or
  other gateways.

5. Other Services

- Both parties agree to exchange a directly-peered NNTP News Feed.
  This news exchange is to take precedence over any news feed
  arrangements made between their customers, to avoid wasting the
  bandwidth on the bi-lateral link with multiple redundant news
  feeds. Both parties reserve the right to prevent their customers
  from direct exchange of news with the other party or its customers
  to ensure this, and will endeavour to encourage their customers to
  adhere to this policy.

- A pre-condition of this news exchange is that both parties have
  independent international news feeds.

- Both parties agree to attempt to prevent redundant use of the
  bi-lateral link between them by co-ordinating deployment of any
  other application protocols whose operation most efficiently
  follows the network topology, for example Multicast and NTP.

6. Routing and Registries

- Exchange of routing information between the parties' routers will
  use BGP version 4. Least-specific CIDR-aggregate routes will be
  exchanged wherever possible.

- All networks and aggregates announced between the parties will be
  registered with the RIPE NCC and/or InterNIC. Both parties will
  ensure that up-to-date policy and network membership information
  for their Autonomous Systems will be registered with the RIPE NCC,
  and other relevant routing registries.

7. General

- Each party will provide to the other an e-mail Point-of-Contact
  for initial problem resolution, and a telephone POC for 24-hour
  problem resolution.

- Both parties recognise the importance of the role of the RIPE NCC,
  and the desirability of contributing to the RIPE NCC's funding.

- In the event of the creation of a National Neutral Interconnect or
  similar, both parties commit to migrating their bi-lateral peering
  to be ultimately replaced with connections to this interconnect.

- In the absence of the above, this agreement is subject to yearly
  review, and either side may withdraw after the review without
  prejudice.

- There is no commercial or other relationship between the parties
  beyond the scope of this peering agreement.

- In all announcements or explanations either publicly, or to
  prospective or existing customers, both parties agree to adhere to
  the above text when describing the relationship between them.