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/[email protected]/
[routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Previous message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Next message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Thu Oct 11 21:41:09 CEST 2018
In message <E1gAaoe-0004fx-GZ at www-apps-1.ripe.net>, Marco Schmidt <mschmidt at ripe.net> wrote: >https://www.ripe.net/participate/policies/proposals/2018-06 Two comments: 1) In section 2.0 please change the word "must" to "will". 2) Please append the following additional sentence to section 2.0: A permanent record of all route objects deleted from the RIPE IRR as a result of this policy, together with copies of all then-current referenced database objects, at the time of the deletion will be maintained and published by RIPE NCC, either via a simple plain text web page or as plain text provided to the public via some other means (e.g. a traditional port 43 WHOIS service), (I believe that all details relating to this clean-up should be preserved for posterity and should be easily accessible to both current and future researchers and historians.)
- Previous message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
- Next message (by thread): [routing-wg] 2018-06 New Policy Proposal (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]