Re: [nvo3] Rtgdir early review of draft-ietf-nvo3-encap-07

[Michael Richardson <[e-mail]>]

Donald Eastlake <[e-mail]> wrote:
    > If it is reasonable for something to be retained as "a record for
    > future reference" then, in my opinion, it follows that it is a
    > plausible candidate for publication as an RFC, likely an Informational
    > RFC, which is the category shown on the title page of this draft.

The IESG has declined to publish use case documents and pushed back on a lot
of things.  It's no longer 1992 :-)
But, as a record for decision making, I don't think that the document does a
good job.

    >> Major Issues:
    >>
    >> The document jumps right into comparing the three protocols.

    > Given that the purpose of the draft is to cover the comparison of the
    > protocols and selection of one, what sort of material do you think
    > should appear before the comparisons?

Maybe (from memory):
  1) establish the basis of comparison
  2) the environment in which things are targetted
  3) a bit more about why each protocol is the way it is.
  4) why converge at all.

    >> The deficiencies of each protocol are very briefly noted.
    >> No diagrams or extracts of the relevant protocols are included to help a
    >> reader understand the deficiencies.
    >>
    >> Few readers are likely to have a deep understanding of all three, so some
    >> contrasting pictures would be helpful.

    > Some such diagrams could be added.

Thank you.

    >> The two major issues with GENEVE (can be longer than 256 bytes, has a hard to
    >> parse in hardware TLV structure) are identified.  But the document seems to
    >> conclude on GENEVE, without explaining why those major issues are not issues,
    >> or how they would be mitigated.

    > Jon Hudson responded to this point and something along the lines of
    > his answer could be incorporated into the draft.

I am not privvy to such a thread.
That's why I'm an external reviewer.


--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide