Re: draft-ietf-pkix-logotypes-06.txt

[Dean Povey <povey@xxxxxxxxxxxxx>]

On Wed, 23 Oct 2002 19:33:04 MST, "Trevor Freeman" wrote: 
>Dean,
>The approach you suggest would put the onus on the application having
>text to audio technology to support this case as apposed to simply
>playing an audio file. And that text to audio technology must work for
>all languages and cope with translation. That is a pretty high bar.

How else do you think visually impaired people read web pages?  I don't 
know a huge amount about this, but there is a variety of software (e.g. 
JAWS see http://www.freedomscientific.com/fs_products/software_jaws.asp) 
that does text to speech translation, and when you develop web sites for 
accessibility you consider how such software will "read" your 
site.

However, the comment about languages is interesting, will
internationalization issues be addressed in audio types?

I apologise for not raising this issue earlier than last call, but it 
seems there is sufficient controversy about this feature to warrant a 
decision.  I think most of the major arguments have been covered, and I 
have seen at least one other call for a straw poll on the feature.  I have 
no wish to hold up this draft endlessly.

I think the issue of accessibility is an important one, but perhaps this 
needs to be addressed in a separate draft that considers other parts of 
PKIX as well.

If we are to hold a straw poll, might I suggest rather than a simple 
plebiscite on whether audio is in or out that the options proposed be:

1. To exclude the audio type from the draft, and either provide text
   addressing accessibility concerns (for example using the suggestion that
   software read out the issuer and/or subject names), or make a work item
   to write a separate draft which deals with accessibility issues related
   to PKIX in general.

2. To leave the audio type in, and add text to security considerations to
   deal with the problem of distinguishing audio for trust purposes from 
   any other audio that an application might present, as well as address 
   the internationalisation issue.

Thoughts?
-- 
Dean Povey,             |em: povey@xxxxxxxxxxxxx|JCSI: Java security toolkit
Wedgetail Communications|ph:  +61 7 3023 5139   |uPKI: Embedded/C PKI toolkit
Level 14, 388 Queen St, |fax: +61 7 3023 5199   |uSSL: Embedded/C SSL toolkit
Brisbane, Australia     |www: www.wedgetail.com |XML Security: XML Signatures