[I2nsf] Call for WG adoption of draft-xibassnez-i2nsf-capability

Linda Dunbar <linda.dunbar@huawei.com> Wed, 02 November 2016 19:32 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 049321297CD for <i2nsf@ietfa.amsl.com>; Wed, 2 Nov 2016 12:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.717
X-Spam-Level:
X-Spam-Status: No, score=-5.717 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 4B1oAvShmCrv for <i2nsf@ietfa.amsl.com>; Wed, 2 Nov 2016 12:32:02 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5E8D129867 for <i2nsf@ietf.org>; Wed, 2 Nov 2016 12:32:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CUK10359; Wed, 02 Nov 2016 19:31:59 +0000 (GMT)
Received: from DFWEML701-CAH.china.huawei.com (10.193.5.175) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 2 Nov 2016 19:31:58 +0000
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml701-cah.china.huawei.com ([10.193.5.175]) with mapi id 14.03.0235.001; Wed, 2 Nov 2016 12:31:55 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "'i2nsf@ietf.org'" <i2nsf@ietf.org>
Thread-Topic: Call for WG adoption of draft-xibassnez-i2nsf-capability
Thread-Index: AdI1P4aCL9QtqHoaQ/m80KBWAtjgKQ==
Date: Wed, 02 Nov 2016 19:31:55 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657F669C6@dfweml501-mbb>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.128]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657F669C6dfweml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.581A3F30.0003, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 04356d339082c3b4532ca4cdf6d15a7d
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/WM_ikm9E0S0wsZc1e_CYKwIJnX4>
Subject: [I2nsf] Call for WG adoption of draft-xibassnez-i2nsf-capability
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: Wed, 02 Nov 2016 19:32:05 -0000

Dear WG:

This email serves as a call for WG adoption of draft-xibassnez-i2nsf-capability as a WG document. Considering people will be traveling to Seoul for IETF 97 and the Thanksgiving holiday afterwards, the call for adoption will run for 3.5 weeks ending Nov 28, 2016.

draft-xibassnez-i2nsf-capability-00 actually is the -07 version of draft-xia-i2nsf-capability-interface-IM, draft name change as the result of the progress of I2NSF terminology and merge with
draft-baspez-i2nsf-capabilities<https://datatracker.ietf.org/doc/draft-baspez-i2nsf-capabilities/>

Please note that this is a call for adoption, and not a last call for content of the document. Adopting a WG document simply means that the WG will focus its efforts on that particular draft going forward, and use that document for resolving open issues and documenting the WG's decisions.

Please indicate whether you support adoption for not, and if not why. Issues you have with the current document itself can also be raised, but they should be raised in the context of what should be changed in the document going forward, rather than a pre-condition for adoption.

Finally, now is also a good time to poll for knowledge of any IPR that applies to this draft, in line with the IPR disclosure obligations for WG participants (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author please respond to this email (to the chairs) whether or not you are aware of any relevant IPR
https://datatracker.ietf.org/doc/draft-xibassnez-i2nsf-capability/


Thank you,

Linda & Adrian