RE: [Sipping] Text support in SIP phones

[Henry Sinnreich <[e-mail]>]

Keith, thanks for bringing balance, I believe, to this discussion.

We could formulate soemthing like "SIP phones that have a text display
and advertised as supporting the hearing or speech disabled MUST..."

Would this be OK?

Henry

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] 
> On Behalf Of Drage, Keith (Keith)
> Sent: Tuesday, June 10, 2003 8:14 AM
> To: 'Henry Sinnreich'; 'Gunnar Hellström'; 'Sipping@Ietf. 
> Org'; 'Sipforum-Discussion@Lists. Su. Se'
> Subject: RE: [Sipping] Text support in SIP phones
> 
> 
> I would suggest that treating these sort of things as MUST 
> strength is best left to national regulatory requirements, 
> along with other things like fitness for purpose and so on. I 
> have no objection to their being mentioned. By the way, I 
> understood this document was being progressed as authors 
> individual submission, and was therefore not standards track.
> 
> Any such MUST would surely need to be qualified anyway. If 
> the purpose of the devise is such that it renders a textual 
> devise irrelevant, then why require one to be fitted. Suppose 
> we were designing a SIP phone for the totally blind, and this 
> was designed to be worn as a headset, a text device would be 
> irrelevant to such a user, and positioning such a device 
> where it could be seen would require an extra box hanging out 
> of the side of the product.
> 
> regards
> 
> Keith
> 
> Keith Drage
> Lucent Technologies
> Tel: [phone]
> Email: [e-mail] 
> 
> > -----Original Message-----
> > From: Henry Sinnreich [mailto:[e-mail]]
> > Sent: 27 May 2003 17:18
> > To: 'Gunnar Hellström'; 'Sipping@Ietf. Org';
> > 'Sipforum-Discussion@Lists.
> > Su. Se'
> > Cc: 'Henry Sinnreich'
> > Subject: RE: [Sipping] Text support in SIP phones
> > 
> > 
> > Gunnar, this all seems very reasonable, and I will try to insert it 
> > properly.
> > 
> > Henry
> > 
> > > -----Original Message-----
> > > From: [e-mail] [mailto:[e-mail]]
> > > On Behalf Of Gunnar Hellström
> > > Sent: Thursday, May 22, 2003 6:54 PM
> > > To: 'Sipping@Ietf. Org'; Sipforum-Discussion@Lists. Su. Se
> > > Cc: Henry Sinnreich
> > > Subject: [Sipping] Text support in SIP phones
> > > 
> > > 
> > > Sorry, I missed out the reference to the SIP device specification.
> > > 
> > > Henry and all,
> > > 
> > > Some time ago, I suggested addition of support for real time
> > > text communication to the SIP device specification 
> > > 
> > 
> http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-00.txt
> > > 
> > > This was the simple part of the proposal:
> > > 
> > > > SIP-zz, digital text support: SIP telephone devices MUST support
> > > >   real time text conversation using RFC 2793 [y] for the
> > > text stream.
> > > >   It MUST be possible to use text simultaneously with voice.
> > > >
> > > >
> > > >
> > > > ---------------------------------------------
> > > > In 4.11 Ringer Behaviour  : add the section below for the
> > > purpose of
> > > > deaf, hearing impaired, deaf-blind people and people in the
> > > garden and
> > > > noisy
> > > > locations:
> > > >
> > > > SIP Telephony devices MUST provide an external interface to an
> > > > external alerting system.
> > > >
> > > >
> > > >
> > > > Add to References
> > > > -----------------
> > > > [y] G. Hellstrom: "RTP Payload for Text Conversation.", 
> RFC 2793,
> > > > IETF, May 2000.
> > > >
> > > > --------------------------------------------------------------
> > > 
> > > The reception of this proposal was very positive.
> > > Now, I would like to see the final formulation, and check
> > > that we agree on it.
> > > 
> > > I regard this requirement to be very light. In the Interface
> > > section ( e.g.
> > > Int-2) , there is already mentioning of mandatory text input 
> > > mechanisms, and assumptions that a display would be normal, 
> > > since handling of phone books and buddy lists are mandatory. 
> > > To re-use these text interface devices during the call for 
> > > standardised text conversation purposes seems straightforward.
> > > 
> > > It could be wise to add the T.140 text presentation protocol
> > > as a codec to the codec section. The normal SDP used together 
> > > with RFC2793 for text could also be specified. Do you want 
> > to do that?
> > > 
> > > 
> > > -----
> > > 
> > > We also need to check the ideas around the other proposed
> > > requirements: The requirement to include text telephone modem 
> > > in all designs where an RJ11 phone connector exists, and the 
> > > requirement to support RFC 3351. I suggest that we start with 
> > > the straightforward and mainstream requirement above. Is that 
> > > accepted as it is?
> > > 
> > > 
> > > Regards
> > > 
> > > Gunnar
> > > -------------------------------------------
> > > Gunnar Hellström, Omnitor, Renathvägen 2
> > > SE 121 37 Johanneshov, SWEDEN
> > > Tel: [phone]  Mob: [phone]
> > > e-mail: [e-mail]
> > > web: www.omnitor.se
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listi> nfo/sipping
> > > This list 
> is for NEW development of the 
> application of SIP Use 
> > > [e-mail] for questions on current sip Use 
> > > [e-mail] for new developments of core SIP
> > > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use 
> > [e-mail] for questions on current sip Use 
> > [e-mail] for new developments of core SIP
> > 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [e-mail] for questions on current 
> sip Use [e-mail] for new developments of core SIP
> 
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP