Re: [eppext] Minutes for our meeting in Yokohama IETF94

Rik Ribbers <rik.ribbers@sidn.nl> Thu, 05 November 2015 20:32 UTC

Return-Path: <rik.ribbers@sidn.nl>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 586E21B3505 for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 12:32:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.684
X-Spam-Level:
X-Spam-Status: No, score=0.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, J_CHICKENPOX_64=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ok5S2igfQwZ7 for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 12:32:34 -0800 (PST)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12CB71B370C for <eppext@ietf.org>; Thu, 5 Nov 2015 12:32:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn-nl; c=relaxed/relaxed; h=from:to:cc:subject:thread-topic:thread-index:date:message-id:references:in-reply-to:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:x-mailer:x-ms-exchange-transport-fromentityheader:x-originating-ip:content-type:mime-version; bh=x+A+IFOnIrHGPg6v8WvbbLhju6YiXwS8x58IYVHXwec=; b=UEpfHLjzuUkLyC9Fq/S+WUClRCR1NbgXPWqlbQR/aKXWC1hOxWlKFoBBAyWYMZJTGPn4Pgyz/GorC+cDHRse07f3DPujFHCQFbTOnHZsXLU0gabFOcAa/GcbN5DB3vnMu0NyVqUEtpnxDuPMYBa/W2OQb4jaW6Do3sUn7qGaWmloKEFITMnU1BwVoZ5EcWlf3hQtQZe+VFbGp0ALs8V+ZaHuyBYGfS58fM8sGEYrSkLFRuASvi3ISAIOIrr3dyyAMO/pVFLnLpXQOeWSEZ1xk3AsjwnvFOf/lvCwxL4us+8Bgh2aN61bgOfks3ptt4X5qvq4WcZbKay3OTV2QnzHeQ==
Received: from ka-mbx02.SIDN.local ([192.168.2.178]) by arn2-kamx.sidn.nl with ESMTP id tA5KWU6H027844-tA5KWU6J027844 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Thu, 5 Nov 2015 21:32:30 +0100
Received: from ka-mbx02.SIDN.local (192.168.2.178) by ka-mbx02.SIDN.local (192.168.2.178) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Thu, 5 Nov 2015 21:32:33 +0100
Received: from ka-mbx02.SIDN.local ([fe80::9855:369a:1ca4:6549]) by ka-mbx02.SIDN.local ([fe80::9855:369a:1ca4:6549%13]) with mapi id 15.00.1076.000; Thu, 5 Nov 2015 21:32:33 +0100
From: Rik Ribbers <rik.ribbers@sidn.nl>
To: Antoin Verschuren <ietf@antoin.nl>
Thread-Topic: [eppext] Minutes for our meeting in Yokohama IETF94
Thread-Index: AQHRF97gMDn0cGq6KEGTOqnSTlIjj56NjeEAgABDzAA=
Date: Thu, 5 Nov 2015 20:32:33 +0000
Message-ID: <F5145519-6428-4722-9DE1-19FB33BE98A2@sidn.nl>
References: <CAJ9-zoXEL_QMsGJ1ZkNr61VHqXRCFCR8o6_UHO7vZxRtV-ZL=w@mail.gmail.com> <0101FBC0-248F-4560-9364-F023B901A959@zdns.cn> <38638B99-20DF-40B3-B431-36ECFE27485F@sidn.nl> <2015110519525639913345@teleinfo.cn> <CDF93078-FA84-48EB-8EC0-DAE733681C6E@sidn.nl> <77db8b89.aea.150d83acd38.Coremail.zhoulinlin@cnnic.cn> <425852A8-E258-4660-BB6D-6D78A2CD1D27@verisign.com> <CC7C221E-729E-4351-BB72-009F3174B74F@antoin.nl>
In-Reply-To: <CC7C221E-729E-4351-BB72-009F3174B74F@antoin.nl>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3096.5)
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.4.205]
Content-Type: multipart/signed; boundary="Apple-Mail=_1E51BF6F-0AD2-445E-AD1A-868C283BDACC"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/5Ep424-cYAmNi-0LIiQuwMAAawk>
Cc: eppext <EppExt@ietf.org>
Subject: Re: [eppext] Minutes for our meeting in Yokohama IETF94
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2015 20:32:36 -0000

Thanks for the clarification

Gr,
Rik

> On 06 Nov 2015, at 01:29, Antoin Verschuren <ietf@antoin.nl> wrote:
> 
> As always, adoption of documents is not done in the meeting, but decisions are always taken on the mailinglist.
> Hums during the meeting is an indication for the chairs of the direction the working group wants to go.
> To my recollection, we had 2 hums during the meeting:
> 
> The first hum was on the general question if the working group wanted to work on Informational documents in general as the proposed charter states that informational RFC’s for EPP extensions can follow the Expert review path. The hum indicated strong consensus that we would not exclude working on informational documents so we will not exclude that in our proposed charter.
> 
> The second hum was if the working group agreed to divide the upcoming work into groups to set clear deadlines for our milestones as we cannot prioritize every document with our small working group with limited resources.
> 
> As specific for the nv draft, we didn’t make a final decision yet, but we would send the proposed list of milestones to the mailinglist, with the inclusion of the nv draft in group 1, and ask the mailinglist for approval of the milestones. Not everyone had read the nv draft yet, so one outcome could still be that the nv draft will not be in our milestones if there is objection on the mailinglist.
> All the documents in our milestones will be working group documents off course.
> When it is decided that the nv draft will not become a working group document, one can still request review from the working group members as an example for the verification framework.
> 
> Advise from me: I would suggest to the authors of the verification framework to replace the word "verification" with "validation" as that captures the process more then verification. Validation was also used for ENUM to verify the correctness of phone numbers and it’s owners, so there might be some good guidance in the ENUM documentation.
> 
> - --
> Antoin Verschuren
> 
> Tweevoren 6, 5672 SB Nuenen, NL
> M: +31 6 37682392
> 
> 
> 
> 
> 
> 
> Op 5 nov. 2015, om 16:30 heeft Gould, James <JGould@verisign.com> het volgende geschreven:
> 
>> I recall a vote around inclusion of informational drafts in general but I don’t remember a vote around inclusion of the nv draft itself.  It would be interesting to here from others on the list whether they support or don’t support inclusion of the nv draft based on what was discussed at the meeting and what has been discussed on this thread thus far.  I obviously feel that it is an important draft that deserves adoption by the working group.
>> —
>> 
>> JG
>> 
>> 
>> <BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png>
>> 
>> James Gould
>> Distinguished Engineer
>> jgould@Verisign.com
>> 
>> 703-948-3271
>> 12061 Bluemont Way
>> Reston, VA 20190
>> 
>> VerisignInc.com
>> 
>>> On Nov 5, 2015, at 10:19 AM, Linlin Zhou <zhoulinlin@cnnic.cn> wrote:
>>> 
>>> Dear WG,
>>> 
>>>> I see your point. I am a horrible jabber scribe….I missed that remark by Jim Galvin completely.
>>>> 
>>>> 
>>>> @Chairs: Can you make a clear statement on the list to either confirm or decline my interpretation about the verification drafts being adopted or not.
>>>> 
>>> Same question to chairs. Could you please confirm on the mailing list again whether nv draft is included in WG document?
>>> I recalled my memory that several people have comments to express concerns on nv draft and it seems not be fully supported to be adopted. But it appeared in the milestone. It confused me a lot. Thanks.
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> On 05 Nov 2015, at 20:52, xiejiagui@teleinfo.cnwrote:
>>>>> 
>>>>> 
>>>>> Hello Rik,
>>>>> Let me post the messages from the Jabber:
>>>>> <Catch.jpg>
>>>>> <CatchF973.jpg>
>>>>> 
>>>>> 
>>>>> Jim Galvin(JimG?) has confirmed  this .
>>>>> 
>>>>> 
>>>>> We do think it's useful to discuss this draft in the WG, and any comments about this draft are welcome.
>>>>> 
>>> Regards,
>>> Linlin
>>> _______________________________________________
>>> EppExt mailing list
>>> EppExt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/eppext
>> 
>> _______________________________________________
>> EppExt mailing list
>> EppExt@ietf.org
>> https://www.ietf.org/mailman/listinfo/eppext
> 
> _______________________________________________
> EppExt mailing list
> EppExt@ietf.org
> https://www.ietf.org/mailman/listinfo/eppext