[homenet] after the meeting comments on draft-ietf-homenet-front-end-naming-delegation-07

Denis Ovsienko <denis@ovsienko.info> Tue, 24 July 2018 16:31 UTC

Return-Path: <denis@ovsienko.info>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CBF7130EE7 for <homenet@ietfa.amsl.com>; Tue, 24 Jul 2018 09:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.102
X-Spam-Level:
X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ovsienko.info
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 Smrx14aeMgK4 for <homenet@ietfa.amsl.com>; Tue, 24 Jul 2018 09:31:52 -0700 (PDT)
Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3843A130EBE for <homenet@ietf.org>; Tue, 24 Jul 2018 09:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1532449906; s=zohomail; d=ovsienko.info; i=denis@ovsienko.info; h=Date:From:To:Message-ID:In-Reply-To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=1396; bh=voII2ceOhiXKazfWSY0tWOFhuqsA94Qz+0UiMugiehk=; b=UwkohWO9oAS4KBufQ5xzRZwmA/DQQJqlGEfikhRM6bQZEKAL2Xq5YRhTUcj7Y70M zCNcw1CBY2/MGQ57EppdD71f34T/qlIfIE0IIUsp9BhsKptGgqMz2oVWpjeYDBvC9D+ H1wpFUEiXlY3Hdg4GPn7Zl8WfwGzKqgpXGuZPMGs=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1532449906275726.9105646464884; Tue, 24 Jul 2018 09:31:46 -0700 (PDT)
Date: Tue, 24 Jul 2018 17:31:46 +0100
From: Denis Ovsienko <denis@ovsienko.info>
To: homenet <homenet@ietf.org>
Message-ID: <164cd21de61.cf472e3065599.3014191005552687277@ovsienko.info>
In-Reply-To:
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/pSQaCMXAECPfz_D5pEpngoqZ3ao>
Subject: [homenet] after the meeting comments on draft-ietf-homenet-front-end-naming-delegation-07
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 16:31:54 -0000

Hello group.

What I was trying to say at the WG meeting was the following. Looking at the slide with the red arrow between a DNS server in the home network and a DNS server somewhere on the Internet, the following scenario immediately came to my mind.

1. A home network is connected to the Internet through an ISP A. Everything is synchronous and works.
2. The link to ISP A fails.
3. For the next month the home network remains half time disconnected and half time connected through ISP B. Regardless of the Internet reachability, devices come and go, and the network tries to update its zone.
4. The link to ISP A is restored and works for the next three months.
5. The user occasionally connects to ISP B in parallel, as a matter of habit.
6. Go to 2.

Now, given the suggestion that the ISP maintains the zone, it would make sense to think what happens when the ISP's copy is no longer updated and the home network copy has changed. I have briefly looked through the I-D and have not found anything that would explicitly make sure that the zone cannot go split-brain. And if it goes split-brain, will it necessarily synchronize afterwards with no human intervention? Maybe those provisions are there, but I did not see them, in that case please disregard the comment.

Feel free to use this input to improve the document, if it gives you any new ideas.

-- 
    Denis Ovsienko