Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Cc: Bill Woodcock <woody@pch.net>, Nishal Goburdhan <nishal@pch.net>,
	Sara Alamin <sara@pch.net>
Subject: Re: [NNagain] are you Bill Woodcock?
Date: Fri, 19 Jan 2024 10:03:56 +0100	[thread overview]
Message-ID: <CAJUtOOige+kr1XnjEnjvK_ht_kzDO=4Zi8c=V9nDn4AfibE_-g@mail.gmail.com> (raw)
In-Reply-To: <CAJUtOOi1TsheU_1KnwJDp0Za8kqHXAzYe9uGPvg_yRDuuurq_g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4083 bytes --]

Btw, would it be possible to make it a Galene/Zoom link, available to join
in for public, so I can share it to bufferbloat-related, NANOG/NOG, etc
mailing lists?

I believe it would be helpful to awful lot of people!

All the best,

Frank
Frantisek (Frank) Borsik

https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com


On Fri, 19 Jan 2024 at 10:01 AM, Frantisek Borsik <
frantisek.borsik@gmail.com> wrote:

> Works for me.
>
>
> All the best,
>
> Frank
> Frantisek (Frank) Borsik
>
> https://www.linkedin.com/in/frantisekborsik
> Signal, Telegram, WhatsApp: +421919416714
> iMessage, mobile: +420775230885
> Skype: casioa5302ca
> frantisek.borsik@gmail.com
>
>
> On Fri, 19 Jan 2024 at 9:36 AM, Bill Woodcock via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
>
>> On Jan 19, 2024, at 05:38, le berger des photons via Nnagain wrote:
>> On 1/18/2024 6:14 PM, Bill Woodcock via Nnagain wrote:
>>
>> Do y’all (meaning folks on the list generally) want to just organize up a
>> video-call, to talk about how IXPs work, and address questions? I can
>> get a few of my other staff on the call, who’ve also dealt with a lot of
>> IXPs, and can add to my perspective.
>>
>>
>> yes,  I"m interested.  please do.
>>
>>
>> Ok.  I just checked with Sara and Nishal, and they can both do it next
>> Monday, the 22nd of January.  I don’t know where everyone is, but perhaps
>> the timeslot outlined in red, below, would inconvenience the fewest number
>> of people the least amount?  Maybe block out 90 minutes, start with some
>> background, and then move into discussion?  If I’m mis-reading the room
>> about where people are, let me know, and we could do it later in the day.
>>
>> *Tokyo*
>>
>> *Singapore*
>>
>> *Mumbai*
>>
>> *Dubai*
>>
>> *Johannesburg*
>>
>> *Paris*
>>
>> *London*
>>
>> *New York*
>>
>> *San Francisco*
>>
>> Mon 5:00 pm
>>
>> Mon 4:00 pm
>>
>> Mon 1:30 pm
>>
>> Mon 12:00 noon
>>
>> Mon 10:00 am
>>
>> Mon 9:00 am
>>
>> Mon 8:00 am
>>
>> Mon 3:00 am
>>
>> Mon 12:00 midnight
>>
>> Mon 6:00 pm
>>
>> Mon 5:00 pm
>>
>> Mon 2:30 pm
>>
>> Mon 1:00 pm
>>
>> Mon 11:00 am
>>
>> Mon 10:00 am
>>
>> Mon 9:00 am
>>
>> Mon 4:00 am
>>
>> Mon 1:00 am
>>
>> Mon 7:00 pm
>>
>> Mon 6:00 pm
>>
>> Mon 3:30 pm
>>
>> Mon 2:00 pm
>>
>> Mon 12:00 noon
>>
>> Mon 11:00 am
>>
>> Mon 10:00 am
>>
>> Mon 5:00 am
>>
>> Mon 2:00 am
>>
>> Mon 8:00 pm
>>
>> Mon 7:00 pm
>>
>> Mon 4:30 pm
>>
>> Mon 3:00 pm
>>
>> Mon 1:00 pm
>>
>> Mon 12:00 noon
>>
>> Mon 11:00 am
>>
>> Mon 6:00 am
>>
>> Mon 3:00 am
>>
>> Mon 9:00 pm
>>
>> Mon 8:00 pm
>>
>> Mon 5:30 pm
>>
>> Mon 4:00 pm
>>
>> Mon 2:00 pm
>>
>> Mon 1:00 pm
>>
>> Mon 12:00 noon
>>
>> Mon 7:00 am
>>
>> Mon 4:00 am
>>
>> Mon 10:00 pm
>>
>> Mon 9:00 pm
>>
>> Mon 6:30 pm
>>
>> Mon 5:00 pm
>>
>> Mon 3:00 pm
>>
>> Mon 2:00 pm
>>
>> Mon 1:00 pm
>>
>> Mon 8:00 am
>>
>> Mon 5:00 am
>>
>> Mon 11:00 pm
>>
>> Mon 10:00 pm
>>
>> Mon 7:30 pm
>>
>> Mon 6:00 pm
>>
>> Mon 4:00 pm
>>
>> Mon 3:00 pm
>>
>> Mon 2:00 pm
>>
>> Mon 9:00 am
>>
>> Mon 6:00 am
>>
>> Tue 12:00 midnight
>>
>> Mon 11:00 pm
>>
>> Mon 8:30 pm
>>
>> Mon 7:00 pm
>>
>> Mon 5:00 pm
>>
>> Mon 4:00 pm
>>
>> Mon 3:00 pm
>>
>> Mon 10:00 am
>>
>> Mon 7:00 am
>>
>> Tue 1:00 am
>>
>> Tue 12:00 midnight
>>
>> Mon 9:30 pm
>>
>> Mon 8:00 pm
>>
>> Mon 6:00 pm
>>
>> Mon 5:00 pm
>>
>> Mon 4:00 pm
>>
>> Mon 11:00 am
>>
>> Mon 8:00 am
>>
>> Tue 2:00 am
>>
>> Tue 1:00 am
>>
>> Mon 10:30 pm
>>
>> Mon 9:00 pm
>>
>> Mon 7:00 pm
>>
>> Mon 6:00 pm
>>
>> Mon 5:00 pm
>>
>> Mon 12:00 noon
>>
>> Mon 9:00 am
>>
>>                                 -Bill
>>
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
>>
>

[-- Attachment #2: Type: text/html, Size: 61247 bytes --]

  reply	other threads:[~2024-01-19  8:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 21:51 le berger des photons
2024-01-18 22:38 ` Bill Woodcock
2024-01-19  1:56   ` Dick Roy
2024-01-19  2:14     ` Bill Woodcock
2024-01-19  3:03       ` Dick Roy
2024-01-19  3:12       ` Dave Crocker
2024-01-19  4:38         ` le berger des photons
2024-01-19  8:36           ` Bill Woodcock
2024-01-19  9:01             ` Frantisek Borsik
2024-01-19  9:03               ` Frantisek Borsik [this message]
2024-01-19 11:38             ` le berger des photons
2024-01-19 20:18               ` rjmcmahon
2024-01-21 19:08                 ` Joe Williams
2024-01-21 23:14             ` Bill Woodcock
2024-01-23  9:06               ` le berger des photons
2024-01-23  9:23                 ` Frantisek Borsik
2024-01-19  7:14   ` Sebastian Moeller
2024-01-19  7:26     ` Bill Woodcock
2024-01-19  7:51       ` Frantisek Borsik

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/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJUtOOige+kr1XnjEnjvK_ht_kzDO=4Zi8c=V9nDn4AfibE_-g@mail.gmail.com' \
    --to=frantisek.borsik@gmail.com \
    --cc=nishal@pch.net \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=sara@pch.net \
    --cc=woody@pch.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