Summary

  • LACNIC’s 13 October account of CaribNOG 32 ties an operator’s own IP addresses and ASN to multihoming, private peering and fewer renumbering steps when changing providers.
  • The advice describes a capability, not a reported deployment: an ASN does not guarantee another network will accept a route or a content provider will install a cache.

Analysis

A familiar recommendation in a Caribbean setting

CaribNOG 32 met in Willemstad, Curaçao, from 7 to 9 October. LACNIC’s 13 October recap says the closing technical session moved from concepts to router configuration. It ends with a message the registry calls familiar: operators should obtain their own IP addresses and ASN.

The post connects those resources with multihoming, private peering and avoiding renumbering when an upstream changes. It also says content providers check an operator’s addresses and ASN when deciding whether to place a cache in its network. No operator that changed providers, cache installation or measured outcome is identified. This is advice from a conference report, not a new allocation rule or evidence of adoption in the Caribbean.

The number is a routing-policy handle

An IP prefix identifies destinations; an autonomous system number identifies a network’s routing policy in inter-domain routing. RFC 1930 says an AS should represent one clearly defined routing policy and cautions that a single-homed site generally does not need a separate AS just to have one.

LACNIC’s current ASN request criteria make the distinction operational. An applicant must need to interconnect with independent ASes now or plan to do so within six months, and describe its routing policy, intended AS peers and announced addresses. LACNIC says an unused assignment may be revoked after that period.

Portability still depends on other networks

An independently assigned prefix and ASN can let an operator plan announcements across multiple upstreams rather than rely on a provider’s numbering. The route still has to be announced, accepted and carried. Filters, routing authorizations, contracts, capacity and physical paths remain relevant. A registry entry is not a circuit, and an ASN cannot compel another network to carry a route.

The same limit applies to caches. Resource records may help a content provider assess a network, as LACNIC says; they do not establish that demand, facilities, backhaul or commercial terms justify an installation. The report gives no threshold or cache decision to inspect.

Sources