<?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: Convergence versus common-carrier principles</title>
	<atom:link href="http://lirneasia.net/2007/09/convergence-versus-common-carrier-principles/feed/" rel="self" type="application/rss+xml" />
	<link>http://lirneasia.net/2007/09/convergence-versus-common-carrier-principles/</link>
	<description>LIRNEasia</description>
	<pubDate>Thu, 04 Dec 2008 07:31:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: samarajiva</title>
		<link>http://lirneasia.net/2007/09/convergence-versus-common-carrier-principles/#comment-9250</link>
		<dc:creator>samarajiva</dc:creator>
		<pubDate>Fri, 28 Sep 2007 06:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.lirneasia.net/2007/09/convergence-versus-common-carrier-principles/#comment-9250</guid>
		<description>The content provisions of the common carrier doctrine apply to point-to-point messages.   It is important to distinguish between point-to-point and point-to-multipoint (or broadcast).

Here, the messages are actually point-to-point, in that the recipient has registered.  The fact that they are sent simultaneously and not sequentially does not make them broadcasts.  When point-to-point messages are transmitted without consent they used to be called nuisance calls; many countries have laws against them.

In broadcast (including cell broadcast, a mobile functionality that we are studying for disaster warnings), there is no consent.

If I want to receive a message and the only way to receive it is through the use of the number that I use, the phone company has no business getting in the middle.

Distinguished from this are broadcast messages, where the recipient has not requested them.   There, it is important that the phone company provide the recipient with the means to prevent undesirable messages from coming in.</description>
		<content:encoded><![CDATA[<p>The content provisions of the common carrier doctrine apply to point-to-point messages.   It is important to distinguish between point-to-point and point-to-multipoint (or broadcast).</p>
<p>Here, the messages are actually point-to-point, in that the recipient has registered.  The fact that they are sent simultaneously and not sequentially does not make them broadcasts.  When point-to-point messages are transmitted without consent they used to be called nuisance calls; many countries have laws against them.</p>
<p>In broadcast (including cell broadcast, a mobile functionality that we are studying for disaster warnings), there is no consent.</p>
<p>If I want to receive a message and the only way to receive it is through the use of the number that I use, the phone company has no business getting in the middle.</p>
<p>Distinguished from this are broadcast messages, where the recipient has not requested them.   There, it is important that the phone company provide the recipient with the means to prevent undesirable messages from coming in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy</title>
		<link>http://lirneasia.net/2007/09/convergence-versus-common-carrier-principles/#comment-9251</link>
		<dc:creator>Amy</dc:creator>
		<pubDate>Thu, 27 Sep 2007 20:38:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lirneasia.net/2007/09/convergence-versus-common-carrier-principles/#comment-9251</guid>
		<description>Would common carriage doctrine continue to apply to mass text messages sent from the internet to groups - using txtmob or twitter or other texting broadcast applications? Does the one to many, rather than one to one, alter the principle?</description>
		<content:encoded><![CDATA[<p>Would common carriage doctrine continue to apply to mass text messages sent from the internet to groups - using txtmob or twitter or other texting broadcast applications? Does the one to many, rather than one to one, alter the principle?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
