[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] Future of the requirements document



-----BEGIN PGP SIGNED MESSAGE-----

Here is my position on the requirements document, FWIW:

 - I read the document very thoroughly when preparing the changes I
   suggested on 9 October, and I think that adopting those changes would
   fix all of the overspecifications and technical errors. No-one has
   objected to any of those changes, and none of them are particularly
   controversial.

 - as well as overspecifications, there are arguably some under-
   specifications in the document, but this is much less of a problem.
   I don't think it needs to be solved completely; just add a disclaimer
   that the requirements listed are necessary, but that there may be
   disagreement on their sufficiency.

 - there is value in publishing the document despite the previous point,
   as a historical record if nothing else. Its description of the
   relation between domain names and hostnames, and of the DNS
   architecture, is accurate and useful.

 - writing a new document to replace the requirements doc would take
   longer than fixing it. In fact, it could have been fixed a month ago
   if the authors had been more responsive.


> That is, again, subject to discussion.  But I'd hope that those
> who advocate keeping/ fixing the requirements doc explain why it
> is important enough to keep the WG in operation --and hold up the
> protocol documents-- for what I think would be many extra months.

The requirements doc isn't on the critical path for approving protocol
documents at all. If the authors don't feel they have time to fix it,
send me the nroff source and I'll make the changes.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBPBUwDzkCAxeYt5gVAQHoBwgAyHct5NxhU1rTPH7Y+Mf618ePxYjKRWc9
x4F+Rs41AzPv/lobTN2ZO0730io/sdvm83RrmU9I/AnYP3YBJ/89kH9izzYCSPVU
dMDewpO8n/IsP45jSSkdyRjRnTpuMPuPch3i7qzMkxDTY2laxW1UM/L9+QUUGd22
efawp6XjqdwUvChEjp8bI7+qBBa8ieodZ73yy0NZOAQ0dD8kHArtdO95lu1QfnP5
ib+S9WxAgtr9L338ohkoIKaRIaQmNd7cKFwn6rdguoErmAJmkvMFhf9CL6jBMFrm
59pAZdcXT3cEHstcQhH48YnhHtQO8d47w/9Y/0IvRSfV8F5yx86Bmg==
=68MZ
-----END PGP SIGNATURE-----