Re: [mif] Route option for DHCPv6 - next steps?
Lorenzo Colitti <lorenzo@google.com> Tue, 10 April 2012 03:23 UTC
Return-Path: <lorenzo@google.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 2AFF621F854F for <mif@ietfa.amsl.com>; Mon, 9 Apr 2012 20:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 5d3Ghm0afwfm for <mif@ietfa.amsl.com>; Mon, 9 Apr 2012 20:23:01 -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 5858C21F854E for <mif@ietf.org>; Mon, 9 Apr 2012 20:23:01 -0700 (PDT)
Received: by iazz13 with SMTP id z13so8131429iaz.31 for <mif@ietf.org>; Mon, 09 Apr 2012 20:23:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=AhRedeiXg+ShA1yBGfB3iy95jZrtltUnoKpuZpmLdso=; b=kPSBvRdlLu1o07k1SpJB4M03E787Dw9B1R8knQHWAPpgMjd2BX2IU2JdQaAs0eQdjs saZo9xZUTOBjrWQlwBxTE9llj8ZLCrF8RDKbjRlCIkOae2uYW1F6Od1wOpFNHO+uzzTI 2C8stS/khbipColg43tqZkA8z1g6MzdAsPkWr24Q41iIE6qu7HE4pmbh0gOqx5bj+9Ss KOiK3g6BCv9ZM7ZF4vNlVPSTa9Imx5wdHuIAlYXIwOg7YGDHJeEyGyCuDNtae7zfDKCJ ogVinA+R7HETnFAJrwawg5rpnRom4s+Z9kyxDN3nyExRxqL9QDsmLePtrsWSvGgfJK0b 2xpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=AhRedeiXg+ShA1yBGfB3iy95jZrtltUnoKpuZpmLdso=; b=CWVD/8+F2z2oykJ+62BPwyXkwkM1S1RpG6cxVHIs+V/n93JhJpAe0IgC0ty/dAibV6 KMP4CqkRncZBQ8yAfUCykcmm8v00/bPmU9E7i3bSKYqFs5eYFFFcA2Yk4NH+SmWJRwqT iNTdyvuJbk2eV9ZDl66om5Vdz2UMResqR4qDl8Qgen5R4A7oxS0h0fTKf5cOp/a3x8se yiALr7WBXuktA0Fu0aXTES2TOE/0agvvoymirXfyVXRwV/ESQPxQEnxTU8wrIbSLmQ5L 5UhfM14xRaH0DfaNoGgb8qH0K6PPtEF8kC7RLBbNhBSfWavcXu27Zc0RIpUfN82zLTef NF8g==
Received: by 10.50.155.168 with SMTP id vx8mr924687igb.11.1334028181043; Mon, 09 Apr 2012 20:23:01 -0700 (PDT)
Received: by 10.50.155.168 with SMTP id vx8mr924675igb.11.1334028180757; Mon, 09 Apr 2012 20:23:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.187.169 with HTTP; Mon, 9 Apr 2012 20:22:40 -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>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 10 Apr 2012 12:22:40 +0900
Message-ID: <CAKD1Yr3dEL_NB9MZyX_aj_B-m+9jO9yNzrmqV0UtkbdtLUHaEg@mail.gmail.com>
To: jouni korhonen <jouni.nospam@gmail.com>
Content-Type: multipart/alternative; boundary="e89a8f2349c1d59e6704bd4aa3ac"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQn5nbmHDEUfTdEodrdsSYWlnd41+1+Ga1nkSECJOZF+m0uRn+YbsFlqzapV1dEpuGxabLSXmeuvQBq3ixs79SYQh/5udM0F/OY/f1o3ak6SpAV3oi9nivxTPYVUzBiz1JEP1l8v
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
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, 10 Apr 2012 03:23:02 -0000
On Fri, Apr 6, 2012 at 05:27, 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. > That seems like it would meet the desired use case, right? > Assuming unicast RA would be doable using just RFC6085, then there should > not be much, if anything, to do protocol wise. You mean the text that allows "mapping of an IPv6 packet with a multicast destination address into an Ethernet link-layer unicast address, when it is clear that only one address is relevant"? So, in effect, the router would say that "this RA is only relevant to one host, so I'm going to unicast it to that one host"?
- 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