Thread Subject: Re: FW: Alerting
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Schomburg, Paul
Date: Thu, Feb 28 2008 2:20 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: FW: Alerting"
- Previous message in thread: Gregg Vanderheiden: "FW: Alerting"
- Messages sorted by: Author | Thread | Date
Gregg: Thanks for sending this - it looks like an interesting protocol, but we'll need to review with technical experts. Do you know of any examples where RFC 4235 <http://tools.ietf.org/html/rfc4235> is supported in products today? In general, I do not think the TEITAC should recommend a particular standard unless it is widely adopted and necessary to guarantee interoperability. In this case I don't think interoperability is critical, since a proprietary solution may work just as well in an office environment. If RFC 4235 <http://tools.ietf.org/html/rfc4235> is as useful as the write-up indicates then I think the market will see many uses for it, but I don't think we should rule out proprietary approaches here either.
I wonder if the desired result can be achieved if the two notes were combined into one as follows:
NOTE: VoIP phones or VoIP telephone-emulation software can meet this provision by communicating via a network protocol with compatible software or hardware devices that provide visual and tactile alerting signals in the environment of people who cannot hear or cannot see and hear.