IETF Logo Mail Archive

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

Maglione Roberta <roberta.maglione@telecomitalia.it> Tue, 24 April 2012 07:29 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 8839521F85D4 for <mif@ietfa.amsl.com>; Tue, 24 Apr 2012 00:29: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=[AWL=-0.001, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, 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 7L9755K2w-TP for <mif@ietfa.amsl.com>; Tue, 24 Apr 2012 00:29:41 -0700 (PDT)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF7921F85D8 for <mif@ietf.org>; Tue, 24 Apr 2012 00:29:40 -0700 (PDT)
Content-Type: multipart/mixed; boundary="_1cc6e115-433b-48cb-bd60-d8ac57a00c91_"
Received: from GRFHUB703BA020.griffon.local (10.188.101.113) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.3.245.1; Tue, 24 Apr 2012 09:29:38 +0200
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by GRFHUB703BA020.griffon.local ([10.188.101.113]) with mapi; Tue, 24 Apr 2012 09:29:38 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Lorenzo Colitti' <lorenzo@google.com>
Date: Tue, 24 Apr 2012 09:29:38 +0200
Thread-Topic: [mif] Route option for DHCPv6 - next steps?
Thread-Index: Ac0h6oH5P/QJOAj4TVy3443lQtw9UAAARd2w
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE51370AD04C@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> <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> <CAKD1Yr3UqnSaxdLYuQGAaAmdKH1m3BKbW=h=epWK_V4=+V2qUw@mail.gmail.com>
In-Reply-To: <CAKD1Yr3UqnSaxdLYuQGAaAmdKH1m3BKbW=h=epWK_V4=+V2qUw@mail.gmail.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
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:29:41 -0000

> Right. That's why RADIUS was mentioned earlier in this thread.

and it was already clarified in this thread that RADIUS cannot be applicable in all scenarios.
http://www.ietf.org/mail-archive/web/mif/current/msg01757.html

Roberta

________________________________
From: Lorenzo Colitti [mailto:lorenzo@google.com]
Sent: martedì 24 aprile 2012 9.18
To: Maglione Roberta
Cc: Ted Lemon; Arifumi Matsumoto; MIF List Mailing
Subject: Re: [mif] Route option for DHCPv6 - next steps?

On Tue, Apr 24, 2012 at 16:06, Maglione Roberta <roberta.maglione@telecomitalia.it<mailto:roberta.maglione@telecomitalia.it>> wrote:
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.

Right. That's why RADIUS was mentioned earlier in this thread.

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.

But you have to update all the clients.
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.

[cid:00000000000000000000000000000003@TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

v2.23.0 | Report a Bug | By Email