Understanding the Role and Responsibilities of a Sponsoring Local Internet Registry

Welcome to my latest blog post where we delve into the pivotal role of a Sponsoring Local Internet Registry (LIR) and their importance in managing end user relationships in the realm of Internet resource allocation. This article is inspired by an instructional video from the RIPE NCC, presented by IP resource analyst and part-time trainer, Yu and Mackey. We’ll break down the hierarchy of Internet resource management, the responsibilities of a sponsoring LIR, and best practices for maintaining a healthy and compliant operation.

The Hierarchy of Internet Resource Management

Before we dive into the specifics of a local internet registry’s duties, let’s establish the hierarchy that exists within internet resource management. At the top, we have IANA (the Internet Assigned Numbers Authority), which oversees global IP address allocation, among other critical functions. Below IANA are the five Regional Internet Registries (RIRs), each serving a different portion of the globe. RIPE NCC, for instance, covers Europe, Central Asia, and parts of the Middle East.

Members of an RIR, such as RIPE NCC, are recognized as Local Internet Registries. LIRs are responsible for the distribution and management of IP addresses within their region. They serve a variety of end users, which can include companies, charities, schools, or even individuals.

Responsibilities of a Sponsoring LIR

As a sponsoring LIR, there’s a myriad of responsibilities that you must uphold. Not only are you tasked with requesting and assigning Internet resources on behalf of your end users, but you also need to ensure that the registry remains updated, handle abuse-related matters, and perform due diligence ahead of any requests sent to the RIPE NCC. Additionally, you’ll represent your end user in any communication with the RIPE NCC.

Let’s look at these responsibilities in a structured format:

Independent Resources and Transfers

It’s crucial to understand that independent resources, such as IPv6 provider-independent space or AS numbers, are owned by the end user, not the LIR. These resources can be transferred between sponsoring LIRs if, for instance, an end user changes their service provider. However, the LIR must ensure that these transfers are recorded accurately, and in cases where resources are no longer needed, they are returned to the RIPE NCC, not retained by the LIR.

IPv4 resources are a special case due to scarcity, and typically, end users will only receive IPv4 resources from the LIR’s own allocation. However, the LIR may assist the end user in obtaining IPv4 through the RIPE NCC’s Transfer Listing Service.

Updating the Registry and Handling Abuse Complaints

Keeping the RIPE registry up-to-date is not just good practice, it’s a requirement. Whether it’s a simple name change or a more significant event like a merger or acquisition, these changes need to be reported to the RIPE NCC promptly. This ensures the integrity of the registry and the rightful ownership and use of the resources.

Abuse complaints, which can arise from DDoS attacks, spam, or malware, need to be addressed either by the LIR or the end user. If the end user is unresponsive, the responsibility falls on the LIR. In extreme cases, where the end user is consistently unreachable, the LIR may consider terminating the sponsorship agreement.

Do’s and Don’ts for Sponsoring LIRs

To encapsulate the essence of a sponsoring LIR’s responsibilities, here’s a quick list of do’s and don’ts:

• Do keep in touch with your end users to monitor their resource usage and changes in their status or structure.
• Don’t allow end users to contact the RIPE NCC directly; the LIR should be the intermediary.
• Do keep the RIPE NCC informed of all changes involving your end users.
• Don’t use end users’ internet resources for your LIR’s operations.

Conclusion

In summary, a sponsoring LIR plays a critical role in managing internet resources for end users. By maintaining open communication lines, ensuring accurate registry data, handling abuse complaints, and performing due diligence, LIRs can provide excellent service while adhering to the rules set out by the RIPE NCC. Remember, the RIPE NCC is always available to assist with any questions or concerns related to your role as a sponsoring LIR.

If you’re involved in managing a local internet registry or are an end user seeking to understand your relationship with your LIR, I hope this article has been informative. For further guidance and resources, do not hesitate to reach out to the RIPE NCC directly.

Understanding Subnetting in Practical Terms: Designing Coffee Shop Networks

Welcome back to another blog post where we dive into the riveting world of network design. Today, we’re scratching the itch of a very interesting scenario: subnetting for coffee shops. I’ve been tasked with creating a network design that provides a robust and efficient IP addressing scheme for a series of new coffee shops. So, grab a cup of joe, and let’s embark on this caffeinated networking adventure together.

Introduction to the Scenario

Imagine you are launching a series of coffee shops, each requiring a distinct network to support employees, devices, and guests. You have a single /24 network at your disposal: 10.1.1.0/24. The goal is to carve out this network to accommodate three coffee shops, each with specific host requirements.

Each coffee shop consists of:

• 5 employees
• 1 server
• 2 Raspberry Pis
• 2 Wireless Access Points (WAPs)
• Up to 20 guests at a time

Doing the math, that’s approximately 30 hosts, but let’s round it up to 40 hosts for some extra breathing room. The challenge is to create subnets based on these host requirements and not just arbitrary network divisions.

Technical Breakdown

The first step in subnetting, based on host requirements, involves determining the number of host bits needed to support the required number of devices. Using the principle that the number of hosts is 2ⁿ – 2 (where n is the number of host bits), we can deduce the correct subnet mask.

Based on our requirements, we need to save (or reserve) 6 bits for hosts. Therefore, if we start with a /24 network, we need to convert it into a /26 network, which will provide us with 64 IP addresses per subnet, 62 of which are usable for hosts. In binary, the subnet mask for a /26 network is 11111111.11111111.11111111.11000000, which translates to 255.255.255.192 in decimal notation.

Subnet Allocation

With our subnet mask determined, we can now allocate subnets for each coffee shop. Since we are dealing with a /26 subnet, we will increment our networks by 64 for each subnet. Here’s how the networks for the three coffee shops would be divided:

Conclusion

Subnetting can initially seem daunting, but when you apply it to a real-world situation like setting up networks for coffee shops, it becomes much more approachable. By breaking down the requirements, calculating the number of needed host bits, and determining the subnet mask, we’ve successfully created a subnetting scheme that ensures each coffee shop has a network tailored to its specific needs. Remember, practice makes perfect, and the more you work with subnetting, the more intuitive it becomes. So keep brewing up those network designs!