draft-ietf-crisp-firs-contact-02.txt   draft-ietf-crisp-firs-contact-03.txt 
INTERNET-DRAFT Eric A. Hall INTERNET-DRAFT Eric A. Hall
Document: draft-ietf-crisp-firs-contact-02.txt July 2003 Document: draft-ietf-crisp-firs-contact-03.txt August 2003
Expires: February, 2004 Expires: March, 2004
Category: Standards-Track Category: Standards-Track
Defining and Locating Contact Information Defining and Locating Contact Information
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 50 skipping to change at line 50
(FIRS) described in [FIRS-ARCH] and [FIRS-CORE]. (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.....................................6
5.1. Query Pre-Processing....................................6 5.1. Query Pre-Processing....................................6
5.2. Query Bootstrapping.....................................7 5.2. Query Bootstrapping.....................................6
5.3. LDAP Matching...........................................7 5.3. LDAP Matching...........................................7
5.4. Example Query...........................................8 5.4. Example Query...........................................8
6. Security Considerations....................................8 6. Security Considerations....................................8
7. IANA Considerations........................................9 7. IANA Considerations........................................9
8. Normative References.......................................9 8. Normative References.......................................9
9. Changes from Previous Versions............................10 9. Changes from Previous Versions............................10
10. Author's Addresses........................................11 10. Author's Addresses........................................11
11. Acknowledgments...........................................11 11. Acknowledgments...........................................11
12. Full Copyright Statement..................................11 12. Full Copyright Statement..................................11
skipping to change at line 87 skipping to change at line 87
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 that set, which specification should be read in the context of that set, which
currently includes [FIRS-ARCH], [FIRS-CORE], [FIRS-DNS], currently includes [FIRS-ARCH], [FIRS-CORE], [FIRS-DNS],
[FIRS-DNSRR], [FIRS-ASN], [FIRS-IPV4] and [FIRS-IPV6]. [FIRS-DNSRR], [FIRS-ASN], [FIRS-IPV4] and [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] Hall I-D Expires: March 2004 [page 2]
3. Naming Syntax 3. Naming Syntax
The naming syntax for contact entries in FIRS MUST follow the form The naming syntax for contact entries in FIRS MUST follow the form
of "cn=<inetContactSyntax>,cn=inetResources,<partition>", where of "cn=<inetContactSyntax>,cn=inetResources,<partition>", where
<inetContactSyntax> is an email address representing a contact <inetContactSyntax> is an email address representing a contact
resource, and where <partition> is a sequence of domainComponent resource, and where <partition> is a sequence of domainComponent
relative distinguished names which identifies the scope of relative distinguished names which identifies the scope of
authority for the selected directory partition. authority for the selected directory partition.
The inetContactSyntax is unstructured, in that it uses The inetContactSyntax is unstructured, in that it uses
skipping to change at line 133 skipping to change at line 133
c. The domain element MUST be normalized according to the c. The domain element MUST be normalized according to the
inetDnsDomainSyntax procedure defined in [FIRS-DNS]. inetDnsDomainSyntax procedure defined in [FIRS-DNS].
Once all of these steps have successfully completed, the email Once all of these steps have successfully completed, the email
address can be stored in the directory or used as an assertion address can be stored in the directory or used as an assertion
value. Any fatal error conditions encountered during these value. Any fatal error conditions encountered during these
conversions MUST result in a local failure; FIRS-aware conversions MUST result in a local failure; FIRS-aware
applications MUST NOT store or transmit non-normalized email applications MUST NOT store or transmit non-normalized email
addresses for any purposes. addresses for any purposes.
Hall I-D Expires: February 2004 [page 3] Hall I-D Expires: March 2004 [page 3]
The inetContactSyntax syntax is as follows: The inetContactSyntax syntax is as follows:
inetContactSyntax inetContactSyntax
( 1.3.6.1.4.1.7161.1.4.1 NAME 'inetContactSyntax' DESC 'A ( 1.3.6.1.4.1.7161.1.4.0
fully-qualified email address.' ) NAME 'inetContactSyntax'
DESC 'A fully-qualified email address.' )
Note that the use of the "at" separator character is illegal as Note that the use of the "at" separator character is illegal as
data in URLs, and these characters will be escaped before they are data in URLs, and these characters will be escaped before they are
stored in a URL as data. stored in a URL as data.
Also note that UTF-8 characters use character codes which are Also note that UTF-8 characters use character codes which are
frequently illegal as data in URLs, and many of those octet values frequently illegal as data in URLs, and many of those octet values
will probably be escaped before they are stored in a URL as data. will probably be escaped before they are stored in a URL as data.
4. Object Classes and Attributes 4. Object Classes and Attributes
Contact entries in FIRS MUST use the inetOrgPerson object class as Contact entries in FIRS MUST use the inetOrgPerson object class as
defined in RFC 2798 [RFC2798], in addition to the mandatory object defined in RFC 2798 [RFC2798], in addition to the mandatory object
classes defined in [FIRS-CORE]. Contact entries MUST be treated as classes defined in [FIRS-CORE]. Contact entries MUST be treated as
containers capable of holding subordinate entries. If an entry containers capable of holding subordinate entries.
exists as a referral source, the entry MUST also be defined with
the referral object class, in addition to the above requirements. 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 inetOrgPerson object class is a structural object class. The The inetOrgPerson object class is a structural object class. The
inetOrgPerson object class has three mandatory attributes (cn, sn, inetOrgPerson object class has three mandatory attributes (cn, sn,
and objectClass), and has several optional attributes. Contact and objectClass), and has several optional attributes. Contact
entries also inherit the attributes defined in the inetResources entries also inherit the attributes defined in the inetResources
object class when they are used with FIRS. object class when they are used with FIRS.
Refer to [RFC2798] for the inetOrgPerson schema definitions. Refer to [RFC2798] for the inetOrgPerson schema definitions.
Note that the "mail" attribute defined for use with the Note that the "mail" attribute defined for use with the
inetOrgPerson object class is restricted to seven-bit character inetOrgPerson object class is restricted to seven-bit character
codes and is typically interpreted as [US-ASCII], and is therefore codes and is typically interpreted as [US-ASCII], and is therefore
not compatible with the inetContactSyntax rules defined in section not compatible with the inetContactSyntax rules defined in section
3. As such, if the mail domain uses an internationalized domain 3. As such, if the mail domain uses an internationalized domain
name, the domain element of the mail attribute MUST be reduced to name, the domain element of the mail attribute MUST be reduced to
its ASCII-compatible form using the ToASCII process defined in its ASCII-compatible form using the ToASCII process defined in
[RFC3490], and MUST NOT use the UTF-8 encoding. [RFC3490], and MUST NOT use the UTF-8 encoding.
Hall I-D Expires: March 2004 [page 4]
Note that International postal regulations generally require that Note that International postal regulations generally require that
the recipient address on an envelope be provided in a language and the recipient address on an envelope be provided in a language and
charset which is native to the recipient's country, with the charset which is native to the recipient's country, with the
exception of the destination country name which should be provided exception of the destination country name which should be provided
in a language and charset that is native to the sender's country. in a language and charset that is native to the sender's country.
Hall I-D Expires: February 2004 [page 4]
This model ensures that the sender's post office will be able to This model ensures that the sender's post office will be able to
route the mail to the recipient's country, while also ensuring route the mail to the recipient's country, while also ensuring
that the destination country's post office will be able to perform that the destination country's post office will be able to perform
local delivery. In order to facilitate this usage, the country local delivery. In order to facilitate this usage, the country
attribute value MAY (encouraged) be localized to the local user's attribute value MAY (encouraged) be localized to the local user's
nomenclature for a country, but other postal address information nomenclature for a country, but other postal address information
SHOULD NOT be localized. SHOULD NOT be localized.
Notwithstanding the above, it is ENCOURAGED that contact names be Notwithstanding the above, it is ENCOURAGED that contact names be
provided in English forms in order to facilitate inter-party provided in English forms in order to facilitate inter-party
skipping to change at line 206 skipping to change at line 210
stated in the preceding paragraph however, any postal stated in the preceding paragraph however, any postal
communications for that person SHOULD use the native-language communications for that person SHOULD use the native-language
representation (at least on the envelope) in order to facilitate representation (at least on the envelope) in order to facilitate
the delivery of postal mail. the delivery of postal mail.
An example of the inetOrgPerson object class in use is shown in An example of the inetOrgPerson object class in use is shown in
Figure 1 below. The example includes attributes from the Figure 1 below. The example includes attributes from the
inetOrgPerson, inetResources, and inetAssociatedResources object inetOrgPerson, inetResources, and inetAssociatedResources object
classes. classes.
Hall I-D Expires: February 2004 [page 5]
cn=admins@example.com,cn=inetResources,dc=example,dc=com cn=admins@example.com,cn=inetResources,dc=example,dc=com
[top object class] [top object class]
[inetResources object class] [inetResources object class]
[inetOrgPerson object class] [inetOrgPerson object class]
[inetAssociatedResources object class] [inetAssociatedResources object class]
| |
+-attribute: description
| value: "Administrators for the example.com network."
|
+-attribute: givenName
| value: "Network"
|
+-attribute: sn
| value: "Administrators"
|
+-attribute: mail +-attribute: mail
| value: "admins@example.com" | value: "admins@example.com"
| |
+-attribute: inetAssociatedDnsDomain
| value: "example.com"
| value: "2.0.192.in-addr.arpa"
|
+-attribute: inetAssociatedIpv4Network +-attribute: inetAssociatedIpv4Network
value: "192.0.2.0/24" value: "192.0.2.0/24"
Figure 1: The entry for the admins@example.com contact in the Figure 1: The entry for the admins@example.com contact in the
dc=netsol,dc=com partition. dc=netsol,dc=com partition.
Hall I-D Expires: March 2004 [page 5]
5. Query Processing Rules 5. Query Processing Rules
Queries for contact entries have several special requirements, as Queries for contact entries have several special requirements, as
discussed in the following sections. discussed 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.
The authoritative partition for a contact entry is determined by The authoritative partition for a contact entry is determined by
mapping the domain element of a normalized email address to a mapping the domain element of a normalized email address to a
sequence of domainComponent labels. sequence of domainComponent labels.
Hall I-D Expires: February 2004 [page 6]
Since the domainComponent attribute is restricted to seven-bit Since the domainComponent attribute is restricted to seven-bit
characters, the domain element MUST be converted to its IDNA form characters, the domain element MUST be converted to its IDNA form
using the "ToASCII" conversion operation specified in [RFC3490], using the "ToASCII" conversion operation specified in [RFC3490],
with the "UseSTD3ASCIIRules" flag disabled (FIRS applications MAY with the "UseSTD3ASCIIRules" flag disabled (FIRS applications MAY
reuse the output from the conversion performed in step 3.c if the reuse the output from the conversion performed in step 3.c if the
entire conversion process is known to have completed entire conversion process is known to have completed
successfully). The resulting sequence of ASCII labels are used to successfully). The resulting sequence of ASCII labels are used to
form the domainComponent sequence which represents the form the domainComponent sequence which represents the
authoritative partition for the email address. authoritative partition for the email address.
skipping to change at line 282 skipping to change at line 272
distinguished names of the authoritative partition. distinguished names of the authoritative partition.
FIRS clients MAY use the targeted or top-down bootstrap models for FIRS clients MAY use the targeted or top-down bootstrap models for
queries if necessary or desirable. However, it is not likely that queries if necessary or desirable. However, it is not likely that
entries will be found for all possible contacts using these models entries will be found for all possible contacts using these models
(the "dc=com" partition is not likely to have entries for all of (the "dc=com" partition is not likely to have entries for all of
the possible contacts with mailboxes in the "com" hierarchy, for the possible contacts with mailboxes in the "com" hierarchy, for
example). As such, the bottom-up bootstrap model will be the most example). As such, the bottom-up bootstrap model will be the most
useful in most cases, and MUST be used by default. useful in most cases, and MUST be used by default.
Hall I-D Expires: March 2004 [page 6]
Note that registration bodies can allocate email addresses within Note that registration bodies can allocate email addresses within
their own managed portion of the DNS namespace if predictability their own managed portion of the DNS namespace if predictability
is at a premium. For example, a registrar could assign is at a premium. For example, a registrar could assign
"user@registrar.com" email addresses to the contact entries that "user@registrar.com" email addresses to the contact entries that
it creates, thereby ensuring that the contact entries are always it creates, thereby ensuring that the contact entries are always
locatable and managed. locatable and managed.
5.3. LDAP Matching 5.3. LDAP Matching
FIRS clients MUST specify equalityMatch matching filters in LDAP If the server advertises the inetOrgPerson object class and the
searches for contact entries. inetContactMatch matching filter in the inetResourcesControl
server control, FIRS clients MUST use the inetDnsDomainMatch
matching filter in LDAP searches for contact entries.
In order to ensure that all of the relevant entries are found The inetContactMatch filter provides an identifier and search
(including any referrals), the search filters for these resources string format which collectively inform a queried server that a
MUST specify the inetOrgPerson object class and the cn attribute. specific contact identifier should be searched for, and that any
For example, "(&(objectclass=inetOrgPerson) inetOrgPerson object class entries which match the assertion value
(cn=admins@example.com))" with a search base of should be returned.
Hall I-D Expires: February 2004 [page 7] The inetContactMatch filter is defined as follows:
"cn=inetResources,dc=netsol,dc=com" would find all of the
inetOrgPerson object class entries of "cn=admins@example.com" in inetContactMatch
the "dc=netsol,dc=com" partition. ( 1.3.6.1.4.1.7161.1.4.0.1
NAME 'inetDnsDomainMatch'
SYNTAX 1.3.6.1.4.1.7161.1.4.0 )
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 to the resulting LDAP query.
A FIRS server MUST compare the assertion value against the
distinguished name of all entries within and beneath the container
specified by the search base of the query. Any entry in that
hierarchy with an object class of inetOrgPerson and a
distinguished name component that is equal to the assertion value
MUST be returned to the client (this specifically includes any
child entries, such as referral stubs). Entries which do not have
an object class of inetOrgPerson MUST NOT be returned.
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 matching filters, although FIRS clients MUST NOT expect
filters they wish (these may be required to support generic LDAP any additional filters to be available.
clients), although FIRS clients MUST NOT expect any additional
filters to be available. Hall I-D Expires: March 2004 [page 7]
If the server does not advertise support for the inetContactMatch
matching filter in the inetResourcesControl server control, the
client MAY choose to emulate the 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 inetContactMatch matching filter
in the inetResourcesControl control, the client MUST use it.
5.4. Example Query 5.4. Example Query
The following example assumes that the user has specified The following example assumes that the user has specified
"admins@example.com" as the query value: "admins@example.com" as the query value:
a. Normalize the input, which is "admins@example.com" in this a. Normalize the input, which is "admins@example.com" in this
case. case.
b. Determine the canonical authoritative partition, which is b. Determine the canonical authoritative partition, which is
skipping to change at line 337 skipping to change at line 352
"cn=inetResources,dc=example,dc=com" if the defaults are "cn=inetResources,dc=example,dc=com" if the defaults are
used. used.
d. Initiate a DNS lookup for the SRV resource records d. Initiate a DNS lookup for the SRV resource records
associated with "_ldap._tcp.example.com." For the purpose associated with "_ldap._tcp.example.com." For the purpose
of this example, assume that this lookup succeeds, with the of this example, assume that this lookup succeeds, with the
DNS response message indicating that "firs.example.com" is DNS response message indicating that "firs.example.com" is
the preferred LDAP server. the preferred LDAP server.
e. Submit an LDAPv3 query to the specified server, using e. Submit an LDAPv3 query to the specified server, using
"(&(objectClass=inetOrgPerson)(cn:dn:admins@example.com))" "(1.3.6.1.4.1.7161.1.4.0.1:=admins@example.com)" as the
as the matching filter, "cn=inetResources,dc=example, matching filter, "cn=inetResources,dc=example, dc=com" as
dc=com" as the search base, and the global query defaults the search base, and the global query defaults defined in
defined in [FIRS-CORE]. [FIRS-CORE].
f. Assume that no referrals are received. Display the answer f. Assume that no referrals are received. Display the answer
data which has been received and exit the query. data which has been received and exit the query.
6. Security Considerations 6. Security Considerations
Hall I-D Expires: February 2004 [page 8]
Security considerations are discussed in [FIRS-ARCH]. Security considerations are discussed in [FIRS-ARCH].
Hall I-D Expires: March 2004 [page 8]
7. IANA Considerations 7. IANA Considerations
IANA considerations are discussed in [FIRS-ARCH]. IANA considerations are discussed in [FIRS-ARCH].
8. Normative References 8. Normative References
[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, July Guide", draft-ietf-crisp-firs-arch-03, August
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, July 2003. 03, August 2003.
[FIRS-CONTCT] Hall, E. "Defining and Locating Contact
Persons in the Federated Internet Registry
Service", draft-ietf-crisp-firs-contact-01,
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, July 2003. firs-core-03, August 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, July 2003. draft-ietf-crisp-firs-dns-03, August 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, July Service", draft-ietf-crisp-firs-dnsrr-03, 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, July Service", draft-ietf-crisp-firs-ipv4-03,
2003. August 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, July Service", draft-ietf-crisp-firs-ipv6-03,
2003. August 2003.
[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: February 2004 [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.
Hall I-D Expires: March 2004 [page 9]
[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.
[RFC2279] Yergeau, F. "UTF-8, a transformation format of [RFC2279] Yergeau, F. "UTF-8, a transformation format of
ISO 10646", RFC 2279, January 1998. ISO 10646", RFC 2279, January 1998.
[RFC2596] Wahl, M., and Howes, T. "Use of Language Codes [RFC2596] Wahl, M., and Howes, T. "Use of Language Codes
in LDAP", RFC 2596, May 1999. in LDAP", RFC 2596, May 1999.
[RFC2798] Smith, M. "Definition of the inetOrgPerson [RFC2798] Smith, M. "Definition of the inetOrgPerson
skipping to change at line 429 skipping to change at line 439
[RFC3490] Faltstrom, P., Hoffman, P., and Costello, A. [RFC3490] Faltstrom, P., Hoffman, P., and Costello, A.
"Internationalizing Domain Names in "Internationalizing Domain Names in
Applications (IDNA)", RFC 3490, March 2003. Applications (IDNA)", RFC 3490, March 2003.
[US-ASCII] Cerf, V. "ASCII format for Network [US-ASCII] Cerf, V. "ASCII format for Network
Interchange", RFC 20, October 1969. Interchange", RFC 20, October 1969.
9. Changes from Previous Versions 9. Changes from Previous Versions
draft-ietf-crisp-firs-contact-03:
* Several clarifications and corrections have been made.
* The inetContactMatch matching filter was defined. The use
of equalityMatch and extensibleMatch has been deprecated.
draft-ietf-crisp-firs-contact-02:
* Several clarifications and corrections have been made.
draft-ietf-crisp-firs-contact-01: draft-ietf-crisp-firs-contact-01:
* Several clarifications and corrections have been made. * Several clarifications and corrections have been made.
* 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.
draft-ietf-crisp-firs-contact-00: draft-ietf-crisp-firs-contact-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
Hall I-D Expires: March 2004 [page 10]
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.
draft-ietf-crisp-lw-user-01: draft-ietf-crisp-lw-user-01:
Hall I-D Expires: February 2004 [page 10]
* Removed references to LDAPS (LDAP-over-SSL), which is not a * Removed references to LDAPS (LDAP-over-SSL), which is not a
standards-track protocol. standards-track protocol.
* Added a discussion on localization considerations. * Added a discussion on localization considerations.
* Moved attribute-specific security requirements to the * Moved attribute-specific security requirements to the
Security section. Security section.
10. Author's Addresses 10. Author's Addresses
skipping to change at line 492 skipping to change at line 514
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.
Hall I-D Expires: March 2004 [page 11]
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.
Hall I-D Expires: February 2004 [page 11]
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: February 2004 [page 12] Hall I-D Expires: March 2004 [page 12]
 End of changes. 

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