Re: [pim] Last Call: <draft-ietf-pim-igmp-mld-yang-10.txt> (A YANG data model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)) to Proposed Standard

Xufeng Liu <xufeng.liu.ietf@gmail.com> Mon, 29 April 2019 15:37 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 D0D3512032C; Mon, 29 Apr 2019 08:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_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 s-fsOD78-i9e; Mon, 29 Apr 2019 08:37:39 -0700 (PDT)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 17F111200F9; Mon, 29 Apr 2019 08:37:39 -0700 (PDT)
Received: by mail-it1-x136.google.com with SMTP id k64so9584855itb.5; Mon, 29 Apr 2019 08:37:39 -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=7fEVy+BUfduLPFVPfkUK3PAHY4mBks7xqCYskWuC7Ko=; b=GAZhkEvy+H5Ddk5MF1GfHcgl4AMI2aAIxZGgcI85QYmQ9Yzqnp21RBRS4hxOEeIGFu dB0++UZXUaTPdeOrKaSD4J3ifNLW1mZXEBOVUInk9X5oa/NIYSVv1J+sqAPEmOHatXEo pakulSUkqiZjuYY3OvNtKGn1D9649T9kLYrPyd2SRM4KzKJFYh7VD3BlN4gD1MfSIWas YJpR/C0VDFy2PEnGjLw1j2hqxBfUwBFuugP1V0H81G+F7ed9JACbIodxV0Bzr0SCnOVI PV32RdivHMhwtqUFUQazUN8G/mr/rlPNabh+NZLGnGPWUGhQd1VDZg/BcI8x6tclxz8k nVIg==
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=7fEVy+BUfduLPFVPfkUK3PAHY4mBks7xqCYskWuC7Ko=; b=cina5nO9YrqTkcPJ+ZstIojgbKTQdQg3k/W/7HF9E697p6I2zJeg2c/6u69R6Ysacr KOANlaKknC030wPB2s4tSWdJssvCJq+v8haGVNWLMHPu7jY0y8UI+AZdbtHdWs92S+gt 3SBbqhkhCLYn4e8CgWJk7RadUhhSCY2qPEIkntR74ozC2Knt7D19Ex+Z7BqG3wFpSSOM I/adIKSqvwqKBJ4u6YNdkBPz+/U1+8mmAuOP0ufy4/kIQAAbzAMChO0F1S2/G5OFVjEc IlKtEwpilPqnN0iD5eVMtghgVXnPn2VDQRHUgkFH/3hRbmOTmyrVSEGcs3IAUea7T1TF fdkw==
X-Gm-Message-State: APjAAAUWwtE7f+2HjNprW9qa8wHZj6sjEl5FJEbVTulROrUM+/GdSFar aHF+PGgNlZRQemQdCt6y/UpzQ8TOuq+Uwp4aoLk=
X-Google-Smtp-Source: APXvYqyu78XzIXZjbVsjmOlauupTIfbxkkVdkH/MQ9REE2IoOSJECnNCmgnCcYbxYcFaiSa9fOs3g3dYRZQHhhkDDKc=
X-Received: by 2002:a24:4682:: with SMTP id j124mr19538390itb.90.1556552258407; Mon, 29 Apr 2019 08:37:38 -0700 (PDT)
MIME-Version: 1.0
References: <154844808422.29188.6676721895526799.idtracker@ietfa.amsl.com> <016301d4b598$12950700$4001a8c0@gateway.2wire.net>
In-Reply-To: <016301d4b598$12950700$4001a8c0@gateway.2wire.net>
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Mon, 29 Apr 2019 11:37:27 -0400
Message-ID: <CAEz6PPRUH9Ox49OgdqbdVmn9KiWWXxGAOfkWbJ2cwe_EmTpEXg@mail.gmail.com>
To: tom petch <daedulus@btconnect.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "pim-chairs@ietf.org" <pim-chairs@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "draft-ietf-pim-igmp-mld-yang@ietf.org" <draft-ietf-pim-igmp-mld-yang@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006fd39d0587ad10df"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/v8DjclefUkcvAwuqN4_s5l2Gz4A>
Subject: Re: [pim] Last Call: <draft-ietf-pim-igmp-mld-yang-10.txt> (A YANG data model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)) 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: Mon, 29 Apr 2019 15:37:42 -0000

Hi Tom,

Thanks for the review. We have posted the updated
https://tools.ietf.org/html/draft-ietf-pim-igmp-mld-yang-11 to address
these issues, along with other review comments.

Best regards,
- Xufeng

On Sat, Jan 26, 2019 at 11:57 AM tom petch <daedulus@btconnect.com>; wrote:

> Some initial  thoughts on this I-D
>
> Prefer 'Abstract' before 'Copyright' and 'Status'
>
[Xufeng]: Changed the order.

>
>    | acl       | ietf-access-control-list | [I-D.ietf-acl-yang] |
> better to have
>    | acl       | ietf-access-control-list | [RFC YYYY] |
> Note to RFC Editor please replace YYYY with number assigned to draft-
> ietf-netmod-acl-model
>
[Xufeng]: Fixed.

>
> YANG module needs the Copyright statement
>
[Xufeng]: Fixed.

>
> 4. IGMP and MLD YANG Modules
> suggests that there are two modules but I only see one
>
[Xufeng]: The text is wrong. Fixed. There is only one module.

>
>       import ietf-inet-types {
> and other imports need a reference clause to identify the RFC; for acl
> you need such as
> RFC YYYY "Network Access Control List (ACL) YANG Data Model",
> Note to RFC Editor please replace YYYY with number assigned to draft-
> ietf-netmod-acl-model
> ( you can put all RFC Editor Notes in one place at the front - they
> prefer it this way)
>
[Xufeng]: Fixed.

>
>       revision 2019-01-03 {
> there must only be one revision clause stating 'Initial revision' with
> date of publication supplied by RFC Editor to match that on the file
> statement
>
[Xufeng]: Removed the extra revision statetments.

>
> several lines are too long e.g.
>              If QQIC >= 128, QQIC represents a floating-point value as
> follows:
>
[Xufeng]: Fixed these lines and other lines with the same problem.

>
> 5. Security Considerations
>    transport is TLS [RFC5246].
> this is now superseded
>
[Xufeng]: Updated.

>
> 6. IANA Considerations
>    Names registry [RFC7950]:
> this is a poor reference since all it does is tell you to go to RFC6020;
> better to tell the reader to go straight there.
>
[Xufeng]: Use RFC6020 now.

>
>    [I-D.ietf-netmod-rfc6087bis] Bierman, A., "Guidelines for Authors
> this is now out of date - RFC8407
> (and it tells you to do most of what I have listed above:-)
>
[Xufeng]: Updated.

>
> Tom Petch
>
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>;
> To: "IETF-Announce" <ietf-announce@ietf.org>;
> Cc: <pim-chairs@ietf.org>;; <pim@ietf.org>;;
> <draft-ietf-pim-igmp-mld-yang@ietf.org>;
> Sent: Friday, January 25, 2019 8:28 PM
>
> >
> > The IESG has received a request from the Protocols for IP Multicast WG
> (pim)
> > to consider the following document: - 'A YANG data model for Internet
> Group
> > Management Protocol (IGMP) and
> >    Multicast Listener Discovery (MLD)'
> >   <draft-ietf-pim-igmp-mld-yang-10.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
> > ietf@ietf.org mailing lists by 2019-02-08. 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) devices.
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-pim-igmp-mld-yang/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-ietf-pim-igmp-mld-yang/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
> >
>
>