Re: [v6ops] v6ops charter update discussion
Mikael Abrahamsson <swmike@swm.pp.se> Tue, 14 April 2015 05:19 UTC
Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7FD91B3398; Mon, 13 Apr 2015 22:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.661
X-Spam-Level:
X-Spam-Status: No, score=-0.661 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, J_CHICKENPOX_24=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ngK9_FaNhDW4; Mon, 13 Apr 2015 22:19:36 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C17C1B3393; Mon, 13 Apr 2015 22:19:35 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2A6ECA1; Tue, 14 Apr 2015 07:19:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1428988773; bh=fPFkXxnewBzGEKHs6pYpb3FCizibDBVtvSf4X8PRycg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Ok8FrrroxWNo+j/QXy172vhUxn+vaMDlYIH3DQXnKTejMwGrpN9O7kJ+HxufwHigc aiO0cja1RgGENeAsK8sD58+bYed2y2bB2qsW7Pxq4HCSpz9GAzfm/ID4UicxzW/C/0 tjAqqXFpFxM/d10g3UIiJZwnHRNRLhAmPrk+IyVM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 1F8239F; Tue, 14 Apr 2015 07:19:33 +0200 (CEST)
Date: Tue, 14 Apr 2015 07:19:33 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Fred Baker (fred)" <fred@cisco.com>
In-Reply-To: <AD667352-663E-4333-ACFD-2BA0919482E0@cisco.com>
Message-ID: <alpine.DEB.2.02.1504140649500.16871@uplift.swm.pp.se>
References: <AD667352-663E-4333-ACFD-2BA0919482E0@cisco.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-1792334646-1428988773=:16871"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/K4jtl2ljG5WS0jbXT2PjlpDxEIM>
Cc: IPv6 Ops WG <v6ops@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>
Subject: Re: [v6ops] v6ops charter update discussion
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Apr 2015 05:19:38 -0000
On Mon, 13 Apr 2015, Fred Baker (fred) wrote: > Lee and I are reviewing the v6ops charter. I have attached a proposed charter and diffs against the current one. Joel has not commented on this yet, and while we have run it by the sunset4 chairs, we haven’t gotten a reading from them. Sunset4 is relevant because possibly the ipv4-as-a-service discussion would be better handled there. In this email, I’m soliciting opinions in general. > > The charter update started with Lee feeling that the fourth bullet of our current charter, which reads > 4. Publish Informational or BCP RFCs that identify and analyze > solutions for deploying IPv6 within common network environments, > such as ISP Networks, Enterprise Networks, Unmanaged Networks > (Home/Small Office), and Cellular Networks. > (http://datatracker.ietf.org/wg/v6ops/charter/) > is largely done. We know how to deploy IPv6. Hm, while I generally agree with you, does this mean that these kinds of RFCs will be out-of-scope for v6ops going forward? I would hate for us to take this out of the charter and then turn people away when they show up with a document for a solution we didn't think of yet. Or perhaps paragraph 1 is enough to allow for capturing these kinds of documents? > 4. Describe an operational roadmap to IPv6-only network deployment, > with or without IPv4 delivered as an overlay or translation > service. Fully agreed. > On another point, Lee and I have been discussing the operational reports > we had at IETF 92, and feel that was time well spent. Those had a common > thread, which was the deployment of Softwire’s MAP-E and MAP-T > technologies in their networks. We are thinking about asking companies > deploying IPv6 in Europe, Asia, and South America to make reports in the > coming three meetings, on their IPv6 deployments and the issues they > face. Would that be of general interest? How would you propose to tune > that concept? I think this is worthwile, as long as it's not going to be come a long list of 10-15 minute presentations saying the same thing. For those, we can keep it on the list. I always welcome operational reports in the meetings, but they need to contain news, not "we experienced the same thing as <foo> and solved it the same way". I would like to hear from the ds.lite deployers out there, I know they exist. Also from 464XLAT+NAT64 deployments (probably in mobile). -- Mikael Abrahamsson email: swmike@swm.pp.se
- [v6ops] v6ops charter update discussion Fred Baker (fred)
- Re: [v6ops] v6ops charter update discussion Mikael Abrahamsson
- Re: [v6ops] v6ops charter update discussion Brian E Carpenter
- Re: [v6ops] [sunset4] v6ops charter update discus… joel jaeggli
- Re: [v6ops] v6ops charter update discussion George, Wes