'Re: draft-ietf-6man-slaac-renum: Processing of PIO Lifetimes at Hosts'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Re: draft-ietf-6man-slaac-renum: Processing of PIO Lifetimes at Hosts
From:       Ted Lemon <mellon () fugue ! com>
Date:       2020-09-10 19:40:25
Message-ID: 50E6A218-5677-43E6-A49D-C807ABD4D8B1 () fugue ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On Sep 10, 2020, at 3:29 PM, Fernando Gont <fgont@si6networks.com> wrote:
> > To see if we can properly solve the larger robustness problems. If there is one.
> 
> Give that we have been discussing the topic for more than 1.5 years, and that we \
> have a problem statement document (draft-ietf-v6ops-slaac-renum), is it too much to \
> expect that the problem be acknowledged, and that we try to solve it, instead of \
> possibly boiling the ocean?

Indeed, best is the enemy of good enough here. Let's proceed with the work we are \
doing before adding new work.

[Attachment #5 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class="">On Sep 10, 2020, at 3:29 PM, Fernando Gont \
&lt;<a href="mailto:fgont@si6networks.com" class="">fgont@si6networks.com</a>&gt; \
wrote:<div><blockquote type="cite" class=""><div class=""><div class=""><blockquote \
type="cite" style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; \
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: \
auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; \
-webkit-text-stroke-width: 0px; text-decoration: none;" class="">To see if we can \
properly solve the larger robustness problems. If there is one.<br \
class=""></blockquote><br style="caret-color: rgb(0, 0, 0); font-family: \
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; \
font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; \
text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span \
style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 14px; \
font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: \
normal; text-align: start; text-indent: 0px; text-transform: none; white-space: \
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; \
float: none; display: inline !important;" class="">Give that we have been discussing \
the topic for more than 1.5 years, and that we have a problem statement document \
(draft-ietf-v6ops-slaac-renum), is it too much to expect that the problem be \
acknowledged, and that we try to solve it, instead of possibly boiling the \
ocean?</span></div></div></blockquote></div><br class=""><div class="">Indeed, best \
is the enemy of good enough here. Let's proceed with the work we are doing before \
adding new work.</div><div class=""><br class=""></div></body></html>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

[prev in list] [next in list] [prev in thread] [next in thread] 