Re: [6tisch] [6lo] Informal 6LO Security Discussion during IETF 92

[James Woodyatt <[e-mail]>]

Everyone—

Here is the Doodle poll: <https://doodle.com/88z8uczakdumqs39>. I have
removed the confusing entries from the list of available options. The
currently winning choice is Thursday evening at 7:00p. I haven't got any
ideas for a location yet. Unless anybody has a better suggestion, the hotel
saloon is the default. In the event we choose a different venue, I'll show
up at the saloon 15 minutes early to collect people who didn't get the news.

I'd like to close the Doodle poll soon? Can everyone with an interest in
choosing a time for the gathering please get their votes registered before
the start of the afternoon sessions today? I'll announce the winning time
then.

On Mon, Mar 23, 2015 at 1:17 AM, Samita Chakrabarti <
[e-mail]> wrote:

>  Hello 6lo WG colleagues:
>
>
>
> James, Gabriel and I ( along with Ralph) are trying to arrange this
> meeting  to get an idea what folks are thinking about 6lo-security,
> bootstrapping options etc.. Since we don’t have enough WG time and many
> last minute security related requests  – we thought of having an informal
> discussions which will  give the participants/us an  idea how we should
> approach solving the security at the 6lo-level and what  the key questions
> are.
>
>
>
> For example: one question comes up often how to tie the multi-level
> security with a common information ?
>
>
>
> Please fill in the Doodle poll before the 6lo session – so we can have a
> concrete plan that we can announce at the meeting J
>
>
>
> Also, it’ll be a good opportunity to have an  informal get together and it
>  should be fun!
>
>
>
> Meeting place suggestions are welcome – please let James know on a unicast
> message J
>
>
>
> Best regards and see you many of you f2f  at the 6lo meeting!
>
>
>
> -Samita
>
>
>
> *From:* 6lo [mailto:[e-mail]] *On Behalf Of *James Woodyatt
> *Sent:* Sunday, March 22, 2015 4:01 PM
> *To:* [e-mail]
> *Cc:* [e-mail];
> [e-mail];
> [e-mail];
> [e-mail]; [e-mail];
> [e-mail]
> *Subject:* Re: [6lo] Informal 6LO Security Discussion during IETF 92
>
>
>
> Everyone—
>
>
>
> Doodle is silently timezone sensitive but doesn't make it obvious how to
> set the timezone for a meeting, other than the default: local time for the
> administrator. So, when I was choosing times thinking everyone would see
> local time unadorned with timezone, everyone else was getting ridiculous
> meeting times. I have edited the poll to add the time slots I was
> originally trying to set, adjusted for US Central timezone. I did not
> remove the original slots. Please revisit the poll.
>
>
>
> On Fri, Mar 20, 2015 at 10:36 PM, James Woodyatt <[e-mail]> wrote:
>
> Everyone—
>
>
>
> I've been asked to organize an informal gathering during IETF 92 for the
> purpose of discussing and understanding the various proposals for work
> in 6LO and related groups in the area of security protocols, and to
> consider whether asking the 6LO chairs to form a design team at this time
> is appropriate.
>
>
>
> This would not be an IETF meeting, and we would not have a written agenda
> or a meeting room with presentation equipment. It would be an informal
> discussion.
>
>
>
> I already know of some drafts in this category, but it would help to know
> if I missed any, so I can make sure their authors are invited to the
> gathering:
>
>
>
>   I-D.sarikaya-6lo-cga-nd
>
>   I-D.mglt-6lo-aes-implicit-iv
>
>   I-D.mglt-6lo-diet-esp (and related)
>
>   I-D.thaler-6lo-privacy-addrs
>
>   I-D.richardson-6tisch--security-6top
>
>
>
> To start off, I've created a Doodle pool <
> https://doodle.com/88z8uczakdumqs39> to gauge interest and converge on a
> suitable time slot. If you're interested in attending, please register your
> opinion about where and when to meet using the poll, or by emailing
> [e-mail] directly. I'm the administrator of the poll, so if
> you have a suggested time slot that I didn't list (I just listed evening
> slots immediately following the close of all the official IETF business)
> then please alert me directly, and I'll add it.
>
>
>
>
>
> --
>
> james woodyatt <[e-mail]>
>
> Nest Labs, Communications Engineering
>
>
>
>
>
> --
>
> james woodyatt <[e-mail]>
>
> Nest Labs, Communications Engineering
>



-- 
james woodyatt <[e-mail]>
Nest Labs, Communications Engineering