Re: The way APNIC operates ...
Hi,
>Must (should) they change AS# ?
Again, this would be a contractual issue -- if ISP#1 has contractual
language that says they must return the AS if they change providers, then
obviously that's what the customer would need to do. APNIC takes no
position on whether this is good or bad (in contrast to the situation with
IP addresses where we strongly encourage ISPs to have contractual language
indicating the customer must return address space when they change
providers).
It is worth noting however that renumbering an AS is relatively easy (at
least compared to renumbering IP addresses), thus should a provider require
AS numbers be returned, changing the router configs in which the AS number
is referenced (in my experience, managed centrally) would be all that would
be required.
>If ISP#4, ISP#5 is in North America, and the user switchs to them.
>Should they change AS# ?
Where the ISP is located or where the AS number has been allocated is
irrelevant -- there is no hierarchical significance with ASes.
>(2) Does APNIC really inform that there is a possibility for a waiver ?
As I described in previous mail, if an organization indicates they feel the
APNIC membership fee is an undue burden, we inform them they can petition
the executive council to waive (or reduce) their fee. In addition, waivers
are documented in the APNIC by-laws -- something that is included (by
reference) in the service agreement (contract) organizations sign when they
become members.
>I know a case, where APNIC did not inform that a waiver is possible.
If the organization did not indicate the fee would be a burden, we don't
normally volunteer the information that they may apply for a waiver.
>Nevertheless, I am against the waiver policy in regions with more than one
>APNIC member.
Understood. If you feel strongly about this, I'd recommend you propose the
membership amend the APNIC by-laws to remove this responsibility from the
APNIC Executive.
>They may be not happy with the whole system/IANA.
I myself am not particularly happy with various aspects of the Internet
registry system, however I'm just the hired help (:-)).
The policies that APNIC follow are those imposed on us by the IANA or the
IETF. Given these policies are (theoretically) global in applicability,
there are many limitations in how much APNIC can modify those policies.
However, there is an effort being made within the IETF to evolve the
registry system so it can remain relevant. PAGAN (Policies And Guidelines
for the Allocation of Network numbers) was initiated (by me actually, but
I've recently resigned as a co-chair due to lack of time) in the IETF and
there is a mailing list/archives. If you'd like to subscribe to PAGAN send
a message of "subscribe" to pagan-request at apnic dot net, archives are available
from ftp://ftp.apnic.net/mailing-lists/pagan/* (note: PAGAN used to be
called IRE (Internet Registry Evolution), but we got too much DNS-related
traffic -- PAGAN is very specifically targeted at address allocation issues,
_NOT_ DNS issues).
Regards,
-drc
_________________________________________________________________________
| To unsubscribe: send "unsubscribe" to apnic-talk-request at apnic dot net |
+-----------------------------------------------------------------------+