From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Fwd: [116attendees] Side meeting for Satellite networking tomorrow
Date: Mon, 27 Mar 2023 11:03:02 +0200 [thread overview]
Message-ID: <4344EA6C-B667-4A92-A6DD-B0BD2BE695E7@gmx.de> (raw)
In-Reply-To: <BY5PR13MB3144FD0B52E1279612C2460DE98B9@BY5PR13MB3144.namprd13.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
Saw this in the IETF-116 Mailing list.
Might be interesting to some here (though most will likely know this already).
Regards
Sebastian
> Begin forwarded message:
>
> From: Lin Han <lin.han@futurewei.com>
> Subject: [116attendees] Side meeting for Satellite networking tomorrow
> Date: March 27, 2023 at 09:20:06 GMT+2
> To: "116attendees@ietf.org" <116attendees@ietf.org>, "EToSat@ietf.org" <etosat@ietf.org>, "tvr@ietf.org" <tvr@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
>
>
> Hi,
>
> We will have side meeting for satellite networking tomorrow, Mar. 28, Tuesday, from 11:00AM to 12:30PM local time, in the room G301.
> If you are interested in the similar works, pls join us to discuss.
>
> For the details of the meeting, see https://github.com/lh95129/IETF-116-satellite-network-side-meeting.
> All slides are uploaded in https://github.com/lh95129/IETF-116-satellite-network-side-meeting/tree/main/Materials
>
> The zoom meeting info is:
> Zoom link: https://futurewei.zoom.us/j/7743893573?pwd=YjJ1cnpIb1VhakVSeVg0UFVmcmlIQT09
> Meeting ID: 774 389 3573
> Passcode: sat123
>
> Regards
>
> Lin
>
>
> --
> 116attendees mailing list
> 116attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/116attendees
[-- Attachment #2: Type: text/html, Size: 4307 bytes --]
parent reply other threads:[~2023-03-27 9:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BY5PR13MB3144FD0B52E1279612C2460DE98B9@BY5PR13MB3144.namprd13.prod.outlook.com>]
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=4344EA6C-B667-4A92-A6DD-B0BD2BE695E7@gmx.de \
--to=moeller0@gmx.de \
--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