IETF Logo Mail Archive

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

Kyle Larose <kyle@agilicus.com> Tue, 12 May 2020 12:10 UTC

Return-Path: <kyle@agilicus.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 5C8FD3A0645 for <captive-portals@ietfa.amsl.com>; Tue, 12 May 2020 05:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=agilicus.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 iolachxwhZ9J for <captive-portals@ietfa.amsl.com>; Tue, 12 May 2020 05:10:04 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 ED6F73A053E for <captive-portals@ietf.org>; Tue, 12 May 2020 05:10:03 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id k18so4579504ion.0 for <captive-portals@ietf.org>; Tue, 12 May 2020 05:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=agilicus.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/aSRBMFl83oWEoK/uOSNR7M/A5ne8tpFYZT7ERE9+Lw=; b=DjnIpVSDp4/2JQFok4P2ewnD/vnQQ0Z7yzz+cW1RgSBqvqRTQmSGy6UDfq/3LDzCGA ZmbePt2cHlwXDaKsvAN8+KmRV4wiKGF/WKLVBsqXicnwZMWTU8HHPQgMGp4hs5JdWGTF hb5/SZVOIsMwNJGRI+cCRkfqQxODjljNk98g946li/e2N67WW3K+2aqiK6JQVLGGtY71 OrdqMbLf8OUTRg0mGtEVWt03uT4TO0a7RAJC6pKsE7IpMWhDaRZy3ER2mdIPjwZurjHa X35m33OBV2faZLB500g1ER3wwZTu27euf0EemnbeHwRXmFNFgAK2dAv7OuWmCUMk1AtD ZyqA==
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=/aSRBMFl83oWEoK/uOSNR7M/A5ne8tpFYZT7ERE9+Lw=; b=UH0t3lwEI2fZrZe+uklHrjcMKnOJvYBSnwRq19zphaOfSGVp6t2joHBNUAcNXwqtVu XJtDH5AeN4yzbKVmcHnbWaUiVHyrIzgErT4Z2e/bqz70MKatpFLAzxA7DinY2+cxKBhl raZzdPlNUrigeMUghZqekXTxLGTQFdsxu8xrEXuiCuYio4JJka6rTRsOmMOMjjg08iL0 flRIOV2R5QRcFzzV6wi6+eheFa+D5AHLi2W61vc1UJRuSRs99BGjibVcuQG+pkOMuAbo yxBDJwJKkInnARj8tdEDFge3vlTwywqujPO37xJgLQBKowaLemOPoTh4kOzbjEZt4uBm /AWg==
X-Gm-Message-State: AGi0PuYl8T05FgHKRShM/pFtPsJ1bIITe6PNGaHeYDDxNx3GXyKqoj/U 4aSifxbanP6Ea/TbIdfjkhs+mxCDJPalLE6Tw3ru
X-Google-Smtp-Source: APiQypJLmKdp8oC/+dEFg1P7FKinS3QN22+7aoEz8Oujd5IB8hkCV1t2HZTvviOWvAZWIUm+g/jBcXIABD0qmKabCHc=
X-Received: by 2002:a02:a90e:: with SMTP id n14mr19824673jam.97.1589285402977; Tue, 12 May 2020 05:10:02 -0700 (PDT)
MIME-Version: 1.0
References: <158921606984.25307.13122538106790691765@ietfa.amsl.com> <CA+nkc8Axa4QrmQH9SYug-eBG+UuUZ-vvys=itkCUs-sVLRDjHA@mail.gmail.com>
In-Reply-To: <CA+nkc8Axa4QrmQH9SYug-eBG+UuUZ-vvys=itkCUs-sVLRDjHA@mail.gmail.com>
From: Kyle Larose <kyle@agilicus.com>
Date: Tue, 12 May 2020 08:09:52 -0400
Message-ID: <CACuvLgww+zSWHRdQ5zs94ARJcf9J2Rzx4Ob6fpoaQquuVgR8ww@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
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: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/Ej--3YRowqLfF28lvYuEqSJjsVs>
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:10:05 -0000

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?

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

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.
>>
>>
>>
>>
>>
>> _______________________________________________
>> Captive-portals mailing list
>> Captive-portals@ietf.org
>> https://www.ietf.org/mailman/listinfo/captive-portals

v2.23.0 | Report a Bug | By Email