Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failover-protocol-00
Kim Kinnear <kkinnear@cisco.com> Mon, 30 November 2015 15:45 UTC
Return-Path: <kkinnear@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5D61B2E1E for <dhcwg@ietfa.amsl.com>; Mon, 30 Nov 2015 07:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 CLq3yz3_2XSZ for <dhcwg@ietfa.amsl.com>; Mon, 30 Nov 2015 07:44:59 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB23C1B2E6A for <dhcwg@ietf.org>; Mon, 30 Nov 2015 07:44:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1193; q=dns/txt; s=iport; t=1448898299; x=1450107899; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=B7xorTdhW8cnXAxgwFyvJRG1d6JZfQN1+rT+8raXObo=; b=fu13pQMqCiXeDe79WBTnT0MS01j1/jbP661A9dkcYAE9eBrcxQ7N5RAC hgfrRJ4YruDugfOP4vKIcz3+pr56Eir/Bb1Dmum0gRRQ9H9F1wWKKQyQG fx5gnzWJzX+xLmJaHJqoagarjv90lJua5etB6W9E/0W8WmhOxBZSCI4fZ g=;
X-IronPort-AV: E=Sophos;i="5.20,364,1444694400"; d="scan'208";a="632304467"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Nov 2015 15:44:57 +0000
Received: from dhcp-10-131-65-141.cisco.com (dhcp-10-131-65-141.cisco.com [10.131.65.141]) (authenticated bits=0) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id tAUFitkW018034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Nov 2015 15:44:56 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <B25C3B4C-69B5-4818-A145-CDAC106E940C@cisco.com>
Date: Mon, 30 Nov 2015 10:44:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AE56C14-0E13-4F63-94F9-F8409C5E0C94@cisco.com>
References: <66cb478301394af2a9981ed20fd9942d@XCH-ALN-003.cisco.com> <B25C3B4C-69B5-4818-A145-CDAC106E940C@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.3096.5)
X-Authenticated-User: kkinnear
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/12xUTtzM6SHWuNfZziwHKFOPqlQ>
Cc: "Bernie Volz (volz)" <volz@cisco.com>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failover-protocol-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 30 Nov 2015 15:45:00 -0000
Folks, One of Bernie's comments on the failover draft was: > - 7.1 (Time Skew) – Should we require NTP to synchronize the clocks on failover partners? The current draft (-00.txt) has a capability to allow the failover protocol to operate with two machines which have clock skew of a largely arbitrary amount (limited in some way to perhaps 24 hours or something). So two systems that are 3-5 minutes apart (the usual skew, if any) will work fine. Bernie is suggesting that we require failover partners to have essentially synchronized time by requiring NTP sync. If they are synchronized to the level of 1-2 seconds, that would be synchronized for the purposes of this protocol. We aren't talking milliseconds here. Is that a good idea? Should that be a requirement for DHCPv6 failover? Most folks running our particular v4 failover seem to run synchronized systems, though we have a few customers that don't. Those systems don't tend to be off by more than a couple of minutes, usually. I'm interested in opinions as to whether we should require time sync between failover partners for the DHCPv6 failover protocol. Thanks -- Kim
- [dhcwg] Review of draft-ietf-dhc-dhcpv6-failover-… Bernie Volz (volz)
- Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failo… Kim Kinnear
- Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failo… Kim Kinnear
- Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failo… Simon Hobson
- Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failo… Brian Haberman
- Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failo… Bernie Volz (volz)
- Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failo… Bernie Volz (volz)
- Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failo… Bernie Volz (volz)