Michael Richardson writes:
> Did you get any real feedback as to why they are hesistant though?
Not really. And most of the people there were already doing IPv6.
> I've heard that lack of widespread training is one oft cited reason, but at
> the same time, managers refuse to actually provide
Jens Link writes:
> https://gitlab.com/jenslink/advent-of-ipv6
And yes this is a private repo. Wouldn't want to give away all the fun
stuff we may come up with.
Jens
--
| Delbrueckstr. 41| 12051 Berlin, Germ
Not sure if I send this to this list. Last year I started working in a
new IPv6 project and needed a place to collect some links.
So here we go: https://gitlab.com/jenslink/ipv6-resources/
Fell free to send merge requests.
Jens
--
Nico Schottelius writes:
Hi,
> I'd be up for participating in such an adventure, in terms of
> contributing ideas and/or (co-)sponsoring as well.
>
> The IPv6 train is moving - ch000ch000!
I just created a gitlab project.
https://gitlab.com/jenslink/advent-of-ipv6
Jens
--
Raymond Jetten writes:
> Dear IPv6 Working Group,
>
> Jen Linkova, who has been one of the co-chairs of the IPv6 Working Group
> since RIPE 69
>
> has announced she wishes to step down at the RIPE 88 meeting in
> Kraków, at the end of her term.
>
> Thus, we have a call for candidates.
If
Hi,
last Monday there was an event by https://www.eco.de titled
"IPv6 in Germany - How do we help those who are hesitant?"
It was a nice day but unfortunately very few of the hesitant people where
there. As I'm also currently working in a rather big IPv6 project IPv6
know how and training is
Michael Richardson writes:
> A few years ago there was a presentation about getting IPv6 MX setup for
> various Dutch entities: Municipalities, Hospitals, etc. I couldn't find this
> in the agendas for the past ten RIPE meetings for IPv6. Maybe it was in a
> plenary. I think it was
Michael Richardson writes:
> A few years ago there was a presentation about getting IPv6 MX setup for
> various Dutch entities: Municipalities, Hospitals, etc. I couldn't find this
> in the agendas for the past ten RIPE meetings for IPv6. Maybe it was in a
> plenary. I think it was
Nico Schottelius via ipv6-wg writes:
Hi,
> For those who want to be involved/know what is going on: gitlab (and
> github and so on) has a nice "watch" features that notifies on any
> change.
so here is a small summary of what you need to participate. As already
mentioned the project will use
Nico Schottelius via ipv6-wg writes:
> For those who want to be involved/know what is going on: gitlab (and
> github and so on) has a nice "watch" features that notifies on any
> change.
A "how to contribute" document is already on my todo list.
> Jens, what do you think about a short, monthly
Hi,
about a month ago I was asked on Twitter if I new any good and current
books ob IPv6. Apparently there is nothing current[1].
I came up with the idea of starting an OpenSource Guide on IPv6. I
created a git repo: https://gitlab.com/jenslink/ipv6guide and also
have (sponsored) hardware to run
Hi,
just ran into this on twitter:
https://github.com/buraglio/broken-v6only
---
A running list of applications and processes that just do not work with
the total absence of IPv4 on on a host. Contributions welcome and encouraged.
---
Maybe the RIPE community can give more input.
Jens
--
Fernando Gont writes:
>> The SEND requirment? No OS I'm aware of does support it and it only
>> makes sense when the networking hardware and the OS support it.
>
> I think SEND is a smart spec/artifact... but I also think that I would
> probably have a hard time finding a reason to deploy it.
Tim Chown via ipv6-wg writes:
Hi,
> - Is the linkage to the IPv6 Ready Logo programme still desired?
It this still a thing? Haven't heard of it in a long time.
> - Are there new classes of equipment to add, e.g. IoT/low power,
Probably. Maybe another document? Does it make sense to
Bernd Naumann writes:
> Try "Browser"
I only get "Install flash". Using Firefox and Chromium.
Jens
--
| Delbrueckstr. 41| 12051 Berlin, Germany | +49-151-18721264 |
| http://blog.quux.de | jabber:
Ondřej Caletka writes:
> Expert presenters will talk about what it means to run IPv6-only data
> centres, ISPs and enterprises, among other topics. You can view the
> agenda at:
> https://www.ripe.net/support/training/ripe-ncc-educa/ripe-ncc-educa-ipv6-2020
"Adobe Connect requires Flash Player
Philip Homburg writes:
> I don't know where to put it, but there may be a benefit for a list that
> lists known internet services that do not (or poorly) support IPv6 and with
> replacements that do support them.
Some time ago I setup a wiki for stuff like that but got abused pretty
fast. I'll
Ondřej Caletka writes:
Hi,
> Register at:
> https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184
$ dig www.eventbrite.nl +short
$
"IPv6-only"
Jens
--
| Delbrueckstr. 41| 12051 Berlin,
Ivan Pepelnjak writes:
> What happened to /etc/hosts files?
The source of all evil. Or on the other hand: A good way to earn
money. I wrote an invoice for looking into /etc/hosts once.
> And this has the underlying problem in large development setups where
> the single developer or
Uros Gaber writes:
> Hi all,
>
> as a developer I can say with some confidence, that a big hurdle is to
> use hostname instead of IPs, it's way simpler to use IP during
> development than to use hostname where you have to configure DNS
> record to do so.
and DNS always breaks and is way to
Andreas Härpfer writes:
Hi,
> I think in the off-record discussion after her talk Veronika was
> also asked about the sad status of Github with regard to IPv6 and
> she promised to address this to the appropriate folks within
> Microsoft.
it's a long an sad story. Many people have asked. Every
Jen Linkova writes:
Hi,
> We are looking for talks. COVID-19 does not seem to be a reason good
> enough to slow down IPv6 deployments. I suspect it might be a reason
> for accelerate them, actually. So stories about 'IPv6 in the Time of
> Cholera' (or any other talks about IPv6) are
Nico Schottelius writes:
> I think at RIPE79 there was 1 v6only/nat64 network and 1 dual stack, the
> latter being the default.
This is the setup for a couple of years and only few people are using
it. One of the reasons might be that devices will connect to a known
network without any user
Sander Steffann writes:
> I would expect such devices mostly in a home network (gaming consoles
> etc). On a business meeting network like RIPE the number of IPv4-only
> devices is negligible.
I guess there will be quite a few devices were people disable IPv6.
>> We cannot use DNS64 if we
Philip Homburg writes:
> NAT64 is also not attractive from a backward compatibility point of view:
At the last meeting Enno talked[1] about plans for a large wireless
deployment running v6 only + NAT64 / DNS64. As I know which
"Supermarket" Enno is talking about:
If this would be deployed in
Dave Taht writes:
Dave,
> If I can get *one* person in this working group to go down to their
> local coffee shop and make ipv6 work by whatever means necessary (and
> also fix their bufferbloat) - I'll consider my participation in this
> thread a success.
you have to be strong now. Your
"S.P.Zeidler" writes:
> Given we'll have enterprise walled gardens with v4 inside for a long time,
> that indeed will take decades. If you plan projects that span more than
> one decade, making sure it's IPv6 capable will at least save you money
> in the long run, because enterprise-only
Carlos Friaças via ipv6-wg writes:
> Hi Alexander, All,
>
> Github is now owned by Microsoft.
> Someone from Microsoft reading this? Maybe Veronika from Microsoft and
> the UK IPv6 Council?
>
> Cisco: just saw a post from Eric Vyncke. :-))
twitter, slack, amazon, stackexchange, redhat
Anton Rieger writes:
> In the IPv4 net many are scattered (right now)
This is good from a security perspective. Confuses the attacker!
Jens
--
| Delbrueckstr. 41| 12051 Berlin, Germany |
Jan Zorz - Go6 writes:
Jan,
> I would like to encourage you to submit a proposal to RIPE PC for a BoF
> that would discuss your topic.
This is a great idea. I will do so right after finishing this mail
> If you get enough like-minded people to the BoF and present the
> usefulness of more
Enno Rey writes:
> Hi,
>
> I support the proposal. Once a protocol has reached mainstream
> deployment (as IPv6 has) a dedicated WG might no longer be needed. I
> mean, there's no IPv4 WG either, right?
>
> now back to my day job, full of #IPv6
So you are done with your work and Bjoern can get
Olivier MJ Crépin-Leblond writes:
> Dear Jens,
>
> you're right. I also think that TCP-IP is unable to cope with today's
> Internet traffic and we should use a modern protocol like X.25: the
> problem with IPv6 is not the v6 part, it's the IP. Kindest regards,
Back to OSI? I like that!
Riccardo Gori writes:
>>> 1. WHY should it have NAT
>> NATs are good. They provide security.
>
> Are you sure you are about networking?
People believer this so it must be true.I wont question the believes and
wisdom of thousands of networking experts.
Jens
--
Carlos Friaças via ipv6-wg writes:
> CIDR.
> People that thought that terminology to students over the years really
> fumbled...
years ago? It's till taught. Did a entry level Juniper Certification
some time ago and they asked which Class 10.10.10.10 belongs to. Sure
CIDR turned 26 last month
Uros Gaber writes:
> On 3 Oct 2019, at 14:03, Job Snijders wrote:
>> Even worse, delivering email over ipv6 to the mail giants is a far
>> worse experience than via ipv4. More emails arrive when you
>> disable ipv6 on your mail servers.
> I would say the same experience as long as
Carlos Friaças via ipv6-wg writes:
> Hi,
> (Respectfully)
>
> IPv6 _is_ working.
github, stackexchange, twitter, amazon.com
As a small test: Try to see if you can get all the packages needed for
Linux from Scratch on an IPv6 only host (with out any form of NAT /
proxy). There was as
Andreas Härpfer writes:
>> On 3. Oct 2019, at 13:16, Antonio Prado via ipv6-wg wrote:
> No worries, looking at the headers and seeing that nearly all
> received-by mail hops in the original mail use IPv6 addresses
> -- and considering that IPv6 doesn't work anyway -- the whole
> email
Uros Gaber writes:
> 1. WHY should it have NAT
NATs are good. They provide security.
> 2. What do you understand under class, IPv4 "Classes" are just defined
> subnet groups (simply put)
Things need names. Numbers are hard to remember. We have Class-A for /8,
Class-B for /16 and Class-C for
Hi,
after now almost 12 years using, working and teaching[1]
IPv6 I've come to the conclusion that IPv6 is a mistake and will
not work.
Therefore the RIPE IPv6 WG should be disbanded and replaced
with a new WG that MUST investigate all possible solutions to
artificially prolong the live of IPv4
Jetten Raymond writes:
> However, I’m very willing to stand for re-election, and serve another
> term as IPv6 WG co-chair, which I hope you all find a good idea.
+1 from my side.
Jens
--
| Delbrueckstr. 41|
Ivan Pepelnjak writes:
> The problem is often internal networking. Every large cloud provider
> probably wrote their own overlay networking implementation, and would
> have to reimplement it for IPv6
I can't hear it anymore.
Sometimes IT is a world full of surprises and
Benedikt Stockebrand writes:
> They used AWS/S3 for some relevant stuff, and since it was done
> externally it wasn't properly QAed. When Amazon switched IPv6 off
> again, they had a little bit of an issue. We only found out kind of
> accidentially, especially so
Benedikt Stockebrand writes:
Hi,
>> Well many content providers / startups use "the cloud". No IPv6 there,
>> no content.
>
> Stopitstopitstopitstopit!
Seriously. Several people told me "If AWS doesn't offer IPv6 we don't
need IPv6." On the other hand someone told me
Benedikt Stockebrand writes:
Hi,
>> And may I add cloud providers?
>
> No, you may not. Definitely not. Go away. And take those enterprises
> using them as a cheap CDN with you...
Well many content providers / startups use "the cloud". No IPv6 there,
no content.
>
Peter Koch p...@denic.de writes:
Atlas should be used as an Internet measurement tool, not as a reconnaissance
mechanism for the hosts' networks. ULA only equals no IPv6 in my opinion.
I think it might be interesting to see what breaks (and what not) when ULA and
some form of address
45 matches
Mail list logo