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?
Best,
Tommy
> On May 24, 2018, at 5:11 AM, Fernando Gont <[email protected]> wrote:
>
> Folks,
>
> Any thoughts?
>
> Thanks!
> Fernando
>
>
>
>
> On 03/21/2018 07:58 PM, Fernando Gont wrote:
>> Folks,
>>
>> Based on the feedback received today, I have split our document
>> <https://www.ietf.org/internet-drafts/draft-gont-taps-address-usage-problem-statement-00.txt>
>> into this two documents:
>>
>> * Problem statement with respect to limitations of the Sockets API:
>> <https://www.ietf.org/id/draft-gont-taps-sockets-api-limitations-00.txt>
>>
>> * Analysis of IPv6 address properties:
>> <https://www.ietf.org/internet-drafts/draft-gont-taps-address-analysis-00.txt>
>>
>> Your feedback will be appreciated. We'd also appreciate guidance on how
>> to move forward. :-)
>>
>> Thanks!
>>
>> Best regards,
>>
>
>
> --
> Fernando Gont
> SI6 Networks
> e-mail: [email protected]
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> _______________________________________________
> Taps mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/taps
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
