BPF List
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>,
	"bpf\@vger.kernel.org" <bpf@vger.kernel.org>,
	"bpf\@ietf.org" <bpf@ietf.org>
Subject: Re: [Bpf] IETF 118 Call for Agenda Items
Date: Sat, 04 Nov 2023 11:52:30 +0100	[thread overview]
Message-ID: <3448856.1699095150@dyas> (raw)
In-Reply-To: <PH7PR21MB38787378F01B057C9FF7D25BA3A4A@PH7PR21MB3878.namprd21.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1727 bytes --]


Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org> wrote:
    >> -----Original Message----- From: David Vernet <void@manifault.com>
    >> Sent: Monday, October 9, 2023 7:09 PM To: bpf@ietf.org Cc:
    >> bpf@vger.kernel.org; bpf-chairs@ietf.org; Erik Kline
    >> <ek.ietf@gmail.com>; Suresh Krishnan <suresh.krishnan@gmail.com>
    >> Subject: IETF 118 Call for Agenda Items
    >>
    >> Hello,
    >>
    >> The BPF working group will be holding a meeting at IETF 118 in a two
    >> hour time slot. The chairs are in the process of setting the
    >> agenda. We would like to solicit agenda items that would be of
    >> interest to the WG participants with a preference to the items that
    >> address the topics of interest covered by the charter. Please send us
    >> your request(s) for slots to bpf-chairs@ietf.org, detailing:
    >>
    >> * Topic and presenter info * Name of associated draft (if any) *
    >> Requested slot duration
    >>
    >> Thanks Suresh and David

    > Just wanted to remind everyone that the BPF working group meeting is
    > coming up on Monday 2023-11-06 09:30-11:30 CET (yes that's 1:30am US
    > Pacific time), and anyone who registers can participate online.

1:30am US PST on Monday morning, which many of us think of as being late
Sunday night.  So don't get the day wrong, use a computer calendering program.

    > Registration: https://registration.ietf.org/118/ Online day pass for
    > Monday is $140 USD or $55 for students.

And there are fee waivers available, and for remote speakers, chairs can get single
session logins.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*




[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

[-- Attachment #2: Type: text/plain, Size: 76 bytes --]

-- 
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf

WARNING: multiple messages have this Message-ID (diff)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>,
	"bpf\@vger.kernel.org" <bpf@vger.kernel.org>,
	"bpf\@ietf.org" <bpf@ietf.org>
Subject: Re: [Bpf] IETF 118 Call for Agenda Items
Date: Sat, 04 Nov 2023 11:52:30 +0100	[thread overview]
Message-ID: <3448856.1699095150@dyas> (raw)
Message-ID: <20231104105230.570RGCBDb9MpwxdQWTnyZJXksEOQfx48GPiXKd-xr9c@z> (raw)
In-Reply-To: <PH7PR21MB38787378F01B057C9FF7D25BA3A4A@PH7PR21MB3878.namprd21.prod.outlook.com>

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


Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org> wrote:
    >> -----Original Message----- From: David Vernet <void@manifault.com>
    >> Sent: Monday, October 9, 2023 7:09 PM To: bpf@ietf.org Cc:
    >> bpf@vger.kernel.org; bpf-chairs@ietf.org; Erik Kline
    >> <ek.ietf@gmail.com>; Suresh Krishnan <suresh.krishnan@gmail.com>
    >> Subject: IETF 118 Call for Agenda Items
    >>
    >> Hello,
    >>
    >> The BPF working group will be holding a meeting at IETF 118 in a two
    >> hour time slot. The chairs are in the process of setting the
    >> agenda. We would like to solicit agenda items that would be of
    >> interest to the WG participants with a preference to the items that
    >> address the topics of interest covered by the charter. Please send us
    >> your request(s) for slots to bpf-chairs@ietf.org, detailing:
    >>
    >> * Topic and presenter info * Name of associated draft (if any) *
    >> Requested slot duration
    >>
    >> Thanks Suresh and David

    > Just wanted to remind everyone that the BPF working group meeting is
    > coming up on Monday 2023-11-06 09:30-11:30 CET (yes that's 1:30am US
    > Pacific time), and anyone who registers can participate online.

1:30am US PST on Monday morning, which many of us think of as being late
Sunday night.  So don't get the day wrong, use a computer calendering program.

    > Registration: https://registration.ietf.org/118/ Online day pass for
    > Monday is $140 USD or $55 for students.

And there are fee waivers available, and for remote speakers, chairs can get single
session logins.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

  parent reply	other threads:[~2023-11-04 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 17:08 IETF 118 Call for Agenda Items David Vernet
2023-10-09 17:08 ` [Bpf] " David Vernet
2023-11-04 10:17 ` Dave Thaler
2023-11-04 10:17   ` [Bpf] " Dave Thaler
2023-11-04 10:52   ` Michael Richardson [this message]
2023-11-04 10:52     ` Michael Richardson

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

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

  git send-email \
    --in-reply-to=3448856.1699095150@dyas \
    --to=mcr+ietf@sandelman.ca \
    --cc=bpf@ietf.org \
    --cc=bpf@vger.kernel.org \
    --cc=dthaler=40microsoft.com@dmarc.ietf.org \
    /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