User Tools

Site Tools


peering-toolbox:single_upstream_private_peer

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
peering-toolbox:single_upstream_private_peer [2022/08/01 17:34] – [Single Upstream & Private Peer] philippeering-toolbox:single_upstream_private_peer [2022/08/26 18:07] – [Letter of Authority] philip
Line 10: Line 10:
   - [[single_upstream_private_peer#bgp_with_upstream|Adding the peering, introducing BGP with the upstream]]   - [[single_upstream_private_peer#bgp_with_upstream|Adding the peering, introducing BGP with the upstream]]
  
-A diagram describing the scenario being discussed is below.+A diagram showing the typical physical layout of this scenario is shown below
  
 {{:peering-toolbox:1-private-peer.png?400| }} {{:peering-toolbox:1-private-peer.png?400| }}
Line 65: Line 65:
 The next step is to provide them with a [[single_upstream#letter_of_authority|Letter of Authority]] (if required) which requests their upstreams and peers to allow your address space originated by your ASN. The next step is to provide them with a [[single_upstream#letter_of_authority|Letter of Authority]] (if required) which requests their upstreams and peers to allow your address space originated by your ASN.
  
-LOAs are not usually required as a ROA should be enough to prove the holder of the address space and the origin ASN. But some operators insist on the LOA, still.+LOAs are not usually required as a ROA is enough to prove the holder of the address space and the origin ASN. But some operators still insist on LOA.
  
 ==== ROA and Route Object ==== ==== ROA and Route Object ====
peering-toolbox/single_upstream_private_peer.txt · Last modified: 2022/08/26 19:55 by philip