Re: [mif] RFC 6731 implementations

Ted Lemon <mellon@fugue.com> Thu, 03 November 2022 16:22 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20DF8C14CE2D for <mif@ietfa.amsl.com>; Thu, 3 Nov 2022 09:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20210112.gappssmtp.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 kmL3zkkvx8jj for <mif@ietfa.amsl.com>; Thu, 3 Nov 2022 09:22:15 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 273AFC14F722 for <mif@ietf.org>; Thu, 3 Nov 2022 09:22:15 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id 8so1477372qka.1 for <mif@ietf.org>; Thu, 03 Nov 2022 09:22:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TOZqhQT6HfVLf4N+KWMFmBQ9jVLVQZPH0DqImbndhdk=; b=uV8B5U5e1Y9OkuScv7b/3pJ1XjJ8tS3EtQbKpU2LMI+b7/mF0gLOoSu/heuEVwoO5w s5TvZamHIUqb7o6jrhRQdtnygNDdSsj9yIkHTdPPwIvzHLk6ZYxN1Afuq2n7FQFG5PKK XY0TJJNaRRR9s5rU3yfwKwFipDXbujeLorSFgiiablFPzbMgcBwPzh4OZ4moqsKQFkdH WVZ5Kfp9bGqqbWl9iHt5KV+PJoE9mu/5fjmyj+RDd0AnDHcQQPxyp/2ec4z19X7pReUW LELOQEaM1MHm4XKRZaHqlWe/RIrke7CjcsV4AkCSWgagLfGHIzYP5t8DgKJLtxtwmxE5 Zq9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TOZqhQT6HfVLf4N+KWMFmBQ9jVLVQZPH0DqImbndhdk=; b=KHNnYuoOEKeV+QVQ6hOZkAo1fLbcT1oVuKRCunKk3be4pE6kaSA4LFsluZvcrE+J3M EOS7S0Xar4Mtjnr67STXzBONGhpbkHKY06pVLiThgkoU8XiFbbeKtDw+SdEv54bBo1CS 8+AuXWCQMfDnoqmxNrOXy93+ssgYjV1oLXSlZMXrEB7apK4SnbF4SDnxzA+r/JyAxQMa gKyKW6jWLO8m9iVNP2INPI6qhHMF8osxl/eWev6xfZnUNGn/QaF1XjjX/ZwAz+B1JYyi No2JcN5HByVLUqUtWN5Efq7UysnbgLwl+676X4utG2D/ULmIY5dvC5H19F7Q53o5DRoE fs5A==
X-Gm-Message-State: ACrzQf3J61l+RYKm0wcJSi9VNC2qlCsI7bQe+UXSiosExsbsB1D1jEvA rr0OwW1i5jVC9LdiCX9B4U9X/CAg5bgrWEdsJvJioA==
X-Google-Smtp-Source: AMsMyM6baB9mkStOKMTQPqhOcM+Z+xXi6DIMgjLENy5hfZVs6cf+nVbUxbXQ103AQ76ofrleVK1H2A0PeJAQrCSSB94=
X-Received: by 2002:a05:620a:cd0:b0:6fa:27c8:c024 with SMTP id b16-20020a05620a0cd000b006fa27c8c024mr16809096qkj.189.1667492533925; Thu, 03 Nov 2022 09:22:13 -0700 (PDT)
MIME-Version: 1.0
References: <83c25827-1211-8c1c-9001-e6cb6fdaaab9@redhat.com>
In-Reply-To: <83c25827-1211-8c1c-9001-e6cb6fdaaab9@redhat.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 03 Nov 2022 17:21:38 +0100
Message-ID: <CAPt1N1mQA8gYp_2RNJM4Sxq+ifAdQv5B=Aet0wLQwjZ72R+O=A@mail.gmail.com>
To: Petr Menšík <pemensik@redhat.com>
Cc: mif@ietf.org
Content-Type: multipart/alternative; boundary="000000000000268dc005ec935c2c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mif/vFJI3_CyRFoDJUv-K5I0OV6r8fc>
Subject: Re: [mif] RFC 6731 implementations
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2022 16:22:19 -0000

You might want to read this:

https://datatracker.ietf.org/doc/rfc7556/

And this:

https://www.rfc-editor.org/rfc/rfc8801.html


On Thu, Nov 3, 2022 at 4:55 PM Petr Menšík <pemensik@redhat.com> wrote:

> Hello former MIF group members,
>
> I have found RFC 6731 [1], which is Standard Tracks since December 2012.
> I have found reference to it from some draft of add WG. When I read it,
> I found it proposes solution to existing problem on Linux desktops,
> which is not yet sufficiently solved. A bit similar attempt is
> implemented by systemd-resolved [2], but does not use any standardized way.
>
> I think every device with multiple interfaces is potential candidate for
> it. Every laptop with ethernet+wifi, every smart phone with
> wifi+cellular network. Yet I haven't found any attempts to implement RFC
> 6731. Do you know existing implementations for any operating system? Is
> it used somewhere already? Is there a reason why it is not widely used?
>
> I work in Red Hat as a Software Engineer, maintaining some DNS packages.
> Dnsmasq has some integration with Network Manager, which does something
> similar. Yet they are misusing dns-search parameter of DHCP protocol. I
> would like to add more proper support, but I find current standards
> confusing. Is there more relevant successor to this standard?
>
> Best Regards,
> Petr
>
> 1. https://www.rfc-editor.org/rfc/rfc6731.html
> 2. https://systemd.io/RESOLVED-VPNS/
>
> --
> Petr Menšík
> Software Engineer, RHEL
> Red Hat, http://www.redhat.com/
> PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>