Opened 11 years ago

Closed 11 years ago

#151 closed defect (fixed)

Hannes' Review

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


Hi Marc,

here are a few additional remarks:
(my comments are inserted with ">")

2.1 Trafic Policing

if all trafic is over one or two ports, then no easy way to
differentiate delay sensitive trafic to bulk trafic.

I believe you have to state here how you envision the quality of service mechanisms to work.

2.2 Deploying New Protocols

If port 80 and 443 are the only ports open, then given that
middleboxes in networks are inspecting packets and validate HTTP
trafic, then a new protocol requiring a different transport port is
not deployable.

There are two aspects in the list of items here:

1) What circumstances in the environment require HTTP-based protocol designs?
Item 2.2 falls under that category.

2) What are the implications from running everything on top of HTTP?
Item 2.1 falls under item 2.1.

I believe you will have to separate the two aspects into separate lists.
Maybe start with (1) and then explain (2). This would require a document restructuring.

2.3. Overloading HTTP

HTTP was defined with a specific limited set of requirements

HTTP is a very generic protocol that has been extended to support other communication models, see WebSockets?.

So, you will have to be a bit more specific what you mean by overloading or what you consider to be outside of HTTP.

I still believe that the "everything over HTTP" is really not the important aspect that keeps the development going but rather the usage of JavaScript?. We may quite likely see very different design with HTTP 2.0 but JavaScript? will not go away (unless it gets replaced by something like Dart).

2.4. Increasing the rate of usage of IP addresses

I did not got the point here. Are you saying that running everything over HTTP will require more IP addresses? How is that?

2.5. More Complex Operations

Here the question is how you do network monitoring. You do not describe the architecture you assume and therefore I cannot tell you whether this is correct or not.

2.6. Inability to Deploy Applications and Protocols

What is the best protocol depends on the assumptions you work with. If you consider it better not to have your IP camera working at all (like it happened with earlier VoIP software that couldn't get through NATs) then maybe some other protocols are better.

2.7. Applications Become Only HTTP-based

I would omit this point since it does not say a lot but there is also the issue to consider that not all applications use HTTP. For example, if you think about the efforts ongoing on in the CORE WG where a UDP-based HTTP variant is defined for Internet of Things. Then, there are also areas where HTTP has not be used - think about the routing protocols. Also think about server-to-server communication where there is not necessarily the same limitation regarding firewall and NAT traversal present.

2.8. Applications Need to Become Very Smart for Opening Connection

This a correct observation but again this has been going on for a while. We have ICE (as a generic NAT / firewall traversal mechanism) and also the IP guys have defined their protocol to test paths -- REAP.

2.9. Should IETF Protocols Only Use HTTP Encapsulation

Here the post-standardization I had sent to you earlier kicks in. There is more than just carrying data over HTTP but in many cases you want to make use of HTTP-based features. This would then argue for a REST-based design.

  1. Mitigation

IPv6 does not mitigate the problems since the problems are not only about NAT traversal. The problems also exist with firewalls, which will less likely to disappear. Additionally, the transition to IPv6 seems to increase NATs and so it actually make it works. So, I would drop this section.

Change History (1)

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

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

most comments were 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.