APNIC Home APNIC Home
Info & FAQ |  Resource services |  Training |  Meetings |  Membership |  Documents |  Whois & Search |  Internet community

You're here:  Home  Mailing Lists apops 


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [apops] APNIC new block of addresses



 son, 
	you might want to ensure that all the hardware vendors who
	design/build hardware based on RFC's will respect your
	administrative choice to delegate this /24 prefix.  I say this
	with the battlescars that came from getting venders to 
	rebuild their ASICs and replace all their fielded hardware
	when we deployed CIDR.  CIDR, as a technology, impacted
	everyone, and was the -ONLY- reason vendors made the
	change. It took three years to get hardware updated.
        I doubt vendors will go through the same multimillion
	$CURRENCY change for a single /24.  

	As a testcase, I recommend that APNIC delegate this prefix
	to a site that provides critical services to APNIC and then
	test your reachability to said service -BEFORE- to inflict
	the same pain on one of your members.

% 
% 
% Hi Geoff,
% 
% Thank you for your email but since RFC3300 has specifically
% indicates that this /24 reservation will subject for future
% allocation. As APNIC received the /8 from IANA without any
% condidtion or detail regarding this. In this case we assume
% we have the authority to fully utilise the whole /8 as normal.
% 
% Regards
% 
% son
% 
% APNIC staff
% 
% On Fri, 21 Feb 2003, Geoff Huston wrote:
% 
% > To quote RFC 3300:
% > 
% > 223.255.255.0/24 Reserved but subject to allocation --
% > 
% > i.e. I assume that this is an allocation of 223.0.0.0/8 MINUS the /24 as 
% > noted in
% > RFC3300
% > 
% > Thanks
% > 
% >    Geoff
% > 
% > 
% > At 10:06 AM 2/17/2003 +1000, John Tran wrote:
% > 
% > >Dear colleagues
% > >
% > >APNIC received IPv4 address blocks 222/8 and 223/8 from IANA in February 2003
% > >and will be making allocations from these ranges in the near future.
% > >
% > >This announcement is being made for the information of the Internet
% > >community so that network configurations such as routing filters
% > >may be updated as appropriate.
% > >
% > >For more information on the resources administered by APNIC, see:
% > >
% > >     http://www.apnic.net/db/ranges.html
% > >
% > >For information on the minimum allocation sizes within address ranges
% > >administered by APNIC, see:
% > >
% > >     http://www.apnic.net/db/min-alloc.html
% > >
% > >
% > >Kind regards
% > >
% > >Son
% > >
% > >____________________________________________________________________
% > >Resources Services Manager                      <Son@apnic.net>
% > >Asia Pacific Network Information Centre       phone: +61 7 3858 3100
% > >http://www.apnic.net                          fax:   +61 7 3858 3199
% > >Helpdesk                                      phone: +61 7 3858 3188
% > >                                               email: helpdesk@apnic.net
% > >Please send Internet Resource Requests to <hostmaster@apnic.net>
% > >_____________________________________________________________________
% > >
% > >
% > >
% > >
% > >
% > >
% > >
% > >
% > >
% > >_______________________________________________
% > >Apnic-announce mailing list
% > >Apnic-announce@lists.apnic.net
% > >http://mailman.apnic.net/mailman/listinfo/apnic-announce
% > >_______________________________________________
% > >apnic-talk mailing list
% > >apnic-talk@lists.apnic.net
% > >http://mailman.apnic.net/mailman/listinfo/apnic-talk
% > >
% > >_______________________________________________
% > >apops mailing list
% > >apops@apops.net
% > >http://mailman.apnic.net/mailman/listinfo/apops
% > 
% > 
% > 
% 
% _______________________________________________
% apops mailing list
% apops@apops.net
% http://mailman.apnic.net/mailman/listinfo/apops
% 


-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).