A regional planning commission merged township networks that used private ASNs and now advertises to the public Internet from a public ASN. What must happen to those private ASNs before updates leave the public edge?
Select an answer to reveal the explanation.
Short Explanation
Private ASNs are like internal extension numbers—fine inside the merged townships, wrong on letterhead to the Internet. At the public edge, peel those private hops off so the world only sees your public ASN path.
Full Explanation
Private AS numbers (for example 64512–65534 historically, plus the four-octet private range) must not remain in AS paths advertised to the global Internet. Edge policy removes private ASNs when advertising from the public ASN toward eBGP ISPs. Prepending or inventing AS_TRANS placeholders does not satisfy that cleanup. Synchronization settings are unrelated to private-AS hygiene.