Re: [pim] [yang-doctors] Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot!

"Acee Lindem (acee)" <acee@cisco.com> Mon, 01 October 2018 14:07 UTC

Return-Path: <acee@cisco.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 16834130DFE; Mon, 1 Oct 2018 07:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.955
X-Spam-Level:
X-Spam-Status: No, score=-14.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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
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 1geUHn7m-m5V; Mon, 1 Oct 2018 07:07:07 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CF98130DFA; Mon, 1 Oct 2018 07:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=30070; q=dns/txt; s=iport; t=1538402827; x=1539612427; h=from:to:cc:subject:date:message-id:mime-version; bh=DLTUySuohNr7k64R6tOVnKK7SjKWruvDWr6u8Jhw5W0=; b=AZwlVxYXJHCRgBF+YG4FjR3FUexXw/OAuiNNZxd7VuFYZPzsIWDwqhsq 00wAy4i/jWELwKMSCaJypuCHJqRjVkSElmSbD5ZBtLRXEzxxYd/XljB19 TrG9/HIDVusn+x/H/Hrdmf7YMKsCgwB+eCn1S84weBikJXK0rlV2+gLnj U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AbAABAKbJb/4sNJK1aGQEBAQEBAQEBAQEBAQcBAQEBAQGBVIEUd2Z/KAqDapQugWglmFQLhGwCF4N5ITcVAQMBAQIBAQJtKIU4AQECAyNWEgEGAhEDAQEBIQcDAgQwFAkKBAENBYMhAYEdZIkEm02BLooKiwIXggCBEicME4IeLoUeFoJLMYIEIgKJRIQ4hXuJMgkCkDIXgUeEW4ktlQoCERSBJTMigVVwFWUBgkEJgkSOB2+LZ4EfAQE
X-IronPort-AV: E=Sophos;i="5.54,327,1534809600"; d="scan'208,217";a="178818423"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Oct 2018 14:07:05 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w91E75KU009390 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Oct 2018 14:07:05 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 1 Oct 2018 10:07:04 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1395.000; Mon, 1 Oct 2018 10:07:04 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, Hongji Zhao <hongji.zhao@ericsson.com>
CC: YANG Doctors <yang-doctors@ietf.org>, "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>
Thread-Topic: [yang-doctors] Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot!
Thread-Index: AQHUWZAIg0bAVGEH+UWAo2QEnUAQog==
Date: Mon, 01 Oct 2018 14:07:04 +0000
Message-ID: <9FBAE41A-6E7A-4240-9372-10656CD1E018@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.9.101]
Content-Type: multipart/alternative; boundary="_000_9FBAE41A6E7A4240937210656CD1E018ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.145, xch-rtp-005.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/MdRK-ocZ8Xdu-b2uzFCdJgz4ozw>
Subject: Re: [pim] [yang-doctors] Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot!
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: Mon, 01 Oct 2018 14:07:11 -0000

Hi Hongji, Reshad,
I agree with Reshad. While both hierarchies have been implemented on various network devices, it is more straight forward to include protocol interface configuration and state in the hierarchy of the protocol instance rather than have it on the interface itself. The only time you want to place it on the interface is when the protocol instance is scoped to a single interface (e.g., VRRP).
Thanks,
Acee

From: yang-doctors <yang-doctors-bounces@ietf.org> on behalf of "Reshad Rahman (rrahman)" <rrahman@cisco.com>
Date: Monday, October 1, 2018 at 9:22 AM
To: Hongji Zhao <hongji.zhao@ericsson.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "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>
Subject: Re: [yang-doctors] Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot!

Hi Hongji,

I understand that these statistics are interface specific, but I still don’t understand why you think augmenting if:interface is better, can you please explain? For me these counts are IGMP/MLD snooping specific, so should be under the snooping instance.

As an example, take a look at section 2.7 of draft-ietf-ospf-yang, the per-interface OSPF counters are under OSPF protocol container, not augment of if:interface.

Regards,
Reshad.

From: Hongji Zhao <hongji.zhao@ericsson.com>
Date: Tuesday, September 25, 2018 at 12:30 AM
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>
Subject: RE: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot!

Hi Reshad,

The statistics are related with igmp-mld-snooping, not only with mrouter interface.
The query is the number of  igmp query messages. The membership-report-v1/2/3 indicates the number of membership report v1/2/3 messages. The leave indicates the number of leave messages.
The pim is the number of pim hello messages. They are used to generate and maintain the entries for l2 multicast forwarding, multicast router interface, IGMP&MLD snooping membership, etc.

So I think keeping them under augment of if:interface is better.  What do you think of that?
Thanks!

BR/Hongji
赵宏吉

From: Reshad Rahman (rrahman) <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Sent: Thursday, September 20, 2018 8:26 PM
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,

It looks like those statistics are needed only for interfaces (not for PWs) , so you could keep them under augment of if:interface, or put those stats under bridge-mrouter-interface and l2vpn-mrouter-interface-ac in the snooping-instance. My preference is for the latter.

Regards,
Reshad.

From: Hongji Zhao <hongji.zhao@ericsson.com<mailto:hongji.zhao@ericsson.com>>
Date: Monday, September 17, 2018 at 10:28 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,

In augment /if:interfaces/if:interface, besides mrouter related data, there are still some statistics related with igmp-mld-snooping.
If take out the whole augmentation of if:interfaces, the statistics will be lost.  What do you think of that?

augment /if:interfaces/if:interface:
    +--rw igmp-mld-snooping
       +--ro statistics
          +--ro received
          |  +--ro query?                  yang:counter64
          |  +--ro membership-report-v1?   yang:counter64
          |  +--ro membership-report-v2?   yang:counter64
          |  +--ro membership-report-v3?   yang:counter64
          |  +--ro leave?                  yang:counter64
          |  +--ro non-member-leave?       yang:counter64
          |  +--ro pim?                    yang:counter64
          +--ro sent
             +--ro query?                  yang:counter64
             +--ro membership-report-v1?   yang:counter64
             +--ro membership-report-v2?   yang:counter64
             +--ro membership-report-v3?   yang:counter64
             +--ro leave?                  yang:counter64
             +--ro non-member-leave?       yang:counter64
             +--ro pim?                    yang:counter64

BR/Hongji
赵宏吉