IETF Logo Mail Archive

Re: [pim] 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> Wed, 10 June 2020 11:45 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 8FE2A3A0992; Wed, 10 Jun 2020 04:45:12 -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 Z9BfFCKUiGbW; Wed, 10 Jun 2020 04:45:10 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60098.outbound.protection.outlook.com [40.107.6.98]) (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 E2DFF3A098B; Wed, 10 Jun 2020 04:45:09 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WgUc+uiPb5Gept/Nfp5g384XCd7SQeQx8yC6QjpQJSbfHe5LCntOQnsAEnZ6LvY3h97lBxiUiSbOe5PYIpKfKu1lTTBqC3kps88qluvvYV28QW1Fz3adAj7N3fSTKx2GfOMzhJtffiEZOj9eKjAdMLacid5v4fciDMf6N4o2W2tGrZb0FS9LHVRHPWSV7SSAMWEyQCacv+LuE5gGUxb4uyC2XjWYIRVXeennLhfEsn3Leo1pLTca+WxoyAWJkZbICCQ0TiQKdyhydi5W8HBN/QZNDD2/k+Klt78oo8mFCrINRpWzORx57kCAeTLWYMAjzq0q6aOi0EMIlhf4c6MGew==
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=qTMTYj79ynE+uIoFvbcPkyX9DG3juftE57vgdh8xs8o=; b=b+1yMCWRy5LWwZtyVw5+JQCWhHUc6htlhpVISbCOoZhMEz1zmPg1JngwcI7TN+fRiU0JsUkK8RdC/NDQVtNXRd6iopF42szy1ketrOpX6+aDa5shfr310Qz3GMMYb0EcZHZQApFLlMODOEuUVqRDhJ6hEliaq04tjmMfPUrXOX1zz+g6TbelOHaOnqSza1vN/QoKBPxeIxrEq3qoqA/Xuq9QMXXfNzdef3jJWytyGCsF7O+NREuJJB/jooNlMwsSxMHZzlkVDPUSq1RC0HVRrJzG2doTo1yZ8zsRsd8brhqD6vBPZusSsu28Yp4MDnKzi+Sn7sx4NzFUJK1PBa8CMQ==
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=qTMTYj79ynE+uIoFvbcPkyX9DG3juftE57vgdh8xs8o=; b=nZUJLw+q6cCIZUmBy3GHVydo9c7oop1b3I7RUKQQqixrJ7BbVJdjVSnXS2mu73Wbj24oiAU0l/K8dkhr7dTkNHAYWfeYL2nA46qv273Kb/U8xKv429I1GE9820db/7g5uhCyA1H/dm8VWgxxDck5JyTOpvYgpebpn9ZTKBeXXTg=
Authentication-Results: btconnect.com; dkim=none (message not signed) header.d=none;btconnect.com; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16) by VI1PR0701MB3021.eurprd07.prod.outlook.com (2603:10a6:800:8c::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.11; Wed, 10 Jun 2020 11:45:06 +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; Wed, 10 Jun 2020 11:45:06 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
References: <159101702558.32435.15616119449036382064@ietfa.amsl.com> <DB6PR0701MB211826971407DCB2A99998D7CE830@DB6PR0701MB2118.eurprd07.prod.outlook.com>
Date: Wed, 10 Jun 2020 12:44:52 +0100
Message-ID: <1UWB4IgZSy.11NOwQkWKz1@pc8xp>
In-Reply-To: <DB6PR0701MB211826971407DCB2A99998D7CE830@DB6PR0701MB2118.eurprd07.prod.outlook.com>
From: tom petch <daedulus@btconnect.com>
To: tom petch <ietfid@btconnect.com>, last-call@ietf.org
Cc: pim@ietf.org
User-Agent: OEClassic/3.0 (WinXP.2600; F; 2019-11-28)
X-ClientProxiedBy: LO3P123CA0018.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:ba::23) To VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from pc8xp (86.139.211.47) by LO3P123CA0018.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:ba::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.20 via Frontend Transport; Wed, 10 Jun 2020 11:45:05 +0000
X-Originating-IP: [86.139.211.47]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: b46b9d96-3d8b-4126-f481-08d80d33b883
X-MS-TrafficTypeDiagnostic: VI1PR0701MB3021:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB302171200D9A56000E35AAC1C6830@VI1PR0701MB3021.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-Forefront-PRVS: 0430FA5CB7
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: J9st8nTTvKl0QsBUIw823SdnJye7/nT7962oO4B179oxSORunNnnaF/LwYWKH/EbPgckyaAg4vBhwlFz47QvN1muIPF+rNAKf9qJNFfE+mLTybNhVn+ERfFsdCTWPY52ZoHxYhzVOpR4gB6jpv/QqQwJa7YKripieiuldukNX4LaOeZO5Yq4uSfXAxs6EmWAjAixhQ6r/1CRYorBpIo2zSo96Ekxc0tdro4+ZPWIJrkfic2HeeSK5Mfx8FesTMn9ARhhDCzyLlsZ0KU0AbuOxIkuu2BOrNvupmBXjaVwylPF7YROS9pQMqhyveQ7OpRQ8ywGSkrcpJXPlxGST5F66SSuZN7BmXkcJTMJKqr6ammNaH7k+BYIb+g4E1iSztwCK/WNYlqtJAizB7ns3wp6Mw==
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:(346002)(136003)(376002)(39860400002)(366004)(396003)(33716001)(966005)(956004)(52116002)(66946007)(2906002)(296002)(6666004)(16526019)(66476007)(52230400001)(66556008)(316002)(6496006)(9686003)(186003)(55016002)(9576002)(83380400001)(8676002)(478600001)(5660300002)(4326008)(66574014)(86362001)(45080400002)(26005)(53546011)(8936002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: vq6fsJ3J+qPVhvtA4VfQpZS49QhPzzbC+Zl+EKkwBqk8P43F3nvwbCOISk9+soR0KKdy1a9TpAQwFUtIzJL9M/k9/PWm/yS0byUarF7OgcYvj3xlMId174QDbYKwp6imjkwoGYmtEDTt5dq0VSkx/8gIXyXTt4SwQiI6GFn17WF8kSlkHJs3BJBUbtbn62k0sNAPuBCzzHaa3FOObb9b8+SPeqfFa+fXIJuaYO4BBMNlPKqXWvWC2RFqRJyuIX2Hd6hKzLhtAnRHNgiJLBrjhxfo/FOUGgr9ry6kFuP09Eyvp4EQkZsXk4CfwGje9JsvreIgqmN1PPEJKaTe6hVgyXFmuhuk0hyocO75PeXgRaClhFp5FkPYUPFknh/deCRVifc8lPmCGBBFm81kuuYqrIk/VdawV5B51OqGbD8dEEmK3226uzhZZzZdmXiMEKzPoNL6AI48scIvoKAIBsMIe4Vbnq7ZqElsqD2zYzUSrz8=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b46b9d96-3d8b-4126-f481-08d80d33b883
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Jun 2020 11:45:06.6582 (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: mEUlbyAoQfQnfGlsd4jGoXTFqKr+jDECih17m0VJdoKud8lyPconYjsBHUjZP/3I44FmMvQSS+oFjmZk0kLziw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB3021
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/RcFVvBgYESaS-NQ79KkddQkcCS8>
Subject: Re: [pim] 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: Wed, 10 Jun 2020 11:45:13 -0000

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






---
New Outlook Express and Windows Live Mail replacement - get it here:
https://www.oeclassic.com/


----- 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

v2.23.0 | Report a Bug | By Email