IETF Logo Mail Archive

Re: [dhcwg] DHCPv6 Failover -- LAST CHANCE

"Bernie Volz (volz)" <volz@cisco.com> Tue, 06 September 2016 01:41 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6293C12B00D for <dhcwg@ietfa.amsl.com>; Mon, 5 Sep 2016 18:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.028
X-Spam-Level:
X-Spam-Status: No, score=-16.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEL3UO_EcT5F for <dhcwg@ietfa.amsl.com>; Mon, 5 Sep 2016 18:41:44 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DBD812B006 for <dhcwg@ietf.org>; Mon, 5 Sep 2016 18:41:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15992; q=dns/txt; s=iport; t=1473126104; x=1474335704; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Y6GVDXbRBme6j51lWkW1ywH4FsBL1e8dRWD+MU0YdMw=; b=L6RKkVCWdRVOfs6MuBGebUkkkopabV2AYUlj1TAGxM+tpt8jmYw5IW09 CORK9Sb/oqvegtXutnRqf2mH8dkcwKdPJjhsIUoayRKuheo59MlblE6xW UdEzaTk3AZFgc7dJzAV/KSqaZzPiS8YJ73hAXfZdq+KtAfc+UwNW6xD9l M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DQAQANHs5X/4gNJK1dGQEBAQEBAQEBAQEBgnozAQEBAQEeV3wHjSeaC4tvhQ2CAhkBCoV4AhyBNDgUAQIBAQEBAQEBXieEYQEBAQMBAQEBIApBCwULAgEGAhEEAQEoAwICAiULFAkIAgQBDQUIiDoIDpMPnSSMIgEBAQEBAQEBAQEBAQEBAQEBAQEBARcFin2EEhEBMx+CTIJaBZlTAY8ugXWIEoVZjEyDeQEeNoRHcIRLgSB/AQEB
X-IronPort-AV: E=Sophos;i="5.30,289,1470700800"; d="scan'208,217";a="319847755"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Sep 2016 01:41:43 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u861fhxC032687 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 6 Sep 2016 01:41:43 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 5 Sep 2016 20:41:42 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Mon, 5 Sep 2016 20:41:42 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: 神明達哉 <jinmei@wide.ad.jp>, Ted Lemon <mellon@fugue.com>
Thread-Topic: [dhcwg] DHCPv6 Failover -- LAST CHANCE
Thread-Index: AQHSBU9435MONICEd0SXLa4V51dyuqBm+NmAgAEcjQCAA56XsA==
Date: Tue, 06 Sep 2016 01:41:42 +0000
Message-ID: <115af86f8b8d410f8591e9f76e666212@XCH-ALN-003.cisco.com>
References: <58B66897-2F0D-4916-AF5A-42D5DC172DE5@cisco.com> <CAJE_bqeX5iAmGupySR=h3NW3NbSiT3rqD+Qh-d_i+iO8k90Yjg@mail.gmail.com> <CAPt1N1=F4PhxRC75Rk6NGN3PGEXOg3-SC9GPy0Huv6QjTvziRw@mail.gmail.com>
In-Reply-To: <CAPt1N1=F4PhxRC75Rk6NGN3PGEXOg3-SC9GPy0Huv6QjTvziRw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.98.1.205]
Content-Type: multipart/alternative; boundary="_000_115af86f8b8d410f8591e9f76e666212XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/-vR7J6ukbc7HFiG1x4tKCaRRldM>
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Simon Hobson <dhcp1@thehobsons.co.uk>, "Kim Kinnear (kkinnear)" <kkinnear@cisco.com>
Subject: Re: [dhcwg] DHCPv6 Failover -- LAST CHANCE
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2016 01:41:48 -0000

And, there’s still time to read the entire document (WGLC ends a week for now). And, the WGLC could be extended if someone requested more time – yes, it is a rather long and somewhat complex document. We extended 3315bis.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Saturday, September 03, 2016 9:22 AM
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: <dhcwg@ietf.org> <dhcwg@ietf.org>; Kim Kinnear (kkinnear) <kkinnear@cisco.com>
Subject: Re: [dhcwg] DHCPv6 Failover -- LAST CHANCE

Jinmei-san, the question is, is it better to publish something that's basically good but has a few non-blocking issues, or to not publish it at all?   I too would like to see the document get more review and maybe a couple of interoperating implementations, but if we have to wait for the bis document for that, I'm okay with it.

On Fri, Sep 2, 2016 at 4:23 PM, 神明達哉 <jinmei@wide.ad.jp<mailto:jinmei@wide.ad.jp>> wrote:
At Fri, 2 Sep 2016 15:23:13 -0400,
Kim Kinnear <kkinnear@cisco.com<mailto:kkinnear@cisco.com>> wrote:

> We have some detailed technical reviews.  What we *really* need now
> are people to just read it and say:
>
>   "I think this draft should move forward".
>
> That's all you have to do.  Any review would be nice, but we really
> just need people to read it and send in email that says "move this
> forward".

I feel sorry that I simply couldn't find time to read this big
document and provide useful feedback, but I also feel nervous by
seeing this action...it's hard to believe that if someone reads this
size of complicated technical document and can just say "it should
move forward".  Even after getting reviews and revised, it's quite
likely for every new reader to find at least one or a few non-trivial
issues.  So, if the only response to the call is just "move forward",
I wonder if it's really a careful read.  And, now, if we move forward
just by counting a certain number of 'yes', does that mean something?
If we think we've already got sufficient level of technical reviews,
isn't it itself enough to move forward (to which I wouldn't be
opposed)?  If not, counting more simple "move forward" responses just
as a prerequisite for moving forward doesn't seem to be a good way to
move forward.

Just my two cents.  Again, I'm sorry I cannot be more productive...

--
JINMEI, Tatuya

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email