[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: What can you do to the ASN.1 wo getting into trouble with the IESG?

To: Harald Alvestrand <Harald@Alvestrand.no>, "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, Leif Johansson <leifj@it.su.se>
Subject: Re: What can you do to the ASN.1 wo getting into trouble with the IESG?
From: Patrik Fältström <paf@cisco.com>
Date: Thu, 31 Aug 2000 07:27:00 +0200
Cc: ietf-ldapbis@OpenLDAP.org
In-reply-to: <4.3.2.7.2.20000830221843.018a3c38@127.0.0.1>
References: <200008300856.KAA10484@mail.su.se> <4.3.2.7.2.20000830221843.018a3c38@127.0.0.1>

At 22.21 +0200 00-08-30, Harald Alvestrand wrote:

Adding new features to work around or replace broken features MUST be done using the extension mechanism (and documented outside the core RFCs) unless it is really, really necessary to do otherwise.


I would say: "...really really really really really really necessary..."

And, if you do, don't be surprised if someone want to recycle at Proposed.

paf

References:
- What can you do to the ASN.1 wo getting into trouble with the IESG?
  - From: Leif Johansson <leifj@it.su.se>
- Re: What can you do to the ASN.1 wo getting into trouble with the IESG?
  - From: Harald Alvestrand <Harald@Alvestrand.no>

Prev by Date: Re: What can you do to the ASN.1 wo getting into trouble with the IESG?
Next by Date: RE: X.500 and LDAP alignment
Index(es):
- Chronological
- Thread