IETF Logo Mail Archive

Re: [OPSEC] Ted Lemon's Discuss on draft-ietf-opsec-dhcpv6-shield-05: (with DISCUSS and COMMENT)

Ted Lemon <Ted.Lemon@nominum.com> Sat, 07 February 2015 19:48 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C451A19F7; Sat, 7 Feb 2015 11:48:16 -0800 (PST)
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 WU32iIePfir8; Sat, 7 Feb 2015 11:48:14 -0800 (PST)
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 F00E61A0AF1; Sat, 7 Feb 2015 11:48:01 -0800 (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 Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id BC897DA00EF; Sat, 7 Feb 2015 19:48:01 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6C02653E08A; Sat, 7 Feb 2015 11:48:01 -0800 (PST)
Received: from [192.168.1.4] (70.196.212.73) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sat, 7 Feb 2015 11:48:01 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <20150207194616.20651.30892.idtracker@ietfa.amsl.com>
Date: Sat, 07 Feb 2015 12:47:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <EF7F96C3-8FDA-4522-94DF-5DA97F4C75BC@nominum.com>
References: <20150207194616.20651.30892.idtracker@ietfa.amsl.com>
To: The IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [70.196.212.73]
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsec/XwagCItmBaxM0Gv5UZOXzVeqioc>
Cc: draft-ietf-opsec-dhcpv6-shield@ietf.org, opsec@ietf.org, draft-ietf-opsec-dhcpv6-shield.ad@ietf.org, draft-ietf-opsec-dhcpv6-shield.shepherd@ietf.org, opsec-chairs@ietf.org, brian.e.carpenter@gmail.com
Subject: Re: [OPSEC] Ted Lemon's Discuss on draft-ietf-opsec-dhcpv6-shield-05: (with DISCUSS and COMMENT)
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec/>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Feb 2015 19:48:16 -0000

On Feb 7, 2015, at 12:46 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> The reason for this is that we can safely assume that any IP extension
> header that appears in a packet conforms to RFC 6564. 

What I mean here is that any IP extension header not already standardized at the time of publication of this document, which presumably any implementation conforming to this document will be aware of.   Of course there are IP extension headers already defined that do not conform to RFC 6564.

v2.23.0 | Report a Bug | By Email