From: David Collier-Brown <davec-b@rogers.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Fwd: Intended BUFFERBLOAT FREE AND CONGESTION RESILIENT SATCOM NETWORKS (ARTES AT 6B.129)
Date: Thu, 12 Dec 2024 11:04:25 -0500 [thread overview]
Message-ID: <2f67ef80-b00e-4f59-aa73-bb88361b7039@rogers.com> (raw)
In-Reply-To: <CAC=tZ0pJJPCnJRcW43y1j_Dp5gZta4HHG72eWhEX+O_SwgSfYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
If you have a partner or presence in Canada, you can apply.
--dave
On 12/12/24 10:37, David Fernández via Starlink wrote:
> Well, EU and a bit more, like CA and GB.
>
> *Open To Tenderers From*
> AT+BE+CA+CH+CZ+DE+DK+GR+ES+FI+FR+GB+HU+IE+IT+LU+NL+NO+PL+PT+RO+SE
>
>
> On Thu, 12 Dec 2024 at 16:21, Dave Taht <dave.taht@gmail.com> wrote:
>
> Oh darn, it is eu only.
>
> On Thu, Dec 12, 2024 at 6:41 AM Dave Taht <dave.taht@gmail.com> wrote:
> >
> > That made my day, thank you.
> >
> > On Thu, Dec 12, 2024 at 6:17 AM David Fernández via Starlink
> > <starlink@lists.bufferbloat.net> wrote:
> > >
> > > Issued, with the following closing date: 13/03/2025 13:00:00
> > >
> https://esastar-publication-ext.sso.esa.int/ESATenderActions/details/75587
> > >
> > > ---------- Forwarded message ---------
> > > From: David Fernández <davidfdzp@gmail.com>
> > > Date: Tue, 10 Dec 2024 at 15:31
> > > Subject: Fwd: Intended BUFFERBLOAT FREE AND CONGESTION
> RESILIENT SATCOM NETWORKS (ARTES AT 6B.129)
> > > To: starlink <starlink@lists.bufferbloat.net>
> > >
> > >
> > > Updated:
> > >
> https://esastar-publication-ext.sso.esa.int/ESATenderActions/details/75587
> > >
> > > ---------- Forwarded message ---------
> > > From: David Fernández <davidfdzp@gmail.com>
> > > Date: Mon, 6 May 2024 at 12:42
> > > Subject: Intended BUFFERBLOAT FREE AND CONGESTION RESILIENT
> SATCOM NETWORKS (ARTES AT 6B.129)
> > > To: starlink <starlink@lists.bufferbloat.net>
> > >
> > >
> > > Dear all,
> > >
> > > You may express your interest on this:
> > >
> https://esastar-publication-ext.sso.esa.int/ESATenderActions/details/75587
> > >
> > > Regards,
> > >
> > > David F.
> > > _______________________________________________
> > > Starlink mailing list
> > > Starlink@lists.bufferbloat.net
> > > https://lists.bufferbloat.net/listinfo/starlink
> >
> >
> >
> > --
> > Dave Täht CSO, LibreQos
>
>
>
> --
> Dave Täht CSO, LibreQos
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 6836 bytes --]
next prev parent reply other threads:[~2024-12-12 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:42 [Starlink] " David Fernández
2024-12-10 14:31 ` [Starlink] Fwd: " David Fernández
2024-12-12 14:17 ` David Fernández
2024-12-12 14:41 ` Dave Taht
2024-12-12 14:42 ` David Fernández
2024-12-12 15:21 ` Dave Taht
2024-12-12 15:37 ` David Fernández
2024-12-12 16:04 ` David Collier-Brown [this message]
2024-12-12 23:07 ` Brandon Butterworth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f67ef80-b00e-4f59-aa73-bb88361b7039@rogers.com \
--to=davec-b@rogers.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox