LLU: Bitstream gets a launch date

[BGE]

Is the bitstream access reliant on Telkom's MSAN node roll-out? Certainly hope not, else it's going to take forever!

 

[Kosmik]

RPM please do an article explaining how the bitstream system will work vs the IPC system and how this will affect the ISP service offerings as well as the price breakdown - i.e. how does this affect the ADSL line rental side as well as the ISP side. Please also get technical in terms of the equipment - old exchanges vs new and so forth.

+1. Great idea!

 

[MickeyD]

Is the bitstream access reliant on Telkom's MSAN node roll-out?

No.

 

[ToxicBunny]

Yeah.. an article talking about the differences for the ISP and for the consumer would be great actually

If it means lower costs for me as a consumer I'm keen as beans for this.

 

[zamicro]

So IPv6 will finally start to be usable in SA.

 

[Roman4604]

Yeah.. an article talking about the differences for the ISP and for the consumer would be great actually

I think that would be a bit premature. As mentioned above, today the term bitstream is a concept, a high level framework indicating where in the incumbent's network access seekers would interconnect.

There is no standard specification for the technical nature of this type of interconnection, as DSL access technology has evolved/changed so much from the time when bitstream was envisaged. Today there are many diverse technical solutions possible for achieving the intent of bitstream.

So before there can be any talk of impacts/benefits for the industry & market, the specification of what bitstream means in the SA context going forward needs to be defined. Let's hope the working group gets cracking at their workings, otherwise that new deadline may be in doubt.

 

[Bern]

@ Roman4604

Maybe an article on the various technical options then so we can get an idea of what is on the cards from Telkom and the ISPs point of view. It might allow us to make a few comments/suggestions to ensure the best composition of the product.

 

[j4ck455]

I think that would be a bit premature. As mentioned above, today the term bitstream is a concept, a high level framework indicating where in the incumbent's network access seekers would interconnect.

There is no standard specification for the technical nature of this type of interconnection, as DSL access technology has evolved/changed so much from the time when bitstream was envisaged. Today there are many diverse technical solutions possible for achieving the intent of bitstream.

So before there can be any talk of impacts/benefits for the industry & market, the specification of what bitstream means in the SA context going forward needs to be defined. Let's hope the working group gets cracking at their workings, otherwise that new deadline may be in doubt.

Prior to ICASA's public LLU hearings last year, there were ISPs saying that Telkom had already embarked on an implementation of what Telkom considered to be Bitstream.

I would be very surprised if Telkom doesn't just tell ICASA, "this" is the Bitstream implementation on the table - it's Telkom's way or the eTolled highway.

 

[Roman4604]

I would be very surprised if Telkom doesn't just tell ICASA, "this" is the Bitstream implementation on the table - it's Telkom's way or the eTolled highway.

Suppose it depends on how forceful ICASA want to be, either prescribe based on overseas markets (dictate) or just endorse what Telkom propose (facilitate)?

Although there are probably quite a few ways to do it, my understanding is there are only two practical options; layer 3 using the IPStream architecture, or layer 2 using some sort of QinQ VLANing on their MetroE access rings. There are pros and cons both, my guess we'll land up with IPStream but who knows, really depends on the capabilities of the equipment Telkom has deployed?

 

[j4ck455]

Suppose it depends on how forceful ICASA want to be, either prescribe based on overseas markets (dictate) or just endorse what Telkom propose (facilitate)?

Although there are probably quite a few ways to do it, my understanding is there are only two practical options; layer 3 using the IPStream architecture, or layer 2 using some sort of QinQ VLANing on their MetroE access rings. There are pros and cons both, my guess we'll land up with IPStream but who knows, really depends on the capabilities of the equipment Telkom has deployed?

I haven't got a clue as far as the technicalities go, but if you had to hazard a guess, which option do you think the big ISPs (like MWEB) would prefer to have implemented and which option would be the most flexible in terms of product offerings and future innovation?

 

[Roman4604]

I haven't got a clue as far as the technicalities go, but if you had to hazard a guess, which option do you think the big ISPs (like MWEB) would prefer to have implemented and which option would be the most flexible in terms of product offerings and future innovation?

Too early to tell, as they say "the devils in the detail". My personal guess, if its a trade off between the layer 2 approach's flexibility & control (more scope for innovation) and the layer 3 one's greater reach, I'd go with the latter. Broadband is essentially a numbers game.

I do think whichever option(s) is chosen, it will be expensive. ISPs will have to commit to sizable upfront expenditure for the longer term differentiation & costing gains. Anyone expecting the benefits to flow through to the end-user market in a rapid manner will probably be dissapointed.

 

[ToxicBunny]

I do remember people mentioning before that Telkoms "current" BitStream type product that they're testing atm, is a form of IPStream technology.

 

[Roman4604]

I do remember people mentioning before that Telkoms "current" BitStream type product that they're testing atm, is a form of IPStream technology.

Well it all depends where ICASA wants to take this process.

By the strictest (original) definitions IPStream is not really bitstream, but in the modern packet based world its close enough from a practical perspective. The jist of it is that the original (packetised) bitstream generated by the subscriber's CPE device is presented to the ISP unaltered (incl session/protocol headers), which is not currently the case with IPConnect.