IETF Logo Mail Archive

Re: [netmod] WG Last Call: draft-ietf-netmod-acl-model-15

Kent Watsen <kwatsen@juniper.net> Wed, 17 January 2018 23:33 UTC

Return-Path: <kwatsen@juniper.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABAF12EA59 for <netmod@ietfa.amsl.com>; Wed, 17 Jan 2018 15:33:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 hl2Ba6b9cPoi for <netmod@ietfa.amsl.com>; Wed, 17 Jan 2018 15:33:10 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 C2ADA12D893 for <netmod@ietf.org>; Wed, 17 Jan 2018 15:33:10 -0800 (PST)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0HNTVv8026215; Wed, 17 Jan 2018 15:33:09 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=+K8RGctL/mJU9I8US+ED4YploCnYmqZmpBJCv813CYg=; b=2IRxg2aPdNZkH9TBHJOQAXhsWVylwnY/bW9P88R5/6P41BE1VEbTduUEi0W5kv3YqeHh 6v7vKbaUv33JCTX02u7n1I2RSTE3tFbK0o6j1nySAC/2Q4c0NlIr/vkh1QRim1Wwf9Qe KQB8cR7pj29XyP/xN+JI1wqGIBammabSFaYKZw+/arnfky03WAwTswbb2ApT/6LzPFbu RczHNNS320uvo4hNnkdISJiWYVyRliGjzTbH4wkDxiAPqsuap91a6GhKYuezj4sJK3lH tfrJp02HAGv+wwUtIDCpeHFVdjNIRbXBiB9ROcsMIbSXaW3L1uzSWdnfjVei64xZzia+ /Q==
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp0114.outbound.protection.outlook.com [207.46.163.114]) by mx0a-00273201.pphosted.com with ESMTP id 2fjg3kr0pa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 17 Jan 2018 15:33:09 -0800
Received: from DM5PR05MB3484.namprd05.prod.outlook.com (10.174.240.147) by DM5PR05MB2812.namprd05.prod.outlook.com (10.168.175.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.9; Wed, 17 Jan 2018 23:33:07 +0000
Received: from DM5PR05MB3484.namprd05.prod.outlook.com ([10.174.240.147]) by DM5PR05MB3484.namprd05.prod.outlook.com ([10.174.240.147]) with mapi id 15.20.0428.014; Wed, 17 Jan 2018 23:33:07 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] WG Last Call: draft-ietf-netmod-acl-model-15
Thread-Index: AQHTj93UjCIcW+s9eES+j5KHC1NlIKN4qxIAgAABR4D//7cngA==
Date: Wed, 17 Jan 2018 23:33:07 +0000
Message-ID: <BA276029-048F-4B80-A104-924DD1C488F1@juniper.net>
References: <8C19AD4C-0DCA-4D96-A070-0D76BE92BFA4@juniper.net> <20180117224916.4xtwnxgsw3snzwvf@elstar.local> <B3AAE9DB-1F4B-40F5-91BC-7A283B6E5F8B@gmail.com>
In-Reply-To: <B3AAE9DB-1F4B-40F5-91BC-7A283B6E5F8B@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR05MB2812; 7:8T8T9elASXUUFY+O8Yq20N9tpeX96+fg0E6OZz5T9SR71XW5Z8V/4GuesR+C8DoVr97MhNiUToX6SH8q0SlmX+NZUf0E1+zW7SzbcGnxDFDZ8dnR7ZSjjmlr9nBpOAqlgaKkMbv0uuvTxGZEz9F0+8Ur0GHUlIccwYVd9STwGnj3lS+wjuNldyUFOTyrw4SFMzU2yqjlmTZG2JqSsGlonpc9+C8ZixQ0DyTWWhmwT+5qnO5EiUPqyt8ZdnxNlhXh
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d2c1cad6-f043-439b-ddc6-08d55e02a9e6
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534125)(4602075)(4627221)(201703031133081)(201702281549075)(48565401081)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:DM5PR05MB2812;
x-ms-traffictypediagnostic: DM5PR05MB2812:
x-microsoft-antispam-prvs: <DM5PR05MB28124D02A2160A070E3B151BA5E90@DM5PR05MB2812.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231045)(2400053)(944501161)(6055026)(6041268)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(6072148)(201708071742011); SRVR:DM5PR05MB2812; BCL:0; PCL:0; RULEID:(100000803126)(100110400120); SRVR:DM5PR05MB2812;
x-forefront-prvs: 0555EC8317
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(39860400002)(396003)(366004)(39380400002)(189003)(199004)(105586002)(102836004)(68736007)(4326008)(25786009)(81156014)(6246003)(39060400002)(8676002)(81166006)(2950100002)(59450400001)(83506002)(77096007)(82746002)(316002)(26005)(6506007)(99286004)(76176011)(33656002)(86362001)(83716003)(58126008)(110136005)(3280700002)(6116002)(66066001)(3846002)(14454004)(478600001)(53936002)(2906002)(36756003)(305945005)(97736004)(230783001)(106356001)(7736002)(2900100001)(5660300001)(8936002)(3660700001)(6512007)(229853002)(6486002)(6436002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB2812; H:DM5PR05MB3484.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)
x-microsoft-antispam-message-info: k+RvcC8N7/2KkaYTfrH73fZBgoirKu1mRLc7HXRS2ADH/Vlta6SmxoDJFDIANcmbX+aPrvzeMpEQarIn6kjB1Q==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <C0AB7B5FC2C89D49A86A1CD816ABFFA1@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: d2c1cad6-f043-439b-ddc6-08d55e02a9e6
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jan 2018 23:33:07.5593 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB2812
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-17_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801170318
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/X6ZB6iUpdH4B-mcjyCkrvrg478w>
Subject: Re: [netmod] WG Last Call: draft-ietf-netmod-acl-model-15
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2018 23:33:12 -0000

H Mahesh,

>> - There is an open issue in the document (section 8) - are we going
>>  to resolve that during WG last call or is this a leftover?
>
> This will be resolved in the next version of the module. It is
> documented under Issues tab in GitHub. Should we remove it from
> the draft?

Most of Juergen's comments are editorial in nature and can truly be handled as part of the LC process, but this open issue has me worried, as it may result in a significant technical change.  

What will it take to close this open issue?  Is it just a matter of the getting the WG to agree that it's not an issue, or do we already know that it is a real issue and only the solution is pending?

Thanks,
Kent

v2.23.0 | Report a Bug | By Email