On 30/11/2012, at 10:41 AM, Pete Resnick <presnick@xxxxxxxxxxxxxxxx> wrote: > Like Randy, I am completely agnostic on the question of dividing the registries vs. adding an attribute to the registries to distinguish between reservations and other special uses. But one comment on the other item in your message: > > On 11/29/12 4:26 PM, Geoff Huston wrote: > >> I also disagree with the approach to publish the intended contents of this special purpose registry as an RFC ans the registry itself is the intended mode of authoritatively describing those resources that have been assigned for special purposes. Obviously any RFC will age out and drift away from the registry, and the need to constantly publish updating RFCs to ensure that the latest RFC is reasonably close to the registry contents seems to me to be counter-productive at best. >> > > I think (hope) you've misinterpreted this. The document serves two purposes: To define the registries (section 2.1, which is really the BCPish part of this document) And I was saying that I would prefer to see protocol address plan reservations not be included in the special purpose registry. > and to populate the registries with initial values (sections 2.2 and 2.3). Some time ago there was value in this "initial population" concept to sort some of the claims of special purpose address assignments, but I thought that we were over it and the draft restates what is already n the registry. > 2.1 is the real content of the documentthat will live on, get updated, etc., whereas 2.2 and 2.3 are probably better as an appendix, and I don't think there's any expectation that those sections ought to be kept up to date with future RFCs to match the registry. (Indeed, it might be nice if 2.2 and 2.3 were removed before publication, but that's not been our practice.) Personally the removal before publication of the registry contents would be something I would support. > > Does that allay your concern? > no - as I would prefer to see protocol address plan reservations not be included in the special purpose registry. The IPv4 address plan reservations appear to be 0/8, 127/8 and 240/4. The others appear to be various forms of special prupose assignments. In IPv6 I see reservations for ::1/128, ::/128 as far as I can tell - the remainder are reasonably seen as Special Purpose Assignments I would suggest. regards, Geoff