One document matched: draft-ietf-crisp-firs-ipv4-03.txt
Differences from draft-ietf-crisp-firs-ipv4-02.txt
INTERNET-DRAFT Eric A. Hall
Document: draft-ietf-crisp-firs-ipv4-03.txt August 2003
Expires: March, 2004
Category: Experimental
Defining and Locating IPv4 Address Blocks
in the Federated Internet Registry Service
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document defines LDAP schema and searching rules for IPv4
address blocks, in support of the Federated Internet Registry
Service (FIRS) described in [FIRS-ARCH] and [FIRS-CORE].
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
Table of Contents
1. Introduction...............................................2
2. Prerequisites and Terminology..............................2
3. Naming Syntax..............................................3
4. Object Classes and Attributes..............................4
5. Query Processing Rules.....................................8
5.1. Query Pre-Processing....................................9
5.2. LDAP Matching..........................................10
5.3. Example Query..........................................11
6. Security Considerations...................................13
7. IANA Considerations.......................................13
8. Normative References......................................13
9. Changes from Previous Versions............................14
10. Author's Address..........................................15
11. Acknowledgments...........................................15
12. Full Copyright Statement..................................16
1. Introduction
This specification defines the naming syntax, object classes,
attributes, matching filters, and query processing rules for
storing and locating IPv4 address blocks in the FIRS service.
Refer to [FIRS-ARCH] for information on the FIRS architecture and
[FIRS-CORE] for the schema definitions and rules which govern the
FIRS service as a whole.
Note that reverse-lookup DNS domains for IPv4 address blocks are
managed as DNS domain entries in [FIRS-DNS]. These are entirely
different network resources, and should not be confused with IPv4
address block entries.
The definitions in this specification are intended to be used with
FIRS. Their usage outside of FIRS is not prohibited, but any such
usage is beyond this specification's scope of authority.
2. Prerequisites and Terminology
The complete set of specifications in the FIRS collection
cumulative define a structured and distributed information service
using LDAPv3 for the data-formatting and transport functions. This
specification should be read in the context of that set, which
currently includes [FIRS-ARCH], [FIRS-CORE], [FIRS-DNS],
[FIRS-DNSRR], [FIRS-CONTCT], [FIRS-ASN] and [FIRS-IPV6].
Hall I-D Expires: March 2004 [page 2]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
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.
3. Naming Syntax
The naming syntax for IPv4 address blocks in FIRS MUST follow the
form of "cn=<inetIpv4NetworkSyntax>,cn=inetResources,<partition>",
where <inetIpv4NetworkSyntax> is the IPv4 address block resource,
and where <partition> is a sequence of domainComponent relative
distinguished names which identifies the scope of authority for
the selected directory partition.
The inetIpv4NetworkSyntax rules use the traditional "dotted-quad"
notation, where each of four sub-components provide a decimal
value that represents one octet from a 32-bit IPv4 address, with
the sub-components being separated by a full-stop (period)
character, and with the four-part sequence being followed by a "/"
character and a decimal "prefix" value.
Entries which use the inetIpv4NetworkSyntax MUST use the starting
address from a range of inclusive addresses, and MUST use CIDR
prefix notation. In this manner, it is possible to create an
inetIpv4Network entry for a range of addresses of any size,
including a single host address or the entire IPv4 address space.
The leading zeroes from each octet MUST be removed before the
value is stored or used in a query. Octets which have a value of
zero MUST be represented by the single-digit value of "0".
If an input string does not match this syntax, a FIRS-aware
application MAY attempt to manipulate the input string to form a
valid value. For example, if a user enters a traditional IPv4
address without specifying a prefix value, the application MAY
append "/32" to the end of the input string to form a valid
assertion value. Similarly, if a user provides an octal or
hexadecimal value, the client MAY attempt to convert the input
string to the traditional dotted-quad IPv4 address notation.
Hall I-D Expires: March 2004 [page 3]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
An augmented BNF for this syntax is as follows:
inetIpv4NetworkSyntax = inetIpv4Octet "." inetIpv4Octet "."
inetIpv4Octet "." inetIpv4Octet "/" inetIpv4Prefix
inetIpv4Octet = decimal value between "0" and "255"
inclusive, with the non-affective leading zeroes removed
inetIpv4Prefix = decimal value between "1" and "32"
inclusive, with the non-affective leading zeroes removed
The schema definition for inetIpv4NetworkSyntax is as follows:
inetIpv4NetworkSyntax
( 1.3.6.1.4.1.7161.1.5.0
NAME 'inetIpv4NetworkSyntax'
DESC 'An IPv4 address and prefix.' )
For example, an IPv4 address block with a range of addresses
between "10.0.0.0" and "10.0.255.255" inclusive would be written
as "cn=10.0.0.0/16", while a host address of "192.0.2.14" would be
written as "cn=192.0.2.14/32".
Note that the entry name of "cn=0.0.0.0/0" encompasses the entire
IPv4 address space.
Note that the use of "/" is illegal as data in URLs, and MUST be
escaped before it is stored in a URL as data.
4. Object Classes and Attributes
IPv4 address block entries in FIRS MUST use the inetIpv4Network
object class, in addition to the mandatory object classes defined
in [FIRS-CORE]. IPv4 address block entries MUST be treated as
containers capable of holding subordinate entries.
If an entry exists as a referral source, the entry MUST be defined
with the referral object class, in addition to the other object
classes defined above. Referral sources MUST NOT contain
subordinate entries. Refer to section 3.5 of [FIRS-CORE] for more
information on referral entries in FIRS.
The inetIpv4Network object class is a structural object class
which is subordinate to the inetResources object class. The
inetIpv4Network object class has no mandatory attributes, although
Hall I-D Expires: March 2004 [page 4]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
it does have several optional attributes. The inetIpv4Network
object class also inherits the attributes defined in the
inetResources object class, including the "cn" naming attribute.
The schema definition for the inetIpv4Network object class is as
follows:
inetIpv4Network
( 1.3.6.1.4.1.7161.1.5.1
NAME 'inetIpv4Network'
DESC 'IPv4 network attributes.'
SUP inetResources
STRUCTURAL
MAY ( inetIpv4DelegationStatus $ inetIpv4DelegationDate $
inetIpv4Registrar $ inetIpv4Registry $ inetIpv4Contacts $
inetIpv4RoutingContacts $ inetIpv4ParentNetwork $
inetIpv4SiblingNetworks $ inetIpv4ChildNetworks ) )
The attributes from the inetIpv4Network object class are described
below:
inetIpv4Contacts
( 1.3.6.1.4.1.7161.1.5.2
NAME 'inetIpv4Contacts'
DESC 'Contacts for general administrative issues concerning
this address block.'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.7161.1.4.0 )
inetIpv4DelegationDate
( 1.3.6.1.4.1.7161.1.5.3
NAME 'inetIpv4DelegationDate'
DESC 'Date this address block was delegated.'
EQUALITY generalizedTimeMatch
ORDERING generalizedTimeOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.24
SINGLE-VALUE )
inetIpv4DelegationStatus
( 1.3.6.1.4.1.7161.1.5.4
NAME 'inetIpv4DelegationStatus'
DESC 'Delegation status of this address block.'
EQUALITY numericStringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{2}
SINGLE-VALUE )
Hall I-D Expires: March 2004 [page 5]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
NOTE: In an effort to facilitate internationalization and
programmatic processing, the current status of a delegation
is identified by a 16-bit integer. The values and status
mapping is as follows:
0 Reserved delegation (permanently inactive)
1 Assigned and active (normal state)
2 Assigned but not yet active (new delegation)
3 Assigned but on hold (disputed)
4 Assignment revoked (database purge pending)
Additional values are reserved for future use, and are to
be administered by IANA.
Note that there is no status code for "unassigned";
unassigned entries SHOULD NOT exist, and SHOULD NOT be
returned as answers.
inetIpv4Registrar
( 1.3.6.1.4.1.7161.1.5.5
NAME 'inetIpv4Registrar'
DESC 'Registrar or sub-registry who delegated this address
block.'
EQUALITY caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
NOTE: The inetIpv4Registrar attribute uses a URL to
indicate the registrar who delegated the address block. The
attribute structure is identical to the labeledURI
attribute, as defined in [RFC2798], including the URL and
textual comments. The data can refer to any valid URL.
inetIpv4Registry
( 1.3.6.1.4.1.7161.1.5.6
NAME 'inetIpv4Registry'
DESC 'Regional registry where this address block is
managed.'
EQUALITY caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
NOTE: The inetIpv4Registry attribute uses a URL to indicate
the registry who is ultimately responsible for the address
block. The attribute structure is identical to the
labeledURI attribute, as defined in [RFC2798], including
the URL and textual comments. The data can refer to any
valid URL.
Hall I-D Expires: March 2004 [page 6]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
inetIpv4ParentNetworks
( 1.3.6.1.4.1.7161.1.5.7
NAME 'inetIpv4ParentNetworks'
DESC 'IPv4 parent networks directly associated with this
address block.'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.7161.1.5.0 )
inetIpv4SiblingNetworks
( 1.3.6.1.4.1.7161.1.5.8
NAME 'inetIpv4SiblingNetworks'
DESC 'IPv4 sibling networks directly associated with this
address block.'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.7161.1.5.0 )
inetIpv4ChildNetworks
( 1.3.6.1.4.1.7161.1.5.9
NAME 'inetIpv4ChildNetworks'
DESC 'IPv4 child networks directly associated with this
address block.'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.7161.1.5.0 )
inetIpv4RoutingContacts
( 1.3.6.1.4.1.7161.1.5.10
NAME 'inetIpv4RoutingContacts'
DESC 'Contacts for routing-related problems with this
address block.'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.7161.1.4.0 )
Hall I-D Expires: March 2004 [page 7]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
Two examples of the of the inetIpv4Network object class are shown
in Figure 1 below. The examples also include attributes from the
iinetResources, inetAssociatedResources, and referral object
classes.
cn=192.0.2.0/24,cn=inetResources,dc=in-addr,dc=arpa
[top object class]
[inetResources object class]
[inetIpv4Network object class]
[inetAssociatedResources object class]
|
+-attribute: description
| value: "Example Hosting's IPv4 address block"
|
+-attribute: inetIpv4Contacts
| value: "hostmaster@example.com"
|
+-attribute: inetAssociatedAsNumbers
| value: "65535"
|
+-attribute: inetIpv4Registry
| value: "http://www.arin.net/ (ARIN)"
|
+-cn=ref1,cn=192.0.2.0/24,cn=inetResources,dc=in-addr,dc=arpa
[top object class]
[inetResources object class]
[inetIpv4Network object class]
[referral object class]
|
+-attribute: ref
value: "ldap:///dc=arin,dc=net???
(1.3.6.1.4.1.7161.1.5.0.1:=192.0.2.0%2F24)"
Figure 1: The entry for the 192.0.2.0/24 address block in the
dc=in-addr,dc=arpa partition, and a child referral entry.
Note that the "/" separator in the LDAP referral URL shown in
Figure 1 has been escaped as "%2F" to be made URL-safe.
5. Query Processing Rules
Queries for IPv4 address blocks have several special requirements,
as discussed in the following sections.
Refer to [FIRS-CORE] for general information about FIRS queries.
Hall I-D Expires: March 2004 [page 8]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
5.1. Query Pre-Processing
FIRS clients MUST use the targeted bootstrap model by default for
IPv4 address block queries, using the "in-addr.arpa" zone as the
seed domain for the initial query.
FIRS clients MAY use the top-down or bottom-up bootstrap models
for queries if necessary or desirable. However, it is not likely
that entries will be found for all IPv4 address block resources
using these models. As such, the targeted bootstrap model will be
the most useful in most cases, and MUST be used by default.
When the bottom-up bootstrap model is used, the authoritative
partition for an IPv4 address block is determined by mapping the
normalized input to an associated reverse-lookup DNS domain name,
and then mapping the resulting DNS domain name to a sequence of
domainComponent labels.
The least-significant octet MUST include the subnet prefix in this
mapping process, except in those cases where the address falls on
an eight-bit boundary. In those cases where the address block
specifies a 32-bit host address, the subnet prefix MUST be
stripped from the input during the mapping process. In those cases
where the address block specifies a legacy "address class", the
least-significant octet and subnet prefix MUST both be stripped
from the input during the mapping process. These steps are
necessary in order to ensure that the reverse-pointer delegations
in the public DNS are correctly matched to the authoritative
partitions (note that these rules only apply to the mapping
process by which an authoritative partition is constructed, and do
not apply to the process by which the entry-specific relative
distinguished name is constructed).
For example, a host-specific IPv4 address block of "192.0.2.14/32"
would be mapped to the reverse-lookup DNS domain name of
"14.2.0.192.in-addr.arpa." which would in turn be mapped to
"dc=14,dc=2,dc=0,dc=192,dc=in-addr,dc=arpa", and which would then
be used as the authoritative partition for the bottom-up bootstrap
process. Similarly, a classless IPv4 address block of
"192.0.2.0/20" would be mapped to the reverse-lookup domain name
of "0/20.14.2.0.192.in-addr.arpa", which would be mapped to the
fully-qualified distinguished name of
"dc=0/20,dc=14,dc=2,dc=0,dc=192,dc=in-addr,dc=arpa".
Hall I-D Expires: March 2004 [page 9]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
5.2. LDAP Matching
If the server advertises the inetIpv4Network object class and
inetIpv4NetworkMatch matching filter in the inetResourcesControl
server control, FIRS clients MUST use the inetIpv4NetworkMatch
matching filter in LDAP searches for IPv4 network entries.
The inetIpv4NetworkMatch filter provides an identifier and search
string format which collectively inform a queried server that a
specific IPv4 address should be searched for, and that any
matching inetIpv4network object class entries should be returned.
The inetIpv4NetworkMatch filter is defined as follows:
inetIpv4NetworkMatch
(1.3.6.1.4.1.7161.1.5.0.1
NAME 'inetIpv4NetworkMatch'
SYNTAX inetIpv4NetworkSyntax )
Clients MUST ensure that the query input is normalized according
to the rules specified in section 3 before the input is used as
the assertion value in the resulting LDAP query.
A FIRS server MUST compare the assertion value against the
distinguished name of all entries within and beneath the container
of the partition specified in the search base. Any entry in that
hierarchy with an object class of inetIpv4Network and a
distinguished name that is clearly superior to the IPv4 address
provided in the assertion value MUST be returned. Entries which do
not have an object class of inetIpv4Network MUST NOT be returned.
Entries which are not clearly superior to the queried address MUST
NOT be returned.
Note that "superiority" means that the address ranges specified in
the entry names clearly encompass the address range specified in
the assertion value. This can be reverse-computed by repeatedly
shrinking the prefix size of the address in the assertion value,
and using the resulting network/prefix pair as a matching value.
Hall I-D Expires: March 2004 [page 10]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
An example of this matching logic is illustrated below, using the
assertion value of "10.127.0.0/16" and the search base of
"cn=inetResources,dc=in-addr,dc=arpa":
set searchBase "cn=inetResources,dc=in-addr,dc=arpa"
find ( ( objectClass equals inetIpv4Network) and
( ( nameComponent equals "cn=10.127.0.0/16" ) or
( nameComponent equals "cn=10.126.0.0/15") ) or
( nameComponent equals "cn=10.124.0.0/14") ) or
( nameComponent equals "cn=10.120.0.0/13") ) or
( nameComponent equals "cn=10.112.0.0/12") ) or
( nameComponent equals "cn=10.96.0.0/11") ) or
( nameComponent equals "cn=10.64.0.0/10") ) or
( nameComponent equals "cn=10.0.0.0/9") ) or
( nameComponent equals "cn=10.0.0.0/8") )
Note that the entry name of "cn=0.0.0.0/0" encompasses the entire
IPv4 address space. When used in conjunction with referrals, this
entry MAY be used to redirect all inetIpv4NetworkMatch queries to
another partition for subsequent processing.
The matching filters defined in this specification MUST be
supported by FIRS clients and servers. FIRS servers MAY support
additional matching filters, although FIRS clients MUST NOT expect
any additional filters to be available.
If the server does not advertise support for the
inetIpv4NetworkMatch matching filter in the inetResourcesControl
server control, the client MAY choose to emulate this matching
filter through the use of locally-constructed equalityMatch
filters. However, this process can result in incomplete answers in
some cases, so if the server advertises support for the
inetIpv4NetworkMatch matching filter in the inetResourcesControl
control, the client MUST use it.
5.3. Example Query
The following example assumes that the user has specified
"192.0.2.14/32" as the query value:
a. Normalize the input, which is "192.0.2.14/32" in this case.
b. Determine the canonical authoritative partition.
Hall I-D Expires: March 2004 [page 11]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
1. Map the input sequence to the reverse-lookup domain
name, which is "14.2.0.192.in-addr.arpa" in this case.
2. Determine the initial domain name which is appropriate
for the bootstrap model in use. In the default case of
a targeted query, use "in-addr.arpa". In the case of a
bottom-up query, use the label sequence determined in
step 5.3.b.1. In the case of a top-down query, set the
domain name to "arpa".
3. Map the domain name to an authoritative partition,
which would be "dc=in-addr,dc=arpa" if the default
bootstrap model were in use.
c. Determine the search base for the query, which will be
"cn=inetResources,dc=arpa" if the defaults are used.
d. Initiate a DNS lookup for the SRV resource records
associated with "_ldap._tcp.in-addr.arpa." For the purpose
of this example, assume that this lookup succeeds, with the
DNS response message indicating that "firs.iana.org" is the
preferred LDAP server.
e. Submit an LDAPv3 query to the specified server, using
"(&(objectClass=inetIpv4Network)
(1.3.6.1.4.1.7161.1.5.8:=192.0.2.14/32))" as the matching
filter, "cn=inetResources,dc=in-addr,dc=arpa" as the search
base, and the global query defaults defined in [FIRS-CORE].
f. Assume that the queried server returns a continuation
reference referral which points to
"ldap:///cn=inetResources,dc=arin,dc=net". The
distinguished name element of
"cn=inetResources,dc=arin,dc=net" will be used as the new
search base, while "dc=arin,dc=net" will be used as the new
authoritative partition.
g. Initiate a DNS lookup for the SRV resource records
associated with "_ldap._tcp. arin.net." For the purpose of
this example, assume that this lookup succeeds, with the
DNS response message indicating that "firs.arin.net" is the
preferred LDAP server.
h. Submit an LDAPv3 query to the specified server, using
"(&(objectClass=inetIpv4Network)
(1.3.6.1.4.1.7161.1.5.8:=192.0.2.14/32)" as the matching
Hall I-D Expires: March 2004 [page 12]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
filter, "cn=inetResources,dc=arin,dc=net" as the search
base, and the global query defaults defined in [FIRS-CORE].
i. Assume that no other referrals are received. Display the
answer data which has been received and exit the query.
6. Security Considerations
Security considerations are discussed in [FIRS-ARCH].
7. IANA Considerations
This specification uses the "dc=in-addr,dc=arpa" directory
partition by default. It is expected that authoritative LDAP
partitions will be mapped to that zone, and that FIRS-capable LDAP
servers will be established to service this partition, with this
partition containing IPv4-specific entries which will provide
referrals to the appropriate RIR partitions. It is further
expected that IANA will oversee the creation and management of the
in-addr.arpa domain's LDAP SRV resource records, the
"dc=in-addr,dc=arpa" LDAP partition, and the necessary LDAP
servers.
The inetIpv4DelegationStatus attribute uses numeric code values.
It is expected that IANA will manage the assignment of these
values.
Additional IANA considerations are discussed in [FIRS-ARCH].
8. Normative References
[RFC2247] Kille, S., Wahl, M., Grimstad, A., Huber, R.,
and Sataluri, S. "Using Domains in LDAP/X.500
DNs", RFC 2247, January 1998.
[RFC2251] Wahl, M., Howes, T., and Kille, S.
"Lightweight Directory Access Protocol (v3)",
RFC 2251, December 1997.
[RFC2252] Wahl, M., Coulbeck, A., Howes, T., and Kille,
S. "Lightweight Directory Access Protocol
(v3): Attribute Syntax Definitions", RFC 2252,
December 1997.
[RFC2254] Howes, T. "The String Representation of LDAP
Search Filters", RFC 2254, December 1997.
Hall I-D Expires: March 2004 [page 13]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
[FIRS-ARCH] Hall, E. "The Federated Internet Registry
Service: Architecture and Implementation
Guide", draft-ietf-crisp-firs-arch-03, August
2003.
[FIRS-ASN] Hall, E. "Defining and Locating Autonomous
System Numbers in the Federated Internet
Registry Service", draft-ietf-crisp-firs-asn-
03, August 2003.
[FIRS-CONTCT] Hall, E. "Defining and Locating Contact
Persons in the Federated Internet Registry
Service", draft-ietf-crisp-firs-contact-03,
August 2003.
[FIRS-CORE] Hall, E. "The Federated Internet Registry
Service: Core Elements", draft-ietf-crisp-
firs-core-03, August 2003.
[FIRS-DNS] Hall, E. "Defining and Locating DNS Domains in
the Federated Internet Registry Service",
draft-ietf-crisp-firs-dns-03, August 2003.
[FIRS-DNSRR] Hall, E. "Defining and Locating DNS Resource
Records in the Federated Internet Registry
Service", draft-ietf-crisp-firs-dnsrr-02, July
2003.
[FIRS-IPV6] Hall, E. "Defining and Locating IPv6 Address
Blocks in the Federated Internet Registry
Service", draft-ietf-crisp-firs-ipv6-03,
August 2003.
9. Changes from Previous Versions
draft-ietf-crisp-firs-ipv4-03:
* Several clarifications and corrections have been made.
* Clarified the matching behavior, and added sample logic
that demonstrates efficient matching behavior.
* Added the inetIpv4ParentNetworks, inetIpv4SiblingNetworks,
and inetIpv4ChildNetworks attributes.
* Several attributes had their OIDs changed. NOTE THAT THIS
IS AN INTERNET DRAFT, AND THAT THE OIDS ARE SUBJECT TO
ADDITIONAL CHANGES AS THIS DOCUMENT IS EDITED.
Hall I-D Expires: March 2004 [page 14]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
draft-ietf-crisp-firs-ipv4-02:
* Several clarifications and corrections have been made.
* Changed the default bootstrap model to use targeted
queries, with "in-addr.arpa" as the default zone and
"dc=in-addr,dc=arpa" as the default partition.
draft-ietf-crisp-firs-ipv4-01:
* Several clarifications and corrections have been made.
draft-ietf-crisp-firs-ipv4-00:
* Restructured the document set.
* "Attribute references" have been eliminated from the
specification. All referential attributes now provide
actual data instead of URL pointers to data. Clients that
wish to retrieve these values will need to start new
queries using the data values instead of URLs.
* The attribute-specific operational attributes have been
eliminated as unnecessary.
* The inetIpv4Registrar and inetIpv4Registry attributes were
added.
* Several attributes had their OIDs changed. NOTE THAT THIS
IS AN INTERNET DRAFT, AND THAT THE OIDS ARE SUBJECT TO
ADDITIONAL CHANGES AS THIS DOCUMENT IS EDITED.
* Several typographical errors have been fixed.
* Some unnecessary text has been removed.
10. Author's Address
Eric A. Hall
ehall@ehsco.com
11. Acknowledgments
Funding for the RFC editor function is currently provided by the
Internet Society.
Hall I-D Expires: March 2004 [page 15]
Internet Draft draft-ietf-crisp-firs-ipv4-03.txt August 2003
Portions of this document were funded by VeriSign Labs.
The first version of this specification was co-authored by Andrew
Newton of VeriSign Labs, and subsequent versions continue to be
developed with his active participation. Edward Lewis also
contributed significant feedback to this specification in the
later stages of its developments.
12. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared,
copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed
for the purpose of developing Internet standards in which case the
procedures for copyrights defined in the Internet Standards
process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not
be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS 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.
Hall I-D Expires: March 2004 [page 16] | PAFTECH AB 2003-2026 | 2026-04-24 01:33:45 |