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/[email protected]/
[ncc-services-wg] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
- Previous message (by thread): [ncc-services-wg] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
- Next message (by thread): [ncc-services-wg] RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrey Semenchuk
andrey at trifle.net
Thu Jan 3 15:04:41 CET 2013
Sascha Luck wrote: > On Thu, Jan 03, 2013 at 02:13:33PM +0100, Shane Kerr wrote: >> An alternate approach would be for the RIPE NCC to act as a go-between >> for communicating with resource holders. > > Not that I dislike the idea but, considering automated antispam > bitching, that might be a DDoS vector ;) ... and ff the DDoS occurs in this situation, it should be prevented as the any other DDoS -- Best wishes, Andrey Semenchuk Trifle Internet Service Provider (056) 731-99-11 www.trifle.net
- Previous message (by thread): [ncc-services-wg] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
- Next message (by thread): [ncc-services-wg] RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]