Re: [dhcwg] Kathleen Moriarty's No Objection on draft-ietf-dhc-dynamic-shared-v4allocation-07: (with COMMENT)

Ted Lemon <Ted.Lemon@nominum.com> Thu, 28 May 2015 03:12 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCC21A1A70; Wed, 27 May 2015 20:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 3UiNhaK5NluK; Wed, 27 May 2015 20:12:01 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B47031A1A6D; Wed, 27 May 2015 20:12:01 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 7771ADA0085; Thu, 28 May 2015 03:12:01 +0000 (UTC)
Received: from [10.0.20.121] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 27 May 2015 20:11:55 -0700
References: <20150527233931.6042.26234.idtracker@ietfa.amsl.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <20150527233931.6042.26234.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <0250B544-8B63-4859-9AD5-2EB815FB81A7@nominum.com>
X-Mailer: iPad Mail (12F69)
From: Ted Lemon <Ted.Lemon@nominum.com>
Date: Wed, 27 May 2015 23:11:54 -0400
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/aLrviknBrnmeszFlQBPfUWouLY8>
Cc: "<draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org>" <draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org>, "<volz@cisco.com>" <volz@cisco.com>, "<dhc-chairs@ietf.org>" <dhc-chairs@ietf.org>, "<draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org>" <draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org>, The IESG <iesg@ietf.org>, "<dhcwg@ietf.org>" <dhcwg@ietf.org>, "<draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org>" <draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org>
Subject: Re: [dhcwg] Kathleen Moriarty's No Objection on draft-ietf-dhc-dynamic-shared-v4allocation-07: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2015 03:12:03 -0000

On May 27, 2015, at 7:39 PM, Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com> wrote:
> I have many of the same questions as Stephen, so I support his discuss
> and comments.  In particular, I'd like to see text int he security
> considerations about sending traffic to the wrong host and how that is
> prevented as well as risks.  Stephen hits on this in his comments and I'd
> like to see it addressed in the security considerations section.  Since
> that's the point of the draft (multiple hosts using the same IPs), it is
> a major consideration.

If you are concerned about this, the time to have objected would have been when A+P got standardized a few months ago. There is no way to address that concern in this document, which is just about configuring A+P clients. FWIW it was talked about and, I think, addressed adequately in the base specifications.