domstat.net

Website loading time

during the test: 2.51 s

cable connection (average): 3.24 s

DSL connection (average): 3.97 s

modem (average): 42.61 s

HTTP headers

HTTP/1.0 200 OK

Content-Type: text/html; charset=UTF-8

Expires: Sat, 15 Oct 2011 21:39:18 GMT

Date: Sat, 15 Oct 2011 21:39:18 GMT

Cache-Control: private, max-age=0

Last-Modified: Sat, 15 Oct 2011 19:45:37 GMT

ETag: "45b09e9d-b8e9-43ba-ab6f-facdcf0ff685"

X-Content-Type-Options: nosniff

X-XSS-Protection: 1; mode=block

Server: GSE

Information about DNS servers

Received from the first DNS server

Request to the server "disruptivewireless.blogspot.com"
You used the following DNS server:
DNS Name: ns2.hostmonster.com
DNS Server Address: 69.89.16.8#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 54522
flag: qr rd ra REQUEST: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

REQUEST SECTION:
disruptivewireless.blogspot.com. IN ANY

ANSWER SECTION:
disruptivewireless.blogspot.com. 3600 IN CNAME blogspot.l.google.com.

AUTHORITY SECTION:
blogspot.com. 300198 IN NS ns4.google.com.
blogspot.com. 300198 IN NS ns3.google.com.
blogspot.com. 300198 IN NS ns2.google.com.
blogspot.com. 300198 IN NS ns1.google.com.

SECTION NOTES:
ns1.google.com. 245673 IN A 216.239.32.10
ns2.google.com. 245667 IN A 216.239.34.10
ns3.google.com. 245666 IN A 216.239.36.10
ns4.google.com. 245668 IN A 216.239.38.10

Received 217 bytes from address 69.89.16.8#53 in 141 ms

Received from the second DNS server

Request to the server "disruptivewireless.blogspot.com"
You used the following DNS server:
DNS Name: ns1.hostmonster.com
DNS Server Address: 74.220.195.131#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 33558
flag: qr rd ra REQUEST: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

REQUEST SECTION:
disruptivewireless.blogspot.com. IN ANY

ANSWER SECTION:
disruptivewireless.blogspot.com. 3600 IN CNAME blogspot.l.google.com.

AUTHORITY SECTION:
blogspot.com. 307365 IN NS ns4.google.com.
blogspot.com. 307365 IN NS ns1.google.com.
blogspot.com. 307365 IN NS ns3.google.com.
blogspot.com. 307365 IN NS ns2.google.com.

SECTION NOTES:
ns1.google.com. 245730 IN A 216.239.32.10
ns2.google.com. 245722 IN A 216.239.34.10
ns3.google.com. 245727 IN A 216.239.36.10
ns4.google.com. 245724 IN A 216.239.38.10

Received 217 bytes from address 74.220.195.131#53 in 141 ms

Subdomains (the first 50)

Typos (misspells)

Location

IP: 209.85.175.132

continent: NA, country: United States (USA), city: Mountain View

Website value

rank in the traffic statistics:

There is not enough data to estimate website value.

Basic information

website build using CSS

code weight: 280.72 KB

text per all code ratio: 16 %

title: Dean Bubley's Disruptive Wireless

description:

keywords:

encoding: UTF-8

language: en

Website code analysis

one word phrases repeated minimum three times

two word phrases repeated minimum three times

three word phrases repeated minimum three times

B tags

Small-group collaborative workshops.Next events: US East Coast, Autumn 2011

Social networking

Travel/transport

Connectivity

EDIT 1am 6/10/11: RIP Steve Jobs

U tags

I tags

Small-group collaborative workshops.Next events: US East Coast, Autumn 2011

Up to now, there is no existing standard or de facto standard for Connection Managers.  Operators and OEM/ODM have to develop and use different and dedicated solutions, thus increasing the effort and time to market.

For Mobile Broadband devices, this situation is critical and leading to a strong effort for service providers to develop connection manager applications as there are already several networks to support and any new mobile broadband device such as USB modem requires to redevelop existing connection managers to be implemented and supported by these applications.

For smartphones or tablets, the importance of management of Wi-Fi offloads for example and/or the need to expose information status on the connection to applications is requiring a solution through the connection manager application.

Furthermore, new fast growing businesses such as Connected Devices & M2M are facing the same hurtles and will need as well a solution to reduce the impacts and efforts to deal with the connection management aspects."

"The OpenCMAPI enabler SHALL be configured to use the operator defined list of preferred SSID preconfigured in the device and/or the WSID (Wlan Specific Identifier) list in accordance with [3GPP TS 24.234] if present in the SIM/RUIM/NAA on UICC"

"The OpenCMAPI enabler SHALL be able to force the association on a SSID, visible or not"

"The OpenCMAPI enabler SHALL be able to modify or delete only WiFi profile that are not predefined by the operator"

"The OpenCMAPI enabler SHALL allow the user or the application using the Open CMAPI to connect to Known network or Unknown network manually"

very

If you don't understand fixed ethernet, then you have no business doing anything with the wireless version either

Is that all? It's the same device with a better camera and that voice recognition thingy. Where's our big screen, our NFC, our LTE - what happened to all the leaked designs and mockups of cases for a new device?

Why did it take them so long to do this, surely this isn't 16 months work, these changes are minor

[Note: it's more important to add UMTS to CDMA than vice-versa for outbound roaming, although I'm sure Vodafone likes the idea of being able to roam onto Verizon]

Edit: there's also a chance Apple will do something truly disruptive with its LTE implementation, and move to a full dual-radio SVLTE approach, keeping telephony on circuit-based radio connections rather than relying on VoIP on LTE or the uber-clunky, worse-than-useless circuit-switched fallback option. Interestingly, Huawei has now started floating dual-radio as a possible option (ZTE has for some time).

Hat-top to Zahid for spotting this, I'll follow up another time in depth - and it's also covered in the Future of Voice workshops' section on LTE.

images

headers

H1

H2

Future of Voice: Taking Voice beyond Ordinary Telephony

Wednesday, October 12, 2011

Monday, October 10, 2011

Wednesday, October 05, 2011

Follow by Email

REPORT: Why IMS RCS will fail as a massmarket service

Twitter

NEW THOUGHT LEADERSHIP PAPER: Top 10 Technologies for Mobile Broadband Traffic Management

NEW REPORT: Fixed and Mobile Broadband Business Models

Subscribe To

Disruptive Analysis Workshops

Dean Bubley's upcoming conferences & events

Want to hear some Disruption? Dean Bubley can speak at your event

Consultancy Services

Followers

Syndication

About Me

I'd recommend.....

Blog Archive

Analytics

H3

Future of Voice: Taking Voice beyond Ordinary Telephony

Wednesday, October 12, 2011

Monday, October 10, 2011

Wednesday, October 05, 2011

Follow by Email

REPORT: Why IMS RCS will fail as a massmarket service

Twitter

NEW THOUGHT LEADERSHIP PAPER: Top 10 Technologies for Mobile Broadband Traffic Management

NEW REPORT: Fixed and Mobile Broadband Business Models

Subscribe To

Disruptive Analysis Workshops

Dean Bubley's upcoming conferences & events

Want to hear some Disruption? Dean Bubley can speak at your event

Consultancy Services

Followers

Syndication

About Me

I'd recommend.....

Blog Archive

Analytics

H4

H5

H6

internal links

external links