Opened 11 years ago

Closed 11 years ago

#153 closed defect (fixed)

Dave's Review

Reported by: dthaler@… Owned by: marc.blanchet@…
Priority: major Milestone: milestone1
Component: draft-blanchet-iab-internetoverhttp Version: 1.0
Severity: Candidate WG Document Keywords:
Cc:

Description

Section 2.4:

If an organization has N different services which each normally take
a different port, then it has to use N IP addresses, one for each
service and bind the service on port 443 (or 80) on that IP address.

That doesn't follow. You can have a multiplexing layer on top of
port 80 or 443 that allows for N different services on top. Indeed
there have been many attempts at defining such layers in the past
and several of the HTTP2.0 proposals include multiplexing.
And you don't need a new version of HTTP to do it, you could define
a multiplexing subprotocol over websockets today.

Section 2.6:

Having the effect of not being able to use the best protocols for the
purpose of the application protocol.

The term "best" is subjective since there are many metrics.
(See RFC 5218...) I suspect you mean best in terms of
"Good Technical Design" metric then keep in mind what RFC 5218
says: "experience shows that good technical design has minimal
impact on initial success compared with other factors".

If you define best by "least costly" or "easiest to deploy" or
whatever else then you reach different conclusions.

Change History (2)

comment:1 Changed 11 years ago by marc.blanchet@…

"And you don't need a new version of HTTP to do it, you could define
a multiplexing subprotocol over websockets today."

agree, (and will add some text about it). but I was talking about current-deployed-already-available services (i.e. http, jabber, sip, smtp, ...), that require a specific port by itself. One of the (conclusion) point of the draft that I was trying to make was exactly your statement: should we define (and redefine) all protocols over http (for example using web sockets). So I think we agree on the conclusion. That section was more "what is happening today without web sockets, with currently defined protocols/services".

The term "best" is subjective since there are many metrics.

ok. will be changed to something better.

comment:2 Changed 11 years ago by marc.blanchet@…

  • Resolution set to fixed
  • Status changed from new to closed

integrated in the -00 posted. Please open a new ticket if other comments or comments not addressed.

Note: See TracTickets for help on using tickets.