IETF Logo Mail Archive

Re: [netmod] Last Call: <draft-ietf-netmod-ip-cfg-12.txt> (A YANG Data Model for IP Management) to Proposed Standard

Andy Bierman <andy@yumaworks.com> Tue, 11 February 2014 19:01 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB461A06F1 for <netmod@ietfa.amsl.com>; Tue, 11 Feb 2014 11:01:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 fk_4EJwJD1nu for <netmod@ietfa.amsl.com>; Tue, 11 Feb 2014 11:00:59 -0800 (PST)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 048DF1A06E5 for <netmod@ietf.org>; Tue, 11 Feb 2014 11:00:58 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id f11so12228968qae.24 for <netmod@ietf.org>; Tue, 11 Feb 2014 11:00:58 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XsDDiq3fWn2MdAyKR44d4097b0h9ccuuAmRUtEzJEVo=; b=aks+NmL0YjnKTlO3BmEmEjDVlWkdRPnWqP17KOa4ncMczf4SPbqEZeOdIN3r66ejPi 21PQwPFQQdbX02pfPoR1KV5n5KDo93HEhYNFxtV4cylI2Bz0L2kDAnQFfwWLH1MnUm3T CrZEMRIUBriV4iWClwyzmOAYUoSJAUQmPh3k2f5DSdH+urJGgy84lVUa5nzYsbVVEEZf BpwNRRb7aUWsxu3Kn6GCJBTf9K2OdrbR1VXv6EoUnZXivweMG46bDrEiF6ur00YxqQL1 jiZfbfACeU5soIj5HxeXaJghuERMMXVjEvn2NDmt9HiWwrycACkF2m9NXAXF6fUkBmdp Hpzw==
X-Gm-Message-State: ALoCoQkmxwmdUgCh4HQYwAVKlo49NXowWiBWx4LIkrb/WO59I0tAvTbsPrLZhg1gUXEMzN1dLFnZ
MIME-Version: 1.0
X-Received: by 10.140.87.9 with SMTP id q9mr55960384qgd.94.1392145258262; Tue, 11 Feb 2014 11:00:58 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Tue, 11 Feb 2014 11:00:58 -0800 (PST)
In-Reply-To: <CF1FD10F.215E2%yiya@cisco.com>
References: <20140109142947.16194.98784.idtracker@ietfa.amsl.com> <CF1FBB8F.215CB%yiya@cisco.com> <20140211175618.GA78562@elstar.local> <CF1FD10F.215E2%yiya@cisco.com>
Date: Tue, 11 Feb 2014 11:00:58 -0800
Message-ID: <CABCOCHThk-s46RDzRNTdAg+fZJHD_RkuJYUARXVfZMb95NLECQ@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: "Yi Yang (yiya)" <yiya@cisco.com>
Content-Type: multipart/alternative; boundary="001a113a359c98470004f2261313"
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-ip-cfg-12.txt> (A YANG Data Model for IP Management) to Proposed Standard
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2014 19:01:05 -0000

Hi,

I think the title is close enough, especially since it is already past WGLC.
The 2nd sentence in the introduction is clear enough:

   The data model covers configuration of per-interface IPv4 and IPv6
   parameters, and mappings of IP addresses to link-layer addresses.


Global parameters may get added later to this RFC.



Andy


On Tue, Feb 11, 2014 at 10:21 AM, Yi Yang (yiya) <yiya@cisco.com> wrote:

> Hi Juergen,
>
> There are certain IP related management tasks are per host, not
> necessarily per interface. For example, enable/disable/rate-limit icmp, or
> enable DHCP on a router -- such tasks probably are more system-mgmt
> related.
>
> My concern is really about the title itself -- IMO, something like A YANG
> Data Model for Interface IP Management, or A YANG Data Model for IP
> Management of Interfaces, is more appropriate.
>
> Yi
>
>
> On 2/11/14 12:56 PM, "Juergen Schoenwaelder"
> <j.schoenwaelder@jacobs-university.de> wrote:
>
> >On Tue, Feb 11, 2014 at 04:38:33PM +0000, Yi Yang (yiya) wrote:
> >> One thing confuse me is the title of the draft -- when I first read it,
> >>I
> >> thought this is about overall IP configuration, including router,
> >> interface and etc. But it turns out this is really for interface only.
> >>Can
> >> we change the name of the draft to something more specific?
> >>
> >
> >What do you mean with "router interface and etc."? What do you think
> >is missing? Note that this document has passed WG last call and IETF
> >last call ended on 2014-01-23. Note also that there is
> >draft-ietf-netmod-routing-cfg-13 providing a core routing abstraction
> >to be augmented with routing protocol specific extensions.
> >
> >/js
> >
> >--
> >Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> >Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> >Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>

v2.23.0 | Report a Bug | By Email