Re: WGLC for draft-ietf-dmm-ondemand-mobility-08 --

rOn Fri, Dec 9, 2016 at 3:59 AM, Dave Dolson <[email protected]> wrote:

> 5. Are there new errors from bind(), listen() or connect(), etc.?
>
> E.g., socket option is FIXED, but user explicitly specified a COA address
> to bind to?
>

+1. An implementer would probably choose to return EADDRNOTAVAIL if an API
requested a type of address that is not available, but the draft makes no
mention of that.

The draft also fails to mention which of the APIs will result in a request
to the network (which can block for a long period of time) and which will
not. It will be quite unexpected to app developers if system calls such as
bind() and setsockopt(), which always return immediately, can suddenly
block for whole seconds. It would also be highly unexpected if connect() on
a UDP socket took a long time since it currently returns immediately.

I don't think it's a good idea to overload these existing system calls with
new "obtain an prefix from the network" semantics. It's better to add a new
system call for that.

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm