Hi Joe,
I've sent a set of diagrams to Alan for inclusion. They are the following:
* An example flow in which request action is used to ask the client to
renew a certificate.
* An example error flow of the above
* An example flow where only the TLS authentication is required.
Eliot
On 28.06.23 01:04, Joseph Salowey wrote:
We are nearing completion of RFC7170bis. There are a few open issues
in github - https://github.com/emu-wg/rfc7170bis/issues
Issue 21 <https://github.com/emu-wg/rfc7170bis/issues/21> - links to
the errata to verify that they have been addressed in the draft and
provides text for resolving the errata. In many cases it might be
easier to resolve as "wait for document update". Please review to
make sure the errata have been correctly addressed.
Issue 20 <https://github.com/emu-wg/rfc7170bis/issues/20> - we are
waiting on some flows on PKCS #10/#7 - I think Eliot has this action
item.
Issue 8 <https://github.com/emu-wg/rfc7170bis/issues/8> - is also a
related item, perhaps these can be addressed together.
Issue 17 <https://github.com/emu-wg/rfc7170bis/issues/17> - this is a
request to add mandatory to implement ciphersuites. Some more
discussion is needed on this.
Issue 15 <https://github.com/emu-wg/rfc7170bis/issues/15> - Discusses
an issue with chained EAP methods and proposes that we add some text
and a new error message to address this problem. Do people think this
needs addressing?
Once we resolve these issues we can move the draft forward.
Cheers,
Joe
_______________________________________________
Emu mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/emu
_______________________________________________
Emu mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/emu
