Re: [mif] Route option for DHCPv6 - next steps?
Lorenzo Colitti <lorenzo@google.com> Wed, 25 April 2012 09:03 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 B2EC721F874F for <mif@ietfa.amsl.com>; Wed, 25 Apr 2012 02:03:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.912
X-Spam-Level:
X-Spam-Status: No, score=-102.912 tagged_above=-999 required=5 tests=[AWL=0.064, 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 zOy6sYlptl6Z for <mif@ietfa.amsl.com>; Wed, 25 Apr 2012 02:03:54 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA4821F8742 for <mif@ietf.org>; Wed, 25 Apr 2012 02:03:53 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so2528910obb.31 for <mif@ietf.org>; Wed, 25 Apr 2012 02:03:52 -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=JRTTk6v43uhlxh/Y6MK0NrKOXrCaWH+fnwmgufNlY/o=; b=Q5P6yIUOnPq0X7qKePgCiQ6lvVqM8t84QmP/uBhXgh/bSP3v0L4ZQ2OfI6bfaNj3HW oQZTi/66Lv4RL7gjik4n1RwHbRrxI1tR9oDQzEIOfkScLA+cq46hCMUYyvNatE2Mp+2O VreBG94x/myrvhcC6C4NmxeHsKWxYEO87Y9ek2D6qMIvd01dCNgKRnskzw4Dgu9TBDXa VRDLFOeIxiR4s2cfkJYSqTQcdIx5TSIuEUDVCRCCsLhri8evpE+WBJij1KEu+9MZwxO9 uLN3bW0SFObmYGfVEH6T7u3EPnPMt6+5p595GbakVXFbS1fmjzucwOcG6ktogBrf9Nwf nMzg==
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=JRTTk6v43uhlxh/Y6MK0NrKOXrCaWH+fnwmgufNlY/o=; b=eeBb8CEyG+0lPK9m/1q+joAXX792UzkD8qB/CiSzhj+C66Ek4X7E70RqFR3xXfz8d1 SaV10CacF8lo24gqAYBeP0Qt0ZKBRmYND4Slf5rijcrDbRg7CqpD2ErLE7vo4NZwYfFv qku4f4pY5/qIJxI2kJYTW47oC0Ev2nYSqx0VOxXaRzDwh8QtFkv3rpOQoO7y839lKbB+ WrKNuOvHWYj0CdsQaKqCdP44VDykZPwN9MNoT2QKJBuY0w1X7SWWFAS3w6PI+knoj/Z1 f2V6om3zIiv6IZTsSxIlD9wkU7WByrlqDQdbY4552gHiQMwgCe2s7y5kL4OrQlpmHSbw 5COQ==
Received: by 10.182.113.42 with SMTP id iv10mr2416430obb.18.1335344632878; Wed, 25 Apr 2012 02:03:52 -0700 (PDT)
Received: by 10.182.113.42 with SMTP id iv10mr2416423obb.18.1335344632730; Wed, 25 Apr 2012 02:03:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.220.3 with HTTP; Wed, 25 Apr 2012 02:03:31 -0700 (PDT)
In-Reply-To: <4F969A70.5090506@gmail.com>
References: <75459BC2-E733-45C0-BC1C-25A19BBA1137@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> <4F96550E.6020709@gmail.com> <CAKD1Yr0d4ez4dogDk1gRvUHvWpoTBEg_4HatQQoa5oa3Yu9NFw@mail.gmail.com> <4F965BD2.1080906@gmail.com> <CAKD1Yr1=ry45uw=Xy1Gf5t30oC=ugzMGpwz7kbwctgXvg83WLw@mail.gmail.com> <4F969A70.5090506@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 25 Apr 2012 18:03:31 +0900
Message-ID: <CAKD1Yr20RCw36rW7VOJRqWA__LuBytF40zr0-cecvpafkJUk=w@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary="f46d04479f977c95a904be7d2600"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQlGGb83RDE5amMU1KIwJt9bjfcCbwrlxaUVL4FFsZo16NoVdDDVNc7vZgWe+VrsJhimJNMP/WLdOodNBontFLbuI2JsJOYggytP/J9jnI51aWk8Nlgmj5M4Mwr2Ya8tVpZ5a+G+
Cc: 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: Wed, 25 Apr 2012 09:03:55 -0000
On Tue, Apr 24, 2012 at 21:20, Alexandru Petrescu < alexandru.petrescu@gmail.com> wrote: > W-1: When the router is attached to the WAN interface link, it MUST >> act as an IPv6 host for the purposes of stateless [RFC4862] or >> stateful [RFC3315] interface address assignment. >> > > That is not enough for specific routes. Ok it covers the default routes, > but not specific routes such as rfc4191. Sure. But RFC 6204 also doesn't say "must implement a DHCPv6 route option". So if you want to ensure that the CE router can configure more-specific routes, you have to modify RFC 6204 either way. In one case, you need to modify it to say "must implement a DHCPv6 route option". In the other, you need to modify it to say "must implement RFC 4191". Note that the RFC already says that "nodes that will be deployed in SOHO environments SHOULD implement RFC 4191", so RFC 4191 is likely already implemented.
- 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