IETF Logo Mail Archive

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

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 05 April 2012 20:46 UTC

Return-Path: <sarikaya2012@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 E993A21F85CF for <mif@ietfa.amsl.com>; Thu, 5 Apr 2012 13:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 YHfQv3yD-uM9 for <mif@ietfa.amsl.com>; Thu, 5 Apr 2012 13:46:56 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8D521F85C3 for <mif@ietf.org>; Thu, 5 Apr 2012 13:46:56 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2705940iaz.31 for <mif@ietf.org>; Thu, 05 Apr 2012 13:46:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=wiv9/9MsLieAqRal53Y2S6Uzxy7pABk6hYE7STOacEg=; b=kRPHEdPfp2j0/fqDSeQNubUMZu72+gCApXEpIS2L/Ns4pp+fgxOvI1P7XJUCFzXqOC 9yc/T7ovYhbxTM/3MCdysmrsNBiS5gVo+eyFu+HXLyOSu6QXtHko9r6TyBpRA6ttT6tV Ea+r3Sg5yxsEE4MR3S7DdulIUtFm8qxGREczXGgFuDi96e248uOZpkgHT1D3QkE+FX63 q+3j3FPL5iSxStDQnEAW8UgRv9AhUJnuNdA1xvMe7ov2XdvT+meB7GvKBn3LyaUMTNYK ZuXCM+EwRlxEqyj52kYrfsPw/R+srMF9a7w9b9mWPvMzFdwLlCXPax1RMJW1MKPioNJk lI+g==
MIME-Version: 1.0
Received: by 10.43.52.74 with SMTP id vl10mr2661500icb.55.1333658811371; Thu, 05 Apr 2012 13:46:51 -0700 (PDT)
Received: by 10.231.141.146 with HTTP; Thu, 5 Apr 2012 13:46:50 -0700 (PDT)
In-Reply-To: <97D4F82A-6321-403F-9097-F7B48601DCD5@gmail.com>
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> <CAAedzxpMtu_7jWuES5=EKK4oqsFsvt4tPpu0J4fy3Uz4-TEt6Q@mail.gmail.com> <97D4F82A-6321-403F-9097-F7B48601DCD5@gmail.com>
Date: Thu, 05 Apr 2012 15:46:50 -0500
Message-ID: <CAC8QAcf2qD02-OqahnYO72M1ntdt6O8NEmLpZpROY=q9G-Xcyg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: jouni korhonen <jouni.nospam@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "mif@ietf.org" <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
Reply-To: sarikaya@ieee.org
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: Thu, 05 Apr 2012 20:46:57 -0000

On Thu, Apr 5, 2012 at 3:27 PM, jouni korhonen <jouni.nospam@gmail.com> wrote:
>
> RADEXT is working on http://tools.ietf.org/html/draft-ietf-radext-ipv6-access-06
> which adds attributes for RFC4191 use, for example. That is then also implicitly
> available for Diameter.
>
> Assuming unicast RA would be doable using just RFC6085,

I don't understand what RFC 6085 has to do with this discussion?


> then there should not
> be much, if anything, to do protocol wise. The router that gets provisioned per
> host via AAA knows the l2-l3 mapping already.. and the AAA server also learns
> it. For dynamic changes of routes, AAA server can use e.g. l2 or l3 addresses
> for a session identification when it sends a change of authorization..
>
> The assumption here is that each host gets separately authorized when they attach
> the network, which might be an issue on some links & deployments. However, some
> network architectures with multiple routers/gateways (can) already use AAA for
> centralized address management at per host granularity.
>
> - Jouni
>
>
> On Apr 4, 2012, at 4:53 AM, Erik Kline wrote:
>
>>> It's true, as Jari said, that this can be accomplished in other ways, and maybe it would be better if it would.   If there were some better central management solution for populating unicast RA mappings on the router, then unicast RA would indeed address the exact use case that I think we care about.   But without the mechanism for populating routers, we still have a poorly-addressed use case.   And then the question is, do we want to develop a whole new protocol just to solve this one small problem?
>>>
>>> It might be worth developing the protocol just to put this issue to bed.
>>
>> Is RADIUS suitable for this?  At one point it was the general
>> non-client provisioning protocol of choice, I thought.  I have not
>> been following any of the evolving diameter work, but would a RADIUS
>> option suffice?
>> _______________________________________________
>> mif mailing list
>> mif@ietf.org
>> https://www.ietf.org/mailman/listinfo/mif
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

v2.23.0 | Report a Bug | By Email