Thread Subject: Template material to review before Monday's call

Return to this mailing list's archives

From: Brenda Battat
Date: Fri, Mar 02 2007 12:45 PM
Subject: Template material to review before Monday's call

Dear TCC Subcommittee Members:

As we agreed on our last call, this coming Monday we will discuss
changes that we would like to see based on our discussions so far. The
lion's share of what you will see in the Template, which is linked
below, has been provided by Diane Golden. Bruce Bailey kindly posted to
the Wiki.

This is just a starting point and we look for your input on next
Monday's call on what we have so far and what needs to be added.

The page is up at URL:

http://teitac.org/wiki/Telecom_Report_2007-03-12
<http://teitac.org/wiki/Telecom_Report_2007-03-12>

Thank you and talk on Monday!

Brenda Battat

Associate Executive Director

Hearing Loss Association of America (formerly SHHH)

301-657-2248 phone

301-913-9413 fax

From: Gregg Vanderheiden
Date: Sun, Mar 04 2007 10:35 PM
Subject: Re: Template material to review before Monday'scall

Thoughts on the Issue Summary etc.





1) We need to change the TTY provisions to reflect the new IP networks.
If we don't want to call IP Telephones as 'telecom' then we can change the
name of this group. But I think this group needs to be the one that talks
about VoIP phones.



2) The TTY provisions should be rewritten to say something like "TTY
for PSTN system and IPText for IP systems"



3) "other text conversation functionality" it too vague. People
converse on email and SMS even thought turn around times of 7 min are not
unusual for SMS. Suggest we add 'real-time'



4) Having "a text conversation' function is not sufficient. There has
to be a standard one that is supported by all or transcoded to a standard
one or you can't have end to end conversation. WE can punt as to what it
is maybe (probably not a good idea but..) but we need to specify that the
standard is used.



5) We need to treat video as separate because video cannot substitute
for text. Although it is so much faster when people on both ends sign, it
will not work for the majority of people who cannot sign.



6)









1194.23(a1) Telecommunications products or systems that provide a function
allowing voice communication and do not themselves provide TTY for PSTN or
the standard real-time IP text format for IP systems:

(1) shall provide a standard non-acoustic connection point for TTYs for PSTN
products or an equivalent connection method for real-time IP text format for
IP systems and

(2) On PSTN systems microphones shall be capable of being turned on and off
to allow the user to intermix speech with text use.

(3) On IP systems it shall be possible to transmit text and speech in
parallel in both directions.



1194.23(a2) Telecommunications products or systems that provide a function
allowing voice communication and have sufficient bandwidth to support
real-time video signing but do not themselves provide real-time video
communication sufficient to support signing:

(1) shall provide a standard connection point attaching a real-time signing
device and

(2) On PSTN systems microphones shall be capable of being turned on and off
to allow the user to intermix speech with video.

(3) On IP systems it shall be possible to transmit text, video and speech in
parallel in both directions.



1194.23(b) Telecommunications products, which include voice communication
functionality, shall support the standard real-time text protocol for that
medium:

(1) on PSTN they shall support EIA/TIA 825 Baudot standard TTY signal
protocol.

(2) on IP networks they shall support ITU T-140 and RFC 4301 or shall be
capable of converting to this.





Etc






Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.






_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Brenda Battat
Sent: Friday, March 02, 2007 1:48 PM
To: TEITAC Telecommunications Subcommittee
Subject: [teitac-telecom] Template material to review before Monday's call

Dear TCC Subcommittee Members:

As we agreed on our last call, this coming Monday we will discuss changes
that we would like to see based on our discussions so far. The lion's share
of what you will see in the Template, which is linked below, has been
provided by Diane Golden. Bruce Bailey kindly posted to the Wiki.

This is just a starting point and we look for your input on next Monday's
call on what we have so far and what needs to be added.

The page is up at URL:

<http://teitac.org/wiki/Telecom_Report_2007-03-12>
http://teitac.org/wiki/Telecom_Report_2007-03-12

Thank you and talk on Monday!

Brenda Battat

Associate Executive Director

Hearing Loss Association of America (formerly SHHH)

301-657-2248 phone

301-913-9413 fax








_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg
Vanderheiden
Sent: Thursday, February 08, 2007 11:39 AM
To: 'TEITAC Telecommunications Subcommittee'
Subject: [teitac-telecom] Security and Text over IP T140







This is the security chapter from RFC 4103:



---------------------------------------------------



8. Security Considerations



All of the security considerations from Section 14 of RFC 3550 [2]

apply.



8.1. Confidentiality



Because the intention of the described payload format is to carry

text in a text conversation, security measures in the form of

encryption are of importance. The amount of data in a text

conversation session is low. Therefore, any encryption method MAY be

selected and applied to T.140 session contents or to whole RTP

packets. Secure Real-time Transport Protocol (SRTP) [14] provides a

suitable method for ensuring confidentiality.



8.2. Integrity



It may be desirable to protect the text contents of an RTP stream

against manipulation. SRTP [14] provides methods for providing

integrity that MAY be applied.



8.3. Source Authentication



There are several methods of making sure the source of the text is

the intended one.



Text streams are usually used in a multimedia control environment.

Security measures for authentication are available and SHOULD be

applied in the registration and session establishment procedures, so

that the identity of the sender of the text stream is reliably

associated with the person or device setting up the session. Once

established, SRTP [14] mechanisms MAY be applied to ascertain that

the source is maintained the same during the session.



----------------------------------------------------



RFC 4504 Sip telephony device requirements, that can be used as a general
profiling document for SIP terminals says:



4.3. Privacy



Media Encryption

Secure RTP (SRTP) [62] MAY be used for the encryption of media

such as audio, text, and video, after the keying information

has been passed by SIP signaling. Instant messaging MAY be

protected end-to-end using S/MIME.



-------------------------------------------------------------------------



This page from SNOM can be another indicator that SRTP is becoming the
default method for media encryption.

http://www.snom.com/521.html




Gregg

------------------------

Gregg C Vanderheiden Ph.D.
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848

DSS Player at http://tinyurl.com/dho6b

<http://trace.wisc.edu:8080/mailman/listinfo/>

From: BLACKLER, ELLEN (ATTSI)
Date: Mon, Mar 05 2007 12:20 PM
Subject: Re: Template material to review before Monday'scall

This is the link we are discussing

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Brenda
Battat
Sent: Friday, March 02, 2007 2:48 PM
To: TEITAC Telecommunications Subcommittee
Subject: [teitac-telecom] Template material to review before
Monday's call


Dear TCC Subcommittee Members:

As we agreed on our last call, this coming Monday we will
discuss changes that we would like to see based on our discussions so
far. The lion's share of what you will see in the Template, which is
linked below, has been provided by Diane Golden. Bruce Bailey kindly
posted to the Wiki.

This is just a starting point and we look for your input on next
Monday's call on what we have so far and what needs to be added.

The page is up at URL:

http://teitac.org/wiki/Telecom_Report_2007-03-12
<http://teitac.org/wiki/Telecom_Report_2007-03-12>

Thank you and talk on Monday!

Brenda Battat

Associate Executive Director

Hearing Loss Association of America (formerly SHHH)

301-657-2248 phone

301-913-9413 fax