This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Previous message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Next message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Massar
jeroen at unfix.org
Thu Dec 1 18:30:05 CET 2005
[multiple messages compressed into one] Florian Weimer wrote: > * Hans Petter Holen: > >> Very easy. In the Internet the equivalent of phone numers, the DNS names >> are alleady portable - so you can easily switch ISP and keep your email >> address and URLs without renumbering. > > I can't put DNS names on network interfaces. But I can use private > address space and NAT, or public address space, DNS rewriting and > double NAT. Not pretty, but gets the job done. (psst... 'double NAT' is one of the things shim6 is going to use) As for "DNS rewriting" any example of that? bmanning at vacation.karoshi.com wrote: > On Thu, Dec 01, 2005 at 04:53:44PM +0100, Jeroen Massar wrote: >> As an exercise for the readers try to remember why there are >> filters on >> IPv4 /24 boundaries and the try to figure out why there are quite a >> number of people not wanting IPv6 PI to fill their IPv6 routing >> tables. > > one might also ask why a RIB/FIB entry has more relevance > for one size prefix instead of another. Ease of filtering. Not much more. The 'worthiness' of a prefix depends more on the service provided in that prefix. One for instance would not really want to loose the connectivity to all the DNS root or TLD servers and most ISP's will have a nice red glowing phone when connectivity to google/msn etc is broken. Max Tulyev wrote: >> Last time I was a hosting proivider I signed up as a LIR and built my >> own network infrastructure to the nearest IX points. >> This time I have outrourced the lot and my 300 server serverfarm is >> behind a firewall on a handfull of IP addresses >>> Changing ISP is really easy? >> Yes. > > Stop. You have 10000 domains. You have IP address(es) from ISP A . > You are moving to ISP B with OTHER address(es). And you don't need to > send 10000 modify requests for these 10000 domains to change A (NS, > MX) records. Where is the magic? ;-) The same as the phone number system. One at a time. Or script your setup, you do know what 'management software' means do you? Look up the term ITIL or ASL once ;) With such a setup I suggest you outsource your "ISP" to the real ISP or plan ahead and become real good friends with your current ISP. You need a /28 and want "Provider Independence". I use a /28 at home. Lets say that I want "PI" too, that would mean I am going to get, pay for and maintain: - Multiple Redundant Routers - Multiple Redundant Links - Multiple Redundant Transits - Own 24/7 NOC (things will fail) - and a lot more... You are willing to do and pay for all that, but don't want to become an LIR? Nah, I rather let some real ISP handle all of that, they have the time to fiddle with peering and transit agreements, billing and all kinds of other time consuming things. Elmar K. Bins wrote: > Even to the risk of upsetting you... How can you calling yourself a 'fat-fingered jerk' upset me ? :) > These filters do not exist to blind out small PI assignments, they are > in place to remove accidental leakage of IGP prefixes caused by some > fat-fingered jerk like myself... So you filter on a /24 because of IGP, thus you will leak out a /23? Adding 8 or so prefixes doesn't really get noticed by many people, but adding 10k does. Filtering based on routing-DB information is thus much better than doing it based on some arbitrary limit. Greets, Jeroen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 238 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/ipv6-wg/attachments/20051201/7c3d6030/attachment.sig>
- Previous message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Next message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]