<div dir="ltr"><div class="gmail_default" style="font-size:small">See inline comments.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">--<br>Brian</div></div>
<br><div class="gmail_quote">On Tue, Apr 24, 2018 at 12:29 PM, Owen DeLong <span dir="ltr"><<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
> On Apr 24, 2018, at 08:35 , Gert Doering <<a href="mailto:gert@space.net">gert@space.net</a>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> On Tue, Apr 24, 2018 at 10:56:06AM -0400, William Herrin wrote:<br>
>> On Tue, Apr 24, 2018 at 8:23 AM, Gert Doering <<a href="mailto:gert@space.net">gert@space.net</a>> wrote:<br>
>>> On Tue, Apr 24, 2018 at 08:21:36AM -0400, ARIN wrote:<br>
>>>> * Question: Should attachments be prohibited on ARIN public<br>
>>>> mailing lists?<br>
>>> <br>
>>> I do not have a particular opinion on that, but *if* you disallow attachments,<br>
>>> please make it smart enough to not break PGP-signed mails in MIME format<br>
>>> (which come with an "attachment" for the signature) in the process.<br>
>> <br>
>> Hi Gert,<br>
>> <br>
>> "Not break" as in maintain the signature or "not break" as in don't<br>
>> strip the signature and then keep the multipart/signed content-type<br>
>> breaking the validator?<br>
> <br>
> "do not fumble with mail that is PGP signed", not in any way. <br>
> <br>
> Do not modify the body, those header parts that are covered by the <br>
> signature, or the signature itself, or the MIME structure tieing parts<br>
> together.<br>
<br>
</span>What you are effectively arguing for here is “Allow attachments as long<br>
as the message at least pretends to be PGP signed.”<br>
<br>
If we’re going to block attachments, then we should do so.<br></blockquote><div><br><div style="font-size:small" class="gmail_default">+1</div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If not, then I’m fine with that.<br></blockquote><div> </div><div style="font-size:small" class="gmail_default">+1 <br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
However, in deference to the PGP signed aficionados, I would suggest that<br>
we pass (unaltered) any PGP signed message which contains only text/plain,<br>
text/ascii, text/rtf, and PGP-related MIME parts. For others, we should<br>
return an error message to the poster explaining that attachments are not<br>
allowed, but PGP signatures are still permitted.<br>
<span class="HOEnZb"><font color="#888888"><br>
Owen<br></font></span></blockquote><div><br><div style="font-size:small" class="gmail_default">Does discussion conducted on ARIN public lists need to be PGP signed?</div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
</font></span><span class="im HOEnZb"><br>
> <br>
>> Personally, I wouldn't mind seeing all emails squashed to a single<br>
>> MIME text/plain part. It might even improve the quoting mess where a<br>
>> lot of mail software can't figure out how to mark the components of<br>
>> the mail or sometimes indents an entire paragraph unwrapped instead of<br>
>> indenting the lines.<br>
> <br>
> I would totally second *that* :-) - but I'm afraid that was not the<br>
> question asked.<br>
> <br>
> Gert Doering<br>
> -- NetMaster<br>
> -- <br>
> have you enabled IPv6 on something today...?<br>
> <br>
> SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer<br>
> Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann<br>
> D-80807 Muenchen HRB: 136055 (AG Muenchen)<br>
> Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279<br>
</span><div class="HOEnZb"><div class="h5">> ______________________________<wbr>_________________<br>
> ARIN-Consult<br>
> You are receiving this message because you are subscribed to the ARIN Consult Mailing<br>
> List (<a href="mailto:ARIN-consult@arin.net">ARIN-consult@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="http://lists.arin.net/mailman/listinfo/arin-consult" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-consult</a> Please contact the ARIN Member Services<br>
> Help Desk at <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
<br>
______________________________<wbr>_________________<br>
ARIN-Consult<br>
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br>
List (<a href="mailto:ARIN-consult@arin.net">ARIN-consult@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-consult</a> Please contact the ARIN Member Services<br>
Help Desk at <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
</div></div></blockquote></div><br></div></div>