Re: [mif] New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt

Ted Lemon <Ted.Lemon@nominum.com> Sun, 21 October 2012 03:01 UTC

Return-Path: <Ted.Lemon@nominum.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 4579521F891D for <mif@ietfa.amsl.com>; Sat, 20 Oct 2012 20:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level:
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOrTym1t1z5s for <mif@ietfa.amsl.com>; Sat, 20 Oct 2012 20:01:09 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id A345D21F891B for <mif@ietf.org>; Sat, 20 Oct 2012 20:01:09 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUINldTQEuMz350Y2CGPLYC4EGJVFTZqI@postini.com; Sat, 20 Oct 2012 20:01:09 PDT
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 DB2D51B829A for <mif@ietf.org>; Sat, 20 Oct 2012 20:01:08 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D216D19005C; Sat, 20 Oct 2012 20:01:08 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Sat, 20 Oct 2012 20:01:08 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: [mif] New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt
Thread-Index: AQHNrS3iW6gFvmNkqUiZ8bkm+bpnwpfB+fWAgAATB4CAAXzwgIAAAbKA
Date: Sun, 21 Oct 2012 03:01:08 +0000
Message-ID: <CD611B92-16E5-4836-BF43-DEB9706155CD@nominum.com>
References: <913383AAA69FF945B8F946018B75898A1480EDFA@xmb-rcd-x10.cisco.com> <7E99AA25-66C2-4A4D-B251-0E71F31FBA26@nominum.com> <913383AAA69FF945B8F946018B75898A148124F2@xmb-rcd-x10.cisco.com> <09806E4D-E6BA-431A-9BB4-F59AD64885A7@nominum.com> <913383AAA69FF945B8F946018B75898A14812900@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A14812900@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C6C64991A7F19C438B6F9FED1BA64B7C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt
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: Sun, 21 Oct 2012 03:01:10 -0000

On Oct 20, 2012, at 10:55 PM, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> wrote:
> Yes. In such Managed Networks, SLAAC is disabled and IPv6 addresses are only assigned using DHCPv6 server. Switches in such environments provide First Hop Security by gleaning DHCP/NDP messages and can make sure hosts are using the IPv6 addresses assigned by the DHCPv6 server only (Source Guard). With the technique in this draft only certain hosts will be permitted assignment of IA_TA and not for other hosts. 

That makes sense—thanks for clarifying!