[homenet] primary / secondary configuration

Daniel Migault <daniel.migault@ericsson.com> Fri, 07 June 2019 20:28 UTC

Return-Path: <mglt.ietf@gmail.com>
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 7466E120294 for <homenet@ietfa.amsl.com>; Fri, 7 Jun 2019 13:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 DRURD3keoze6 for <homenet@ietfa.amsl.com>; Fri, 7 Jun 2019 13:28:05 -0700 (PDT)
Received: from mail-qk1-f172.google.com (mail-qk1-f172.google.com [209.85.222.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3132120242 for <homenet@ietf.org>; Fri, 7 Jun 2019 13:28:05 -0700 (PDT)
Received: by mail-qk1-f172.google.com with SMTP id a27so2082720qkk.5 for <homenet@ietf.org>; Fri, 07 Jun 2019 13:28:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Mr+S5ZYo2N7hVJwul0UhB6GYzmufxKcR5sxHcscv3J0=; b=lk7Wd9EXnm9h2Lcvc+pe4b8rLIjy6oE9IQQfUxt3aaZTvKknvT/+rsVrA1JNs0cd9n VBFpwzTh6sC9yWkoolK9fYiFYMi5+K3Bls6qeP8BIBnbEbT0Bu5NSRFdelsgRtfLe4rB z6V83P2M12vJfFbpXypzO+ZMZvk6UCZOqtTvVqDE5nyXJlDX6CYfhFgc2HA/FZXhQ1Hf OezZrBNbDCuXmJcVMiVu0uvh9HGjQ6l31W1YqHaX5yXvz2WxtyTxZR8CoS37NIu7mYzo QTX2mjjsRnaYnVFqnOvQ1pDsVDhO4hynYwnIlXBnStJ5q7SF9sigBF9l1wrGBGM7tIZ4 CZtA==
X-Gm-Message-State: APjAAAWmebGskrXQ2RNWBwkyfokChsJS48AT0n8jG7ebrEJMzgo6D4MJ 5qQJTobqnP4sVchTXe7eEaY7o1Wk0v6cJaZpQ79z+fCo
X-Google-Smtp-Source: APXvYqz6yIsKFbTmQlcS6NxLHfDlZNclmf4bMlSSE6bZYPS46S5EjYRHVVl4o3FaRBV+hhRGe13WRc0ZgFBZrtx7D/I=
X-Received: by 2002:a37:7783:: with SMTP id s125mr44157225qkc.267.1559939284583; Fri, 07 Jun 2019 13:28:04 -0700 (PDT)
MIME-Version: 1.0
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Fri, 07 Jun 2019 16:27:53 -0400
Message-ID: <CADZyTknGV8huQzVrQcJgFu82HGkOhBe9Q2f23bBXYT8-WOjtPg@mail.gmail.com>
To: homenet <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000edca30058ac1aa24"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/YjEXoN9OY4NxwW-z0SyAsOQ1Hws>
Subject: [homenet] primary / secondary configuration
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 07 Jun 2019 20:28:20 -0000

Hi,

We are looking for a simple way to configure the primary / secondary DNS
setting between the homenet and the outsourcing infrastructure. The
exchange of these information is done over a secure channel - let say TLS.
While we coudl re-define a configuration template / mechanism we believe
that re-using widely deployed libraries would ease the deployment.

The HNA is responsible for building / signing the zone and synchronising
the zone with the outsourcing infrastructure. To build the zone some
elements of the infrastructure are needed such as the NS and IP for
example. One way to enable the transmission of information from the the
outsourcing infrastructure to the homenet is to use an well known fqdn
hna.example.com with an AXFR request. Does it sound reasonable ?

On the other hand, the outsourcing infrastructure needs to know the fqdn of
the hna. One way to provide that information could be to re-use DNS update
updating the SOA of hna.example.com. The fqdn of the hna would be indicated
using the MNAME field. Does it sounds reasonable as well ?

Yours,
Daniel