Re: [802SEC] Schedule for 802.24 upcoming meetings
I would agree with Roger that OmniRAN should take care of collisions
with 'cross-802' groups but other 802 WGs as well. Thinking of potential
participants in OmniRAN SG, people already working in the higher layer
of the 802 networking stack may be the more likely candidates. Aligning
across all the WGs may be a challenge, however if there are patterns in
the schedules of the WGs, then it is worth to take them into account.
Is it appropriate to run an EC SG mainly in the evening slots? If yes, I
would opt that OmniRAN meets in Vancouver on Mo 1930-2130, Tue 1930-2130
and Thu afternoon 1330-1530 and potentially 1600-1800. It would not
overlap with 802.24 and would avoid too many collisions with the other
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of ext Roger Marks
Sent: Tuesday, November 20, 2012 23:43
To: STDS-802-SEC SEC
Subject: Re: [802SEC] Schedule for 802.24 upcoming meetings
Max prefers <email@example.com>.
Regarding the proposal, I think it's worth considering as a suggestion,
but we need to consider other factors as well. I agree that the TAGs and
the current ECSG are "cross-802" groups to some degree, and all have
interest overlapping with the membership of the WGs. However, the same
can be said of other WGs as well. 802.19 is a clear example, but not the
The philosophy of limiting schedule overlap among 802.18, 802.24, and
OmniRAN is, I guess, based on the presumption that there are a lot of
participants who want to attend all three. Personally, I can't think of
anyone in that category, because the technical topics are pretty
diverse. For example, I attend 802.18 sometimes, but I don't recall
seeing anyone else in an 802.18 meeting who was also in a meeting of the
802.16 HetNet SG (which carried the OmniRAN activity). I do know that
there has been some common interest between 802.18 and 802.24, but that
probably depends on the specific agendas.
I think that the key to successful OmniRAN scheduling is to limit
overlap with the activities in the WGs that look upward toward Layer 3.
On 2012/11/20, at 03:05 PM, James P. K. Gilb wrote:
> That sounds like a good idea. I will coordinate with Mike and Max.
> Roger, can you send me Max's email so we can pick times that don't
conflict among 802.18, 802.24 and the new ECSG?
> James Gilb
> On 11/19/2012 05:01 PM, Paul Nikolich wrote:
>> Per our discussion Friday evening, it will best if the other
>> groups interleave their schedules with yours to permit maximum
>> availability to those 802 participants interested in those cross-802
>> activities. Please try to work out the details with your colleagues.
>> ------ Original Message ------
>> From: "James P. K. Gilb" <firstname.lastname@example.org>
>> To: STDS-802-SEC@listserv.ieee.org
>> Sent: 11/19/2012 6:44:18 PM
>> Subject: [802SEC] Schedule for 802.24 upcoming meetings
>>> 802.24 will have an ad-hoc meeting in Vancouver in conjunction with
>>> the Wireless Interim meeting, The meeting dates and times will be:
>>> Jan 2013: Mon. 16:00-18:00 15 Jan 2013: Tue. 16:00-18:00 16 Jan
>>> Wed. 16:00-18:00
>>> 802.24 will have its next regular meeting during the IEEE 802
>>> session in Orlando. The meeting dates and times will be: 18 Mar
>>> Mon. 16:00-18:00 19 Mar 2013: Tue. 16:00-18:00 20 Mar 2013: Wed.
>>> James Gilb IEEE 802.24 Smart Grid TAG Chair
>>> ---------- This email is sent from the 802 Executive Committee email
>>> reflector. This list is maintained by Listserv.
> This email is sent from the 802 Executive Committee email reflector.
This list is maintained by Listserv.
This email is sent from the 802 Executive Committee email reflector.
This list is maintained by Listserv.
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.