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: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
- 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 ]
Nick Hilliard
nick at netability.ie
Fri Mar 29 21:46:11 CET 2013
On 29/03/2013 20:16, Richard Hartmann wrote: > 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. > RIPE-PDP-YYYY-NN will always refer to the most up to date version of the PDP. > 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. Does this need to be a policy? Could we not just ask the RIPE NCC kindly to implement this rather than spending the next 6 months arguing, nodding sagely or violently disagreeing about this? This is an operational detail; nothing to do with policy. Nick
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
- 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 ]