IETF Logo Mail Archive

Re: [Captive-portals] option 160 conflict

Tommy Pauly <tpauly@apple.com> Mon, 23 December 2019 17:58 UTC

Return-Path: <tpauly@apple.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 2F1D6120CAA for <captive-portals@ietfa.amsl.com>; Mon, 23 Dec 2019 09:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 y-jYWPme_oLx for <captive-portals@ietfa.amsl.com>; Mon, 23 Dec 2019 09:58:15 -0800 (PST)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5B13120CA2 for <captive-portals@ietf.org>; Mon, 23 Dec 2019 09:58:15 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id xBNHqHYH007611; Mon, 23 Dec 2019 09:58:11 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : content-type : content-transfer-encoding : from : mime-version : subject : date : message-id : references : cc : in-reply-to : to; s=20180706; bh=AxL9Hg6J01CyUu8Ntr5XzuVq8vVFmlHR8bpiFZlqb84=; b=sGU74c4obmet/lCrDWrnCzp9iMCIcgQKHIa+wHrTbFDY4WR6gEe0AG4hJ89gXiZshdd2 gD8B9ljfMb5mz2oU5Cn0tJlYo4dl4+e704pK669tvuSLBKLOza5HIFRfsVURruFn9/Gg qWAkAPAJtLGWrOHvJhYIZeT78KTOyIAxAhFikoznk+pboAEi1AZzZksHS3M7kpLNwa2B c81iIUce2TKbuWRetth3SO2E8ObCM55kbgIcNp32t9PZmYvuG3tXhgA29TJvEPGlb2uR hkSaUFP7dR969uGE7Lmwx+tZf5uOMwd1D/T4qGRg6lL2Q2ugCAQJ5lnZJQDsbwQOGFRM wg==
Received: from ma1-mtap-s02.corp.apple.com (ma1-mtap-s02.corp.apple.com [17.40.76.6]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2x1gxw29kj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 23 Dec 2019 09:58:11 -0800
Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s02.corp.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0Q2Z00DYA8KYQE20@ma1-mtap-s02.corp.apple.com>; Mon, 23 Dec 2019 09:58:11 -0800 (PST)
Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0Q2Z00G008K2LT00@nwk-mmpp-sz09.apple.com>; Mon, 23 Dec 2019 09:58:10 -0800 (PST)
X-Va-A:
X-Va-T-CD:
X-Va-E-CD:
X-Va-R-CD:
X-Va-CD: 0
X-Va-ID: c9e25f10-02f2-47fa-8369-de4ddb63554c
X-V-A:
X-V-T-CD: 08daaeda8696783f7bdde9d2f4757251
X-V-E-CD: ab4b98dd9665150474513f41f5c654ad
X-V-R-CD: bc65fba3c5fd2e58404201a87315dfaf
X-V-CD: 0
X-V-ID: 69089bd2-bafa-4e62-919d-687629627800
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-12-23_07:,, signatures=0
Received: from [17.234.76.43] (unknown [17.234.76.43]) by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0Q2Z002UJ8KWQO10@nwk-mmpp-sz09.apple.com>; Mon, 23 Dec 2019 09:58:09 -0800 (PST)
Sender: tpauly@apple.com
Content-type: multipart/alternative; boundary="Apple-Mail-7B18A614-CFBB-44D1-8C9D-5F901C6D29AC"
Content-transfer-encoding: 7bit
From: Tommy Pauly <tpauly@apple.com>
MIME-version: 1.0 (1.0)
Date: Mon, 23 Dec 2019 09:58:08 -0800
Message-id: <150E4F32-236A-4D59-B74C-36BF523DCE55@apple.com>
References: <CAKD1Yr2yvqqw=APnyAb=gygR5KK6U7tcx3STGa9e6a8kJYO03w@mail.gmail.com>
Cc: "Bernie Volz (volz)" <volz@cisco.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "captive-portals@ietf.org" <captive-portals@ietf.org>, Warren Kumari <warren@kumari.net>
In-reply-to: <CAKD1Yr2yvqqw=APnyAb=gygR5KK6U7tcx3STGa9e6a8kJYO03w@mail.gmail.com>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (18A181)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-12-23_07:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/7ZABJuTUDOIz-G4Ntwdytk_NwbY>
Subject: Re: [Captive-portals] option 160 conflict
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, 23 Dec 2019 17:58:17 -0000


> On Dec 21, 2019, at 7:48 PM, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org> wrote:
> 
> 
>> On Sat, 21 Dec 2019, 07:53 Bernie Volz (volz), <volz@cisco.com> wrote:
>> 1) It would not really remove the overlap for a long while (until all of the clients that used the "old" 160 Capport option are upgraded). So, devices will still need to deal with it for a long while.
> 
> 
> Do any clients or networks actually implement 160 to mean capport? I know that iOS and Android, which seem most interested in this option, do not yet.

I am not aware of anything using the option yet. iOS does not use it; we used it for interop testing, but that is not in production code. 
> 
> If they do not, the right thing to do would be to get a new option code, and do so as soon as possible so the implementations that are being written this year can immediately start using the new one.

I would also urge that if we want a new code, we allocate it soon so that the implementations can quickly test it out and ship the right value. 

Tommy

> _______________________________________________
> Captive-portals mailing list
> Captive-portals@ietf.org
> https://www.ietf.org/mailman/listinfo/captive-portals

v2.23.0 | Report a Bug | By Email