Re: [netmod] Suresh Krishnan's Discuss on draft-ietf-netmod-acl-model-19: (with DISCUSS)

Mahesh Jethanandani <mjethanandani@gmail.com> Thu, 27 September 2018 06:43 UTC

Return-Path: <mjethanandani@gmail.com>
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 83A00130E0A; Wed, 26 Sep 2018 23:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 4nutOI3lNHZ3; Wed, 26 Sep 2018 23:43:13 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95786130E02; Wed, 26 Sep 2018 23:43:13 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id g2-v6so1153350pgu.11; Wed, 26 Sep 2018 23:43:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:mime-version:in-reply-to:content-transfer-encoding :message-id:cc:from:subject:date:to; bh=djx2VqrOaI5Pe0kiYY5EFK54iqZMsUoIqUbDadtgHIQ=; b=cStkWN5urWWVUWNNk+r3HwXn409k8SAtGfqZKVB1PtQ5pETrcxFLCVbT5G7PGPmXeV 01GCxWq14A2fUkqdMgWAItHg00FLSwUzw6WbMRdWn5aIuPFhGqfVFi26D33DGqead3Lh pjwWDXPB9d+k1+5QrieehKtL361EeIBX1KqTM4sXQGdy7eukG3B3epQROQIP+X/AdwcI 8uqiqSUGG77vKWLpYLRq4Bil06vOCjUnSE14z6UgWh9C5Y5pCsF/s7kcPkJUhiJHoEYp oDW053oyinEBShlLh4ns2Ag+Om4WyIpg7N0QKdWD63xsa7QqrjjOHOmzTlrzHVL+f3m5 EI/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:mime-version:in-reply-to :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=djx2VqrOaI5Pe0kiYY5EFK54iqZMsUoIqUbDadtgHIQ=; b=WRZMER9IfOhVpKNEm5uy//dRygTuxOB0D5Y4HMZ+gxopVpYIy9Hk5N0aEvdBHxWUGE zlB/AMK3jgGF7ioYlt55Tol3JBv8gwivDFe4MNV6UDDt27QHdEoy7nkTzuirAmV3kLIq wBNCF2TYY2HyYYPH/7fm9fXzpz00FfLWow6JmRsymWN7hVpsGPFzGSZhXRshykWjEVaZ a8RaohcGJ7u11i1ahCSilf/P7Zhkq32p9L8gLtQss6VeRSmB8tEbH392WKwMA71uMYc1 Ds9+ygvf2gplAP6eJesbfyfaM/tZCaChNs/+o5p2XX6y5jdDImMwQO1kEOAlLcF3YauY SM1g==
X-Gm-Message-State: ABuFfohxHj7z2k1bvkVzR/advpojqYJEljEzIwa1aWRKhy08Gw3IahMa 9cW0V1i7RHn6/7EiMQNiqk8WQrd1
X-Google-Smtp-Source: ACcGV60Uttio4nt8z6q91kJPZdw5U4yVFdKe8XikYCBk6kYeyjQsidZrRwvtef2cLOQ2se2ff3D6wg==
X-Received: by 2002:a17:902:e185:: with SMTP id cd5-v6mr9136682plb.224.1538030592607; Wed, 26 Sep 2018 23:43:12 -0700 (PDT)
Received: from ?IPv6:2601:647:4700:1280:8935:fa6f:7c98:11ec? ([2601:647:4700:1280:8935:fa6f:7c98:11ec]) by smtp.gmail.com with ESMTPSA id g6-v6sm1473199pgg.7.2018.09.26.23.43.11 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 26 Sep 2018 23:43:11 -0700 (PDT)
References: <153802301104.21537.2286706947979489902.idtracker@ietfa.amsl.com> <A493EEA5-B108-4EE5-8965-EE08CE3B4D4E@gmail.com> <31264851-1F0E-44D0-9E54-BBBD080F7936@kaloom.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <31264851-1F0E-44D0-9E54-BBBD080F7936@kaloom.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BEE33E1-43B1-416B-AC2A-B08A46569AE3@gmail.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-netmod-acl-model@ietf.org" <draft-ietf-netmod-acl-model@ietf.org>, Kent Watsen <kwatsen@juniper.net>, "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
X-Mailer: iPad Mail (13G36)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Date: Wed, 26 Sep 2018 23:43:10 -0700
To: Suresh Krishnan <Suresh@kaloom.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/hMTAslKuM0aI1pxM9OZOvYAXtjs>
Subject: Re: [netmod] Suresh Krishnan's Discuss on draft-ietf-netmod-acl-model-19: (with DISCUSS)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 Sep 2018 06:43:16 -0000

Hi Suresh,

Is the model usable as is? Can it be augmented for other protocols? 

I think the answer to both the questions is yes. I do not see why then can requests like yours not be handled as separate drafts. What is the reason to hold up this draft this late in the game?

Cheers.

> On Sep 26, 2018, at 10:06 PM, Suresh Krishnan <Suresh@kaloom.com> wrote:
> 
> Hi Mahesh,
>  Thanks for your quick reply. Please find comments inline.
> 
>> On Sep 27, 2018, at 12:57 AM, Mahesh Jethanandani <mjethanandani@gmail.com> wrote:
>> 
>> Hi Suresh,
>> 
>>> On Sep 26, 2018, at 9:36 PM, Suresh Krishnan <suresh@kaloom.com> wrote:
>>> 
>>> Suresh Krishnan has entered the following ballot position for
>>> draft-ietf-netmod-acl-model-19: Discuss
>>> 
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>> 
>>> 
>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>>> for more information about IESG DISCUSS and COMMENT positions.
>>> 
>>> 
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-model/
>>> 
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>> 
>>> This document is missing ACL handling for ICMPv6 (RFC4443) completely. As the
>>> ICMP types and codes are different for ICMP and ICMPv6 I think this model
>>> should be included to cover ICMPv6.
>> 
>> I understand that there are many protocols that fall into such a criteria. As has already been discussed, we are offering the minimum set of protocols for which there is a demand, while giving the option to extend it through augmentations of the base model.
> 
> I understand where you are coming from but ICMPv6 is not just another protocol. It is a core protocol in the IPv6 protocol suite. Do you know of any systems that support IPv6 acls but not support ICMPv6 there?
> 
>> 
>> Let us not boil the ocean. As it is, this draft has been in the works for more than 4 years.
> 
> This is a very clear and bounded request (i.e. not boiling the ocean). I do not think this will be significant amount of work. If you do feel otherwise, I will be glad to revisit my position
> 
> Regards
> Suresh