[dhcwg] Comments on some aspects on draft-yeh-dhc-dhcpv6-prefix-pool-opt-08
Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 07 September 2012 12:44 UTC
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A48F21F8715 for <dhcwg@ietfa.amsl.com>; Fri, 7 Sep 2012 05:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZ5FRCrv7pBd for <dhcwg@ietfa.amsl.com>; Fri, 7 Sep 2012 05:44:55 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 3478F21F8734 for <dhcwg@ietf.org>; Fri, 7 Sep 2012 05:44:55 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id q87Cirbq008562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Fri, 7 Sep 2012 14:44:53 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id q87CirvI018816 for <dhcwg@ietf.org>; Fri, 7 Sep 2012 14:44:53 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id q87Cin3h015555 for <dhcwg@ietf.org>; Fri, 7 Sep 2012 14:44:53 +0200
Message-ID: <5049EC41.3080809@gmail.com>
Date: Fri, 07 Sep 2012 14:44:49 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Comments on some aspects on draft-yeh-dhc-dhcpv6-prefix-pool-opt-08
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 07 Sep 2012 12:44:56 -0000
DHC WG, Comments on some aspects on this draft. > When a routing protocol is enabled on the network-facing interface > of the PE router, all the routes directing to the customer networks > are advertised in the ISP network. This will make the number of > route entries in the routing table on the ISP router be unacceptable > large. Hence, it is desirable to aggregate the routes directing to > the customer networks on the PE router. In general, I can visualize the problem, and I believe more things about it: - it could be better described with an example and a topology which pictures many routes (like in 1, 2 ... n). This is just a comment, not necessarily should be done. (Graphs are already drawn which is good already in the draft.) - but if we do and draw pictures we may realize that the problem is exhibited in cases where the default route may not be given enough importance. For example, if the Relay has a single default route and is statically in charge of a short prefix (many subprefixes) then there is no problem of Relay advertising too many routes - only one. And of course, if it is not possible to have the Relay in charge of a single short prefix then ultimately one ends up with many specific routes advertised to the network and with the need to reduce them. One alternative solution may be to have a mechanism by which the Relay itself first executes Requesting Router (before being a Relay) to obtain that short prefix, at which point we no longer talk 'snooping'. This could be the Prefix Pool Option without snooping. Alex
- Re: [dhcwg] Comments on some aspects on draft-yeh… Leaf yeh
- [dhcwg] Comments on some aspects on draft-yeh-dhc… Alexandru Petrescu
- Re: [dhcwg] Comments on some aspects on draft-yeh… Ole Trøan
- Re: [dhcwg] Comments on some aspects on draft-yeh… JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK)