Re: [pim] Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hongji Zhao <hongji.zhao@ericsson.com> Fri, 14 September 2018 03:47 UTC

Return-Path: <hongji.zhao@ericsson.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 C56D01271FF for <pim@ietfa.amsl.com>; Thu, 13 Sep 2018 20:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.308
X-Spam-Level:
X-Spam-Status: No, score=-4.308 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=YAOT507t; dkim=pass (1024-bit key) header.d=ericsson.com header.b=WXA+Oodw
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 Bh9qR6DFdeta for <pim@ietfa.amsl.com>; Thu, 13 Sep 2018 20:47:05 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 36D57130DFC for <pim@ietf.org>; Thu, 13 Sep 2018 20:47:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1536896821; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=HlIJKWMXUkGxJyH/MGiUYlI8VNY81mBAdXsC70Fa5CY=; b=YAOT507taXEBFrC+L+ARXM/LiW06m1rXUCjZp4OEVbHuGUQYPN+QZlvdpRf/zDhh Ue14W5DsYelhOwzY10cxo+MWQr3hvQVl/ykcpuXA9giqksM9/tLAAQqUHKOJWrhL WR8l0dC4Rn18QhI3osm5QMW4xh82AQ9rkT/ZlVOLHwo=;
X-AuditID: c1b4fb2d-20bff700000055ff-7e-5b9b2f35f655
Received: from ESESSMB502.ericsson.se (Unknown_Domain [153.88.183.120]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 41.26.22015.53F2B9B5; Fri, 14 Sep 2018 05:47:01 +0200 (CEST)
Received: from ESESSMB501.ericsson.se (153.88.183.162) by ESESSMB502.ericsson.se (153.88.183.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 14 Sep 2018 05:47:01 +0200
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 14 Sep 2018 05:47:01 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HlIJKWMXUkGxJyH/MGiUYlI8VNY81mBAdXsC70Fa5CY=; b=WXA+OodwipAQFfeIeYbwyQaUwTgyPmdMSPQK5Gkxgm5i+Z+4z2FLrtt5INQWEVz7aFunylHpP8cOKKfqMLUccjg3LR4Y/V45SCNPmjDyxNJkVWMYjTSCAYQ3ND0uqTm+JoBaanYiE1dcHG7DI+E7blDWBClfj6OueHrT88dJm4U=
Received: from VI1PR07MB4192.eurprd07.prod.outlook.com (20.176.6.29) by VI1PR07MB1727.eurprd07.prod.outlook.com (10.166.143.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1143.11; Fri, 14 Sep 2018 03:46:59 +0000
Received: from VI1PR07MB4192.eurprd07.prod.outlook.com ([fe80::4849:1c1a:e22a:c079]) by VI1PR07MB4192.eurprd07.prod.outlook.com ([fe80::4849:1c1a:e22a:c079%3]) with mapi id 15.20.1143.014; Fri, 14 Sep 2018 03:47:00 +0000
From: Hongji Zhao <hongji.zhao@ericsson.com>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
CC: "draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org" <draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org>, "pim@ietf.org" <pim@ietf.org>, YANG Doctors <yang-doctors@ietf.org>
Thread-Topic: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03
Thread-Index: AQHUS46loXgObm2x0Ei/3RFB/3PPP6TvIS9w
Date: Fri, 14 Sep 2018 03:46:59 +0000
Message-ID: <VI1PR07MB419228965CBBF4412CB6D0FC96190@VI1PR07MB4192.eurprd07.prod.outlook.com>
References: <VI1PR07MB41921D54D3B708744DFFE21796270@VI1PR07MB4192.eurprd07.prod.outlook.com> <D88D0793-9EE6-4D95-9F4B-C0B483C1F21C@cisco.com> <VI1PR07MB419207CA816246DAD95F455396040@VI1PR07MB4192.eurprd07.prod.outlook.com> <A383C3C0-E62B-48DB-95DF-A52968BE2FFF@cisco.com>
In-Reply-To: <A383C3C0-E62B-48DB-95DF-A52968BE2FFF@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hongji.zhao@ericsson.com;
x-originating-ip: [106.38.5.8]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB1727; 6:kVi/DiCtKtQeT1ISgL2FKx24oaQb9vmNsmGNldqkEUDqfoi0PSlxGwslswSudqC1sePSGT8fBQ3icDgnMpYDlEsB7TgSjXkyIhZa9YDyWmZfUbGMqZHmXxpf7dMGmMbd8VpscmlwlfCYCE0mf6TujJ2yHUZp2ozRSHFYvhIlcB+drvy9yJYxZdEXFsxHilWgn66WasoahMRE2/I1Iy1A8XyBksV6YZmdyeWAb4xkovVd7c5zLaNfaMcZdZEP8apRyTs3kcC8+/YMkaKe5TzBL10RaRU/T5whxO1LPLL7Ykt8/2zpfM/71OYcqTIAk1cpEaJwWbnMrZLZnk1m89MAOsVXJL4pwL0KVoC6EME1CylpfloYAGPPvgd4P2TIR4L3sZcYcydar4mWZn5yp3bTWhVy7/O/pZgkofbQektEKmZE/pWA39rVp00/aXENNL4Sge9ZeZUsJ/6cC8fazUeRSQ==; 5:iY+ZUHVaVLhvWxELDtcMWi+kBT4x9qRpiDi8nOCuy8hWg6fOEgugmVM0q5JJW8mDZ8hqQYqVBaTEc01hb3gfghR3xUMhGApZ6xfHuK9DBevAmxMRokRXsjTP+8XWj5WC0VzODcs+mH1LsPmaY1IYOrLQaz0X303Zf/ffeXnsMDM=; 7:3xw1GgCSrShrXz2jQO6mMXEn5oa7JJbY5l72MwXGrBdgsyVWeogewLRY4W71gU1eF7rDvCiPUvy2cDHa5T7Uxouly7cPcq5ZozUSIpNRDBE6CKmYjhPQNEmAyzCRymhOw45lRuSsravsD20qI4XEnkxoTSd32DHNUwVpSlS/ymJmjoOi4Ev4yHuZ4R0negHQP1/vCMumYaQFR60F2o0yG8Xxzw9blEE+U/+BGmfPK8RO3J1yoa75t3fCohvtu8tH
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: d6dcb538-710b-432d-485b-08d619f4b9da
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB1727;
x-ms-traffictypediagnostic: VI1PR07MB1727:
x-microsoft-antispam-prvs: <VI1PR07MB17272CF2AED764338A057D3296190@VI1PR07MB1727.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(28532068793085)(120809045254105)(95692535739014)(21748063052155)(248295561703944);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231311)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123562045)(20161123564045)(201708071742011)(7699050); SRVR:VI1PR07MB1727; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1727;
x-forefront-prvs: 07954CC105
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(376002)(346002)(366004)(39860400002)(189003)(199004)(69234005)(93886005)(19609705001)(11346002)(8676002)(54906003)(224903001)(102836004)(9326002)(186003)(476003)(26005)(53546011)(6506007)(2900100001)(33656002)(86362001)(81156014)(105586002)(6916009)(106356001)(66066001)(316002)(446003)(5660300001)(8936002)(4326008)(81166006)(256004)(5024004)(14444005)(25786009)(7696005)(6246003)(76176011)(6116002)(68736007)(2906002)(3846002)(790700001)(966005)(14454004)(7736002)(478600001)(229853002)(55016002)(99286004)(74316002)(53936002)(236005)(486006)(54896002)(9686003)(6436002)(6306002)(44832011)(97736004)(606006)(5250100002)(28003001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB1727; H:VI1PR07MB4192.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: z0L6Zqv/a1GCmBed7ojKD9BaxSPLs7VOasZpMlvNV+i0n4FcvzLV6quNqMedRKI/9ZuU+ZcrP64LvQchMszSOoylRTrpNgsuDzKO8GD891jr9nYX7uRGOUdrVZRiCaEiBR1kiXuNIllWwhNyRkqB+lpaOB0dDuxYFPcH1XDYlk4hH6+x/yuRGvnqXY/soS5bVwH+EtLoUHF/ufrEdKy7sScD79FnBPosfaalfMaVQ4D8Uotz3ERAK51klNkLLTFbRb+w2d1y/AVMPWov7T2QY5WyFms3Gc/9rmLq6jBMgxnXksHN/BDKW/BYGjtKp/w5cCrdVC47b94Kds01C6isUPv38t0pEPAHlJ3+POrTSjg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB419228965CBBF4412CB6D0FC96190VI1PR07MB4192eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d6dcb538-710b-432d-485b-08d619f4b9da
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Sep 2018 03:46:59.9588 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1727
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTYRTHe/bu8k4aPC3Nk6HhKDBxTqfCSItFX0Qp+lAUWujQN2fOTfaq qUFNxNKWl1Ap17wwxMxMSUvnnMOGmpNIUTS1JEwJR3Sxi6FGte2d4Lf/Oed3zv/5w0MSwl5O AJmpzqW0aoVKxPVh11/oKxDHSB4kR5iaQ2RW/Xuu7OfSPCGbbSvlySotQ0jOjq/desqJb2nZ YJ1hJfnEpVOqzHxKKzme6qNsLnvLzfkzzCrYbLYgHbJaWbcRnwQcDTPTepf2IYV4BMHouolg inUENvMihylaWHBzykm4V9i4moCZ/rPM4C4LLPoFL/UBQc3kInJTXBwG5frnrg2S9MWRsNkR 62YI3Itg1THjMdyL+xAsP7J6zvpiM4LWL0GMlkL3x2nE2B2GCpuB5z4kwBfBMHWSMatjwbBp zcPw8TGYdVR5NML74Pd4hycdgf1hYaXJmxRDi3WCYLQfOJf/chg+GTpHinlMPwhWO2u8TCBM NemR2wywjQe6sSEvJIZvdXVe6BRU3vvHZaCXCMyNOi8UCqvFg574gLPg/sAVhrmDoGfZyd52 a69YYlejCMOOxzJaA2vrVR4twHvAUb/CNrhOEfgIdFkkDBIMtfolHqNDoNTYwNvZb0a8duRH UzSdnSGNCqe0mWk0rVGHq6ncbuT6TS+ebYnN6PGnE3aESSTaLbj2y5As5Cjy6cJsOwKSEPkK us65WoJ0RWERpdWkaPNUFG1HB0i2yF8Q3m5NEuIMRS6VRVE5lHZ7yiL5ATpEnxbVf26YOGoV 9KsPfU8cTw3unU92XJ9TloelJZiM8qCJ1huWmB5fed0upTEKF8mVK12xl/KUMClWmiUSscl4 a39c3Jg08d3DwYKE6I6Sy6qw+mJ+Y4r96sao7aAmEF7HC560/zhv3pS+elMyN7Dn60pnf9la 27SzxFYRYBGxaaUiMpTQ0or/z0uy2EkDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/516HtVLJu3ABATXaEQlZN8PjmZA>
Subject: Re: [pim] Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03
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: Fri, 14 Sep 2018 03:47:09 -0000

Hi Reshad,

Do you mean it’s best to take out the whole augmentation of if:interfaces?

And besides it, do you have any other comments about the latest version of igmp snooping model?

Thanks a lot!

BR/Hongji
赵宏吉

From: Reshad Rahman (rrahman) <rrahman@cisco.com>
Sent: Friday, September 14, 2018 2:22 AM
To: Hongji Zhao <hongji.zhao@ericsson.com>
Cc: draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org; pim@ietf.org; YANG Doctors <yang-doctors@ietf.org>
Subject: Re: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Hongji,

Yes I believe it’s best to take out the augment of if:interfaces and have everything in the l2vpn-instance or bridge. Also, right now I believe  the model is inconsistent because PWs which can be used for mrouter-interface do not have any config outside of l2vpn-instance (but AC interfaces used as mrouter-interface do have mrouter config under if:interface ).

Regards,
Reshad.

From: Hongji Zhao <hongji.zhao@ericsson.com<mailto:hongji.zhao@ericsson.com>>
Date: Monday, September 10, 2018 at 10:18 PM
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Cc: "draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org<mailto:draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org>" <draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org<mailto:draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org>>, "pim@ietf.org<mailto:pim@ietf.org>" <pim@ietf.org<mailto:pim@ietf.org>>, YANG Doctors <yang-doctors@ietf.org<mailto:yang-doctors@ietf.org>>
Subject: RE: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Reshad,

Thanks for your reply.

In IGMP Snooping, the mrouter interface (i.e. Multicast router interface)  is the interface which connects to the multicast router. So there may be more than one mrouter interfaces in a l2vpn-instance or BRIDGE.
As you say,  an interface refers to l2vpn-instance and l2vpn-instance has lists of ACs and PWs for the same mrouter-interface functionality.

Here is how to configure and show Internet Group Management Protocol (IGMP) snooping for IPv4 multicast traffic on the Cisco 7600 series routers.
Gi1/1,Gi2/1,Fa3/48 are all the mrouter interfaces in vlan 1.

Displaying Multicast Router Interfaces
When you enable IGMP snooping, the router automatically learns to which interface the multicast
routers are connected.
To display multicast router interfaces, perform this task:
This example shows how to display the multicast router interfaces in VLAN 1:
Router# show ip igmp snooping mrouter vlan 1
vlan ports
-----+----------------------------------------
1 Gi1/1,Gi2/1,Fa3/48,Router


In the current igmp snooping model, we can configure static-mrouter-interface and static-l2-multicast-group either under the igmp-snooping-instance or under the augment /if:interfaces/if:interface. The purpose is to provide the customer more than one way to configure static-mrouter-interface and static-l2-multicast-group.
Maybe it looks in a mess.
If removing the static-mrouter-interface and static-l2-multicast-group under augment /if:interfaces/if:interface is better, I can remove them.


BR/Hongji
赵宏吉

From: Reshad Rahman (rrahman) <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Sent: Monday, September 10, 2018 6:25 AM
To: Hongji Zhao <hongji.zhao@ericsson.com<mailto:hongji.zhao@ericsson.com>>
Cc: draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org<mailto:draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org>; pim@ietf.org<mailto:pim@ietf.org>; YANG Doctors <yang-doctors@ietf.org<mailto:yang-doctors@ietf.org>>
Subject: Re: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Hongji,

I’ve taken a look at the latest rev, thanks for changing the model to augment l2vpn-instance and bridge, I believe this improves the model substantially. Before posting review comments on the latest version, I’d like to get clarifications/closure on the following (this was my 2nd main comment from initial review, email attached).

With the augment of if:interface, we have IGMP/MLD snooping data both under l2vpn-instance or bridge (via the augment) and under if:interface. To me such a segmentation of the IGMP/MLD snooping data is undesirable, is it not possible to have the data for static-mrouter-interface and static-l2-multicast-group under l2vpn-instance or bridge? For example, looking at static-mrouter-interface, we have leaf-lists of ACs/PWs and then under interface we have an l2vpn-instance name (should be leafref btw), so looks like interface refers to l2vpn-instance and l2vpn-instance has lists of ACs and PWs for the same mrouter-interface functionality. I don’t get it.

Regards,
Reshad.

2)            If:interface is augmented and has the name of the l2vpn-instance. This config seems redundant since under l2vpn-instance (draft-ietf-bess-l2vpn-yang)
there is already an interface-ref for AC (Access Circuit). Why not augment the L2VPN endpoint or AC?
--------Augmenting if:interface in this model is used to configure static multicast router interface (static-mrouter-interface) and static l2 multicast forward table.
                    They are the concepts in IGMP/MLD Snooping. Augmenting if:interface could cover BRIDGE and L2VPN scenario at the same time.




From: Hongji Zhao <hongji.zhao@ericsson.com<mailto:hongji.zhao@ericsson.com>>
Date: Monday, August 6, 2018 at 11:36 PM
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Cc: "draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org<mailto:draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org>" <draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org<mailto:draft-ietf-pim-igmp-mld-snooping-yang.all@ietf.org>>, "pim@ietf.org<mailto:pim@ietf.org>" <pim@ietf.org<mailto:pim@ietf.org>>
Subject: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Reshad,

I have updated the draft-ietf-pim-igmp-mld-snooping-yang according to your comments and upload the latest version.

In the new version I augmented the l2vpn-instance (from draft-ietf-bess-l2vpn-yang) and ieee802-dot1q-bridge module instead of the old reference style. I also addressed your other comments.

Could you please review it again? Thanks a lot!



https://datatracker.ietf.org/doc/draft-ietf-pim-igmp-mld-snooping-yang/


BR/Hongji

赵宏吉



FYI, easier to read https://datatracker.ietf.org/doc/review-ietf-pim-igmp-mld-snooping-yang-03-yangdoctors-early-rahman-2018-06-28/ than the email below.



On 2018-06-28, 5:42 PM, "yang-doctors on behalf of Reshad Rahman" <yang-doctors-bounces@ietf.org on behalf of rrahman=40cisco.com@dmarc.ietf.org<mailto:yang-doctors-bounces@ietf.org%20on%20behalf%20of%20rrahman=40cisco.com@dmarc.ietf.org>> wrote:



    Reviewer: Reshad Rahman

    Review result: On the Right Track



    YANG Doctor review of draft-ietf-pim-igmp-mld-snooping-yang-03 (by Reshad

    Rahman)

1)      The YANG model has a new container+list for bridges and

    “l2vpn-instances”.  Why not augment l2vpn-instance (from

    draft-ietf-bess-l2vpn-yang)? …



    I will have to re-review once the issues are addressed.