On Wed, Jan 06, 2016 at 06:08:07PM +0100, Peter Palfrader wrote: > Martin Zobel-Helas schrieb am Mittwoch, dem 06. Jänner 2016: > > > Hi, > > > > On Wed Jan 06, 2016 at 13:55:31 +0000, Marcin Kulisz wrote: > > > If this mirror is not intended to be used by public outside Azure I'm not > > > really convinced that it should be available under debian.org domain for simple > > > reason service is not (and probably not going to be) under DSA control. > > > > with my DSA hat on: none of the mirrors under ftp.CC.debian.org are > > under DSA control. Some of the mirrors might be administrated by > > individual members of the DSA team, but none is official under DSA > > control. > > Yes, but this isn't one of those. > > Hosters usually have their http://mirror.$hoster/, such as > http://mirror.nl.leaseweb.net/debian/. > > I do not see why this should be under .debian.org if it's not intended > for the general public. Having something under mirrors.azure or > whatever this is called seems perfectly reasonable. The original posting had this text: } The remaining question is where service names for such mirrors, not only } in Azure but possibly also in other cloud infrastructures, should reside } within the debian.org zone. } } As we now have "debian.mirrors.debian.org", I would think about } "$vendor.mirrors.debian.org" and, if they really want to mirror debug, } also "debug.$vendor.mirrors.debian.org". But I'm open to suggestions. For some reason I do read a deeper idea in it. Such as "If we provide '$vendor.mirror.debian.org DNS stuff', then we can do smart things like .... " Is it? Groeten Geert Stappers -- Leven en laten leven
Attachment:
signature.asc
Description: Digital signature