While the charter updates are being formally approved, we can start
discussions about the new work items. Please respond with comments,
queries, or feedback on the items listed below.
Work item:
- A mechanism based on strong shared secrets. This mechanism
should strive to be simple and compact
While the charter updates are being formally approved, we can start
discussions about the new work items. Please respond with comments,
queries, or feedback on the items listed below.
Work item:
- Charter updates
Status:
The charter revision is in IESG evaluation.
While the charter updates are being formally approved, we can start
discussions about the new work items. Please respond with comments,
queries, or feedback on the items listed below.
Work items:
- A document that defines EAP channel bindings and provides
guidance for establishing EAP channel
While the charter updates are being formally approved, we can start
discussions about the new work items. Please respond with comments,
queries, or feedback on the items listed below.
Work item:
- A mechanism to support extensible communication within a
TLS protected tunnel. This mechanism mus
This is a consensus call for acceptance of the tunnel requirements draft
as an EMU WG work item. The consensus call will last until June 20,
2008. Please send email to the list stating whether you are in favor or
opposed to accepting this document as an EMU WG work item.
http://tools.ietf.org/i
> A tunnel method draft has been submitted:
>
> http://tools.ietf.org/id/draft-salowey-emu-eaptunnel-req-01.txt
>
> A separate call for consensus will be issued for this document.
RFC3748 (section 2.1) states:
However, the peer
and authenticator MUST utilize only one authentication me
Josh Howlett wrote:
> Am I correct in understanding that section 3.3 ('Chained EAP Methods')
> is not a violation of RFC3748 because it only applies to methods run
> *within* the tunnel method itself, and not to other methods that might
> precede or follow the tunnel method? In other words, this is
Alan:
I don't think we have a cryptographic binding WG work item, but a
channel binding one. However, the crypto-binding requirement is captured
in the Tunnel method requirement draft, as it is required to run a
single tunneled EAP method or chained ones.
> -Original Message-
> From: [EMA
