[AusNOG] My Predictions for the ISP Industry

Smith, Mark mark.smith at nn.com.au
Thu Mar 15 09:47:22 EST 2012


I think the definition of IPv6 CPE working well at least is not suffering from any of the problems identified in my presentation from last year - in particular, there is a big gap between "working" and "working well".

http://www.ausnog.net/images/ausnog-05/presentations/5-2-residential%20ipv6%20cpe%20-%20what%20not%20to%20do%20and%20other%20observations.pdf



________________________________

From: ausnog-bounces at lists.ausnog.net [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Grant Moritz
Sent: Wednesday, 14 March 2012 8:21 PM
To: ausnog at lists.ausnog.net
Subject: Re: [AusNOG] My Predictions for the ISP Industry


 >  Does that Netcomm and other gear in that same leage actually support v6
 >  properly?


I did a bit of work with Netcomm after Mark / Matthew left Internode in testing the firmware and it worked well. There was only one minor concern before I would have been ready to Netcomm to release it although never had a chance to have it resolved before I left Helpdesk.


>put @ipv6 into the username field (i think they default to ipv6 for new customers now?)


Correct, IPv6 is set on the backend by default, the setting can be changed in My Internode. Default = having to use @ipv6.internode Enabled = Dual stack using @internode.on.net Disabled = Off


>I have a Billion 7401VGP-M, and there's no firmware upgrade at all which would provide IPv6 support

None of the M series are IPv6 compatible unfortunately.

>... and an NBN connection, with new dual-stack CPE replacing their
>5-year-old v4-only ADSL modem.


Which reminds me the NP805N was released recently and it was actually out of box IPv6, in addition to the Siemens C610 which is slated to get IPv6 later this year and the end point is definitely getting there.



Thanks,

Grant Moritz




On Wed, Mar 14, 2012 at 5:19 PM, Smith, Mark <mark.smith at nn.com.au> wrote:


        Variable length addresses have been done before (TCPv1 (TCP/IP before TCP and IP were split), CLNS), and the majority of humans tend to simple fixed length addressing, even when they have a choice. My understanding is that address lookups would also be harder or at least the hardware to make them fast would also be more expensive.

        (TCPv1 supported variable length addresses composed of a number of 4 bit components, with the number of components also encoded as 4 bits, ranging in value from 1 to 15, giving a maximum variable length address size of 60 bits.)



        -----Original Message-----
        From: ausnog-bounces at lists.ausnog.net [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Mark Delany
        Sent: Wednesday, 14 March 2012 5:08 PM
        To: ausnog at lists.ausnog.net
        Subject: Re: [AusNOG] My Predictions for the ISP Industry


        On 14Mar12, Mark Newton allegedly wrote:
        > On Wed, Mar 14, 2012 at 03:10:30PM +1000, Terry Sweetser wrote:
        >
        >  > On 14/03/12 12:17, Noel Butler wrote:
        >  > > facebook (god help them)
        >  >
        >  > https://www.v6.facebook.com/
        >
        > Which is, of course, 2620:0:1cfe:face:b00c::3
        >                                  ^^^^^^^^^
        >
        > I prefer to put dead:beef:c00f:ee into my addresses.

        Anyone remember the suggestion to make v6 addresses be variable length strings?

        Route my packet to com.facebook.www please.

        Or route my packet to org.dotat.atdot at newton where org.dotat.atdot decides what to do with anything following its own prefix.

        Crazy? Maybe. I do note however that both "com.facebook.www" and "org.dotat.atdot" fit in the same space as a v6 address and present a self-encoded CIDR-like address.


        Mark.
        _______________________________________________
        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
        ______________________________________________________________________

        _______________________________________________
        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