IETF Logo Mail Archive

RE: Fwd: Broadband Forum liaison to IETF on IPv6 security

"Hemant Singh (shemant)" <shemant@cisco.com> Mon, 09 November 2009 01:05 UTC

Return-Path: <shemant@cisco.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 3A1703A6898 for <ipv6@core3.amsl.com>; Sun, 8 Nov 2009 17:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.855
X-Spam-Level:
X-Spam-Status: No, score=-5.855 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 H81ANHn5dC7q for <ipv6@core3.amsl.com>; Sun, 8 Nov 2009 17:05:18 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id EA3EF3A686D for <ipv6@ietf.org>; Sun, 8 Nov 2009 17:05:17 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEAE/59kqtJV2Y/2dsb2JhbACEcZVEqGyHFYIUCY0CgTKBIoEWVASBaA
X-IronPort-AV: E=Sophos;i="4.44,705,1249257600"; d="scan'208";a="67000240"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-2.cisco.com with ESMTP; 09 Nov 2009 01:05:42 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id nA915gKk027145; Mon, 9 Nov 2009 01:05:42 GMT
Received: from xmb-rcd-114.cisco.com ([72.163.62.156]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 8 Nov 2009 19:05:42 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Subject: RE: Fwd: Broadband Forum liaison to IETF on IPv6 security
Date: Sun, 08 Nov 2009 19:05:40 -0600
Message-ID: <AF742F21C1FCEE4DAB7F4842ABDC511C11DDA4@XMB-RCD-114.cisco.com>
In-Reply-To: <AF742F21C1FCEE4DAB7F4842ABDC511C11DD08@XMB-RCD-114.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Fwd: Broadband Forum liaison to IETF on IPv6 security
Thread-Index: AcpfD9ATPsDVSCGmTqCpJYWjx52aqwABaHbAAAUHVrAAAurLsAACWa5AAACk0zAAAQdzgABkwmjg
References: <AFC1ACFB-FDFA-482C-AAF9-7995F5CEFE1F@broadband-forum.org><F311A255-3303-4C9D-B270-D1D23DE31E31@cisco.com><200911061358.nA6DwXNq025458@cichlid.raleigh.ibm.com><3C6F21684E7C954193E6C7C4573B76270367855A0E@IMCMBX1.MITRE.ORG><alpine.OSX.1.00.0911060823410.126@cust11794.lava.net><3C6F21684E7C954193E6C7C4573B76270367855B2F@IMCMBX1.MITRE.ORG><BB56240F3A190F469C52A57138047A03037B07E3@xmb-rtp-211.amer.cisco.com><3C6F21684E7C954193E6C7C4573B76270367855CA1@IMCMBX1.MITRE.ORG><AF742F21C1FCEE4DAB7F4842ABDC511C11DCF6@XMB-RCD-114.cisco.com><3C6F21684E7C954193E6C7C4573B76270367855CBC@IMCMBX1.MITRE.ORG> <AF742F21C1FCEE4DAB7F4842ABDC511C11DD08@XMB-RCD-114.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Dunn, Jeffrey H." <jdunn@mitre.org>, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, Antonio Querubin <tony@lava.net>
X-OriginalArrivalTime: 09 Nov 2009 01:05:42.0456 (UTC) FILETIME=[C26C4B80:01CA60D8]
X-Mailman-Approved-At: Mon, 09 Nov 2009 00:35:49 -0800
Cc: Thomas Narten <narten@us.ibm.com>, 6man-ads@tools.ietf.org, Mailing List <ipv6@ietf.org>, william.allen.simpson@gmail.com, Hesham Soliman <hesham@elevatemobile.com>, Erik Nordmark <erik.nordmark@sun.com>, Susan@core3.amsl.com, savi-ads@tools.ietf.org, IPv6 Operations <v6ops@ops.ietf.org>, "Susan Thomson (sethomso)" <sethomso@cisco.com>, "Fred Baker (fred)" <fred@cisco.com>, v6ops-ads@tools.ietf.org, IETF@core3.amsl.com, Robin Mersh <rmersh@broadband-forum.org>, JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
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: Mon, 09 Nov 2009 01:05:19 -0000

So have I and Wes been able to close the issue for the DSL Forum folks?  Implement ND Proxy at your first-hop IPv6 router/access concentrator.  

Thanks,

Hemant

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Hemant Singh (shemant)
Sent: Saturday, November 07, 2009 10:07 AM
To: Dunn, Jeffrey H.; Wes Beebee (wbeebee); Antonio Querubin
Cc: Thomas Narten; 6man-ads@tools.ietf.org; SAVI Mailing List; william.allen.simpson@gmail.com; Hesham Soliman; Erik Nordmark; Susan@core3.amsl.com; savi-ads@tools.ietf.org; Robin Mersh; Susan Thomson (sethomso); Fred Baker (fred); v6ops-ads@tools.ietf.org; IETF@core3.amsl.com; IPv6 Operations; Mailing List; JINMEI Tatuya / 神明達哉
Subject: RE: Fwd: Broadband Forum liaison to IETF on IPv6 security

Jeffrey,

The answer to your question is a yes.  Alternatively, the ISP may just dole out a delegated prefix shorter than a /64 and the CPE Rtr has to live with it but the ISP may use something like a /55 that gives sufficient number of links in the home LAN.  I will reply to any more discussion on this thread once I reach Hiroshima. 

Hemant

-----Original Message-----
From: Dunn, Jeffrey H. [mailto:jdunn@mitre.org] 
Sent: Friday, November 06, 2009 7:31 PM
To: Hemant Singh (shemant); Wes Beebee (wbeebee); Antonio Querubin
Cc: Thomas Narten; Fred Baker (fred); 6man-ads@tools.ietf.org; SAVI Mailing List; william.allen.simpson@gmail.com; Hesham Soliman; IETF@core3.amsl.com; Erik Nordmark; savi-ads@tools.ietf.org; IPv6 Operations; Susan Thomson (sethomso); v6ops-ads@tools.ietf.org; Robin Mersh; Mailing List; Susan@core3.amsl.com; JINMEI Tatuya / 神明達哉; Dunn, Jeffrey H.
Subject: RE: Fwd: Broadband Forum liaison to IETF on IPv6 security

OK. Then the CPE router has a unique /64 for all of its broadcast domains? Does that mean that the customer needs to tell the ISP how many /64 prefixes they need?

Best Regards, 
  
Jeffrey Dunn 
Info Systems Eng., Lead 
MITRE Corporation.
(301) 448-6965 (mobile)


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email