On 24/07/2018 01:21, Tommy Pauly wrote:
Picking this thread up again, I would like to see us incorporate IPv6 address
selection into a post-sockets API model.
Here's a straw man proposal of how we can expose this via the TAPS Interface:
- A new property for Local Address Preference, which can be a tuple of:
1. Stable/Public
2. Temporary/Private
3. Unique For Connection
- Listeners would default to (1). Connections would default to (2)
- If you specify (3), the system will try to get an entirely new IPv6 address
that has never been used before
- You can find out the address you used on your Listener/Connection
This type of API would allow us to add in the functionality Erik had asked for,
to allow a client to be able to request a new address. The other alternative
would be to have some out-of-band API to request a new API, but I think marking
this on a connection is preferable, since it allows us to enforce this per-path
and per-protocol even.
What do people think?
Looks good, especially if it's not actually tied to IPv6, i.e. if you
delete "IPv6" in the two places it occurs above. (I realise this is an
IETF group and IETF has nailed its colours to the IPv6 mast, but it
would be good if TAPS could be more widely applicable than just over the
Internet, e.g. between mobile device and MEC.)
--
John Grant
Chair, ETSI ISG NGP
Nine Tiles, Cambridge, England
+44 1223 862599 and +44 1223 511455
https://www.etsi.org/technologies-clusters/technologies/next-generation-protocols
http://www.ninetiles.com
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
