[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Fwd: Broadband Forum liaison to IETF on IPv6 security
- To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, Antonio Querubin <tony@lava.net>
- Subject: RE: Fwd: Broadband Forum liaison to IETF on IPv6 security
- From: "Dunn, Jeffrey H." <jdunn@mitre.org>
- Date: Fri, 6 Nov 2009 20:29:25 -0500
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: Thomas Narten <narten@us.ibm.com>, "Fred Baker (fred)" <fred@cisco.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>, "IETF@core3.amsl.com" <IETF@core3.amsl.com>, Erik Nordmark <erik.nordmark@sun.com>, "savi-ads@tools.ietf.org" <savi-ads@tools.ietf.org>, IPv6 Operations <v6ops@ops.ietf.org>, "Susan Thomson (sethomso)" <sethomso@cisco.com>, "v6ops-ads@tools.ietf.org" <v6ops-ads@tools.ietf.org>, Robin Mersh <rmersh@broadband-forum.org>, Mailing List <ipv6@ietf.org>, "Susan@core3.amsl.com" <Susan@core3.amsl.com>, JINMEI Tatuya / çæéå <jinmei@isl.rdc.toshiba.co.jp>, "Dunn, Jeffrey H." <jdunn@mitre.org>
- In-reply-to: <AF742F21C1FCEE4DAB7F4842ABDC511C11DD08@XMB-RCD-114.cisco.com>
- 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>
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)