[dhcwg] fw:New Version Notification for draft-cui-dhc-dhcpv6-yang-03.txt

Linhui Sun <lh.sunlinh@gmail.com> Mon, 06 July 2015 11:36 UTC

Return-Path: <lh.sunlinh@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB5F1A0045 for <dhcwg@ietfa.amsl.com>; Mon, 6 Jul 2015 04:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.899
X-Spam-Level:
X-Spam-Status: No, score=-0.899 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, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, SPF_PASS=-0.001] autolearn=no
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 ovzalafgaSld for <dhcwg@ietfa.amsl.com>; Mon, 6 Jul 2015 04:36:46 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 1D05E1A0006 for <dhcwg@ietf.org>; Mon, 6 Jul 2015 04:36:40 -0700 (PDT)
Received: by pacgz10 with SMTP id gz10so20556296pac.3 for <dhcwg@ietf.org>; Mon, 06 Jul 2015 04:36:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:to:references:subject:mime-version :content-type:content-transfer-encoding:content-disposition; bh=oYjRGTJ0sbxW03Lm9yQgSp/EO4fHN5uo7gSEmilmKFk=; b=LklifL5rBVGjVD0VsVRaN/UgPGxJ8zQUot36Oiaog5YVaeSG5gXsicMcIcO1i2E9+1 wBuy+poYM/ZEZMU97smpsh6ws5xfcKxGXW7uyv4TyUnFrZXXAYiGna2rvi3FQvXt7hoU G3syi5U10wf+9NMB0mT42xJ/Yxh7fwpQ/kyKkywR4nhhZUfa1fEjS3vtkO2i18jKAJAC PMeS00EnU+gDL6DP9yTcwSuJjeaomfpKQAFwsboQSYyzC0RAOgcygvym6MxZV5BDN4s4 RCb7f77b7VapOg/Kmh4kdM8Gq/I5L4U/8P6+0YGFv7JaJHBHh17QYUH9JOv8k2y+i9t1 Qi2A==
X-Received: by 10.68.91.197 with SMTP id cg5mr105535018pbb.26.1436182599724; Mon, 06 Jul 2015 04:36:39 -0700 (PDT)
Received: from [127.0.0.1] ([119.28.3.169]) by mx.google.com with ESMTPSA id os7sm17985534pdb.51.2015.07.06.04.36.37 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Jul 2015 04:36:38 -0700 (PDT)
Message-ID: <559a6846.4784460a.3697.0735@mx.google.com>
X-Google-Original-Message-ID: <emc_0f455b7185df4354bf61d01f534fb52b>
Date: Mon, 06 Jul 2015 19:36:34 +0800
From: Linhui Sun <lh.sunlinh@gmail.com>
To: dhcwg <dhcwg@ietf.org>
References: <20150704024530.18232.76335.idtracker@ietfa.amsl.com>
X-Mailer: YoMail.Win
X-YoMail-GUID: emc_0f455b7185df4354bf61d01f534fb52b
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
Content-Disposition: inline
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/3CHlOe8TAsZKAV4pfzyKbhN36Nc>
Subject: [dhcwg] fw:New Version Notification for draft-cui-dhc-dhcpv6-yang-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jul 2015 11:36:48 -0000

Hi all,

We've updated a new version for draft-cui-dhc-dhcpv6-yang-03. The major changes include,

1) Add a description in section 1 to explain why the DHCPv6 client model is considered.
2) Add containers and lists in the server, relay and client portions respectively to achieve easy configuration of multiple sets of possible options.
3) A hierarchy is introduced in the server portion to allow administrator configuring the server with different parameters (e.g. option sets) at different levels (i.e. global, network, addr/prefix pool level and host level).
4) Correct errors in data types.

The IETF93 is approaching, please could you review the new version and comments are welcome.

Best regards, 
Linhui

< internet-drafts@ietf.org> 2015-07-04 10:45:30 wrote:


A new version of I-D, draft-cui-dhc-dhcpv6-yang-03.txt
has been successfully submitted by Linhui Sun and posted to the
IETF repository.


Name: draft-cui-dhc-dhcpv6-yang
Revision: 03
Title: YANG Data Model for DHCPv6 Configuration
Document date: 2015-07-03
Group: Individual Submission
Pages: 66
URL: https://http://www.ietf.org" rel="nofollow">http://www.ietf.org" rel="nofollow">www.ietf.org/internet-drafts/draft-cui-dhc-dhcpv6-yang-03.txt
Status: https://datatracker.ietf.org/doc/draft-cui-dhc-dhcpv6-yang/" rel="nofollow">https://datatracker.ietf.org/doc/draft-cui-dhc-dhcpv6-yang/" rel="nofollow">https://datatracker.ietf.org/doc/draft-cui-dhc-dhcpv6-yang/
Htmlized: https://tools.ietf.org/html/draft-cui-dhc-dhcpv6-yang-03" rel="nofollow">https://tools.ietf.org/html/draft-cui-dhc-dhcpv6-yang-03" rel="nofollow">https://tools.ietf.org/html/draft-cui-dhc-dhcpv6-yang-03
Diff: https://www.ietf.org/rfcdiff?url2=draft-cui-dhc-dhcpv6-yang-03" rel="nofollow">https://www.ietf.org/rfcdiff?url2=draft-cui-dhc-dhcpv6-yang-03" rel="nofollow">https://www.ietf.org/rfcdiff?url2=draft-cui-dhc-dhcpv6-yang-03


Abstract:
There has no unified method to configure DHCPv6 server ,relay and
client itself, always pre-configured manually by operators.


IETF netmod WG has developed a general data model for NETCONF
protocol, YANG data model [RFC6020].


This document defines a YANG data model for the configuration and
management of DHCPv6 server, DHCPv6 relay and DHCPv6 client. With
this model, the operators can configure and manage the devices by
using NETCONF.









Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.


The IETF Secretariat