Re: [mif] Route option for DHCPv6 - next steps?

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 24 April 2012 07:22 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 861B221F85A3 for <mif@ietfa.amsl.com>; Tue, 24 Apr 2012 00:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.57
X-Spam-Level:
X-Spam-Status: No, score=-101.57 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUrtAA7RT01o for <mif@ietfa.amsl.com>; Tue, 24 Apr 2012 00:22:53 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id D6AB021F85A1 for <mif@ietf.org>; Tue, 24 Apr 2012 00:22:52 -0700 (PDT)
Received: by eeke51 with SMTP id e51so69583eek.31 for <mif@ietf.org>; Tue, 24 Apr 2012 00:22:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pDm+3BQlG1OrOdwLdb7362SZ1TuZYoOZqtOQlN/LaFA=; b=yJj0YPWM7YawS4TtrvU4kxfXljRnu1iux1fhd46HUckEePXdFksDlsWwaIeZNZZ98W cTFEKkJwwCOB5R5jBtzqsmInrvtOyXhkWY0kHpDliQRQLNR/R7Sd2vp4s9/4eHiinx1I USpUCQD8g6Tl/LSO82OzUizgr1i01IFxwHvJaZJHkchQCdvK14LrU1unuh5TUvi84DBM +zbjPkHIM7+Ks4jXCrLzTXEZ0WDgD25YIuVQAykKdZDZrBV6W+c99ACkLFGhHAn0BXO3 /hXLzVfacw7kBANxrWeKQ4myo2sUDQ3xWuYC7XKrf4SUtMHH5/mSrcYl1Ip31cpYal8X GE7A==
Received: by 10.14.127.5 with SMTP id c5mr3118302eei.120.1335252171977; Tue, 24 Apr 2012 00:22:51 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-216-233.as13285.net. [2.102.216.233]) by mx.google.com with ESMTPS id m55sm83266895eei.1.2012.04.24.00.22.49 (version=SSLv3 cipher=OTHER); Tue, 24 Apr 2012 00:22:51 -0700 (PDT)
Message-ID: <4F9654C7.3010305@gmail.com>
Date: Tue, 24 Apr 2012 08:22:47 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
References: <75459BC2-E733-45C0-BC1C-25A19BBA1137@gmail.com> <CAKD1Yr3RUUthiawKrmxjSNqzEbJcOLpHvDGb9XLtdiU-tfEYyw@mail.gmail.com> <4F744831.3070406@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307472D4175@mbx-01.win.nominum.com> <4F7453FC.3010502@gmail.com> <4F74546D.4060808@gmail.com> <72C42575-6BE2-4F27-B7F4-AA4539DA7EF9@lilacglade.org> <8D23D4052ABE7A4490E77B1A012B6307472D43A1@mbx-01.win.nominum.com> <069301cd0dd2$5954df00$0bfe9d00$@tndh.net> <550B9F79-1642-469F-9ED3-96DA26AA40AB@lilacglade.org> <97D4F82A-63! 21-403F-9097-F7B48601DCD5@gmail.com> <CAFFjW4hkGMm+mLSzpdWPcFLUcY3Hkyb+BDxh+5910YtfZxGD-A@mail.gmail.com> <CA+H2C9Zu3AS6aTxg1gebe0ZS2LXWmJjOPpbhaUHGZtXvF0UipQ@mail.gmail.com> <17F90720-AA1F-4F74-9598-2E5A5AC813CE@nttv6.net> <CAKD1Yr1s7SARfnowZV1uU=dDPi46-OjRQnM4otKsW3Y-k+84cw@mail.gmail.com> <F4D68CC2-27C5-4FB1-A11F-026E5261DB77@nttv6.net> <765F32AC-FBE3-4E8B-B698-1955C5601C2B@nominum.com> <282BBE8A501E1F4DA9C775F964BB21FE51370AD04A@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE51370AD04A@GRFMBX704BA020.griffon.local>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: MIF List Mailing <mif@ietf.org>
Subject: Re: [mif] Route option for DHCPv6 - next steps?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 07:22:53 -0000

On 2012-04-24 08:06, Maglione Roberta wrote:
>> It would help to complete this argument if you unpacked the details here.   > Why is RA so much more expensive than DHCP in this case?   I get the sense > that this is obvious to the people who are promoting various DHCP route
>> options, but it clearly isn't obvious to people who aren't network
>> operators, so more detail is needed.
> 
> Because in order to be able to use RA's you would need to somehow provision each single BNG (the router that is supposed to send the RA) with the route information to be sent into RA's for all the subscribers and if, for any reason, you need to move a subscriber from one BNG to another you would need to re-provision the same information on the other BNG.
> 
> While with DHCPv6 you can have a single centralized provision point and no additional configuration required on the BNG.  This is an operational difference for an operator.

Unfortunately, people with zero experience of running a reasonably large
network seem unable to understand this elementary point.

This is much bigger than a MIF issue.

   Brian