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

"Hemant Singh (shemant)" <shemant@cisco.com> Sat, 07 November 2009 00:23 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 C714228C133; Fri, 6 Nov 2009 16:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.667
X-Spam-Level:
X-Spam-Status: No, score=-5.667 tagged_above=-999 required=5 tests=[AWL=0.932, 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 sTDVLckV28+q; Fri, 6 Nov 2009 16:23:20 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 8B96228C12F; Fri, 6 Nov 2009 16:23:20 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEACpN9EqrR7Ht/2dsb2JhbACEcpU/qgeHEoIUCY5hgTKBIoEWVASBZw
X-IronPort-AV: E=Sophos;i="4.44,697,1249257600"; d="scan'208";a="426815182"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 07 Nov 2009 00:23:44 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id nA70Nhpq012954; Sat, 7 Nov 2009 00:23:44 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); Fri, 6 Nov 2009 18:23:43 -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: Fri, 06 Nov 2009 18:23:41 -0600
Message-ID: <AF742F21C1FCEE4DAB7F4842ABDC511C11DCF6@XMB-RCD-114.cisco.com>
In-Reply-To: <3C6F21684E7C954193E6C7C4573B76270367855CA1@IMCMBX1.MITRE.ORG>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Fwd: Broadband Forum liaison to IETF on IPv6 security
Thread-Index: AcpfD9ATPsDVSCGmTqCpJYWjx52aqwABaHbAAAUHVrAAAurLsAACWa5A
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>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dunn, Jeffrey H." <jdunn@mitre.org>, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, Antonio Querubin <tony@lava.net>
X-OriginalArrivalTime: 07 Nov 2009 00:23:43.0526 (UTC) FILETIME=[90329460:01CA5F40]
X-Mailman-Approved-At: Sat, 07 Nov 2009 04:57:51 -0800
Cc: Thomas Narten <narten@us.ibm.com>, 6man-ads@tools.ietf.org, SAVI Mailing List <savi@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, Robin Mersh <rmersh@broadband-forum.org>, "Susan Thomson (sethomso)" <sethomso@cisco.com>, "Fred Baker (fred)" <fred@cisco.com>, v6ops-ads@tools.ietf.org, IETF@core3.amsl.com, IPv6 Operations <v6ops@ops.ietf.org>, Mailing List <ipv6@ietf.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: Sat, 07 Nov 2009 00:23:21 -0000

This is the same thought I emailed about that the access concentrator in the NBMA link performing ND Proxy - Wes and I are saying the same thing - he put is very nicely in concise form.  The access concentrator is also the first hop IPv6 router to the broadband enabled home and note that a router interface joins only the all-nodes mcast address and the interface solicited-node mcast address.  Such an interface mcast join will not let the router see all NS(DAD)s on the link.  That is why when a router in the BMA or NBMA link starts sniffing all mcast traffic, then the router sees all the NS(DAD)s on its link and this sniffing for all mcast traffic happens to be the first requirement of a ND Proxy!

As for your question below, the CPE Router in the home has got to have been delegated a prefix and each home gets a different prefix, so how can the UGA from the home device from one home ever encounter a dup at the access concentrator?  If anything dups can exist within the same home, but the CPE Router already takes care of those dups in the home LAN link.

Hemant

-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On Behalf Of Dunn, Jeffrey H.
Sent: Friday, November 06, 2009 6:26 PM
To: 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

Wes,

That is an interesting idea. One question occurs to me that you can probably answer. What happens if a host behind the CPE router does SLAAC, configures a UGA? Since it has already done DAD, the host assumes it has an unused address. When the host finally tries to use the UGA to access the Internet and the access router sends an NA or NS(DAD), what should the host do? It has already validated the UGA using DAD. My interpretation is that it should reply to the NS(DAD) with an NA (based on RFC 4862). I am not sure about a duplicate NA, since DAD is supposed to prevent this. 

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


-----Original Message-----
From: Wes Beebee (wbeebee) [mailto:wbeebee@cisco.com] 
Sent: Friday, November 06, 2009 4:48 PM
To: Dunn, Jeffrey H.; 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 / 神明達哉
Subject: RE: Fwd: Broadband Forum liaison to IETF on IPv6 security

The key is that the access router (which is the only router that knows this is an NBMA link and not a BMA link) can selectively decide to send ND messages (either NA's or NS(DAD) messages) when the access router detects that there is a duplicate on the link.  This is the minimum requirement to support DAD on an NBMA link.  This would need to specified in an NBMA-specific document and probably doesn't need to be mentioned in a document like RFC 4861.

- Wes 

-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On Behalf Of Dunn, Jeffrey H.
Sent: Friday, November 06, 2009 2:18 PM
To: 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

Antonio,

Regardless of whether the ISP bridges the NBMA links or not, the CPE router will not propagate the ND or NS messages onto these links. The Ethernet and Wi-Fi BMA LAN segments are separate logical links from each other and the ISP link(s). How will the CPE router be "convinced" to bridge these link-local scoped messages off link?

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


-----Original Message-----
From: Antonio Querubin [mailto:tony@lava.net]
Sent: Friday, November 06, 2009 1:35 PM
To: Dunn, Jeffrey H.
Cc: Thomas Narten; Fred Baker; 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; Thomson; v6ops-ads@tools.ietf.org; Robin Mersh; Mailing List; Susan@core3.amsl.com; JINMEI Tatuya / 神明達哉
Subject: RE: Fwd: Broadband Forum liaison to IETF on IPv6 security

On Fri, 6 Nov 2009, Dunn, Jeffrey H. wrote:

> The problem is IMHO the following: How to assign an IPv6 UGA to CPE 
> hosts attached to a BMA LAN (usually Ethernet or Wi-Fi) that is in 
> turn connected via a CPE router through an NBMA link (cable modem or 
> DSL) to an ISP router that provides Internet access. Currently, there 
> are two

And what happens when there are multiple CPE routers

a)  connected via a BMA LAN to the DSL or cable modem

and/or

b)  'connected' via separate NBMA links but are on the same WAN subnet (assigned by the ISP)

I think in the latter, if the ISP decides to silo the individual NBMA links then they need to adjust for that in how they do the sub-delegation which is I think what the issue is.  But if the ISP actually bridges the separate NBMA links, then there's no silo issue and the CPE can pretend they're in 'a'.

Antonio Querubin
808-545-5282 x3003
e-mail/xmpp:  tony@lava.net