The various implementers have been having substantial conversions behind the 
scenes about TEAP.   There are a number of interoperability issues which have 
come up, and therefore need to be addressed.

  The discussions were held offline to avoid bothering the list with details 
about C code, functions, etc.  It looks like we're approaching clarity on how 
TEAP operates, so I'm posting this message now.

  The current feeling is that the document has substantial room for 
improvement.  I'm writing new non-normative text, or rewording some of the  
non-normative text.  These changes address questions which were raised by 
implementers.

  There may need to be small changes to the key derivation functions.  Both 
RFC7170 and 7170bis are unclear enough that multiple implementations have done 
different things.  We're currently investigating exactly what those difference 
are.

  Once we have some quantitative data, we will update the WG with the 
information.  We can then discuss what the next steps are.

  The document is currently held in the RFC editor queue, waiting for 
draft-ietf-lamps-rfc7030-csrattrs.  I expect that once we finish updates to 
7170bis, we will need to run the document through the WG last call again.

  As the bulk of the changes are just clarifications, I hope that the last call 
process will be quick.

  Once I have a new revision of the document, I will post a message to the list 
summarizing the changes.  I've been tracking each individual change as a 
separate git commit.  The hope is that the resulting series of commits will be 
easy to understand and to review.

  So I had hoped that 7170bis was done.  But in the interest of improving the 
document to increase interoperability, it looks like it needs more work.

  Alan DeKok.

_______________________________________________
Emu mailing list -- emu@ietf.org
To unsubscribe send an email to emu-le...@ietf.org

Reply via email to