draft-ietf-crisp-firs-asn-00.txt   draft-ietf-crisp-firs-asn-01.txt 
INTERNET-DRAFT Eric A. Hall INTERNET-DRAFT Eric A. Hall
Document: draft-ietf-crisp-firs-asn-00.txt May 2003 Document: draft-ietf-crisp-firs-asn-01.txt May 2003
Expires: December, 2003 Expires: December, 2003
Category: Standards-Track Category: Standards-Track
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.
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 This document defines LDAP schema and searching rules for
autonomous system numbers, in support of the Internet Resource autonomous system numbers, in support of the Federated Internet
Query Service 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.............................4
5. Query Processing Rules....................................6 5. Query Processing Rules....................................7
5.1. Query Pre-Processing...................................7 5.1. Query Pre-Processing...................................7
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. Author's Addresses........................................9
9. Normative References......................................9 9. Normative References......................................9
10. Acknowledgments..........................................11 10. Acknowledgments..........................................11
11. Changes from Previous Versions...........................11 11. Changes from Previous Versions...........................11
skipping to change at line 74 skipping to change at line 75
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 the complete set of
specifications, which currently include the following: specifications, which currently include the following:
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]
Hall I-D Expires: December 2003 [page 2] Hall I-D Expires: December 2003 [page 2]
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 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.
skipping to change at line 128 skipping to change at line 131
"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:
Hall I-D Expires: December 2003 [page 3]
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.4.1 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"
skipping to change at line 170 skipping to change at line 174
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.4.0 NAME 'inetAsNumber' DESC 'Autonomous
system attributes.' SUP inetResources STRUCTURAL MAY ( system attributes.' SUP inetResources STRUCTURAL MAY (
inetAsnDelegationStatus $ inetAsnDelegationDate $ 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:
Hall I-D Expires: December 2003 [page 4]
inetAsnContacts inetAsnContacts
( 1.3.6.1.4.1.7161.1.4.2 NAME 'inetAsnContacts' DESC ( 1.3.6.1.4.1.7161.1.4.2 NAME 'inetAsnContacts' DESC
'Contacts for general administrative issues concerning 'Contacts for general administrative issues concerning
this ASN.' EQUALITY caseIgnoreMatch SYNTAX this ASN.' EQUALITY caseIgnoreMatch SYNTAX
inetContactSyntax ) inetContactSyntax )
inetAsnDelegationDate inetAsnDelegationDate
( 1.3.6.1.4.1.7161.1.4.3 NAME 'inetAsnDelegationDate' DESC ( 1.3.6.1.4.1.7161.1.4.3 NAME 'inetAsnDelegationDate' DESC
'Date this ASN was delegated.' EQUALITY 'Date this ASN was delegated.' EQUALITY
generalizedTimeMatch ORDERING generalizedTimeOrderingMatch generalizedTimeMatch ORDERING generalizedTimeOrderingMatch
skipping to change at line 216 skipping to change at line 220
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.4.5 NAME 'inetAsnRegistrar' DESC
'Registrar who delegated this ASN.' EQUALITY 'Registrar who delegated this ASN.' EQUALITY
caseIgnoreMatch SYNTAX directoryString ) caseIgnoreMatch SYNTAX directoryString )
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.
Hall I-D Expires: December 2003 [page 5]
inetAsnRegistry inetAsnRegistry
( 1.3.6.1.4.1.7161.1.4.6 NAME 'inetAsnRegistry' DESC ( 1.3.6.1.4.1.7161.1.4.6 NAME 'inetAsnRegistry' DESC
'Registry where this ASN is managed.' EQUALITY 'Registry where this ASN is managed.' EQUALITY
caseIgnoreMatch SYNTAX directoryString ) caseIgnoreMatch SYNTAX directoryString )
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.
skipping to change at line 261 skipping to change at line 266
| 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.
Hall I-D Expires: December 2003 [page 6]
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.
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=arpa" as the authoritative partition, and MUST use
"cn=inetResources,dc=arpa" for the search base. It is expected "cn=inetResources,dc=arpa" for the search base. It is expected
skipping to change at line 295 skipping to change at line 303
ASN queries. ASN queries.
FIRS clients MAY use the targeted bootstrap model for queries if FIRS clients MAY use the targeted bootstrap model for queries if
necessary or desirable. necessary or desirable.
Due to the lack of any public DNS delegation mapping service, Due to the lack of any public DNS delegation mapping service,
there is no practical reason for FIRS clients to use the bottom-up there is no practical reason for FIRS clients to use the bottom-up
model with ASN queries. 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 naming element
of the resource as a distinguished name attribute. For example, of the resource as a distinguished name attribute. For example,
"(&(objectclass=inetAsNumber)(cn:dn:65535))" with a search base of "(&(objectclass=inetAsNumber)(cn:dn:65535))" with a search base of
Hall I-D Expires: December 2003 [page 7]
"cn=inetResources,dc=arin,dc=net" would find all of the "cn=inetResources,dc=arin,dc=net" would find all of the
inetAsNumber object class entries with a relative distinguished inetAsNumber object class entries with a relative distinguished
name of "cn=65535" in the "dc=arin,dc=net" partition. name of "cn=65535" in the "dc=arin,dc=net" partition.
Hall I-D Expires: December 2003 [page 7]
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.
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=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=arpa" in the case of ASNs.
skipping to change at line 349 skipping to change at line 360
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.
Hall I-D Expires: December 2003 [page 8]
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].
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
skipping to change at line 407 skipping to change at line 423
[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.
[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.
[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.
Hall I-D Expires: December 2003 [page 10] Hall I-D Expires: December 2003 [page 10]
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.
11. Changes from Previous Versions 11. Changes from Previous Versions
skipping to change at line 455 skipping to change at line 472
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.
11. Changes from Previous Versions 11. Changes from Previous Versions
draft-ietf-crisp-fir-asn-00:
draft-ietf-crisp-firs-asn-01:
* Several clarifications and corrections have been made.
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
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
skipping to change at line 480 skipping to change at line 502
* 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.
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
Hall I-D Expires: December 2003 [page 11]
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
procedures for copyrights defined in the Internet Standards procedures for copyrights defined in the Internet Standards
process must be followed, or as required to translate it into process must be followed, or as required to translate it into
languages other than English. languages other than English.
 End of changes. 

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