IETF Logo Mail Archive

Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?

Fred Baker <fredbaker.ietf@gmail.com> Thu, 15 March 2018 09:47 UTC

Return-Path: <fredbaker.ietf@gmail.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 DFF9A12D947; Thu, 15 Mar 2018 02:47:50 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3iKX3SET98tC; Thu, 15 Mar 2018 02:47:49 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (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 BA37A12D942; Thu, 15 Mar 2018 02:47:48 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id l123so3779078vke.8; Thu, 15 Mar 2018 02:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VXWRSXNWxZSS/4kztEq+Dkt0zzFtgVbiSezXKYYS0Xc=; b=hkOMNe+Dgfh7PPlDvuMiFLBc94/a575R7SmMiTIAmL+Pz3zXPErSi8AH0yVJi/HWfL 7uRDHKDjJ+Wgt1Vg5OLX3dBLgG/7fVFDS1CYqFlWF2/dTyIzRtJfdHotVL1XFIqht06U eAQZjeiZcNoFxZJxpjDX7k9d2/8RV9tg8E67JYSrafrX5ZD+nefJmCq+z/TYrEz7pr9L xyna7/SANZPx+9bF0lzqA2sMY+fY6/vqNo17Hi4+A3IsKsNFIjw8l/mLj7DxvR54gM1m l1J8tgcANmwfpKOnZzgGyxQI+SAxwfFnY92oargHAOa4ZasOhXBs/4tJBhPIISeOp8Rq SDOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VXWRSXNWxZSS/4kztEq+Dkt0zzFtgVbiSezXKYYS0Xc=; b=LvG47HEhhIFt9V4AronniZFYadLkIEMKqoBfSjcR1T/mNniVnEGadk+vkR9BX87Wso ypkzBuBuqaxJVu6yCOwZenRf+5ldrUZ3ogy4DRKfYwZZgJQjvJZdqMh1lmaN/zkdxZap Kmk48fOgqv+DpQUbhp+3TWGVbxQR4UjYEXZhH7kP5hkJbdK1DN3nrUUQJME7EORwde+v +fDSvM4jlH+gwUEkyACSZL8D58iRYs6wr97pTd3CZ47rAHTyZq7+rxezdf/zQjzMb3G7 zKN7kyh1ZJLFHKwtRufWb22Bb15EwxbTTk6qsYGUDho7C7+iI7nPXjdHvNnvrjawycMu LuTQ==
X-Gm-Message-State: AElRT7FMo1bzm+epfwXDjQLQjwjsVgyjYKlgVGKCalCpmlBhITv75qgK 5ho+lvFyDaPHh22iZPfQQL8=
X-Google-Smtp-Source: AG47ELuEjeGrD/CPcLLSe2n+jTLpfZcb000AL3bgyDl2QbHur4Yc3+Eg14K4yxitKn32kXPR82avwA==
X-Received: by 10.31.108.87 with SMTP id h84mr2808530vkc.166.1521107267789; Thu, 15 Mar 2018 02:47:47 -0700 (PDT)
Received: from [172.20.7.214] ([67.203.214.34]) by smtp.gmail.com with ESMTPSA id y50sm1589315uay.19.2018.03.15.02.47.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Mar 2018 02:47:46 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <D27651B7-CFE5-403A-8B5E-C9D462D6F379@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5BA61AC6-AB84-4864-BC9A-8A6BBB08BE08"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Thu, 15 Mar 2018 05:47:44 -0400
In-Reply-To: <4e2c097afdd34ad2a7f31cb463704a72@XCH15-06-08.nw.nos.boeing.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
To: Fred Templin <Fred.L.Templin@boeing.com>
References: <172cd17ae54a4adba58ffcdfb522fac5@XCH15-06-08.nw.nos.boeing.com> <1af67899f24b43fa87013c61e59f0de8@XCH15-06-08.nw.nos.boeing.com> <017501d3b868$7d9a9a70$78cfcf50$@gmail.com> <9490580a13eb497ba22c19a9e360a49b@XCH15-06-08.nw.nos.boeing.com> <ddd6c6a937b342abaf5811377f88d731@XCH15-06-08.nw.nos.boeing.com> <4e2c097afdd34ad2a7f31cb463704a72@XCH15-06-08.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6BtTp4gbuIcNFEuQQz7rkKtd0jM>
Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
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: Thu, 15 Mar 2018 09:47:51 -0000


> On Mar 15, 2018, at 1:23 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> 
> v6ops chairs,
> 
> My understanding from what I have been told in the past is that, in order
> to get a meeting agenda slot for a document, there needs to be discussion
> on the list and people expressing support for adoption. This document
> has seen both of those, so please add 'draft-templin-v6ops-pdhost' to
> the agenda - 10mins should be fine.
> 
> Thanks - Fred

I have updated the agenda at https://datatracker.ietf.org/meeting/101/materials/agenda-101-v6ops

I would't actually agree that support for adoption is required; that comes when we want to discuss adoption. And for adoption, on a mailing list with 1000 people, of which 100-200 show up at meetings, four (and with the author, five) doesn't constitute a consensus. What I have told you is that people need to show operational interest in the draft - "this would be useful in my environment". What the chairs are looking for in the case of pdhost is people saying "that would be a useful model for me to deploy in my data center or other environment".

>> -----Original Message-----
>> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Templin, Fred L
>> Sent: Wednesday, March 14, 2018 10:24 AM
>> To: v6ops@ietf.org
>> Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
>> 
>> To add to what I said yesterday, to my understanding this qualifies the
>> work to be added to the IETF101 agenda. Please confirm.
>> 
>>> -----Original Message-----
>>> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Templin, Fred L
>>> Sent: Tuesday, March 13, 2018 8:16 AM
>>> To: 7riw77@gmail.com; v6ops@ietf.org
>>> Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
>>> 
>>> Thanks Russ,
>>> 
>>> Others have also expressed their support in earlier posts:
>>> 
>>> https://www.ietf.org/mail-archive/web/v6ops/current/msg28663.html
>>> https://www.ietf.org/mail-archive/web/v6ops/current/msg28675.html
>>> https://www.ietf.org/mail-archive/web/v6ops/current/msg28746.html
>>> 
>>> There was also quite a bit of list discussion about it back in the Nov-Dec
>>> timeframe since IETF100.
>>> 
>>> Fred
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: 7riw77@gmail.com [mailto:7riw77@gmail.com]
>>>> Sent: Saturday, March 10, 2018 4:08 AM
>>>> To: Templin, Fred L <Fred.L.Templin@boeing.com>; v6ops@ietf.org
>>>> Subject: RE: [v6ops] draft-templin-v6ops-pdhost a working group draft?
>>>> 
>>>> 
>>>>> Please review and comment on the latest draft version (below). Would like to
>>>>> see support for this as a working group item, as it provides value to the
>>>>> community.
>>>> 
>>>> I support this as a WG draft.
>>>> 
>>>> 😊
>>>> 
>>>> Russ
>>>> 
>>> 
>>> _______________________________________________
>>> 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

v2.23.0 | Report a Bug | By Email