Thanks every one for suggestions. I found one more resource which is more in
tune with what I was looking for:
https://blog.apnic.net/2023/04/04/ipv6-architecture-and-subnetting-guide-for-network-engineers-and-operators/
X.
Sent with [Proton Mail](https://proton.me/) secure email.
---
On 31 Jul 2023 at 11:19:29, Sander Steffann wrote:
> See if you can find a friendly local person in your local Network
> Operators Group (NOG) to help you a bit. NOGs are a great place for those
> looking to learn. And otherwise feel free to contact me off-list. I’ll
> happily get you started.
Hi,
> We are not using IGP as of now, its a small NOC with a couple of devices.
I would strongly suggest using an IGP (probably OSPF) even in a small setup. It
will allow you much greater flexibility and redundancy with very little effort.
See if you can find a friendly local person in your
Thanks for your input Michael. The vagueness of the problem description
reflects my own confusion.
We are not using IGP as of now, its a small NOC with a couple of devices.
--- Original Message ---
On Monday, July 31st, 2023 at 12:38 AM, Michael Richardson
wrote:
> Each router
Xuo Guoto via ipv6-wg wrote:
> 1. How will we assign address to routers? Like will we should be
> assigning 2001:db8:2000::1/35 or 2001:db8:2000::1/64 for router
No.
Each router needs a /128 as a loopback address to use.
I assign them all from a single /64 for that purpose.
The /128s go
Hello all,
Resurrecting an old thread to share some experience when trying to start
deploying ipv6 on a small London based ISP.
As a start we are deploying in a test location which is setup as a "site". We
have a /29 allocated and that's been divided into /32 for each site. Which is
again
Sent: Thursday, June 1, 2023 4:20 PM
To: Paolo Volpato
Cc: ipv6-wg@ripe.net
Subject: Re: [ipv6-wg] Clear Guidance for Enterprises
Hi Paolo,
thanks for your help with this project.
Lack of budget is of course a problem. But if the IT departments could at least
quantify the budget, this would help
Hi,
On 6/1/23 17:21, Wilhelm Boeddinghaus wrote:
Hi Andreas,
if the government starts shutting down services with IPv4, the pressure
for IPv6 will rise :-) There are no laws needed.
Many countries have some sort of equal access laws, that could be used
to prevent shutting down IPv4 services.
Hi,
On Sun, Jun 04, 2023 at 08:16:58PM +, Jordan A. Borgner wrote:
> What's very important too is to get the application developers on board.
> Advances in the software that uses the network (and gives it its reason
> to exist) is a crucial factor I think. If there are technical benefits
>
On 6/3/23 12:33, Gert Doering wrote:
> So, what else can we do?
At the end a number of factors that make up the big picture must play
together to roll that stone up the hill, and all of them influence one
another, at least a bit. Compatibility to other networks, amount of
work to maintain the own
of RFC 9386 on IPv6
deployment status.
I would be happy to contribute to this effort.
Best regards
Paolo
-Original Message-
From: ipv6-wg On Behalf Of Wilhelm Boeddinghaus
Sent: Tuesday, May 30, 2023 6:06 PM
To: ipv6-wg@ripe.net
Subject: [ipv6-wg] Clear Guidance for Enterprises
Hi
Hi,
On Sat, Jun 03, 2023 at 07:53:48PM +, Ole Troan (otroan) wrote:
> Thought experiment.
> IPv6 wasn?t invented.
> Would we be able to make IPv4 continue to roll down the hill for another 25
> years?
Whether there's 3 or 4 layers of NAT won't matter much... everything
that is not TCP or
Hi,
On Sat, Jun 03, 2023 at 07:00:48PM +0100, Nick Hilliard wrote:
> Gert Doering wrote on 03/06/2023 13:33:
> > So how do we get there?
>
> We got where we are now because there are compelling reasons to deploy
> ipv4, but not compelling reasons to deploy ipv6.
On "the wild Internet", I
Gert Doering wrote on 03/06/2023 13:33:
So how do we get there?
We got where we are now because there are compelling reasons to deploy
ipv4, but not compelling reasons to deploy ipv6. IPv4 is the stone that
rolled down the hill; ipv6 is the stone that, 25 years later, people are
still
Hi,
On Fri, Jun 02, 2023 at 11:15:51PM +, Jordan A. Borgner wrote:
> Companies just need to _feel_ that IPv4 isn't going to get them very far
> anymore and that it's better to prepare for the future now because its
> better to have options rather than to need them when the time has come.
So
On 6/1/23 15:06, Nick Hilliard wrote:
> Which government service would you suggest shutting down on ipv4?
I can't imagine any government to require anyone to support IPv6, one
particular protocol, explicitly, and even less to require anyone to shut
down still-working IPv4. If you can't even
Benedikt Merkl via ipv6-wg wrote on 01/06/2023 15:25:
The government still relies on their Fax machines, so not sure if that
is going to happen soon. But you have my support on shutting v4 services. :)
Which government service would you suggest shutting down on ipv4? The
online tax submission
onal Services &
> Administration SE, Mülheim an der Ruhr ∙ Registergericht: Amtsgericht
> Duisburg · HRB 34355
>
> Geschäftsführende Direktoren: Dr. David Godschalk, Daniel Koch, Reiner
> Mischke, Inka Rückle
>
> Weitere Gesellschafter: ALDI SE & Co. Kommanditgesellschafte
ation SE, Mülheim an der Ruhr ∙ Registergericht: Amtsgericht
>> Duisburg · HRB 34355
>>
>> Geschäftsführende Direktoren: Dr. David Godschalk, Daniel Koch, Reiner
>> Mischke, Inka Rückle
>>
>> Weitere Gesellschafter: ALDI SE & Co. Kommanditgesellschaften der
n der
Unternehmensgruppe ALDI SÜD
-Original Message-
From: ipv6-wg On Behalf Of Paolo Volpato
via ipv6-wg
Sent: Mittwoch, 31. Mai 2023 08:42
To: Wilhelm Boeddinghaus
Cc: ipv6-wg@ripe.net
Subject: Re: [ipv6-wg] Clear Guidance for Enterprises
Caution: This email originated from outsi
be happy to contribute to this effort.
Best regards
Paolo
-Original Message-
From: ipv6-wg On Behalf Of Wilhelm Boeddinghaus
Sent: Tuesday, May 30, 2023 6:06 PM
To: ipv6-wg@ripe.net
Subject: [ipv6-wg] Clear Guidance for Enterprises
Hi,
at the end of my talk during the RIPE86 IPv6 working
On 5/30/23 19:06, Wilhelm Boeddinghaus wrote:
They have no time and they lack knowledge
Well, they seem to have the time to learn about and invest in
complicated and outdated NAT solutions in order to stretch what little
IPv4 they have. Let's produce some IPv6-only (with some proper
Hi
> The civil servants were concerned that adding an IPv6 requirement would
> further reduce competition and make managing cost more difficult.
And this is - in my opinion - just a reflection of the typical
counter-argument coming from these IT consultants being reluctant getting their
Hi,
On Tue, 30 May 2023 at 23:52, Springob, Andreas (IIT-CSS/Network &
Identity Solutions) wrote:
>
> Hi Wilhelm,
>
> Lot of things were said and all are correct. Lack of knowledge, budget,
> priority, interest, projects, success. It might be rather an approach for
> RIPE and other RIRs to get
2023 08:42
To: Wilhelm Boeddinghaus
Cc: ipv6-wg@ripe.net
Subject: Re: [ipv6-wg] Clear Guidance for Enterprises
Caution: This email originated from outside of the ALDI-HOFER organisation. If
the content looks suspicious, please report this email via the "Phish Alert
Report" button or th
.
Best regards
Paolo
-Original Message-
From: ipv6-wg On Behalf Of Wilhelm Boeddinghaus
Sent: Tuesday, May 30, 2023 6:06 PM
To: ipv6-wg@ripe.net
Subject: [ipv6-wg] Clear Guidance for Enterprises
Hi,
at the end of my talk during the RIPE86 IPv6 working group I promised to start
work
Hi Wilhelm
Me being a network engineer in an enterprise and an IPv6 enthusiast can say,
that it even fails within the IT.
Many IT workers, from server administrators over network consultants to
application / solution designers still ignore IPv6 as an avoidable burden.
Every time I talk vendor
On 30 May 2023, at 18:50, Michael Richardson wrote:
Wilhelm Boeddinghaus wrote:
We have often wondere why enterprises do not migrate to IPv6. One
possible answer is: They have no time and they lack knowledge. Many IT
departments don't have any spare time for reading RFCs.
They have no
Wilhelm Boeddinghaus wrote:
> We have often wondere why enterprises do not migrate to IPv6. One
> possible answer is: They have no time and they lack knowledge. Many IT
> departments don't have any spare time for reading RFCs.
They have no management mandate on spending their time
Hi,
at the end of my talk during the RIPE86 IPv6 working group I promised to
start work on a paper with clear guidance for enterprises to migrate
their networks to IPv6.
We have often wondere why enterprises do not migrate to IPv6. One
possible answer is: They have no time and they lack
30 matches
Mail list logo
