IETF Logo Mail Archive

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

"Dunn, Jeffrey H." <jdunn@mitre.org> Sat, 07 November 2009 04:52 UTC

Return-Path: <jdunn@mitre.org>
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 356583A6886; Fri, 6 Nov 2009 20:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.112
X-Spam-Level:
X-Spam-Status: No, score=-6.112 tagged_above=-999 required=5 tests=[AWL=0.487, 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 RbMHC8c8Vteh; Fri, 6 Nov 2009 20:52:10 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 102883A67A4; Fri, 6 Nov 2009 20:52:08 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id nA71TTEK028254; Fri, 6 Nov 2009 20:29:30 -0500
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id nA71TTcc028251; Fri, 6 Nov 2009 20:29:29 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Fri, 6 Nov 2009 20:29:28 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, Antonio Querubin <tony@lava.net>
Date: Fri, 06 Nov 2009 20:29:25 -0500
Subject: RE: Fwd: Broadband Forum liaison to IETF on IPv6 security
Thread-Topic: Fwd: Broadband Forum liaison to IETF on IPv6 security
Thread-Index: AcpfD9ATPsDVSCGmTqCpJYWjx52aqwABaHbAAAUHVrAAAurLsAACWa5AAACk0zAAAQdzgAABAHUA
Message-ID: <3C6F21684E7C954193E6C7C4573B76270367855CBF@IMCMBX1.MITRE.ORG>
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>
In-Reply-To: <AF742F21C1FCEE4DAB7F4842ABDC511C11DD08@XMB-RCD-114.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Sat, 07 Nov 2009 04:57:51 -0800
Cc: Thomas Narten <narten@us.ibm.com>, "6man-ads@tools.ietf.org" <6man-ads@tools.ietf.org>, SAVI Mailing List <savi@ietf.org>, "william.allen.simpson@gmail.com" <william.allen.simpson@gmail.com>, Hesham Soliman <hesham@elevatemobile.com>, Erik Nordmark <erik.nordmark@sun.com>, "Susan@core3.amsl.com" <Susan@core3.amsl.com>, "savi-ads@tools.ietf.org" <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" <v6ops-ads@tools.ietf.org>, "IETF@core3.amsl.com" <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 04:52:11 -0000

Hemant,

Fair enough. I suppose that there are enough /55's or /56's that every household can have one; however, it does make "right sizing" the initial allocation to the ISP very important. We would not want to be allocating non-contiguous /28's on a regular basis :-)

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


-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com] 
Sent: Friday, November 06, 2009 8:07 PM
To: Dunn, Jeffrey H.; 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 / 神明達哉
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)

v2.23.0 | Report a Bug | By Email