IPV4 ROUTING AUTHORIZATION — PREPARATION TEMPLATE This unsigned template grants no permission. Obtain the recipient's required form and have the authorized resource-holder representative review it. Complete all placeholders. Keep exactly one scope option below. Issue date: [YYYY-MM-DD] Effective period: [START AND END, OR EXPLICITLY AGREED VALIDITY] Reference: [CHANGE OR AGREEMENT REFERENCE] Issuer / resource holder: [LEGAL NAME] Registry organization reference: [RIR AND ORGANIZATION IDENTIFIER] Registered address: [ADDRESS] Recipient provider: [LEGAL NAME] Recipient provider ASN: [ASN] Customer / network operator: [LEGAL NAME] Authorized IPv4 prefixes: [EXACT PREFIX] [ADDITIONAL EXACT PREFIX, IF APPLICABLE] KEEP ONE SCOPE OPTION AND REMOVE THE OTHER: Option A — customer origination, provider transit The issuer authorizes [CUSTOMER LEGAL NAME], using origin [CUSTOMER ASN], to originate the prefixes listed above. The recipient provider is authorized to accept and propagate those customer-originated routes within the agreed service. This does not authorize the provider to substitute its own origin ASN. Option B — provider origination The issuer authorizes [PROVIDER LEGAL NAME], using origin [PROVIDER ASN], to originate the prefixes listed above within the agreed service. Any additional providers and their permitted roles: [LIST EXPLICITLY, OR STATE NONE; CONFIRM EACH RECIPIENT'S ACCEPTANCE] This authorization does not transfer resource registration or ownership. IRR objects, RPKI authorizations and BGP configuration are managed separately. Changes or withdrawal must be coordinated through the contacts below and the applicable service agreement. Signer: [FULL NAME] Role: [ROLE AND BASIS OF AUTHORITY] Organization: [LEGAL NAME] Verification contact: [EMAIL AND TELEPHONE] Signature: [SIGNATURE IN THE FORMAT ACCEPTED BY THE RECIPIENT] Signed on: [YYYY-MM-DD]