<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 22/04/2010 5:11 PM, Daniel Hooper wrote:
<blockquote
cite="mid:8567621549F91A4B8AC810FFF582CB534E1BA94F47@mx5.team.emerge.net.au"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#002060;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">“</span>but
will be forced
to travel all the way out to an interconnect point and through RSP1,
then be
handed over to RSP2”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That’s just the nature of the beast, if factory
#1 was
really serious about exchanging large volumes of traffic to the
premises next
door wouldn’t they be eligible to purchase a layer2 style of service
from
an RSP? I haven’t seen any thing so far that mandates that providers
must
only sell layer3 services. Surely the RSP could apply for a VLAN to be
mapped
between port X on customers ONT and mapped to another port on another
ONT?</p>
</div>
</blockquote>
<br>
NBNCo won't sell a VLAN directly between two ONT ports to build an
end-to-end service. NBNCo's services are all ONTport-to-POI.<br>
<br>
But I agree thats the nature of the beast, its exactly what happens now
when two locations are connected to two different providers - or even
to the same provider. If factory#1 was serious about large data volumes
to a location nearby they would find a local carrier to dig some fibre
or establish a microwave link directly between the two buildings, and
bypass the NBN connection. Just because a building is connected to the
NBN doesn't mean thats ALL they can be connected to.<br>
<br>
The argument is an example to highlight a concept of "efficiency". My
belief is that strict efficiency in terms of shortest-geographic-path
is a concept that is largely out the window and immaterial. We don't
care about efficient routing of telephone calls these days, its all
about least-cost not shortest-path - I can call the person next door
and have the call routed around the planet a couple of times, and I
don't care as long as the audio quality is OK. With ubiquitous fibre
infrastructure leading to almost unlimited bandwidth in practical
terms, the only effect from non-shortest-path traffic flows that the
end-user expriences is a few millisecs of latency - if this causes
capacity issues for the provider, than the provider has to find a way
around it by finding a more optimal path, or possibly finding a longer
but cheaper path so they can afford more capacity - either way, the
argument that traffic between two locations that are next door to each
other shouldn't ever flow beyond the end of the street doesn't hold in
my view.<br>
<br>
Paul.<br>
<br>
</body>
</html>