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/dns-wg@ripe.net/
[dns-wg] Followup to IANA TLD delegation problem
- Previous message (by thread): [dns-wg] Followup to IANA TLD delegation problem
- Next message (by thread): [dns-wg] Followup to IANA TLD delegation problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jaap Akkerhuis
jaap at NLnetLabs.nl
Thu Jun 23 10:35:59 CEST 2005
I do not think they answer the concerns I have. As Jim has said: >Aside from his observations, the >list has been silent. So the WG should now consider this discussion closed. It is not silent since I rose these points. Political decisions may result from this, this is why I would have prefered to be exhaustive and fair. But I do not understand your political layer: now we discuss source code and operational procedures. There has been no discussion. >[Authors of drafts will typically circulate them to colleagues for >feedback before they get published.] This is a BCP based upon three years of work and test by an independent organisation (IETF was not interested). What is reported here is more experimental than operational. Hence my interest. Why don't you just publish it? I only see it mentioned by you on various mailing lists, but the actual thing never surfaced. jaap
- Previous message (by thread): [dns-wg] Followup to IANA TLD delegation problem
- Next message (by thread): [dns-wg] Followup to IANA TLD delegation problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]