IETF Logo Mail Archive

Re: [Captive-portals] Discovering captive portal API URL via DNS?

Lorenzo Colitti <lorenzo@google.com> Wed, 04 September 2019 08:00 UTC

Return-Path: <lorenzo@google.com>
X-Original-To: captive-portals@ietfa.amsl.com
Delivered-To: captive-portals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C57211200CE for <captive-portals@ietfa.amsl.com>; Wed, 4 Sep 2019 01:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 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, URIBL_BLOCKED=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 4YqFJVk_FRK2 for <captive-portals@ietfa.amsl.com>; Wed, 4 Sep 2019 01:00:55 -0700 (PDT)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 EFA071200CC for <captive-portals@ietf.org>; Wed, 4 Sep 2019 01:00:54 -0700 (PDT)
Received: by mail-wr1-x42b.google.com with SMTP id 30so9169754wrk.11 for <captive-portals@ietf.org>; Wed, 04 Sep 2019 01:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fD6vvx3+ELZ0Ffy/xFDmBgEiaaOMKtQZo5YwyZ5QAw0=; b=s83oh/WTrjNGwUvmoseeu84Sf1vDeLFLBQcewA4iAQOXqJmZF3hWoqt29+r7KK2mr6 iZtSjJQeBv9WMJdQnlDKU2pVrBWyzNxM6dVIFlFxLEJ0vgFmNpDgI38xrxhPS5RMFRTH HNAYlnwLsw9quMoSEtTvpghbENBJuEScLPMfZAQN8/pB6h4zzBlkGfAwPD84XYf8Rmea 4zR3j4Q5scAdE2kxRmUQJq1JSZBAt5C2rBVrPByQqWe3KiX1o2HUjtNZ0ZRvqxl6vKYe w+zU2t42PUhgcm7/XxWsEUbhRKys6KtbALEeETq2qcVihvpe9KxPz8Xpnbs3XFkQV5NP fasQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fD6vvx3+ELZ0Ffy/xFDmBgEiaaOMKtQZo5YwyZ5QAw0=; b=ApUKyYNk2LB/fWTRSO6hNQN0MwSWo/olSHGoIryK6OZ9U7FasUEZ2Y4qyMVQLaxOz2 uouwaVa1O8rMQsV9AT633OrQaGHRBR8OGWDqbA4DbCRKW6X2+/ay/c/rV2dRUEeTRkzm IoChSVHz/LcZhWTDpoJiLedPt9JXTD3pvWeRDmXT7KjbPnOKAnSg1KF9zvaLXYGwSEGk viYpTqSPWEfkY338NxIkoHwG9k0PWsZrdqYYXBNTc4ZWw4TvPhmj1L1SGH4lpqSRTlrH G2UrzwFnimYmdPfxGGaPTMgDy35zMbCdgegTgLLowzm3NDfmTT6iBMRldX0U3DSAJPnh F+tQ==
X-Gm-Message-State: APjAAAUIYjwiC0cuXt3mkWanoF+V98QDMa24zMumM9YRCaibe7vfzrTz jDFZVKgOyWCWLHQZ/xQ1AaOA+eiuOr4ZxHXwDEkWt34hvZg=
X-Google-Smtp-Source: APXvYqxLJWu7TAIrGVnk8ZN+e/HFHjo+yGfPD5SXXx1IoNzF7eBzoc08wXyh4Z3QPNg7tQx2t/2byeJKhDwCva/RpLQ=
X-Received: by 2002:a05:6000:1189:: with SMTP id g9mr16417026wrx.117.1567584053149; Wed, 04 Sep 2019 01:00:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAKD1Yr1mR57OsOzDtjM=7YCV_R6zFF9WPxqA-XrWsuJWv+VTag@mail.gmail.com> <18051.1567582038@dooku.sandelman.ca>
In-Reply-To: <18051.1567582038@dooku.sandelman.ca>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 04 Sep 2019 17:00:41 +0900
Message-ID: <CAKD1Yr0RvYU9TDjiU4Pm9QdVY_Z4XAN74wXcWhMhJ+smQLr_aw@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: captive-portals@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a5539b0591b59ac0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/d1_CrMY7uCH8PUS6QXVALCAPbJs>
Subject: Re: [Captive-portals] Discovering captive portal API URL via DNS?
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of issues related to captive portals <captive-portals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/captive-portals/>
List-Post: <mailto:captive-portals@ietf.org>
List-Help: <mailto:captive-portals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2019 08:00:57 -0000

On Wed, Sep 4, 2019 at 4:27 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

> that things like DoT/DoH can not be used by the captive portal client.
> (I just want to make the assumption explicit. I'm not complaining about it)
>

That's not really an assumption - the fact that the captive portal client
can't do DoT/DoH is mostly true today, because unless the portal is open,
443 and 853 are likely to be blocked. By and large, DoT / DoH clients
probably already know not to attempt them on captive portals.

v2.23.0 | Report a Bug | By Email