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

RFC Editor <rfc-editor@rfc-editor.org> Tue, 21 July 2020 22:40 UTC

Return-Path: <rfc-ed@rfc-editor.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 854AE3A0B7B for <i2nsf@ietfa.amsl.com>; Tue, 21 Jul 2020 15:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 Z40Dd7z14dta for <i2nsf@ietfa.amsl.com>; Tue, 21 Jul 2020 15:40:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE7F33A0B75 for <i2nsf@ietf.org>; Tue, 21 Jul 2020 15:40:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 6000) id A86BBF40756; Tue, 21 Jul 2020 15:39:46 -0700 (PDT)
Date: Tue, 21 Jul 2020 15:39:46 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: Roman Danyliw <rdd@cert.org>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, RFC Editor <rfc-editor@rfc-editor.org>
Message-ID: <20200721223946.GA29086@rfc-editor.org>
References: <CAPK2DexDutVYc5wU5JQb=jVv6uGjufJZVVwg+NXJ-oewRTZizw@mail.gmail.com> <20200716185216.GA17127@rfc-editor.org> <CAPK2Dex_AQcCEcvDwqRwPah73K13G_prvHdi9UdyTvxS2T=1vA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAPK2Dex_AQcCEcvDwqRwPah73K13G_prvHdi9UdyTvxS2T=1vA@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/p8-ucF06QQOPXXJLNElTu8LQfXY>
Subject: [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: Tue, 21 Jul 2020 22:40:03 -0000

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>