Re: [dhcwg] Review of draft-ietf-dhc-dhcpv6-failover-protocol-00

Brian Haberman <brian@innovationslab.net> Mon, 30 November 2015 18:30 UTC

Return-Path: <brian@innovationslab.net>
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 2607D1A038C for <dhcwg@ietfa.amsl.com>; Mon, 30 Nov 2015 10:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 csadQaDwTqKF for <dhcwg@ietfa.amsl.com>; Mon, 30 Nov 2015 10:30:44 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 382D01A02BE for <dhcwg@ietf.org>; Mon, 30 Nov 2015 10:30:44 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id F104B88130 for <dhcwg@ietf.org>; Mon, 30 Nov 2015 10:30:41 -0800 (PST)
Received: from clemson.jhuapl.edu (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id C402F328081A for <dhcwg@ietf.org>; Mon, 30 Nov 2015 10:30:38 -0800 (PST)
To: dhcwg@ietf.org
References: <66cb478301394af2a9981ed20fd9942d@XCH-ALN-003.cisco.com> <B25C3B4C-69B5-4818-A145-CDAC106E940C@cisco.com> <5AE56C14-0E13-4F63-94F9-F8409C5E0C94@cisco.com> <29AE5313-D17E-4F78-BBBC-395BB0AE3589@thehobsons.co.uk>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <565C95C8.4070601@innovationslab.net>
Date: Mon, 30 Nov 2015 13:30:32 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <29AE5313-D17E-4F78-BBBC-395BB0AE3589@thehobsons.co.uk>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="tak9IuTn8cfWh0NXLbHTmwVlxS7jgQLrD"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/oa7aoT6Xb8ZlrgT0p4HfNRpyMIg>
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 18:30:45 -0000

As the AD who shepherds the time-related WGs...

On 11/30/15 11:56 AM, Simon Hobson wrote:
> Kim Kinnear <kkinnear@cisco.com> wrote:
> 
>> 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.
> 
> I see two points :
> 
> 1) If the time should be synced, then I would suggest merely
> requiring that, rather than specifying NTP - ie specify the what
> rather than the how.

The above makes sense since NTP is not the only protocol available to
synchronize time.

Regards,
Brian