IETF Logo Mail Archive

Re: [I2nsf] RFC or not RFC in I2NSF?

Rakesh Kumar <rkkumar@juniper.net> Thu, 03 November 2016 15:25 UTC

Return-Path: <rkkumar@juniper.net>
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 9CCF61294EA for <i2nsf@ietfa.amsl.com>; Thu, 3 Nov 2016 08:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 qOKq4hSA4tfc for <i2nsf@ietfa.amsl.com>; Thu, 3 Nov 2016 08:25:39 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0093.outbound.protection.outlook.com [104.47.36.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA890129A48 for <i2nsf@ietf.org>; Thu, 3 Nov 2016 08:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=VxujP5Ti6CmOhz0RCaMarFShSRMlrEVnIf+SWO8n7ms=; b=Tg0AVYLbz7gGwe7cwPCVALKowJObN5URuYlDEfRn+nrdSdX2uHPbDKA1xrCKucrw/r2O86Pid+n+5nK68PweZnAi8y1+stUFVDws+qArXwBgc/aTXPM/tolaqFf5dkbvFzhpbsUEwyCo5ku75bqCyyitBKUEPypSr+KyM2qy5y8=
Received: from BN6PR05MB2993.namprd05.prod.outlook.com (10.173.19.11) by BN6PR05MB2994.namprd05.prod.outlook.com (10.173.19.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.707.1; Thu, 3 Nov 2016 15:25:37 +0000
Received: from BN6PR05MB2993.namprd05.prod.outlook.com ([10.173.19.11]) by BN6PR05MB2993.namprd05.prod.outlook.com ([10.173.19.11]) with mapi id 15.01.0707.004; Thu, 3 Nov 2016 15:25:37 +0000
From: Rakesh Kumar <rkkumar@juniper.net>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [I2nsf] RFC or not RFC in I2NSF?
Thread-Index: AdI1OMuOIxe/Y2TRRAyM9mvFSt7GuAAcw5sA
Date: Thu, 03 Nov 2016 15:25:37 +0000
Message-ID: <5D2B0AEB-5B2C-4F75-8E62-A4348CDF5DFE@juniper.net>
References: <047b01d23538$d076e820$7164b860$@olddog.co.uk>
In-Reply-To: <047b01d23538$d076e820$7164b860$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.18.0.160709
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rkkumar@juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [73.241.94.21]
x-ms-office365-filtering-correlation-id: b170feb4-a30d-44cf-4bbb-08d403fda9d0
x-microsoft-exchange-diagnostics: 1; BN6PR05MB2994; 7:a3z623XvtoAoTaKjy5/YpvbSnVf097frkZKd0I7y1J0lQ4RBqgwZh6VaW5ShkQk+8Ih9JBuXgm3Fz7dbVmUs8GwwPfjidLuZOFldbwY202PPxT0qO0BPBfAIGio8ueBUbIodI75J7eyyZxFmIO7ic8oI9AUXU2Hox1Y4+SrTM18AF49bDJVMm4/ZM4zwxGDN/frStQoe6YUvYz0+WZJE+aojz2ZCmaMN/uNgYrlv9I9VQQLKkdQ/iTMBH+IWFs/jPGe4vUbDSwfMiV8F1BfeL0zi3HEFL1JgYBVUZDgJqffHMh9tiBEiPxY7KvYTBuuULE4rlph0STZs8POY4HS60zQrGITbtLD3nu3pzs3fAbw=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN6PR05MB2994;
x-microsoft-antispam-prvs: <BN6PR05MB29946596E551E6185752FE1EADA30@BN6PR05MB2994.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:BN6PR05MB2994; BCL:0; PCL:0; RULEID:; SRVR:BN6PR05MB2994;
x-forefront-prvs: 011579F31F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(24454002)(377454003)(189002)(199003)(102836003)(36756003)(2950100002)(5002640100001)(8936002)(5660300001)(86362001)(2906002)(7846002)(101416001)(33656002)(10400500002)(54356999)(76176999)(50986999)(7736002)(66066001)(19580405001)(19580395003)(586003)(82746002)(305945005)(3660700001)(77096005)(106356001)(15975445007)(83506001)(105586002)(99286002)(189998001)(92566002)(3280700002)(122556002)(81166006)(2900100001)(87936001)(3846002)(83716003)(6116002)(5001770100001)(2501003)(4326007)(8676002)(4001350100001)(11100500001)(68736007)(97736004)(81156014)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR05MB2994; H:BN6PR05MB2993.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <87C9B9C340E4124ABE9DC95A27E614A9@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Nov 2016 15:25:37.5721 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB2994
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/V-tcUIwOSPv8VQ9lA6HtxIr6NcY>
Cc: 'Kathleen Moriarty' <kathleen.moriarty.ietf@gmail.com>
Subject: Re: [I2nsf] RFC or not RFC in I2NSF?
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.17
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, 03 Nov 2016 15:25:40 -0000

Hi,

It looks good but I hope, we would publish the information model as well, it is the basis for development as different vendors/supplier may build differently capable systems. Here is a quote from RFC3444 (section 3.0).

“An important characteristic of IMs is that they can (and generally
   should) specify relationships between objects.  Organizations may use
   the contents of an IM to delimit the functionality that can be
   included in a DM.”
 
I am curious, whether other IETF WGs such as I2RS are publishing information model.

Regards, 
Rakesh

On 11/2/16, 11:42 AM, "I2nsf on behalf of Adrian Farrel" <i2nsf-bounces@ietf.org on behalf of adrian@olddog.co.uk> wrote:

    Hi,
    
    We have a charter action and milestone to decide whether to publish our work as
    RFCs or not. The milestone reads:
    
    > WG decides whether to progress adopted drafts for publication as RFCs (use
    cases,
    > framework, information model, and examination of existing secure communication
    > mechanisms) 
    
    We had some (light) conversations on the list and arrived at the following
    position, I think. This is your chance to scream if you disagree - otherwise,
    this is the email of record documenting our plan.
    
    use cases
    draft-ietf-i2nsf-problem-and-use-cases
    Pursue publication
    
    framework
    draft-ietf-i2nsf-framework
    Pursue publication
    
    information model
    Not yet clear, but some feeling that we should publish.
    Pending adoption and more work.
    
    gap analysis for protocols
    draft-ietf-i2nsf-gap-analysis
    Do not publish
    Keep draft alive for as long as it is useful, then archive
    
    requirements for protocol extensions
    Covered as part of draft-ietf-i2nsf-client-facing-interface-req-00 
    Pursue publication
    
    examination of existing secure communication mechanisms
    Aim to add this to  draft-ietf-i2nsf-client-facing-interface-req-00 
    Pursue publication
    
    terminology
    draft-ietf-i2nsf-terminology
    Pursue publication
    
    Cheers,
    Adrian
    
    _______________________________________________
    I2nsf mailing list
    I2nsf@ietf.org
    https://www.ietf.org/mailman/listinfo/i2nsf

v2.23.0 | Report a Bug | By Email