This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9223 - It is unlikely this will work on mobile as you cannot make tcp connections into a mobile phone. They will be blocked by the operator's firewall and this is very unlikely to change. Of course, this isn't a reason not to specify this, but it's good to be aw
Summary: It is unlikely this will work on mobile as you cannot make tcp connections in...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-10 12:55 UTC by contributor
Modified: 2011-05-10 01:03 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-03-10 12:55:49 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#devices

Comment:
It is unlikely this will work on mobile as you cannot make tcp connections
into a mobile phone. They will be blocked by the operator's firewall and this
is very unlikely to change. Of course, this isn't a reason not to specify
this, but it's good to be aware that it will not work for a very large class
of devices.

Posted from: 74.125.57.49
Comment 1 Ian 'Hixie' Hickson 2010-03-30 22:59:15 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: no change made (no change requested)
Rationale: Yeah. The same problem actually exists with home networks that use NAT (many of them). The solution is some form of NAT traversal. This is all a subject for another spec that this spec can rely on, though (hopefully something for the IETF).
Comment 2 Ian 'Hixie' Hickson 2011-05-10 01:03:00 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: no spec change
Rationale: Ok, the spec is now updated to use ICE which should help with this as much as we practically can.