Bring a RIPE IPv6 PI /48 to Google Cloud (BYOIP)

What you need

• A RIPE IPv6 PI /48 (or a /48 from a larger allocation) that you control — this becomes your Public Advertised Prefix.
• An RPKI ROA authorizing Google's ASN AS396982 to originate your prefix (max length /48).
• Reverse-DNS validation of the prefix — Google verifies ownership using ROA plus reverse DNS, and may ask for a PTR/TXT validation token.
• The prefix must not be advertised elsewhere when you announce it on Google Cloud.

What GetIPv6 does (your sponsoring LIR)

• Creates and maintains the ROA for AS396982 (max length /48) in RIPE RPKI.
• Sets up reverse DNS for the /48 and adds any PTR/TXT validation token Google requests.
• Provides a Letter of Authorization (LoA) if requested.
• Keeps the /48 un-advertised during onboarding.

Google-side steps

1. Create a Public Advertised Prefix (PAP) for your /48. Google validates it against the ROA and reverse DNS — this is the step that can take time while checks propagate.
2. Create Public Delegated Prefixes (PDP) from the PAP. Valid top-level PDP lengths are /32, /40, /48, /56; a sub-prefix can be the same size or smaller, but no more than 24 bits longer than its parent.
3. Allocate addresses from the delegated prefix to your Google Cloud resources (VMs, load balancers).
4. Announce the PAP when you're ready. Withdraw any other origin for the /48 first.

Order of operations that matters

• The ROA (AS396982) and reverse DNS must be in place before you create the PAP — validation fails otherwise.
• Stop advertising the /48 elsewhere before you announce on Google Cloud — two origins for the same prefix will conflict.

After onboarding

• You control the announcement — withdraw the PAP and move the /48 elsewhere at any time.
• The same /48 can be prepared for other clouds later; only one may advertise it at a time.