[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-zeilenga-ldap-user-schema
Hi Russ,
I certainly don't mean to cut off discussion of the draft, and I agree
with Harald that there are few disasters that will loom up at us in
the two weeks before the retreat. I suggest you go ahead with
the DEFER, in other words, and we can continue the discussion
in person.
regards,
Ted
On Monday, April 14, 2003, at 11:37 PM, Russ Housley wrote:
Ted:
I did not know that Bert was waiting on this draft. Since the
long-term solution is in line with this document, I will not delay it.
But, I would appreciate your help in keeping the embedded client as
simple as possible and broadly interoperable.
Russ
At 05:38 PM 4/14/2003 -0700, Ted Hardie wrote:
Hi Russ,
If you have a strong need to have this discussed face-to-face,
then using the defer to give us time at the retreat certainly makes
sense.
The piece that is missing for me seems to fit here:
I am getting quite frustrated about this issue. When everyone
agrees on the long-term solution, I am reluctant to let alternative
short-term solutions achieve RFC status that will cause bloat in
clients, interoperability hassles for users, or, more likely, both.
Since this draft is the long term solution, I'm not sure I
understand how it achieving RFC status relates
to the alternative short-term solutions reaching RFC. If its
_omission_ of a specific hook (like ;binary)
is perceived as precluding the short term solution, then we may be
able to clarify that in the IESG note
as well. Text like:
Readers will note that this document does not specify $FOO,
which was originally part of
RFC XXXX. The LDAP community is currently considering the
use of $FOO, and the IESG
expects a separate document to describe whether $FOO will be
deprecated or how its
usage within the LDAP community has changed.
If the resolution looked fast or easy, I would say wait, but
Bert is already waiting on this
draft and I'm not sure "good, fast, or cheap" will be forthcoming.
If this is all much more complicated, then we can discuss it
at the retreat.
Sorry for your frustration, and I hope my own ignorance of
the history here isn't adding to it,
regards,
Ted
Hardie