Jump to content

Property talk:P3761

Add topic
From Wikidata
Latest comment: 9 years ago by Pintoch in topic Merging IP ranges

Documentation

Descriptionrange of IPv4 addresses owned
RepresentsIPv4 routing prefix (Q29001140)
Data typeString
Domain
According to this template: organization (Q43229)
According to statements in the property:
internet backbone (Q1360517), organization (Q43229) or human (Q5)
When possible, data should only be stored as statements
Allowed values(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]?|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]?|25[0-5])\/([0-9]|[12][0-9]|3[0-2])
ExampleUniversity of Oxford (Q34433) → 163.1.0.0/16
Helsinki University Hospital (Q246315) → 193.166.190.0/24
Sourcehttps://www.ripe.net/manage-ips-and-asns/db
https://www.arin.net/
https://www.apnic.net/
https://www.afrinic.net/
https://www.lacnic.net/
https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml
See alsoIPv6 routing prefix (P3793), autonomous system number (P3797)
Lists
Proposal discussionProposal discussion
Current uses
Total2,456
Main statement2,45399.9% of uses
Qualifier2<0.1% of uses
Reference1<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]?|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]?|25[0-5])/([0-9]|[12][0-9]|3[0-2]): value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P3761#Format, hourly updated report, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3761#Unique value, SPARQL (every item), SPARQL (by value)
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P3761#Scope, hourly updated report, SPARQL
Type “internet backbone (Q1360517), organization (Q43229), human (Q5): item must contain property “instance of (P31)” with classes “internet backbone (Q1360517), organization (Q43229), human (Q5)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3761#Type Q1360517, Q43229, Q5, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3761#Entity types


Merging IP ranges

[edit]

In my first additions of IP ranges to institutions I have added the ranges as they are represented by RIPE, but in fact some of these ranges can be merged. For instance on University of Orléans (Q13334), the IP ranges '193.49.80.0/24','193.49.81.0/24','193.49.82.0/24','193.49.83.0/24' can be merged into '193.49.80.0/22'. I plan to merge automatically these ranges in the coming days. − Pintoch (talk) 20:57, 4 April 2017 (UTC)Reply