[dhcwg] Mail regarding draft-gandhewar-dhc-v6-relay-initiated and draft-gandhewar-dhc-relay-initiated-release

김우태 <gmin1004@gmail.com> Fri, 04 September 2015 00:54 UTC

Return-Path: <gmin1004@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 D4EC91B4225 for <dhcwg@ietfa.amsl.com>; Thu, 3 Sep 2015 17:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.35
X-Spam-Level: **
X-Spam-Status: No, score=2.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, J_CHICKENPOX_25=0.6, MIME_8BIT_HEADER=0.3, 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 fTGXuN6Ptij1 for <dhcwg@ietfa.amsl.com>; Thu, 3 Sep 2015 17:54:38 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::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 045601B4242 for <dhcwg@ietf.org>; Thu, 3 Sep 2015 17:54:38 -0700 (PDT)
Received: by pacwi10 with SMTP id wi10so6468014pac.3 for <dhcwg@ietf.org>; Thu, 03 Sep 2015 17:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=limYxH8fIJC1QpVFqvNP5uVBSPleZXI6MEw3zSGehKY=; b=UGqS9862/8xZH0AWSOZz97KyfdqD6nqbUgi99xWdqCbdj86T0ceHcaiocb/ttcDJyp i266Z8m6WqmChLxd54p+rGQkCzBqcA12BY2Di9HW8wEBIx1oWexmklIokZJlUDQic65g fIUyX1LhQTggb0cTO8JNWzDoHoLvyh5TWAZTY/WMzthdILbCWSi0ph1AS7gQaPzFEyVu 8Kr9vOn2rxI9Ao0z/8cBmcyK7eFGDbcmJzXqN0bWgObSKHo4Hif+5ppxdl/jXCMVcKAU B/UeYxTn6xFpCE4Eq0ltMr9okNH/uLy2DlySCwFpedVuqsJvpSeeMGl7LKXfDcT2TXTj UcNQ==
X-Received: by 10.68.224.162 with SMTP id rd2mr1831145pbc.33.1441328077717; Thu, 03 Sep 2015 17:54:37 -0700 (PDT)
Received: from UTAEPC ([183.107.120.36]) by smtp.gmail.com with ESMTPSA id fd5sm359738pbb.53.2015.09.03.17.54.35 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 03 Sep 2015 17:54:36 -0700 (PDT)
From: =?ks_c_5601-1987?B?sei/7MXC?= <gmin1004@gmail.com>
To: <dhcwg@ietf.org>
References: <001501d0e6ab$d296f910$77c4eb30$@gmail.com>
In-Reply-To: <001501d0e6ab$d296f910$77c4eb30$@gmail.com>
Date: Fri, 4 Sep 2015 09:54:32 +0900
Message-ID: <001801d0e6ac$453ccbc0$cfb66340$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJ/8MCK/MR/a4ewM5q7kKddtCjq8ZzNdteQ
Content-Language: ko
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/kMb4rnVVdyEm_Cc3uBjq202xYJo>
Cc: sgandhewar@juniper.net
Subject: [dhcwg] Mail regarding draft-gandhewar-dhc-v6-relay-initiated and draft-gandhewar-dhc-relay-initiated-release
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: Fri, 04 Sep 2015 00:56:48 -0000

Hi All,

These Drafts offers a useful way to implement DHCPv4/v6 Resource Management
and we see value in these features and would like to see this as RFC. We
support this drafts to become RFC.
For example, in kt(Korea Telecom) field DHCP server, DHCP release message
generated only 0.05% of devices which IP address assigned in one day. And
99.95% devices didn't generate DHCP release messages in case of devices
power-off.

And in some cases, IPv4/v6 addresses regulations by administrator or DHCP
server can be impacted on IP assignment processes. But these features can
be very useful.

Regards,
utae.Kim
kt infrra laboratory
gmin1004@gmail.com