Re: Android and DHCPv6 again

2015-10-06 Thread Enno Rey
Hi, On Tue, Oct 06, 2015 at 08:59:14PM -0430, Alejandro Acosta wrote: > Hello, > This is a question a should test myself but anyhow I would like to > hear your comments. > What happen (on the client side/Android maybe) if I advertise the DNS > information in the RA and I also enable the O

RE: Telus ADSL IPv6 Roll Out

2015-10-06 Thread Steve Mikulasik
I looked around a bit more and I am assigned a /56. It was confusing in their router, digging through a few more pages showed the /56. Performance is significantly worse through IPv6 on Telus right now, google takes twice as long (14ms IPv4, 30ms IPv6) and facebook is significantly worse

Re: How to wish you hadn't forced ipv6 adoption (was "How to force rapid ipv6 adoption")

2015-10-06 Thread MÃ¥ns Nilsson
Subject: How to wish you hadn't forced ipv6 adoption (was "How to force rapid ipv6 adoption") Date: Thu, Oct 01, 2015 at 11:06:34PM -0400 Quoting Rob McEwen (r...@invaluement.com): > > I welcome IPv6 adoption in the near future in all but one area: the sending > IPs of valid mail servers. Those

RIPE atlas probes

2015-10-06 Thread Weir, Colin
?Hello attendees, I have a few RIPE Atlas probes with me at the conference for distribution. If you're interested in participating in RIPE measurements, please get in touch with me off-list and I'll be happy to give you one. We have a special interest in the following ASNs, which currently

Re: How to wish you hadn't forced ipv6 adoption (was "How to force rapid ipv6 adoption")

2015-10-06 Thread George Michaelson
X.400 required a session key. IIRC you had to know the other side of the mail exchange and do (weak, but of the time what we did) shared secret swaps to bootstrap the protocol. Of course, a cheat-sheet of 'your idea will not work because [ ]' kills it, but I do recall with some fondness that in

Re: RIPE atlas probes

2015-10-06 Thread joel jaeggli
On 10/6/15 12:20 PM, Weir, Colin wrote: > 3549 > > LVLT-3549 - Level 3 Communications, Inc. 3549 and 3356 probes should have largely the same vantage point since the former remains as a thin veneer on the latter. > > > > -- > Colin Weir > Engineer, Quality of Experience, Comcast

Re: RIPE atlas probes

2015-10-06 Thread Alan Buxey
'should have largely the same vantage point ...' That's *exactly* one of the functions of these probes. It's very interesting what they can find out. Never assume (you know the rest of that...) alan

Re: Android and DHCPv6 again

2015-10-06 Thread Bruce Horth
The Android client should ignore the O-flag and just use the information in the RA. Windows clients will ignore the DNS option in the RA and do a DHCP request for the Other information. My understanding is you can enabled the O-flag for stateless DHCPv6 and set the RA DNS option at the same time.

Re: Android and DHCPv6 again

2015-10-06 Thread Bruce Horth
Your device may be getting an address, but without a recursive DNS server it may be useless. If you're going to do SLAAC you'll also need to supply your client with a recursive DNS server. Android prefers RFC 6106. As you mentioned, Google has decided not to support DHCPv6 in Android.

Re: Android and DHCPv6 again

2015-10-06 Thread Alejandro Acosta
Hello, This is a question a should test myself but anyhow I would like to hear your comments. What happen (on the client side/Android maybe) if I advertise the DNS information in the RA and I also enable the O bit? Thanks, Alejandro, El 10/6/2015 a las 8:39 PM, Bruce Horth escribió: > Your

Updated NANOG 65 DD4BC presentation file.

2015-10-06 Thread Roland Dobbins
I'd inadvertently failed to upload the final revision of the DD4BC presentation file from NANOG 65 - please find the updated .pdf file here, apologies for my confusion: --- Roland Dobbins

Request for contact from KPN

2015-10-06 Thread Chris Russell
Hi Apologies for using the list - is anyone from KPN around and can drop me a line off-list ? Ta Chris

This came up in the security meeting today in Monteal - New tacacs Work!

2015-10-06 Thread Christopher Morrow
As mentioned, there's a draft to collect and 'fix' problems that we (google netops folks) see with tacacs+ today: If folk can give this a quick read, send comments to the authors (see draft for emails of authors) OR the ops area wg