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/bcop@ripe.net/
[bcop] Proposal for a new BCOP document...
- Previous message (by thread): [bcop] RIPE-690 BCOP is now published...
- Next message (by thread): [bcop] Proposal for a new BCOP document...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Zorz - Go6
jan at go6.si
Mon Oct 16 16:19:10 CEST 2017
Dear BCOP TF community, Now when we are finished with this IPv6 prefix delegations BCOP, I would like to suggest a new topic for a new document. While traveling around the world and talking to operators - another quite generic complaint formed up as quite a popular one: "I'm running email server on IPv4, because anti-spam mechanisms works quite well on IP-reputation basis, but on IPv6 there is no such thing, therefore I'm not enabling my receiving email server on IPv6" Sooo... let's join in an effort to document the best current operational practices how to effectively run your email server op IPv6 and survive. I'm asking for volunteers here on this mailing list and I'll ask for volunteers at our Dubai meeting. We need people with operational experience running a receiving email servers on IPv6 to document the best ways how to do it. Any takers? Cheers and see you all in Dubai, Jan -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3976 bytes Desc: S/MIME Cryptographic Signature URL: </ripe/mail/archives/bcop/attachments/20171016/51b6b6d0/attachment.p7s>
- Previous message (by thread): [bcop] RIPE-690 BCOP is now published...
- Next message (by thread): [bcop] Proposal for a new BCOP document...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ BCOP Archives ]