Re: [pim] Apply for WGLC about draft-ietf-pim-igmp-mld-snooping-yang

Stig Venaas <stig@venaas.com> Tue, 08 January 2019 18:26 UTC

Return-Path: <stig@venaas.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 A37C9130F70 for <pim@ietfa.amsl.com>; Tue, 8 Jan 2019 10:26:16 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=venaas-com.20150623.gappssmtp.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 0AbapwM58AjR for <pim@ietfa.amsl.com>; Tue, 8 Jan 2019 10:26:14 -0800 (PST)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479D0130F6D for <pim@ietf.org>; Tue, 8 Jan 2019 10:26:14 -0800 (PST)
Received: by mail-ed1-x531.google.com with SMTP id h15so5187334edb.4 for <pim@ietf.org>; Tue, 08 Jan 2019 10:26:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=qFwbmZtpidU3gaBgIz/NQdgSHsNUnPsc3F8KFxBLj8c=; b=1bqrCfSGQLM4V9hA1ANYlMeYOFEkR4hFgDPuvMks6gHUeVKkvOIi+8RXWqqWuopPyR E6UhCHJXk4xzTUNlA1IEVuVr+tUpVTs8crLqjNOHDnFRslnrNmXEZBclnvRgkuuZxhpP 2niaYHQb9215mNOax4CVVuAMctWm7d+iAYU898i07Jzy+J6KzY8iWhIrS9buhVet9Q53 9iXHMpQUjlitvtvsRunn04Ww1o6lIyVX1cUB/lnOg2CBHbqfZqDKy5j9gIRJqVd5p3x5 gx4dzETzUjprzQ8J910pSpyxMd1mEj29vT6iKZWYeOhQd6yoMAUpX/Q3dDVLhSgw4wyl bPfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=qFwbmZtpidU3gaBgIz/NQdgSHsNUnPsc3F8KFxBLj8c=; b=h/THxqnhCuwocXOWtmUFcRYdRxhWj5cJyEgr1UNGeDe2LPZKKq+oWuFxcXFPHi1SBS 0nUzMMLSyJ6mmOp+TXPAhgWXOzEsjs1r8Scq804PzR+t1mF3ijZaG3mmARo8ShxdYNOE PMf+8V1rG+0O1FQay5ANNWbeYSP4vjCedRolOlWXaaHDugG+yLnMYZJS/ZqmxTDRBMtb rrpUEe9lr9W42EsgWJlzjZOB0J6Xjo1UCzd+Ef1Kj7P/yxemJBw68LyQ2lIGh5QkWnCV Ia/Z4P170OXc5W3wviismHBVTTacIXdJGeJ1S5Qgl8jLaDz3ws2hvwvDGiR0RYNhu5mh CK7g==
X-Gm-Message-State: AJcUukfFFccas4Bxd/1qEvbvCt+6xTRYhM4E4f4cMTZS7fRVfMGqp3qF RMI1ApbZzYdQh6TUNGCLW4Tgj/k27bSZe2BH7xXJiDtdgUqg4Q==
X-Google-Smtp-Source: ALg8bN7AgtJ17jc43iO7mfCVuok+/HnScBNpSg//HvvB9dZz7pnJI4LiAm1YnNBYOlu1k9mbDdaghquzfKjeyT3qw8M=
X-Received: by 2002:a50:acc3:: with SMTP id x61mr3132284edc.76.1546971972709; Tue, 08 Jan 2019 10:26:12 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR07MB41929655CC0AD35AC4F46EE196BD0@VI1PR07MB4192.eurprd07.prod.outlook.com> <alpine.DEB.2.20.1812201148160.3869@uplift.swm.pp.se> <VI1PR07MB4192C5D503B8FEA0062CFC3C96B80@VI1PR07MB4192.eurprd07.prod.outlook.com> <alpine.DEB.2.20.1812210747430.3869@uplift.swm.pp.se> <VI1PR07MB419267D6E06028E8FC1615E196B80@VI1PR07MB4192.eurprd07.prod.outlook.com> <alpine.DEB.2.20.1812211029580.3757@uplift.swm.pp.se> <VI1PR07MB4192CB6B6780E9AB79D708C2968A0@VI1PR07MB4192.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB4192CB6B6780E9AB79D708C2968A0@VI1PR07MB4192.eurprd07.prod.outlook.com>
From: Stig Venaas <stig@venaas.com>
Date: Tue, 8 Jan 2019 10:26:01 -0800
Message-ID: <CAHANBtJJ03wEUH6A+UauqmdBwQYrq1y5My6k_Rwdp22Ek+_X9g@mail.gmail.com>
To: Hongji Zhao <hongji.zhao@ericsson.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, Michael McBride <Michael.McBride@huawei.com>, "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/OXNURtPv2h5K6wHAJ-C4jRWWz60>
Subject: Re: [pim] Apply for WGLC about draft-ietf-pim-igmp-mld-snooping-yang
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: Tue, 08 Jan 2019 18:26:17 -0000

Hi

There have been some changes to draft-ietf-pim-igmp-mld-yang based on
YANG doctor input, and I believe some more are planned. Please
consider whether any of these changes might apply here as well. I'm
wondering in particular if there are any high level design changes.

Thanks,
Stig

On Mon, Jan 7, 2019 at 11:16 PM Hongji Zhao <hongji.zhao@ericsson.com>; wrote:
>
> Hi Mikael,
>
>  Regarding the leaf expire, we have changed type into rt-types:timer-value-seconds16.  This type could express "infinity".
>  Thanks a lot !
>
> BR/Hongji
> 赵宏吉
>
> -----Original Message-----
> From: Mikael Abrahamsson <swmike@swm.pp.se>;
> Sent: Friday, December 21, 2018 5:37 PM
> To: Hongji Zhao <hongji.zhao@ericsson.com>;
> Cc: Stig Venaas <stig@venaas.com>;; Michael McBride <Michael.McBride@huawei.com>;; pim@ietf.org
> Subject: RE: [pim] Apply for WGLC about draft-ietf-pim-igmp-mld-snooping-yang
>
> On Fri, 21 Dec 2018, Hongji Zhao wrote:
>
> > Hi Mikael,
> >
> > This is a "mandatory true", it means all the dynamic groups need expire. The group(who is read-only)  list only includes dynamic groups.
> > I suppose it won't be a statically configured group.
> >
> > Do you think it should not be "mandatory true"?  OR the group (who is read-only) should include the statically configured group?
>
> I believe operational data should show all groups currently being handled, regardless if they're statically configured or not. I want to be able to see other aspects of them, so it would be a bad idea if they were omitted from the list just because they're statically configured.
>
> Minimum change could be to either remove the "mandatory true;" and say that groups without known expiry time doesn't report this value, or one could say that uint32 max value means "infinity". There could be other ways.
>
> I have no strong opinion how to handle this, but I'd like to see it defined in the model how to handle statically configured groups with no defined expiry time.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se