[AusNOG] My Predictions for the ISP Industry

Smith, Mark mark.smith at nn.com.au
Wed Mar 14 13:53:42 EST 2012


However, DNS isn't the only "service parameter" you want to propagate to hosts.

Typing in or cutting-and-pasting service parameters, such as NTP, SIP, etc., etc. addresses is both error prone and very user-unfriendly, and something that I don't think we should be continuing to asking our non-technical customers to do (or to have to do on our relatives behalf!). In IPv6 the answer is either stateful or stateless DHCP to propagate all these non-addressing related parameters to the hosts.

Ideally it should be possible to propagate a subscriber specific option to a subscriber's hosts, behind their CPE. An example of this sort of option is the DHCPv6 Geolocation option. For fixed broadband customers, this option could be provided to the subscriber with the geographical location of their service (which usually coresponds with their residence), and then propagated via stateless DHCPv6 to their VoIP handsets. This information could then be used to assist emergency services should the customer dial 000.

I think of RAs as solving the network layer (i.e. layer 3 only) configuration problem (default gateway, MTU, default hop count value, addressing), and (stateless) DHCPv6 as solving the application/services layer parameter configuration problem (i.e. DNS domain, DNS resolver address, NTP, SIP, Geolocation etc.). I think stateful DHCPv6 (i.e. IPv6 address assigning DHCPv6) is more about having database driven address assignment, and in IPv6, that seems to me to really only be about recording who is using what address when (sharing scarce addresses certainly isn't!). While useful, database driven address assignment doesn't guarantee all used addresses are recorded, as hosts can statically be configured with addresses, independent of the stateful DHCPv6 server. See http://tools.ietf.org/html/draft-chown-v6ops-address-accountability-01 "IPv6 Address Accountability Considerations" for some discussion.



-----Original Message-----
From: ausnog-bounces at lists.ausnog.net [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Mattia Rossi
Sent: Wednesday, 14 March 2012 11:02 AM
To: ausnog at lists.ausnog.net
Subject: Re: [AusNOG] My Predictions for the ISP Industry

On 14/03/2012 10:28, Mark Newton wrote:
> On Wed, Mar 14, 2012 at 09:25:05AM +1000, Nicholas Meredith wrote:
>
>   >  Does that Netcomm and other gear in that same leage actually support v6
>   >  properly?
>
> Yes.
>
>   >  Does it run a v6 DNS masquerade?
>
> Yes.
>
>   >  Will RA correctly assign v6 DNS to hosts?
>
> Well, no -- RA doesn't assign DNS.

I guess Nicholas was referring to RDNSS (http://tools.ietf.org/html/rfc6106). Which is supported by MacOSX since Lion, Linux and FreeBSD.

You'd need DHCP to be able to get DNS to a Windows box anyway though, so it doesn't really matter whether it's supported or not.

Current best practice is to have SLAAC for addressing and routing (default route) and DHCP for the rest (DNS, SIP, etc.).

DHCP only won't work either, as there's no option for a default route in
DHCPv6 yet, so you can get an address, but no way out to the Internet..
Currently discussed in the IETF, we'll see some resolution on that hopefully after the Paris meeting.

But back to the topic:

I have a Billion 7401VGP-M, and there's no firmware upgrade at all which would provide IPv6 support. So I'll have to deploy an additional device behind the Billion to get IPv6 eventually (if iiNet decides to extend the trials further than to their Bob devices at some point) and put the Billion in bridging mode (reducing it to an ADSL modem in fact).
Not a real problem for me though. There's plenty of devices to chose from.
TP-Links cost pretty much nothing, and most of them support IPv6. All the ones without ADSL modem, can be upgraded to OpenWRT or DD-WRT - heck you can even run FreeBSD on them:
http://adrianchadd.blogspot.com.au/2011/11/freebsd-on-tp-link-tl-wr1043nd.html

The only drawback many (if not all) of those devics is, that they don't have RA-guard (http://tools.ietf.org/html/rfc6105) in them. So if your silly friend comes to your house with his old WinXP box sending out RA's which are based on his Teredo prefix, he'll screw up your IPv6 network quite quickly. this is based on real observation of the wireless network here at Swinburne. Plenty of that stuff happening.

Mat
_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog


This email is intended for the named recipient only. The information contained in this message may be confidential, or commercially sensitive. If you are not the intended recipient you must not reproduce or distribute any part of the email, disclose its contents to any other party, or take any action in reliance on it. If you have received this email in error, please contact the sender immediately and please delete this message completely from any systems. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________



More information about the AusNOG mailing list