(hence the filename). But at
least for the time being, we decided to better focus on the problem
statement first.
Any comments will be very appreciated -- including whether the topic
itself might be of interest to this group.
Thanks!
Best regards,
--
Fernando Gont
SI6 Networks
e-mail: fg
.
Thanks so much for your comments!
I this work is of interest to the TAPS WG, we could try to move this one
forward in this wg, and also think of a subsequent I-D with
recommendations (more on this later).
Thoughts?
Thanks!
Cheers,
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fin
ld provide the mechanisms
that allow apps/OSes t make the tradeoffs. But everything starts with
understanding the problem, and understanding the tradeoffs.
Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
___
g, one might think f "one
address per module" (whatever that is), or one address per
process/thread... but I'm not sure I'd default to "one address per
connection".
I think that there might only be specific cases/scenarios where one
might want to do this.
Thanks,
--
Fernando Gont
rtainly, one address per application would be a more sensible default.
However, I'm of the idea that whatever default one picks is the result
of an analysys of tradeoffs, and not the other way around.
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: 31
uable input but I don't think we should be the venue for
> it's development.
FWIW, I brought this to taps upon suggestion I got on 6man...
Thanks!
CHeers,
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
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: fg...@si6networks.com
PGP Fingerprint: 31C6 D484 63B2
me that does look a lot like source address
> selection in TAPS. There could be useful input here to a few paras in
> the TAPS architecture. It's not clear to me that would require a new
> draft though in TAPS to achieve this.
Could you please rovide a reference to the document so that I can ta
at least there seems to be a disconnect. Address properties, selection
> and lifetimes are not dealt with well (if at all) by transport layer and
> application implementations.
FWIW, that's my take as well.
Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: 31C6 D4
Hello, Erik,
On 03/21/2018 05:47 PM, Erik Kline wrote:
> On 21 March 2018 at 09:58, Fernando Gont <fg...@si6networks.com> wrote:
>> Folks,
>>
>> Based on the feedback received today, I have split our document
>> <https://www.ietf.org/internet-drafts/draft-gont-
raft-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,
--
posed agenda item:
* Title: "Problem Statement Regarding IPv6 Address Usage"
* Filename: draft-gont-taps-address-usage-problem-statement-00
* Presenter: Fernando Gont
* Topic to be discussed:
Whether the topic is of interest for this wg, and possibly adopting the
I-D as wg document
mments will be appreciated.
Thanks!
Best regards,
Fernando
Forwarded Message
Subject: New Version Notification for
draft-gont-taps-address-usage-problem-statement-00.txt
Date: Wed, 28 Feb 2018 03:46:50 -0800
From: internet-dra...@ietf.org
To: Fernando Gont <fg...@si6net
yments.
How could one accommodate such deployments? (ignoring them eventually
means that the network admins needs to figure out his own hack)
Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
On 02/13/2018 08:30 PM, Erik Kline wrote:
> On 13 February 2018 at 15:15, Fernando Gont <fg...@si6networks.com> wrote:
>> Hello, Tommy,
>>
>> On 02/13/2018 08:04 PM, Tommy Pauly wrote:
>>> Yes, I think this topic is very relevant to the work that can b
tacker might require "a lot of work"
from a server without even proving that it can receive the return packets.
Thanks!
Cheers,
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494
__
MHO deserve discussion.
And aside from the regular address systems normally configure, if one
were to specify an API one would probably want to provide a mechanism
for apps to be able to request sole/single-use addresses (.e.g., one
address per app or container).
Thoughts?
Thanks!
Regards,
--
something else you were expecting to see in the text?
Looks like I got confused -- my bad, sorry! -- No changes expected here.
Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494
__
18 matches
Mail list logo