Talk proposal to hotRFC IETF 120

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear chair

Please find below my proposal talk summary to  HotRFC at IETF 120

Rgs
Pascal Urien

Presenter: Pascal Urien (in person), Telecom Paris, France, Pascal.Urien@xxxxxxxxxxxxxxxx
Title: Online TLS secure element for low-power high-security personal servers.
Abstract.
TLS for secure elements (TLS-SE [1]) is a TLS1.3 pre-shared-key (PSK) profile for secure elements. Ten billion secure elements are produced every year, including six billion Javacards, which execute applications written in the Javacard language. The physical size of an SE chip is about 5x5mm². TLS-SE can be implemented in Javacard, identified by a TLS server name (SEN, Secure Element Name) included in the historical bytes (up to 15 bytes) of the Answer To Reset (ATR).
Secured resources (SE security level is about EAL6+ according to Common Criteria standards) are available thanks to Uniform Resource Identifiers (URI) such as:
shells://sen@xxxxxxxxxx/?query, in which the query syntax is an open topic.
A Secure Element server may use a single SE (nano server, [1]) with an ISO7816 physical interface, or a grid of SEs (personal server, [3]), for example connected via an I2C bus.
Nano servers [1][2] can be designed with a system on chip (SoC) using open IDEs such as Arduino. With a Wi-Fi interface, the observed power consumption is about 0,2 W (5 W/day), so a small solar panel can be used for power supply.
Personal servers [3] use Secure Element Processors (SEP) implementing an I2C bridge with an ISO7816 interface. They are connected to the internet via a TCP/IP host such as Raspberry Pi. They also support the RACS [4] protocol for on-demand services. The observed power consumption is about 1,6 W + NSE * 0,15 W.
The TLS-SE ecosystem [5][6] is based on open hardware and software technologies (Arduino IDE, C/C++ GCC, Javacard Oracle JDK). We are looking for partners to develop an application framework realizing open trusted services for internet users.
[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://datatracker.ietf.org/doc/html/draft-urien-core-racs
[5] https://github.com/purien/TLS-SE
[6] https://github.com/purien/IoSE




Le sam. 13 juil. 2024 à 01:22, Liz Flynn <lflynn@xxxxxxxx> 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 hotrfc@xxxxxxxx no later than Friday, 2024-07-19, 2400 local meeting time 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 hotrfc@xxxxxxxx no later than Saturday, 2024-07-20, 2400 local meeting time.

  • 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, 2024-07-21, 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/120/sidemeetings.


--
120attendees mailing list -- 120attendees@xxxxxxxx
To unsubscribe send an email to 120attendees-leave@xxxxxxxx

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux