<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Telephone Number System for VRS</title>
	<atom:link href="http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/</link>
	<description>POSTS ALERTS REGARDING TRS &#38; ITS RELATED ISSUES</description>
	<pubDate>Tue, 06 Jan 2009 12:20:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: edsalert</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-30370</link>
		<dc:creator>edsalert</dc:creator>
		<pubDate>Wed, 18 Jun 2008 15:58:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-30370</guid>
		<description>Bob,

Essentially all the proposals will provide REAL telephone number (TN) of which either IP or URI will ride on.   So that means the responsiblity to verify the deaf/hon rests on VRS or IP providers.   There are different ways to verify; one of verification procedure is via post card to the physical address and ask the person to use info on post card to either call or email or log in.  This is just one example.    Also, firewalls will be at the VRS providers so they can help protect y'all.   Bottom line is as u said security needs to be where deaf/hon are comfortable with.   

Ed</description>
		<content:encoded><![CDATA[<p>Bob,</p>
<p>Essentially all the proposals will provide REAL telephone number (TN) of which either IP or URI will ride on.   So that means the responsiblity to verify the deaf/hon rests on VRS or IP providers.   There are different ways to verify; one of verification procedure is via post card to the physical address and ask the person to use info on post card to either call or email or log in.  This is just one example.    Also, firewalls will be at the VRS providers so they can help protect y&#8217;all.   Bottom line is as u said security needs to be where deaf/hon are comfortable with.   </p>
<p>Ed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edsalert</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-30369</link>
		<dc:creator>edsalert</dc:creator>
		<pubDate>Wed, 18 Jun 2008 15:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-30369</guid>
		<description>Nick,

If I understand the proposals especially the NeuStar and Dash right.   VRS providers will be able to offer features that you mentioned.  We deaf and hoh will be able to choose VRS providers on the basis of features offered.   

On the telemarketeer.  It is going to be an issue.  Even though, Ten Digit Phone Number will greatly minimize the scammed calls, many businesses because they have been "burned" by the scammers, will still hang up on ANY relay calls.   So what is needed?  Probably massive advertising to business that because of new TN, scammers will be minimized will need to be done.  Also, maybe educate deaf/hoh on how to utilize VRS or IP by using different kind of announcement; example:  First tell Relay Operator or Video Interpreter NOT to announce standard introduction, instead use my announcement "Hi this is Ed Bosson calling you through xyzVRS.  May I speak to a person knowledgeable about light and tough tent?"   Or Or maybe not even use xyzvrs if u get a very good video interpreter.   

Ed B
RT Administrator</description>
		<content:encoded><![CDATA[<p>Nick,</p>
<p>If I understand the proposals especially the NeuStar and Dash right.   VRS providers will be able to offer features that you mentioned.  We deaf and hoh will be able to choose VRS providers on the basis of features offered.   </p>
<p>On the telemarketeer.  It is going to be an issue.  Even though, Ten Digit Phone Number will greatly minimize the scammed calls, many businesses because they have been &#8220;burned&#8221; by the scammers, will still hang up on ANY relay calls.   So what is needed?  Probably massive advertising to business that because of new TN, scammers will be minimized will need to be done.  Also, maybe educate deaf/hoh on how to utilize VRS or IP by using different kind of announcement; example:  First tell Relay Operator or Video Interpreter NOT to announce standard introduction, instead use my announcement &#8220;Hi this is Ed Bosson calling you through xyzVRS.  May I speak to a person knowledgeable about light and tough tent?&#8221;   Or Or maybe not even use xyzvrs if u get a very good video interpreter.   </p>
<p>Ed B<br />
RT Administrator</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deaf Network of Texas &#187; Blog Archive &#187; Telephone Number System for VRS</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29871</link>
		<dc:creator>Deaf Network of Texas &#187; Blog Archive &#187; Telephone Number System for VRS</dc:creator>
		<pubDate>Tue, 10 Jun 2008 11:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29871</guid>
		<description>[...] http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/" rel="nofollow">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bob</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29801</link>
		<dc:creator>bob</dc:creator>
		<pubDate>Mon, 09 Jun 2008 19:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29801</guid>
		<description>I have not read any of the proposals yet but wanted to say something about comment by ed above on URI vs IP.   URI are translated to IP anyways - it is the protocol that we need to look at.  For example using HTTP, sometimes the hostname is put in the header in the request.  Using URI alone won't help identify the caller or prevent scammer.  But I haven't read the proposals yet so I may be missing something.

One great way to verify caller is to use something called client verification that is part of HTTPS protocol.  A caller could go to a VRS site to sign up where caller will receive a certificate assigned to the caller.  This certificate is then installed on caller's computer in the store (for example Key Chain in OS X or Certificate Store in Windows) where the browser can load it when VRS web server requests for one.  If a scam call is made, VRS will know exactly who did it by checking the certificate used.  But of course this depends on how VRS verifies the caller's identity in the first place!

Always remember, security is as strong as the weakest link.  Also obscurity is not security :)

As a bonus to certificates, all VRS could be using a common trusted certificate service to create caller certificates.  This means certificate created by one VRS is easily usable by other VRS-es.  Tons of information can be inserted into certificate such as caller's phone number.

bob</description>
		<content:encoded><![CDATA[<p>I have not read any of the proposals yet but wanted to say something about comment by ed above on URI vs IP.   URI are translated to IP anyways - it is the protocol that we need to look at.  For example using HTTP, sometimes the hostname is put in the header in the request.  Using URI alone won&#8217;t help identify the caller or prevent scammer.  But I haven&#8217;t read the proposals yet so I may be missing something.</p>
<p>One great way to verify caller is to use something called client verification that is part of HTTPS protocol.  A caller could go to a VRS site to sign up where caller will receive a certificate assigned to the caller.  This certificate is then installed on caller&#8217;s computer in the store (for example Key Chain in OS X or Certificate Store in Windows) where the browser can load it when VRS web server requests for one.  If a scam call is made, VRS will know exactly who did it by checking the certificate used.  But of course this depends on how VRS verifies the caller&#8217;s identity in the first place!</p>
<p>Always remember, security is as strong as the weakest link.  Also obscurity is not security <img src='http://www.edsalert.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>As a bonus to certificates, all VRS could be using a common trusted certificate service to create caller certificates.  This means certificate created by one VRS is easily usable by other VRS-es.  Tons of information can be inserted into certificate such as caller&#8217;s phone number.</p>
<p>bob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29797</link>
		<dc:creator>Troy</dc:creator>
		<pubDate>Mon, 09 Jun 2008 18:19:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29797</guid>
		<description>http://fjallfoss.fcc.gov/prod/ecfs/retrieve.cgi?native_or_pdf=pdf&#38;id_document=6520012409</description>
		<content:encoded><![CDATA[<p><a href="http://fjallfoss.fcc.gov/prod/ecfs/retrieve.cgi?native_or_pdf=pdf&amp;id_document=6520012409" rel="nofollow">http://fjallfoss.fcc.gov/prod/ecfs/retrieve.cgi?native_or_pdf=pdf&amp;id_document=6520012409</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29766</link>
		<dc:creator>Troy</dc:creator>
		<pubDate>Mon, 09 Jun 2008 13:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29766</guid>
		<description>I want local numbers, not 800 numbers.</description>
		<content:encoded><![CDATA[<p>I want local numbers, not 800 numbers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29765</link>
		<dc:creator>Troy</dc:creator>
		<pubDate>Mon, 09 Jun 2008 13:50:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29765</guid>
		<description>As long as it does not require ip address, I will support any companies that will give 10 dig. numbers without following ip address.</description>
		<content:encoded><![CDATA[<p>As long as it does not require ip address, I will support any companies that will give 10 dig. numbers without following ip address.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Vera</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29756</link>
		<dc:creator>Nick Vera</dc:creator>
		<pubDate>Mon, 09 Jun 2008 12:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29756</guid>
		<description>Hi Ed,

It is good to see you in return from the hiatus. Congratulations on your receiving the honorary degree from Gallaudet University last month! 

I would love to use this system to identify the caller ID, preventable from the scammers, and direct call for hearing people to contact me. To my knowledge, CSDVRS and IP-Relay provided me these numbers for hearing people to call me. Some people hung on me because they believe the VRS that are such as telemarketers. I understand Sorenson add new feature for direct call. Do you know any of these VRS outlets that provide the same approaches? 

Nick Vera</description>
		<content:encoded><![CDATA[<p>Hi Ed,</p>
<p>It is good to see you in return from the hiatus. Congratulations on your receiving the honorary degree from Gallaudet University last month! </p>
<p>I would love to use this system to identify the caller ID, preventable from the scammers, and direct call for hearing people to contact me. To my knowledge, CSDVRS and IP-Relay provided me these numbers for hearing people to call me. Some people hung on me because they believe the VRS that are such as telemarketers. I understand Sorenson add new feature for direct call. Do you know any of these VRS outlets that provide the same approaches? </p>
<p>Nick Vera</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alfred Sonnenstrahl</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29752</link>
		<dc:creator>Alfred Sonnenstrahl</dc:creator>
		<pubDate>Mon, 09 Jun 2008 11:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29752</guid>
		<description>Ed

Good Comments.  Good rationale.  Good safeguards.  However, I am apprehensive of being in a position to select which is the best solution simply because I dont have the expertise, knowledge, and access to all information.  Are these proposals exposing ALL information?  Is there any hidden agenda among these proposals that we, inexperienced people, should be aware of before casting our preferences.

For example, are all car owners familiar with the engines?  How many gallons of gas in tank?  How many cylinders?  Impact of cylinders on performances?

Because of these unanswered questions, we, the consumers, should tell the FCC what we, the consumers, want as consumers.

We need to remember that, in this setting, there is an extremely unusual situation that needs to be looked into before any decision is to be made.  All videophones are being made by VRS providers.  Let me repeat...VRS providers manufacture their own videophones.  Videophones are being programmed by VRS companies.

For example, all VP100 and VP200 have SVRS in the listing and it cannot be removed.  It is on the top of the contact list.  It cannot be lowered.  It has an icon on the main menu.  It cannot be removed.

Should SVRS be authorized to provide numbers and customers want to switch to another VRS, how will this be done without wasting time and energy by trying to bypass the VRS provider's manufactured restrictions?

Have these proposals proposed solutions to these issues above?

In closing, we, the consumers, as Ed would say, need to keep our eyes OPEN...proactively!

Sonny</description>
		<content:encoded><![CDATA[<p>Ed</p>
<p>Good Comments.  Good rationale.  Good safeguards.  However, I am apprehensive of being in a position to select which is the best solution simply because I dont have the expertise, knowledge, and access to all information.  Are these proposals exposing ALL information?  Is there any hidden agenda among these proposals that we, inexperienced people, should be aware of before casting our preferences.</p>
<p>For example, are all car owners familiar with the engines?  How many gallons of gas in tank?  How many cylinders?  Impact of cylinders on performances?</p>
<p>Because of these unanswered questions, we, the consumers, should tell the FCC what we, the consumers, want as consumers.</p>
<p>We need to remember that, in this setting, there is an extremely unusual situation that needs to be looked into before any decision is to be made.  All videophones are being made by VRS providers.  Let me repeat&#8230;VRS providers manufacture their own videophones.  Videophones are being programmed by VRS companies.</p>
<p>For example, all VP100 and VP200 have SVRS in the listing and it cannot be removed.  It is on the top of the contact list.  It cannot be lowered.  It has an icon on the main menu.  It cannot be removed.</p>
<p>Should SVRS be authorized to provide numbers and customers want to switch to another VRS, how will this be done without wasting time and energy by trying to bypass the VRS provider&#8217;s manufactured restrictions?</p>
<p>Have these proposals proposed solutions to these issues above?</p>
<p>In closing, we, the consumers, as Ed would say, need to keep our eyes OPEN&#8230;proactively!</p>
<p>Sonny</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edsalert</title>
		<link>http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29745</link>
		<dc:creator>edsalert</dc:creator>
		<pubDate>Mon, 09 Jun 2008 09:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.edsalert.com/2008/06/09/telephone-number-system-for-vrs/#comment-29745</guid>
		<description>David B, Bob Daniel got it right. URI is the way to go to get features like caller id, video mail, etc. URI will offer opportunity for VRS providers to &#34;compete&#34; for VRS users. To strictly go by only IP address and not go thru&#160;URI will make it difficult to offer features. Also, security is best with URI - as all calls, both vp to vp and VRS calls will go thru VRS provider thus will be protected by their firewall. Fraud calls will be minimized by URI cuz everyone would need to select their preference for VRS provider and VRS providers will need to do verification that the person signing up is who they really are. With IP address, it would be nearly impossible to do that thus scammers would have a field day. eyes open and thumbs up, Ed</description>
		<content:encoded><![CDATA[<p>David B, Bob Daniel got it right. URI is the way to go to get features like caller id, video mail, etc. URI will offer opportunity for VRS providers to &quot;compete&quot; for VRS users. To strictly go by only IP address and not go thru&nbsp;URI will make it difficult to offer features. Also, security is best with URI - as all calls, both vp to vp and VRS calls will go thru VRS provider thus will be protected by their firewall. Fraud calls will be minimized by URI cuz everyone would need to select their preference for VRS provider and VRS providers will need to do verification that the person signing up is who they really are. With IP address, it would be nearly impossible to do that thus scammers would have a field day. eyes open and thumbs up, Ed</p>
]]></content:encoded>
	</item>
</channel>
</rss>
