On Thu, Oct 23, 2014 at 03:37:23PM +0200, Marco Schmidt wrote:
A proposed change to RIPE Document "IPv6 Addresses for Internet Root Servers In The RIPE Region" is now available for discussion.
1) the motivating pointer to RFC 2119 is misguided. RIPE documents do not make a reference to RFC 2119 in general and even less so in this particular case. There's already enough confusion in the IETF with "must" vs "MUST", i.e., when keywords do and don't bear their special meaning. 2) the change is unnecessary and does not provide clarification. The text is already clearly stating that assigned address space stays with the service and will (have to) be returned to the RIPE NCC if the service is terminated. A "should" is sufficient. 3) The status of ripe-233, especially in the light of the omnibus document ripe-623 is probably a bit vague. ripe-233 exists for historic reference, therefore any change applied by this proposal would retroactively try to change the rule for past assignments with no new assignments to be expected (for lack of policy). 4) Issuing a new document with a new timestamp is likely to cause more confusion than it strives to solve (lacking sth equivalent to a "Historic" document status and/or explanatory introductory text in the updated document). Resolved, no support -Peter