Summary

  • Fernando Frediani coauthored both versions of LAC-2019-6 with Jordi Palet Martínez and Carlos Friacas. LACNIC implemented the rule on 22 January 2020.
  • The rule places exclusivity with the resource recipient while allowing a third party to use the resource with the recipient's authorization, subject to other current policies. LACNIC's present manual retains that wording.

“Exclusive” is a word that can make a network operator reach for a lawyer. A customer may run addresses through a different organisation's network; a route may originate under another ASN. Who gets to decide whether that use belongs to the recipient or crosses the registry's line? Fernando Frediani, an infrastructure engineer whose LACNIC speaker biography spans datacentres and Internet providers, helped put an answer into the rulebook.

The LAC-2019-6 policy history lists Frediani alongside Jordi Palet Martínez and Carlos Friacas as authors of both drafts. Their change lifted a description of the Internet registry system out of an IPv4-only chapter and placed it among general definitions. The resulting sentence reaches addresses and ASNs. It says LACNIC and national-registry resources are used exclusively by their recipients or by third parties those recipients authorize, when the policies in force permit the arrangement. The recipient holds the key; the key still has to fit the other locks in the manual.

LACNIC's staff analysis supplied three practical pictures. A recipient can originate its resource under its own ASN. A recipient can register a client reassignment in WHOIS. Another organisation's ASN can originate the block after prior authorization. These were staff interpretations of the proposed text, not a census of networks already doing each thing. The same analysis expected no change to the registration system. This was a change in the rule for reading the ledger, not a new ledger.

The authors also recommended that authorizations could be verified using RPKI. “Recommended” matters: a verifier can look for technical evidence, while the actual permission still rests with the recipient and the rest of the policy. There is no magic packet that turns an unauthorized arrangement into an authorized one.

LACNIC implemented LAC-2019-6 on 22 January 2020. Its current Policy Manual, version 2.21, still carries the clause in definition 0.10. Frediani and his coauthors left a small but durable instruction: when an address appears outside the recipient's own network, ask for the recipient's authorization and the governing policy before deciding what “exclusive” means.