IETF Logo Mail Archive

Re: [v6ops] New Version Notification for draft-yourtchenko-ra-dhcpv6-comparison-00.txt (fwd)

Ted Lemon <ted.lemon@nominum.com> Tue, 07 January 2014 04:11 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 135C01ADF7A for <v6ops@ietfa.amsl.com>; Mon, 6 Jan 2014 20:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8GDpViJ8cIT7 for <v6ops@ietfa.amsl.com>; Mon, 6 Jan 2014 20:11:42 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 13F541ADF72 for <v6ops@ietf.org>; Mon, 6 Jan 2014 20:11:42 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUst+dR1wzFCQ9N1wEpTTwsSZph0n7aV1@postini.com; Mon, 06 Jan 2014 20:11:33 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 721E01B82D6 for <v6ops@ietf.org>; Mon, 6 Jan 2014 20:11:33 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 53F9C19005C; Mon, 6 Jan 2014 20:11:33 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 6 Jan 2014 20:11:27 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAEmG1=qLxqWdB8JR4rbAS-TyqQtPcGnZvVb7DSBCrmFcrm0vUA@mail.gmail.com>
Date: Mon, 06 Jan 2014 23:11:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <50833006-C1DA-4F71-BFE4-C9E1F6F29076@nominum.com>
References: <alpine.OSX.2.00.1311271353550.3903@ayourtch-mac> <1386274786.29351.YahooMailNeo@web142501.mail.bf1.yahoo.com> <alpine.OSX.2.00.1312060759220.68814@ayourtch-mac> <1386378082.99914.YahooMailNeo@web161901.mail.bf1.yahoo.com> <alpine.OSX.2.00.1312072028290.68814@ayourtch-mac> <F024FF5B-35A6-4221-952C-4A730A68C59D@delong.com> <alpine.OSX.2.00.1312080643090.68814@ayourtch-mac> <B561C767-677A-4A37-BA69-EB24951B2817@delong.com> <52A4C6FD.1080504@gmail.com> <98CACA9B-AD61-460A-93AC-D5EEA1176706@delong.com> <CAEmG1=qLxqWdB8JR4rbAS-TyqQtPcGnZvVb7DSBCrmFcrm0vUA@mail.gmail.com>
To: Matthew Petach <mpetach@netflight.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] New Version Notification for draft-yourtchenko-ra-dhcpv6-comparison-00.txt (fwd)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 04:11:44 -0000

On Jan 6, 2014, at 10:10 PM, Matthew Petach <mpetach@netflight.com> wrote:
> There are multi-billion dollar companies that have a need
> to operate their networks in very specific ways. 

If you set your routers to send RAs with the M bit set and the A bit set on any prefixes that are advertised, then devices will not autoconfigure using SLAAC (or at least, they shouldn't).   That delivers to you the exact functionality you say you want.   What change are you arguing for in addition to this?

v2.23.0 | Report a Bug | By Email