draft-ietf-crisp-firs-asn-01.txt   draft-ietf-crisp-firs-asn-02.txt 
INTERNET-DRAFT Eric A. Hall INTERNET-DRAFT Eric A. Hall
Document: draft-ietf-crisp-firs-asn-01.txt May 2003 Document: draft-ietf-crisp-firs-asn-02.txt July 2003
Expires: December, 2003 Expires: February, 2004
Category: Standards-Track Category: Experimental
Defining and Locating Autonomous System Numbers Defining and Locating Autonomous System Numbers
in the Federated Internet Registry Service in the Federated Internet Registry Service
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at line 44 skipping to change at line 44
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document defines LDAP schema and searching rules for This document defines LDAP schema and searching rules for
autonomous system numbers, in support of the Federated Internet autonomous system numbers, in support of the Federated Internet
Registry Service (FIRS) described in [FIRS-ARCH] and [FIRS-CORE]. Registry Service (FIRS) described in [FIRS-ARCH] and [FIRS-CORE].
Table of Contents Table of Contents
1. Introduction..............................................2 1. Introduction...............................................2
2. Prerequisites and Terminology.............................2 2. Prerequisites and Terminology..............................2
3. Naming Syntax.............................................3 3. Naming Syntax..............................................3
4. Object Classes and Attributes.............................4 4. Object Classes and Attributes..............................3
5. Query Processing Rules....................................7 5. Query Processing Rules.....................................6
5.1. Query Pre-Processing...................................7 5.1. Query Pre-Processing....................................6
5.2. Query Bootstrapping....................................7 5.2. Query Bootstrapping.....................................7
5.3. LDAP Matching..........................................7 5.3. LDAP Matching...........................................7
5.4. Example Query..........................................8 5.4. Example Query...........................................8
6. Security Considerations...................................9 6. Security Considerations....................................9
7. IANA Considerations.......................................9 7. IANA Considerations........................................9
8. Author's Addresses........................................9 8. Normative References.......................................9
9. Normative References......................................9 9. Changes from Previous Versions............................10
10. Acknowledgments..........................................11 10. Author's Address..........................................11
11. Changes from Previous Versions...........................11 11. Acknowledgments...........................................11
12. Full Copyright Statement.................................11 12. Full Copyright Statement..................................12
1. Introduction 1. Introduction
This specification defines the naming syntax, object classes, This specification defines the naming syntax, object classes,
attributes, matching filters, and query processing rules for attributes, matching filters, and query processing rules for
storing and locating Autonomous System Numbers (ASNs) in the FIRS storing and locating Autonomous System Numbers (ASNs) in the FIRS
service. Refer to [FIRS-ARCH] for information on the FIRS service. Refer to [FIRS-ARCH] for information on the FIRS
architecture and [FIRS-CORE] for the schema definitions and rules architecture and [FIRS-CORE] for the schema definitions and rules
which govern the FIRS service as a whole. which govern the FIRS service as a whole.
The definitions in this specification are intended to be used with The definitions in this specification are intended to be used with
FIRS. Their usage outside of FIRS is not prohibited, but any such FIRS. Their usage outside of FIRS is not prohibited, but any such
usage is beyond this specification's scope of authority. usage is beyond this specification's scope of authority.
2. Prerequisites and Terminology 2. Prerequisites and Terminology
The complete set of specifications in the FIRS collection The complete set of specifications in the FIRS collection
cumulative define a structured and distributed information service cumulative define a structured and distributed information service
using LDAPv3 for the data-formatting and transport functions. This using LDAPv3 for the data-formatting and transport functions. This
specification should be read in the context of the complete set of specification should be read in the context of that set, which
specifications, which currently include the following: currently includes [FIRS-ARCH], [FIRS-CORE], [FIRS-DNS],
[FIRS-DNSRR], [FIRS-CONTCT], [FIRS-IPV4] and [FIRS-IPV6].
draft-ietf-crisp-firs-arch-01, "The Federated Internet
Registry Service: Architecture and Implementation"
[FIRS-ARCH]
Hall I-D Expires: December 2003 [page 2]
draft-ietf-crisp-firs-core-01, "The Federated Internet
Registry Service: Core Elements" [FIRS-CORE]
draft-ietf-crisp-firs-dns-01, "Defining and Locating DNS
Domains in the Federated Internet Registry Service"
[FIRS-DNS]
draft-ietf-crisp-firs-dnsrr-01, "Defining and Locating DNS
Resource Records in the Federated Internet Registry
Service" [FIRS-DNSRR]
draft-ietf-crisp-firs-contact-01, "Defining and Locating
Contact Persons in the Federated Internet Registry Service"
[FIRS-CONTCT]
draft-ietf-crisp-firs-asn-01, "Defining and Locating
Autonomous System Numbers in the Federated Internet
Registry Service" (this document) [FIRS-ASN]
draft-ietf-crisp-firs-ipv4-01, "Defining and Locating IPv4
Address Blocks in the Federated Internet Registry Service"
[FIRS-IPV4]
draft-ietf-crisp-firs-ipv6-01, "Defining and Locating IPv6
Address Blocks in the Federated Internet Registry Service"
[FIRS-IPV6]
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in RFC 2119. in this document are to be interpreted as described in RFC 2119.
Hall I-D Expires: February 2004 [page 2]
3. Naming Syntax 3. Naming Syntax
The naming syntax for ASN entries in FIRS MUST follow the form of The naming syntax for ASN entries in FIRS MUST follow the form of
"cn=<inetAsNumberSyntax>,cn=inetResources,<partition>", where "cn=<inetAsNumberSyntax>,cn=inetResources,<partition>", where
<inetAsNumberSyntax> is the Autonomous System Number resource, and <inetAsNumberSyntax> is the Autonomous System Number resource, and
where <partition> is a sequence of domainComponent relative where <partition> is a sequence of domainComponent relative
distinguished names which identifies the scope of authority for distinguished names which identifies the scope of authority for
the selected directory partition. the selected directory partition.
Entries which use the inetAsNumberSyntax rules use the decimal Entries which use the inetAsNumberSyntax rules use the decimal
equivalent of a 16-bit autonomous system number, with the non- equivalent of a 16-bit autonomous system number, with the non-
affective leading zeroes removed. affective leading zeroes removed.
Hall I-D Expires: December 2003 [page 3]
An augmented BNF for this syntax is as follows: An augmented BNF for this syntax is as follows:
inetAsNumberSyntax = decimal value between "0" and "65535" inetAsNumberSyntax = decimal value between "0" and "65535"
inclusive, with the non-affective leading zeroes removed inclusive, with the non-affective leading zeroes removed
The schema definition for inetAsNumberSyntax is as follows: The schema definition for inetAsNumberSyntax is as follows:
inetAsNumberSyntax inetAsNumberSyntax
( 1.3.6.1.4.1.7161.1.4.1 NAME 'inetAsNumberSyntax' DESC 'An ( 1.3.6.1.4.1.7161.1.7.0 NAME 'inetAsNumberSyntax' DESC 'An
autonomous system number.' ) autonomous system number.' )
For example, an entry for ASN "1" in the "dc=arin,dc=net" For example, an entry for ASN "1" in the "dc=arin,dc=net"
partition would be "cn=1,cn=inetResources,dc=arin,dc=net", while partition would be "cn=1,cn=inetResources,dc=arin,dc=net", while
an entry for AS number "65535" in the same partition would be an entry for AS number "65535" in the same partition would be
"cn=65535,cn=inetResources,dc=arin,dc=net". "cn=65535,cn=inetResources,dc=arin,dc=net".
4. Object Classes and Attributes 4. Object Classes and Attributes
ASN-specific entries in FIRS MUST use the inetAsNumber object ASN-specific entries in FIRS MUST use the inetAsNumber object
skipping to change at line 164 skipping to change at line 133
source, the entry MUST also be defined with the referral object source, the entry MUST also be defined with the referral object
class, in addition to the above requirements. class, in addition to the above requirements.
The inetAsNumber object class is a structural object class which The inetAsNumber object class is a structural object class which
is subordinate to the inetResources object class. The inetAsNumber is subordinate to the inetResources object class. The inetAsNumber
object class has no mandatory attributes, although it does have object class has no mandatory attributes, although it does have
several optional attributes. The inetAsNumber object class also several optional attributes. The inetAsNumber object class also
inherits the attributes defined in the inetResources object class, inherits the attributes defined in the inetResources object class,
including the "cn" naming attribute. including the "cn" naming attribute.
Hall I-D Expires: February 2004 [page 3]
The schema definition for the inetAsNumber object class is as The schema definition for the inetAsNumber object class is as
follows: follows:
inetAsNumber inetAsNumber
( 1.3.6.1.4.1.7161.1.4.0 NAME 'inetAsNumber' DESC 'Autonomous ( 1.3.6.1.4.1.7161.1.7.1
system attributes.' SUP inetResources STRUCTURAL MAY ( NAME 'inetAsNumber'
inetAsnDelegationStatus $ inetAsnDelegationDate $ DESC 'Autonomous system attributes.'
SUP inetResources
STRUCTURAL
MAY ( inetAsnDelegationStatus $ inetAsnDelegationDate $
inetAsnRegistrar $ inetAsnRegistry $ inetAsnContacts $ inetAsnRegistrar $ inetAsnRegistry $ inetAsnContacts $
inetAsnRoutingContacts ) ) inetAsnRoutingContacts ) )
Hall I-D Expires: December 2003 [page 4]
The attributes from the inetAsNumber object class are described The attributes from the inetAsNumber object class are described
below: below:
inetAsnContacts inetAsnContacts
( 1.3.6.1.4.1.7161.1.4.2 NAME 'inetAsnContacts' DESC ( 1.3.6.1.4.1.7161.1.7.2
'Contacts for general administrative issues concerning NAME 'inetAsnContacts'
this ASN.' EQUALITY caseIgnoreMatch SYNTAX DESC 'Contacts for general administrative issues
inetContactSyntax ) concerning this ASN.'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.7161.1.7.1 )
inetAsnDelegationDate inetAsnDelegationDate
( 1.3.6.1.4.1.7161.1.4.3 NAME 'inetAsnDelegationDate' DESC ( 1.3.6.1.4.1.7161.1.7.3
'Date this ASN was delegated.' EQUALITY NAME 'inetAsnDelegationDate'
generalizedTimeMatch ORDERING generalizedTimeOrderingMatch DESC 'Date this ASN was delegated.'
SYNTAX generalizedTime SINGLE-VALUE ) EQUALITY generalizedTimeMatch
ORDERING generalizedTimeOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.24
SINGLE-VALUE )
inetAsnDelegationStatus inetAsnDelegationStatus
( 1.3.6.1.4.1.7161.1.4.4 NAME 'inetAsnDelegationStatus' DESC ( 1.3.6.1.4.1.7161.1.7.4
'Delegation status for this AS number.' EQUALITY NAME 'inetAsnDelegationStatus'
numericStringMatch SYNTAX numericString{2} SINGLE-VALUE ) DESC 'Delegation status for this AS number.'
EQUALITY numericStringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{2}
SINGLE-VALUE )
Hall I-D Expires: February 2004 [page 4]
NOTE: In an effort to facilitate internationalization and NOTE: In an effort to facilitate internationalization and
programmatic processing, the current status of a delegation programmatic processing, the current status of a delegation
is identified by a 16-bit integer. The values and status is identified by a 16-bit integer. The values and status
mapping is as follows: mapping is as follows:
0 Reserved delegation (permanently inactive) 0 Reserved delegation (permanently inactive)
1 Assigned and active (normal state) 1 Assigned and active (normal state)
2 Assigned but not yet active (new delegation) 2 Assigned but not yet active (new delegation)
3 Assigned but on hold (disputed) 3 Assigned but on hold (disputed)
4 Assignment revoked (database purge pending) 4 Assignment revoked (database purge pending)
Additional values are reserved for future use, and are to Additional values are reserved for future use, and are to
be administered by IANA. be administered by IANA.
Note that there is no status code for "unassigned"; Note that there is no status code for "unassigned";
unassigned entries SHOULD NOT exist, and SHOULD NOT be unassigned entries SHOULD NOT exist, and SHOULD NOT be
returned as answers. returned as answers.
inetAsnRegistrar inetAsnRegistrar
( 1.3.6.1.4.1.7161.1.4.5 NAME 'inetAsnRegistrar' DESC ( 1.3.6.1.4.1.7161.1.7.5
'Registrar who delegated this ASN.' EQUALITY NAME 'inetAsnRegistrar'
caseIgnoreMatch SYNTAX directoryString ) DESC 'Registrar who delegated this ASN.'
EQUALITY caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
NOTE: The inetAsnRegistrar attribute uses a URL to indicate NOTE: The inetAsnRegistrar attribute uses a URL to indicate
the registrar who delegated the ASN. The attribute the registrar who delegated the ASN. The attribute
Hall I-D Expires: December 2003 [page 5]
structure is identical to the labeledURI attribute, as structure is identical to the labeledURI attribute, as
defined in [RFC2798], including the URL and textual defined in [RFC2798], including the URL and textual
comments. The data can refer to any valid URL. comments. The data can refer to any valid URL.
inetAsnRegistry inetAsnRegistry
( 1.3.6.1.4.1.7161.1.4.6 NAME 'inetAsnRegistry' DESC ( 1.3.6.1.4.1.7161.1.7.6
'Registry where this ASN is managed.' EQUALITY NAME 'inetAsnRegistry'
caseIgnoreMatch SYNTAX directoryString ) DESC 'Registry where this ASN is managed.'
EQUALITY caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
NOTE: The inetAsnRegistry attribute uses a URL to indicate NOTE: The inetAsnRegistry attribute uses a URL to indicate
the registry who is ultimately responsible for the ASN. The the registry who is ultimately responsible for the ASN. The
attribute structure is identical to the labeledURI attribute structure is identical to the labeledURI
attribute, as defined in [RFC2798], including the URL and attribute, as defined in [RFC2798], including the URL and
textual comments. The data can refer to any valid URL. textual comments. The data can refer to any valid URL.
Hall I-D Expires: February 2004 [page 5]
inetAsnRoutingContacts inetAsnRoutingContacts
( 1.3.6.1.4.1.7161.1.4.7 NAME 'inetAsnRoutingContacts' DESC ( 1.3.6.1.4.1.7161.1.7.7
'Contacts for routing-related problems with this ASN.' NAME 'inetAsnRoutingContacts'
EQUALITY caseIgnoreMatch SYNTAX inetContactSyntax ) DESC 'Contacts for routing-related problems with this
ASN.'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.7161.1.7.1 )
An example of an inetAsNumber entry is shown in Figure 1 below. An example of an inetAsNumber entry is shown in Figure 1 below.
The example includes attributes from the inetAsNumber, The example includes attributes from the inetAsNumber,
inetResources, and inetAssociatedResources object classes. inetResources, and inetAssociatedResources object classes.
cn=65535,cn=inetResources,dc=arin,dc=net cn=65535,cn=inetResources,dc=arin,dc=net
[top object class] [top object class]
[inetResources object class] [inetResources object class]
[inetAsNumber object class] [inetAsNumber object class]
[inetAssociatedResources object class] [inetAssociatedResources object class]
skipping to change at line 266 skipping to change at line 253
| value: "hostmaster@example.net" | value: "hostmaster@example.net"
| |
+-attribute: inetAssociatedIpv4Networks +-attribute: inetAssociatedIpv4Networks
| value: "192.0.2.0/24" | value: "192.0.2.0/24"
| |
+-attribute: inetAsnRegistrar +-attribute: inetAsnRegistrar
value: "http://www.arin.net/ (ARIN)" value: "http://www.arin.net/ (ARIN)"
Figure 1: The entry for ASN 65535 in the dc=arin,dc=net partition. Figure 1: The entry for ASN 65535 in the dc=arin,dc=net partition.
Hall I-D Expires: December 2003 [page 6]
5. Query Processing Rules 5. Query Processing Rules
Queries for ASNs have several special requirements, as discussed Queries for ASNs have several special requirements, as discussed
in the following sections. in the following sections.
Refer to [FIRS-CORE] for general information about FIRS queries. Refer to [FIRS-CORE] for general information about FIRS queries.
5.1. Query Pre-Processing 5.1. Query Pre-Processing
Clients MUST ensure that the query input is normalized according Clients MUST ensure that the query input is normalized according
to the rules specified in section 3 before the input is used as to the rules specified in section 3 before the input is used as
the assertion value to the resulting LDAP query. the assertion value to the resulting LDAP query.
Hall I-D Expires: February 2004 [page 6]
There are no pre-existing mechanisms for mapping ASNs to domain There are no pre-existing mechanisms for mapping ASNs to domain
names. As such, there are no pre-existing mechanisms for mapping names. As such, there are no pre-existing mechanisms for mapping
ASNs to authoritative LDAP partitions. In order to facilitate ASNs to authoritative LDAP partitions. In order to facilitate
interoperability, FIRS queries for ASN resources MUST use interoperability, FIRS queries for ASN resources MUST use
"dc=arpa" as the authoritative partition, and MUST use "dc=asn,dc=arpa" as the authoritative partition, and MUST use
"cn=inetResources,dc=arpa" for the search base. It is expected "cn=inetResources,dc=asn,dc=arpa" for the search base. It is
that FIRS-compliant LDAP servers will be established to serve this expected that FIRS-compliant LDAP servers will be established to
directory partition, with these servers providing entry-specific serve this directory partition, with these servers providing
referrals to registrar-specific servers. entry-specific referrals to registrar-specific servers.
5.2. Query Bootstrapping 5.2. Query Bootstrapping
FIRS clients MUST use the top-down bootstrap model by default for FIRS clients MUST use the targeted bootstrap model by default for
ASN queries. ASN queries, using the "asn.arpa" zone as the seed domain for the
initial query.
FIRS clients MAY use the targeted bootstrap model for queries if
necessary or desirable.
Due to the lack of any public DNS delegation mapping service, FIRS clients MAY use the top-down bootstrap model for queries if
there is no practical reason for FIRS clients to use the bottom-up necessary or desirable. Due to the lack of any public DNS
model with ASN queries. delegation mapping service, there is no practical reason for FIRS
clients to use the bottom-up model with ASN queries.
5.3. LDAP Matching 5.3. LDAP Matching
FIRS clients MUST specify equalityMatch matching filters in LDAP FIRS clients MUST specify equalityMatch matching filters in LDAP
searches for ASN entries. searches for ASN entries.
In order to ensure that all of the relevant entries are found In order to ensure that all of the relevant entries are found
(including any referrals), the search filters for these resources (including any referrals), the search filters for these resources
MUST specify the inetAsNumber object class and the naming element MUST specify the inetAsNumber object class and the cn attribute.
of the resource as a distinguished name attribute. For example, For example, "(&(objectclass=inetAsNumber)(cn=65535))" with a
"(&(objectclass=inetAsNumber)(cn:dn:65535))" with a search base of search base of "cn=inetResources,dc=arin,dc=net" would find all of
the inetAsNumber object class entries of "cn=65535" in the
Hall I-D Expires: December 2003 [page 7] "dc=arin,dc=net" partition.
"cn=inetResources,dc=arin,dc=net" would find all of the
inetAsNumber object class entries with a relative distinguished
name of "cn=65535" in the "dc=arin,dc=net" partition.
The matching filters defined in this specification MUST be The matching filters defined in this specification MUST be
supported by FIRS clients and servers. FIRS servers MAY support supported by FIRS clients and servers. FIRS servers MAY support
additional sub-string filters, soundex filters, or any other additional sub-string filters, soundex filters, or any other
filters they wish (these may be required to support generic LDAP filters they wish (these may be required to support generic LDAP
clients), although FIRS clients MUST NOT expect any additional clients), although FIRS clients MUST NOT expect any additional
filters to be available. filters to be available.
Hall I-D Expires: February 2004 [page 7]
5.4. Example Query 5.4. Example Query
The following example assumes that the user has specified "65535" The following example assumes that the user has specified "65535"
as the query value: as the query value:
a. Normalize the input, which is "65535" in this case. a. Normalize the input, which is "65535" in this case.
b. Determine the authoritative partition, which is always b. Determine the authoritative partition, which is always "
"dc=arpa" in the case of ASNs. dc=asn,dc=arpa" in the case of ASNs.
c. Determine the search base for the query, which is always c. Determine the search base for the query, which is always
"cn=inetResources,dc=arpa" in the case of ASNs. "cn=inetResources,dc=asn,dc=arpa" in the case of ASNs.
d. Initiate a DNS lookup for the SRV resource records d. Initiate a DNS lookup for the SRV resource records
associated with "_ldap._tcp.arpa." For the purpose of this associated with "_ldap._tcp.asn.arpa." For the purpose of
example, assume that this lookup succeeds, with the DNS this example, assume that this lookup succeeds, with the
response message indicating that "firs.iana.org" is the DNS response message indicating that "firs.iana.org" is the
preferred LDAP server. preferred LDAP server.
e. Submit an LDAPv3 query to the specified server, using e. Submit an LDAPv3 query to the specified server, using
"(&(objectclass=inetAsNumber)(cn:dn:65535))" as the "(&(objectclass=inetAsNumber)(cn:dn:65535))" as the
matching filter, "cn=inetResources,dc=arpa" as the search matching filter, "cn=inetResources,dc=asn,dc=arpa" as the
base, and the global query defaults defined in [FIRS-CORE]. search base, and the global query defaults defined in
[FIRS-CORE].
f. Assume that the queried server returns a continuation f. Assume that the queried server returns a continuation
reference referral which points to reference referral which points to
"ldap:///cn=inetResources,dc=arin,dc=net". The "ldap:///cn=inetResources,dc=arin,dc=net". The
distinguished name element of distinguished name element of
"cn=inetResources,dc=arin,dc=net" will be used as the new "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 search base, while "dc=arin,dc=net" will be used as the new
authoritative partition. authoritative partition.
g. Initiate a DNS lookup for the SRV resource records g. Initiate a DNS lookup for the SRV resource records
associated with "_ldap._tcp.arin.net." For the purpose of associated with "_ldap._tcp.arin.net." For the purpose of
this example, assume that this lookup succeeds, with the this example, assume that this lookup succeeds, with the
Hall I-D Expires: December 2003 [page 8]
DNS response message indicating that "firs.arin.net" is the DNS response message indicating that "firs.arin.net" is the
preferred LDAP server. preferred LDAP server.
h. Submit an LDAPv3 query to the specified server, using h. Submit an LDAPv3 query to the specified server, using
"(&(objectclass=inetAsNumber)(cn:dn:65535))" as the "(&(objectclass=inetAsNumber)(cn:dn:65535))" as the
matching filter, "cn=inetResources,dc=arin,dc=net" as the matching filter, "cn=inetResources,dc=arin,dc=net" as the
search base, and the global query defaults defined in search base, and the global query defaults defined in
[FIRS-CORE]. [FIRS-CORE].
Hall I-D Expires: February 2004 [page 8]
i. Assume that no other referrals are received. Display the i. Assume that no other referrals are received. Display the
answer data which has been received and exit the query. answer data which has been received and exit the query.
6. Security Considerations 6. Security Considerations
Security considerations are discussed in [FIRS-ARCH]. Security considerations are discussed in [FIRS-ARCH].
7. IANA Considerations 7. IANA Considerations
ASNs are not currently represented in the global DNS, and there ASNs are not currently represented in the global DNS, and there
are no standardized mechanisms for mapping ASNs to authoritative are no simple mechanisms for mapping ASNs to authoritative
partitions using the public DNS. This specification uses the partitions using the public DNS. This specification uses the
"arpa" zone for this mapping function with the expectation that "asn.arpa" zone for this mapping function, with the expectation
FIRS-capable LDAP servers will be established, and that that this zone will be created by IANA. It is also expected that
authoritative partitions will be mapped to that zone, with this authoritative LDAP partitions will be mapped to that zone, and
partition containing ASN-specific entries which will provide that FIRS-capable LDAP servers will be established to service this
referrals to the appropriate registrar's partitions. It is further partition, with this partition containing ASN-specific entries
expected that IANA will oversee the creation and management of the which will provide referrals to the appropriate RIR partitions. It
ARPA domain's LDAP SRV resource records, the "dc=arpa" LDAP is further expected that IANA will oversee the creation and
partition, and the necessary LDAP servers. management of the asn.arpa domain's LDAP SRV resource records, the
"dc=asn,dc=arpa" LDAP partition, and the necessary LDAP servers.
The inetAsnDelegationStatus attribute uses numeric code values. It The inetAsnDelegationStatus attribute uses numeric code values. It
is expected that IANA will manage the assignment of these values. is expected that IANA will manage the assignment of these values.
Additional IANA considerations are discussed in [FIRS-ARCH]. Additional IANA considerations are discussed in [FIRS-ARCH].
8. Author's Addresses 8. Normative References
Eric A. Hall
ehall@ehsco.com
9. Normative References
[RFC2247] Kille, S., Wahl, M., Grimstad, A., Huber, R., [RFC2247] Kille, S., Wahl, M., Grimstad, A., Huber, R.,
and Sataluri, S. "Using Domains in LDAP/X.500 and Sataluri, S. "Using Domains in LDAP/X.500
DNs", RFC 2247, January 1998. DNs", RFC 2247, January 1998.
Hall I-D Expires: December 2003 [page 9]
[RFC2251] Wahl, M., Howes, T., and Kille, S. [RFC2251] Wahl, M., Howes, T., and Kille, S.
"Lightweight Directory Access Protocol (v3)", "Lightweight Directory Access Protocol (v3)",
RFC 2251, December 1997. RFC 2251, December 1997.
[RFC2252] Wahl, M., Coulbeck, A., Howes, T., and Kille, [RFC2252] Wahl, M., Coulbeck, A., Howes, T., and Kille,
S. "Lightweight Directory Access Protocol S. "Lightweight Directory Access Protocol
(v3): Attribute Syntax Definitions", RFC 2252, (v3): Attribute Syntax Definitions", RFC 2252,
December 1997. December 1997.
[RFC2254] Howes, T. "The String Representation of LDAP [RFC2254] Howes, T. "The String Representation of LDAP
Search Filters", RFC 2254, December 1997. Search Filters", RFC 2254, December 1997.
Hall I-D Expires: February 2004 [page 9]
[FIRS-ARCH] Hall, E. "The Federated Internet Registry [FIRS-ARCH] Hall, E. "The Federated Internet Registry
Service: Architecture and Implementation Service: Architecture and Implementation
Guide", draft-ietf-crisp-firs-arch-01, May Guide", draft-ietf-crisp-firs-arch-02, July
2003. 2003.
[FIRS-ASN] Hall, E. "Defining and Locating Autonomous [FIRS-ASN] Hall, E. "Defining and Locating Autonomous
System Numbers in the Federated Internet System Numbers in the Federated Internet
Registry Service", draft-ietf-crisp-firs-asn- Registry Service", draft-ietf-crisp-firs-asn-
01, May 2003. 02, July 2003.
[FIRS-CONTCT] Hall, E. "Defining and Locating Contact [FIRS-CONTCT] Hall, E. "Defining and Locating Contact
Persons in the Federated Internet Registry Persons in the Federated Internet Registry
Service", draft-ietf-crisp-firs-contact-01, Service", draft-ietf-crisp-firs-contact-02,
May 2003. July 2003.
[FIRS-CORE] Hall, E. "The Federated Internet Registry [FIRS-CORE] Hall, E. "The Federated Internet Registry
Service: Core Elements", draft-ietf-crisp- Service: Core Elements", draft-ietf-crisp-
firs-core-01, May 2003. firs-core-02, July 2003.
[FIRS-DNS] Hall, E. "Defining and Locating DNS Domains in [FIRS-DNS] Hall, E. "Defining and Locating DNS Domains in
the Federated Internet Registry Service", the Federated Internet Registry Service",
draft-ietf-crisp-firs-dns-01, May 2003. draft-ietf-crisp-firs-dns-02, July 2003.
[FIRS-DNSRR] Hall, E. "Defining and Locating DNS Resource [FIRS-DNSRR] Hall, E. "Defining and Locating DNS Resource
Records in the Federated Internet Registry Records in the Federated Internet Registry
Service", draft-ietf-crisp-firs-dnsrr-01, May Service", draft-ietf-crisp-firs-dnsrr-02, July
2003. 2003.
[FIRS-IPV4] Hall, E. "Defining and Locating IPv4 Address [FIRS-IPV4] Hall, E. "Defining and Locating IPv4 Address
Blocks in the Federated Internet Registry Blocks in the Federated Internet Registry
Service", draft-ietf-crisp-firs-ipv4-01, May Service", draft-ietf-crisp-firs-ipv4-02, July
2003. 2003.
[FIRS-IPV6] Hall, E. "Defining and Locating IPv6 Address [FIRS-IPV6] Hall, E. "Defining and Locating IPv6 Address
Blocks in the Federated Internet Registry Blocks in the Federated Internet Registry
Service", draft-ietf-crisp-firs-ipv6-01, May Service", draft-ietf-crisp-firs-ipv6-02, July
2003. 2003.
Hall I-D Expires: December 2003 [page 10] 9. Changes from Previous Versions
10. Acknowledgments
Funding for the RFC editor function is currently provided by the draft-ietf-crisp-firs-asn-02:
Internet Society.
Portions of this document were funded by Verisign Labs. * Several clarifications and corrections have been made.
The first version of this specification was co-authored by Andrew * Changed the default bootstrap model to use targeted
Newton of Verisign Labs, and subsequent versions continue to be queries, with "asn.arpa" as the default zone and
developed with his active participation. "dc=asn,dc=arpa" as the default partition.
11. Changes from Previous Versions Hall I-D Expires: February 2004 [page 10]
* 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.
draft-ietf-crisp-firs-asn-01: draft-ietf-crisp-firs-asn-01:
* Several clarifications and corrections have been made. * Several clarifications and corrections have been made.
draft-ietf-crisp-firs-asn-00: draft-ietf-crisp-firs-asn-00:
* Restructured the document set. * Restructured the document set.
* "Attribute references" have been eliminated from the * "Attribute references" have been eliminated from the
skipping to change at line 501 skipping to change at line 482
added. added.
* Several attributes had their OIDs changed. NOTE THAT THIS * Several attributes had their OIDs changed. NOTE THAT THIS
IS AN INTERNET DRAFT, AND THAT THE OIDS ARE SUBJECT TO IS AN INTERNET DRAFT, AND THAT THE OIDS ARE SUBJECT TO
ADDITIONAL CHANGES AS THIS DOCUMENT IS EDITED. ADDITIONAL CHANGES AS THIS DOCUMENT IS EDITED.
* Several typographical errors have been fixed. * Several typographical errors have been fixed.
* Some unnecessary text has been removed. * 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.
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
Hall I-D Expires: February 2004 [page 11]
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 12. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Hall I-D Expires: December 2003 [page 11]
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared, explain it or assist in its implementation may be prepared,
copied, published and distributed, in whole or in part, without copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed Internet Society or other Internet organizations, except as needed
for the purpose of developing Internet standards in which case the for the purpose of developing Internet standards in which case the
skipping to change at line 530 skipping to change at line 530
The limited permissions granted above are perpetual and will not The limited permissions granted above are perpetual and will not
be revoked by the Internet Society or its successors or assigns. be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on This document and the information contained herein is provided on
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Hall I-D Expires: December 2003 [page 12] Hall I-D Expires: February 2004 [page 12]
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/