[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 ]
Gerry Demaret
ml+ripe-list at x-net.be
Sat Mar 16 14:35:25 CET 2013
On 03/15/2013 08:12 PM, 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. > 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. +1 I actually had the exact same thought a few weeks ago, so I guess it wouldn't be a bad thing. > 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. I'm not a fan of this alternative. Embedding the WG's name would make the names longer and would mean that either the YYYY-NN part would need to remain globally unique in the RIPE-PDP-* namespace or it wouldn't. Both options could cause confusion since: * RIPE-PDP-APWG-2013-01 and RIPE-PDP-APWG-2013-03 could exist, but perhaps RIPE-PDP-APWG-2013-02 not. I might spend useless time looking for a document that never existed. * Both RIPE-PDP-APWG-2013-01 and RIPE-PDP-AAWG-2013-01 would exist. It might be just me, but those strings confuse my brain. I would prefer to stick with RIPE-PDP-2013-01. Gerry
- 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 ]