Re: [OPSEC] RtgDir: Last Call Review of draft-ietf-opsec-v6-21.txt - "Operational Security Considerations for IPv6 Networks"

"Acee Lindem (acee)" <acee@cisco.com> Tue, 09 February 2021 11:29 UTC

Return-Path: <acee@cisco.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D57E13A19CF; Tue, 9 Feb 2021 03:29:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level:
X-Spam-Status: No, score=-9.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=aUpVfv2t; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=XdRzhkDY
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 mGml_FoTfr8K; Tue, 9 Feb 2021 03:28:58 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C97A3A19D7; Tue, 9 Feb 2021 03:28:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10232; q=dns/txt; s=iport; t=1612870138; x=1614079738; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=pJMzSzW/6e2j5tV3qE45Yf9GedwXCuUeDJXvzWm6pQY=; b=aUpVfv2tSQhvBM35wEIdZEagvcvBHj2MWwxg//PAriCxdVxI4aOIEN+j nwBsJ31MV/8tIzfaOkEegatvTHuf/MYZ1SdaEGphYr2uJfaM9zvvdiqLc aUOFSJu26qpr+aPbWMud6IZg9DctDvm4j8nf0QLBjqy51ZLTKXnSDru6i 0=;
X-IPAS-Result: A0BZAQBucSJg/4gNJK1iHAEBAQEBAQcBARIBAQQEAQFAgT4EAQELAYFSUQd2WjYxCoQ3g0gDjg4DjxaKBoJTA1QLAQEBDQEBIwoCBAEBhEsCF4FrAiU3Bg4CAwEBAQMCAwEBAQEFAQEBAgEGBHGFYQ2GQwEBAQEDIxEMAQEnAQ8BCwQCAQgRAwECAwIfBwICAjAVCAgCBAENBYJwAYJVAy4BDqNdAooldoEygwQBAQaBMwGDTxiCEgmBDioBgnWCbBI+R4ZAJhuCAIEQASccglY+glILAoFfJoJwNIIrgVktRAEWTQQYCiEPASINHgMrHQg5DhUFBgsZBQyRBoJ5h2udYQqCeogpgQ2SUQMfgy6BNIkThW+PQZQ0iyuRTCIFIGSDVAIEAgQFAg4BAQaBaySBV3AVOyoBgj4JRxcCDY4fDRYUgzqBAYNYO4VFcwI1AgYBCQEBAwl8iggBMV0BAQ
IronPort-PHdr: 9a23:Myg8+hK9B5bxNtTTf9mcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeGvKk/h17SVoKd4PVB2KLasKHlDGoH55vJ8HUPa4dFWBJNj8IK1xchD8iIBQyeTrbqYiU2Ed4EWApj+He2YkNUA835IVbVpy764TsbAB6qMw1zK6z8EZLTiMLi0ee09tXTbgxEiSD7b6l1KUC9rB7asY8dho4xJw==3D
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,164,1610409600"; d="scan'208";a="642949852"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Feb 2021 11:28:55 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 119BSts9007611 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 9 Feb 2021 11:28:55 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 9 Feb 2021 05:28:54 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 9 Feb 2021 05:28:54 -0600
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 9 Feb 2021 05:28:54 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VEzvGanOzMkwRejKqg61CDw2sYxNeBHg3gxkXjlW6K1NZzKYFz57j7V01/iGhSI0WqjfzYHKumzk2G/q2FYsj2H1gTUQhjxzdDzwlFpsj2UHfe0dSRyruvsp4em75T6wqe4Bwz2IhHtUKj2PutsbUgYzxXbzHX96SonvIr+R7LUJvQfvpt+02gJ53+ycrNOyr4z0hKvpAA7TOqmJ2rt7XaAabMHw/IVpWF1rlUNBqvyjKQRZZr5JXtdIvzpQ4nTmrv492w5Rp5w1XzgpK28L7i7W4pyKWoFz5J0i91NmFTCcVU6r1TutAfeAfd7AC6bOlnVxQE4Zxrh+GR7pGWesqQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pJMzSzW/6e2j5tV3qE45Yf9GedwXCuUeDJXvzWm6pQY=; b=YZc90GE0pVEeet5tk+XnJQRM7pgbqveJ7c4SCk1fXS6gvrmE0LDuCyNNF/oZi9eZLzU/hf+fnHobyyz7V07VqU2jJaRdqOEMHIXRtYJ6rwTL21AVaVStViJH/8aDKOJnSgJOWXTaHKYOdRGV2KcPX8KcSnOzfI235un1Dqn5j9xkJjeBQWz9qWVgk1VAJu/CM/FfQkECY9/Kwc7wTtcJMYOU0JQFSbVfUVxrqvs0AsbwTiBjERTWL1dhVnks4F5pIm+0YGre78scJvg8y+o7HkcZz2Gq2LN58BLienrHI9qg1EzeW4QbATiV4B2Sr7Fq+OqBCTOxDVU9uGV+rY2loQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pJMzSzW/6e2j5tV3qE45Yf9GedwXCuUeDJXvzWm6pQY=; b=XdRzhkDYOMV/Qq9gUQ69js5+v83PPTXUANYJUBzF5m8xUP+YlmTFRTz1ITlbMSjC6A3zfko4BrV8QUTVln1zl8DpvE/w4Y/VGm+NmKMq+nKWiVc6qPa2VOGNlA8olmLPlkvUdlVWGRKhXhYncg6gvumrjEZQ0gUn3Hxu3x+1IqQ=
Received: from BYAPR11MB2887.namprd11.prod.outlook.com (2603:10b6:a03:89::27) by BY5PR11MB4340.namprd11.prod.outlook.com (2603:10b6:a03:1bb::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25; Tue, 9 Feb 2021 11:28:53 +0000
Received: from BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::a053:fad0:cf70:98b6]) by BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::a053:fad0:cf70:98b6%4]) with mapi id 15.20.3846.026; Tue, 9 Feb 2021 11:28:53 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "draft-ietf-opsec-v6@ietf.org" <draft-ietf-opsec-v6@ietf.org>
CC: Routing Directorate <rtg-dir@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>
Thread-Topic: [OPSEC] RtgDir: Last Call Review of draft-ietf-opsec-v6-21.txt - "Operational Security Considerations for IPv6 Networks"
Thread-Index: AQHW/mnCSuHTph4XfkqN4chzQxwti6pPXNGA
Date: Tue, 09 Feb 2021 11:28:52 +0000
Message-ID: <F1C2CC46-5EEA-48D8-B925-EAB4D35B58DB@cisco.com>
References: <A15E3C08-3EFF-4ACF-BD32-9FEE8CEC5777@cisco.com>
In-Reply-To: <A15E3C08-3EFF-4ACF-BD32-9FEE8CEC5777@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21011103
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e5a2d461-6195-47ab-b975-08d8ccede13d
x-ms-traffictypediagnostic: BY5PR11MB4340:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BY5PR11MB434072E275D211B8A53165C8C28E9@BY5PR11MB4340.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 17YocRq/PKDWeWi/PneFegg66bQ6WYb3mczANLKKBqqch2ZgdPkt2gzXEUNZ2E5uWRrhYIUBrpk3my3wOfsjuZvyuP13m9F+TjlXzbeQTXRvwhXto2tI/2GSbOpPcX6ftLzcTLH81+oJNXbCb0nkIC8qeTDd9vD/II6WtfiWcQwLQ74Ykb4MC7FnBRTUOuXCiS8/k9DYeuE43vFXGyuWeoEQuZiWO+6vxxT4E/tp2nMGRgtX1vR/bqmrFGoldDBnMqjUCJ1qw0TJV1u6xDfe7LKDAdTUqDXmU8e7oGaAA445DSrJvB5oaZKenbAcRHj3LrUmx+LboqgrWq25TruelhIXZF1kyP1gglgb1hhUqfaA6yX8dX9Rqy0Co0nEB1XKpXqXaEskztZeeZ7+1y+tNIASXjgPLNIGAYh/K1CwJmY+bGIHOMwAvI8FlxdsAGpzN+hF/96zrKZ8UrtsHujxat0J4PfRBY4FJezLhGJZLZlb7wx2B5HIAIYjOe/SV1TzTt3+rMuKl8nx3nGe3KqPlCLda1ab1p5fNflm0b1GByLkof9DxGdrGa+pHicWLvRLpIRr222V2yIou63g31huKWncugtaQpIyJiXiEeETGCIbCMikUfPKmlIBr39NzlGCrHWW2H8yJunUuG9Xotj78L1ZEFS69jCsBncgw4/OzOnEVzmBUJiZ+JGjtayB1aj1
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2887.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(136003)(39860400002)(376002)(366004)(346002)(76116006)(8676002)(66946007)(186003)(4326008)(26005)(71200400001)(86362001)(66446008)(15650500001)(66556008)(64756008)(5660300002)(316002)(8936002)(36756003)(54906003)(110136005)(83080400002)(66476007)(2616005)(6486002)(2906002)(33656002)(6506007)(53546011)(450100002)(83380400001)(6512007)(66574015)(966005)(478600001)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: fXCZdVJkMBRp4OZixKgP8Jbi3NKBLA1bH2mrkDcgwLjefL+823BziK3rGMb1cddvSPCpO66TfOC6WJZfpthyquuWqoBOc5C91JyXHfB42F+Uezm+N1NlePmq8mIlLNutBpRQGRZrtePJggwqQ0pqg34pcsny0rwCwdgf+EBKENg1D6KqbNC8LeMinbS261VmsHlr6sZfK79V6yK0980gNYy9NduPT9kSJX0Qm7SpYEW8AH4X1LUzGEhrdAD3sxUbCN8tpCN9chMhZr1lTSfVwmi9GmdjNopwoF9DXnSSRvYLl/sklYY+H5vHxNuDgeT/HdlxzsZ46o00rlVcq1SaJQtIdoOmo/ylRXobPmsTVe6Em3QMNgi8Monvt+il1frV2PbZvxLAl3T0LUxifnTX0Fn4hzDIEqu4ZdytMI0qF9B7DW8Y/yKyWZDEymyOlmyVVNkRACn30OVaOjXtUYRxATh/2EkgpcXsvGwDguWeIWYjYgJl40gM36zeNpl92JeRprxI8nZgTNiqkGQwLBUJVH/LAIa0lvhrGKeTRnawSdKhfqEZrbuK2AlbS9XW+7sQ2Pp6P3Nwrqu7dJr+CWLi20vkQ5iYox65VYL5dz7NIxVFuJxU+xaN+9RNcAVJ3vaH4kFdLwZ7joo3cKmMduHo4z6bHxv9ZXOOHAD2BaWwGyWYrO387bfRWpytRD9hDJ8ujdINnw7+CfnxPox1PvK8fMiJS0rIvF+J7YdgbdW/gdpo6uvJXfkVjYRJFjKwhLWaINIyE9z33yEVwXkFForrGfvDjwtnCoIuxSBFvnlshtfgpXt/V0FMPoJg9xwD6P/qobc/oZ2u0VgtcO5gbUjrNWBNQ5zVrKyG4pS5qczW4DS3NQAR1N/R+K4Ov6+4UR71iaXRC1wWw50TrofQe39evrMs1NPY0swYzu61WFrKT+/3WoVc/+hf+mJD7n8WXg6Wn6pJGUql/8xaCnWygu2I+NouroFp3Niug0SlhQg+haF8A+8dcL591Cld/6kG0SacWDBDL/TJHsvu9ClkedN8I3nXfaNE9al8lGvbV/1pQ2AiesxJ+FOI4NoDV5XjM1die/B5sPnv+j2UlfQdbrvGJOjZNSy3/h55Xg8XYe36vZlgrEo5JSrB0Ow646phxPetsZzmvgKz/cxurDW5a78UvxmQEXWHTQroQDLVDSqSpcjYSCQsAMVvEmSnEjp6gQ5YUWKY9cU41+WyqbI1zgs1+ainl4rxxoI/iAnVWLkywLGgy3XBUg0zcIk1TaHOM+E1OyCYyGcXpqpXPxrTqjBQR6RpQY9fYtVlNhMv6ll34sgmK7n11DS74epOojKNV/Zl
Content-Type: text/plain; charset="utf-8"
Content-ID: <288061A82A44CA4E8A2E070EB4124647@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2887.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e5a2d461-6195-47ab-b975-08d8ccede13d
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Feb 2021 11:28:52.9720 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4rGSvT+pE0CxMaZTSZXL8X4HefyXUoBFSeOMiBJpiQBHm4DV2Kq/YS1Vox3+JtJX
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4340
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/hViDVvNbuT7D3S0DMKDZdenq9CU>
Subject: Re: [OPSEC] RtgDir: Last Call Review of draft-ietf-opsec-v6-21.txt - "Operational Security Considerations for IPv6 Networks"
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsec/>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2021 11:29:01 -0000

Hi Eric,

Thanks for incorporating my comments. See one inline. 

On 2/9/21, 6:10 AM, "Eric Vyncke (evyncke)" <evyncke@cisco.com> wrote:

    Hello Acee,

    Thank you for your directorate review and sorry for such a belated reply!

    Special thanks for the DIFF containing suggestions for improving the text. Most of them have been applied (none of the authors is English native so such assistance is welcome)

    Look below for EV> for more comments.

    Regards

    -éric

    -----Original Message-----
    From: "Acee Lindem (acee)" <acee@cisco.com>
    Date: Tuesday, 3 December 2019 at 17:21
    To: "draft-ietf-opsec-v6@ietf.org" <draft-ietf-opsec-v6@ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>
    Cc: Routing Directorate <rtg-dir@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
    Subject: [OPSEC] RtgDir: Last Call Review of draft-ietf-opsec-v6-21.txt - "Operational Security Considerations for IPv6 Networks"

         Hello,

        I have been selected as the Routing Directorate reviewer for this draft.
        The Routing Directorate seeks to review all routing or routing-related
        drafts as they pass through IETF last call and IESG review, and
        sometimes on special request. The purpose of the review is to provide
        assistance to the Routing ADs. For more information about the Routing
        Directorate, please see ​

          http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

        Although these comments are primarily for the use of the Routing ADs,
        it would be helpful if you could consider them along with any other
        IETF Early Review/Last Call  comments that you receive, and strive to
        resolve them through discussion or by updating the draft.

        Document: draft-ietf-opsec-v6-21.txt
        Reviewer: Acee Lindem
        Review Date: 12/2/2019
        IETF LC End Date: Soon
        Intended Status:  Informational

        Summary: The document contains a lot of useful recommendations and
                 references for Operational Security in IPv6 networks. Since
                        the document has "Informational" status, none of the text is
                        normative.

                        While the information content is very good, parts of the
                        document are very hard to read and need revision. In general,
                        the usage of long clauses connected by semicolons should be
                        discouraged and the lists connected in this manner should
                        be replaced with complete sentences. I've attached a diffs
                        with editorial suggests but didn't try and rewrite all the
                        semicolon connected text segments.

    EV> let's hope that the RFC Editor will find and remediate those long constructs.

                        There are also minor issues that need to be addressed.

        Major Issues: None

        Minor Issues:

            1. Section 1.0 - What do you mean by "updating it with that have been
               standardized since 2007."? It just doesn't read right.

    EV> text has been simplified in -23

            2. Section 2.1 - IPv4 also allows multiple addresses per interface,
               i.e., secondary addresses. So what is new?

    EV>  last sentence now reads as
     "Having by default multiple
       IPv6 addresses per interface is a major change compared to the unique
       IPv4 address per interface for hosts (secondary IPv4 addresses are
       not common); especially for audits (see section Section 2.6.2.3)."

            3. Section 2.1.5 - The whole discussion on how to use Router
               Advertisement (RA) messages lacks enough context to understand.
               Also, expand RA in the first occurrence.

    EV> text was not clear indeed, changed

            4. Section 2.2.3 - Expand out NDP since it is not clear that it is
               Neighbor Discovery Protocol from the context. It is expanded later
               in section 2.3.

    EV> thanks, fixed

            5. Section 2.4 - RFC 6192 not only defines the "router control plane"
                but provides much better guidance for control plane filtering than
                section 2.4.1 and 2.4.2.

    EV> text updated

            6. Section 2.4.1 and 2.4.2 - The ingress ACL should only be applied on
               the packets punted to the RP.

    EV> indeed, added

            7. Section 2.4.1 - If OSPFv3 vitual links are used, the destination
               address will not be a link-local address.

    EV> trusting you on this one, text modified

            8. Section 2.4.3 - Suggest references for Path MTU Discovery
               and traceroute.

    EV> good idea

            9. Section 2.5.1 - HMAC MD5 is considered vulnerable.

    EV> let's indeed remove this paragraph

           10. Section 2.5.2 - What prior section describes the operational
               costs of IPsec?

    EV> oups the previous section was deleted revisions ago...

           11. Section 2.5.3 - Need expansion and reference for RADB.

    EV> indeed, added reference to https://www.radb.net/ 

           12. Section 2.6 - Need expansion and reference for GDPR.

    EV> indeed, added reference to https://eur-lex.europa.eu/eli/reg/2016/679/oj

           13. Section 2.7.1 - ACLs are typically per address family so this
               recommendation isn't
               really feasible. Please revise.

    EV> I disagree, this is a platform limitation. Text unchanged.

ACEE> I don't know of a platform that doesn't have this limitation. Also, the IETF YANG model is organized with all ACL entries in an ACL being the same type. 

See excerpt from RFC 8519:

  list acl {
      key "name";
      description
        "An ACL is an ordered list of ACEs.  Each ACE has a
         list of match criteria and a list of actions.
         Since there are several kinds of ACLs implemented
         with different attributes for different vendors,
         this model accommodates customizing ACLs for
         each kind and for each vendor.";
      leaf name {
        type string {
          length "1..64";
        }
        description
          "The name of the access list.  A device MAY further
           restrict the length of this name; space and special
           characters are not allowed.";
      }
      leaf type {
        type acl-type;
        description
          "Type of ACL.  Indicates the primary intended
           type of match criteria (e.g., Ethernet, IPv4, IPv6, mixed,
           etc.) used in the list instance.";
      }

However, I don't feel that strongly. 

Thanks,
Acee


           14. Section 2.7.2.6 - Expand MAP-E and MAP-T.

    EV> done

           15. Section 3.1 and 4.1 - Define bogon and provide reference.

    EV> done, added reference to CYMRU

           16. Section 3.2 - Bad reference in fourth paragraph.

    EV> fixed in -22

           17. Section 5 - Suggest references for Teredo tunnels and NAT-PT.
               Also, expand NAT-PT on first occurrence.

    EV> good idea for Teredo (added) and NAPT is now defined in section 1

        Nits: Attached diff with suggested edits.

    EV> big thanks for them

        Thanks,
        Acee