Ben,
On 28 June 2015 at 16:05, Stephen Kent<[email protected]> wrote:
IETF standards need to be unambiguous. Code is very helpful, but it is not a
substitute
for a rigorous description of how to resolve the issue that Onderj raised.
Whilst I am not necessarily opposed to that, there has to be a point
at which you stop explaining what can be worked out given existing
information. The RFC does state how the hash is calculated, from which
it is clear what the placement of each node is in the hash
calculation.
My comment is based on the question that was posed by someone for
whom it was not clear. If most other (independent) implementers find
the text clear enough, OK.
Citing a tech paper is not the preferred approach for IETF docs. We
often reproduce info that is available via other means, so that RFCs
are as self-contained as possible.
Steve
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
