Re: [mif] Route option for DHCPv6 - next steps?
Maglione Roberta <roberta.maglione@telecomitalia.it> Tue, 24 April 2012 07:06 UTC
Return-Path: <roberta.maglione@telecomitalia.it>
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 F3CF211E808D for <mif@ietfa.amsl.com>; Tue, 24 Apr 2012 00:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.719
X-Spam-Level:
X-Spam-Status: No, score=-1.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1]
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 pY6eSs1diSqK for <mif@ietfa.amsl.com>; Tue, 24 Apr 2012 00:06:41 -0700 (PDT)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id F0B5921F8551 for <mif@ietf.org>; Tue, 24 Apr 2012 00:06:40 -0700 (PDT)
Received: from GRFHUB702BA020.griffon.local (10.188.101.112) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.3.245.1; Tue, 24 Apr 2012 09:06:31 +0200
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by GRFHUB702BA020.griffon.local ([10.188.101.112]) with mapi; Tue, 24 Apr 2012 09:06:31 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Ted Lemon' <Ted.Lemon@nominum.com>, Arifumi Matsumoto <arifumi@nttv6.net>
Date: Tue, 24 Apr 2012 09:06:31 +0200
Thread-Topic: [mif] Route option for DHCPv6 - next steps?
Thread-Index: AQHNDL2jhfr6t6vyVEeGR+93z5NinJZ/3M2AgAG+LoD//4t2bYAAgpgAgAAAh4CAABcYAP//i0r4gAC0mQD//8qt3gAjg1aA//+udoeAB9F/gIACyb4AgAeCygCAAWAsAIAC8VsAgARAqQCAC32NgIAARPoAgABWhvA=
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE51370AD04A@GRFMBX704BA020.griffon.local>
References: <75459BC2-E733-45C0-BC1C-25A19BBA1137@gmail.com> <CAE97176.17DF4%wdec@cisco.com> <CANF0JMD_zfXGcfMy+rCOFXS1aCZ3RPHoRtkBeS8kDgOFcfQ8Fg@mail.gmail.com> <75D251D1-9828-4AFE-9BEF-B376E97133C7@nominum.com> <CANF0JMBbhrF0G=hSvcvyZAddAMW7oSO5KpzUmcJXCtwcnmyWOw@mail.gmail.com> <4A221CE5-ECF0-4E07-9329-E6BAA3F06A96@nominum.com> <4EC4AADB.8030803@piuha.net> <DD1241D5-B794-49C3-A3A2-4294248DDD10@gmail.com> <4F719186.3060507@gmail.com> <CAKD1Yr3tSoDPcheriWdZEeKyhqpDANCP7Co0wVVqK5+mXc7e5A@mail.gmail.com> <4F72CD22.3080604@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>
In-Reply-To: <765F32AC-FBE3-4E8B-B698-1955C5601C2B@nominum.com>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, it-IT
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:06:42 -0000
> 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. Best regards, Roberta -----Original Message----- From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of Ted Lemon Sent: lunedì 23 aprile 2012 15.38 To: Arifumi Matsumoto Cc: MIF List Mailing Subject: Re: [mif] Route option for DHCPv6 - next steps? On Apr 23, 2012, at 5:31 AM, Arifumi Matsumoto <arifumi@nttv6.net> wrote: > I said, "From the access network provider perspective". > It is the cost they have to pay that matters to them. 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. > AFAIK, only Windows Vista and above supports RFC 4191 by default, though. This is not a good argument. Windows Vista is ancient. We can't define IPv6 in terms of the functionality present in Windows XP. _______________________________________________ mif mailing list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Tomek Mrugalski
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Margaret Wasserman
- Re: [mif] Route option for DHCPv6 - next steps? Margaret Wasserman
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Tony Hain
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Margaret Wasserman
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] use cases - Router instead of Host (was… Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Tony Hain
- Re: [mif] Route option for DHCPv6 - next steps? Tony Hain
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Tony Hain
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Tony Hain
- Re: [mif] Route option for DHCPv6 - next steps? Erik Kline
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Erik Kline
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Tony Hain
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Brian E Carpenter
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Brian E Carpenter
- Re: [mif] Route option for DHCPv6 - next steps? jouni korhonen
- Re: [mif] Route option for DHCPv6 - next steps? Behcet Sarikaya
- Re: [mif] Route option for DHCPv6 - next steps? Sri Gundavelli
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Wojciech Dec
- Re: [mif] Route option for DHCPv6 - next steps? Tao Sun
- Re: [mif] Route option for DHCPv6 - next steps? Arifumi Matsumoto
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Arifumi Matsumoto
- Re: [mif] Route option for DHCPv6 - next steps? Ted Lemon
- Re: [mif] Route option for DHCPv6 - next steps? Maglione Roberta
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Brian E Carpenter
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Maglione Roberta
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? jouni korhonen
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Alexandru Petrescu
- Re: [mif] Route option for DHCPv6 - next steps? Lorenzo Colitti
- Re: [mif] Route option for DHCPv6 - next steps? Behcet Sarikaya