|
I have a few issues with this document that I'd like to see resolved.
1) References to RFC 1738. Can we update these to 2396 and make the
appropriate section changes?
1) Allow the use of <userinfo>@<host>:<port> (RFC 2396)
rather than hostport. This provides a more consistent alternative to using
!bindname=jimse
2) Missing search constraints: The following elements of a search request
are missing. derefAliases, size/timeLimit, typesOnly. We need some of these
to be available, specifically for referrals and search continuations.
3) BNF grammar. It would be nice if the document specified what flavor of
BNF is being used in section 3. Also, it might be easier to read if the order of
the definitions followed their order in the URL like this:
ldapurl = scheme "://"
[hostport]
["/"
[dn ["?" [attributes] ["?" [scope] ["?" [filter] ["?" extensions]]]]]] scheme = "ldap" hostport = hostport from Section 5 of RFC 1738 [5] dn = distinguishedName from Section 3 of [1] attributes = attrdesc *("," attrdesc) attrdesc = AttributeDescription from Section 4.1.5 of [2] scope = "base" / "one" / "sub" filter = filter from Section 4 of [4] extensions = extension *("," extension) extension = ["!"] extype ["=" exvalue] extype = token / xtoken exvalue = LDAPString from section 4.1.2 of [2] token = oid from section 4.1 of [3] xtoken = ("X-" / "x-") token Jim
>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/23/00 6:25:03 PM >>> I draw your attention to the following I-D: The LDAP URL Format draft-smith-ldapv3-url-update-00.txtt This I-D proposes a technical specification to replace RFC 2255. I request you review this I-D as a strawman proposal to fulfill LDAPbis proposed work item. No technical changes were made to the specification. Your comments are solicited. |