Re: [Captive-portals] Last Call: <draft-ietf-capport-architecture-08.txt> (CAPPORT Architecture) to Informational RFC

Bob Harold <rharolde@umich.edu> Tue, 12 May 2020 12:32 UTC

Return-Path: <rharolde@umich.edu>
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 BB7C43A0885 for <captive-portals@ietfa.amsl.com>; Tue, 12 May 2020 05:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 dxxt998PF6Bw for <captive-portals@ietfa.amsl.com>; Tue, 12 May 2020 05:32:47 -0700 (PDT)
Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (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 5E2463A0864 for <captive-portals@ietf.org>; Tue, 12 May 2020 05:32:47 -0700 (PDT)
Received: by mail-lj1-x242.google.com with SMTP id u20so3128130ljo.1 for <captive-portals@ietf.org>; Tue, 12 May 2020 05:32:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qf9jqCpradgLrYP1xPHZ9PsMIY+rhg3iZuTzzhqjW40=; b=XJn20fgbDxxldsuaMoV7t4mRxZZcqQsJDMVA44xrafU712cgQewqcpC2+OlzOlUPl8 pXPhlQl5XLA6fpnROfVnVKNr8l3OBSDBg7vvJE6s31NzkgWh7FzR0qPZsqpO9LpcUeBo /zVyy/aSWCWvpvB2b+FM2bP1HCkIHZeVsvrDygviKP+PdhyhS/vaGHp9irtTWCpLm5hI PeJh+SqyBcH6oF2/DCyhzWjkDTsFKgiJx24OEDiB3jqjwyho3B+F0Ryo82BCJ6j0tQ7d dUifBVrO8mtRQUbzbqef2OuT8pFqYBG2KMmJnJu8IAJeiYk8IXKFhyxQwpbaw0jyJLUG ME9w==
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=qf9jqCpradgLrYP1xPHZ9PsMIY+rhg3iZuTzzhqjW40=; b=T/T+ohmIEskc+AIL50bVIyL9xT0wckgFjKxTKBniNr91JmYLZfyoMT7iD1KEplXQF0 0b/1xrm7Va+7vyLM0hyTdUDPGnACKj/7CTyBWj3NpAj3VuphuLH5qHgVb0jKVlIWfQQE 1MKghyNuUmyZ0h3iu+VY+1MM+HU3ylM/hIeR41lGUbaenocCfYWtzDv+SjTngIJKyAUW 79iusIGKKcuHX7w3cASXtuAhAKK7/z4Yr4xmjzwhWs850BIlX//NwvP7bmHvfd+2wyKq 2d8emJXKSrBGjUx7FD0JEqNCHZaM8taVgEu09/e7CGngzhYCGHXI+cg4Pc2kgFz4wkoQ u14w==
X-Gm-Message-State: AOAM532BJ/7t/fUlkQzpNqsLDvrbl0pspVdkBX4BqdMid97NDTKM+4v4 3rSxJoxKwR58xzEaqliwHRK6viYfDJS1M4hD1wr69g==
X-Google-Smtp-Source: ABdhPJxLcWFvbTS1UQRDl/yAZRmKcmycWGYl8FBplL7QHl+pJHih9rn4K3wDySYtZA1XipfExOIQgOudX3T46LBbnsc=
X-Received: by 2002:a2e:8512:: with SMTP id j18mr13746193lji.201.1589286765414; Tue, 12 May 2020 05:32:45 -0700 (PDT)
MIME-Version: 1.0
References: <158921606984.25307.13122538106790691765@ietfa.amsl.com> <CA+nkc8Axa4QrmQH9SYug-eBG+UuUZ-vvys=itkCUs-sVLRDjHA@mail.gmail.com> <CACuvLgww+zSWHRdQ5zs94ARJcf9J2Rzx4Ob6fpoaQquuVgR8ww@mail.gmail.com>
In-Reply-To: <CACuvLgww+zSWHRdQ5zs94ARJcf9J2Rzx4Ob6fpoaQquuVgR8ww@mail.gmail.com>
From: Bob Harold <rharolde@umich.edu>
Date: Tue, 12 May 2020 08:32:34 -0400
Message-ID: <CA+nkc8CrRp+C_pFopgWRNCoCYD8s0HGd-_Xhs-ACfm6279shNA@mail.gmail.com>
To: Kyle Larose <kyle@agilicus.com>
Cc: last-call@ietf.org, IETF-Announce <ietf-announce@ietf.org>, draft-ietf-capport-architecture@ietf.org, capport-chairs@ietf.org, captive-portals@ietf.org, Martin Thomson <mt@lowentropy.net>, barryleiba@gmail.com
Content-Type: multipart/alternative; boundary="00000000000019662c05a572a97c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/UqsfKeEhDJRNyjz-0AO_QW_pcag>
Subject: Re: [Captive-portals] Last Call: <draft-ietf-capport-architecture-08.txt> (CAPPORT Architecture) to Informational RFC
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, 12 May 2020 12:32:50 -0000

On Tue, May 12, 2020 at 8:10 AM Kyle Larose <kyle@agilicus.com> wrote:

> Hi Bob,
>
> Thanks for the quick feedback.
>
> > I am curious why section 3.4 does not consider the MAC Address as a
> possible identifier?
>
> Its omission doesn't mean that the MAC Address is not a valid
> identifier. One should evaluate it using the criteria provided in 3.2
> and 3.3. When I wrote the skeleton of this section, I left the MAC
> Address out more to keep the section short than anything, though I did
> consider adding it.
>
> Bob, do you think the MAC address needs to be considered in this
> section for completeness?
>


I won't argue too much if you decide to leave it out, but it seems like the
most obvious identifier, and is used by many things, so it would be good to
list its pros and cons.



> How does the capport wg feel as a whole about this question?
>


I am also wondering the same thing.


Thanks,
>
> Kyle
>
> On Mon, 11 May 2020 at 13:36, Bob Harold <rharolde@umich.edu> wrote:
> >
> > I am curious why section 3.4 does not consider the MAC Address as a
> possible identifier?
> >
> > --
> > Bob Harold
> >
> >
> > On Mon, May 11, 2020 at 12:56 PM The IESG <iesg-secretary@ietf.org>
> wrote:
> >>
> >>
> >> The IESG has received a request from the Captive Portal Interaction WG
> >> (capport) to consider the following document: - 'CAPPORT Architecture'
> >>   <draft-ietf-capport-architecture-08.txt> as Informational RFC
> >>
> >> The IESG plans to make a decision in the next few weeks, and solicits
> final
> >> comments on this action. Please send substantive comments to the
> >> last-call@ietf.org mailing lists by 2020-05-25. Exceptionally,
> comments may
> >> be sent to iesg@ietf.org instead. In either case, please retain the
> beginning
> >> of the Subject line to allow automated sorting.
> >>
> >> Abstract
> >>
> >>
> >>    This document describes a CAPPORT architecture.  DHCP or Router
> >>    Advertisements, an optional signaling protocol, and an HTTP API are
> >>    used to provide the solution.  The role of Provisioning Domains
> >>    (PvDs) is described.
> >>
> >>
> >>
> >>
> >> The file can be obtained via
> >> https://datatracker.ietf.org/doc/draft-ietf-capport-architecture/
> >>
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
>
>