> In this draft it has some requirements for generating ULA-C prefixes and > then in 7.0 it requires the RIRs to publish an RFC documenting how they > will implement these requirements.
I don't think the RIRs necessarily need to publish an RFC. The main point is for the RIRs to have sufficiently documented what they propose to do so that everyone is happy with proposal and it's written down somewhere. The details of exactly what documentation is sufficient can be discussed and shouldn't become a rathole relative to the bigger question of whether ULA-C shold go forward at all. > But a better way is for the ULA-C document to include this. Well, one thing to balance here is the part the IETF specifies and the part the RIRs specify (in terms of operational policy). Putting it all in one document complicates that and might result in the some of the text appearing to come from the IETF (and the IETF then being authoritative) rather than the RIRs. I don't think we want that either. > I note that any algorithm for checking (and registering) a generated > prefix in the 5 RIR databases could easily be done in advance so > that each RIR keeps a supply of unique ULA-C prefixes on hand based > on their forecast rate of requests for such addresses. There are lots of ways of achieving uniqueness. One thing the authors discussed quite a bit (with rough consensus at best!) was to what degree the operational details of how to carry out the proposal should be specified in this ID. Personally, I'd rather see less detail in the IETF document, with it concentrating on the desired/required properties of ULA-Cs. Presumably, if we define the properties clearly/properly, how they are produced operationally would be a detail and not really our concern, i.e., so long as the desired properties are preserved. Thomas -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
