Supplier IP Import Guide

For the i.lease / idolist Lease Out workspace

Suppliers can import owned IPv4 prefixes into i.lease in two ways:

1. Manual CIDR import: paste the prefixes you want to onboard.
2. Import by Org ID: let the system discover eligible prefixes from approved Org IDs.

After import, the prefixes continue through the same operational flow:
Select IP, Set Up IP Details, Set Pricing,
and Review & Submit.

Latest Workflow Demo Video

Watch the latest supplier-import workflow demo below:

Open video in new tab

Before You Start

1. Make sure you control the IPv4 resources you want to import.
2. Prepare clean CIDR entries, one per line, or confirm that your Org IDs are already approved in the system.
3. Decide whether each prefix will be platform_managed or supplier_managed.
4. For platform-managed delivery, complete the required maintainer or ownership checks before final submission.

Method 1: Manual CIDR Import

Step 1: Open Lease IP to Monetize

In Lease Out, open Lease IP to Monetize. Paste one CIDR per line,
then click Add IPs.

Use this method when you already know exactly which prefixes you want to list.

Manual CIDR import starts from Lease Out > Lease IP to Monetize.

Step 2: Choose the Prefixes to Continue

After the session is created, the Select IP to Monetize step shows the imported prefixes.
Review the list, keep only the prefixes you want to proceed with, and confirm the RIR and lease term for each row.

If a line is invalid, it will not move forward until the CIDR is corrected.

Select the prefixes that should enter setup and pricing.

Step 3: Set Up IP Details

In Set Up IP Details, define how each prefix will be prepared for monetization.
This is where you confirm items such as split behavior, reservation handling, and maintainer readiness.

If a prefix is set to platform_managed, the maintainer verification must pass before you submit the session.

Use the setup step to confirm delivery mode and operational readiness.

Platform Delivery: Add i.lease Maintainer Information by RIR

If the supplier chooses Platform delivery, open the prefix setup page and switch the
Setup mode to Platform delivery. The page then shows the exact
i.lease maintainer entries that the supplier must add on the RIR side before clicking
Confirm maintainer setup.

When Platform delivery is selected, the setup page shows the required maintainer entries and the confirm button.

Add the following maintainer values according to the RIR of the prefix:

RIPE Steps

1. Open RIPE Database Webupdates and sign in with your RIPE NCC Access account.
2. Search for the target resource object, usually the relevant inetnum that contains the prefix.
3. Edit the object in Webupdates.
4. Add HK-LARUS-1-MNT to mnt-by, mnt-lower, and mnt-routes as required by the i.lease setup screen.
5. Submit the update, then return to i.lease and click Confirm maintainer setup.

APNIC Steps

1. Log in to MyAPNIC.
2. Open Resources > Maintainers if you need to add or manage the maintainer object in your account.
3. If you need to create or edit Whois objects directly, use Resources > Whois updates.
4. Update the relevant resource object so that MAINT-LCS-HK appears in the maintainer-protected fields required for the prefix.
5. Save the change, then return to i.lease and run Confirm maintainer setup.

AFRINIC Steps

1. Log in to MyAFRINIC to manage your account and resource information.
2. If you need to create or inspect a maintainer object, use the AFRINIC Whois workflow and query tools at
   https://afrinic.net/whois-web/public/query.
   
3. Ensure the relevant Whois object includes both LARUS-SERVICE-MNT and CIL1-MNT in the maintainer-related fields required for the resource.
4. If the maintainer object itself needs to be created or attached to resources, follow AFRINIC’s Whois maintainer procedure and contact AFRINIC support when required by their process.
5. After the Whois update is visible, return to i.lease and click Confirm maintainer setup.
6. Ask the supplier to update the relevant RIR object with the required i.lease maintainer entry or entries.
7. Return to the setup page and click Confirm maintainer setup.
8. If Whois verification passes, the page confirms that the platform maintainer is set correctly.
9. If verification fails, use the missing-entry hint on the page to see which maintainer value still needs to be added.

This verification step is required for prefixes that will be handled by the platform after payment.

Step 4: Set Pricing

Open Set Pricing and assign the pricing model for each selected prefix.
Review the rows carefully so the prefixes moving into review already have the intended commercial terms.

Pricing is configured per selected prefix before marketplace submission.

Step 5: Review and Submit

The last step is Add IP to Marketplace. Review the selected prefixes, confirm the
key ToS points, complete the required checkboxes, and submit the batch.

After submission, the prefixes move into the platform review workflow instead of becoming instantly live.

Review the import batch and submit it to marketplace review.

Method 2: Import by Org ID

Use Import by Org ID when the supplier already has approved Org IDs in the system.
This flow is useful when you want i.lease to discover eligible prefixes for you instead of pasting CIDRs manually.

Step 1: Select Ready Org IDs

Open Lease Out > Import by Org ID, then select one or more Org IDs with a
Ready status.

Step 2: Review the Discovery Preview

Once selected, i.lease searches the related RIR / RDAP data and shows a discovery preview.
The preview tells you which prefixes are importable, which ones are skipped, and why.

Step 3: Continue With Discovered IPs

Click Continue with discovered IPs to create a new import session. From that point on,
the process joins the same Select IP, Set Up, Pricing,
and Review workflow used by manual CIDR import.

Import by Org ID shows both the available Org IDs and the discovery preview in one workflow.

What Happens After Submission

Once the session is submitted, valid selected prefixes are written into the formal supplier-import records.
You can then track their operational state in My Monetized IPs.

Common next statuses include pending review, pending document follow-up, sent to abuse email
(waiting online signature), pending LOA-A review, and approved or rejected outcomes.

LOA-A: Platform-Managed Signing Workflow

This step applies only to prefixes configured as Platform delivery /
platform_managed.

After the import batch is submitted, i.lease generates an LOA-A file and sends it to the supplier
company's stored abuse email. The supplier then completes the LOA-A online signature
on the same prefix detail page and submits it for admin review.

The LOA section in My Monetized IPs shows the current LOA-A status, available actions, and the next step the supplier needs to complete.

How to Complete the LOA-A Step

1. Open Lease Out > My Monetized IPs.
2. Open the relevant prefix detail page after the batch has been submitted.
3. Check the LOA section and confirm the current status.
4. If the status is Sent to Abuse Email, action is required from supplier side.
5. Use Download LOA-A Template if you need to preview the current LOA-A file from the system.
6. Use Resend LOA-A if the original email was missed or the supplier needs the file sent again.
7. Click Sign LOA-A Online in the detail page.
8. In the signing dialog, review the LOA-A preview and click Reload if the document did not load correctly.
9. Fill Signatory Name and Signatory Title.
10. (Optional) Upload Company Chop / Seal image in PNG/JPG/JPEG/WEBP format (max 4MB).
11. Draw the signature in the signature pad and click Confirm.
12. The system generates the signed LOA-A PDF and submits it for review. The status then moves to Pending LOA-A Review.
13. Wait for admin review. If approved, the status becomes Approved. If rejected, the page shows the reject reason and you can submit a corrected online signature again.

LOA-A Status Guide

Where the LOA-A Email Is Sent

For the platform-managed flow, LOA-A delivery uses the supplier company's stored abuse email in i.lease.

1. Open Company Settings > Company Profile.
2. Edit the supplier company record.
3. Check that Abuse Handling Email contains the mailbox that should receive the LOA-A message.
4. Save the profile before you resubmit or resend the LOA-A email.

If the company abuse email is empty or invalid, the LOA-A email cannot be sent successfully.

Supplier-Managed Ownership Confirmation by Email

This step applies to prefixes configured as Supplier delivery, not
Platform delivery.

1. Submit the import session normally from the Review page.
2. After submission, i.lease sends an ownership-confirmation email for the prefix.
3. The confirmation recipient is resolved from the prefix’s RIR records.
   The system sends the ownership-confirmation email to the WHOIS admin email found for the prefix.
   
4. The recipient opens the confirmation link in the email.
5. Once the link is confirmed, the offer is marked as ownership-confirmed.
6. For supplier-managed offers, ownership confirmation is the trigger that allows the offer to move forward automatically.

If the RIR records for the prefix do not expose a valid WHOIS admin email,
the ownership email cannot be sent successfully.

How to Resend the Ownership Confirmation Email

1. Open My Monetized IPs.
2. Open the relevant prefix detail page.
3. Use the ownership-confirmation resend action if the email needs to be sent again.

Use this resend flow when the WHOIS admin mailbox missed the first email or the original token expired.

Company Abuse Email: Where to Set It

The company abuse email in i.lease is a separate setting from the WHOIS admin ownership-confirmation recipient.

Current product behavior:

• Ownership confirmation recipient: resolved from the prefix’s WHOIS admin email in RIR records.
• Company abuse email in i.lease: managed in the supplier company profile and used as the company’s stored abuse contact. It is also the email used for LOA-A delivery in the platform-managed flow.

How to Set the Company Abuse Email in i.lease

1. Open Company Settings > Company Profile.
2. Open the company record you want to edit.
3. Click the edit action for the company profile.
4. Update the abuse contact fields:
   Abuse Handling Name,
   Abuse Handling Phone,
   Abuse Handling Email,
   and Abuse Handling Address.
   
5. Save the company profile.

If you want ownership-confirmation emails to reach a different mailbox, changing the company profile alone is not enough.
You must update the WHOIS admin contact information in the relevant RIR records for that prefix.

Quick Tips

• Use one CIDR per line for manual import to avoid parsing errors.
• Only prefixes that pass validation move into the later pricing and review steps.
• For platform-managed delivery, finish the maintainer checks before final confirmation.
• If you already manage prefixes through approved Org IDs, use Org ID discovery to speed up onboarding.