[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 ]
Daniel Roesen
dr at cluenet.de
Mon Mar 18 10:23:05 CET 2013
On Sat, Mar 16, 2013 at 03:20:31PM +0000, Alex Le Heux wrote: > I think that overloading the name in such a way is only useful if both > 2014-86-APWG and 2014-86-NCCSERVICES are possible. If the serial number of > a proposal is unique across the different working groups, I don't see a > need to include the WG in the name. I find the proposal to be very good, and agree with Alex that no WG should be included, if the serial number is unique anyway. > Otherwise we should also consider including things like the name of the > proposer, current stage of the PDP it is in, version, etc, etc :) Don't forget shoe size. :) Best regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0
- 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 ]