Re: [v6ops] Spencer Dawkins' No Objection on charter-ietf-v6ops-03-00: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 19 August 2015 03:59 UTC

Return-Path: <spencerdawkins.ietf@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 6A9CA1A8989; Tue, 18 Aug 2015 20:59:32 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 H-Si2zhSzpVG; Tue, 18 Aug 2015 20:59:31 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (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 C5F841A88A9; Tue, 18 Aug 2015 20:59:27 -0700 (PDT)
Received: by vkpp190 with SMTP id p190so647681vkp.3; Tue, 18 Aug 2015 20:59:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LosIbXOdSkym1Lhu2YsGPlOBf3OFf+X4dwt8dQmJzp0=; b=BeceOqUHVDDEjZ0+sEBNtHWuTrGhhZUE7w7y4PNVmK2U6Zxl/3rxiMzJ4kdf2fcPWs 2N1auUH6BkBxmbHK4JuG4PmVS7co2MlCve8X0fUJ9gymWDeLHkeYgZIwL/xTxMfemCT+ y9LUSgJ2w1t+p9TVu5eiaF6j3samk6SBbEmEZ5qAc8K9d3Y5C6in/cMNQy5cKGgTygxz OxX5pbSNal1Uuwij0wE5cbSlWk6K/zVyIDu7viVbNBJ0fXz8rgWBrUzRm1AZhdBCq32O /8IxUo4XH84dVwGm1l5JHumZ8lLqdObtUnamJdD/mD4lHQNOLDLqjA9fwV8RTHQbkIHs Xr+w==
MIME-Version: 1.0
X-Received: by 10.52.114.196 with SMTP id ji4mr13626015vdb.24.1439956767091; Tue, 18 Aug 2015 20:59:27 -0700 (PDT)
Received: by 10.31.63.1 with HTTP; Tue, 18 Aug 2015 20:59:27 -0700 (PDT)
In-Reply-To: <6274BA70-5FEE-487A-BD02-3F7BE33BB733@cisco.com>
References: <20150817162014.13511.99968.idtracker@ietfa.amsl.com> <6274BA70-5FEE-487A-BD02-3F7BE33BB733@cisco.com>
Date: Tue, 18 Aug 2015 22:59:27 -0500
Message-ID: <CAKKJt-d7JLCvUQ+wuZmMt7dkGeV1u9T+XXoNkxKWXrD1_3yBHQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: multipart/alternative; boundary="bcaec548a503983083051da20fca"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/LZLeZLkSqbcjTiX0P0B2z3644gM>
Cc: v6ops list <v6ops@ietf.org>, The IESG <iesg@ietf.org>, Joel Jaeggli <joelja@gmail.com>
Subject: Re: [v6ops] Spencer Dawkins' No Objection on charter-ietf-v6ops-03-00: (with COMMENT)
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: <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: Wed, 19 Aug 2015 03:59:32 -0000

Hi, Fred,

On Tue, Aug 18, 2015 at 6:26 PM, Fred Baker (fred) <fred@cisco.com> wrote:

>
> > On Aug 17, 2015, at 9:20 AM, Spencer Dawkins <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > This looks like a fine revised charter. I had slight uneasiness about
> > adding
> >
> > "2.  Solicit input from network operators and users to identify
> > operational interaction issues with the IPv4 Internet, and determine
> > solutions or workarounds to those issues."
> >
> > because I wondered if this will make v6ops more attractive for NAT
> > proposals, but if that's the right thing to do, please do the right
> > thing.
>
> In fairness, there is an update to RFC 6145, incorporating a erratum, RFC
> 6791, draft-ietf-6man-deprecate-atomfrag-generation, and
> draft-ietf-v6ops-siit-eam, happening on the v6ops list right now. The
> obvious other working groups are either defunct or about to be. Joel told
> us that if v6ops could agree on the update (which is pretty close), he
> would take it as AD-sponsored. So, yes, there is a question of translation,
> and it is being driven by operational considerations.
>
> The question that the sunset4 chairs had with Lee and I was how this fit
> with their charter, which is essentially about IPv4 shutdown. The current
> charter wording was worked out with them.


Thank you for the helpful background. I'm entirely comfortable with the
proposed charter revision.

Spencer