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

Martin Thomson <mt@lowentropy.net> Mon, 11 May 2020 22:46 UTC

Return-Path: <mt@lowentropy.net>
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 4D6783A0D7E; Mon, 11 May 2020 15:46:50 -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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=glJFctXe; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VlcKpOSm
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 YjyIFNkftmAS; Mon, 11 May 2020 15:46:48 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 653EB3A0D7D; Mon, 11 May 2020 15:46:48 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 801A72F9; Mon, 11 May 2020 18:46:47 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Mon, 11 May 2020 18:46:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type:content-transfer-encoding; s=fm2; bh=5D AG6Zq7YEA1+ONiL7/OfHu/GN8LtktKumHXv6kYudM=; b=glJFctXeR4+YvFm8hA BYQkoW30JSwQJZn47iLRlULsjc70Lz3ZVknhrHN+BQeZMPmTlJ3eA1nssFcMreqJ 1tabJkDrf1W8srdurUklES4Wz6Trs5o5PXSWTXAImtmCn1Wg2jvrolnfwK/oquYz fkLm87vFx8HWz6gMLLslNp3kzxzAiTRDz7JKlyI0Ei1gOOm8bfW7ZmaxB12TusNU cXSQb79jZ2FZj53LlP9o2W5YKvN7rZV7cM4Jp9oyDmInKAP7NLjtpoX8chF+/SfW vZBgmj9bnQrOLUyMjdD6KcggEJMaomdwnHmRJKQ71/gGFz/MzI/i0TOJyyOr/hgg w8Mg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=5DAG6Zq7YEA1+ONiL7/OfHu/GN8LtktKumHXv6kYu dM=; b=VlcKpOSmM/yNoAFU9kgw7WDAdHmrb33UcdGcCcCOpzYGXeuGuSpfaojfR AqRI1o2PXUvqD23zXwLUkzNQ93B5gxrQbjeK4R4+NY/DoD5UsUQUdltX10FaaCx0 tpftSfcFucjECkUABSohaannaaugxkdKj929Kr+pRz6O94fTwO6NX+pcqLtkCltQ wruA2oj7wtu0N7pi9etsT7XRiyeb3awVFeoFzK3dF4O3Rb5/aHglOqUUrnSzcMjo RW71udrjzVnnew/WFAjIKSo5RmNjAtToXG+9Bm2C+DDlu4ll3GuaJnFYja809kpA +RKH9a4O6MHHb3sumh9vn/y65C3Fw==
X-ME-Sender: <xms:1tW5XtbIY3ZN6Cb2zipyJj1Msoqpv2gMi4S9VZ7mQaO3kHY7MBVJ-g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrledugddufecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecugg ftrfgrthhtvghrnhepueehiedtgfefteeltdfhffdvffffgeevkeduuefhleekudektdek gedtgfdvuedvnecuffhomhgrihhnpehivghtfhdrohhrghdptghishgtohdrtghomhenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhho figvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:1tW5XqsK85zw_YCRaAbPs0JfPW6-HrVarnCQ3eW_fRQ-YuWmJm5-Kw> <xmx:1tW5XsqD7WSdjC1HTXn3TFKGgp1A79ZA9czWjgsnvb3rFijJml6zGw> <xmx:1tW5XqQReP9SZqRiBtMZ4PqvybnR-bRSQbciYnewN6VIA1vvbFki8Q> <xmx:19W5XoAoLh2I8B30oz3wOfCUGHoGBGQdBzzmGxzcgCEVAXOsuJtmyA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id A5821E00AA; Mon, 11 May 2020 18:46:46 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-413-g750b809-fmstable-20200507v1
Mime-Version: 1.0
Message-Id: <700f3376-1119-4b73-b31a-4739ee691aae@www.fastmail.com>
In-Reply-To: <7494D1C3-0E14-4522-BD94-546CCE2DB047@commscope.com>
References: <158921606984.25307.13122538106790691765@ietfa.amsl.com> <CA+nkc8Axa4QrmQH9SYug-eBG+UuUZ-vvys=itkCUs-sVLRDjHA@mail.gmail.com> <7494D1C3-0E14-4522-BD94-546CCE2DB047@commscope.com>
Date: Tue, 12 May 2020 08:46:27 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: "Tirupachur Comerica, Subash" <subash.tirupachurcomerica@commscope.com>, "last-call@ietf.org" <last-call@ietf.org>
Cc: "capport-chairs@ietf.org" <capport-chairs@ietf.org>, "draft-ietf-capport-architecture@ietf.org" <draft-ietf-capport-architecture@ietf.org>, "captive-portals@ietf.org" <captive-portals@ietf.org>, "barryleiba@gmail.com" <barryleiba@gmail.com>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/S9ycfM5JU-G2I-DrQZDNIchiWlU>
Subject: Re: [Captive-portals] =?utf-8?q?Last_Call=3A_=3Cdraft-ietf-capport-a?= =?utf-8?q?rchitecture-08=2Etxt=3E_=28CAPPORT_Architecture=29_to_Informati?= =?utf-8?q?onal_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: Mon, 11 May 2020 22:46:50 -0000

Editors,

I've opened a few issues on the comments Subash indicated were still pending.  I think that we can take these as last call comments in the usual fashion.  I don't see a pressing reason to update the draft, but it would be nice if you could take a look at the remaining items to see if there is any action required.

On Tue, May 12, 2020, at 03:50, Tirupachur Comerica, Subash wrote:
>  
> Hi,
> 
> Sorry, I had sent these comments sometime back, a few are still valid.
> 
> Could you please take care of these?
> 
> 
> Thanks,
> 
> Subash
> 
> 
> 
> *From: *"Tirupachur Comerica, Subash" <subash.tirupachurcomerica@commscope.com>
> *Date: *Thursday, April 30, 2020 at 4:19 PM
> *To: *"captive-portals@ietf.org" <captive-portals@ietf.org>
> *Subject: *AD review of draft-ietf-capport-architecture-07
> 
> 
> Hi,
> 
> I was reviewing this AD and found a few discrepancy needing 
> clarifications, couple of them may just be editorial in nature.
> 
> Appreciate your response on this, thanks.
> 
> 
> Thanks,
> 
> Subash
> 
> 
> *_Section 1.2_*
> 
> Captive Network and Captive Portal are used interchangeably, so do we 
> define captive portal or network or both? – [Pending]
> 
> 
> *_Section 2.3_*
> 
> At minimum, the API MUST provide: (1) the state of captivity and (2) a 
> URI for the Captive Portal Server. – [Pending]
> 
> - However, in draft-ietf-capport-api, section 5: API State Structure, 
> only "captive" (boolean): is mandatory whereas "user-portal-url" 
> (string): is optional. One of these two drafts may need an update for 
> consistency.
> 
> *_ _*
> 
> *_Section 2.6 Component Diagram_*
> 
> Although the Provisioning Service, API Server, and Web Portal Server 
> functions are shown as discrete blocks, they could of course be 
> combined into a single element. – [Pending]
> 
> - Here may be we can add the [Captive Portal Enforcement] as well, for 
> eg: API Server, Web Portal Server and Enforcement can co-exist on a 
> single WiFi Access-Point using ACLs. Also there is a feeble reference 
> to this co-location in Section 3.4.1
> 
> 
> *_Section 3 Captive Portal Signal_*
> 
> Is Enforcement Device defined anywhere else? Is it same as Captive 
> Portal Enforcement(I guess so) Or does it coordinate with it? – 
> [Resolved, Please ignore]
> 
> 
> 
> *From: *Captive-portals <captive-portals-bounces@ietf.org> on behalf of 
> Bob Harold <rharolde@umich.edu>
> *Date: *Monday, May 11, 2020 at 10:35 AM
> *To: *"last-call@ietf.org" <last-call@ietf.org>
> *Cc: *"capport-chairs@ietf.org" <capport-chairs@ietf.org>, 
> "draft-ietf-capport-architecture@ietf.org" 
> <draft-ietf-capport-architecture@ietf.org>, "captive-portals@ietf.org" 
> <captive-portals@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, 
> "barryleiba@gmail.com" <barryleiba@gmail.com>, Martin Thomson 
> <mt@lowentropy.net>
> *Subject: *Re: [Captive-portals] Last Call: 
> <draft-ietf-capport-architecture-08.txt> (CAPPORT Architecture) to 
> Informational RFC
> 
> 
> 
> 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/ <https://secure-web.cisco.com/1yVzqJ3UqY3xwLQUGHinMzu-7twa12PiLIN7EN50B62FLD0cXno02n3f_Qw7DSpKpG96CA7TKBLzu9xzC6TVQejhSfGo-jrF8DNmSa3LVszDOuk89O1tF28heTpZxo-Zl4Kzk3DxQoD5Hc8fDnwaLz69x04aBTgzTGR2Tf9ZMouiJgl4PjT97QOV7tu7viXpNVyNfM-2molaELtIJWJd00DqIJTzR2Hap7yETyceSjQTihOQh7tPi056W8nOWCQ-MxwbxsGzR5V37Soo1SFiKSaR_KHKYhK_NLd4ys-MQ_bKZmZiS_YEiEQX_q0lLjmFgTrqjGvQxzlOj0gwI4zthZQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-capport-architecture%2F>
> > 
> > 
> > 
> >  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 <https://secure-web.cisco.com/1luUyQqfEnnX25r5RvmYXc4O6JMe744dFK_VSJQto5cvtJVqN7Y0Ie7SkRZBkDnAUWnL8L3b4ifd7pTzCT-EsrZmZhOLnLmd_gJDefmDNmw8a8wnbkHiR12asEIcSP9COhQWmnSY75DStoZ7N9Bidi67LQuNxiFexwf8r9J6F6QHrpMpgDgnqiyNKBaJcIC6GmF8UsF3j95f2eFjpdr_0ttHQuXj_XrxTJebBxaS3EdYg8OZsH713lH0DH-VYJ0a_IXiATDxiGaA7gvKppncYKLUo1Pi-xZ7HgL6prLTkzjLEwRFRGlYdkwrDLKV6zUZcbT23_4lyApm-XMaOQo4KZEFyQOebJB-U33Nrqn2nO7w/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcaptive-portals>
> 
> _______________________________________________
> Captive-portals mailing list
> Captive-portals@ietf.org
> https://www.ietf.org/mailman/listinfo/captive-portals
>