Hi Fernando-
draft-gont-taps-address-usage-problem-statement says
This document analyzes the impact of a number of properties of IPv6
addresses on areas such as security and privacy, and analyzes how
IPv6 addresses are curently generated and employed by different
operating systems and applications. Finally, it provides a problem
statement by identifying and analyzing gaps that prevent systems
and
applications from fully-leveraging IPv6 addressing capabilities,
setting the basis for further work that could fill those gaps.
I think the applicability of this work goes potentially far beyond TAPS
as it applies to any application's use of IPv6 addresses. I'm a little
worried that this wg doesn't contain sufficiently broad perspective to
make recommendations. Indeed, I see TAPS as a consumer of this doc more
than source of the recommendations. My opinion is that this is kind of
out of scope for our wg. I would support another group with the right
expertise to support it (maybe 6MAN or V6OPS). I think TAPS would
provide some valuable input but I don't think we should be the venue for
it's development.
If the working group speaks up, I can be persuaded otherwise.
--aaron
On 6 Aug 2018, at 4:58, Fernando Gont wrote:
Folks,
There has been some discussion over time about
* draft-gont-taps-address-usage-problem-statement
* draft-gont-taps-address-analysis
The former describes problems we're facing nowaadys as a result of
limited APIs, whereas the second discuss different properties of
addresses, hopefully shedding some light on how we could make a better
usage of the available addreses.
Chairs: Do you think it would be reasonable to poll the wg for
adoption
of these two documents?
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
