Authorize Recipients of Delegated Blocks to Sign ROAs

LAC-2020-10-v1 LAC-2020-10-v2 Vs
References:
New
Deleted
Modified
Authors

Name: Hernan Moguilevsky
Email: noc.hernan@gmail.com
Organization: Community

Name: Hernan Moguilevsky
Email: noc.hernan@gmail.com
Organization: Community

Summary

Once this policy is implemented, the technical contact of the organization receiving an IP prefix delegation from a provider will be able to sign the ROAs for said prefix for the duration of the delegation.

OUnca ve this policy isz implementead,a thela polítechnica, l contact of the oOrganizatcioón receiving ptora de un bloque IP prefix delegatidon frpomr aun provieedor será willcapaz bde firmabr le to sign the ROAs fopara sadidcho prefix fjor thmientras dure lation of the delegatcioón.

Rationale (Describe the problem you intend to solve)

This proposal seeks to solve the problems that those who receive prefixes delegated by their providers have for signing the ROAs for those prefixes.

This proposal seeks to solve the problems that those who receive prefixes delegated by their providers hcave fnnort signing the ROAs for those prefixes.

Current text

2.3.2.13. Registering assignments
All IPv4 address block assignments of a /29 or larger block made by an ISP to customers connected to their network and users of services provided must be registered on LACNIC's WHOIS database no more than 7 days after the assignment. The information available in the WHOIS database will also be used by LACNIC when analyzing additional IPv4 address block requests made by the ISP.

Assignment registration is also necessary for the following reasons:

- To ensure that the IR has completed or is close to completing address space allocation such that the allocation of additional space is justified.
- To inform the Internet community which organization is using the IPv4 address space, including the point of contact in case of operational, security or other types of issues.
- To study IPv4 address allocation within the region.
- To facilitate the geolocation of sub-assignments made by members in our region.

2.3.2.13. Registerationg aof Assignments
All IPv4 address block assignments of a /29 or larger block made by an ISP to customers connected to their network and users of services provided must be registered on LACNIC's WHOIS database no more than 7 days after the assignment. The information available in the WHOIS database will also be used by LACNIC when analyzing additional IPv4 address block requests made by the ISP.

Assignment registration is also necessary for the following reasons:

- To ensure that the IR has completed or is close to completing address space allocation such that the allocation of additional space is justified.
- To inform the Internet community which organization is using the IPv4 address space, including the point of contact in case of operation
a problems, security or other types of issues, etc.
- To study IPv4 address allocation within the region.
- To facilitate the geolocation of sub-assignments made by members in our region.

New text

2.3.2.13. Registration of Assignments
All IPv4 assignments of prefixes equal to or larger than a /29 made by an ISP to customers connected to their network and to users of the services they provide must be registered in LACNIC's WHOIS database not more than 7 days after the assignment. The information available in the WHOIS database will also be used by LACNIC when analyzing additional IPv4 address requests submitted by the ISP.

As long as the prefixes are registered in the WHOIS database, the receiving client will have the exclusive right to create and manage the RPKI Route Origin Authorization (ROA) certificates for said resources.
Such certificates will be managed by the technical contact of the receiving organization.

Assignments must also be registered for the following reasons:
- To ensure that the IR has completed or is close to completing address space allocation such that the allocation of additional space is justified.
- To inform the Internet community which organization is using the IPv4 address space, including the point of contact in case of operational, security or other types of issues.
- To study IPv4 address allocation in the region.
- To facilitate the geolocation of sub-assignments made by members in our region.
- To strengthen Internet routing security, ensuring the proper implementation of RPKI.

2.3.2.13. Registration of Assignments
All IPv4 a
ddress block assignments of prefixes equal to/29 or larger thanblock a /29
made by an ISP to customers connected to their network and to users of the services they provided must be registered ion LACNIC's WHOIS database not more than 7 days after the assignment. The information available in the WHOIS database will also be used by LACNIC when analyzing additional IPv4 address block requests submittaded by the ISP.

As long as the prefixes are registered in the WHOIS database, the rec
eiving clpient will have the exclusive right to create and manage the RPKI Route Origin Authorizations (ROA) certificates) for said resources.
Such certificateAs wsill be managed by the technical comentact of the receiving organizstration.

Ass
ignments must also bne rcegisstearedy for the following reasons:
- To ensure that the IR has completed or is close to completing address space allocation such that the allocation of additional space is justified.
- To inform the Internet community which organization is using the IPv4 address space, including the point of contact in case of operation
a problems, security or other types of issues, etc.
- To study IPv4 address allocation
within the region.
- To facilitate the geolocation of sub-assignments made by members in our region.

- To strengthen Internet routing security, ensuring the proper implementation of RPKI.

Additional information

The community has been discussing the need for this policy.
RPKI adoption continues to grow, so signing the ROAs should no longer depend on the holder of the recourses we have been delegated.

The community has been discussing the need for this policy.
RPKI adoption continues to grow,
so siganingd thwe ROAs should no longer depend on the holder of the recsourses we have been delegated to sign the ROAs.

References

-

-