IETF Logo Mail Archive

Re: [Add] Existing RFC 8801 and 6731 implementations?

Erik Kline <ek.ietf@gmail.com> Tue, 31 May 2022 21:14 UTC

Return-Path: <ek.ietf@gmail.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7BC3C157B34 for <add@ietfa.amsl.com>; Tue, 31 May 2022 14:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEXDwabXgAXq for <add@ietfa.amsl.com>; Tue, 31 May 2022 14:14:50 -0700 (PDT)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF9ABC15790C for <add@ietf.org>; Tue, 31 May 2022 14:14:50 -0700 (PDT)
Received: by mail-oi1-x235.google.com with SMTP id y131so79429oia.6 for <add@ietf.org>; Tue, 31 May 2022 14:14:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cjXEOi03Xqn5bZm01qtTZ2+yWhv9A5qCft7mM4UL/OI=; b=fQK0sxdlGy5KJXFquE7wC7EFJQAIpE0wXWS1vVqUFXJD9f08fa/V6H8VJxYYIU/Qud dpuPSlpmhSnBz2V4Q1pDg6dG7P/86T6tP6UX8H7Ijc+Xcnh5kBr9jjDfvbLfs7wIv7nR XPuXu8HWemr7H01umGq86b/0DvcQlZkcKWbxeNjWBIwZJLYvNLIGyg8P5onF12k+FcZL 4T54s/7mr+eEq0ZsVBFOJ6QrbTKCB2Mm1FXK8IitwP6Xjpmt5NEparLW9W/LlwvOYMkG Z2inBde45/0A0xSjJarSG2QAaJtuU3R74sU7crhbABS4O+S7iUIi3gNPiD0CL1SW7YEO s9hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cjXEOi03Xqn5bZm01qtTZ2+yWhv9A5qCft7mM4UL/OI=; b=6pYNhdSZsWuhyZGHage/ZhxERPK6vy1bWXiJ/MZ8+zQ6hK9lQfyAiCNqCPNTZkIo73 ZVqswLyYDc8Lf7mJnL3WAk5xYV/IHYb/LPVxzusWTxOuNqbVC0cNA8jc/OJItFK3QRpj CLT/Vgksl/pM5yrazUVZP5lU00JvEuYRjVy7JkKqVqifF9he/foO7mvTXIfj7TdiEhlJ 77K5KnCOth0cJr1b8HSRYuP6ArPIMF8qnlK1B2ZzDBGJ1LFvkHtyAsr27vq4EdQhnu09 nWJA/GDtKEB5p5KXYe3VTQIF2GCfVTUqcmviFio8rFtqnZYUuYqjd1IC2Nh3v2TA5hor kQdA==
X-Gm-Message-State: AOAM533yQ4i5m4NvLiz3b2FR1rI7otgFZgJfio1EuJorCdT0kRZ3gIZB phoJozluOUZ/AHB7AWPD1zFkY7pD5rlJCwOj+2C8YDOY
X-Google-Smtp-Source: ABdhPJzmv4P5tbWDnWQoYeUXdJDkeOZLX2OH1Xbk/BqUkpM6LanGsA0pv/qbBpQep7gGO7MrF0MOd+UnecTgKzCMMy8=
X-Received: by 2002:a05:6808:4d1:b0:32a:f930:3e32 with SMTP id a17-20020a05680804d100b0032af9303e32mr12827031oie.291.1654031689937; Tue, 31 May 2022 14:14:49 -0700 (PDT)
MIME-Version: 1.0
References: <66091396-06a4-9637-f1b0-3b67f3565677@redhat.com>
In-Reply-To: <66091396-06a4-9637-f1b0-3b67f3565677@redhat.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Tue, 31 May 2022 14:14:39 -0700
Message-ID: <CAMGpriW=uhLAH4qsRkHMNjdNRLCfFO9OSRz0G2COWrZ42gooBQ@mail.gmail.com>
To: Petr Menšík <pemensik@redhat.com>
Cc: ADD Mailing list <add@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, Tommy Pauly <tpauly@apple.com>
Content-Type: multipart/alternative; boundary="000000000000537ae405e0554321"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/O6LKEfhyHoaDYTOuo-cOAmqxbOA>
Subject: Re: [Add] Existing RFC 8801 and 6731 implementations?
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2022 21:14:51 -0000

There are devices (notably mobile devices) that support provisioning
domains conceptually (i.e. RFC 7556).  I'm not aware of any implementation
support for 8801 yet though.

Having support in the Linux kernel would be great, but would mean -- among
other things -- adding structures to keep track of RAs and their next-hop
origins, which would also help make things like RFC 6724 rule 5.5 possible
(among other things).  Perhaps that work is underway, or has been
completed, but I'm not aware of any such support.

On Tue, May 31, 2022 at 3:27 AM Petr Menšík <pemensik@redhat.com> wrote:

> Hello,
>
> I work in Red Hat on RHEL dns servers like Unbound, dnsmasq or bind.
>
> I would like to ask if there is known implementation for RFC 8801
> Provisioning Domains? Is it implemented as optional part of any system?
> Does some vendor support it even in production?
>
> Is there also known RFC 6731 implementation? Linux desktops have some
> support using systemd-resolved or dnsmasq to send different name trees
> to different servers. But neither does use well standardized solution.
>
> Are there known implementations following one of those RFC mentioned for
> other systems like Microsoft Windows, Apple systems or Google Android?
> Do you know any other systems implementing split DNS on client side? I
> would like to gather experience with such implementations, but I am
> unsure what would be the best place to ask. I know 6731 is from
> different workgroup which already ended, but it were referenced from 8801.
>
> Best Regards,
>
> Petr
>
> --
> Petr Menšík
> Software Engineer
> Red Hat, http://www.redhat.com/
> email: pemensik@redhat.com
> PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
>
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>

v2.23.0 | Report a Bug | By Email