Re: [Captive-portals] Fwd: I-D Action: draft-ietf-capport-architecture-03.txt

David Bird <dbird@google.com> Tue, 01 January 2019 01:44 UTC

Return-Path: <dbird@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 8CAAC12D4ED for <captive-portals@ietfa.amsl.com>; Mon, 31 Dec 2018 17:44:39 -0800 (PST)
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_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 7SDKNhMuB8kv for <captive-portals@ietfa.amsl.com>; Mon, 31 Dec 2018 17:44:37 -0800 (PST)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 2B81112426E for <captive-portals@ietf.org>; Mon, 31 Dec 2018 17:44:37 -0800 (PST)
Received: by mail-it1-x12f.google.com with SMTP id b5so35271812iti.2 for <captive-portals@ietf.org>; Mon, 31 Dec 2018 17:44:37 -0800 (PST)
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=y78B5t6a+nEuHjIosFlNdsVHEax9lSbOs4jm1+XIpK8=; b=txxbUuPrc//WZsHw/vNY/5EjCdKZ+h7EW7VozpeZ6ev343UXc0wQ+HMcni1x9APmup aG5rXWPZdtVLPOfAJVgk1OmcoVYxfTDrtDCRCmr7KMurTQshuwwUiRKEVdwEcJBJCd7Z cek0W3vBNQUwXE+weSUSeKJ0kwXjdBTCKz0MA06aipqrJu1bPoBN4N8ej8uhvjzmxxda RyuiSHx47iQhEYemhf3VfI2Y7FvAAf5Kt+GBmXY12YheB+e/PObPXSfO4qy2BlO5KxZA y21YSIhUR0bDLdoVq5I9XJIOZKWSr8jdMB7f47CTNkvmigpbNS8IMqjxuzWxT1oMc5wK 62PA==
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=y78B5t6a+nEuHjIosFlNdsVHEax9lSbOs4jm1+XIpK8=; b=jXdqU4atjCzyamtu7ez4nOxkz+wXOCi8GPst9Jn9VL8kANflJ2TN6fwFWtjM6f3cQ0 9mWkfTakkjSECzcAa2IcX/JmwGL6y2wnIgMviO4l8dHS1K+PCrQ4zFrUsCCSqyKWOPo2 Ikb9xdWSG90TxbojoUnMb+rUR3xMIkm+A9BQsTeOCS41gH0D/qwt7hOBdDbg1dbkfJSR cBN+RbWuc6Oh3wdi7WDpPtleCDCvh0vzbxcZ7iI6Qd4jJ24Y9+1erGs9L5f+P1MwfXXh wsTXNKb5ul0xqNg4QXuHfmTNRFqmv6FySQs3YpYwZOkZs5tc+NflNH5lT9nq1zOheIcd MOzQ==
X-Gm-Message-State: AA+aEWaHzUYHkjPEm0THDQsDcO9gx1PJKcxkHHkZpbghTBVAXYIyt0pG d6kk+G1GZZhHZDd/cq/cgMv8cMGTc6Zdgv13gd0Hbw==
X-Google-Smtp-Source: AFSGD/UV+ZlVhdTVvH1OHsunXb7eklVh1sst11Hqz3jEoj31oXR3TSKVmJOoWHXC3fxjhxVTRM47GQDkqkXmQ9ADc+Y=
X-Received: by 2002:a05:660c:b43:: with SMTP id m3mr25123370itl.126.1546307076019; Mon, 31 Dec 2018 17:44:36 -0800 (PST)
MIME-Version: 1.0
References: <154593193395.11930.16738431366515870255@ietfa.amsl.com> <CACuvLgwCSB13U6rXGLTwpQ-riT+7fi_HyKLD2FjzDexA4u0Rkg@mail.gmail.com> <CADo9JyWAFvBiBqb5oA-vGED1Cpo8F37GzAQhke_=E1ZpJrWdSQ@mail.gmail.com> <1546226168.2302634.1621590656.150FEA52@webmail.messagingengine.com> <b2cc2e81fb2c6226d482cdd9e2cbff0cf33120df.camel@laposte.net>
In-Reply-To: <b2cc2e81fb2c6226d482cdd9e2cbff0cf33120df.camel@laposte.net>
From: David Bird <dbird@google.com>
Date: Mon, 31 Dec 2018 17:44:23 -0800
Message-ID: <CADo9JyWSxWGxKk+EBDsKg76gzKZYhdiXh8dvLnsxEZKi=XWB_A@mail.gmail.com>
To: Nicolas Mailhot <nicolas.mailhot=40laposte.net@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, captive-portals@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fb4908057e5bab24"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/vS8hnehZp3gajA4bEOi1GmVVvu4>
Subject: Re: [Captive-portals] Fwd: I-D Action: draft-ietf-capport-architecture-03.txt
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: Tue, 01 Jan 2019 01:44:40 -0000

Imagine if other network notifications were binary ... "You have no route
to at least one host, but not telling you which one."

I have to agree; the signaling section - without even specifying any real
solution - is only trying to limit any future work .. and not for any
technical reasons, at least not on the network infrastructure side.

I think there are maybe two motivating factors for those pushing the binary
agenda:
- A misguided attempt at enforcing net neutrality - when, in fact, a binary
signaling protocol doesn't solve (or prevent) any net neutrality issues, it
only makes them less transparent (to the network device and user)
- A misguided attempt at limiting the signaling protocol because it is just
easier on the user device side to think binary - when, in fact, nothing is
preventing the UE from treating the "full-disclosure" notification as
something binary (until the device software can think beyond the binary
captive portal)



On Mon, Dec 31, 2018 at 5:47 AM Nicolas Mailhot <nicolas.mailhot=
40laposte.net@dmarc.ietf.org> wrote:

> Le lundi 31 décembre 2018 à 14:16 +1100, Martin Thomson a écrit :
> > no hats...
> >
> > On Fri, Dec 28, 2018, at 06:14, David Bird wrote:
> > > I, for one, think "Document that the signaling protocol does not
> > > provide
> > > mechanisms for non-binary blocking." is where IETF tries to become
> > > a some
> > > sort of legal authority...
> >
> > The IETF describes what consenting protocol participants can do.  So,
> > I'm fairly sure that legal authority has no bearing on
> > this.  However, your point remains a good one.
>
> Let's be honest and cut the crap.
>
> Binary blocking does not exist. No one with an ounce of technical know-
> how will ever implement such a thing.
>
> A plane/train portal will provide free access to the train/plane live
> location map, a school will provide free access to the school library
> website and class schedules, a corp will provide free access to the
> corp internal webapps, an internet cofee will provide free access to
> its commercial portal with remaining time counter, parental controls
> will provide free access to Disney comics, and so on. Tech stuff
> documentation, including portal documentation, is online by defaut
> nowadays. Even lightbulbs and toasters can have their own webpage.
> Pretenting a network equipment will not in 2018 is utter dishonest
> technical bullshit. That's not consensus at work that's capture by
> special interests.
>
> Normalising binary blocking is as idiotic as normalising that home
> doors have no locks because some ultra marginal rural neighborhoods can
> afford not to lock their doors (Guess what? They buy doors with locks
> like everyone else. They just choose not to use them. And even when
> they do not lock their main door they *will* lock the shed containing
> dangerous sharp instruments in presence of small children).
>
> When the IETF tries to pretend, that the default is different from the
> one any last year IT student will naturally implement, it is taking a
> political not technical stance. It is sabotaging its own standards. It
> is discrediting itself as a neutral technical authority.
>
> --
> Nicolas Mailhot
>
> _______________________________________________
> Captive-portals mailing list
> Captive-portals@ietf.org
> https://www.ietf.org/mailman/listinfo/captive-portals
>