[I2nsf] I2NSF WG milestone & deliverable check

Linda Dunbar <linda.dunbar@huawei.com> Fri, 06 April 2018 22:28 UTC

Return-Path: <linda.dunbar@huawei.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 78D8F1242EA for <i2nsf@ietfa.amsl.com>; Fri, 6 Apr 2018 15:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 0sgWOHsuy85U for <i2nsf@ietfa.amsl.com>; Fri, 6 Apr 2018 15:28:16 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.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 C91A2120227 for <i2nsf@ietf.org>; Fri, 6 Apr 2018 15:28:15 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A7CA9EAE5050A for <i2nsf@ietf.org>; Fri, 6 Apr 2018 23:28:11 +0100 (IST)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 6 Apr 2018 23:28:12 +0100
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.91]) by SJCEML702-CHM.china.huawei.com ([169.254.4.179]) with mapi id 14.03.0382.000; Fri, 6 Apr 2018 15:28:10 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: I2NSF WG milestone & deliverable check
Thread-Index: AdPN9dZV2XRBX2nzTvu4mbv3E7U5Xw==
Date: Fri, 06 Apr 2018 22:28:09 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B023521@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.93]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B023521SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/-XMR68r6irH07x9W4pmJ_PKJC_A>
Subject: [I2nsf] I2NSF WG milestone & deliverable check
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: Fri, 06 Apr 2018 22:28:18 -0000

I2NSF WG,

Obviously we need to re-adjust our milestone established when the WG was created 2 years ago. We actually are pretty much on track, except the IESG publication dates are off.

Among the following WG documents, can authors give an estimate when you think the document can be completed? So we can adjust the milestone accordingly.




Document

Date

Status

IPR

AD / Shepherd


Active Internet-Drafts (7 hits)


draft-ietf-i2nsf-applicability-02<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-applicability/>
Applicability of Interfaces to Network Security Functions to Network-Based Security Services

2018-03-05
20 pages

I-D Exists
WG Document
Apr 2017


draft-ietf-i2nsf-capability-01<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability/>
Information Model of NSFs Capabilities

2018-04-03 <https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-capability-01>
57 pages New

I-D Exists
WG Document


draft-ietf-i2nsf-client-facing-interface-req-04<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-client-facing-interface-req/>
Requirements for Client-Facing Interface to Security Controller

2018-01-16
24 pages

I-D Exists
WG Document
Jun 2016


draft-ietf-i2nsf-consumer-facing-interface-dm-00<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-consumer-facing-interface-dm/>
I2NSF Consumer-Facing Interface YANG Data Model

2018-03-05 ☯
53 pages

I-D Exists
WG Document


draft-ietf-i2nsf-nsf-facing-interface-dm-00<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-facing-interface-dm/>
I2NSF Network Security Function-Facing Interface YANG Data Model

2018-03-05 ☯
46 pages

I-D Exists
WG Document


draft-ietf-i2nsf-sdn-ipsec-flow-protection-01<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/>
Software-Defined Networking (SDN)-based IPsec Flow Protection




Oct 2017

Data Models and Applicability Statements to IESG for publication

Apr 2017

All early drafts to IESG for publication (if WG decided to proceed): use cases, problem statement, and gap analysis document; framework document; information model requirements for extensions to protocols document; examination of existing secure communication mechanisms document

Apr 2017

Adopt IANA registry consideration as WG document

Done

Adopt applicability statements as WG Document
draft-ietf-i2nsf-applicability<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-applicability/>

Done

Adopt data models as WG document
draft-jeong-i2nsf-consumer-facing-interface-dm<https://datatracker.ietf.org/doc/draft-jeong-i2nsf-consumer-facing-interface-dm/>
draft-kim-i2nsf-nsf-facing-interface-data-model<https://datatracker.ietf.org/doc/draft-kim-i2nsf-nsf-facing-interface-data-model/>

Dec 2016

Adopt examination of existing secure communication mechanisms as WG document

Done

Adopt info model as WG document (if desired)
draft-baspez-i2nsf-capabilities<https://datatracker.ietf.org/doc/draft-baspez-i2nsf-capabilities/>

Done

WG decides whether to progress adopted drafts for publication as RFCs (use cases, framework, information model, and examination of existing secure communication mechanisms)

Done

Adopt requirements for extensions to protocols as WG document
draft-ietf-i2nsf-client-facing-interface-req<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-client-facing-interface-req/>

Done

Adopt framework as WG document
draft-ietf-i2nsf-framework<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-framework/>
draft-ietf-i2nsf-terminology<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-terminology/>

Done

Adopt use Cases, problem statement, and gap analysis as WG document
draft-ietf-i2nsf-gap-analysis<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-gap-analysis/>
draft-ietf-i2nsf-problem-and-use-cases<https://datatracker.ietf.org/doc/draft-ietf-i2nsf-problem-and-use-cases/>


Thanks, Linda & Yoav