Philip Smith's Internet Development Site

User Tools

Site Tools

Trace:
peering-toolbox:single_upstream

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
peering-toolbox:single_upstream [2022/08/26 18:04] – [Letter of Authority] philippeering-toolbox:single_upstream [2022/08/26 19:53] (current) – [Own Addressing] philip
Line 47: Line 47:
   - Deploy the address block across the network as appropriate (if limited IPv4, NAT may be needed)   - Deploy the address block across the network as appropriate (if limited IPv4, NAT may be needed)
   - Create a Route Object for the address space using the upstream provider's ASN (via the RIR member portal)   - Create a Route Object for the address space using the upstream provider's ASN (via the RIR member portal)
-  - Create a ROA for the address space using the upstream provider's ASN (via the RIR member portal)+  - Create a [[peering-toolbox/route_origin_authorisation|ROA]] for the address space using the upstream provider's ASN (via the RIR member portal)
   - Provide a [[peering-toolbox/single_upstream#letter_of_authority|Letter of Authority]] to their upstream provider requesting their peers and transits accept and propagate the address space (some providers request this, so it is good to be prepared)   - Provide a [[peering-toolbox/single_upstream#letter_of_authority|Letter of Authority]] to their upstream provider requesting their peers and transits accept and propagate the address space (some providers request this, so it is good to be prepared)
   - Organise with the upstream (transit provider) for the address space to be announced globally and routed to them.   - Organise with the upstream (transit provider) for the address space to be announced globally and routed to them.
peering-toolbox/single_upstream.txt · Last modified: 2022/08/26 19:53 by philip