From: rhanley@google.com
To: openbmc@lists.ozlabs.org, neladk@microsoft.com
Subject: Invitation: BMC Aggregator Presentation Layer @ Thu Feb 6, 2020 10am - 11am (PST) (openbmc@lists.ozlabs.org)
Date: Wed, 29 Jan 2020 23:59:22 +0000 [thread overview]
Message-ID: <0000000000002b849a059d50210d@google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2097 bytes --]
You have been invited to the following event.
Title: BMC Aggregator Presentation Layer
Sorry for the delay in putting together this follow up meeting.
We made some progress in hashing out some of the requirements of a BMC
aggregator in our last meeting.
However, one of the issues that needs more discussion is what features are
needed in a presentation layer for this aggregator.
I think this discussion is one of the biggest blockers before we can
trading any designs, and I look forward to hearing about any use cases that
people are considering.
(P.S. I will be creating a second meeting that is more amenable to Asian
timezones)
When: Thu Feb 6, 2020 10am – 11am Pacific Time - Los Angeles
Where: SVL-MAT3-4-Saturn (5) [GVC]
Joining info: Join Hangouts Meet
https://meet.google.com/fzh-kuvi-wqo
Join by phone
+1 406-686-3826 (PIN: 214092)
More phone numbers: https://tel.meet/fzh-kuvi-wqo?pin=3999618259371&hs=0
Calendar: openbmc@lists.ozlabs.org
Who:
* rhanley@google.com - organizer
* openbmc@lists.ozlabs.org
* neladk@microsoft.com
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=MmtrNzRhYmsybzdlMG1hbmRwZWJwY2Y2NnMgb3BlbmJtY0BsaXN0cy5vemxhYnMub3Jn&tok=MTgjcmhhbmxleUBnb29nbGUuY29tYzI4YWY2MzM1ZWUwMjcwN2FlYmEwMGEwN2ViYmVjNzJmNThmZTRkOA&ctz=America%2FLos_Angeles&hl=en&es=0
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
openbmc@lists.ozlabs.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
Forwarding this invitation could allow any recipient to send a response to
the organizer and be added to the guest list, or invite others regardless
of their own invitation status, or to modify your RSVP. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
[-- Attachment #1.2: Type: text/html, Size: 12429 bytes --]
[-- Attachment #1.3: Type: text/calendar, Size: 2501 bytes --]
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20200206T180000Z
DTEND:20200206T190000Z
DTSTAMP:20200129T235922Z
ORGANIZER;CN=rhanley@google.com:mailto:rhanley@google.com
UID:2kk74abk2o7e0mandpebpcf66s@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=openbmc@lists.ozlabs.org;X-NUM-GUESTS=0:mailto:openbmc@lists.ozlabs
.org
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
UE;CN=SVL-MAT3-4-Saturn (5) [GVC];X-NUM-GUESTS=0:mailto:google.com_726f6f6d
5f75735f73766c5f6d6174335f345f346839@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=neladk@microsoft.com;X-NUM-GUESTS=0:mailto:neladk@microsoft.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=rhanley@google.com;X-NUM-GUESTS=0:mailto:rhanley@google.com
X-MICROSOFT-CDO-OWNERAPPTID:623331368
CREATED:20200129T235922Z
DESCRIPTION:Sorry for the delay in putting together this follow up meeting.
\n\nWe made some progress in hashing out some of the requirements of a BMC
aggregator in our last meeting. \n\nHowever\, one of the issues that needs
more discussion is what features are needed in a presentation layer for thi
s aggregator.\n\nI think this discussion is one of the biggest blockers bef
ore we can trading any designs\, and I look forward to hearing about any us
e cases that people are considering.\n\n(P.S. I will be creating a second m
eeting that is more amenable to Asian timezones)\n\n-::~:~::~:~:~:~:~:~:~:~
:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do
not edit this section of the description.\n\nThis event has a video call.\
nJoin: https://meet.google.com/fzh-kuvi-wqo\n+1 406-686-3826 PIN: 214092#\n
View more phone numbers: https://tel.meet/fzh-kuvi-wqo?pin=3999618259371&hs
=7\n\nView your event at https://www.google.com/calendar/event?action=VIEW&
eid=MmtrNzRhYmsybzdlMG1hbmRwZWJwY2Y2NnMgb3BlbmJtY0BsaXN0cy5vemxhYnMub3Jn&to
k=MTgjcmhhbmxleUBnb29nbGUuY29tYzI4YWY2MzM1ZWUwMjcwN2FlYmEwMGEwN2ViYmVjNzJmN
ThmZTRkOA&ctz=America%2FLos_Angeles&hl=en&es=1.\n-::~:~::~:~:~:~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20200129T235922Z
LOCATION:SVL-MAT3-4-Saturn (5) [GVC]
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:BMC Aggregator Presentation Layer
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 2549 bytes --]
reply other threads:[~2020-01-29 23:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0000000000002b849a059d50210d@google.com \
--to=rhanley@google.com \
--cc=neladk@microsoft.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.