Re: [v6ops] v6ops charter update discussion

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 14 April 2015 20:51 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 CE4721A1BAA; Tue, 14 Apr 2015 13:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_24=0.6, SPF_PASS=-0.001] autolearn=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 9w_72xVkFwpt; Tue, 14 Apr 2015 13:51:49 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C57F1A1B9C; Tue, 14 Apr 2015 13:51:49 -0700 (PDT)
Received: by pdbqd1 with SMTP id qd1so25368335pdb.2; Tue, 14 Apr 2015 13:51:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AfJqHyfZ1E7Upcakq1RAxDQ/ijrd2NViF7YZrmEaZ1o=; b=O6z6YhGu8H3XgFxY8Ly1PdhLdF+OjAysu6GPYdUeVa0PhvcjEtP6gdGxySFfBQLHMF M28VSabvVd4jbp29vxEUmU3xXdTe7grASVZVYWiSfAfz7BUy3C53vhmL2wgHmbXMDlRQ MV1JdhW+cRH8gnxXXIVom5gaAV9QM3Oc8WgTfDFFacssi+IRuC0JzY/CujGH6kP4ALLi L2H9c/BprEIi7Gr4797bAQ7hqHzQaHdPmU/KsK7BJI093FtrrXJBtY8b6J2DAjqbtZe2 1rScVP2ji3UCqcK+yaEVyCp3f8JbjfmiIdj8NAeIbF8QtffHi+5sRVMzRMO+q4EYvs2V L8wA==
X-Received: by 10.70.129.202 with SMTP id ny10mr39443189pdb.107.1429044709165; Tue, 14 Apr 2015 13:51:49 -0700 (PDT)
Received: from ?IPv6:2406:e007:632e:1:28cc:dc4c:9703:6781? ([2406:e007:632e:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id yy2sm1986641pbb.6.2015.04.14.13.51.45 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Apr 2015 13:51:47 -0700 (PDT)
Message-ID: <552D7DE3.8060607@gmail.com>
Date: Wed, 15 Apr 2015 08:51:47 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, "Fred Baker (fred)" <fred@cisco.com>
References: <AD667352-663E-4333-ACFD-2BA0919482E0@cisco.com> <alpine.DEB.2.02.1504140649500.16871@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1504140649500.16871@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/t52gBTSdJuFZ7UD4Ga2Fl_lzCRg>
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 20:51:51 -0000

On 14/04/2015 17:19, Mikael Abrahamsson wrote:
> 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.

I agree that we should not exclude such work, and it could be that the
existing documents need corrections, but on the other hand the time
for soliciting new work in this area is past.

> Or perhaps paragraph 1 is enough to allow for capturing these kinds of documents?

Yes, because it mentions "solutions".

>>    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".

Correct, and I don't think it needs to be strictly regional, although
that may be a travel optimisation. I would suggesting soliciting lightning
talks on ipv6-ops@lists.cluenet.de. There are handy messages there from
time to time, like
http://lists.cluenet.de/pipermail/ipv6-ops/2014-December/010402.html

   Brian

> 
> I would like to hear from the ds.lite deployers out there, I know they exist. Also from 464XLAT+NAT64 deployments (probably in
> mobile).
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>