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

"Gould, James" <JGould@verisign.com> Thu, 05 November 2015 15:33 UTC

Return-Path: <JGould@verisign.com>
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 93EA91B2FB7 for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 07:33:35 -0800 (PST)
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, HTML_MESSAGE=0.001, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 SQ3FALIwq27c for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 07:33:33 -0800 (PST)
Received: from mail-oi0-f97.google.com (mail-oi0-f97.google.com [209.85.218.97]) (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 042211B2F50 for <EppExt@ietf.org>; Thu, 5 Nov 2015 07:30:13 -0800 (PST)
Received: by oies6 with SMTP id s6so3822036oie.1 for <EppExt@ietf.org>; Thu, 05 Nov 2015 07:30:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=f7o6dAMDrIjHebY36FPtKQwbcDxC5fufp0/1qW8qKOU=; b=T1a2A2nr6GvDSKqQierw1C9IDhInB9LiknGhr91UzFhAmT+9nf0LlBXo5S04WkppGv sHzanLc7A/koYghZRYi4t9ow/VD5PM9vhZYe/eEhTYlzz2xLiqZlnNfLfY3HqpgC7wjO EvWtcbkoKqAwe48HiEnZU5ChZ0U2Rn/iQ6tf8aLLFG2slEJwMS3yE3CWi18Uy6Tpwajg yd+beVUlb0kI6el1bWuHXl4rjc4ItlZS9Tm6hShkKb9OtzvmVXfpuRkCh7TrasA3BmXY B01rl5s+93L/zrL5BTX0EUXRerEuLBg0Y2A8cLkJoHhDBV4toUX4/5bxNotgaktQw7QI 5LRg==
X-Gm-Message-State: ALoCoQm8uqS4b7+UuRTm8iu7t8hXz18HPcOAUiW0XpOJ6k250kQG0oQvq1UBYWhKfZ7R3tRt5/Ny96J+MilyHxD6sRlSeKzlqA==
X-Received: by 10.31.52.216 with SMTP id b207mr7796375vka.69.1446737411849; Thu, 05 Nov 2015 07:30:11 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id g20sm52292vkc.8.2015.11.05.07.30.11 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 05 Nov 2015 07:30:11 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id tA5FU8A8013538 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Nov 2015 10:30:08 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 5 Nov 2015 10:30:07 -0500
From: "Gould, James" <JGould@verisign.com>
To: Linlin Zhou <zhoulinlin@cnnic.cn>
Thread-Topic: [eppext] Minutes for our meeting in Yokohama IETF94
Thread-Index: AQHRF6m9eK/y8o0l60m7mZABbgQMIp6N3xmAgAADFwA=
Date: Thu, 5 Nov 2015 15:30:07 +0000
Message-ID: <425852A8-E258-4660-BB6D-6D78A2CD1D27@verisign.com>
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>
In-Reply-To: <77db8b89.aea.150d83acd38.Coremail.zhoulinlin@cnnic.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_425852A8E2584660BB6D6D78A2CD1D27verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/1UM2rD_U4tHNs3zCW9YkgKbToy8>
Cc: Rik Ribbers <rik.ribbers@sidn.nl>, Ulrich Wisser <ulrich@wisser.se>, Jiagui Xie <xiejiagui@teleinfo.cn>, eppext <EppExt@ietf.org>, Declan Ma <madi@zdns.cn>
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 15:33:35 -0000

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


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Nov 5, 2015, at 10:19 AM, Linlin Zhou <zhoulinlin@cnnic.cn<mailto: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<mailto: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<mailto:EppExt@ietf.org>
https://www.ietf.org/mailman/listinfo/eppext