Re: [pim] [Last-Call] Last Call: <draft-ietf-pim-igmp-mld-snooping-yang-12.txt> (A Yang Data Model for IGMP and MLD Snooping) to Proposed Standard

tom petch <daedulus@btconnect.com> Thu, 11 June 2020 11:20 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7223A003C; Thu, 11 Jun 2020 04:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.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 BKkE6byTeZu8; Thu, 11 Jun 2020 04:20:23 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150138.outbound.protection.outlook.com [40.107.15.138]) (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 09A8A3A003B; Thu, 11 Jun 2020 04:19:58 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YNol+Y1bi7max3dTYeMfPDH1GcedX++BxGcjYOiuVTZNNQXNW6HfQ46V2o9Y0gQsOU8sWqUXrFIcI2D+a2njDwICOdxf6u94uCLhz1OVtWHW9vx35qUJ0d0SF+t++vke+ONrot0g3Cu23khAzI5U2pKosQ4AVPtq9vhkRr6ReVfOQdHgI7OrH9KhXLlI3f/zviRMWM6QRt9wZmHyUBEDau/aSle5iIQb+2ZKkfk76G+oKCDzLgu/ZE14TlMPuBKIWk2Ie8ivk2+GXRZOmb++3yJ5eG0f669xtdSCyWS56kraeUq+iFmpG2jql/EXAUqwXDl4OXySTMtoW8MLW6+vVQ==
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=bm5QcrxWB+JJQTghV3c5KbuWqX45Tgjk6Nbzufp+kNs=; b=VOcl5+rjlBBxPIxlPeV3g5Vzr5WfPSTkyntnp3+3HozyUqb5tVWu7sNlqSH3DyrexVTQxGfTOfCE8Ce9cqPlAazdHhwUoBG0GTYl4w8+t4SNgQAHEuYX+Q2y4AmT3OpkHPfmH41i8QVP1mx+3yngOsyo7lmi/XijR2mZN5aIc5Hbx3YhLSxzxULGCtUqH18T/c/CR4GWxSB1e5TTWXYkhKW++56dxMF5Oq2vEeOvBXDi8qo+mwsMHW/+rV6N5nWiNwEdGKDCNRk34sUNmDy3yekCzNytUXqGfoxfrGhMdm7ITma9l6PULe+MsEbNhW8tNrBKZcxgsVCgzUWkzGIfUQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bm5QcrxWB+JJQTghV3c5KbuWqX45Tgjk6Nbzufp+kNs=; b=uz13beknh9tLyaAbV+kJnL3A3LUuxa+IrcqkQA3Nm+4xaJLu20URdEeEtUZ9rFfKDoComevvgdfioBO4OnnLklb87pr2NShcQ9/WuH/WfeXS8cBqtMsV1aDLJm+PZ//2zv+nlADJObmv0ORqTumDPzBDPtsGkEGhoevZqycEp8g=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16) by VI1PR07MB4846.eurprd07.prod.outlook.com (2603:10a6:803:8d::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.9; Thu, 11 Jun 2020 11:19:56 +0000
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176]) by VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176%11]) with mapi id 15.20.3109.007; Thu, 11 Jun 2020 11:19:56 +0000
To: last-call@ietf.org, pim@ietf.org
References: <159101702558.32435.15616119449036382064@ietfa.amsl.com> <DB6PR0701MB211826971407DCB2A99998D7CE830@DB6PR0701MB2118.eurprd07.prod.outlook.com> <1UWB4IgZSy.11NOwQkWKz1@pc8xp>
From: tom petch <daedulus@btconnect.com>
Message-ID: <5EE21354.7020400@btconnect.com>
Date: Thu, 11 Jun 2020 12:19:48 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <1UWB4IgZSy.11NOwQkWKz1@pc8xp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LO2P265CA0348.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:d::24) To VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.139.211.47) by LO2P265CA0348.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:d::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3088.19 via Frontend Transport; Thu, 11 Jun 2020 11:19:55 +0000
X-Originating-IP: [86.139.211.47]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 7e5203a3-75ab-4cbc-1a33-08d80df95e7e
X-MS-TrafficTypeDiagnostic: VI1PR07MB4846:
X-Microsoft-Antispam-PRVS: <VI1PR07MB4846DED22154A3B0B5809FF8C6800@VI1PR07MB4846.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-Forefront-PRVS: 0431F981D8
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: bst6hxVqRbSeRmQ4EKbnJ/Px/zCf3uiTL1MaJIcod3wFH2+Ljc99S0Tb5+x3qW8uQSyYyfJtrMd+xW8Y/pMVTVwKO4AdLldP8/1EOJmitX/HbfbiqApXXe5y/JACFZQTSKyhw4MMyb/HRgZdUJP5LYRiNDwTNdE0gOPc4pyNFkVD5MfVYPuVPKMDLE7PxoWHR14g1KZhF7GhMyQ0GqAVDjZ50yibvLu+2LXy7KXhH1MCi6Snfi9fW9deFI60ZftQCP9QOxOaOhfgFc3SYeYwwYyqCXsFvJdhwH+61emONt45XrkRR5gUCvqKwMquJ1xlxNMFawETTdQ/7KHtchtXtTOpG+Oh6/Y2o4aZEh4k15Ou8XOGgYv7H+QKarD2T9ydRzrV4TWepBLIAzd9jae8iA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR0701MB2480.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(136003)(376002)(396003)(346002)(39860400002)(366004)(33656002)(5660300002)(8936002)(8676002)(186003)(316002)(2906002)(52116002)(6486002)(87266011)(16526019)(16576012)(450100002)(36756003)(53546011)(86362001)(26005)(83380400001)(66946007)(66476007)(66556008)(478600001)(956004)(2616005)(6666004)(66574014)(966005); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: V0ZBrYCuX0elL6/b9Rr8STpuBVEfW1eiCkrFBPgKvtPUYgG80q4+QHYH/Uuw60XxU7eU4QOtPqnKLu3vVzApEpBqVXdak7xqnBCklGF9NCy/mk2RFVNeTMESCise0KX8RsTwxOI6IZCyRswnrF5F6EiN4yxB1n+5g5wR/AXp/WstlMga6rTln7F4ihc3t6656b9LM5MrxIlvA1J6epcrqxOq29HNzii3sJ5Z02YlOgM4PqAm46HcmOUJVQFzUhY/erGgE9rfGXa9O76bS9OrG5PkbPY8hZ4NRsFKS6RMKxpQk+QL3WcorXEVIhMdHe79nAyMMultXLbWScp3wMBOtzwvaIzMRCl0132IM03z8nGd2a9rSh8Te91q6t2hSlxbQWzaBCbQtipK0+kK65y7pLUtvXnv/QUBlnIefi7O5wx/+BjcOrlQ2D0usXQ9nm7fu4WxYUCg1gRCl+NLGjUABmd32k5+NFvq8mCfXgS51u8=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7e5203a3-75ab-4cbc-1a33-08d80df95e7e
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jun 2020 11:19:55.9074 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: e/aKhS23Npv5QRa5DCXkNs2ewkKlbjPPGqmJVcKwynLqBOY3YY0rVWi/N5JyicqQogXmR8WBoVvqCw7CPF9UrQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4846
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/oNYTXQldUJChhQktWiI7Cxi-mac>
Subject: Re: [pim] [Last-Call] Last Call: <draft-ietf-pim-igmp-mld-snooping-yang-12.txt> (A Yang Data Model for IGMP and MLD Snooping) to Proposed Standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2020 11:20:26 -0000

Separately, two more YANG quirks

The augment have no conditional - rather the YANG 'when' is one level 
down on the container, not something I am used to nor the practice in 
other pim yang.

YANG must be plain text - [RFC 4541] looks like a markup

Tom Petch


On 10/06/2020 12:44, tom petch wrote:
>
> The RPC to clear the tables are somewhat insecure.  The default is to clear all so a mistake in entering a valid address will clear everything.  It would be more secure to have an explicit option for clear all.
>
> The RPC to clear the tables has no restrictions; a NACM deny all might be appropriate
>
> RPC or ACTION?  the latter may be suitable.
>
> RFC5790 is referenced by the YANG module but is not in the I-D References
>
> feature feature* is unusual; that an identifier is a feature is usually apparent from the context in which the identifier is used and so including 'feature' in the name is redundant
>
> And to state the obvious the formatting lacks leading spaces which will doubtless get fixed some time.
>
> Tom Petch
>
>
>
> ----- Original Message -----
> From: tom petch <ietfid@btconnect.com>
> To: tom petch <daedulus@btconnect.com>
> Sent: 10/06/2020 12:31:25
> Subject: Fw: Last Call: <draft-ietf-pim-igmp-mld-snooping-yang-12.txt> (A Yang Data Model for IGMP and MLD Snooping) to Proposed Standard
> ________________________________________________________________________________
>
>
>
> ________________________________________
> From: IETF-Announce <ietf-announce-bounces@ietf.org> on behalf of The IESG <iesg-secretary@ietf.org>
> Sent: 01 June 2020 14:10
> To: IETF-Announce
> Cc: draft-ietf-pim-igmp-mld-snooping-yang@ietf.org; pim-chairs@ietf.org; pim@ietf.org
> Subject: Last Call: <draft-ietf-pim-igmp-mld-snooping-yang-12.txt> (A Yang Data Model for IGMP and MLD Snooping) to Proposed Standard
>
>
> The IESG has received a request from the Protocols for IP Multicast WG (pim)
> to consider the following document: - 'A Yang Data Model for IGMP and MLD
> Snooping'
>    <draft-ietf-pim-igmp-mld-snooping-yang-12.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2020-06-15. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
>
> Abstract
>
>
> This document defines a YANG data model that can be used to configure
> and manage Internet Group Management Protocol (IGMP) and Multicast
> Listener Discovery (MLD) Snooping devices. The YANG module in this
> document conforms to Network Management Datastore Architecture (NMDA).
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-pim-igmp-mld-snooping-yang/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>      rfc4541: Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches (Informational - IETF stream)
>
>
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>