<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://bgp4all.com.au/pfs/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://bgp4all.com.au/pfs/feed.php">
        <title>Philip Smith&#039;s Internet Development Site - peering-toolbox</title>
        <description></description>
        <link>https://bgp4all.com.au/pfs/</link>
        <image rdf:resource="https://bgp4all.com.au/pfs/_media/wiki/dokuwiki.svg" />
       <dc:date>2026-04-04T07:34:34+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/advanced-peering-examples?rev=1652686458&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/bgp-resources?rev=1679901574&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/hardware?rev=1679878666&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/how-to-peer?rev=1661498078&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/internet_resources?rev=1682832968&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/iops-resources?rev=1679902243&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/looking_glass?rev=1661508475&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/manrs?rev=1661498273&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/more-peers?rev=1679818153&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/next-steps?rev=1679638516&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/peering-bcp?rev=1652686434&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/peering-examples?rev=1661508637&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/peering-operations?rev=1652686394&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/peering-resources?rev=1682835462&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/peering-technologies?rev=1659252162&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/peering_agreement?rev=1679877932&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/peering_policies?rev=1682830095&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/physical_connectivity?rev=1660906913&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/references?rev=1660636003&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/route_collector?rev=1661508061&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/route_origin_authorisation?rev=1661498145&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/route_server?rev=1661508296&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream?rev=1661507610&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_ixp?rev=1682834062&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_private_peer?rev=1661507701&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_two_private_peer?rev=1661507808&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/start?rev=1710241522&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/subject-index?rev=1679904327&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/terminology?rev=1661488905&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/the_internet_routing_registry?rev=1682833158&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/the_peering_database?rev=1682833515&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/trouble-ixp?rev=1652686337&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/trouble-pp?rev=1652686179&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/trouble-tools?rev=1710241292&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/trouble-transit-v-peer?rev=1652686263&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/troubleshooting-basics?rev=1710241072&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/troubleshooting?rev=1652686448&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/what-is-peering?rev=1660804188&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/where-to-peer?rev=1682829551&amp;do=diff"/>
                <rdf:li rdf:resource="https://bgp4all.com.au/pfs/peering-toolbox/why-peer?rev=1682829031&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://bgp4all.com.au/pfs/_media/wiki/dokuwiki.svg">
        <title>Philip Smith's Internet Development Site</title>
        <link>https://bgp4all.com.au/pfs/</link>
        <url>https://bgp4all.com.au/pfs/_media/wiki/dokuwiki.svg</url>
    </image>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/advanced-peering-examples?rev=1652686458&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-16T07:34:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>advanced-peering-examples</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/advanced-peering-examples?rev=1652686458&amp;do=diff</link>
        <description>Advanced Peering Scenarios

This section of the Toolbox documents peering scenarios collected from Euro-IX members and the general community, and shows how to implement them.

	*  to be done...

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/bgp-resources?rev=1679901574&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-27T07:19:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>bgp-resources</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/bgp-resources?rev=1679901574&amp;do=diff</link>
        <description>Border Gateway Protocol

(UPDATED)

The Toolbox cannot provide a tutorial about BGP, but the following are useful pointers for newcomers to the routing protocol.

	*  What is BGP
	*  Autonomous System
	*  Routing Policy
	*  Multihoming
	*  Skills Required
	*  Resources

What is BGP

The Border Gateway Protocol (BGP) is the routing protocol of the Internet. For any operator wishing to enter into a peering relationship with another operator, BGP will almost always be required.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/hardware?rev=1679878666&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-27T00:57:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hardware</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/hardware?rev=1679878666&amp;do=diff</link>
        <description>Router Hardware

An important requirement for establishing any peering link is to ensure that there is suitable router hardware available. This section looks at what considerations need to be made when choosing a router for the new connection being planned.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/how-to-peer?rev=1661498078&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T07:14:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>how-to-peer</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/how-to-peer?rev=1661498078&amp;do=diff</link>
        <description>What is required for Peering

This section of the Toolbox describes what a network operator needs before embarking on their peering journey.

Next Steps

The next steps for any aspiring member of the peering community is to lay the ground work so that their infrastructure is operationally prepared to be able to peer with other Network Operators.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/internet_resources?rev=1682832968&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T05:36:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>internet_resources</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/internet_resources?rev=1682832968&amp;do=diff</link>
        <description>Internet Resources

The Peering Toolbox mentioned elsewhere that Network Operators required Internet Resources. 

When the industry talks about Internet Resources, we mean our own independent IPv4 address space, IPv6 address space, and Autonomous System Number (ASN). A Network Operator needs their own independent Internet Resources to be able to take part in the global peering ecosystem.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/iops-resources?rev=1679902243&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-27T07:30:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>iops-resources</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/iops-resources?rev=1679902243&amp;do=diff</link>
        <description>Best Practices Resources

The section of the Toolbox dedicated to listing useful Internet Best Operational Practices Resources:

	*  Internet Society BCOP page 
	*  MANRS, the Mutually Agreed Norms for Routing Security

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/looking_glass?rev=1661508475&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T10:07:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>looking_glass</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/looking_glass?rev=1661508475&amp;do=diff</link>
        <description>Looking Glass

A Looking Glass is a web front end giving limited access to a router or route-collector/server for:

	*  Viewing the BGP table
	*  Allowing IXP members to verify their outbound BGP policies
	*  Viewing individual paths
	*  Checking traceroute and ping to destinations</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/manrs?rev=1661498273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T07:17:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>manrs</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/manrs?rev=1661498273&amp;do=diff</link>
        <description>MANRS

The Mutually Agreed Norms for Routing Security, known as MANRS, is an industry initiative supported by the Internet Society to improve routing hygiene on the global Internet.

The MANRS website has full information about what this initiative is all about.

The steps mentioned in this</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/more-peers?rev=1679818153&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-26T08:09:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>more-peers</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/more-peers?rev=1679818153&amp;do=diff</link>
        <description>Seeking more peers

(NEW CONTENT)

Once the first peers have been established, and the network operator has got both transit connectivity and connectivity to an IXP and/or private peers, the next step for any newcomer is to start seeking more peers. This section looks at some of the possible strategies the peering team could consider.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/next-steps?rev=1679638516&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-24T06:15:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>next-steps</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/next-steps?rev=1679638516&amp;do=diff</link>
        <description>Establishing Peering

This section completes the introduction by looking at simple deployment scenarios newcomers to interconnection and peering will likely encounter.

	*  Connectivity to another Network
	*  Single Upstream
	*  Adding a Private Peer
	*  Adding Two Private Peers
	*  Peering at an IXP

For other scenarios and a more in-depth look at interconnects, the</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/peering-bcp?rev=1652686434&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-16T07:33:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>peering-bcp</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/peering-bcp?rev=1652686434&amp;do=diff</link>
        <description>Peering Best Practices

This section of the Toolbox documents tricks, tips, hints, and industry best practices for peering, contributed by Euro-IX members and the general Internet community.

	*  to be done
	*  ...

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/peering-examples?rev=1661508637&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T10:10:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>peering-examples</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/peering-examples?rev=1661508637&amp;do=diff</link>
        <description>Peering Scenarios

This section of the Toolbox documents more sophisticated peering scenarios and how to approach each one.

	*  Two Upstreams and a Private Peer
	*  Two Upstreams and Two Private Peers
	*  Two Upstreams and an IXP

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/peering-operations?rev=1652686394&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-16T07:33:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>peering-operations</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/peering-operations?rev=1652686394&amp;do=diff</link>
        <description>Peering Operational Good Practices

This section of the Toolbox documents good practices for peering (and any external link in general).

	*  Link Capacity
	*  Link Quality
	*  Link Reliability
	*  Route Announcements
	*  Route Acceptance
	*  Route Origin Validation</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/peering-resources?rev=1682835462&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T06:17:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>peering-resources</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/peering-resources?rev=1682835462&amp;do=diff</link>
        <description>Peering Resources

(UPDATED)

The section of the Toolbox dedicated to listing useful Peering Resources

Some are described elsewhere in the Toolbox, others have a short description included here for completeness. As ever, please consult the respective websites for more information.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/peering-technologies?rev=1659252162&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-07-31T07:22:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>peering-technologies</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/peering-technologies?rev=1659252162&amp;do=diff</link>
        <description>Peering Technologies

This section of the Toolbox documents technical background of some of the technologies used in the Peering Ecosystem.

	*  IXP Route Collector
	*  IXP Route Server
	*  Looking Glass
	*  ...

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/peering_agreement?rev=1679877932&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-27T00:45:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>peering_agreement</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/peering_agreement?rev=1679877932&amp;do=diff</link>
        <description>Peering Agreement

(UPDATED)

A Peering Agreement is usually a documentation trail that indicates how two network operators are going to interconnect. They are required when operators have Selective or Restricted peering policies.

The documentation trail can take a range of forms depending on the operators involved, and can range from email exchanges all the way to a formal contract between the two entities.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/peering_policies?rev=1682830095&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T04:48:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>peering_policies</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/peering_policies?rev=1682830095&amp;do=diff</link>
        <description>Peering Policies

Every operator needs to decide that their “Peering Policy” needs to be as they embark on their peering journey.

This section looks at what is meant by “Peering Policy”, and how an operator goes about deciding what their policy should be.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/physical_connectivity?rev=1660906913&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-19T11:01:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>physical_connectivity</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/physical_connectivity?rev=1660906913&amp;do=diff</link>
        <description>Connectivity to another Network

This section discusses some of the considerations for a newcomer to interconnection and peering. 

There are two ways of connecting to another entity (be it an IXP or another network operator):

	*  Physical Connection
	*  Remote Peering

Physical Connection</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/references?rev=1660636003&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-16T07:46:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>references</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/references?rev=1660636003&amp;do=diff</link>
        <description>References

The content used for the Peering Toolbox is sourced from many contributors, including:

	*  Introduction to Multihoming Presentation - Philip Smith
	*  Inbound Traffic Engineering Presentation - Philip Smith
	*  Outbound Traffic Engineering Presentation - Philip Smith
	*  Deploying Multihoming Presentation - Philip Smith
	*  Value of Peering Presentation - Philip Smith
	*  BGP Videos - Network Startup Resource Center 
	*  Input from Mark Tinka, Kurt Erik Lindqvist, Matsuzaki Yoshinob…</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/route_collector?rev=1661508061&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T10:01:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>route_collector</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/route_collector?rev=1661508061&amp;do=diff</link>
        <description>IXP Route Collector

A Route Collector is a router or appliance running a routing daemon that gathers routing information from IXP members. 

Purpose

The Route Collector&#039;s purpose is to be a reference for the routing information available at the IXP, and has many uses at the IXP.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/route_origin_authorisation?rev=1661498145&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T07:15:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>route_origin_authorisation</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/route_origin_authorisation?rev=1661498145&amp;do=diff</link>
        <description>Route Origin Authorisation

One of the major problems with the Internet Routing Registry is that the information contained therein is historically placed there on trust. While the five RIRs have made big strides to tidy up their instances of the IRR (allowing object creation only by members), the remainder of the IRR still contains a lot of inaccurate, incorrect, and out dated information. And there is no validation or verification of any of the information provided either - any entity can place…</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/route_server?rev=1661508296&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T10:04:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>route_server</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/route_server?rev=1661508296&amp;do=diff</link>
        <description>IXP Route Server

A Route Server has all the features of a Route Collector, but also announces routes to participating IXP members according to their routing policy definitions.

They are implemented using the same specification as for a Route Collector.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream?rev=1661507610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T09:53:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>single_upstream</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/single_upstream?rev=1661507610&amp;do=diff</link>
        <description>Single Upstream

When an entity decides that it is going to set up to be a network operator (usually an Access Provider), they will purchase an Internet connection from a local network operator.

While this has nothing much to do with peering as such, it is included for completeness, to describe the sequence of events a typical newcomer network operator would navigate.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_ixp?rev=1682834062&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T05:54:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>single_upstream_ixp</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_ixp?rev=1682834062&amp;do=diff</link>
        <description>Peering at an IXP

This section discusses how we scale multiple peerings with our network, using what is known as an Internet Exchange Point.

Internet Exchange Points are open neutral interconnects where network operators (with their own Internet resources) are able to freely interconnect. An IXP is the most efficient and effective way of scaling interconnections between network operators in any one location.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_private_peer?rev=1661507701&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T09:55:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>single_upstream_private_peer</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_private_peer?rev=1661507701&amp;do=diff</link>
        <description>Single Upstream &amp; Private Peer

Most network operators first encounter with peering is when they have a simple connection to their upstream provider. This connection usually involves the operator having a static default route configured on the link to the upstream, with the upstream pointing a simple route to their customer.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_two_private_peer?rev=1661507808&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T09:56:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>single_upstream_two_private_peer</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/single_upstream_two_private_peer?rev=1661507808&amp;do=diff</link>
        <description>Single Upstream with Two Private Peers

This section discusses the next stage which is commonly encountered after a network operator establishes their first ever peering connection: another party is interested in peering as well, because they see the benefits that can be gained.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/start?rev=1710241522&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-03-12T11:05:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/start?rev=1710241522&amp;do=diff</link>
        <description>Euro-IX Peering Toolbox

The Peering Toolbox is designed to be a quick access reference guide to network operators who want to understand the steps need to go through to find and set up peering for their network with other infrastructure operators.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/subject-index?rev=1679904327&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-27T08:05:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>subject-index</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/subject-index?rev=1679904327&amp;do=diff</link>
        <description>Subject Index

The Toolbox topics, in alphabetical order.

2

	*  24x7

A

	*  Access Providers
	*  Advanced Peering Scenarios
	*  AS Object
	*  AS Set
	*  Autonomous System Numbers

B

	*  BGP: What it is
	*  BGP: Autonomous System
	*  BGP: Routing Policy
	*  BGP: Multihoming
	*  BGP: Skills Required
	*  BGP: Resources

C

	*  Choosing a Transit Provider
	*  Connecting to another network
	*  Content Distribution Networks
	*  Content Providers
	*  Creating a PeeringDB entry

E

	*  Establishing …</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/terminology?rev=1661488905&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-26T04:41:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>terminology</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/terminology?rev=1661488905&amp;do=diff</link>
        <description>Glossary of Terms

The section of the Toolbox lists terminology used in the Toolbox that is not explained or discussed elsewhere in the Toolbox.

24x7

When the industry talks about 24×7, it simply means that the facility is available 24 hours per day, 7 days per week. In other words,</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/the_internet_routing_registry?rev=1682833158&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T05:39:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>the_internet_routing_registry</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/the_internet_routing_registry?rev=1682833158&amp;do=diff</link>
        <description>The Internet Routing Registry

The Internet Routing Registry (IRR) is used to document policy of autonomous networks taking part in the global Internet. The IRR has been around since the early days of the Internet, starting off as the Routing Arbiter project operated by Merit Network when the Internet was mostly made up of University and Research institution networks.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/the_peering_database?rev=1682833515&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T05:45:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>the_peering_database</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/the_peering_database?rev=1682833515&amp;do=diff</link>
        <description>The Peering Database

The Peering Database is a freely available, user-maintained database of networks which take part in the global Internet. It is considered the authoritative source of all information relating to network operators who participate in peering around the world.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/trouble-ixp?rev=1652686337&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-16T07:32:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>trouble-ixp</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/trouble-ixp?rev=1652686337&amp;do=diff</link>
        <description>Troubleshooting IXP Peering

It&#039;s not the IXP&#039;s fault!

All about:

	*  link quality issues (member to IXP)
	*  L2 issues (esp L2 VPN - sigh!) (member to IXP)
	*  traffic going wrong way (ie peer sends them back via transit)
	*  BGP misconfigurations (same as previous?)</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/trouble-pp?rev=1652686179&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-16T07:29:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>trouble-pp</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/trouble-pp?rev=1652686179&amp;do=diff</link>
        <description>Troubleshooting Private Peering

All about:

	*  link quality issues
	*  L2 issues (esp L2 VPN - sigh!)
	*  traffic going wrong way (ie peer sends them back via transit)
	*  BGP misconfigurations (same as previous?)

 Back to &quot;Troubleshooting Basics&quot; page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/trouble-tools?rev=1710241292&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-03-12T11:01:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>trouble-tools</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/trouble-tools?rev=1710241292&amp;do=diff</link>
        <description>Peering &amp; Troubleshooting Tools

All about:

	*  MTR/traceroute
	*  ping
	*  smokeping
	*  RouteViews
	*  looking glasses
	*  BGP.he.net
	*  RIS (?)
	*  logs
	*  monitored peering mailbox
	*  Peering Management tools (watching where traffic goes - peering vs transit)</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/trouble-transit-v-peer?rev=1652686263&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-16T07:31:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>trouble-transit-v-peer</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/trouble-transit-v-peer?rev=1652686263&amp;do=diff</link>
        <description>Troubleshooting Transit versus Peering

Probably similar to the private peering troubleshooting. But recap good.

All about:

	*  link quality issues
	*  L2 issues (esp L2 VPN - sigh!)
	*  traffic going wrong way (ie peer sends them back via transit)</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/troubleshooting-basics?rev=1710241072&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-03-12T10:57:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>troubleshooting-basics</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/troubleshooting-basics?rev=1710241072&amp;do=diff</link>
        <description>Basic Troubleshooting

This section of the Toolbox documents basic troubleshooting of EBGP in general and peering connectivity in particular.

	*  Peering &amp; Troubleshooting Tools
	*  Troubleshooting Private Peering
	*  Troubleshooting IXP Peering
	*  Troubleshooting Transit versus Peering traffic
	*  Using BGPlay
	*  ...

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/troubleshooting?rev=1652686448&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-05-16T07:34:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>troubleshooting</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/troubleshooting?rev=1652686448&amp;do=diff</link>
        <description>Advanced Peering Troubleshooting

This section of the Toolbox documents advanced troubleshooting of EBGP in general and peering connectivity in particular.

	*  to be done
	*  ...

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/what-is-peering?rev=1660804188&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-18T06:29:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>what-is-peering</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/what-is-peering?rev=1660804188&amp;do=diff</link>
        <description>Interconnections

This section of the Toolbox describes the Internet ecosystem and how network operators interconnect with each other to create what we know as the Internet.

	*  What is a Network Operator
	*  What is Transit
	*  What is Peering
	*  What is an Internet Exchange Point
	*  The Internet Ecosystem

 Back to Home page</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/where-to-peer?rev=1682829551&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T04:39:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>where-to-peer</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/where-to-peer?rev=1682829551&amp;do=diff</link>
        <description>Where to Peer

This section of the Toolbox describes the where a network operator would seek peering. 

There are two paths available:

	*  Private Peering
	*  Public Peering/Internet Exchange Point

Private Peering

Private peering is where there is a private connection between the two network operators for the purpose of exchanging traffic. The following topics cover the aspects needed in any Private Peering setup.</description>
    </item>
    <item rdf:about="https://bgp4all.com.au/pfs/peering-toolbox/why-peer?rev=1682829031&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-30T04:30:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>why-peer</title>
        <link>https://bgp4all.com.au/pfs/peering-toolbox/why-peer?rev=1682829031&amp;do=diff</link>
        <description>The Importance of Peering

In the previous section, we learned how Network Operators fit into the global Internet ecosystem.

We also learned that they can peer with other networks, or buy transit from other networks, or both.

Operators peer with each other to:</description>
    </item>
</rdf:RDF>
