IETF Logo Mail Archive

Re: Broadband Forum liaison to IETF on IPv6 security

james woodyatt <jhw@apple.com> Fri, 06 November 2009 18:22 UTC

Return-Path: <jhw@apple.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 47E933A69D6; Fri, 6 Nov 2009 10:22:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.547
X-Spam-Level:
X-Spam-Status: No, score=-106.547 tagged_above=-999 required=5 tests=[AWL=2.052, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lkgt7GJ+fFcZ; Fri, 6 Nov 2009 10:22:42 -0800 (PST)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 8C62F3A6998; Fri, 6 Nov 2009 10:22:42 -0800 (PST)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 5D85D78AEE24; Fri, 6 Nov 2009 10:23:06 -0800 (PST)
X-AuditID: 11807137-b7bd4ae000000f0d-c7-4af46989289d
Received: from [17.116.221.39] (Unknown_Domain [17.116.221.39]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 0A.C0.03853.A8964FA4; Fri, 6 Nov 2009 10:23:06 -0800 (PST)
Subject: Re: Broadband Forum liaison to IETF on IPv6 security
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
From: james woodyatt <jhw@apple.com>
In-Reply-To: <200911061358.nA6DwXNq025458@cichlid.raleigh.ibm.com>
Date: Fri, 06 Nov 2009 10:23:05 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <B52C3C2B-924A-4454-B863-57B02F54E5D4@apple.com>
References: <AFC1ACFB-FDFA-482C-AAF9-7995F5CEFE1F@broadband-forum.org> <F311A255-3303-4C9D-B270-D1D23DE31E31@cisco.com> <200911061358.nA6DwXNq025458@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1076)
X-Brightmail-Tracker: AAAAAQAAAZE=
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 18:22:43 -0000

On Nov 6, 2009, at 05:58, Thomas Narten wrote:

> Is there a problem statement somewhere that describes the actual  
> problem for which a solution is needed?
> Has this been put into an ID, for instance?
> I haven't been able to get my head around the actual problem from  
> the (few) emails I've seen.

The letter from the Broadband Forum Technical Chair in the message  
that originated this thread mentions an attachment that includes a  
revised Problem Statement on Duplicate Link Local Addresses, but it  
wasn't forwarded with the letter.

I'd like to read that problem statement.  Where is it?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering

v2.23.0 | Report a Bug | By Email