Re: I-D ACTION:draft-bykim-ipv6-hpd-00.txt

"JORDI PALET MARTINEZ" <jordi.palet@consulintel.es> Thu, 23 October 2003 16:04 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02719 for <ipv6-archive@odin.ietf.org>; Thu, 23 Oct 2003 12:04:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChwN-0005gU-JU for ipv6-archive@odin.ietf.org; Thu, 23 Oct 2003 12:04:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NG3xGx021844 for ipv6-archive@odin.ietf.org; Thu, 23 Oct 2003 12:03:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChwN-0005gF-EW for ipv6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 12:03:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02670 for <ipv6-web-archive@ietf.org>; Thu, 23 Oct 2003 12:03:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AChwK-0003SL-00 for ipv6-web-archive@ietf.org; Thu, 23 Oct 2003 12:03:56 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AChwK-0003SI-00 for ipv6-web-archive@ietf.org; Thu, 23 Oct 2003 12:03:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChvS-0005Vi-Gk; Thu, 23 Oct 2003 12:03:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChv5-0005Sq-SQ for ipv6@optimus.ietf.org; Thu, 23 Oct 2003 12:02:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02589 for <ipv6@ietf.org>; Thu, 23 Oct 2003 12:02:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AChv4-0003Pq-00 for ipv6@ietf.org; Thu, 23 Oct 2003 12:02:38 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es) by ietf-mx with esmtp (Exim 4.12) id 1AChv1-0003Ml-00 for ipv6@ietf.org; Thu, 23 Oct 2003 12:02:38 -0400
Received: from consulintel02 ([202.133.104.44]) (authenticated user jordi.palet@consulintel.es) by consulintel.es (consulintel.es [127.0.0.1]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 39-md50000000006.tmp for <ipv6@ietf.org>; Thu, 23 Oct 2003 18:04:13 +0200
Message-ID: <02e501c3997f$12d2ff60$9402a8c0@consulintel.es>
Reply-To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ipv6@ietf.org
References: <200310231532.LAA29517@ietf.org>
Subject: Re: I-D ACTION:draft-bykim-ipv6-hpd-00.txt
Date: Fri, 24 Oct 2003 00:02:30 +0800
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Thu, 23 Oct 2003 18:04:13 +0200 (not processed: message from valid local sender)
X-MDRemoteIP: 202.133.104.44
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
Content-Transfer-Encoding: 7bit
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

I think this is a very interesting document.

In fact, we have been working in something similar for some time, but still not drafted it.

Our case is a very good example, because we are working in a project (www.6power.org) that deploys IPv6 PLC networks. In our case,
we may have different network configurations, with routers, bridges (PLC repeaters) and CPEs.

The idea is to configure the OSS system, in some cases in a static way (with the subscriber parameters), some others automatically
(but keeping the security to avoid non registered users to use the service).

At this way, when the different devices are plugged into the power network, there is no need to do ANY configuration at the devices,
as they will learn (or "create") an adequate network structure, all the way, until the CPE (that can be also a router, of course).

The idea is to extend the auto-configuration capabilities for IPv6 to the complete network. Today we do an autoconfiguration at the
PLC level already. This could provide one very good reason to deploy IPv6, specially in new networks, as will save a lot of
resources in the setup and operation/maintenance.

I think is a very good example of the utility of this document, and for sure we will be interested in cooperate on it, and most
probably work on concrete implementations.

Regards,
Jordi

----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <IETF-Announce:>
Cc: <ipv6@ietf.org>
Sent: Thursday, October 23, 2003 11:32 PM
Subject: I-D ACTION:draft-bykim-ipv6-hpd-00.txt


> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
> Title : Hierarchical Prefix Delegation Protocol
> Author(s) : B. Kim, K. Lee, J. Park, H. Kim
> Filename : draft-bykim-ipv6-hpd-00.txt
> Pages : 12
> Date : 2003-10-23
>
> Stateless Autoconfiguration enables IPv6 hosts to send a request for a prefix, a network identifier to a router on the subnet.
Using this  ability a host can configure its IPv6 address.  Likewise, by defining a way to request for a prefix to an upper level
router, a router can get a prefix to be assigned to its subnet.
>
> This document describes a protocol for prefix delegation between routers.  It allows routers get prefixes from its upstream
routers, enabling the entire network and its belonging hosts autoconfigure their own addresses.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-bykim-ipv6-hpd-00.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-bykim-ipv6-hpd-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv@ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-bykim-ipv6-hpd-00.txt".
>
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>

**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------