RE: TBTF: A small Doodle of an HTTP Binding

Just a quick comment regarding your note:

	Note: I have a concern with Henrik's suggestion that
	"A binding [binding specification?...NRM] may define
	a set of properties." [4]  In my opinion, the properties
	are defined by our specification (for core functions)
	and by the specifications for various modules (e.g.
	security) and message patterns.  This is a very
	fundamental distinction. 

I believe this is supported in the model that I propose through nesting.
People who want to expose the same properties can do so by either nest
or use properties defined by other parties. I don't think there is any
need for a general interface model.

Henrik