Re: [I2nsf] Stability call for draft-ietf-i2nsf-terminology-03

"Susan Hares" <shares@ndzh.com> Sat, 27 May 2017 16:05 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F17D812947F for <i2nsf@ietfa.amsl.com>; Sat, 27 May 2017 09:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.645
X-Spam-Level: ***
X-Spam-Status: No, score=3.645 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=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 xPYWoEOSgrmq for <i2nsf@ietfa.amsl.com>; Sat, 27 May 2017 09:05:01 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.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 C198612947E for <i2nsf@ietf.org>; Sat, 27 May 2017 09:05:00 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.86.26;
From: Susan Hares <shares@ndzh.com>
To: adrian@olddog.co.uk, i2nsf@ietf.org
References: <082801d2cffc$ce81ffa0$6b85fee0$@olddog.co.uk>
In-Reply-To: <082801d2cffc$ce81ffa0$6b85fee0$@olddog.co.uk>
Date: Sat, 27 May 2017 11:59:25 -0400
Message-ID: <009e01d2d702$36fe0810$a4fa1830$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIXog+a6UaA4Gw4UvWqb5mD2LLMV6F+v2lA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/TUw-FeQ_h6rN_zfl2jnBDG3rVCE>
Subject: Re: [I2nsf] Stability call for draft-ietf-i2nsf-terminology-03
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 May 2017 16:05:02 -0000

Adrian: 

It appears due to my error, I did not respond to this quickly.   Answers
are: 

1) yes - no major changes needed
2) I've read it and edited the terminology document. 
3) It is good for a foundation. 

Sue 

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Thursday, May 18, 2017 1:33 PM
To: i2nsf@ietf.org
Subject: [I2nsf] Stability call for draft-ietf-i2nsf-terminology-03

Hi WG,

The framework document got updated to match the terminology document which
was a good first test.

Now we would like to make sure that the terminology as currently documented
is something we can all work with. Hence this call for review and opinion.

Please respond to the question "Is the terminology draft stable?"

1. No. Major changes are needed.
If you do this you are duty bound to point out the problems, and you are
expected to help solve them.

2. Yes, but I haven't really read it.
If you do this we will chuckle and probably make you stand up at the next WG
meeting.

3. Yes, but I have some minor concerns.
You'll need to point them out and help fix them, but we will still be able
to consider the document as a good basis for future work.

4. Yes, I think this is something we can use as our foundation.

Note that Linda and I don't intend last-calling this document for a bit as
we suspect new terms will show up as other work progresses.

Cheers,
Adrian



_______________________________________________
I2nsf mailing list
I2nsf@ietf.org
https://www.ietf.org/mailman/listinfo/i2nsf