DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
11 Monitoring and Observability Tools for 2023
Learn more
  1. DZone
  2. Coding
  3. Languages
  4. Working Group Takes Aim at HTTP/2.0

Working Group Takes Aim at HTTP/2.0

Chris Smith user avatar by
Chris Smith
·
Jan. 25, 12 · Interview
Like (0)
Save
Tweet
Share
4.19K Views

Join the DZone community and get the full member experience.

Join For Free
Mark Nottingham, author of the Atom Syndication Format and former chair of both IETF and W3C Working Groups, has now set his sights on creating the next HTTP spec with the HTTP Working Group.  When the group was first formed, the idea was to improve the existing standard of HTTP/1.1 due to limited implementer support and a desire to improve interoperability and security.  However, as Nottingham points out:

That's clearly changed in the intervening time; two major browsers have implemented SPDY, a non-textual serialisation of HTTP's semantics, and there are now several other implementations as well (full disclosure: including an experimental one in Python by yours truly).

-- Mark Nottingham

While there seems to be genuine excitement surrounding the possibility of an improved HTTP format, there is also concern that the opportunity to improve will create the desire to completely redesign.

James Snell's response appears to be a common one:

Would love to see that work move forward within this group. I do have concerns about keeping the scope focused, however. Even though the door would be opened to the possibility of new features being introduced, there is obvious danger in opening those doors too wide. I strongly feel that things such as the introduction of new request methods and new header fields, unless there is clear and irrefutable evidence of their general utility within the core of the spec, should continue to be pursued as they are today -- within separate I-D's as extensions to the core protocol. The charter should make it absolutely clear that the goal is an incremental evolution of HTTP/1.1 rather than an opportunity for radical changes.

-- James Snell

Nottingham has set a list of Goals and Milestones for the group to achieve before Submitting HTTP/2.0 to IESG:

Goals and Milestones:

  • Done        First HTTP/1.1 Revision Internet Draft
  • Done        First HTTP Security Properties Internet Draft
  • Feb 2012    Working Group Last Call for HTTP/1.1 Revision
  • Feb 2012    Working Group Last Call for HTTP Security Properties
  • Apr 2012    Submit HTTP/1.1 Revision to IESG for consideration as a
    Proposed Standard
  • Apr 2012    Submit HTTP Security Properties to IESG for consideration as
    Informational RFC
  • May 2012    First HTTP/2.0 Internet Draft
  • May 2013    Request Last Call for HTTP/2.0
  • Jul 2013    Submit HTTP/2.0 to IESG for consideration as a Proposed
    Standard
-- Mark Nottingham

It will be interesting to keep an eye on the group's progress over the next year and half.  For more information, be sure to visit here.


Source: http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0098.html
security Property (programming) Internet (web browser) Mark (designation) Clear (Unix) Requests Milestone (project management) Python (language)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Container Security: Don't Let Your Guard Down
  • File Uploads for the Web (1): Uploading Files With HTML
  • Keep Your Application Secrets Secret
  • Journey to Event Driven, Part 1: Why Event-First Programming Changes Everything

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: