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/
[address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
- Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
- Next message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Mon Nov 14 18:01:46 CET 2005
Hi, On Mon, Nov 14, 2005 at 10:51:58AM +0100, Jørgen Hovland wrote: > > You try to decide here how > > other people run their services. > > No, I am trying to prevent excessive defragmentation of the routing table. I > am trying to prevent a special case of PI where you are not even required to > have your own network. The requirement to this special PI case is so low > that anyone would be able to apply for it - and anyone _will_ apply for it. > In order to prevent that we only permit DNS? Are there any other services > that should be permitted? This is the type of argument that I love most - "if we permit this to you, everybody will want it, too!!!". I read into this that you are afraid that the initial criteria are not strict enough. As far as I can see, the criteria are pretty explicit, and verificable. [..] > >DNS is a special service (UDP packet size stuff) and needs a special > >solution - unfortunately. > > I disagree. DNS is certainly not a special service. The importance of it is > however perhaps greater than many others - many, but far from all. > The packet size thing is a general design problem. As far as I know, there > are currently two methods to solve it: > > * EDNS0 > * TC flag > > If you are going to use the packet size problem as an argument to use > anycast, then I think it would be a good idea to hear reasons why none of > these solutions would be suitable (also because I don't really know it > myself) and perhaps if there are any other solutions that would help solving > the problem? Please. We have been through this part of the discussion half a year ago, and we've asked those that know (the DNS WG) and they tell us "we can't rely on EDNS0, and truncation is bad". It would be very helpful if you could do us the favour and read up on old arguments in the archives. To repeat myself: it's not the AP WG's job to tell the DNS WG how DNS works. We're making policy, (partly) based on the expertise of other working groups. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 81421 SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 D- 80807 Muenchen Fax : +49-89-32356-234
- Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
- Next message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]