Requirements for Distributed Control of Automatic Speech Recognition (ASR), Speaker Identification/Speaker Verification (SI/SV), and Text-to-Speech (TTS) Resources
draft-ietf-speechsc-reqts-07
Discuss
Yes
(Jon Peterson)
No Objection
(Alex Zinin)
(Bill Fenner)
(David Kessens)
(Russ Housley)
(Sam Hartman)
Note: This ballot was opened for revision 07 and is now closed.
Steven Bellovin Former IESG member
Discuss
Discuss
[Treat as non-blocking comment]
(2004-03-17)
Unknown
The suggested use of speech as a biometric authenticator over the Internet is in direct contradiction of the recommendations the cited U.S. National Research Council study [14]. Note also the comments that biometric authenticators must be treated as static passwords when traversing a network -- they're subject to capture and replay. We do not permit use of plaintext passwords in IETF standards. I'm not (quite) prepared to insist that the material on biometrics be deleted from the specification. But I'd really like more discussion of the concerns from the report in the Security Considerations section -- a reader of just this document would have no hint that the report says flat-out that this is a bad idea. Beyond that, the document must mandate use of confidentiality technologies for such uses.
Jon Peterson Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Bert Wijnen Former IESG member
No Objection
No Objection
(2004-03-18)
Unknown
Mmm... what was that RFC-Editor policy about acronyms in titles? This doc has as title: Requirements for Distributed Control of ASR, SI/SV and TTS Resources Quite a few acronyms, no?
Bill Fenner Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss, No Objection)
No Objection
No Objection
()
Unknown
Sam Hartman Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
(2004-03-16)
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
(2004-03-17)
Unknown
I'm a no-ob on this because I don't think it will actively harm the effort to get this work done, but there are a lot of requirements in here that aren't well mapped to specific use cases. The "VCR controls" noted in 4.5, for example make no sense for the speaker identification use case given in 2.3, but those requirements are put forward as if they applied to all use cases. This document also trends away from the requirements to the design on a number of cases (the xml:lang tag for multi-lingual TTS, for example). The acknowlegemetns are, too say the least, interesting; the rules indicating that it is a bad idea for a doc author and chair to be the same aren't there to prevent appropriate acknowledgement when it occurs--they're there to avoid conflicts in role.