[ogf nmc-base svn commit] r16 - /
Author: macfreek Date: 2010-03-15 04:04:44 -0500 (Mon, 15 Mar 2010) New Revision: 16 Modified: chain.eps chain2.eps exchange.dia exchange.eps exchange2.dia exchange2.eps exchange3.dia exchange3.eps filter.eps flow.eps introduction.tex motivation.tex nmc-base.pdf Log: Second some textual changes to introduction and motivation. - Improved figure 2, it tries to convey the concept that a node can be both a client and a server. It now explicitly shows both exchanges. - removed SHOULD/MUST requirements that refer to this document itself. (e.g. "This document MUST define ...."). I found this confusing to read: DOES the document define this, or SHOULD it do so, but does not (yet) do so? Modified: chain.eps =================================================================== (Binary files differ) Modified: chain2.eps =================================================================== (Binary files differ) Modified: exchange.dia =================================================================== (Binary files differ) Modified: exchange.eps =================================================================== (Binary files differ) Modified: exchange2.dia =================================================================== (Binary files differ) Modified: exchange2.eps =================================================================== (Binary files differ) Modified: exchange3.dia =================================================================== (Binary files differ) Modified: exchange3.eps =================================================================== (Binary files differ) Modified: filter.eps =================================================================== (Binary files differ) Modified: flow.eps =================================================================== (Binary files differ) Modified: introduction.tex =================================================================== (Binary files differ) Modified: motivation.tex =================================================================== (Binary files differ) Modified: nmc-base.pdf =================================================================== (Binary files differ)
Freek **finally** committed:
- Improved figure 2, it tries to convey the concept that a node can be both a client and a server. It now explicitly shows both exchanges.
Forgot to mention, I changed the name beneath the picture to the role. Please compare the figure 2 in previous version and this one. To me this is more clear, but please check (maybe this is just my weird brain).
- removed SHOULD/MUST requirements that refer to this document itself. (e.g. "This document MUST define ...."). I found this confusing to read: DOES the document define this, or SHOULD it do so, but does not (yet) do so?
What is not clear to me if this section tries to only define how *this* document must look look, or if it also defines how derivate document must look like. In the first case, I like to change this text to describe how this document looks like rather then how it SHOULD look like. In the second case, I wonder if this should be in a protocol definition document (like this), since it is more of a procedural requirement. I will commit my changes to section 4 in a not-so-distance future (perhaps even sometime before the sun collapses...) Regards, Freek
participants (2)
-
Freek Dijkstra -
svn＠ogf.org