Re: Broadband Forum liaison to IETF on IPv6 security

Thomas Narten <narten@us.ibm.com> Fri, 06 November 2009 19:17 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8163D3A6966; Fri, 6 Nov 2009 11:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.033
X-Spam-Level:
X-Spam-Status: No, score=-4.033 tagged_above=-999 required=5 tests=[AWL=-1.433, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Go2YeYAY24y; Fri, 6 Nov 2009 11:17:38 -0800 (PST)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by core3.amsl.com (Postfix) with ESMTP id 9E18D3A6959; Fri, 6 Nov 2009 11:17:38 -0800 (PST)
Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by e7.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id nA6JEHwN030197; Fri, 6 Nov 2009 14:14:17 -0500
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id nA6JI1P0071058; Fri, 6 Nov 2009 14:18:01 -0500
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id nA6FE0I8031231; Fri, 6 Nov 2009 10:14:00 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-223-3.mts.ibm.com [9.65.223.3]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id nA6FDxSx031160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Nov 2009 10:14:00 -0500
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.3/8.12.5) with ESMTP id nA6JHwVf005230; Fri, 6 Nov 2009 14:17:59 -0500
Message-Id: <200911061917.nA6JHwVf005230@cichlid.raleigh.ibm.com>
To: "Stark, Barbara" <bs7652@att.com>
Subject: Re: Broadband Forum liaison to IETF on IPv6 security
In-reply-to: <7582BC68E4994F4ABF0BD4723975C3FA10C3768C@crexc41p>
References: <AFC1ACFB-FDFA-482C-AAF9-7995F5CEFE1F@broadband-forum.org><F311A255-3303-4C9D-B270-D1D23DE31E31@cisco.com><200911061358.nA6DwXNq025458@cichlid.raleigh.ibm.com> <B52C3C2B-924A-4454-B863-57B02F54E5D4@apple.com> <7582BC68E4994F4ABF0BD4723975C3FA10C3768C@crexc41p>
Comments: In-reply-to "Stark, Barbara" <bs7652@att.com> message dated "Fri, 06 Nov 2009 13:56:02 -0500."
Date: Fri, 06 Nov 2009 14:17:58 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: 6man-ads@tools.ietf.org, SAVI Mailing List <savi@ietf.org>, savi-ads@tools.ietf.org, v6ops-ads@tools.ietf.org, IPv6 Operations <v6ops@ops.ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2009 19:17:39 -0000

> The liaison was posted in March 2009. It can be found here:
> https://datatracker.ietf.org/documents/LIAISON/file621.doc

This is too skimpy of problem statement for me to understand the
details of the problem.

I don't know that a lot is needed. Maybe 2-3 pages is enough. But show
me a diagram, label the pieces, show me the properties of the pieces
and explain what the *exact* problem is. Who needs to do DAD? Why
doesn't it work? etc.

And note that comments like (quoting from the above statement):

  "We can envision a number of scenarios, both malice or vendor
   incompetence by which this can happen."

There is very little anyone can do to prevent "vendor
incompetence". I hope you aren't asking the IETF to solve this
problem! :-)

Thomas