Re: [Hotrfc] IETF 117 HotRFC Talk Proposal

[Pascal Urien <[e-mail]>]

Hi Liz

Below is my final summary, and attached the slides
Best Regards
Pascal

Presenter: Pascal Urien (in person), Telecom Paris, France,
[e-mail]
Title: Trusted sensors for a greener world
Abstract:
Authentication and publication of sensor data is a critical issue when
trust matters. Sensors and network of sensors are widely used to monitor
environmental safety. It is a major topic for the scientific, public and
political communities.
Trust in payments (EMV bank card) or identity (electronic passport) is
achieved thanks to secure elements.
Trusted Sensors can be organized around secure elements including named TLS
servers [1] [3], providing mutual authentication and secure communications.
They may support:
- internal commands for administration.
- exported commands for Actuators/Sensors interactions.
- on-demand cryptographic resources authorization.
Secure element TLS-SE [1] application typically provides Key Management
System (KMS), remotely controlled via the TLS secure channel.
According to [2] dedicated messages can be exported for external execution,
involving interaction with sensors or actuator, whose response is
thereafter inserted in the TLS secure channel [4]
Secure element cryptographic resource can be unlocked by dedicated
messages, used for example to sign blockchain transactions.
In summary, trusted sensors, built over TLS secure elements can be remotely
administered, interact with sensors & actuators, and provide on-demand
cryptographic resources.
Is there a step beyond with the IETF, in order to:
- define framework for trusted sensors
- define network interface
- edit guideline for trusted sensors with open hardware software
[1] https://datatracker.ietf.org/doc/draft-urien-tls-se/
[2] https://datatracker.ietf.org/doc/draft-urien-core-tls-se-io/
[3] https://datatracker.ietf.org/doc/draft-urien-coinrg-iose/
[4] https://www.youtube.com/watch?v=74aoCvrtZ0c




Le sam. 15 juil. 2023 à 00:08, Liz Flynn <[e-mail]> a écrit :

> Hi Pascal,
>
> This is to let you know that we received your HotRFC abstract. You'll be
> on the agenda.
>
> Please send us your slides and any abstract updates no later than the
> first day of the upcoming IETF meeting, Saturday, at 2400 UTC. This will
> allow us to upload everything to the datatracker without wild panic and
> confusion.
>
> To help others help you - please make sure you're clear on what you want
> from other participants. You might be looking for people to help you on new
> proposals, specifications, implementations, or a variety of other things.
> You can put that in your slides, or just say it out loud, but don't let it
> be a mystery!
>
> And thanks for participating in HotRFC!
>
> The HotRFC Team
>
>
> Liz Flynn
> Project Manager / IETF
> [e-mail]
>
>
>
>
> On Jul 10, 2023, at 6:41 AM, Pascal Urien <[e-mail]> wrote:
>
> dear Sir
>
> Attached is   a talk proposal for IETF 117 HotRFC
>
> Best Regards
> Pascal Urien
>
> Presenter: Pascal Urien (in person), Telecom Paris, France
> Abstract
> Authentication and publication of sensor data is a critical issue when
> trust matters. Trust in payments (EMV bank card) or identity (electronic
> passport) is achieved thanks to secure elements.
> Trusted sensors can be designed over secure elements identified by a
> server name [3], which provide secure communication channels over embedded
> TLS-SE servers [1].
> Secure element TLS-SE application typically provides Key Management System
> (KMS), remotely controlled via the TLS secure channel.
> According to [2] dedicated messages can be exported for external
> execution, involving interaction with sensors or actuator, whose response
> is thereafter inserted in the TLS secure channel [4]
> Secure element keys can be unlocked on-demand by dedicated messages, and
> used for example to sign blockchain transactions.
> In summary, trusted sensors, built over TLS secure elements can be
> remotely administered, interact with sensors & actuators, and provide keys
> for blockchain transactions generation collected over secure channels.
>
> Is there a step beyond with the IETF ?
>
> [1] https://datatracker.ietf.org/doc/draft-urien-tls-se/
> [2] https://datatracker.ietf.org/doc/draft-urien-core-tls-se-io/
> [3] https://datatracker.ietf.org/doc/draft-urien-coinrg-iose/
> [4] https://www.youtube.com/watch?v=74aoCvrtZ0c
>
>
> Le jeu. 6 juil. 2023 à 20:35, Liz Flynn <[e-mail]> a écrit :
>
>> Do you have an idea, problem space, or proposal that IETFers and IRTFers
>> should hear about?
>>
>> Do you want to propose IETF or IRTF work but aren’t sure if your idea is
>> ready or who else will be interested?
>>
>> Agenda requests are now being accepted for the Request for Conversation
>> (HotRFC) lightning talk session. Presenters will have 4 minutes to make
>> their case for conversations.. Interested folks can contact the
>> presenter and continue the discussion after the session.
>>
>> Goals include encouraging brainstorming conversations, helping new work
>> proposers find collaborators, raising awareness of relevant work going on
>> elsewhere, and promoting BarBoFs. Past HotRFC lightning talks have covered
>> a broad range of purposes, including:
>>
>>    -
>>
>>    Collaboration: proposals for new standards work or new research
>>    topics that haven't been discussed elsewhere, potentially relevant research
>>    that may be ready for the IETF
>>    - Notification: new topics on the agenda in a BOF, working group or
>>    research group, especially cross-area IETF work
>>    -
>>
>>    Enlightenment: updates on relevant technologies, industry advances
>>    that could affect IETF participants.
>>
>> With strict time limits, concise talks will give viewers a sense of
>> whether they’d like to know more and, importantly, coordinates on how to do
>> so.
>>
>> With the current hybrid IETF meeting format, we’re going to keep things
>> simple and permit only live presentations, either on-site or remote via
>> MeetEcho. Slides must be submitted in advance.
>>
>> To request a slot, submit a short abstract to [e-mail] no later
>> than Friday, 2023-07-21, 2400 UTC that includes the following
>>
>>    - Talk title
>>    - Presenter, Affiliation, and whether you’ll be presenting in person
>>    or remotely
>>    - Short topic abstract (topics should be IETF- or IRTF-related in
>>    some way)
>>    - What you're looking for (education, collaborators, implementers,
>>    etc.)
>>    - Coordinates to learn more, contact those involved, participate in
>>    existing mailing lists and scheduled meetings, and/or relevant formal or
>>    side meetings.
>>    - Any relevant drafts or helpful resources you’d like collaborators
>>    to look at
>>
>> To provide slides, submit ppt or pdf to [e-mail] no later than
>> Saturday, 2023-07-22, 2400 UTC.
>>
>>    -
>>
>>    Talk abstracts and slides  will be posted on the meeting agenda. The
>>    agenda will be updated as requests come in.
>>
>> The session will be on Sunday, 2023-07-23, at 1800 local IETF meeting
>> time
>>
>>    -
>>
>>    All talks will be presented live, whether in-person or via MeetEcho
>>    -
>>
>>    Video of the session will be recorded for later viewing.
>>
>> Spencer Dawkins and Liz Flynn will be hosting the session on-site.  We
>> hope you’ll tune in.
>>
>> -- the HotRFC team
>>
>> P.s. If you think holding a public side meeting would be useful for
>> people who are interested in your topic, there’s a wiki for that, at
>> https://wiki.ietf.org/meeting/117/sidemeetings.
>>
>> --
>> 117attendees mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/117attendees
>>
> --
> Hotrfc mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/hotrfc
>
>
>