Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

"Brzozowski, John" <John_Brzozowski@comcast.com> Mon, 17 July 2017 12:29 UTC

Return-Path: <John_Brzozowski@comcast.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F0C1131B51 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 05:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 lY5XARgNGSGA for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 05:29:46 -0700 (PDT)
Received: from vaadcmhout01.cable.comcast.com (vaadcmhout01.cable.comcast.com [96.114.28.75]) (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 64D62131668 for <v6ops@ietf.org>; Mon, 17 Jul 2017 05:29:46 -0700 (PDT)
X-AuditID: 60721c4b-719ff70000000a8e-bf-596cadb7c291
Received: from VAADCEX11.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id FC.03.02702.7BDAC695; Mon, 17 Jul 2017 08:29:44 -0400 (EDT)
Received: from VAADCEX09.cable.comcast.com (147.191.102.76) by VAADCEX11.cable.comcast.com (147.191.102.78) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 17 Jul 2017 08:29:42 -0400
Received: from VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0]) by VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0%19]) with mapi id 15.00.1293.002; Mon, 17 Jul 2017 08:29:42 -0400
From: "Brzozowski, John" <John_Brzozowski@comcast.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, IPv6 Ops WG <v6ops@ietf.org>
CC: Jim Martin <jim@daedelus.com>, Russ Housley <housley@vigilsec.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, Alissa Cooper <alissa@cooperw.in>, Randy Bush <randy@psg.com>
Thread-Topic: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/tSiyacM1/hfIEykN3ouQq0Z36JX77qAgABj3QA=
Date: Mon, 17 Jul 2017 12:29:42 +0000
Message-ID: <B1504A18-4F95-42A9-B97A-6149D54A3A54@cable.comcast.com>
References: <7643C1DC-76A3-4652-9BB1-D0D42801F37E@consulintel.es> <CAEqgTWYOe=jWp=zVZNLx6DjKjNpPTYaq2jmjryudrGZHKZNq6g@mail.gmail.com> <A5D0385C-F755-4B44-86D8-6E618E77193F@consulintel.es> <CAPt1N1kroh2cPkTr8HRfNjLTdG0hkC1oQsUZdhQzQA5tA9-xug@mail.gmail.com> <9AF791E9-1E12-425E-93A4-2913E2D18CBA@consulintel.es> <CAPt1N1kU4cpVCsp7W3XNAZupYqjTWVH+BNp9bwtznnWD_uP2oQ@mail.gmail.com> <CAEqgTWZzZW0wKggDXjY=-aMfDxzd5-GoRqju1829XwY3aHQuYg@mail.gmail.com> <0FAF1E05-DA4B-47BF-95F7-7EFCD1BED9B0@cable.comcast.com> <42188852-BBEB-4D75-967F-4BED79BBBCAE@consulintel.es>
In-Reply-To: <42188852-BBEB-4D75-967F-4BED79BBBCAE@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C9FCBE52338F0F448E0AE5AE43F367BE@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11Uf0wbVRzPu2vpgX1yu9L2rWMEuojBTOiiaZrN4MQldswmsC3MNlngKCft KG3ttfxYTMQtIoIm/rEJdEbNAjNjA6eigJlz6xo32BbCD3FTNlnWkIHLgmGRwMR5766Fq3/1 m8/nvc/n8/305SiSGUozUG5vkAt4WY8xJU1Rwe+2PD/Y67GbRpvMlvbrq8Ayf/+WyjIVJS2r VxZJy+x7c4Qleu6G0nLt5x/JnSpr308l1kexOcLa+tcEYR0K31ZZu7qWCevxzhPA2jP9SFmi cqS9VMV53HVcoKCwIs3VcewK4Y++3vBH301lE7ha3ApSKUS/iGK37hCtII1i6AECjXTPKDHB 0BcBuvd+kUQMA9T8ySqBiRTajPov/a7CcwZ9EE2Nfw/wIZIeBGj1wbQCExp6L1q6PqaUDu1D A82L8Qvb0fC5X8QzCvoZNDnbT+IZ0rvQwJ2HpOR2UYHaRk+Jbql0EZo405WCZ0Dr0NLIWREn aT36LfY5Ie1Ao67zo6Q0a9HcvX9FYy2dj6YWTiskfCu68WsMSLMJfdd9IY7noJXPJgV9StDM Q1/9UCCN21F/c6nklIOOtd1VSTE3oOHOWPymHl2ODio/BpvCskDhdaHwulBYJhSWCX0BlD0g q45lq5y1Ll8oaNqW72QrPVy+01frZPkg/v0G4PcRyNwzCPqWX4sAmgJGNbz8qcfOKNk6vrE2 AmoowqiFYyk1dubpSl9Vo4vlXeWBkIfjjRkws004CdfgypCnxmiALWcFVLOGerl63sMFhQdp zIInsZB+jeNDvN/tdPtCfHko4IkARJGCbE4vlq1iGw9zAZ9kFgGbKIVRD3OHDtkZupoNcjUc 5+cCCbaeoowImrHzhgBXzTW86fYEE7Rwr7VTYGg5I4bdDC1Rt53RyQlZ3hy4A9MGOf3/yASV GgHVlFrI/bKYm/eztby7Om6tgR/gktQJVLTdCLeeEUAmAcosN8MylVCRLkEl242ANkCFO5b/ Jqj+x1eXCEbh9Xk5gx6+jfVofMkV8q4tbtDB4dIKO5MuI3AAQyb8EONaGb6ewZAN72N2o4xN jpH4rMwDp/BiNDAb964WPjrrezOQxeBTcVBcG8E3xD8ojsm2zoR2vLU2ziS7zQv1EkK9GptY b5ANyuudton1xtF4veM2sd44mFRvO6Z0CSrZydAEXn18hDhe3D7tsN3cc9Rc8JH6ybN+5T8T kzOuC66jK+NTW961lelsvXlHHHtfOFTomCkbW0gfGpk4XbIjNa+ne/GV5T/3O4oWlPUZ7+wy NYRzrbmFLWNfd6w8aDmlun3gid2Rv/Pg7Anz+W9nsk6W39Wmj5s0Bw5nX7pWt6/44e4v50vf Mip4F7vtOTLAs/8BeqR6LcwFAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BBL3qrEQkSOpiPbLw9jy2tXjjqo>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 12:29:48 -0000

The below is not true, this is exactly what some of the author’s in the draft are doing:

“In the real world, you will not disable IPv4 in the LANs of end-users or enterprise customers (at least not now, may be in 3-5 years from now).”

The I-D that we wrote is based on real deployment experiences, not fantasy or sci-fi.

John
+1-484-962-0060

-----Original Message-----
From: v6ops <v6ops-bounces@ietf.org> on behalf of JORDI MARTINEZ <jordi.palet@consulintel.es>
Reply-To: JORDI MARTINEZ <jordi.palet@consulintel.es>
Date: Monday, July 17, 2017 at 10:17
To: v6ops <v6ops@ietf.org>
Cc: Jim Martin <jim@daedelus.com>, Russ Housley <housley@vigilsec.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, Alissa Cooper <alissa@cooperw.in>, Randy Bush <randy@psg.com>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

    However, we have different ways for doing the same, and we should go for the one that has less impact and it is more realistic.
    
    In the real world, you will not disable IPv4 in the LANs of end-users or enterprise customers (at least not now, may be in 3-5 years from now). This is what IETF need to test now. IPv6 only with IPv4 as a service (which is 464XLAT).
    
    Again, and I’m for-IPv6, but being realistic, not considering sci-fi of turning down IPv4 in our customer networks (now).
    
    Regards,
    Jordi
     
    
    -----Mensaje original-----
    De: v6ops <v6ops-bounces@ietf.org> en nombre de "Brzozowski, John" <John_Brzozowski@comcast.com>
    Responder a: <John_Brzozowski@comcast.com>
    Fecha: lunes, 17 de julio de 2017, 10:14
    Para: Noah <noah@neo.co.tz>, Ted Lemon <mellon@fugue.com>
    CC: Jim Martin <jim@daedelus.com>, IPv6 Ops WG <v6ops@ietf.org>, Alissa Cooper <alissa@cooperw.in>, Russ Housley <housley@vigilsec.com>, Randy Bush <randy@psg.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
    Asunto: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
    
        Agree with Noah and Ted.
         
        Note the I-D explicitly documents that a fallback, dual stack SSID must remain available as Noah mentions below.
         
        I fail to see how doing this will harm or discriminate.
         
        We do need to eat our own dogfood, otherwise we are hypocrites.
         
        John
        
        +1-484-962-0060
         
        From:
        v6ops <v6ops-bounces@ietf.org> on behalf of Noah <noah@neo.co.tz>
        Date: Monday, July 17, 2017 at 09:01
        To: Ted Lemon <mellon@fugue.com>
        Cc: Randy Bush <randy@psg.com>, v6ops <v6ops@ietf.org>, Alissa Cooper <alissa@cooperw.in>, Russ Housley <housley@vigilsec.com>, Jim Martin <jim@daedelus.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
        Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
        
         
        
        FWIW and to cater for all, would a fallback dual stack SSID work for the status quo while this 2nd v6 SSID is also experimented upon which is a great idea considering this is IETF.
        
         
        
        Noah
        
        
         
        On 17 Jul 2017 9:54 a.m., "Ted Lemon" <mellon@fugue.com> wrote:
        
        I don't think this is a social justice issue.   Does the IETF think that IPv6 works, or not?   If we think it works, and we have been working for what, 20 years, to make it work, and we have designed all this great
         transition tech, then why on earth would we not want to use it?   This isn't "one draft."   This is roughly half the work of the IETF for the past two decades.
        
         
        On Mon, Jul 17, 2017 at 8:51 AM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
        
        So we agree to change the rules so that we use this network for every ID that want to experiment with it? Otherwise we discriminate among different authors …
        
        I think is a really bad precedent.
        
        Regards,
        Jordi
        
        
        -----Mensaje original-----
        De: Ted Lemon <mellon@fugue.com>
        Responder a: <mellon@fugue.com>
        Fecha: lunes, 17 de julio de 2017, 8:48
        Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
        CC: IPv6 Ops WG <v6ops@ietf.org>, Jim Martin <jim@daedelus.com>, Randy Bush <randy@psg.com>, Suresh
         Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.com>, Alissa Cooper <alissa@cooperw.in>
        Asunto: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
        
            I don't actually know what the goal of the IETF network is other than to provide connectivity.   Because of the vicissitudes of hotel topology, it is often the case that IETF participants experience issues with the
         network at least once or twice per IETF despite the best efforts (and they are quite exceptional) of the NOC team.   I do not really see what the damage is that you are hoping to protect against here.   Users who don't read the NOC announcement?   No sympathy. 
          Sorry.
        
        
        
        
        
        **********************************************
        IPv4 is over
        Are you ready for the new Internet ?
        http://www.consulintel.es
        The IPv6 Company
        
        This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or
         use of the contents of this information, including attached files, is prohibited.
        
        
        
        _______________________________________________
        v6ops mailing list
        v6ops@ietf.org
        https://www.ietf.org/mailman/listinfo/v6ops
        
        
        
        
        
         
        
        
        _______________________________________________
        v6ops mailing list
        v6ops@ietf.org
        https://www.ietf.org/mailman/listinfo/v6ops
        
        
        
        
        
        
        
        _______________________________________________
        v6ops mailing list
        v6ops@ietf.org
        https://www.ietf.org/mailman/listinfo/v6ops
        
    
    
    
    **********************************************
    IPv4 is over
    Are you ready for the new Internet ?
    http://www.consulintel.es
    The IPv6 Company
    
    This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
    
    
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops