attachment-0001
<div dir="ltr"><div><div><div><br clear="all"><div>Hi,<br><br></div><div>Note that the PT-EAP (layer 2 initial endpoint assessment<br></div><div>transport) is in the RFC Editor's Queue awaiting publication<br></div><div>
of IETF standards-track Tunneled EAP later this year - see<br><br><a href="https://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/">https://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/</a><br></div>
<br></div>Cheers,<br></div>- Ira<br><br></div>PS - PT-EAP was the last work item in the IETF NEA WG charter.<br><div><div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">The IESG</b> <span dir="ltr"><<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></span><br>
Date: Fri, Mar 29, 2013 at 3:58 PM<br>Subject: [Nea] Protocol Action: 'PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods' to Proposed Standard (draft-ietf-nea-pt-eap-09.txt)<br>To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>
Cc: nea mailing list <<a href="mailto:nea@ietf.org">nea@ietf.org</a>>, nea chair <<a href="mailto:nea-chairs@tools.ietf.org">nea-chairs@tools.ietf.org</a>>, RFC Editor <<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>><br>
<br><br>The IESG has approved the following document:<br>
- 'PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods'<br>
(draft-ietf-nea-pt-eap-09.txt) as Proposed Standard<br>
<br>
This document is the product of the Network Endpoint Assessment Working<br>
Group.<br>
<br>
The IESG contact persons are Stephen Farrell and Sean Turner.<br>
<br>
A URL of this Internet Draft is:<br>
<a href="http://datatracker.ietf.org/doc/draft-ietf-nea-pt-eap/" target="_blank">http://datatracker.ietf.org/doc/draft-ietf-nea-pt-eap/</a><br>
<br>
<br>
<br>
<br>
Technical Summary<br>
<br>
This document specifies PT-EAP, an Extensible Authentication Protocol<br>
(EAP) based Posture Transport (PT) protocol designed to be used only<br>
inside a TLS protected EAP tunnel method. The document also<br>
describes the intended applicability of PT-EAP.<br>
<br>
Working Group Summary<br>
<br>
In the call for proposals for Posture Transport (PT) specifications, there<br>
were two submissions for an EAP-based PT: one using an EAP method<br>
within an EAP tunnel method, and the other using a TLV format within an<br>
EAP tunnel method. Many discussions were had in the WG on the pros and<br>
cons of each approach. No consensus could be reached. Hence, the AD of<br>
the Working Group (Stephen Farrell) made the selection with the<br>
agreement that the WG would abide by the decision. Stephen selected the<br>
EAP method approach in a message to the NEA WG dated 24 Aug 2011<br>
(<a href="http://www.ietf.org/mail-archive/web/nea/current/msg01187.html" target="_blank">http://www.ietf.org/mail-archive/web/nea/current/msg01187.html</a>). The<br>
WG then adopted the EAP method proposal as a WG document, and<br>
followed the normal process from there. There is WG consensus to move<br>
this document forward.<br>
<br>
Document Quality<br>
<br>
There are no known vendor implementations of this particular specification,<br>
but there are existing implementations of an EAP method which is similar to<br>
what is currently specified. This document was reviewed by several people<br>
in the EMU WG, and no objections were raised.<br>
<br>
Personnel<br>
<br>
Susan Thomson is the Document Shepherd.<br>
Stephen Farrell is the Area Director.<br>
<br>
RFC Editor Note<br>
<br>
- draft-ietf-nea-asokan has been published as RFC 6813<br>
- draft-ietf-nea-pt-tls has been published as RFC 6876<br>
<br>
<br>
<br>
_______________________________________________<br>
Nea mailing list<br>
<a href="mailto:Nea@ietf.org">Nea@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/nea" target="_blank">https://www.ietf.org/mailman/listinfo/nea</a><br>
</div><br></div></div></div></div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.