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

Re: [Syntaxes] Generalized Time inconsistent with ASN.1

To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Subject: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
From: Michael Ströder <michael@stroeder.com>
Date: Thu, 22 May 2003 14:43:02 +0200
Cc: ietf-ldapbis@OpenLDAP.org
In-reply-to: <HBF.20030522msyf@bombur.uio.no>
References: <HBF.20030521bg8n@bombur.uio.no> <004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au> <HBF.20030522msyf@bombur.uio.no>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425

Hallvard B Furuseth wrote:


I take it making the time zone optional is too big a change for ldapbis?
How about allowing servers to support local time, but not demainding it?

Personally I'd like to leave it as is since it's well-defined and simple. What implementors definitely not need is dealing with yet another optional case. We have already way too many "OPTIONALs" in LDAP.

Ciao, Michael.

References:
- [Syntaxes] Generalized Time inconsistent with ASN.1
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- RE: [Syntaxes] Generalized Time inconsistent with ASN.1
  - From: "Steven Legg" <steven.legg@adacel.com.au>
- RE: [Syntaxes] Generalized Time inconsistent with ASN.1
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>

Prev by Date: RE: [Syntaxes] Generalized Time inconsistent with ASN.1
Next by Date: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
Index(es):
- Chronological
- Thread