IETF Logo Mail Archive

Re: [I2nsf] [Roman] Re: Request for Resolving <draft-ietf-i2nsf-applicability>

Roman Danyliw <rdd@cert.org> Thu, 23 July 2020 21:05 UTC

Return-Path: <rdd@cert.org>
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 631AE3A0DBD for <i2nsf@ietfa.amsl.com>; Thu, 23 Jul 2020 14:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 kMt8NsswEwcl for <i2nsf@ietfa.amsl.com>; Thu, 23 Jul 2020 14:05:29 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54FC33A0DB8 for <i2nsf@ietf.org>; Thu, 23 Jul 2020 14:05:28 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 06NL5QVP001348; Thu, 23 Jul 2020 17:05:27 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 06NL5QVP001348
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1595538327; bh=41uNAw13E3k4WVgFbkACLyFiQFd1XELIOY41TsIMxFE=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=HV2giupvd/4k45DICqmpqxwu5pmg86QB+imrz2O8KNTEgdrYm9OC2geFsudFdrwMx kwDt3Ih/sSYgQ5oT9e19+KCUUbcUUxOj/NJcPVfdM/GAOK7U5emEAsamiIk8OhezCW VWnQon52j2cPuoDmiD+UnfsmjmjOlbfElZbG0y44=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 06NL5NqV015178; Thu, 23 Jul 2020 17:05:23 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by CASSINA.ad.sei.cmu.edu (10.64.28.249) with Microsoft SMTP Server (TLS) id 14.3.487.0; Thu, 23 Jul 2020 17:05:23 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Thu, 23 Jul 2020 17:05:23 -0400
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.1979.003; Thu, 23 Jul 2020 17:05:23 -0400
From: Roman Danyliw <rdd@cert.org>
To: RFC Editor <rfc-editor@rfc-editor.org>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [I2nsf] [Roman] Re: Request for Resolving <draft-ietf-i2nsf-applicability>
Thread-Index: AQHWW8qjC26Pl4vSBUSHHv5Egy8UqqkS6yMAgALEqZA=
Date: Thu, 23 Jul 2020 21:05:21 +0000
Message-ID: <b5c99927acec48edb1dafd9653fe17d4@cert.org>
References: <CAPK2DexDutVYc5wU5JQb=jVv6uGjufJZVVwg+NXJ-oewRTZizw@mail.gmail.com> <20200716185216.GA17127@rfc-editor.org> <CAPK2Dex_AQcCEcvDwqRwPah73K13G_prvHdi9UdyTvxS2T=1vA@mail.gmail.com> <20200721223946.GA29086@rfc-editor.org>
In-Reply-To: <20200721223946.GA29086@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.202.156]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/qFRqsv_lhn8tdcoGKcb0eNfw5dk>
Subject: Re: [I2nsf] [Roman] Re: Request for Resolving <draft-ietf-i2nsf-applicability>
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 23 Jul 2020 21:05:32 -0000

Hi Paul!

I'm not so sure we can do that.  By my read, the intent of this document is to show how I2NSF can be used (i.e., it's an applicability statement).  Using the shorthand from [1], the core I2NSF YANG drafts "must be read to understand the technology".  If that's the case, then they have to be normative.   Does that make sense?  

Regards,
Roman

[1] https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/

> -----Original Message-----
> From: I2nsf <i2nsf-bounces@ietf.org> On Behalf Of RFC Editor
> Sent: Tuesday, July 21, 2020 6:40 PM
> To: Roman Danyliw <rdd@cert.org>; Mr. Jaehoon Paul Jeong
> <jaehoon.paul@gmail.com>
> Cc: i2nsf@ietf.org; skku-iotlab-members <skku-iotlab-
> members@googlegroups.com>; RFC Editor <rfc-editor@rfc-editor.org>
> Subject: [I2nsf] [Roman] Re: Request for Resolving <draft-ietf-i2nsf-
> applicability>
> 
> Hi Roman,
> 
> We're hoping you can provide some input here.  Moving references into or out
> of the Normative section requires AD approval.
> 
> Thank you,
> Sandy
> 
> 
> On Fri, Jul 17, 2020 at 08:40:50AM +0900, Mr. Jaehoon Paul Jeong wrote:
> > Hi RFC Editor,
> > If we move those references to Informative References because our
> > I2NSF Applicability Draft will be an Informational RFC.
> > Could you publish our I2NSF Applicability Draft?
> >
> > I CC the Security Area AD, Roman Danyliw for his opinion.
> >
> > Roman,
> > Could you say your opinion on this reference issue?
> >
> > Thanks.
> >
> > Best Regards,
> > Paul
> >
> > On Fri, Jul 17, 2020 at 3:52 AM RFC Editor <rfc-editor@rfc-editor.org>
> > wrote:
> >
> > > Greetings,
> > >
> > > We will update the document as requested, but please note that the
> > > changes described below do not remove the normative reference holds
> > > on this document.  The following Internet-Drafts are listed as
> > > normative references; this document cannot move forward in the
> > > publication process until these documents are also approved for
> publication:
> > >
> > >    draft-ietf-i2nsf-consumer-facing-interface-dm
> > >    draft-ietf-dots-architecture
> > >    draft-ietf-i2nsf-nsf-facing-interface-dm
> > >    draft-ietf-i2nsf-nsf-monitoring-data-model
> > >    draft-ietf-i2nsf-registration-interface-dm
> > >
> > > Note that you do not need to send us an updated XML file as these
> > > I-Ds are updated.  We will update these entries to refer to the RFC
> > > numbers as part of our publication process.
> > >
> > > Please let us know if you have any questions.
> > >
> > > Thank you,
> > > RFC Editor/sg
> > >
> > >
> > > On Thu, Jul 16, 2020 at 12:10:40PM +0900, Mr. Jaehoon Paul Jeong wrote:
> > > > Hi RFC Editor,
> > > >
> > > > Our draft is in the state of MISSREF with the five drafts.
> > > > (https://www.rfc-editor.org/cluster_info.php?cid=C405 <
> > > https://www.rfc-editor.org/cluster_info.php?cid=C405>)
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > >  draft-ietf-i2nsf-consumer-facing-interface-dm   NOT-RECEIVED
> > > >  draft-ietf-dots-architecture   RFC-EDITOR
> > > >  draft-ietf-i2nsf-nsf-facing-interface-dm   NOT-RECEIVED
> > > >  draft-ietf-i2nsf-nsf-monitoring-data-model   NOT-RECEIVED
> > > >  draft-ietf-i2nsf-registration-interface-dm   NOT-RECEIVED
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > >
> > > > Except for draft-ietf-dots-architecture, other drafts will take
> > > > more time until they are approved as RFCs by IESG.
> > > >
> > > > Could you use the latest versions of the I2NSF-relevant drafts for
> > > > the
> > > publication of our draft?
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > > [consumer-facing-inf-dm]
> > > >     Jeong, J., Chung, C., Ahn, T., Kumar, R., and S. Hares,
> > > >     "I2NSF Consumer-Facing Interface YANG Data Model", draft-
> > > >     ietf-i2nsf-consumer-facing-interface-dm-09 (work in
> > > >     progress), July 2020.
> > > >
> > > > [nsf-facing-inf-dm]
> > > >     Kim, J., Jeong, J., Park, J., Hares, S., and Q. Lin,
> > > >     "I2NSF Network Security Function-Facing Interface YANG
> > > >     Data Model", draft-ietf-i2nsf-nsf-facing-interface-dm-09
> > > >     (work in progress), May 2020.
> > > >
> > > > [nsf-monitoring-dm]
> > > >     Jeong, J., Chung, C., Hares, S., Xia, L., and H. Birkholz,
> > > >     "I2NSF NSF Monitoring YANG Data Model", draft-ietf-i2nsf-
> > > >     nsf-monitoring-data-model-03 (work in progress), May 2020.
> > > >
> > > > [registration-inf-dm]
> > > >     Hyun, S., Jeong, J., Roh, T., Wi, S., and J. Park, "I2NSF
> > > >     Registration Interface YANG Data Model", draft-ietf-i2nsf-
> > > >     registration-interface-dm-08 (work in progress), March
> > > >     2020.
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > >
> > > > There are version-ups for the following drafts.
> > > > Could you use the latest versions of them?
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > > [dots-architecture]
> > > >     Mortensen, A., Reddy, T., Andreasen, F., Teague, N., and
> > > >     R. Compton, "Distributed-Denial-of-Service Open Threat
> > > >     Signaling (DOTS) Architecture", draft-ietf-dots-
> > > >     architecture-18 (work in progress), March 2020.
> > > >
> > > > [policy-translation]
> > > >     Jeong, J., Yang, J., Chung, C., and J. Kim, "Security
> > > >     Policy Translation in Interface to Network Security
> > > >     Functions", draft-yang-i2nsf-security-policy-
> > > >     translation-06 (work in progress), May 2020.
> > > >
> > > > [tls-esni]
> > > >     Rescorla, E., Oku, K., Sullivan, N., and C. Wood, "TLS
> > > >     Encrypted Client Hello", draft-ietf-tls-esni-07 (work in
> > > >     progress), June 2020.
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > >
> > > > Also, I2NSF Terminology Draft[i2nsf-terminology] expired, so I
> > > > would
> > > like to
> > > > replace [i2nsf-terminology] with [RFC8329], and remove
> > > [i2nsf-terminology] as
> > > > citations in the text and its reference paragraph from the text.
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > > [i2nsf-terminology]
> > > >     Hares, S., Strassner, J., Lopez, D., Xia, L., and H.
> > > >     Birkholz, "Interface to Network Security Functions (I2NSF)
> > > >     Terminology", draft-ietf-i2nsf-terminology-08 (work in
> > > >     progress), July 2019.
> > > >
> > > > [RFC8329]  Lopez, D., Lopez, E., Dunbar, L., Strassner, J., and R.
> > > >     Kumar, "Framework for Interface to Network Security
> > > >     Functions", RFC 8329, February 2018.
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > >
> > > > There is the addition of IANA Considerations Section as follows.
> > > > Could you include this new section?
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > > 10. IANA Considerations
> > > > This document does not require any IANA actions.
> > > >
> > > --------------------------------------------------------------------
> > > --------
> > > >
> > > > I attach the revised draft's xml and pdf files with the above changes.
> > > >
> > > > Could you move this draft forward to publish it as an RFC?
> > > >
> > > > Thanks.
> > > >
> > > > Best Regards,
> > > > Paul
> > > > --
> > > > ===========================
> > > > Mr. Jaehoon (Paul) Jeong, Ph.D.
> > > > Associate Professor
> > > > Department of Computer Science and Engineering Sungkyunkwan
> > > > University
> > > > Office: +82-31-299-4957
> > > > Email: jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>,
> > > pauljeong@skku.edu <mailto:pauljeong@skku.edu>
> > > > Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
> > > > <
> > > http://cpslab.skku.edu/people-jaehoon-jeong.php>
> > >
> >
> >
> > --
> > ===========================
> > Mr. Jaehoon (Paul) Jeong, Ph.D.
> > Associate Professor
> > Department of Computer Science and Engineering Sungkyunkwan University
> > Office: +82-31-299-4957
> > Email: jaehoon.paul@gmail.com, pauljeong@skku.edu Personal Homepage:
> > http://iotlab.skku.edu/people-jaehoon-jeong.php
> > <http://cpslab.skku.edu/people-jaehoon-jeong.php>
> 
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf

v2.23.0 | Report a Bug | By Email