[Tools-discuss] Re: Be careful when sending images to the list

[Brian E Carpenter <[e-mail]>]

On 27-Jul-24 07:30, Eric Rescorla wrote:
> 
> 
> On Fri, Jul 26, 2024 at 11:40 AM Nicolas Giard <[e-mail] <mailto:[e-mail]>> wrote:
> 
>     Hi Eric,
> 
>     We will use SES soon, but we are not at the moment.
> 
>     However, mail still needs to be processed before submitted to SES for distribution.
>     This processing uses CPU/RAM resources and bandwidth between the compute and SES endpoints.
> 
>     There's also an additional cost to sending attachments, which SES charges per GB (in addition to the per email cost).
> 
>     So yes there are actual costs to embedding images versus just linking to them.
> 
> 
> Yes, I'm asking what those costs are, so that I can get a sense of whether they are material.

If we're really going to discuss this, how many IETF participants still face volume charges or low data caps from their ISPs? Large attachments may hurt such participants.

I thought Robert's original request was very reasonably phrased and left plenty of scope for individual decisions.

    Brian

> 
> -Ekr
> 
> 
>     Nick
> 
>     On Fri, Jul 26, 2024 at 1:31 PM Eric Rescorla <[e-mail] <mailto:[e-mail]>> wrote:
> 
>         In Fri, Jul 26, 2024 at 8:55 AM Robert Sparks <[e-mail] <mailto:[e-mail]>> wrote:
> 
>             Mostly its in the time it takes to hand the larger message off to each recipients next MTA and the bandwidth that consumes. This competes with other traffic to other lists. 
> 
> 
>         I thought we were using SES, in which case isn't it Amazon's bandwidth? Surely they have plenty.
> 
>         -Ekr
> 
> 
>             Until recently it also competed with handling web services requests, but we’ve (almost) separated those concerns.
> 
> 
>             Sent from my iPhone
> 
>>             On Jul 26, 2024, at 6:27 AM, Eric Rescorla <[e-mail] <mailto:[e-mail]>> wrote:
>>
>>             
>>             On Thu, Jul 25, 2024 at 10:44 AM Robert Sparks <[e-mail] <mailto:[e-mail]>> wrote:
>>
>>                 All -
>>
>>                 When sending images, think about the size, and the cost of sending a
>>                 large thing back out to a large number of subscribers. If you need to
>>                 provide a large image, consider using a link one of the many websites
>>                 available for such things.
>>
>>                 When replying to a message with a large image, consider trimming the
>>                 image from the reply.
>>
>>                 Please don't read this as saying "don't send images" - they can be very
>>                 useful, especially on this list. The point is to think about the best
>>                 way to get the images to the list recipients.
>>
>>
>>             Can you provide some sense of the incremental cost to the IETF here? I'm
>>             trying to understand whether it's material.
>>
>>             -Ekr
>>
>         -----------------------------------------------
>         Tools-discuss mailing list -- [e-mail] <mailto:[e-mail]>
>         To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
>         https://mailarchive.ietf.org/arch/browse/tools-discuss/ <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
> 
> 
> -----------------------------------------------
> Tools-discuss mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> https://mailarchive.ietf.org/arch/browse/tools-discuss/