28 May
2013
28 May
'13
4:04 p.m.
On 5/28/13 3:26 PM, Merike Kaeo wrote:
Jan has approached me a few times to see about helping edit a newer version and I am OK with that as long as there are enough changes to warrant a completely new document. We don't want to turn out a new RIPE doc every time one new v6 related RFC is published but certainly we should keep track of enhancements and modifications on best practices as deployments continue and then turn out a new document (and obsolete previous one(s)).
Hey, We can wait until the list of big-change suggestions grows big enough that it makes sense to change the document and the number. <joke>(...or we simply wait for RIPE-666 number and change it then :) :) :) )</joke> Cheers, Jan