[c-nsp] IPv6 SLAAC on P2P or QinQ subints

[Brian Turnbow]

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Tim Densmore
> Sent: mercoledì 7 novembre 2012 17:12
> To: Cisco NSP
> Subject: Re: [c-nsp] IPv6 SLAAC on P2P or QinQ subints
> 
> On 11/7/2012 12:51 AM, Mikael Abrahamsson wrote:
> > I think you need to elaborate what "this" is.
> 
> Sorry.  Considering the number of "use /126 or /127 on P2P links"
> responses I got, I obviously didn't explain myself very well.
> 
> My aim here is to allow CPE, or CPE-connected devices to "pull" IPs via
> SLAAC, with DHCP-PD being a possible end-goal, but one that will require
> forklifting thousands of DSL modems and/or NAT routers.
> 
> Currently for most v4 DSL subscribers, we use "ip unnumbered" pointing
> towards a loopback that functions as the gateway and use DHCP or host
> routes or radius to assign IPs.  This config appears impossible using v6,
> since loopbacks don't send RAs, and DAD wouldn't work with multiple
> isolated P2P links all IPd from the same /64 in any case.  Basically, I'm
> looking for a way to send non-link-local RAs down ATM P2P subints, and
> dot1q qinq subints.

We assign from Radius using
framed-ipv6-prefix
framed-interface-id

prefix assigns the /64 for the link, and id tells the CPE what address to use from the prefix. 
So you know easily the address which makes it easier on the techs when troubleshooting.

Brian

> 
> What's BCP for this scenario?
> 
> Thanks!
> 
> TD
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/


---
This e-mail is intended only for the addressee named above. 
As this e-mail may contain confidential or privileged information, 
if you are not the named addressee, you are not authorized to retain, read, 
copy or disseminate this message or any part of it.   
 
Please consider your environmental responsibility before printing this e-mail.