nanog mailing list archives
Re: IPv6 news
From: trainier () kalsec com
Date: Thu, 13 Oct 2005 16:39:22 -0400
ntpdate -q 2001:0440:1880:1000::0020 server 2001:440:1880:1000::20, stratum 1, offset 0.048519, delay 0.56551 13 Oct 15:41:08 ntpdate[7397]: adjust time server 2001:440:1880:1000::20 offset 0.048519 sec Tim Rainier JORDI PALET MARTINEZ <jordi.palet () consulintel es> Sent by: owner-nanog () merit edu 10/13/2005 03:23 PM Please respond to jordi.palet () consulintel es To "nanog () merit edu" <nanog () merit edu> cc Subject Re: IPv6 news Yes ;-) JPMac:~ jordi$ ntpdate -q 2001:0440:1880:1000::0020 13 Oct 21:23:11 ntpdate[347]: can't find host 2001:0440:1880:1000::0020 server 0.0.0.0, stratum 0, offset 0.000000, delay 32639.00000 server 17.72.133.42, stratum 2, offset -9.996023, delay 0.13766 13 Oct 21:23:12 ntpdate[347]: step time server 17.72.133.42 offset -9.996023 sec Regards, Jordi
De: Peter Lothberg <roll () Stupi SE> Responder a: <owner-nanog () merit edu> Fecha: Thu, 13 Oct 2005 11:05:58 PDT Para: Randy Bush <randy () psg com> CC: "Steven M. Bellovin" <smb () cs columbia edu>, <nanog () nanog org> Asunto: Re: IPv6 newsso having dual stack backbones is very important. but ...Other global providers have a IPv6 network to, all open for business, but there are very VERY few customers. And, I'm not so sure we even have a "Internet" of IPv6 out there either. It looks cold and empty to me. Here's a challange, have NTP server attached directly to a good clock and a IPv6 network. Is there anyone who can talk to it using IPv6 on the Nanog list? (Time20.Stupi.SE, 2001:0440:1880:1000::0020) -Peter
************************************ The IPv6 Portal: http://www.ipv6tf.org Barcelona 2005 Global IPv6 Summit Information available at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
Current thread:
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news), (continued)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Nicholas Suan (Oct 13)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Christopher L. Morrow (Oct 13)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Mikael Abrahamsson (Oct 14)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Jeroen Massar (Oct 14)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Jared Mauch (Oct 14)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Valdis . Kletnieks (Oct 14)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Jared Mauch (Oct 14)
- Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news) Bill Owens (Oct 13)
- Re: IPv6 news Michael . Dillon (Oct 14)
- Re: IPv6 news trainier (Oct 13)
- Re: IPv6 news Valdis . Kletnieks (Oct 13)
- Re: IPv6 news Jared Mauch (Oct 15)
- Re: IPv6 news Joe Abley (Oct 16)
- Re: IPv6 news John Reilly (Oct 16)
- Re: IPv6 news Joe Abley (Oct 16)