Re: [Nea] Congrats on Job Well Done

Does anyone have working code for this protocol?  I would like to validate
a few assumptions.

Joe Klein
"Inveniam viam aut faciam"

On Fri, May 9, 2014 at 4:08 PM, Steve Hanna <steve@hannas.com> wrote:

> Todd,
>
> I presume that you're referring to this IPR disclosure:
>
> https://datatracker.ietf.org/ipr/1889/
>
> If that's the case, you should refer to Cisco's statement
> in the IPR disclosure linked to above.
>
> Speaking only for myself and noting that I'm not a lawyer,
> I don't think there's any reason to worry about that IPR.
> In layman's terms, the Cisco statement says that anyone can
> use their IPR to implement the spec. However, if you sue
> them, they'll sue you back.
>
> Are you planning to implement the spec or just asking?
>
> Thanks,
>
> Steve
>
>
> On 5/9/2014 11:58 AM, TGLASSEY wrote:
>
>> What is the status of the Cisco Patent here?
>>
>> Todd
>>
>> On 5/9/2014 8:10 AM, Steve Hanna wrote:
>>
>>> I'm happy to say that the nea working group has completed our last
>>> milestone: publishing PT-EAP as a Standards Track RFC. TCG has
>>> published a document bringing their corresponding standard
>>> (IF-T/EAP) into alignment with the published version of PT-EAP:
>>>
>>> http://www.trustedcomputinggroup.org/community/2014/05/complete_
>>> set_of_nac_standards_from_ietf_and_tcg
>>>
>>>
>>> So we have achieved our goal of getting one set of standards for
>>> posture assessment.
>>>
>>> This WG will now be closed. The email list will stay open for
>>> any needed discussions.
>>>
>>> Thanks to all who have worked on the NEA protocols over the years.
>>>
>>> Good work!
>>>
>>> Steve Hanna
>>>
>>> -------- Original Message --------
>>> Subject: [Nea] RFC 7171 on PT-EAP: Posture Transport (PT) Protocol for
>>> Extensible Authentication Protocol (EAP) Tunnel Methods
>>> Date: Wed,  7 May 2014 23:15:24 -0700 (PDT)
>>> From: rfc-editor@rfc-editor.org
>>> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>>> CC: drafts-update-ref@iana.org, nea@ietf.org, rfc-editor@rfc-editor.org
>>>
>>> A new Request for Comments is now available in online RFC libraries.
>>>
>>>
>>>         RFC 7171
>>>
>>>         Title:      PT-EAP: Posture Transport (PT) Protocol
>>>                     for Extensible Authentication Protocol (EAP) Tunnel
>>>                     Methods
>>>         Author:     N. Cam-Winget, P. Sangster
>>>         Status:     Standards Track
>>>         Stream:     IETF
>>>         Date:       May 2014
>>>         Mailbox:    ncamwing@cisco.com,
>>>                     paul_sangster@symantec.com
>>>         Pages:      19
>>>         Characters: 45604
>>>         Updates/Obsoletes/SeeAlso:   None
>>>
>>>         I-D Tag:    draft-ietf-nea-pt-eap-09.txt
>>>
>>>         URL:        http://www.rfc-editor.org/rfc/rfc7171.txt
>>>
>>> This document specifies PT-EAP, a Posture Transport (PT) protocol
>>> based on the Extensible Authentication Protocol (EAP) and designed to
>>> be used only inside an EAP tunnel method protected by Transport Layer
>>> Security (TLS).  The document also describes the intended
>>> applicability of PT-EAP.
>>>
>>> This document is a product of the Network Endpoint Assessment Working
>>> Group of the IETF.
>>>
>>> This is now a Proposed Standard.
>>>
>>> STANDARDS TRACK: This document specifies an Internet standards track
>>> protocol for the Internet community,and requests discussion and
>>> suggestions
>>> for improvements.  Please refer to the current edition of the Internet
>>> Official Protocol Standards (STD 1) for the standardization state and
>>> status of this protocol.  Distribution of this memo is unlimited.
>>>
>>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>>> To subscribe or unsubscribe, see
>>>   http://www.ietf.org/mailman/listinfo/ietf-announce
>>>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>>
>>> For searching the RFC series, see http://www.rfc-editor.org/search
>>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>>>
>>> Requests for special distribution should be addressed to either the
>>> author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
>>> specifically noted otherwise on the RFC itself, all RFCs are for
>>> unlimited distribution.
>>>
>>>
>>> The RFC Editor Team
>>> Association Management Solutions, LLC
>>>
>>>
>>> _______________________________________________
>>> Nea mailing list
>>> Nea@ietf.org
>>> https://www.ietf.org/mailman/listinfo/nea
>>>
>>>
>>> _______________________________________________
>>> Nea mailing list
>>> Nea@ietf.org
>>> https://www.ietf.org/mailman/listinfo/nea
>>>
>>>
>>> -----
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 2014.0.4577 / Virus Database: 3931/7462 - Release Date: 05/08/14
>>>
>>>
>>>
>>
> _______________________________________________
> Nea mailing list
> Nea@ietf.org
> https://www.ietf.org/mailman/listinfo/nea
>