draft-ietf-crisp-firs-ipv6-00.txt   draft-ietf-crisp-firs-ipv6-01.txt 
INTERNET-DRAFT Eric A. Hall INTERNET-DRAFT Eric A. Hall
Document: draft-ietf-crisp-firs-ipv6-00.txt May 2003 Document: draft-ietf-crisp-firs-ipv6-01.txt May 2003
Expires: December, 2003 Expires: December, 2003
Category: Experimental Category: Experimental
Defining and Locating IPv6 Address Blocks Defining and Locating IPv6 Address Blocks
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.
skipping to change at line 39 skipping to change at line 39
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
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 IPv6 This document defines LDAP schema and searching rules for IPv6
address blocks, in support of the Internet Resource Query Service address blocks, in support of the Federated Internet Registry
described in [FIRS-ARCH] and [FIRS-CORE]. 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.............................5 4. Object Classes and Attributes.............................5
5. Query Processing Rules....................................7 5. Query Processing Rules....................................7
5.1. Query Pre-Processing...................................8 5.1. Query Pre-Processing...................................8
5.2. Query Bootstrapping....................................8 5.2. Query Bootstrapping....................................8
5.3. LDAP Matching..........................................9 5.3. LDAP Matching..........................................9
5.4. Example Query.........................................10 5.4. Example Query.........................................10
6. Security Considerations..................................11 6. Security Considerations..................................11
7. IANA Considerations......................................11 7. IANA Considerations......................................11
8. Author's Addresses.......................................11 8. Author's Addresses.......................................11
9. Normative References.....................................11 9. Normative References.....................................11
10. Acknowledgments..........................................12 10. Acknowledgments..........................................12
11. Changes from Previous Versions...........................13 11. Changes from Previous Versions...........................12
12. Full Copyright Statement.................................13 12. Full Copyright Statement.................................13
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 IPv6 address blocks in the FIRS service. storing and locating IPv6 address blocks in the FIRS service.
Refer to [FIRS-ARCH] for information on the FIRS architecture and Refer to [FIRS-ARCH] for information on the FIRS architecture and
[FIRS-CORE] for the schema definitions and rules which govern the [FIRS-CORE] for the schema definitions and rules which govern the
FIRS service as a whole. FIRS service as a whole.
Note that reverse-lookup DNS domains for IPv6 address blocks are Note that reverse-lookup DNS domains for IPv6 address blocks are
managed as DNS domain entries in [FIRS-DNS]. These are entirely managed as DNS domain entries in [FIRS-DNS]. These are entirely
different network resources, and should not be confused with IPv6 different network resources, and should not be confused with IPv6
skipping to change at line 79 skipping to change at line 80
Note that reverse-lookup DNS domains for IPv6 address blocks are Note that reverse-lookup DNS domains for IPv6 address blocks are
managed as DNS domain entries in [FIRS-DNS]. These are entirely managed as DNS domain entries in [FIRS-DNS]. These are entirely
different network resources, and should not be confused with IPv6 different network resources, and should not be confused with IPv6
address block entries. address block entries.
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 the complete set of
specifications, which currently include the following: specifications, which currently include the following:
Hall I-D Expires: December 2003 [page 2] Hall I-D Expires: December 2003 [page 2]
draft-ietf-crisp-firs-arch-00, "The Federated Internet draft-ietf-crisp-firs-arch-01, "The Federated Internet
Registry Service: Architecture and Implementation" Registry Service: Architecture and Implementation"
[FIRS-ARCH] [FIRS-ARCH]
draft-ietf-crisp-firs-core-00, "The Federated Internet draft-ietf-crisp-firs-core-01, "The Federated Internet
Registry Service: Core Elements" [FIRS-CORE] Registry Service: Core Elements" [FIRS-CORE]
draft-ietf-crisp-firs-dns-00, "Defining and Locating DNS draft-ietf-crisp-firs-dns-01, "Defining and Locating DNS
Domains in the Federated Internet Registry Service" Domains in the Federated Internet Registry Service"
[FIRS-DNS] [FIRS-DNS]
draft-ietf-crisp-firs-dnsrr-00, "Defining and Locating DNS draft-ietf-crisp-firs-dnsrr-01, "Defining and Locating DNS
Resource Records in the Federated Internet Registry Resource Records in the Federated Internet Registry
Service" [FIRS-DNSRR] Service" [FIRS-DNSRR]
draft-ietf-crisp-firs-contact-00, "Defining and Locating draft-ietf-crisp-firs-contact-01, "Defining and Locating
Contact Persons in the Federated Internet Registry Service" Contact Persons in the Federated Internet Registry Service"
[FIRS-CONTCT] [FIRS-CONTCT]
draft-ietf-crisp-firs-asn-00, "Defining and Locating draft-ietf-crisp-firs-asn-01, "Defining and Locating
Autonomous System Numbers in the Federated Internet Autonomous System Numbers in the Federated Internet
Registry Service" (this document) [FIRS-ASN] Registry Service" (this document) [FIRS-ASN]
draft-ietf-crisp-firs-ipv4-00, "Defining and Locating IPv4 draft-ietf-crisp-firs-ipv4-01, "Defining and Locating IPv4
Address Blocks in the Federated Internet Registry Service" Address Blocks in the Federated Internet Registry Service"
[FIRS-IPV4] [FIRS-IPV4]
draft-ietf-crisp-firs-ipv6-00, "Defining and Locating IPv6 draft-ietf-crisp-firs-ipv6-01, "Defining and Locating IPv6
Address Blocks in the Federated Internet Registry Service" Address Blocks in the Federated Internet Registry Service"
[FIRS-IPV6] [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.
3. Naming Syntax 3. Naming Syntax
The naming syntax for IPv4 address blocks in FIRS MUST follow the The naming syntax for IPv4 address blocks in FIRS MUST follow the
form of "cn=<inetIpv4NetworkSyntax>,cn=inetResources,<partition>", form of "cn=<inetIpv4NetworkSyntax>,cn=inetResources,<partition>",
where <inetIpv6NetworkSyntax > is the IPv6 address block resource, where <inetIpv6NetworkSyntax > is the IPv6 address block resource,
and where <partition> is a sequence of domainComponent relative and 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.
Hall I-D Expires: December 2003 [page 3]
The inetIpv6NetworkSyntax rules use the uncompressed, 32-nibble The inetIpv6NetworkSyntax rules use the uncompressed, 32-nibble
notation, terminated with a subnet "prefix". The network address notation, terminated with a subnet "prefix". The network address
Hall I-D Expires: December 2003 [page 3]
consists of eight sub-components, each of which are separated by a consists of eight sub-components, each of which are separated by a
colon character, and which each consist of four hexadecimal values colon character, and which each consist of four hexadecimal values
that represent one nibble. The entire sequence is followed by a that represent one nibble. The entire sequence is followed by a
"/" character and a three-digit decimal "prefix" value. "/" character and a three-digit decimal "prefix" value.
Entries which use the inetIpv6NetworkSyntax MUST use the starting Entries which use the inetIpv6NetworkSyntax MUST use the starting
address from a range of inclusive addresses, and MUST use CIDR address from a range of inclusive addresses, and MUST use CIDR
prefix notation. In this manner, it is possible to create an prefix notation. In this manner, it is possible to create an
inetIpv6Network entry for a range of addresses of any size inetIpv6Network entry for a range of addresses of any size
(including a single host). (including a single host).
skipping to change at line 176 skipping to change at line 180
inclusive, with the non-affective leading zeroes removed inclusive, with the non-affective leading zeroes removed
The inetIpv6NetworkSyntax syntax is as follows: The inetIpv6NetworkSyntax syntax is as follows:
inetIpv6NetworkSyntax inetIpv6NetworkSyntax
( 1.3.6.1.4.1.7161.1.3.1 NAME 'inetIpv6NetworkSyntax' DESC ( 1.3.6.1.4.1.7161.1.3.1 NAME 'inetIpv6NetworkSyntax' DESC
'An IPv6 address and prefix.' ) 'An IPv6 address and prefix.' )
For example, an IPv6 network with a range of addresses between For example, an IPv6 network with a range of addresses between
"3ffe:ffff::" and "3ffe:ffff:ffff:ffff:ffff:ffff:ffff:ffff" would "3ffe:ffff::" and "3ffe:ffff:ffff:ffff:ffff:ffff:ffff:ffff" would
be written as "cn=3ffe:ffff:0000:0000:0000:0000:0000:0000/32".
Hall I-D Expires: December 2003 [page 4] Hall I-D Expires: December 2003 [page 4]
be written as "cn=3ffe:ffff:0000:0000:0000:0000:0000:0000/32".
Similarly, a host address of "3ffe:ffff::1:2:3:4" would be written Similarly, a host address of "3ffe:ffff::1:2:3:4" would be written
as "cn=3ffe:ffff:0000:0000:0001:0002:0003:0004/128". as "cn=3ffe:ffff:0000:0000:0001:0002:0003:0004/128".
Note that the entry name of Note that the entry name of
"cn=0000:0000:0000:0000:0000:0000:0000:0000/0" encompasses the "cn=0000:0000:0000:0000:0000:0000:0000:0000/0" encompasses the
entire IPv6 address space. entire IPv6 address space.
Note that the use of "/" is illegal as data in URLs, and MUST be Note that the use of "/" is illegal as data in URLs, and MUST be
escaped before it is stored in a URL as data. escaped before it is stored in a URL as data.
skipping to change at line 492 skipping to change at line 506
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.
[RFC3152] Bush, R. "Delegation of IP6.ARPA", RFC 3152, [RFC3152] Bush, R. "Delegation of IP6.ARPA", RFC 3152,
August 2001. August 2001.
Hall I-D Expires: December 2003 [page 11]
[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-00, May Guide", draft-ietf-crisp-firs-arch-01, May
2003. 2003.
Hall I-D Expires: December 2003 [page 11]
[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-
00, May 2003. 01, May 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-00, Service", draft-ietf-crisp-firs-contact-01,
May 2003. May 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-00, May 2003. firs-core-01, May 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-00, May 2003. draft-ietf-crisp-firs-dns-01, May 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-00, May Service", draft-ietf-crisp-firs-dnsrr-01, May
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-00, May Service", draft-ietf-crisp-firs-ipv4-01, May
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-00, May Service", draft-ietf-crisp-firs-ipv6-01, May
2003. 2003.
10. Acknowledgments 10. Acknowledgments
Funding for the RFC editor function is currently provided by the Funding for the RFC editor function is currently provided by the
Internet Society. Internet Society.
Portions of this document were funded by Verisign Labs. Portions of this document were funded by Verisign Labs.
The first version of this specification was co-authored by Andrew The first version of this specification was co-authored by Andrew
Newton of Verisign Labs, and subsequent versions continue to be Newton of Verisign Labs, and subsequent versions continue to be
developed with his active participation. developed with his active participation.
Hall I-D Expires: December 2003 [page 12]
11. Changes from Previous Versions 11. Changes from Previous Versions
draft-ietf-crisp-fir-ipv6-00:
draft-ietf-crisp-firs-ipv6-01:
* Several clarifications and corrections have been made.
Hall I-D Expires: December 2003 [page 12]
draft-ietf-crisp-firs-ipv6-00:
* Restructured the document set. * Restructured the document set.
* "Attribute references" have been eliminated from the * "Attribute references" have been eliminated from the
specification. All referential attributes now provide specification. All referential attributes now provide
actual data instead of URL pointers to data. Clients that actual data instead of URL pointers to data. Clients that
wish to retrieve these values will need to start new wish to retrieve these values will need to start new
queries using the data values instead of URLs. queries using the data values instead of URLs.
* The attribute-specific operational attributes have been * The attribute-specific operational attributes have been
 End of changes. 

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