[DNSOP] resolver-info and capport, pvds, etc

Erik Kline <ek@google.com> Tue, 23 July 2019 15:26 UTC

Return-Path: <ek@google.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A286012033C for <dnsop@ietfa.amsl.com>; Tue, 23 Jul 2019 08:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 rgvo96BjE5nz for <dnsop@ietfa.amsl.com>; Tue, 23 Jul 2019 08:26:56 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 24BD1120338 for <dnsop@ietf.org>; Tue, 23 Jul 2019 08:26:52 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id k8so82739485iot.1 for <dnsop@ietf.org>; Tue, 23 Jul 2019 08:26:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=HROHTCWhHdVLzaobrwp2Ri/9fzsGZRGOvQWHGVkD9ec=; b=SOkoVa3SO3RG9LgBW7KhzM0YrB6uDy4Vestl0x5lCrMph58BsSPBC9VuUl6N1u2wFh Z3t6Pn1tUKGzu5i5T1CtFoDLOQmtfteAjtWIHFQuejPrZCXMvgz3s6e66a7fGOrCK0v+ MF0tcuzmoC1GP006eWENU/5erDZ9SmfrpHWFNmxqJddXrEMGwdL4aXIGXDArjFsAS1GQ 7EW3eWzxv/3YTbq4lfSyZhD+hPc21DM8rC+GiRqeGehvxzBZmYC04Bt5GRW5FeNAKSD8 rVW00eXE0DxFKIUgtv9sSk7syjRVdw27gp5+PLUs4z9VM5Z08vYBtM3z2BKbJIoc4mMC j3yg==
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=HROHTCWhHdVLzaobrwp2Ri/9fzsGZRGOvQWHGVkD9ec=; b=afNPO1/HK6nb2l2LFDvsoGYtOUhawv7oawfa8wu5OWSAHycLMvGbEuampqCfX/KyGo kSAjqUuyz2E3RCKL+v+Ug/CfZ3M89kBHkow4he+55UK8yE0OPaVKUJJAZls4XZ+fSMvT Gi82WwDYFFeXnoe+wtNU0pPnPoAgqDq6WrfOPesazh2yfLKfxHWcmXyj462WJdrShJCD +tDZllJFa0b33i5d8iqbuT9+HvXma5Xvhqs87d67eERrYastRdkDNGE1Uw3bwC33UV+W jwEn1ILimfrKQPRINuWanDHRYMZvAlf8u8/5RuB2Ocb4gWSxd0ADUL7ohvAB+8MDCqXo R6cg==
X-Gm-Message-State: APjAAAVkzCa6LnGaaduXXnKpBILHBxbzRirdfUX7Ot639G7nfygcLmGf KOdTa6zCZ8poy5CGKhA+6FJ0dmWEVcz97ZIQwGc3Q9s0v3Rv8w==
X-Google-Smtp-Source: APXvYqzA7H7phBUkBORa8UQjwO7cIpNC05HtFcpqmUM0C3llIHOZV42qDf9TIrlWIwjVqm1UWcVFto4OdMkxM53v2b0=
X-Received: by 2002:a5d:9642:: with SMTP id d2mr48594471ios.278.1563895610693; Tue, 23 Jul 2019 08:26:50 -0700 (PDT)
MIME-Version: 1.0
From: Erik Kline <ek@google.com>
Date: Tue, 23 Jul 2019 11:26:36 -0400
Message-ID: <CAAedzxpZv1aD+Rq9ohDp80GSuR=+ueVB5bX1htt_QmOPA3OCWg@mail.gmail.com>
To: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000630570058e5ad2b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XTXc0r65W4ANGBMY7cO5rKnNlcg>
Subject: [DNSOP] resolver-info and capport, pvds, etc
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2019 15:26:58 -0000

A few thoughts about resolver-info before I forget.

Capport API _could_ contain some rich resolver info, but I suspect it
really only belongs there if it's import to the captive portal interaction
phase (co-chair both on and off).

There _could also_ be some rich resolver info in the PVD
additional information, but IMHO it's a poor substitute to learning
information from the resolver itself (i.e. prefer fate-sharing).

WRT the well-known name to get a response from a middle resolver: there is
no guarantee that the client has a communications path to mid-level
resolver.  So the resolver info may only be usable by the forwarders
themselves and not to the client.  I think the hop-by-hop DNS lookup is
probably a separate issue to be addressed separately.

2 cents,
-ek