Re: Yangdoctors early review of draft-ietf-rtgwg-routing-types-04

Jeff Tantsura <jefftant@gmail.com> Tue, 13 June 2017 07:45 UTC

Return-Path: <jefftant@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3E61289B0; Tue, 13 Jun 2017 00:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, 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 mL0397LIDymH; Tue, 13 Jun 2017 00:45:31 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 8CDE6128656; Tue, 13 Jun 2017 00:45:30 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id v20so63840902lfa.1; Tue, 13 Jun 2017 00:45:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+qZYrrc8lyq3iSWcVzCl87nxuWGFWq+51yGfweMVerQ=; b=SHs21scf7/gn0yhREK+VKLSofJfNHOSggpKV4JZTJ4CPwt4++CT8JrXGxboiElG9V2 VzE6gwME6TT08BrXMgX/6f6RtvKEaEK3j/IopY5yaWqU0aeR93kHaaBEF2YjjFfiAzGv AK2AjLrFlpXnyRi2PH3wOVA29D0joNrKtNROSst199yJ/xSPg1z5YsA5iyUIm5lyAydo aOy4wvBqGU3rZXIFqy61RcJlR0P09g38AWruJHFPQVo2VWt97bblHjkb+bVOTRZ1fkUy xJcgi31F20uXmwI90pc40T+KbV9O4S2lP/HViAA0TR87IB+DGW/f+8I1z4cJnQnRh/Tu Y6IA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+qZYrrc8lyq3iSWcVzCl87nxuWGFWq+51yGfweMVerQ=; b=i6lBkQbf5QlaPaPVJy5lfbEQpFkBwxNArTZxoXMrYLchYWgTARHsCJiWNvZwni76jf Hgl6pXK3j3NKT6tI5t7WS5spD6+9iC/jDxP/VyF5Tw9YK9OPrpuxVwAP3KNiMQYfsfJT T2iDRlnfrcuKnx313T7LmWa1XOXLG5ziXk6dZcPCXlgp2qWCztk4Ekhu5hrucSvUO/sl D9YrI7ilqyUPu89yQsrzsu1FjlZfHC5wNA9rUIGhyn8CG8JnMjfT8bfZELFxSLS8ammk jJbn2l9Va9pK5uqvntCcwCu1XVtOciemSYNBx5D4N1V9R3XJi1cse8qOBMoiC+mf65Ci y0gA==
X-Gm-Message-State: AODbwcDZoD207SH+3K3pucZU/Go4j4x55grJvVaAFB9mC6s2Az+MU04B 8TfrGmy6C7BrmJxi/aI=
X-Received: by 10.46.92.137 with SMTP id q131mr5585788ljb.124.1497339928416; Tue, 13 Jun 2017 00:45:28 -0700 (PDT)
Received: from [10.119.233.150] (195-22-91-10-static.se.customer.tdc.net. [195.22.91.10]) by smtp.gmail.com with ESMTPSA id x13sm3198459ljd.64.2017.06.13.00.45.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Jun 2017 00:45:27 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: Yangdoctors early review of draft-ietf-rtgwg-routing-types-04
From: Jeff Tantsura <jefftant@gmail.com>
X-Mailer: iPad Mail (14F89)
In-Reply-To: <D564AC33.B2C6F%acee@cisco.com>
Date: Tue, 13 Jun 2017 00:45:26 -0700
Cc: Chris Bowers <cbowers@juniper.net>, Routing WG <rtgwg@ietf.org>, RTG YANG Design Team <rtg-dt-yang-arch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB43025D-7A16-4084-A597-1E35B10D7A72@gmail.com>
References: <823c6e8a-9544-5544-8a99-d05c0ffc7017@cesnet.cz> <D54B2AD5.B085A%acee@cisco.com> <6fc7d6b3-bf13-6861-01d3-c0ed52532629@cesnet.cz> <D564AC33.B2C6F%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/VpZ6CEdbdrClWtx_sS5c_IM71LA>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jun 2017 07:45:33 -0000

Hi Acee,

Thanks, will do.

Regards,
Jeff

> On Jun 12, 2017, at 17:39, Acee Lindem (acee) <acee@cisco.com> wrote:
> 
> Jeff, Chris, 
> 
> The authors believe we are ready for a WG last call.
> 
> Thanks,
> Acee 
> 
>> On 6/12/17, 2:32 AM, "Radek Krejčí" <rkrejci@cesnet.cz> wrote:
>> 
>> Hi Acee,
>> 
>> sorry for the delay. I've checked the changes and the document as well as
>> both the modules seem fine to me now.
>> 
>> Regards,
>> Radek
>> 
>> 
>> Dne 24.5.2017 v 18:23 Acee Lindem (acee) napsal(a):
>>> Hi Radek, 
>>> 
>>> I believe I have addressed your YANG Doctor comments in the -05 version
>>> of
>>> the draft. I used the template in RFC6087Bis, Appendix C which resulted
>>> in
>>> some reorganization of ietf-routing-types.
>>> 
>>> Thanks,
>>> Acee 
>>> 
>>>> On 5/24/17, 6:45 AM, "Radek Krejčí" <rkrejci@cesnet.cz> wrote:
>>>> 
>>>> Reviewer: Radek Krejčí
>>>> Review result: Ready with Nits
>>>> 
>>>> I have reviewed changes made to draft-ietf-rtgwg-routing-types between
>>>> revision 02 and 04 (04 was published just a week after 03). The main
>>>> change is splitting the module into 2 modules: ietf-routing-types and
>>>> iana-routing-types.
>>>> 
>>>> iana-routing-types:
>>>> - since it is IANA-maintained module, IANA should be the 'organization'
>>>> and also the 'contact' value should be changed accordingly (see
>>>> iana-if-type)
>>>> 
>>>> ietf-routing-types:
>>>> - please follow the contact template available in RFC 6087 Appendix B
>>>> (or
>>>> RFC6087bis, Appendix C)
>>>> 
>>>> draft text:
>>>> - if iana-routing-types is supposed to be IANA-maintained module, isn't
>>>> IANA also supposed to be XML registrant contact (IANA Considerations
>>>> section)? 
>>>> - my fault from previous review - since the module imports
>>>> ietf-yang-types, it MUST contain reference to its RFC, which is RFC
>>>> 6991
>>>> (not RFC 6021 as I wrote in my review). So move RFC 6991 reference from
>>>> Informative references section into Normative references where it will
>>>> replace reference to RFC 6021.
>>>> 
>>>> Radek
>> 
>