On 23/05/2017 10:40, Adam Roach wrote:
...
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> The document includes a couple of instances of "reasonable" in normative
> statements (e.g., "reasonable timeout"). I would strongly recommend
> having specific recommendations in the document where this happens.
Yes, will do.
> The CBOR definition has constants for IP_PROTO_TCP and IP_PROTO_UDP, but
> no way to register additional values with IANA. This does not seem
> future-proof.
Separate message to follow.
> Section 3.8.4 talks about behavior when a node has a "globally unique
> address," but provides no guidance for detecting this. Are nodes expected
> to check for link-local, zeroconf, RFC 1918, and RFC 6598 addresses? Any
> others?
Think IPv6, where this is quite well defined. The trouble is that it's
not well supported in the socket API. I think the best we can say in
the text is that it's implementation dependent.
(To find the code for this in the prototype, search for the comment
"This is a hack.")
We did want to write the text independent of the IP version as far
as possible, but trying to do this bit in IPv4 would be masochism.
Regards,
Brian
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
