Happenings at the recent OIW Directory SIG meeting.

Richard Colella <colella@emu.ncsl.nist.gov> Wed, 19 June 1991 17:15 UTC

Received: by merit.edu (5.65/1123-1.0) id AA05217; Wed, 19 Jun 91 13:15:21 -0400
Received: from EMU.NCSL.NIST.GOV by merit.edu (5.65/1123-1.0) id AA05213; Wed, 19 Jun 91 13:15:11 -0400
Received: by emu.ncsl.nist.gov (4.1/NIST(rbj/dougm)) id AA16153; Wed, 19 Jun 91 13:12:39 EDT
Date: Wed, 19 Jun 91 13:12:39 EDT
From: Richard Colella <colella@emu.ncsl.nist.gov>
Organization: National Institute of Standards and Technology (NIST)
Sub-Organization: Computer Systems Laboratory (CSL)
Message-Id: <9106191712.AA16153@emu.ncsl.nist.gov>
To: disi, fox, osi-ds@cs.ucl.ac.uk
Subject: Happenings at the recent OIW Directory SIG meeting.
Cc: Richard_<Colella@osi3.ncsl.nist.gov>, dssig@nisc.sri.com, rlang@nisc.sri.com

The Directory SIG met last week during the OSI Implementors' Workshop.
The agenda included an item resulting from the attempts at SRI to load
the WHOIS database into X.500.  In particular, the postalAddress upper
bound constraint of 30 characters per line was too small for about half
of the 100K entries.  I had offered to carry this issue in on behalf of
the FOX effort;  I am reporting the results more widely, since I
believe this to be of general interest.

The upshot of the SIG meeting is that the SIG voted unanimously to
change the upper bound on a line to 60 characters (the number
of lines will remain at 6).  This change will be reflected in
the Working Agreements out of this meeting, and will be voted
on for inclusion into the Stable Implementation Agreements at
the September meeting.

A number of individuals were polled informally during the week
to get a reading on whether this would be a problem:

	- A representative from the USPS (since the 6x30 constraint
		is based on a UPU standard);

	- A long-standing member of the ANSI/ISO X.500 standards
		effort, who knows the X.500 history; and,

	- Folks from the MHS SIG, who build X.400 products.

The general consensus was that, not only should the Directory SIG
make this change, but it should be used as a driving function get
others to make the same change.

--Richard