Status
| SPDY | |
| Stage | Development |
| Status | In progress |
| Release target | Firefox 11 |
| Health | At risk |
| Status note | Reviews underway. We are still aiming to get this in for FF10 (pref'd off) we need to land NPN support for NSS. The later should land within the next week. If we do get close, we may push this into FF11. |
{{#set:Feature name=SPDY
|Feature stage=Development |Feature status=In progress |Feature version=Firefox 11 |Feature health=At risk |Feature status note=Reviews underway. We are still aiming to get this in for FF10 (pref'd off) we need to land NPN support for NSS. The later should land within the next week. If we do get close, we may push this into FF11. }}
Team
| Product manager | Chris Blizzard |
| Directly Responsible Individual | Josh Aas |
| Lead engineer | Pat McManus |
| Security lead | Curtis Koenig |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Ioana Budnar |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Chris Blizzard
|Feature feature manager=Josh Aas |Feature lead engineer=Pat McManus |Feature security lead=Curtis Koenig |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Ioana Budnar |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
SPDY is a transport protocol designed as a successor to HTTP as part of Google's make the web faster initiative. It is currently supported in google chrome, on most google web services, in the contendo and strangeloopnetworks CDNs, and will be used by the amazon silk tablet browser.
2. Users & use cases
Users of high latency environments such as mobile should be improved page load times for pages with many resources.
Casual browsing will be more secure with respect to eavesdropping.
Servers should see reduced load.
Independent low latency traffic should see reduced queuing delays.
3. Dependencies
Because all of SPDY runs on SSL, having SSL False Start done would be helpful:
https://bugzilla.mozilla.org/show_bug.cgi?id=658222
Also requires NPN support:
https://bugzilla.mozilla.org/show_bug.cgi?id=547312
4. Requirements
Interoperate with other spdy/2 implementations using high levels of concurrency.
Non-goals
SPDY over non-ssl.
Stage 2: Design
5. Functional specification
A SPDY implementation will wrap the existing HTTP implementation as a sort of in-browser proxy. This preserves all of the existing HTTP semantics and tools (e.g. firebug), while leveraging the on-the-wire benefits of SPDY.
6. User experience design
`
Stage 3: Planning
7. Implementation plan
https://bugzilla.mozilla.org/show_bug.cgi?id=528288
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=SPDY is a transport protocol designed as a successor to HTTP as part of Google's make the web faster initiative. It is currently supported in google chrome, on most google web services, in the contendo and strangeloopnetworks CDNs, and will be used by the amazon silk tablet browser. |Feature users and use cases=Users of high latency environments such as mobile should be improved page load times for pages with many resources.
Casual browsing will be more secure with respect to eavesdropping.
Servers should see reduced load.
Independent low latency traffic should see reduced queuing delays. |Feature dependencies=Because all of SPDY runs on SSL, having SSL False Start done would be helpful:
https://bugzilla.mozilla.org/show_bug.cgi?id=658222
Also requires NPN support:
https://bugzilla.mozilla.org/show_bug.cgi?id=547312 |Feature requirements=Interoperate with other spdy/2 implementations using high levels of concurrency. |Feature non-goals=SPDY over non-ssl. |Feature functional spec=A SPDY implementation will wrap the existing HTTP implementation as a sort of in-browser proxy. This preserves all of the existing HTTP semantics and tools (e.g. firebug), while leveraging the on-the-wire benefits of SPDY. |Feature ux design=` |Feature implementation plan=https://bugzilla.mozilla.org/show_bug.cgi?id=528288 |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Platform |
| Secondary roadmap | ` |
| Feature list | Platform |
| Project | Responsiveness |
| Engineering team | Networking |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=Platform |Feature secondary roadmap=` |Feature list=Platform |Feature project=Responsiveness |Feature engineering team=Networking }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | sec-review-complete | Notes |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | Signed off | Test Plan |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-complete |Feature security health=OK |Feature security notes=Notes |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=Signed off |Feature qa notes=Test Plan |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}