Re: [I2nsf] Is there any objection of merging the content from draft-ietf-i2nsf-terminology to draft-ietf-i2nsf-framework draft?

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Wed, 02 August 2017 19:17 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 162C0131C7A; Wed, 2 Aug 2017 12:17:24 -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 RDuEAPgR1JGn; Wed, 2 Aug 2017 12:17:22 -0700 (PDT)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e: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 ED01F132017; Wed, 2 Aug 2017 12:17:18 -0700 (PDT)
Received: by mail-pg0-x236.google.com with SMTP id l64so24724272pge.5; Wed, 02 Aug 2017 12:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=5pofIef9upQW9Ar8peA40MlKv21AQh5+Tn3PxDAHXwg=; b=b1dBZSzgBTlxjfqaWZZz0yrbaAdhPUiio5qP7tfz/CWs5CbjDeXhYK3L9LmSWkHPDL DcxiXhMgSttSulwGyGb0LP+xo0i0z6sh6+9mzOEe9iTslNYvslobr8nQVsf+e9+6oW1G 8jUg50hKTjdayp+5EIppjNiMTK1naNQqmW9tevH822TT+NDVtRQk20AM616Hb+2abVqm OeHxTsq5ukuZ/VQD9zxOkn5yfVJ7zyyyWJJ3xD/8lF4FKoPur/SiwbK+20A94RRZqrGG 9Oco8wrZAwxM98ltTAm01OPSe3kXcSv/sgMv0d2sITVINTj6I4tWVC9Prg/SjjJxe6Aa 1SSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=5pofIef9upQW9Ar8peA40MlKv21AQh5+Tn3PxDAHXwg=; b=fSXn6y1N61BaApVSb4BycQmH8G1vPWMS7G101PYBaFgbkO3UvJbaGIiUs3lVTjQI13 Ce8ZfjSQ654eC61gtIC8gWL4yCTj+5dL/aR+PRvB6AYTMYhNqJX+DEZpYDPHktBCM5Dd xnT3LdkHXXipcD9LJfAzI5xhCJWQCy13ERR6BgZHZe2O5l5E2jEuT9hdG690djMIAZ0S PUR8rjEwo4oqIPEoWDv+nXckCiMylstYm2aHmT0sM6+onpWvzWuK1ANn23lB/BLP/Tgr Ykd77Rro5qY9l2mBmwNtXELnn7dhlFdxEL9XpqeL81KW4TwPpwzHVbpfNG1B0zgkzdNN WeeQ==
X-Gm-Message-State: AIVw1121O4IMWr6fetzAELvy/WRXETY8Cu8BZXbh3q/3Y6Tx8Gs6JOsm T/czCvhzkvonQuKIWM1VU2izRMhAGEoV
X-Received: by 10.98.83.130 with SMTP id h124mr23461889pfb.13.1501701438526; Wed, 02 Aug 2017 12:17:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.144.1 with HTTP; Wed, 2 Aug 2017 12:16:38 -0700 (PDT)
In-Reply-To: <B818037A70EDCC4A86113DA25EC020982209F4E6@SJCEML703-CHM.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F65943677F@SJCEML702-CHM.china.huawei.com> <B818037A70EDCC4A86113DA25EC020982209F4E6@SJCEML703-CHM.china.huawei.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 02 Aug 2017 15:16:38 -0400
Message-ID: <CAHbuEH6RcEj7HDsM1QXE0pmoHh1yp-gYBy0d09RfuMw5HvSWrA@mail.gmail.com>
To: John Strassner <John.sc.Strassner@huawei.com>
Cc: Linda Dunbar <linda.dunbar@huawei.com>, "i2nsf@ietf.org" <I2nsf@ietf.org>, "draft-ietf-i2nsf-framework@ietf.org" <draft-ietf-i2nsf-framework@ietf.org>, "draft-ietf-i2nsf-terminology@ietf.org" <draft-ietf-i2nsf-terminology@ietf.org>, Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/qwUsGLg3x4rLB6ZPyBvQXbjdA-0>
Subject: Re: [I2nsf] Is there any objection of merging the content from draft-ietf-i2nsf-terminology to draft-ietf-i2nsf-framework draft?
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: Wed, 02 Aug 2017 19:17:24 -0000

Hi John,

As a standalone document, the terminology draft is a support document.
The IESG issued the following statement on support documents:
https://www.ietf.org/iesg/statement/support-documents-in-ietf-wgs.html

I have no problem helping a WG to publish support documents, but would
like them to think through what they are doing. We typically see
terminology as part of a main document for a WG and not a draft by
itself.  If it's part of a standards track document (appendix or
terminology section), then there is no question on it's value.

You may want to take a look at the ballots for the WG documents that
have gone through the IESG to date and you'll see the types of issues.
Mainly it is the time/resources spent publishing such documents.  I'd
like to see the terminology published in some document, but not
necessarily as a stand alone document.

Best regards,
Kathleen

On Wed, Aug 2, 2017 at 1:51 PM, John Strassner
<John.sc.Strassner@huawei.com> wrote:
> I expressed some minor concerns before, and will do so again.
>
>
>
> ·         What is the reasoning against publishing an INFORMATIONAL RFC for
> terminology?
>
> ·         Many of the terms in the current terminology draft are not used in
> the framework draft
>
> o   This is because the terminology draft was originally conceived to work
> for many diverse subject areas
>
> o   The framework draft will not cover some of these diverse subjects in
> detail, and hence, does not need those terms; including them will make the
> reading awkward at best
>
> ·         Thus, I would recommend
>
> o   We keep the current terminology draft until these other subject areas
> mature and have WG-adopted drafts (a possible alternative is putting them on
> the wiki; I am not a big fan of wikis)
>
> o   We move the appropriate terms into appropriate drafts
>
> §  Note: this will cause duplication of terms – yet another reason to keep
> the terminology draft
>
>
>
> Regards,
>
> John
>
>
>
> From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Linda Dunbar
> Sent: Wednesday, August 02, 2017 10:31 AM
> To: 'i2nsf@ietf.org' <I2nsf@ietf.org>; draft-ietf-i2nsf-framework@ietf.org;
> draft-ietf-i2nsf-terminology@ietf.org
> Cc: 'Kathleen Moriarty' <kathleen.moriarty.ietf@gmail.com>; Yoav Nir
> <ynir.ietf@gmail.com>
> Subject: [I2nsf] Is there any objection of merging the content from
> draft-ietf-i2nsf-terminology to draft-ietf-i2nsf-framework draft?
>
>
>
> I2NSF participants:
>
>
>
> During the IETF99 I2NSF Session, our AD Kathleen said that the current IESG
> doesn’t like to have RFC for Terminology only drafts. So we should consider
> merging the content of Terminology with other drafts. I2NSF framework draft
> would be a nature place to have the terminologies.
>
>
>
> If you have any objections or concerns of merging the content from
> draft-ietf-i2nsf-terminology to draft-ietf-i2nsf-framework draft, please
> express them to the I2NSF mailing list.
>
>
>
> Thanks, Linda & Yoav.
>
>



-- 

Best regards,
Kathleen