Re: [sig-policy] A second policy proposal for the Policy SIG
JORDI PALET MARTINEZ wrote:
> ...
> 1) I don't think multihomed sites must have higher priority to those that
> need portable block and aren't multihomed.
Mutihomed end sites are the problem to be solved now.
An end site which needs only a single link can connect
to IPv6 internet with non-portable assignment.
> 2) My understanding is that under current APNIC IPv6 Address Allocation and
> Assignment Policy, the university case that I've provided will not fall
> within the initial allocation criteria. The reason for that is the existing
> end user definition. However you seem to agree with me that it should be
> allocated a portable block. So there are to choices here, my PI proposal, or
> the modification of the end-user definition and the initial allocation
> criteria in the existing policy (same proposal as made this week in RIPE).
I think portable assigment becomes too broad if the end sites
which want to avoid renumbering are admitted.
> 3) Critical infrastructures, under the current APNIC IPv6 Address Allocation
> and Assignment Policy, receive a /32. Typically those sites will have more
> than enough with a /48. Consequently the rational in your proposal doesn't
> seems coherent, and this is why I suggested also a /32.
The reasons /32 was chosen for critical infrastructures in APNIC
are slightly different from the reasons when we consider
which prefix length is appropriate for multihomed end sites.
The organizations which receive /32 are nameservers (root, ccTLD,
and gTLD), and registries (IANA, RIRs, and NIRs). Exchange points
are /48. /32 or /48 is defined on other reasons than efficiency
of address consumption.
Portable assignment for multihoming, however, should be considered
on the efficient consumption.
Regards,
Katsuyasu Toyama
>
> Regards,
> Jordi
>
>
>
>
>> De: TOYAMA Katsuyasu <toyama.katsuyasu at lab.ntt dot co dot jp>
>> Responder a: <toyama.katsuyasu at lab.ntt dot co dot jp>
>> Fecha: Sun, 04 Jun 2006 20:44:08 +0900
>> Para: <jordi.palet at consulintel dot es>, <sig-policy at lists dot apnic dot net>
>> Asunto: Re: [sig-policy] A second policy proposal for the Policy SIG
>>
>> Hi Jordi,
>>
>> Thank you for your comments.
>>
>> JORDI PALET MARTINEZ wrote:
>>>> (1) the target of portable assignment is limited only to end sites
>>>> which are multihomed or plan to be multihomed, while Jordi does
>>>> not restrict the target.
>>>>
>>>> End sites which want portability only for independence of
>>>> service providers are NOT the target.
>>>> The end sites which require redundancy with multiple links
>>>> controled by BGP are the target because they have no other
>>>> way to achieve it than portable assignment.
>>> There are sites with have a single link but they have other reasons for
>>> portable addressing. For example, an entity don't need to be multihomed
>>> because SLAs warrantee enough their needs, but they may need to avoid
>>> renumbering if exchanging to a new ISP.
>>>
>>
>> End sites which want to be multihomed in IPv6 do not have solution now.
>> This fact avoids them from stepping into the IPv6 world.
>> I believe they are to be saved in first priority.
>>
>> I know renumbering is not so easy because they have to change not only
>> network address but dns records or others. However, at least these end-
>> sites can achieve their goal to communicate with IPv6 in ususal.
>>
>> Therefore I think portable assignment for multihoming is higher priority.
>>
>>> We may enter here in the debate about what right a "so-called" critical
>>> infrastructure is actually more critical than the independence for those
>>> entities. One example can be a university, which has multiple campuses and
>>> faculties and they are happy with a single link, and even they need a /32
>>> because the number of sites, as they want to keep delegating a /48 to each
>>> of one.
>> The example of campus network you mentioned, can be discussed in the scope
>> of portable allocation policy. It seems to me that the university
>> may be regarded as a service provider for multiple campus and faculties.
>>
>>
>>
>>>> I hope this can reduce unnecessary assignment, and avoid
>>>> rapid expansion of the IPv6 global routing table.
>>> I think that doesn't make a difference, those entities will have more
>>> trouble, but will get in the routing table one way or the other.
>> The end sites that need multihome must pay multiple service providers
>> for the links. It is the hurdle to get the portable assignment but
>> they willingly pay it if they really need the redundancy.
>>
>>>> We are now preparing the comparison of Jordi's proposal, the proposal
>>>> discussed in ARIN, and our proposal.
>>>>
>>> I'm working also in another proposal, also related to this, will try to
>>> finish it during the weekend, so you may want to wait to compare that one
>>> also ;-)
>> OK. I am waiting for it :-)
>>
>>
>>>> Best regards,
>>>> Katsuyasu Toyama
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Kenny Huang wrote:
>>>>>
>>>>>
>>>>> Dear SIG members
>>>>>
>>>>> The proposal "IPv6 portable assignment for multihoming" has been sent to
>>>>> the
>>>>> Policy SIG for review. It will be presented at the Policy SIG at APNIC
>>>>> 22 in Kaohsiung, Taiwan, 4-8 September 2006. You are invited to review and
>>>>> comment on the proposal on the mailing list before the meeting.
>>>>>
>>>>> The proposal's history can be found at:
>>>>>
>>>>> http://www.apnic.net/docs/policy/proposals/prop-035-v001.html
>>>>>
>>>>> Please feel free to submit your own policy proposal for discussion at APNIC
>>>>> 22.
>>>>>
>>>>> Regards
>>>>>
>>>>> Kenny Huang
>>>>> Policy SIG
>>>>> huangk at alum dot sinica dot edu
>>>>>
>>>>>
>>>>> ________________________________________________________________________
>>>>>
>>>>> prop-035-v001: IPv6 portable assignment for multihoming
>>>>> ________________________________________________________________________
>>>>>
>>>>>
>>>>> Authors: Katsuyasu Toyama
>>>>> Takashi Arano
>>>>> Tomohiro Fujisaki
>>>>> Toshinori Ishii
>>>>> Kosuke Ito
>>>>> Dai Nishino,
>>>>> Noriaktsu Ohishi
>>>>> Izumi Okutani
>>>>>
>>>>> Version: 1
>>>>>
>>>>> Date: 2 June 2006
>>>>>
>>>>> SIG: Policy
>>>>>
>>>>>
>>>>>
>>>>> Introduction
>>>>> ------------
>>>>>
>>>>> This policy allows 'end-sites' to be assigned IPv6 portable addresses only
>>>>> if the end-sites are multihomed, or plan to be multihomed.
>>>>>
>>>>>
>>>>>
>>>>> Summary
>>>>> -------
>>>>> The current policy does not allow IPv6 portable assignment to any
>>>>> end-sites. This obstructs end-site organizations which need redundancy
>>>>> in internet connectivity for stable network operation.
>>>>>
>>>>> Shim6, another multihoming technology discussed in IETF, is not a
>>>>> perfect replacement of the current multihoming technology using BGP due
>>>>> to traffic engineering. In addition, it will take time to standardize
>>>>> and implement Shim6.
>>>>>
>>>>>
>>>>>
>>>>> Situation
>>>>> --------
>>>>>
>>>>> ARIN has been discussing the IPv6 Provider-independent address. The
>>>>> draft was proposed in 2005 and moved to the last call after the meeting
>>>>> consensus in April 2006.
>>>>>
>>>>> RIPE started PI discussion at RIPE in this May.
>>>>>
>>>>> AFRINIC and LACNIC discussed similar proposals recently in their Open
>>>>> Policy meetings. In those regions, the issue has been returned to their
>>>>> public mailing lists for further discussion.
>>>>>
>>>>> Note: APNIC uses the term "portable" rather than "provider-independent"
>>>>> (PI).
>>>>>
>>>>>
>>>>>
>>>>> Details
>>>>> -------
>>>>>
>>>>> (1) Assignment target:
>>>>>
>>>>> End-sites which are multihomed or plan to be multihomed, regardless
>>>>> of their size.
>>>>>
>>>>>
>>>>> (2) Assignment criteria:
>>>>>
>>>>> (2-a) The end site which is assigned IPv6 portable address space
>>>>> must be multihomed using the assigned portable address space
>>>>> in three (3) months.
>>>>>
>>>>> (2-b) If the portable address space is not used for multihoming
>>>>> after three (3) months, the address space must be reclaimed.
>>>>>
>>>>> (2-c) The end site which is assigned IPv6 portable address space
>>>>> must pay the fee for the space.
>>>>>
>>>>>
>>>>> (3) Portable address space:
>>>>>
>>>>> (3-a) The portable assignment should be made from a specified block
>>>>> separate from address space used for portable allocations
>>>>>
>>>>> (3-b) The portable assignment size to an end-site should be the same
>>>>> size as in non-portable assignments, currently /48,
>>>>> or a shorter prefix if the end-site can justify it.
>>>>>
>>>>>
>>>>>
>>>>> Pros/Cons
>>>>> ---------
>>>>>
>>>>> Advantages:
>>>>>
>>>>> (1) Provides the solution for end-sites which require redundancy in
>>>>> IPv6 and currently not able to do so due to the lack of
>>>>> technical solutions.
>>>>>
>>>>> (2) Assignment of the portable address space is limited only to
>>>>> 'multihoming purposes'; only end-sites which are or planned to
>>>>> be multihomed can be assigned a portable address. This reduces
>>>>> the consumption of portable address space as well as the growth
>>>>> of the global routing table.
>>>>>
>>>>> (3) Portable assigned address space is separate from portable
>>>>> allocated address space, therefore:
>>>>>
>>>>> (3-1) It helps preventing 'punching holes' in the portable
>>>>> allocated address space because prefixes which are longer
>>>>> than /32 can be filtered in portable allocated space.
>>>>>
>>>>> (3-2) it is relatively easy to abandon the portable assigned
>>>>> address space in case some better techinical solutions
>>>>> are developed in the future.
>>>>>
>>>>>
>>>>> Disadvantages:
>>>>>
>>>>> It may lead to growth in the global routing table, but we think the
>>>>> growth is almost the same in case that providers and end-sites start
>>>>> using 'punching holes' for multihoming.
>>>>>
>>>>>
>>>>>
>>>>> Effect on APNIC
>>>>> ---------------
>>>>> No direct effect on the existing APNIC members, nor changes to the
>>>>> current IPv6 allocation criteria.
>>>>>
>>>>>
>>>>>
>>>>> Effect on NIRs
>>>>> --------------
>>>>> NIR can adopt this policy at its discretion.
>>>>>
>>>>>
>>>>> * sig-policy: APNIC SIG on resource management policy
>>>>> *
>>>>> _______________________________________________
>>>>> sig-policy mailing list
>>>>> sig-policy at lists dot apnic dot net
>>>>> http://mailman.apnic.net/mailman/listinfo/sig-policy
>>>>>
>>>>>
>>>> --
>>>> TOYAMA, Katsuyasu <toyama.katsuyasu at lab.ntt dot co dot jp>
>>>> IP Technology Expert Team, NTT PF-Labs.
>>>> Nippon Telegraph and Telephone Corp.
>>>> TEL: +81-(0)422-59-7906 FAX: +81-(0)422-59-5652
>>>>
>>>>
>>>> * sig-policy: APNIC SIG on resource management policy
>>>> *
>>>> _______________________________________________
>>>> sig-policy mailing list
>>>> sig-policy at lists dot apnic dot net
>>>> http://mailman.apnic.net/mailman/listinfo/sig-policy
>>>
>>>
>>>
>>> **********************************************
>>> The IPv6 Portal: http://www.ipv6tf.org
>>>
>>> Barcelona 2005 Global IPv6 Summit
>>> Slides available at:
>>> http://www.ipv6-es.com
>>>
>>> This electronic message contains information which may be privileged or
>>> confidential. The information is intended to be for the use of the
>>> individual(s) named above. If you are not the intended recipient be aware
>>> that any disclosure, copying, distribution or use of the contents of this
>>> information, including attached files, is prohibited.
>>>
>>>
>>>
>>> * sig-policy: APNIC SIG on resource management policy
>>> *
>>> _______________________________________________
>>> sig-policy mailing list
>>> sig-policy at lists dot apnic dot net
>>> http://mailman.apnic.net/mailman/listinfo/sig-policy
>>>
>>>
>>
>> --
>> TOYAMA, Katsuyasu <toyama.katsuyasu at lab.ntt dot co dot jp>
>> IP Technology Expert Team, NTT PF-Labs.
>> Nippon Telegraph and Telephone Corp.
>> TEL: +81-(0)422-59-7906 FAX: +81-(0)422-59-5652
>>
>
>
>
>
> **********************************************
> The IPv6 Portal: http://www.ipv6tf.org
>
> Barcelona 2005 Global IPv6 Summit
> Slides available at:
> http://www.ipv6-es.com
>
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
>
>
>
> * sig-policy: APNIC SIG on resource management policy *
> _______________________________________________
> sig-policy mailing list
> sig-policy at lists dot apnic dot net
> http://mailman.apnic.net/mailman/listinfo/sig-policy
>
>
--
TOYAMA, Katsuyasu <toyama.katsuyasu at lab.ntt dot co dot jp>
IP Technology Expert Team, NTT PF-Labs.
Nippon Telegraph and Telephone Corp.
TEL: +81-(0)422-59-7906 FAX: +81-(0)422-59-5652