Keyboard Shortcuts
Thread View
j: Next unread messagek: Previous unread messagej a: Jump to all threadsj l: Jump to MailingList overview
Hi, I'm Policy WG Chair of JP Open Policy Forum, Toshio Tachibana.
We had an opinion collection meeting with our community in Japan, and would like to share our input.
For, prop-105, we support this proposal as it is.
For prop-107, while there was no concern expressed over the proposal, some questions were also raised about the needs of the proposal:
<prop-107 related question as below>
------------------------------------------------------------------------ Q1. Does it require the needs based criteria, i.e., plan to be multi- homed for ASN transfer? ------------------------------------------------------------------------ Q2. If the answer to Q1 is yes, in what kind of cases would one wish to transfer ASN while you can still receive assignments from APNIC? ---- We tried some case studies but one has identified clear needs:
a. M&A or business purchase You can transfer IPv4 and ASN at the same time under the current policy.
b. To receive 2 byte ASN rather than 4 byte Assignment rate of 4 byte ASN in the region is relatively high, and there are still 2 byte ASN remaining in APNIC pool.
c. Transfer a part of IPv4 allocations and ASN If IPv4 allocations are only partially transferred to another organization, the transfer source is likely to need the existing ASN to advertise the remaining IPv4 blocks, which were not transferred. ------------------------------------------------------------------------
Related to Q2., there was a comment expressed that this policy may only apply to a very rare case. e.g., an organization has multiple ASNs, and some of it is unused, and there is an organization that wishes to receive this particular ASN range, without M&A or business purchase.
====
Best regards, --- TACHIBANA toshio
Hi Tachibana-san,
Thank you for your comments.
| Q1. Does it require the needs based criteria, i.e., plan to be multi- | homed for ASN transfer?
Yes, from the policy text:
- Proposed policy solution
AS numbers may be transferred if recipient of the transfer will meets the criteria under the current APNIC policy for an assignment of AS numbers.
| Q2. If the answer to Q1 is yes, in what kind of cases would one wish | to transfer ASN while you can still receive assignments from APNIC?
I heard that there are a few requests to transfer the AS number with IPv4 address at the same time with the 'transfer' policy.
As you wrote in 'a.', is is possible use another policy if that is M&A case, but there would be some cases such as the case you mentioned 'c.'
| c. Transfer a part of IPv4 allocations and ASN | If IPv4 allocations are only partially transferred to another | organization, the transfer source is likely to need the | existing ASN to advertise the remaining IPv4 blocks, which | were not transferred.
There will be other cases that organizations who has IPv4 address and ASN want to transfer ASN and almost all of IPv4 address (they want to keep small part of address). This will happen in an organization such as old university with historical address.
Yours Sincerely, -- Tomohiro Fujisaki
From: TACHIBANA toshio toshio@aniani.com Subject: [sig-policy] Comments for prop-105 and prop-107. Date: Mon, 26 Aug 2013 17:22:07 +0900
| Hi, I'm Policy WG Chair of JP Open Policy Forum, Toshio Tachibana. | | We had an opinion collection meeting with our community in Japan, and | would like to share our input. | | For, prop-105, we support this proposal as it is. | | For prop-107, while there was no concern expressed over the proposal, | some questions were also raised about the needs of the proposal: | | <prop-107 related question as below> | | ------------------------------------------------------------------------ | Q1. Does it require the needs based criteria, i.e., plan to be multi- | homed for ASN transfer? | ------------------------------------------------------------------------ | Q2. If the answer to Q1 is yes, in what kind of cases would one wish | to transfer ASN while you can still receive assignments from APNIC? | ---- | We tried some case studies but one has identified clear needs: | | a. M&A or business purchase | You can transfer IPv4 and ASN at the same time under the | current policy. | | b. To receive 2 byte ASN rather than 4 byte | Assignment rate of 4 byte ASN in the region is relatively high, | and there are still 2 byte ASN remaining in APNIC pool. | | c. Transfer a part of IPv4 allocations and ASN | If IPv4 allocations are only partially transferred to another | organization, the transfer source is likely to need the | existing ASN to advertise the remaining IPv4 blocks, which | were not transferred. | ------------------------------------------------------------------------ | | Related to Q2., there was a comment expressed that this policy may only | apply to a very rare case. | e.g., an organization has multiple ASNs, and some of it is unused, and | there is an organization that wishes to receive this particular ASN | range, without M&A or business purchase. | | | ==== | | Best regards, | --- | TACHIBANA toshio | * sig-policy: APNIC SIG on resource management policy * | _______________________________________________ | sig-policy mailing list | sig-policy@lists.apnic.net | http://mailman.apnic.net/mailman/listinfo/sig-policy |
On 8/26/13 03:22 , TACHIBANA toshio wrote: ...
For prop-107, while there was no concern expressed over the proposal, some questions were also raised about the needs of the proposal:
<prop-107 related question as below>
...
Q2. If the answer to Q1 is yes, in what kind of cases would one wish to transfer ASN while you can still receive assignments from APNIC?
We tried some case studies but one has identified clear needs: a. M&A or business purchase You can transfer IPv4 and ASN at the same time under the current policy. b. To receive 2 byte ASN rather than 4 byte Assignment rate of 4 byte ASN in the region is relatively high, and there are still 2 byte ASN remaining in APNIC pool. c. Transfer a part of IPv4 allocations and ASN If IPv4 allocations are only partially transferred to another organization, the transfer source is likely to need the existing ASN to advertise the remaining IPv4 blocks, which were not transferred.
Related to Q2., there was a comment expressed that this policy may only apply to a very rare case. e.g., an organization has multiple ASNs, and some of it is unused, and there is an organization that wishes to receive this particular ASN range, without M&A or business purchase.
There are two other potential use cases;
- Similar to your last comment, organization whats a low numbered 2, 3, or 4 digit ASN and is willing to buy unused ASN from someone else.
- ASN has been loaned out to a project or customer, maybe for a long time, want/need to update registry info to reflect reality of the situation, M&A Transfer doesn't necessarily fit the reality of the situation.
On Aug 26, 2013, at 06:02 , David Farmer farmer@umn.edu wrote:
On 8/26/13 03:22 , TACHIBANA toshio wrote: ...
For prop-107, while there was no concern expressed over the proposal, some questions were also raised about the needs of the proposal:
<prop-107 related question as below>
...
Q2. If the answer to Q1 is yes, in what kind of cases would one wish to transfer ASN while you can still receive assignments from APNIC?
We tried some case studies but one has identified clear needs: a. M&A or business purchase You can transfer IPv4 and ASN at the same time under the current policy. b. To receive 2 byte ASN rather than 4 byte Assignment rate of 4 byte ASN in the region is relatively high, and there are still 2 byte ASN remaining in APNIC pool. c. Transfer a part of IPv4 allocations and ASN If IPv4 allocations are only partially transferred to another organization, the transfer source is likely to need the existing ASN to advertise the remaining IPv4 blocks, which were not transferred.
Related to Q2., there was a comment expressed that this policy may only apply to a very rare case. e.g., an organization has multiple ASNs, and some of it is unused, and there is an organization that wishes to receive this particular ASN range, without M&A or business purchase.
There are two other potential use cases;
- Similar to your last comment, organization whats a low numbered 2, 3, or 4 digit ASN and is willing to buy unused ASN from someone else.
This seems to be a unique pathology to the ARIN region. Other regions don't seem to have any difficulty with 4-byte ASNs.
Owen
Activity Summary
- 3678 days inactive
- 3678 days old
- sig-policy@lists.apnic.net
- 4 participants
- 3 comments