Re: [apnic-talk] inetnum: 0.0.0.0 - 255.255.255.255

    • To: APNIC Mailing List <apnic-talk at apnic dot net>
    • Subject: Re: [apnic-talk] inetnum: 0.0.0.0 - 255.255.255.255
    • From: Anurag Bhatia <me at anuragbhatia dot com>
    • Date: Mon, 22 Apr 2013 17:27:23 +0530
    • Delivered-to: apnic-talk at mailman dot apnic dot net
    • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anuragbhatia.com; s=mail; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=zlxwx6qYv/6EPkBJz8gWsMFoRTyljECDUBijPTF6tCA=; b=nJ9OCtb3sJf6d5EI3MXcn8i3mshD/u6QU2zaWAfnS7OzrKgcvCMrPIvpBZLHNXoW4K IQQmperUA8nqcYYWtA0b5kc3Jzk8E+Rqh3KdAOp3v4nY5knQyjkLKwHfAK7nTSxaY0hO kFJJP64t1yU9AeM6TRvqAaBOqPhLnlmMXsz+c=
    • In-reply-to: <517393B1.5090706 at indo dot net dot id>
    • List-archive: <http://mailman.apnic.net/mailing-lists/apnic-talk/>
    • List-help: <mailto:apnic-talk-request@lists.apnic.net?subject=help>
    • List-id: General discussions on APNIC <apnic-talk.lists.apnic.net>
    • List-post: <mailto:apnic-talk@lists.apnic.net>
    • List-subscribe: <http://mailman.apnic.net/mailman/listinfo/apnic-talk>, <mailto:apnic-talk-request@lists.apnic.net?subject=subscribe>
    • List-unsubscribe: <http://mailman.apnic.net/mailman/options/apnic-talk>, <mailto:apnic-talk-request@lists.apnic.net?subject=unsubscribe>
      • Hello everyone

        I was wondering if someone could explain the logic behind the range used by APNIC.


        I see that ARIN, RIPE etc using entire range 0.0.0.0 to 255.255.255.255

        while APNIC is using 255.0.0.0 - 255.255.255.255



        I see IRINN has made some changes and now it says IANA broadcast but range is what we see in APNIC and as per whois on IRINN.in it suggests source to be APNIC. 


        Kindly correct me if I am wrong but 255.0.0.0 start seems to be of no meaning. Also, I do see strange results based on different queries.

        E.g if I query 0.0.0.0/0 to APNIC, I get:

        anurag:~ anurag$ whois -h whois.apnic.net 0.0.0.0/0
        % [whois.apnic.net node-1]
        % Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

        inetnum:        255.0.0.0 - 255.255.255.255
        netname:        IANA-BROADCAST-ADDRESSES
        descr:          Broadcast addresses
        descr:          These addresses cannot (should not) be routed on the Internet.
        country:        US
        admin-c:        HM20-AP
        tech-c:         NO4-AP
        remarks:        This is a placeholder object to ensure no objects are created
        remarks:        in the enclosing range.
        mnt-by:         MAINT-APNIC-AP
        mnt-lower:      MAINT-APNIC-AP
        changed:        apnic-dbm at apnic dot net 19991214
        changed:        hm-changed at apnic dot net 20040926
        status:         ALLOCATED PORTABLE
        source:         APNIC





        While if I query for just IP address 0.0.0.0 (not entire /0),


        anurag:~ anurag$ 
        anurag:~ anurag$ whois -h whois.apnic.net 0.0.0.0
        % [whois.apnic.net node-3]
        % Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

        inetnum:        0.0.0.0 - 255.255.255.255
        netname:        IANA-BLOCK
        descr:          General placeholder reference for all IPv4 addresses
        remarks:        ------------------------------------------------------
        remarks:
        remarks:        Important:
        remarks:
        remarks:        This registration object does not contain
        remarks:        specific registration details.
        remarks:
        remarks:        This registration object is used only as a
        remarks:        general placeholder for all IPv4 addresses
        remarks:        and may include:



        I am clueless on whether there's a reason behind such address or may be it's a bug?



        Thanks.


        On Sun, Apr 21, 2013 at 12:52 PM, Sanjaya <sanjaya at indo dot net dot id> wrote:
        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,
        Sanjaya


        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



        --
        Salam,
        Sanjaya

        _______________________________________________
        apnic-talk mailing list
        apnic-talk at lists dot apnic dot net
        http://mailman.apnic.net/mailman/listinfo/apnic-talk



        --