Re: [dhcwg] DHCPv6 Failover -- LAST CHANCE

"Karsten Krone (kkrone)" <kkrone@cisco.com> Mon, 05 September 2016 14:37 UTC

Return-Path: <kkrone@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 BA5B712B22B for <dhcwg@ietfa.amsl.com>; Mon, 5 Sep 2016 07:37:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level:
X-Spam-Status: No, score=-16.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 a2Te07d3e_Ra for <dhcwg@ietfa.amsl.com>; Mon, 5 Sep 2016 07:37:39 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 785B812B229 for <dhcwg@ietf.org>; Mon, 5 Sep 2016 07:37:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=736; q=dns/txt; s=iport; t=1473086259; x=1474295859; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=u19YmfpULBdtb2pIQVMVNrZfFfXf64TUe8P+flPJnP0=; b=VE945RKsXa/or+Piq+dv9KuRnXVaqVd8r1TSQcqPi1bc/9vGWTPC1a27 TSwlSgBZnLJp38grB5GK2gErtiN2yMYWJ6d2Et+COyeIbo+K+txM6P3el RESRoxx9IIdWvcyIxSglZzoWohozFzN4KiKA1kLyNs6BNK968mA39fVit I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CpAQCmgs1X/5BdJa1dGgEBAQECAQEBAYMtAQEBAQEeV3wHg0CJZ6h2gg+CAiSFeAIcgSk4FAECAQEBAQEBAV4cC4RiAQEEIxFVAgEGAhoCJgICAjAVEAIEE4hKDpNsnSSMIAEBAQEBAQEBAQEBAQEBAQEBAQEBARcFgQWFKoF4glaEQIMCK4IvAQSZUwGGIIkVCoFOFoReiQ2QRQEeNoRHcIVdfwEBAQ
X-IronPort-AV: E=Sophos;i="5.30,286,1470700800"; d="scan'208";a="317795653"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Sep 2016 14:37:38 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u85EbceQ002932 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Mon, 5 Sep 2016 14:37:38 GMT
Received: from xch-rtp-004.cisco.com (64.101.220.144) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 5 Sep 2016 10:37:37 -0400
Received: from xch-rtp-004.cisco.com ([64.101.220.144]) by XCH-RTP-004.cisco.com ([64.101.220.144]) with mapi id 15.00.1210.000; Mon, 5 Sep 2016 10:37:37 -0400
From: "Karsten Krone (kkrone)" <kkrone@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHCPv6 Failover -- LAST CHANCE
Thread-Index: AQHSBrjO0AZT2h+t3kasLhSWEwk4CqBrXTmA
Date: Mon, 05 Sep 2016 14:37:37 +0000
Message-ID: <EC3BCAE9-6E35-409D-925A-890C8DDD8B35@cisco.com>
References: <58B66897-2F0D-4916-AF5A-42D5DC172DE5@cisco.com> <DDD8A5EF-E416-4FEC-8752-798C6F8F4960@cisco.com> <1655ce6d7d1241ff93eec18e8c07d230@XCH-ALN-010.cisco.com> <FB9543231419BE4588604B11EBD636571E98BAF8@MBX029-E1-VA-2.EXCH029.DOMAIN.LOCAL> <ED7C285E22BEA84F876DE1DA140E585C07879667@MBX029-E1-VA-4.EXCH029.DOMAIN.LOCAL> <0ED63BD7-D8B5-4CA1-AED9-7E869A8C36B5@cisco.com>
In-Reply-To: <0ED63BD7-D8B5-4CA1-AED9-7E869A8C36B5@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.18.0.160709
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.126.37]
Content-Type: text/plain; charset="utf-8"
Content-ID: <33717842B522A44C91BEA83B9FC908F6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/cT8EgQyaA8SHNC37EtDbP7xlEO8>
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: Mon, 05 Sep 2016 14:37:41 -0000

Dear working group,


Following your last call:
——8<————
We are well into the second and *last* WGLC for the DHCPv6 failover draft:
https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-protocol-02

——8<————

I would very much appreciate to see this draft come into existence.
Please move it forward, it does make sense, also for a number of smaller ISPs I work (and have worked) with.

Kind regards,

--
Karsten Krone .:|:..:|:. 
Cisco Germany| Systems Engineer GSP | kkrone@cisco.com