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/ncc-services-wg@ripe.net/
[ncc-services-wg] Pre-PDP discussion: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Fri Mar 15 20:12:38 CET 2013
Dear all, this is the second suggestion: The canonical name of all PDPs will be RIPE-PDP-YYYY-NN. Updated versions will receive suffixes like Internet Drafts, i.e. -v1, -v2, -v3. Old-style PDP names of the format YYYY-NN will remain valid, but all new documentation and communication by RIPE will use the new format. Alternatively, the name of the Working Group may be embedded in all names, e.g. RIPE-PDP-APWG-YYYY-NN, or RIPE-APWG-PDP-YYYY-NN. Rationale should again be obvious: Encoding information in names is good practice. Unique names make life easier for everyone involved. If other RIRs follow suit, cross-referencing becomes easier. Rationale for keeping "PDP" in the WG option is because a WG may want to publish something other than a PDP at some point. The alternatives should be decided upon during the discussion phase of the PDP. Richard
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]