IETF Logo Mail Archive

Re: [v6ops] Outcomes from v6ops@IETF98

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sun, 02 April 2017 21:12 UTC

Return-Path: <prvs=1265f0bd07=jordi.palet@consulintel.es>
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 00758129548 for <v6ops@ietfa.amsl.com>; Sun, 2 Apr 2017 14:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 aw2Lkip6Oby8 for <v6ops@ietfa.amsl.com>; Sun, 2 Apr 2017 14:12:54 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6706B1292FC for <v6ops@ietf.org>; Sun, 2 Apr 2017 14:12:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491167520; x=1491772320; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=r3r9NReRFVSJV+FdJu37EmABi ocsOgbjrmm6vxHNLsc=; b=NbTHNsxcW4gluu/ppelkbzjyojlOpJwm2v6syiV+i 91x5K+z55mZ8ckVDLKrdQ/omEteohDgFdXv3ZBC4H4PRYdX4a93MVbbTS9Wtwdge /TKqlLRli/1XxCiP+Z68Mu64DFos64qmy3BSUypCgf0Pf6m2kjRNVJu4PE28LRxq f0=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=K1kaoJbctobRQ66FqzRUIX0FW6a2O7hN4lZQv6YmFQmHzURRYJvju9aa71CT lo5SYIgNPADDCBQDuE8EcsYzuqqEnAogauh6K+aCdG2XLY8wuOmW5S20H aIQnGnzqHHHLx/mZnec+lY8DRISsbgPd87JWJu4qVnfBGiGo1YVZ88=;
X-MDAV-Processed: mail.consulintel.es, Sun, 02 Apr 2017 23:12:00 +0200
X-Spam-Processed: mail.consulintel.es, Sun, 02 Apr 2017 23:11:59 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005400661.msg for <v6ops@ietf.org>; Sun, 02 Apr 2017 23:11:58 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170402:md50005400661::jMO/pCLKMJVtdczO:00002EKz
X-Return-Path: prvs=1265f0bd07=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Sun, 02 Apr 2017 23:11:54 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops list <v6ops@ietf.org>
Message-ID: <AF51B5EE-C7E9-40A3-8397-DF27BC077400@consulintel.es>
Thread-Topic: [v6ops] Outcomes from v6ops@IETF98
References: <6C1E351B-F8B6-4BC2-890D-993A1F081226@gmail.com>
In-Reply-To: <6C1E351B-F8B6-4BC2-890D-993A1F081226@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gA4znWXp-Gyrs_LPl3EsdcD8N6s>
Subject: Re: [v6ops] Outcomes from v6ops@IETF98
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: Sun, 02 Apr 2017 21:12:59 -0000

Hi Fred,

+1 for the new chapter.

Regarding the interim meeting, do we really need that? I don’t think so, and for some of the participants, it may be an extra cost that not everybody can afford, or for some may be even difficult to attend even remotely if organized with so short notice as May with already a few meetings organized from long time ago … unless, is a short meeting that we can coordinate for example with RIPE (8-12 May, Budapest) or LACNIC (22-26 May, Foz do Iguaçú) meetings which are being hold also in May, and they can spare a meeting room for us for 3-4 hours? Of course, this is only valid if many of the intended participants are also there.

Regarding the new WG items, I have the same understanding that the 3 documents have been adopted. In fact, I just submitted a new version as WG 00 …

Regards,
Jordi
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Fred Baker <fredbaker.ietf@gmail.com>
Responder a: v6ops list <v6ops@ietf.org>
Fecha: miércoles, 29 de marzo de 2017, 22:40
Para: v6ops list <v6ops@ietf.org>
Asunto: [v6ops] Outcomes from v6ops@IETF98

    I have attached a pdf of the proposed charter as it ended this afternoon. I invite public commentary (to v6ops@ietf.org), and if you support using it as it stands, please say so..
    
    One question I intended to ask and didn't get to was the appropriateness of an interim meeting, perhaps in mid-May. It would primarily address draft-ietf-v6ops-ula-usage-considerations and draft-petrescu-v6ops-ipv6-power-ipv4, and potentially draft-ietf-v6ops-design-choices if it is updated. There is an argument for leaving these to IETF 99, and potentially booking a second slot for that discussion. Your opinions?
    
    We have two WGLCs in progress or about to be so. The WGLC on draft-ietf-v6ops-unique-ipv6-prefix-per-host, which Ron opened on 14 March, will end on 9 April. We will then open a WGLC on draft-ietf-v6ops-v4v6-xlat-prefix, to end 23 April.
    
    I believe that the discussion today supported adoption of the following as working group drafts:
    draft-ali-ipv6rtr-reqs (as draft-ietf-v6ops-ipv6rtr-reqs)
    draft-palet-v6ops-rfc7084-bis (as draft-ietf-v6ops-rfc7084-bis)
    draft-pauly-v6ops-happy-eyeballs-update (as draft-ietf-v6ops-happy-eyeballs-update)
    
    None of these can be considered to be "done". I would encourage people with comments to make them to the list, carrying the draft name in the subject line, and including suggested text for anything specific.
    
    _______________________________________________
    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.

v2.23.0 | Report a Bug | By Email