Sorry, I should have said: IRINN is changing the description to be more similar with what is shown in the other registries. But for now they have temporarily removed it.
Cheers,
SanjayaSalam,
On 21/04/2013 5:07 PM, Sanjaya wrote:
Leo is correct. As IRINN also uses RIPE's Whois code, they need to add
this super-block to act as a parent of all IPv4 space delegated through
IRINN.
IRINN has changed the description as Chris suggested, it is now similar
to what is shown in the other registries.
Thanks Jimmy for spotting and alerting us of this.
Regards,
Sanjaya
On 21/04/2013 9:09 AM, Chris Chaundy wrote:
I would suggest that what is needed is the netname and descr entries
to be updated to reflect the object accurately (nothing to do with
broadcast in this context).
Regards, Chris Chaundy
Sent from my iPhone
On 21/04/2013, at 8:53, Leo Vegoda <leo.vegoda at icann dot org> wrote:
Hi Jimmy,_______________________________________________
On Apr 20, 2013, at 9:59 am, i4HK - Jimmy Tam <jimmy at i4hk dot com> wrote:
What's wrong with IRINN ??
All of Internet IPs assigned by IRINN ??
inetnum: 0.0.0.0 - 255.255.255.255
netname: IRINN-BROADCAST-ADDRESSES
descr: Broadcast addresses
descr: These addresses cannot (should not) be routed on the
Internet.
country: IN
admin-c: IH1-IN
tech-c: IH1-IN
status: ALLOCATED PORTABLE
remarks: send spam and abuse report to info at irinn dot in
mnt-by: IRINN-HM
mnt-irt: IRT-IRINNHM-IN
mnt-lower: IRINN-HM
changed: hostmaster2 at irinn dot in 20130420
source: IRINN
The value of the "source:" attribute indicates that this is mirrored
in APNIC's database. When you look at other RPSL databases it is
common to see an object for 0/0 in IPv4 and 0::/0 in IPv6:
leo@Megara ~> whois -h whois.ripe.net 0.0.0.0 - 255.255.255.255 |
head -n 15
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '0.0.0.0 - 255.255.255.255'
inetnum: 0.0.0.0 - 255.255.255.255
netname: IANA-BLK
descr: The whole IPv4 address space
country: EU # Country field is actually all countries in the
world and not just EU countries
leo@Megara ~> whois -h whois.afrinic.net 0.0.0.0 - 255.255.255.255 |
head -n 15
% This is the AfriNIC Whois server.
% Note: this output has been filtered.
% Information related to '0.0.0.0 - 255.255.255.255'
inetnum: 0.0.0.0 - 255.255.255.255
netname: IANA-BLK
descr: The whole IPv4 address space
country: EU # Country is really world wide
org: ORG-IANA1-AFRINIC
admin-c: IANA1-AFRINIC
tech-c: IANA1-AFRINIC
status: ALLOCATED UNSPECIFIED
remarks: The country is really worldwide.
leo@Megara ~> whois -h whois.ripe.net 0::/0 | head -n 15
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '0::/0'
inet6num: 0::/0
netname: IANA-BLK
descr: The whole IPv6 address space
country: EU # Country is really world wide
leo@Megara ~> whois -h whois.afrinic.net 0::/0 | head -n 15
% This is the AfriNIC Whois server.
%WARNING:905: fixed lookup key
%
% The key "0::/0" has been changed to "::/0" for lookup.
% Note: this output has been filtered.
% Information related to '0::/0'
inet6num: 0::/0
netname: ROOT
descr: Root inet6num object
country: EU
org: ORG-IANA1-AFRINIC
leo@Megara ~>
I believe this is generally done to enable RPSS hierarchical
protection rather than as a claim over the entire IPv4 and IPv6
address space.
RFC 2725 (http://www.rfc-editor.org/rfc/rfc2725.txt) says this in
section 9.9 "The root repository must be initially populated with the
allocation of an inetnum covering the prefix 0/0, indicating that
some address allocation authority exists. Similarly an initial
as-block is needed covering the full AS number range."
Kind regards,
Leo
_______________________________________________
apnic-talk mailing list
apnic-talk at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/apnic-talk
apnic-talk mailing list
apnic-talk at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/apnic-talk
--
Sanjaya
_______________________________________________
apnic-talk mailing list
apnic-talk at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/apnic-talk