RFC 4698
IRIS: An Address Registry (areg) Type for the Internet Registry Information Service
Part 1 of 8 🎀
IRIS: An Address Registry (areg) Type for the Internet Registry Information Service 💖
Network Working Group · Request for Comments: 4698 · Category: Standards Track · Date: October 2006
Authors: E. Gunduz (RIPE NCC), A. Newton (VeriSign, Inc.), S. Kerr (RIPE NCC) 🫶
Obsoletes / Updates: This title block doesn't list anything this RFC obsoletes or updates. 🤷♀️
Status of This Memo 📋
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. ✨
Copyright Notice ©️
Copyright (C) The Internet Society (2006). 🌸
Abstract 🦋
This document describes an IRIS registry schema for IP address and Autonomous System Number information. The schema extends the necessary query and result operations of IRIS to provide the functional information service needs for syntaxes and results used by Internet Protocol address registries. It's giving "registry schema for IP addresses and ASNs" 💅
Table of Contents 📜
1. Introduction ....................................................3
2. Document Terminology ............................................3
3. Schema Description ..............................................3
3.1. Query Derivatives ..........................................4
3.1.1. <findContacts> Query ................................4
3.1.2. <findOrganizations> .................................4
3.1.3. <findAutonomousSystemsByName> and
<findNetworksByName> ................................5
3.1.4. <findNetworksByAddress> .............................5
3.1.5. <findNetworksByHandle> ..............................6
3.1.6. <findASByNumber> ....................................6
3.1.7. <findByContact> .....................................7
3.1.8. <findNetworksByNameServer> ..........................7
3.1.9. Contact Search Group ................................8
3.1.10. Common Search Group ................................8
3.1.11. Match Parameters ...................................8
3.2. Result Derivatives .........................................9
3.2.1. <ipv4Network> and <ipv6Network> Results .............9
3.2.2. <autonomousSystem> Result ..........................10
3.2.3. <contact> Result ...................................11
3.2.4. <organization> Result ..............................12
3.2.5. Contact References .................................12
3.2.6. Common Result Child Elements .......................13
3.3. Support for <iris:lookupEntity> ...........................13
4. Terminology for Nesting of Networks ............................14
5. Formal XML Syntax ..............................................18
6. BEEP Transport Compliance ......................................31
6.1. Message Pattern ...........................................31
6.2. Server Authentication .....................................31
7. URI Resolution .................................................31
7.1. Application Service Label .................................31
7.2. Operational Considerations ................................31
7.3. Top-Down Resolution .......................................31
8. Internationalization Considerations ............................32
9. IANA Considerations ............................................32
10. Security Considerations .......................................32
11. References ....................................................33
11.1. Normative References .....................................33
11.2. Informative References ...................................33
Appendix A. Privacy Considerations ................................34
Appendix B. Example Requests and Responses ........................34
B.1. Example 1 .................................................34
B.2. Example 2 .................................................36
Appendix C. Specificity Examples ..................................39
Appendix D. Contributors ..........................................46
Appendix E. Acknowledgements ......................................461. Introduction ✨
An Internet address registry stores information about:
- address ranges
- autonomous system number ranges
- associated contacts and organizations
- name servers
This information is interrelated, and Internet address registries store this information and the information's interrelationships in a manner befitting the needs of each Internet address registry and its constituents. This document specifies a method for accessing and retrieving this information in a common XML format. 🧚
This document describes an IRIS namespace for Internet address registries using an XML Schema [8] derived from and using the IRIS [2] schema. This schema and registry type are provided to demonstrate the extensibility of the IRIS framework beyond the use of domains, a criteria defined in CRISP [4]. 🌈
The schema given in this document is specified using the Extensible Markup Language (XML) 1.0 as described in XML [5], XML Schema notation as described in XML_SD [7] and XML_SS [8], and XML Namespaces as described in XML_NS [6]. 💜
Examples of client/server XML exchanges with this registry type are available in Appendix B. 🍓
2. Document Terminology 🔥
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [1]. 📖
3. Schema Description 🎀
IRIS requires the derivation of both query and result elements by a registry schema. Descriptions for these follow. 🌸
The descriptions contained within this section refer to XML elements and attributes and their relation to the exchange of data within the protocol. These descriptions also contain specifications outside the scope of the formal XML syntax. Therefore, this section will use terms defined by RFC 2119 [1] to describe the specification outside the scope of the formal XML syntax. While reading this section, please reference Section 5 for needed details on the formal XML syntax. 🦋
3.1. Query Derivatives 🔍
3.1.1. <findContacts> Query 👀
<findContacts> searches for contacts given search constraints. 🫧
The allowable search fields are handled by one of the elements in the "contactSearchGroup" (see Section 3.1.9) or the element <organizationId>. The <organizationId> element constrains the query based on the organization ID (handle) associated with contacts. This element is an "exactMatchParameter" (see Section 3.1.11). 💅
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to give a hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as tailoring normalization routines to aid in more effective searches. 🌍
The client SHOULD pass the names unchanged to the server, and the implementation of the server decides if the search is case sensitive or not. 🤍
3.1.2. <findOrganizations> 🏢
<findOrganizations> searches for organizations given search constraints. 🔎
The allowable search fields are handled by one of the elements in the "commonSearchGroup" (see Section 3.1.10) or the element <organizationName>. This element is an "exactOrPartialMatchParameter" (see Section 3.1.11). ✨
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to give a hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as tailoring normalization routines to aid in more effective searches. 🌷
The client SHOULD pass the names unchanged to the server, and the implementation of the server decides if the search is case sensitive or not. 💭
3.1.3. <findAutonomousSystemsByName> and <findNetworksByName> 🏷️
The <findAutonomousSystemsByName> and <findNetworksByName> elements allow searches by name of autonomous systems and networks, respectively. Both have the same format. 🪄
The child element <name> is an "exactOrPartialMatchParameter" (see Section 3.1.11). 🎯
This query also provides optional <language> elements containing language tags. Clients MAY use these elements to give a hint about the natural language(s) of the affected element. Servers MAY use this information in processing the query, such as tailoring normalization routines to aid in more effective searches. 🌺
The client SHOULD pass the names unchanged to the server, and the implementation of the server decides if the search is case sensitive or not. 🙈
3.1.4. <findNetworksByAddress> 🌐
The <findNetworksByAddress> element is a query for a network given a related IP address or IP address range. It has the following child elements: 🗺️
<ipv4Address>- has a child<start>element containing the starting IPv4 address of the network and an optional child of<end>containing the ending IPv4 address of the network. Clients MUST convert any short-form notation to the fully-qualified notation. 💖<ipv6Address>- same as<ipv4Address>, but the child addresses contain IPv6 addresses. Clients MUST convert any short-form notation to the fully-qualified notation. 💜<specificity>- determines the network specificity for the search (see Section 4). Valid values are "exact-match", "all-less-specific", "one-level-less-specific", "all-more-specific", and "one-level-more-specific". This element may have the optional attribute 'allowEquivalences'. When it is set to "true", the result set should include networks with equivalent starting and ending addresses. The default value for 'allowEquivalences' is "false". 🧩
The results from this query MUST be either <ipv4Network> or <ipv6Network> results. More than one network result MAY be returned. 🔥
3.1.5. <findNetworksByHandle> 🪪
The <findNetworksByHandle> element is a query for a network given the handle of a related network. It has the following child elements: 🫶
<networkHandle>- specifies the network handle. 🏷️<specificity>- determines the network specificity for the search (see Section 4). Valid values are "all-less-specifics", "one-level-less-specifics", "all-more-specifics", and "one-level-more-specifics". ✨
The results from this query MUST be either <ipv4Network> or <ipv6Network> results. More than one network result MAY be returned. 👑
This query could be used to discover the parentage relationships between networks that have the same starting and ending addresses. 🕵️♀️
The client SHOULD pass handles unchanged to the server, and the implementation of the server decides if the search is case sensitive or not. 🌸
3.1.6. <findASByNumber> 🦋
okay so <findASByNumber> is the move when you wanna search for autonomous systems by an autonomous system number (ASN) range 💅. It has these child elements:
<asNumberStart>- specifies the start of the ASN range.<asNumberEnd>- specifies the end of the ASN range.<specificity>- determines the range specificity for the search (see Section 4). Valid values are "exact-match", "all-less-specific", "one-level-less-specific", "all-more-specific", and "one-level-more-specific". This element may have the optional attributeallowEquivalences. When it is set to "true", the result set should include ranges with equivalent starting and ending numbers. The default value forallowEquivalencesis "false".
the results from this query MUST be <autonomousSystem> results, and more than one result MAY be returned 🫶
3.1.7. <findByContact> 💜
the <findByContact> element lets you search for autonomous systems, IP networks, and organizations based on the fields tied to that entity's contact 📇 ngl this one is so useful.
the optional search element <returnedResultType> MUST restrict the results to autonomous systems, IPv4 networks, IPv6 networks, or organizations, using the values 'returnASs', 'returnIPv4Networks', 'returnIPv6Networks', and 'returnOrganizations', respectively. ✨
the searchable fields are handled with either the <contactHandle> element or one of the elements in the "contactSearchGroup" (see Section 3.1.9). the <contactHandle> element lets you select entities based on the contact that has the specified contact handle, and it is an "exactMatchParameter" type (see Section 3.1.11). the client SHOULD pass these search fields unchanged to the server, and the server's implementation decides whether the search is case sensitive or not 🌸
the query MAY also be narrowed down with the optional <role> element. the contents of this element show what role the contact has with the entity. the allowable values for this element are "adminContact", "nocContact", "techContact", "abuseContact", and "otherContact" 🎀
this query also gives you optional <language> elements that hold language tags. clients MAY use these elements to give a hint about the natural language(s) of the affected element, and servers MAY use this info when processing the query, like tailoring normalization routines so searches work better 🧚
the results from this query MUST be <ipv4Network> results, <ipv6Network> results, <autonomousSystem> results, or <organization> results. more than one result MAY be returned, and the results MAY be of mixed types. it's giving variety 🌈
3.1.8. <findNetworksByNameServer> 🍓
the <findNetworksByNameServer> element lets you search for IP networks based on their associated name servers 🖥️ the <nameServer> element holds the fully qualified domain name of the name server.
the optional search element <returnedResultType> MUST restrict the results to IPv4 networks or IPv6 networks, using the values 'returnIPv4Networks' and 'returnIPv6Networks', respectively.
the results from this query MUST be <ipv4Network> or <ipv6Network> results. more than one result MAY be returned, and the results MAY be of mixed types 💖
3.1.9. Contact Search Group 🫧
some of the queries above have similar constraints for searching on contacts, so this section covers those shared parameters. it's the copy-paste section that saves everyone's life 😭
<commonName> lets the query be constrained based on the common name of the contact. this constraint is an "exactOrPartialMatchParameter" (see Section 3.1.11).
this group also contains all the members of the "commonSearchGroup" (see Section 3.1.10) 💅
3.1.10. Common Search Group 🌷
okay so some of the queries above have similar constraints for searching on contacts, and this section describes those common parameters. yes, it's the same vibe as the last one, iykyk 🙈
<eMail> constrains the query based on the e-mail address of the contact. this constraint is a "domainResource" type (see Section 3.1.11).
the <city>, <region>, <country>, and <postalCode> elements restrict the scope of the query based on the city, region, country, or postal code of the contact, respectively. these constraints are all "exactMatchParameter" types (see Section 3.1.11). the contents of <country> MUST be compliant with ISO 3166 [9] two-character country codes 🌍
3.1.11. Match Parameters 🎯
some of the queries above have constraints that match strings using matching parameters, and this section explains those parameters. let's get into it 💫
elements of type "exactMatchParameter" will have one child element, <exactMatch>. the contents of this child element have to match exactly in how the constraint is used.
elements of type "partialMatchParameter" will have either a <beginsWith> child element with an optional <endsWith> child element, or just an <endsWith> child element. the content of the <beginsWith> element specifies the beginning character sequence for the constraint. the content of the <endsWith> element specifies the ending character sequence for the constraint 🦋
elements of type "exactOrPartialMatchParameter" can have either the child element allowed with the "exactMatchParameter" type, or the child elements allowed with the "partialMatchParameter" type. choose your fighter 🥊
elements of type "domainResource" can have either the child element allowed with the "exactMatchParameter" type, or a child element of <inDomain>. this parameter type is meant to match email, SIP, Extensible Messaging and Presence Protocol (XMPP), and other kinds of "user@domain" addresses. when this parameter is specified with the <exactMatch> child element, the constraint is based on the whole email address. when it's specified with the <inDomain> child element, the constraint is based on any email address within the domain given. the <inDomain> MUST only contain a valid domain name (i.e., no '@' symbol), and the matching SHOULD take place only on the domain given (i.e., no partial matches with respect to substrings or parent domains). no sneaky substring matches allowed 🙅♀️✨
3.2. Result Derivatives 🎀
3.2.1. <ipv4Network> and <ipv6Network> Results 🌐
the <ipv4Network> and <ipv6Network> share a common definition of 'ipNetworkType' 👯♀️ it has these child elements:
<networkHandle>contains the registry-unique assigned handle for this network.<name>contains a human-friendly name for the network.<startAddress>contains the first IP address of the network.<endAddress>contains the last IP address of the network.<networkType>contains a string denoting the type of network.<networkTypeInfo>is an entity reference to a definition of the values, explained in plain natural language. the referent MUST be a<simpleEntity>as defined by [2].<nameServer>contains the domain name of a nameserver responsible for reverse-DNS mapping for this network.<organization>contains an entity reference to the organization assigned this network. the referent MUST be an<organization>(Section 3.2.4) result.- One of the following:
<parent>contains an entity reference to the parent network of this network. the referent MUST be an<ipv4Network>(Section 3.2.1) result if this reference is a child of<ipv4Network>. the referent MUST be an<ipv6Network>(Section 3.2.1) result if this reference is a child of<ipv6Network>.<noParent>signifies that this network has no parent network.
- Contact references (see Section 3.2.5).
- Common child elements (see Section 3.2.6).
3.2.2. <autonomousSystem> Result 🍭
the <autonomousSystem> element represents an assigned or allocated autonomous system number range 🌙 it has these children:
<asHandle>contains a registry-unique assigned handle for this autonomous system number range.<asNumberStart>contains an integer indicating the starting number for the autonomous system number range.<asNumberEnd>contains an integer indicating the ending number for the autonomous system number range.<name>contains a human-readable name for this autonomous system.<organization>contains an entity reference to the organization assigned or allocated this autonomous system number range. the referent MUST be an<organization>(Section 3.2.4) result.- One of the following:
<parent>contains an entity reference to the parent autonomous system of this autonomous system. the referent MUST be an<autonomousSystem>(Section 3.2.2) result.<noParent>signifies that this autonomous system has no parent autonomous system.
- Contact references (see Section 3.2.5).
- Common child elements (see Section 3.2.6).
3.2.3. <contact> Result 💌
the <contact> element represents the registration of a point of contact 🫶 it has these child elements:
<contactHandle>contains the registry-unique assigned handle for this contact.<commonName>specifies the name of the contact.<eMail>contains the email address for this contact.<sip>contains the sip address for this contact.<organization>contains an entity reference to the organization associated with this contact. the referent MUST be an<organization>(Section 3.2.4) result.<postalAddress>contains information for reaching the contact via postal mail. it is composed of the following child elements:<address>contains the address for this contact.<city>contains the city where this contact is located.<region>contains the national region where this contact is located.<postalCode>contains the postal code where this contact is located.<country>contains the country code where this contact is located. this MUST be compliant with ISO 3166 [9] two-character country codes.
<phone>contains child elements describing the phone number of the contact. the child elements are<number>,<extension>, and<type>.- Common child elements (see Section 3.2.6).
3.2.4. <organization> Result 🏢
the <organization> element represents an organization ✨ it has these child elements:
<name>contains the name of the organization.<id>contains a registry-unique identifier for this organization.<eMail>contains the email address for this organization.<postalAddress>contains a information for reaching the organization via postal mail. it is composed of the following child elements:<address>contains the address for this organization.<city>contains the city where this organization is located.<region>contains the national region where this organization is located.<postalCode>contains the postal code where this organization is located.<country>contains the country code where this organization is located. this MUST be compliant with ISO 3166 [9] two-character country codes.
<phone>contains child elements describing the phone number of the contact. the child elements are<number>,<extension>, and<type>.- Contact references (see Section 3.2.5).
- Common child elements (see Section 3.2.6).
3.2.5. Contact References 🫶
okay so the registry schema in Section 5 bundles up a little group of elements that all point at contacts 📇 this group shows up in a ton of the result types for this registry. each of these elements can appear as many times as needed, and the referent of each MUST be <contact> (Section 3.2.3) results 💅
<adminContact><techContact><nocContact><abuseContact><otherContact>
3.2.6. Common Result Child Elements ✨
the registry schema in Section 5 also groups together the elements that show up most across the result types. this is the group, bestie 🎀
<numberResourceRegistry>holds an entity reference to the number resource registry of record. the referent MUST be an <organization> (Section 3.2.4) result 🏛️<registrationDate>holds the date of first registration 🗓️<lastUpdatedDate>holds the date when the registration was last updated 🌸- the
<iris:seeAlso>element holds an entity reference to an entity that is indirectly associated with this result object. it's giving comments and remarks energy 💬
3.3. Support for <iris:lookupEntity> 🔍
these are the entity classes that the IRIS <lookupEntity> query recognizes for this registry, and yes they're all iconic 👑
ipv4-handleis a registry-unique identifier for an IPv4 network. queries with these names yield a<ipv4Network>result 🌈ipv6-handleis a registry-unique identifier for an IPv6 network. queries with these names yield a<ipv6Network>result 🦋as-handleis a registry-unique identifier for an autonomous system. it yields an<autonomousSystem>result 🧚contact-handleis a registry-unique identifier for a contact. it yields a<contact>result 💜organization-idis a registry-unique identifier for an organization. it yields an<organization>result 🍓- the entity names of these entity classes are case insensitive 🙈
4. Terminology for Nesting of Networks 🪆
okay now we get into how networks nest inside each other, and it's lowkey so satisfying 🦋 these are the terms for describing IP network nesting:
- More specific: given two networks, A and B, A is more specific than B if network B includes all of network A's space, and if network B is larger than network A ✨
- Less specific: the opposite of more specific. network B is less specific than network A if network A's space is completely included in network B, and if network A is smaller than network B 🌙
- Most specific: given a set of networks, these are the networks that are more specific than zero or more of the other networks in the set, and that are not less specific than any of the networks in the set 👑
- Least specific: given a set of networks, these are the networks that are not more specific than any of the other networks in the set 🫧
Examples 💖
+-------------------------------------------------------+
| |
| Given the networks A, B, C, and D as follows: |
| |
| A |---------------------------------| |
| B |-----------------| |
| C |---------| |
| D |-------| |
| |
| |
| Network A is less specific than B, C, and D. |
| Network B is more specific than A. |
| Among these four networks, A is the least specific, |
| and C and D are the most specific. |
| |
+-------------------------------------------------------+Figure 1: Nesting Example 1
+-------------------------------------------------------+
| |
| Given networks E, F, and G: |
| |
| E |----------| |
| F |--------------| |
| G |---| |
| |
| Networks E and F are least specific networks. |
| Networks F and G are most specific networks. |
| |
+-------------------------------------------------------+Figure 2: Nesting Example 2
the next bit assumes there are no overlapping networks in the database 🧐 two networks overlap when they partially cover each other's space. here's how that looks 🎀
A |---------------------|
B |----------------------------|Figure 3: Nesting Example 3
here, networks A and B are overlapping networks, because network A partially encompasses network B's space and network B partially encompasses network A's space 🔥
C |------------------|
D |---------|Figure 4: Nesting Example 4
here, networks C and D are NOT overlapping networks. even though network D covers part of network C's space, network C doesn't partially encompass network D's space. it covers network D completely 💅
the address directory can hold more than one network with the same range. those are called exact match networks 🍓
the parent/child relationship in the internet address directory is unidirectional 🧚 there might also be a parent/child relationship between exact match networks, but a network cannot be a parent and a child of its exact match network at the same time 🙃
the following are the nested matching searches 🔎
(1) all less specifics search: given a range, find all the networks that contain that range (that is, all less specifics and exact matches). these are the networks that fulfill this condition:
(start(network) <= start(search)) AND (end(network) >= end(search))(2) one-level less specifics search: given a range, find only the most specific network that contains that range (there could be multiple networks, but usually it's a single one). this is the set of networks from (1), with the provision that no network in the return set is contained by any other network in the set. if there are exact match networks in the set from (1), they both must appear in the result set. the result set may contain a network that is an exact match to the query range, if the search allows exact matches 🌈
A |-------------------------------|
B |---------------------------|
C |-------|
Query |- - - - - - - - - -|Figure 5: Nesting Example 5
in the case above, the query must return B 💜
A |-------------------------------|
B |---------------------------|
C |---------------------------|
D |-------|
Query |- - - - - - - - - -|Figure 6: Nesting Example 6
here, the query must return B and C, because they're exact matches of each other 👯
A |-------------------------------|
B |---------------------------|
C |---------------------------|
D |-------|
Query |- - - -|Figure 7: Nesting Example 7
here, the query must return B and C, because they're exact matches of each other. D must not be in the result set, since it's an exact match to the query if the search specifies that exact matches of the query range should not appear in the result set 🙈
in Figure 7, if the search specifies that exact matches to the query range are allowed in the result set, then only D must be returned 🫧
(3) all more specifics search: given a range, find all the networks that are fully within that range. the search contains a flag that says whether an exact match to the query range should appear in the result set or not. so the result set may or may not contain the exact match to the query range, depending on what the search asks for ✨ these are the networks that fulfill this condition:
(start(network) >= start(search)) AND (end(network) <= end(search))(4) one-level more specifics search: given a range, find only the least specific networks that are fully within that range. this is the set of networks from (3), with the provision that no network in the return set contains any other network in the return set 🧁
Query |- - - - - - - - - - - - - - - - - - - - - - -|
A |------------------|
B |-------------------------|
C |--------|
D |---------|Figure 8: Nesting Example 8
(5) exact match search: given a range, find the networks that begin and end on the same IP addresses as the range. these are the networks that fulfill this condition:
(start(network) = start(search)) AND (end(network) = end(search))(6) given a range, find the exact match network if it exists. if it doesn't, perform the (2) search 🎯
the following are the parent-child relationship searches 👪
(7) given a network handle, find the network that is the direct (one level up) parent of the network with the given handle 🌷
(8) given a network handle, find the network or networks that are direct (one level down) children of the network with the given handle 🌼
5. Formal XML Syntax 📜
this IP address registry is specified in XML Schema notation. the formal syntax here is a complete schema representation, suitable for automated validation of an XML instance when it's combined with the formal schema syntax of IRIS 🤓
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:areg="urn:ietf:params:xml:ns:areg1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:areg1"
elementFormDefault="qualified" >
<import namespace="urn:ietf:params:xml:ns:iris1" />
<annotation>
<documentation> IP address registry schema derived from IRIS
schema </documentation>
</annotation>
<!-- ========================================= -->
<!-- -->
<!-- Query Types -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Find Autonomous Systems By Name -->
<!-- Find Networks By Name -->
<!-- -->
<complexType name="findByNameType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="name"
type="areg:exactOrPartialMatchParameter" />
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByName" type="areg:findByNameType"
substitutionGroup="iris:query" />
<element name="findAutonomousSystemsByName"
type="areg:findByNameType"
substitutionGroup="iris:query" />Okay bestie, we're still in the XML era 🎀 Here's the next chunk of the schema, with every element and attribute name exactly as written 💅
<!-- -->
<!-- Address/Address Range type for -->
<!-- Find Network -->
<!-- -->
<complexType name="addressRangeType">
<sequence>
<element name="start" type="token" />
<element name="end" type="token" minOccurs="0" maxOccurs="1" />
</sequence>
</complexType>
<!-- -->
<!-- Find Networks By Address -->
<!-- -->
<complexType name="findNetworksByAddressType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<element name="ipv4Address" type="areg:addressRangeType"
/>
<element name="ipv6Address" type="areg:addressRangeType"
/>
</choice>
<element name="specificity">
<complexType>
<simpleContent>
<extension base="areg:specificityType" >
<attribute name="allowEquivalences" type="boolean"
default="false" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByAddress"
type="areg:findNetworksByAddressType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find AS By Number -->
<!-- -->
<complexType name="findASByNumberType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="asNumberStart" type="token" />
<element name="asNumberEnd" type="token" minOccurs="0"
maxOccurs="1" />
<element name="specificity">
<complexType>
<simpleContent>
<extension base="areg:specificityType" >
<attribute name="allowEquivalences" type="boolean"
default="false" />
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findASByNumber" type="areg:findASByNumberType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Specificity Type -->
<!-- -->
<simpleType name="specificityType">
<restriction base="string">
<enumeration value="exact-match" />
<enumeration value="all-less-specific" />
<enumeration value="one-level-less-specific" />
<enumeration value="all-more-specific" />
<enumeration value="one-level-more-specific" />
</restriction>
</simpleType>
<!-- -->
<!-- Find By Contact -->
<!-- -->
<complexType name="findByContactType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<group ref="areg:contactSearchGroup" />
<element name="contactHandle"
type="areg:exactMatchParameter" />
</choice>
<element name="returnedResultType" minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="returnASs" />
<enumeration value="returnIPv4Networks" />
<enumeration value="returnIPv6Networks" />
<enumeration value="returnOrganizations" />
</restriction>
</simpleType>
</element>
<element name="role" minOccurs="0" maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="adminContact" />
<enumeration value="techContact" />
<enumeration value="nocContact" />
<enumeration value="abuseContact" />
<enumeration value="otherContact" />
</restriction>
</simpleType>
</element>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findByContact" type="areg:findByContactType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Networks By Handle -->
<!-- -->
<complexType name="findNetworksByHandleType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="networkHandle" type="token" />
<element name="specificity"
type="areg:specificitySubsetType" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByHandle"
type="areg:findNetworksByHandleType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Specificity Subtype -->
<!-- -->
<simpleType name="specificitySubsetType">
<restriction base="string">
<enumeration value="all-less-specific" />
<enumeration value="one-level-less-specific" />
<enumeration value="all-more-specific" />
<enumeration value="one-level-more-specific" />
</restriction>
</simpleType>
<!-- -->
<!-- Find Contacts -->
<!-- -->
<complexType name="findContactsType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<group ref="areg:contactSearchGroup" />
<element name="organizationId"
type="areg:exactMatchParameter" />
</choice>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findContacts" type="areg:findContactsType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Organizations -->
<!-- -->
<complexType name="findOrganizationsType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<choice>
<element name="organizationName"
type="areg:exactOrPartialMatchParameter" />
<group ref="areg:commonSearchGroup" />
</choice>
<element name="language" type="language" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findOrganizations" type="areg:findOrganizationsType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Find Networks by Name Server -->
<!-- -->
<complexType name="findNetworksByNameServerType">
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="nameServer" type="normalizedString" />
<element name="returnedResultType" minOccurs="0"
maxOccurs="1" >
<simpleType>
<restriction base="string" >
<enumeration value="returnIPv4Networks" />
<enumeration value="returnIPv6Networks" />
</restriction>
</simpleType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByNameServer"
type="areg:findNetworksByNameServerType"
substitutionGroup="iris:query" />
<!-- -->
<!-- Contact Search Group -->
<!-- -->
<group name="contactSearchGroup">
<choice>
<element name="commonName"
type="areg:exactOrPartialMatchParameter" />
<group ref="areg:commonSearchGroup" />
</choice>
</group>
<!-- -->
<!-- Common Search Group -->
<!-- -->
<group name="commonSearchGroup">
<choice>
<element name="eMail" type="areg:domainResourceParameter" />
<element name="city" type="areg:exactMatchParameter" />
<element name="region" type="areg:exactMatchParameter" />
<element name="country" type="areg:exactMatchParameter" />
<element name="postalCode" type="areg:exactMatchParameter" />
</choice>
</group>
<!-- -->
<!-- Parameters for Search Groups -->
<!-- -->
<complexType name="exactOrPartialMatchParameter">
<choice>
<group ref="areg:partialMatchGroup" />
<group ref="areg:exactMatchGroup" />
</choice>
</complexType>
<complexType name="exactMatchParameter">
<group ref="areg:exactMatchGroup" />
</complexType>
<complexType name="partialMatchParameter">
<sequence>
<group ref="areg:partialMatchGroup" />
</sequence>
</complexType>
<complexType name="domainResourceParameter" >
<choice>
<group ref="areg:exactMatchGroup" />
<element name="inDomain" type="token" />
</choice>
</complexType>
<group name="partialMatchGroup">
<choice>
<sequence>
<element name="beginsWith">
<simpleType>
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
</element>
<element minOccurs="0" ref="areg:endsWith"/>
</sequence>
<element ref="areg:endsWith" />
</choice>
</group>
<element name="endsWith">
<simpleType>
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
</element>
<group name="exactMatchGroup">
<sequence>
<element name="exactMatch" type="normalizedString" />
</sequence>
</group>
<!-- ========================================= -->
<!-- -->
<!-- Result Types -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- IPv4 and IPv6 Network Results -->
<!-- --><complexType name="ipNetworkType"> <complexContent> <extension base="iris:resultType"> <sequence> <element name="networkHandle" type="token" minOccurs="0" maxOccurs="1" /> <element name="name" minOccurs="0" maxOccurs="1" type="normalizedString" /> <element name="startAddress" type="token" /> <element name="endAddress" type="token" /> <sequence minOccurs="0" maxOccurs="1"> <element name="networkType" type="normalizedString" minOccurs="1" maxOccurs="1" /> <element name="networkTypeInfo" type="iris:entityType" minOccurs="0" maxOccurs="1" /> </sequence> <element name="nameServer" type="normalizedString" minOccurs="0" maxOccurs="unbounded" /> <element name="organization" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <choice minOccurs="0" maxOccurs="1" > <element name="parent" type="iris:entityType" /> <element name="noParent"> </element> </choice> <group ref="areg:contactGroup" /> <group ref="areg:commonGroup" /> </sequence> </extension> </complexContent> </complexType>
<element name="ipv4Network" type="areg:ipNetworkType" substitutionGroup="iris:result" />
<element name="ipv6Network" type="areg:ipNetworkType" substitutionGroup="iris:result" />
<!-- --> <!-- Autonomous System --> <!-- -->
<complexType name="autonomousSystemType"> <complexContent> <extension base="iris:resultType"> <sequence>
<element name="asHandle" type="token" minOccurs="0" maxOccurs="1" /> <element name="asNumberStart" type="integer" minOccurs="0" maxOccurs="1" /> <element name="asNumberEnd" type="integer" minOccurs="0" maxOccurs="1" /> <element name="name" type="normalizedString" minOccurs="0" maxOccurs="1" /> <element name="organization" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <choice minOccurs="0" maxOccurs="1"> <element name="parent" type="iris:entityType" /> <element name="noParent" /> </choice> <group ref="areg:contactGroup" /> <group ref="areg:commonGroup" /> </sequence> </extension> </complexContent> </complexType>
<element name="autonomousSystem" type="areg:autonomousSystemType" substitutionGroup="iris:result" />
<!-- --> <!-- Contact --> <!-- -->
<complexType name="contactType"> <complexContent> <extension base="iris:resultType"> <sequence> <element name="contactHandle" type="token" minOccurs="0" maxOccurs="1" /> <element name="commonName" type="normalizedString" minOccurs="0" maxOccurs="1" /> <element name="eMail" type="normalizedString" minOccurs="0" maxOccurs="unbounded" /> <element name="sip" type="normalizedString" minOccurs="0" maxOccurs="unbounded" /> <element name="organization" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="postalAddress" minOccurs="0" maxOccurs="unbounded"> <complexType> <sequence> <element name="address" type="string" minOccurs="0" maxOccurs="1" />
<element name="city" type="string" minOccurs="0" maxOccurs="1" /> <element name="region" type="string" minOccurs="0" maxOccurs="1" /> <element name="postalCode" type="normalizedString" minOccurs="0" maxOccurs="1" /> <element name="country" type="token" minOccurs="0" maxOccurs="1" /> </sequence> </complexType> </element> <element name="phone" minOccurs="0" maxOccurs="unbounded" > <complexType> <sequence> <element name="number" type="normalizedString" /> <element name="extension" type="normalizedString" minOccurs="0" maxOccurs="unbounded" /> <element name="type" type="normalizedString" minOccurs="0" maxOccurs="1" /> </sequence> </complexType> </element> <group ref="areg:commonGroup" /> </sequence> </extension> </complexContent> </complexType>
<element name="contact" type="areg:contactType" substitutionGroup="iris:result" />
<!-- --> <!-- Organization --> <!-- -->
<complexType name="organizationType"> <complexContent> <extension base="iris:resultType"> <sequence> <element name="name" type="normalizedString" minOccurs="0" maxOccurs="1" /> <element name="eMail" type="normalizedString" minOccurs="0" maxOccurs="unbounded" /> <element name="id" type="token" /> <element name="postalAddress" minOccurs="0" maxOccurs="unbounded"> <complexType> <sequence>
<element name="address" type="string" minOccurs="0" maxOccurs="1" /> <element name="city" type="string" minOccurs="0" maxOccurs="1" /> <element name="region" type="string" minOccurs="0" maxOccurs="1" /> <element name="postalCode" type="normalizedString" minOccurs="0" maxOccurs="1" /> <element name="country" type="token" minOccurs="0" maxOccurs="1" /> </sequence> </complexType> </element> <element name="phone" minOccurs="0" maxOccurs="unbounded" > <complexType> <sequence> <element name="number" type="normalizedString" /> <element name="extension" type="normalizedString" minOccurs="0" maxOccurs="unbounded" /> <element name="type" type="normalizedString" minOccurs="0" maxOccurs="1" /> </sequence> </complexType> </element> <group ref="areg:contactGroup" /> <group ref="areg:commonGroup" /> </sequence> </extension> </complexContent> </complexType>
<element name="organization" type="areg:organizationType" substitutionGroup="iris:result" />
<!-- --> <!-- Contact Group --> <!-- -->
<group name="contactGroup"> <sequence> <element name="adminContact" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="techContact" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="nocContact" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> <element name="abuseContact" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" />
<element name="otherContact" type="iris:entityType" minOccurs="0" maxOccurs="unbounded" /> </sequence> </group>
<!-- --> <!-- Common Group --> <!-- -->
<group name="commonGroup"> <sequence> <element name="numberResourceRegistry" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element name="registrationDate" type="dateTime" minOccurs="0" maxOccurs="1" /> <element name="lastUpdatedDate" type="dateTime" minOccurs="0" maxOccurs="1" /> <element ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded" /> </sequence> </group> </schema>
Figure 9
6. BEEP Transport Compliance ✨
okay so IRIS lets you add some extra stuff on top of its core capabilities 💅 this section lays out the extensions that IRIS-BEEP [3] allows.
6.1. Message Pattern
this registry type just uses the default message pattern from IRIS-BEEP [3], no drama 🦋
6.2. Server Authentication
same vibe for auth: it uses the default server authentication method from IRIS-BEEP [3] 🔐
7. URI Resolution 🌸
7.1. Application Service Label
check Section 9 for the application service label registration 🏷️
7.2. Operational Considerations
address registries don't have natural links to DNS 🥺 using the reverse DNS tree causes problems for IP address delegation (delegations don't fall on byte boundaries, which is the opposite of reverse DNS), and DNS doesn't currently hold any information about autonomous system delegation.
so for top-down resolution to actually work, it is requested that the IAB instruct IANA to insert and maintain a NAPTR DNS resource record for areg.iris.arpa, as described in Section 9 ✨
7.3. Top-Down Resolution
the top-down alternative resolution method MUST be identified as 'top' in IRIS URIs 💖
here's how the process goes:
- The IRIS [2] direct-resolution process is tried against areg.iris.arpa.
- If the direct-resolution process yields no server for which a connection can be made, then a negative response is returned, and no further action is taken.
It is RECOMMENDED that IRIS clients issuing AREG1 requests use the 'top' resolution method when no resolution method has been explicitly given by a user. IRIS servers accepting AREG1 requests that seek information for which they are not authoritative SHOULD refer clients using the 'top' resolution method 🫶
8. Internationalization Considerations 🌈
this document lays out no new considerations for internationalization beyond those specified in IRIS [2] 🌍
9. IANA Considerations 👑
the following URN has been registered with IANA according to the IANA considerations defined in IRIS [2]:
urn:ietf:params:xml:ns:areg1
the following S-NAPTR application service label has been registered with IANA according to the IANA considerations defined in IRIS [2]: AREG1 💅
under instructions from the IAB, the IANA will create a new second level domain under .arpa called iris (i.e., iris.arpa.). The contents of this new domain are to be under the control of the IAB. Under instructions from the IAB, the IANA will insert and maintain a NAPTR DNS resource record in the iris.arpa. domain for the name areg.iris.arpa. The initial contents for that record is:
areg.iris.arpa. ;; order pref flags service re replacement IN NAPTR 100 10 "" "AREG1:iris.xpc:iris.lwz" "" areg.nro.net
10. Security Considerations ✨
okay bestie, security time 🔒 this doc is literally saying it adds no new security stuff on top of what [2] already covers. so all the security drama lives in IRIS itself 💅 (hi [2] 👋)
11. References 📚
11.1. Normative References
- [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
- [2] Newton, A. and M. Sanz, "IRIS: The Internet Registry Information Service (IRIS) Core Protocol", RFC 3981, January 2005.
- [3] Newton, A. and M. Sanz, "Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)", RFC 3983, January 2005.
- [4] Newton, A., "Cross Registry Internet Service Protocol (CRISP) Requirements", RFC 3707, February 2004.
11.2. Informative References
- [5] World Wide Web Consortium, "Extensible Markup Language (XML) 1.0", W3C XML, February 1998,
<http://www.w3.org/TR/1998/REC-xml-19980210>. - [6] World Wide Web Consortium, "Namespaces in XML", W3C XML Namespaces, January 1999,
<http://www.w3.org/TR/1999/REC-xml-names-19990114>. - [7] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C XML Schema, October 2000,
<http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>. - [8] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C XML Schema, October 2000,
<http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>. - [9] International Organization for Standardization, "Codes for the representation of names of countries, 3rd edition", ISO Standard 3166, August 1988.
Appendix A. Privacy Considerations 🫣
ngl this one is a big deal 😭 internet address registries are sitting on contact details and other info that could totally get misused. so the XML Schema here is built on purpose so that putting any data into a response is optional 🎀 it depends on what the registry serving the data needs and what its policies say.
and when you pair this with the authentication stuff from an IRIS transfer protocol, registries can make authorization policies that fit their needs without wrecking general privacy. like, say the members of a registry decide that NOC contact email addresses should only be visible to other members of that registry 🔐. to make that happen, the XML elements for NOC contacts will never show up in a response to someone who hasn't been authenticated as a member of the registry. main character privacy energy 💜
Appendix B. Example Requests and Responses 🍓
the examples in this section use the string "C:" to show data a client sends to a server, and "S:" to show data a server sends back to a client. let's gooo 🚀
B.1. Example 1
here we're looking up the entity for the contact-handle 'JN560-RIR1' 🧚
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:iris1 iris.xsd" >
C:
C: <searchSet>
C:
C: <lookupEntity
C: registryType="urn:ietf:params:xml:ns:areg1"
C: entityClass="contact-handle"
C: entityName="JN560-RIR1" />
C:
C: </searchSet>
C:
C: </request>
S: <?xml version="1.0"?>
S: <iris:response
S: xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <iris:resultSet>
S: <iris:answer>
S:
S: <contact
S: authority="rir.example.net"
S: registryType="areg1"
S: entityClass="contact-handle"
S: entityName="JN560-RIR1">
S:
S: <contactHandle>JN560-RIR1</contactHandle>
S:
S: <commonName>Bob Smurd</commonName>
S:
S: <organization
S: iris:referentType="organization"
S: authority="rir.example.net"
S: registryType="areg1"
S: entityClass="organization-id"
S: entityName="ORGX">
S: <iris:displayName
S: language="en">
S: Organization X, Inc.
S: </iris:displayName>
S: </organization>
S:
S: <phone>
S: <number>+1-703-555-5555</number>
S: <type>office</type>
S: </phone>
S:
S: </contact>
S:
S: </iris:answer>
S: </iris:resultSet>
S:
S: </iris:response>
Figure 11: Example 1B.2. Example 2
this one is a query to find the IP networks that contain a given address 🌈
C: <?xml version="1.0"?>
C: <request xmlns="urn:ietf:params:xml:ns:iris1"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C:
C: <searchSet>
C: <findNetworksByAddress
C: xmlns="urn:ietf:params:xml:ns:areg1">
C:
C: <ipv4Address>
C: <start>192.0.2.134</start>
C: </ipv4Address>
C:
C: <specificity
C: allowEquivalences="true"
C: >one-level-less-specific</specificity>
C:
C: </findNetworksByAddress>
C: </searchSet>
C:
C: </request>
S: <?xml version="1.0"?>
S: <iris:response xmlns:iris="urn:ietf:params:xml:ns:iris1"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
S:
S: <iris:resultSet>
S: <iris:answer>
S: <areg:ipv4Network
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:areg="urn:ietf:params:xml:ns:areg1"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-128-1" >
S: <networkHandle>
S: NET-192-0-2-128-1
S: </networkHandle>
S: <name>
S: UU-192-0-2-D6
S: </name>
S: <startAddress>
S: 192.0.2.128
S: </startAddress>
S: <endAddress>
S: 192.0.2.255
S: </endAddress>
S: <networkType>reassigned</networkType>
S: <organization
S: iris:referentType="areg:organization"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="organization-id" entityName="ORGX">
S: <iris:displayName language="en">
S: Organization X, Inc.
S: </iris:displayName>
S: </organization>
S: <parent
S: iris:referentType="areg:ipv4Network"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-1"/>
S: <techContact
S: iris:referentType="areg:contact"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="contact-handle" entityName="JN560-RIR1">
S: <iris:displayName language="en">
S: Smurd, Bob
S: </iris:displayName>
S: </techContact>
S: <registrationDate>
S: 2002-11-18T00:00:00-00:00
S: </registrationDate>
S: <lastUpdatedDate>
S: 2002-11-18T00:00:00-00:00
S: </lastUpdatedDate>
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice"/>
S: </areg:ipv4Network>
S: <areg:ipv4Network
S: xmlns="urn:ietf:params:xml:ns:areg1"
S: xmlns:areg="urn:ietf:params:xml:ns:areg1"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-2" >
S: <networkHandle>
S: NET-192-0-2-0-2
S: </networkHandle>
S: <name>
S: UU-192-0-2-0-D5
S: </name>
S: <startAddress>
S: 192.0.2.0
S: </startAddress>
S: <endAddress>
S: 192.0.2.255
S: </endAddress>
S: <networkType>direct allocation</networkType>
S: <nameServer>auth03.ns.example.org</nameServer>
S: <nameServer>auth00.ns.example.org</nameServer>
S: <organization
S: iris:referentType="areg:organization"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="organization-id" entityName="ORGY">
S: <iris:displayName language="en">
S: Organization Y, Inc.
S: </iris:displayName>
S: </organization>
S: <parent
S: iris:referentType="areg:ipv4Network"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="ipv4-handle" entityName="NET-192-0-2-0-1"/>
S: <techContact
S: iris:referentType="areg:contact"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="contact-handle" entityName="OA12-RIR1" />
S: <registrationDate>
S: 2000-10-27T00:00:00-00:00
S: </registrationDate>
S: <lastUpdatedDate>
S: 2002-02-13T00:00:00-00:00
S: </lastUpdatedDate>
S: <iris:seeAlso
S: iris:referentType="ANY"
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice"/>
S: </areg:ipv4Network>
S: </iris:answer>
S: <iris:additional>
S: <iris:simpleEntity
S: authority="rir.example.net" registryType="areg1"
S: entityClass="local" entityName="portability-notice" >
S: <iris:property name="portability" language="en">
S: Addresses within this block are non-portable.
S: </iris:property>
S: </iris:simpleEntity>
S: </iris:additional>
S: </iris:resultSet>
S:
S: </iris:response>
Figure 12: Example 2Appendix C. Specificity Examples ✨
okay bestie, this appendix is a whole gallery of examples showing how the specificity options work for network and ASN searches 🧚 Every figure shows the same database plus one query, followed by what comes back. Let's look at them 💅
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Contents of the DB
Figure 13: Specificity Example 1Okay so now we add a query 👀
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - | 192.0.2.0 - 192.0.2.9
Exact match (1)
Result: C
Figure 14: Specificity Example 2Bestie, this one is an exact match, and the result is C 🎀
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - | 192.0.2.0 - 192.0.2.12
Exact match (2)
Result: None
Figure 15: Specificity Example 3Nothing matches this one, so the result is None 🙈
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
All more specifics, allowEquivalences = false
Result: C, F, & G (A is not included; exact match)
Figure 16: Specificity Example 4Here we ask for all the more specifics with allowEquivalences = false. A is left out because it's an exact match, so the results are C, F, & G 🦋
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
All more specifics, allowEquivalences = true
Result: A, C, F, & G (A is included; exact match)
Figure 17: Specificity Example 5Same query, but now allowEquivalences = true, so A gets to come along to the party too 🎉
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
One level more specifics, allowEquivalences = false
Result: C
Figure 18: Specificity Example 6This time we only look one level down the more-specifics, and with allowEquivalences = false the answer is just C 🌸
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - - - - | 192.0.2.0 - 192.0.2.15
One level more specifics, allowEquivalences = true
Result: A
Figure 19: Specificity Example 7Same one-level search, but with allowEquivalences = true, which gives us A 🫶
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
All less specifics, allowEquivalences = true
Result: A, C, & G (G is included; exact match)
Figure 20: Specificity Example 8Now we flip it and go looking for less specifics. With allowEquivalences = true, G gets included because it's an exact match, so the results are A, C, & G 💖
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
All less specifics, allowEquivalences = false
Result: A & C (G is not included; exact match)
Figure 21: Specificity Example 9Same search, but allowEquivalences = false, so G is dropped and we're left with A & C 🍓
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
One level less specifics, allowEquivalences = true
Result: G (the exact match)
Figure 22: Specificity Example 10One level less, with allowEquivalences = true, and the result is G, the exact match 👑
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query |- - | 192.0.2.6 - 192.0.2.9
One level less specifics, allowEquivalences = false
Result: C
Figure 23: Specificity Example 11One level less with allowEquivalences = false gives us C 🦋
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query|- - - - - - | 192.0.2.0 - 192.0.2.8
One level less specifics, allowEquivalences = false or true
Result: C
Figure 24: Specificity Example 12This query covers 192.0.2.0 - 192.0.2.8. Either setting of allowEquivalences gives C here ✨
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query = E
Find parent (Query argument is a handle)
Result: D
Figure 25: Specificity Example 13Now the query is a handle, E, and we're asking for its parent. The result is D 🧚
A |------------------| 192.0.2.0 - 192.0.2.15
B |------------------| 192.0.2.16 - 192.0.2.31
C |--------------| 192.0.2.0 - 192.0.2.9
D |---------------| 192.0.2.16 - 192.0.2.30
E |---------------| 192.0.2.16 - 192.0.2.30
F |--------| 192.0.2.0 - 192.0.2.5
G |----| 192.0.2.6 - 192.0.2.9
Query = D
Find child (Query argument is a handle)
Result: E
Figure 26: Specificity Example 14Last one! The handle is D this time, and we're looking for its child, which is E 🌈
Appendix D. Contributors 🎀
David Blacka and Tim Christensen made substantial contributions to this document. Literally the MVPs 🫶
Appendix E. Acknowledgements 💜
Eric Hall, William Leibzon, April Marine, George Michaelson, Tim Christensen Cathy Murphy, Andrei Robachevsky, Marcos Sanz, Frederico Neves, Ted Hardie, and many others contributed constructively in the mailing list discussions and IETF Meeting sessions. Huge thanks to everyone who showed up in the mailing lists and at the IETF Meeting sessions 🙌
Authors' Addresses 🧚
Engin Gunduz
RIPE NCC
Singel 258
Amsterdam 1016AB
The Netherlands
Phone: +31 20 535 4444
EMail: e.gunduz@computer.org
Andrew L. Newton
VeriSign, Inc.
21345 Ridgetop Circle
Sterling, VA 20166
USA
Phone: +1 703 948 3382
EMail: andy@hxr.us
Shane W. Kerr
RIPE NCC
Singel 258
Amsterdam 1016AB
The Netherlands
Phone: +31 20 535 4444
EMail: shane@time-travellers.orgFull Copyright Statement 🔥
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property ✨
okay so, the IETF is not taking a side on whether any IPR (intellectual property rights) or other rights someone might claim over the tech in this doc are valid, or how far they reach 🙈 it also doesn't say it personally checked for any of that. no cap. if you want the rules on rights in RFC docs, check BCP 78 and BCP 79 💅
copies of IPR disclosures made to the IETF Secretariat, plus any assurances of licenses that will be made available, or the result of an attempt to get a general license or permission to use those proprietary rights for implementers or users of this spec, can be found at the IETF online IPR repository: http://www.ietf.org/ipr 🦋
the IETF literally invites any interested party to bring any copyrights, patents, patent applications, or other proprietary rights that may cover tech needed to implement this standard to its attention 🫶 just send it to ietf-ipr@ietf.org 💌
Acknowledgement 🎀
funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA) 🌈 iconic supporters, honestly 👑
📦 where this page comes from
- ietf: rfc4698 2006-10
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms