Re: [pim] Suresh Krishnan's No Objection on draft-ietf-pim-igmp-mld-yang-13: (with COMMENT)

Xufeng Liu <xufeng.liu.ietf@gmail.com> Thu, 30 May 2019 11:19 UTC

Return-Path: <xufeng.liu.ietf@gmail.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 13DBD120104; Thu, 30 May 2019 04:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 wGfxj8_jfYOz; Thu, 30 May 2019 04:19:34 -0700 (PDT)
Received: from mail-it1-x12c.google.com (mail-it1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 7C4D7120100; Thu, 30 May 2019 04:19:34 -0700 (PDT)
Received: by mail-it1-x12c.google.com with SMTP id g24so9187316iti.5; Thu, 30 May 2019 04:19:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=f8ykvoE8Bha3vnXhXycBYaR/vlaD0T5DEnl/6XquUvQ=; b=Artat2Vqf9o5w7nsdVmh+8y12UMFVzXH+mdZ8OKmztcXq18DWkMiCn3chpYIX1VLFa wiH3Z5GQZKD/l5OsmNqQCM8cwsA+UjSOZ8vjTD3rRo8+noyFnbVjHzMWlz44o0eSTGXU 5yiaepxzPYeHF01ICsPAA/HunvKvE7oKMoNNIsFDTdfqIk5E8quVW67dWjE//qcOfQvx DtiXlVDfSHxuHUPLAvva4lynrjGtEr4z6Jf9XWDaanIm3UQD5AZ+E8AdK2+4+TRYb6Y6 m5n344Z8G7VZw3cIak8RgOeRtxYyDB9bOuSrc12RL8kJPvPXTcnHseom9eLmVXpSZHgV JIFA==
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; bh=f8ykvoE8Bha3vnXhXycBYaR/vlaD0T5DEnl/6XquUvQ=; b=BMc5cwj3kCY3UiSwByPmXshQ4x2STYii1mA/rpnMI01c87HPvuiA5a6b0ZPEmw3g2Z d/KvIxMYhowd/Rf5lKIbOR1Ha4ilHTsvF7oSuGnYpFkegsHRuZrVUdygKHP2uzU5Rri6 tqNYv5iSA6xbYKrcdyEEiOBBtIK1LVzm16fd8BaqGx+v03+rM+MxXkfknbjcex6o0qsl sz5AZcSH3DkqVm/nAb3HGVhRseVd54c4E33czSUKLQ3sLNyD4K0Jm0DsklTzHpd+oT3J egOg2AcXcvMo+TMa7394FgPUtTpNDELZnsAGvgrixWIyA1P3eZ0OFqzd5WoJoimdXzhu s0QA==
X-Gm-Message-State: APjAAAU93eObdtkJW6WoQkVwRW8YgpRz5ZAnQGypL/50L3xwgF6DObrG JpxTyEKdPICCfc6ES/L36CZBOViP1m3MT80YweQ=
X-Google-Smtp-Source: APXvYqy8hQAIPoiN6Hk5sBSatNbMqi/Mg3c/fAdk0iX6wBcnfI2nKF4sCb+Q0hhrtWA9ShUdFqfw/TLYP2fSD2rUkQg=
X-Received: by 2002:a24:4acd:: with SMTP id k196mr2334217itb.157.1559215173602; Thu, 30 May 2019 04:19:33 -0700 (PDT)
MIME-Version: 1.0
References: <155916744586.5441.2052365244437409953.idtracker@ietfa.amsl.com>
In-Reply-To: <155916744586.5441.2052365244437409953.idtracker@ietfa.amsl.com>
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Thu, 30 May 2019 07:19:22 -0400
Message-ID: <CAEz6PPRNT3=9VD8thKtAjj4T1Psw83OPxQ=c3pD26vdNLmdcug@mail.gmail.com>
To: Suresh Krishnan <suresh@kaloom.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pim-igmp-mld-yang@ietf.org, Stig Venaas <stig@venaas.com>, Alvaro Retana <aretana.ietf@gmail.com>, pim-chairs@ietf.org, pim@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008d1154058a191233"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/npY3y_RPlK79VE3h0ICA0Lk6LvE>
Subject: Re: [pim] Suresh Krishnan's No Objection on draft-ietf-pim-igmp-mld-yang-13: (with COMMENT)
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, 30 May 2019 11:19:37 -0000

Hi Suresh,

Thanks for the review and comments. Some of the version check could be done
in YANG, while the concern was the complexity added to the model, with a
cost to the usability. The authors will examine these cases and address
them using either approach as suggested. Maybe some of them use YANG and
others use explanation descriptions. In the case of the explanation
description, the system can do the validation at the backend and provide
feedback.

Thanks,
- Xufeng

On Wed, May 29, 2019 at 6:04 PM Suresh Krishnan via Datatracker <
noreply@ietf.org> wrote:

> Suresh Krishnan has entered the following ballot position for
> draft-ietf-pim-igmp-mld-yang-13: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pim-igmp-mld-yang/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I do have a general concern with the document in relation to its handling
> of
> multiple protocol versions. There are features in the yang models that
> should
> be conditional but they do not seem to be. Here are some examples.
>
> * The source specific features are to be used with IGMPv3 and MLDv2 and
> will
> not work with the earlier versions * The router alert check is not
> optional for
> MLD or IGMPv3, but is required to be disabled for compatibility with
> earlier
> versions of IGMP. I would also make this feature conditional on the IGMP
> version. If not you need to rethink the defaults for this.
>
> I would like to understand the authors' views on how they plan to address
> the
> potential consistency issues due to these features being unbound in the
> model.
> I would be fine if it is either addressed with yang constructs or with some
> explanatory text to this point.
>
>
>