Re: [v6ops] RFC 7084 on Basic Requirements for IPv6 Customer Edge Routers

[Wuyts Carl <[e-mail]>]

Hi Ole,

I've seen the MAY and SHOULD etc, I just think it is a silly requirement, hence should better not be present, so just leave it out (hint can stay in perfectly)
It in fact leads to customers asking us "too small-checking" in tenders/rfp/..., so as of that moment, you have to start explaining that this is not possible, there is AND should be NO link between them.  You should not put up these reqs to the CPEs at all as they make no sense.  Everyone will translate this their own way.  I've talked to someone not too long ago, claiming that /60 is too small for him/his network, although I would highly doubt he has a CPE with 16 physical intfs...

Regs
Carl




-----Original Message-----
From: Ole Troan [mailto:[e-mail]] 
Sent: maandag 25 november 2013 15:48
To: Wuyts Carl
Cc: [e-mail]; [e-mail]
Subject: Re: [v6ops] RFC 7084 on Basic Requirements for IPv6 Customer Edge Routers

Carl,

> A typical CPE has 4 eth ports and wifi, all joined together as ... the LAN intf, hence 1 interface it is.  You do not hand out different prefixes to wired and wireless.  In fact, you can of course, but this would lead to routed traffic between wired and wireless, which cannot be the target I'd say.
> Potentially, you could have a separate hotspot/public wifi, even more than one potentially,  although for sure not always used, and very often v4-only, hence no real need today for ipv6 prefix today.
> 
> We're deploying in managed CPE, so the hint will for sure not change anything.  I agree it is also "just" a hint, but the req in the RFC says you SHOULD flag "too small" and it's exactly that part which is not ok, not the fact that you should sent a hint or anything. 
> 
> Today, our customers hand out anything between 48 and 64, and size NOT depending on "too big or too small". 
> 
> And I do get a /56 @ home, so works smooth here too, but the choice of /56 is not depending small/big number of physical intfs.

the hint is a MAY. you'd be perfectly fine not including it.
the hint is largely there to give an indication to the server to give the same prefix back as it delegated in a previous session.

cheers,
Ole