From nobody Wed May 7 23:16:13 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4ABC1A022F; Wed, 7 May 2014 23:16:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.553 X-Spam-Level: X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89K2E2Uujo1Q; Wed, 7 May 2014 23:16:06 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id C6F611A04B9; Wed, 7 May 2014 23:16:05 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 81DEC180095; Wed, 7 May 2014 23:15:24 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 6000:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20140508061524.81DEC180095@rfc-editor.org> Date: Wed, 7 May 2014 23:15:24 -0700 (PDT) Archived-At: http://mailarchive.ietf.org/arch/msg/nea/nbqJHEA2Dtw3xLUYfUvW8N8tG5E Cc: drafts-update-ref@iana.org, nea@ietf.org, rfc-editor@rfc-editor.org Subject: [Nea] RFC 7171 on PT-EAP: Posture Transport (PT) Protocol for Extensible Authentication Protocol (EAP) Tunnel Methods X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 06:16:09 -0000 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 From nobody Thu May 8 09:40:16 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2EF21A0085; Thu, 8 May 2014 09:40:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.853 X-Spam-Level: X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y2LtTLSh07dy; Thu, 8 May 2014 09:40:09 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5783D1A0081; Thu, 8 May 2014 09:40:09 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 13E191801A4; Thu, 8 May 2014 09:39:27 -0700 (PDT) To: steve@hannas.com, Paul_Sangster@symantec.com, kaushik@cisco.com X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Message-Id: <20140508163927.13E191801A4@rfc-editor.org> Date: Thu, 8 May 2014 09:39:27 -0700 (PDT) Archived-At: http://mailarchive.ietf.org/arch/msg/nea/Y9hzm35jbnaS4moKhTukMHC98IQ Cc: rfc-editor@rfc-editor.org, nea@ietf.org, iesg@ietf.org Subject: [Nea] [Errata Verified] RFC5792 (3935) X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 16:40:11 -0000 The following errata report has been verified for RFC5792, "PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5792&eid=3935 -------------------------------------- Status: Verified Type: Technical Reported by: Steve Hanna Date Reported: 2014-03-27 Verified by: Stephen Farrell (IESG) Section: 3.1 Original Text ------------- Each PA-TNC message may contain one or more attributes associated with the functional component identified in the component type (PA Subtype) of the Posture Broker (PB) protocol. Corrected Text -------------- Each PA-TNC message may contain zero or more attributes associated with the functional component identified in the component type (PA Subtype) of the Posture Broker (PB) protocol. Notes ----- Section 4 of RFC 5792 says “A PA-TNC message MUST contain a PA-TNC header (defined in section 3.6. followed by a sequence of zero or more PA-TNC attributes.” This contradicts the text in section 3.1, which says “one or more”. The correct text is “zero or more”. There’s no reason why a PA-TNC message containing zero attributes should be prohibited. For PA-TNC messages with some PA subtypes, an empty message containing no attributes may be enough. -------------------------------------- RFC5792 (draft-ietf-nea-pa-tnc-06) -------------------------------------- Title : PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC) Publication Date : March 2010 Author(s) : P. Sangster, K. Narayan Category : PROPOSED STANDARD Source : Network Endpoint Assessment Area : Security Stream : IETF Verifying Party : IESG From nobody Thu May 8 09:40:36 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D2351A0074; Thu, 8 May 2014 09:40:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.853 X-Spam-Level: X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ip9ngAVOnwfb; Thu, 8 May 2014 09:40:34 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id A20A81A0087; Thu, 8 May 2014 09:40:29 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 5E7711801A4; Thu, 8 May 2014 09:39:47 -0700 (PDT) To: steve@hannas.com, Paul_Sangster@symantec.com, kaushik@cisco.com X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Message-Id: <20140508163947.5E7711801A4@rfc-editor.org> Date: Thu, 8 May 2014 09:39:47 -0700 (PDT) Archived-At: http://mailarchive.ietf.org/arch/msg/nea/mQZT6CwuM86EcLVjNwciD-EhTmo Cc: rfc-editor@rfc-editor.org, nea@ietf.org, iesg@ietf.org Subject: [Nea] [Errata Verified] RFC5792 (3936) X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 16:40:35 -0000 The following errata report has been verified for RFC5792, "PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5792&eid=3936 -------------------------------------- Status: Verified Type: Technical Reported by: Steve Hanna Date Reported: 2014-03-27 Verified by: Stephen Farrell (IESG) Section: 3.4 Original Text ------------- As depicted in section 3.2, a PA-TNC message consists of a PA-TNC header followed by a sequence of one or more attributes. Corrected Text -------------- As depicted in section 3.2, a PA-TNC message consists of a PA-TNC header followed by a sequence of zero or more attributes. Notes ----- Section 4 of RFC 5792 says “A PA-TNC message MUST contain a PA-TNC header (defined in section 3.6. followed by a sequence of zero or more PA-TNC attributes.” This contradicts the text in section 3.4, which says “one or more”. The correct text is “zero or more”. There’s no reason why a PA-TNC message containing zero attributes should be prohibited. For PA-TNC messages with some PA subtypes, an empty message containing no attributes may be enough. -------------------------------------- RFC5792 (draft-ietf-nea-pa-tnc-06) -------------------------------------- Title : PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC) Publication Date : March 2010 Author(s) : P. Sangster, K. Narayan Category : PROPOSED STANDARD Source : Network Endpoint Assessment Area : Security Stream : IETF Verifying Party : IESG From nobody Fri May 9 08:12:04 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333D91A0043 for ; Fri, 9 May 2014 08:11:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dbI1bzINqEzx for ; Fri, 9 May 2014 08:11:50 -0700 (PDT) Received: from hannas.com (hannas.com [206.130.105.83]) by ietfa.amsl.com (Postfix) with ESMTP id 8548D1A02EA for ; Fri, 9 May 2014 08:11:00 -0700 (PDT) Received: from [192.168.1.9] (c-50-164-134-218.hsd1.ma.comcast.net [50.164.134.218]) (authenticated bits=0) by hannas.com (8.13.1/8.13.1) with ESMTP id s49FAsKc026539 for ; Fri, 9 May 2014 09:10:55 -0600 Message-ID: <536CEFFA.40509@hannas.com> Date: Fri, 09 May 2014 11:10:50 -0400 From: Steve Hanna User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: nea@ietf.org References: <20140508061524.81DEC180095@rfc-editor.org> In-Reply-To: <20140508061524.81DEC180095@rfc-editor.org> X-Forwarded-Message-Id: <20140508061524.81DEC180095@rfc-editor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/nea/oKAI89oCY76hC3UszwFCVIs43cw Subject: [Nea] Congrats on Job Well Done X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 15:11:53 -0000 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 From nobody Fri May 9 08:58:41 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 138881A02C7 for ; Fri, 9 May 2014 08:58:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.651 X-Spam-Level: X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fi2B2cIXK305 for ; Fri, 9 May 2014 08:58:36 -0700 (PDT) Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id EB1971A02B6 for ; Fri, 9 May 2014 08:58:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=fGl4kGJvbYupFXWHqU8Kd3LgzUQLYe4KWs+jtc1tUVAwUECkKzpPEkiNrK0aeI+1; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [67.180.134.155] (helo=[192.168.0.4]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from ) id 1WinBu-0006pw-9u for nea@ietf.org; Fri, 09 May 2014 11:58:30 -0400 Message-ID: <536CFB32.7010704@earthlink.net> Date: Fri, 09 May 2014 08:58:42 -0700 From: TGLASSEY User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: nea@ietf.org References: <20140508061524.81DEC180095@rfc-editor.org> <536CEFFA.40509@hannas.com> In-Reply-To: <536CEFFA.40509@hannas.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7938caa79a98ac1b68de91301de9e0ecb2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 67.180.134.155 Archived-At: http://mailarchive.ietf.org/arch/msg/nea/cHFhzWUnh9Ibv8ZAuQL2T3QtDrw Subject: Re: [Nea] Congrats on Job Well Done X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 15:58:38 -0000 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 > > -- ------------- Personal Email - Disclaimers Apply From nobody Fri May 9 10:39:25 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 476231A0309; Fri, 9 May 2014 10:39:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0XWT9kT91cQs; Fri, 9 May 2014 10:39:21 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D3641A0303; Fri, 9 May 2014 10:39:21 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IESG Secretary To: IETF Announcement List X-Test-IDTracker: no X-IETF-IDTracker: 5.4.2.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140509173921.2608.57911.idtracker@ietfa.amsl.com> Date: Fri, 09 May 2014 10:39:21 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/nea/_DpPIaMcddGIGusquFnQWUUsx4M Cc: nea@ietf.org, shanna@juniper.net Subject: [Nea] WG Action: Conclusion of Network Endpoint Assessment (NEA) X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Reply-To: iesg@ietf.org List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 17:39:22 -0000 The Network Endpoint Assessment (NEA) in the Security Area has concluded. The IESG contact person is Stephen Farrell. The NEA working group has now successfully completed all of its chartered work items. Many thanks to Steve and Susan for navigating the group through some interesting consensus challenges, and to WG participants for their willingness to reach consensus in the end. The mailing list will remain open. From nobody Fri May 9 13:08:47 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A541A1A00D7 for ; Fri, 9 May 2014 13:08:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mkd86XpHoefM for ; Fri, 9 May 2014 13:08:41 -0700 (PDT) Received: from hannas.com (hannas.com [206.130.105.83]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD171A00B0 for ; Fri, 9 May 2014 13:08:41 -0700 (PDT) Received: from [192.168.1.9] (c-50-164-134-218.hsd1.ma.comcast.net [50.164.134.218]) (authenticated bits=0) by hannas.com (8.13.1/8.13.1) with ESMTP id s49K8YdO032268; Fri, 9 May 2014 14:08:34 -0600 Message-ID: <536D35C1.10303@hannas.com> Date: Fri, 09 May 2014 16:08:33 -0400 From: Steve Hanna User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: TGLASSEY , nea@ietf.org References: <20140508061524.81DEC180095@rfc-editor.org> <536CEFFA.40509@hannas.com> <536CFB32.7010704@earthlink.net> In-Reply-To: <536CFB32.7010704@earthlink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/nea/1TWP_kaN5okfuxjDrkPhGlZ-wRM Subject: Re: [Nea] Congrats on Job Well Done X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 20:08:43 -0000 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 >> >> > From nobody Fri May 9 13:40:53 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F261A001B for ; Fri, 9 May 2014 13:40:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id go8hzzZ286EX for ; Fri, 9 May 2014 13:40:48 -0700 (PDT) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 0CBC21A0013 for ; Fri, 9 May 2014 13:40:47 -0700 (PDT) Received: by mail-qc0-f182.google.com with SMTP id e16so5275721qcx.13 for ; Fri, 09 May 2014 13:40:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=V2TRTl8RAXecYbiVjXRKSuS5JEsaPZdEG0EM4yZzsCg=; b=XoXOoT0PKk44SP/O/f4zn1nut5P3cflVyaO3PcObhA9DLvS/i8o++RhQ1sgW3lvHdl HsbEHd5NdJjCKaRZzmxEn9l6fQaAruTur7Qg0h8vW6SkUwf8Sg7b5be67+qf4ZzpVhAF HcJUmd/FfX8Ya8b9/qmSu3ZeZcIBqFeZOQCG33u4g/MWEkp3eL2FgI1J/D/+ZHkVquYq CdK2PlvTy/Oh2waNK42UkEV8PjEeRnsgcsfF3N6jYnyLJIZDwsIfPMJtwb7BxCGyskXt elSoTHzWLC389Llb8AUf1NBwdqBjv3VSwhr2HXg6jY179bJHaPpIIXqe6L4/mgGcwO0I Tfpw== X-Received: by 10.224.0.79 with SMTP id 15mr18459004qaa.2.1399668042828; Fri, 09 May 2014 13:40:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.192.138 with HTTP; Fri, 9 May 2014 13:40:22 -0700 (PDT) In-Reply-To: <536D35C1.10303@hannas.com> References: <20140508061524.81DEC180095@rfc-editor.org> <536CEFFA.40509@hannas.com> <536CFB32.7010704@earthlink.net> <536D35C1.10303@hannas.com> From: Joe Klein Date: Fri, 9 May 2014 16:40:22 -0400 Message-ID: To: Steve Hanna Content-Type: multipart/alternative; boundary=047d7bf0d4987f2d2704f8fd9cfe Archived-At: http://mailarchive.ietf.org/arch/msg/nea/i0ZAPRSUwzAPJuaLuJ1-OtS4hHY Cc: nea@ietf.org Subject: Re: [Nea] Congrats on Job Well Done X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 20:40:51 -0000 --047d7bf0d4987f2d2704f8fd9cfe Content-Type: text/plain; charset=UTF-8 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 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 > --047d7bf0d4987f2d2704f8fd9cfe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Does anyone have working code for this protocol? =C2=A0I w= ould like to validate a few assumptions.=C2=A0

Joe Klein
"Inveniam viam aut faciam"


On Fri, May 9, 2014 at 4:08 PM, Steve Ha= nna <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, =C2=A07 May 2014 23:15:24 -0700 (PDT)
From: rfc-ed= itor@rfc-editor.org
To: ietf-announ= ce@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.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 RFC 7171

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title: =C2=A0 =C2=A0 =C2=A0PT-EAP: Posture Tran= sport (PT) Protocol
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 for E= xtensible Authentication Protocol (EAP) Tunnel
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Metho= ds
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author: =C2=A0 =C2=A0 N. Cam-Winget, P. Sangste= r
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Status: =C2=A0 =C2=A0 Standards Track
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stream: =C2=A0 =C2=A0 IETF
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date: =C2=A0 =C2=A0 =C2=A0 May 2014
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Mailbox: =C2=A0 =C2=A0ncamwing@cisco.com,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 paul_sangster@sy= mantec.com
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages: =C2=A0 =C2=A0 =C2=A019
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Characters: 45604
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Updates/Obsoletes/SeeAlso: =C2=A0 None

=C2=A0 =C2=A0 =C2=A0 =C2=A0 I-D Tag: =C2=A0 =C2=A0draft-ietf-nea-pt-eap-09.= txt

=C2=A0 =C2=A0 =C2=A0 =C2=A0 URL: =C2=A0 =C2=A0 =C2=A0 =C2=A0http://www.rfc-edi= tor.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). =C2=A0The 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. =C2=A0Please refer to the current edition of the Internet=
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. =C2=A0Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
=C2=A0 http://www.ietf.org/mailman/listinfo/ietf-announce<= br> =C2=A0 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
htt= ps://www.ietf.org/mailman/listinfo/nea


_______________________________________________
Nea mailing list
Nea@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/nea


-----
No virus found in this message.
Checked by AVG - www.avg.c= om
Version: 2014.0.4577 / Virus Database: 3931/7462 - Release Date: 05/08/14



_______________________________________________
Nea mailing list
Nea@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/nea

--047d7bf0d4987f2d2704f8fd9cfe-- From nobody Fri May 9 13:48:43 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0637B1A00D8 for ; Fri, 9 May 2014 13:48:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lt2Zy-a81t2T for ; Fri, 9 May 2014 13:48:37 -0700 (PDT) Received: from hannas.com (hannas.com [206.130.105.83]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6F51A00D5 for ; Fri, 9 May 2014 13:48:37 -0700 (PDT) Received: from [192.168.1.9] (c-50-164-134-218.hsd1.ma.comcast.net [50.164.134.218]) (authenticated bits=0) by hannas.com (8.13.1/8.13.1) with ESMTP id s49KmSkY021686; Fri, 9 May 2014 14:48:29 -0600 Message-ID: <536D3F1B.1070005@hannas.com> Date: Fri, 09 May 2014 16:48:27 -0400 From: Steve Hanna User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Joe Klein References: <20140508061524.81DEC180095@rfc-editor.org> <536CEFFA.40509@hannas.com> <536CFB32.7010704@earthlink.net> <536D35C1.10303@hannas.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/nea/_zGUoLIkt0Sb8dB1UW6uMs4fauw Cc: nea@ietf.org Subject: Re: [Nea] Congrats on Job Well Done X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 20:48:40 -0000 According to this web page, StrongSwan supports an earlier draft: http://wiki.strongswan.org/issues/342 I'm sure that Andreas would love to have another independent implementation to test against so please let him (and the nea list) know if you do an implementation. Thanks, Steve On 5/9/2014 4:40 PM, Joe Klein wrote: > 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 > 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 > > > From nobody Mon May 12 05:55:44 2014 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447491A0694 for ; Mon, 12 May 2014 05:55:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.955 X-Spam-Level: X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EThLQQwF6YZj for ; Mon, 12 May 2014 05:55:41 -0700 (PDT) Received: from mail.strongswan.org (unknown [152.96.80.46]) by ietfa.amsl.com (Postfix) with ESMTP id 513981A068E for ; Mon, 12 May 2014 05:55:41 -0700 (PDT) Received: from [152.96.15.58] (unknown [152.96.15.58]) by mail.strongswan.org (Postfix) with ESMTPSA id 8A58C40541; Mon, 12 May 2014 14:55:27 +0200 (CEST) Message-ID: <5370C4C4.9050909@strongswan.org> Date: Mon, 12 May 2014 14:55:32 +0200 From: Andreas Steffen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Steve Hanna , Joe Klein References: <20140508061524.81DEC180095@rfc-editor.org> <536CEFFA.40509@hannas.com> <536CFB32.7010704@earthlink.net> <536D35C1.10303@hannas.com> <536D3F1B.1070005@hannas.com> In-Reply-To: <536D3F1B.1070005@hannas.com> X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010604010106050004060605" Archived-At: http://mailarchive.ietf.org/arch/msg/nea/aWlqXNZ5VTZnrsfboNyjQM1ya4U Cc: nea@ietf.org Subject: Re: [Nea] Congrats on Job Well Done X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 12:55:43 -0000 This is a cryptographically signed message in MIME format. --------------ms010604010106050004060605 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, a strongSwan developers release is available which implements the RFC 7171 PT-EAP transport protocol: http://download.strongswan.org/strongswan-5.2.0dr3.tar.bz2 As the outer EAP tunnel method protecting the PT-EAP protocol EAP-TTLS is currently used because we haven't implemented RFC 7170 TEAP yet. An example scenario with two strongSwan IPsec Access Requestors (ARs) connecting to a strongSwan VPN Policy Enforcement Point (PEP) via IKEv2 which in turn has an EAP-RADIUS connection to a strongSwan Policy Decision Point (PDP) is shown here: http://www.strongswan.org/uml/testresults5dr/tnc/tnccs-20-pdp-eap/ The complete IETF NEA stack is used: - RFC 5792 PA-TNC - RFC 5793 PB-TNC - RFC 7181 PT-EAP Alternatively the strongSwan pt-tls-client which implements the RFC 6876 PT-TLS transport protocol can connect directly to the strongSwan Policy Decision Point over a TLS socket: http://www.strongswan.org/uml/testresults5dr/tnc/tnccs-20-pdp-pt-tls/ In this alternative scenario the stack is - RFC 5792 PA-TNC - RFC 5793 PB-TNC - RFC 6876 PT-TLS Best regards Andreas On 09.05.2014 22:48, Steve Hanna wrote: > According to this web page, StrongSwan supports an earlier draft: >=20 > http://wiki.strongswan.org/issues/342 >=20 > I'm sure that Andreas would love to have another independent > implementation to test against so please let him (and the nea > list) know if you do an implementation. >=20 > Thanks, >=20 > Steve >=20 > On 5/9/2014 4:40 PM, Joe Klein wrote: >> 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 > > 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: >> >> =20 >> http://www.__trustedcomputinggroup.org/__community/2014/05/complete___= set_of_nac_standards_from___ietf_and_tcg >> >> =20 >> >> >> >> >> 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 th= e >> 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) Protoc= ol >> for Extensible Authentication Protoco= l >> (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 standardizatio= n >> state and >> status of this protocol. Distribution of this memo is >> unlimited. >> >> This announcement is sent to the IETF-Announce and rfc-dis= t >> 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 >> >> >> >=20 > _______________________________________________ > Nea mailing list > Nea@ietf.org > https://www.ietf.org/mailman/listinfo/nea --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Andreas Steffen andreas.steffen@strongswan.org strongSwan - the Open Source VPN Solution! www.strongswan.org Institute for Internet Technologies and Applications University of Applied Sciences Rapperswil CH-8640 Rapperswil (Switzerland) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D[ITA-HSR]=3D=3D --------------ms010604010106050004060605 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMhDCC BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3 MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6 qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95 m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0 dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93 d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy 6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9 sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t 5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGSDCCBTCgAwIBAgIDB7KBMA0GCSqGSIb3DQEB CwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTMwOTI4MTIzNDU4 WhcNMTQwOTMwMDMxMjI2WjBYMScwJQYDVQQDDB5hbmRyZWFzLnN0ZWZmZW5Ac3Ryb25nc3dh bi5vcmcxLTArBgkqhkiG9w0BCQEWHmFuZHJlYXMuc3RlZmZlbkBzdHJvbmdzd2FuLm9yZzCC ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJtxLfnUeESAyEiRlISv6pmUjP1uEd/4 18V5rGVcJbAtzuJfHAlJeHyVaqI8aGjwLN2jHxmPVPJfFi0Z3t/bRAK4u7vnfysSJHTqyrYn 9af2sg59CHvVo9fPEbvX7S+8mi1B2hbWUAVhIO0cmqChBku17gmHdWx+t86gp2v4Ku9ztxC7 D/iNodhHRAofm3RWZSy7VI8W8kifDo2aH2PFG3fw5jFHPxzYNL1DR/ENA2VA1io0x5NA78Mx ZpR6Rgz1jsXp3EgSh+xkcNhY2ugDu1/lIxtvey6JD/BgWIHHh2DI/2gb+HFsDrgVo+A4yf3S u/qv6JHapij26OUCLEYkwdsCAwEAAaOCAuQwggLgMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSw MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUp4bQ66T4CmiuI9i9 RewQZ8gFWdgwHwYDVR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwKQYDVR0RBCIwIIEe YW5kcmVhcy5zdGVmZmVuQHN0cm9uZ3N3YW4ub3JnMIIBTAYDVR0gBIIBQzCCAT8wggE7Bgsr BgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv bGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0 aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5nIHRv IHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBD QSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNv bXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0w K6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUF BwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xh c3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2Vy dHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3Rh cnRzc2wuY29tLzANBgkqhkiG9w0BAQsFAAOCAQEAwrFtQfZk5tTb8e//+hSdJGU7Pfq8k6Ip gpzGWIHwy5h/OKJ9mX/4oXWXxIg5L1iyNX44AbnUBRIr7LxfWsKy1O+SxjlraxmeClKD83fJ bbqFg9f14TpF3KvjQULFvNlJf8mdfjO3JCYeswDw3GBjtWYl49zyqiYYG4ovZ+FcPz38cOUT 6VtAjzVe862tsq1mE86WuxMeEt5rDHSf2BorxN+VbG3R9+5ewcl4P6pxbWYjCooHfg4gcplI qMHaggRZvS9c1p85CT5BTIlcLwf1RZz6/TDgCarGqkQnGKovFSotb/6fafq49C5nAtXkyB9X FDQ7lYoldvA387ATO1FTgjGCA90wggPZAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UE ChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUg U2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0 ZSBDbGllbnQgQ0ECAweygTAJBgUrDgMCGgUAoIICHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA1MTIxMjU1MzJaMCMGCSqGSIb3DQEJBDEWBBQ7QP/c 6F8+Jiby98FvL+GHS25ltzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgB ZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsO AwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklM MRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0 aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50 ZXJtZWRpYXRlIENsaWVudCBDQQIDB7KBMIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkG A1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdp dGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJp bWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMHsoEwDQYJKoZIhvcNAQEBBQAEggEALIL8 7VB5O+adK5FwnrxFNV1iyrWr++wTrbeHbOMdqAMUupd3/FaqayEQwd6T8YguT8Kid5J//k6X Px/67BXPMz5I4w1uuB/dai2P5W+fu+oqs2NSqKd/84x4nTePoBdDiCd1S/sob2G9XgJsw+vR WYI3ceOH4jWeqF+0pWMqlANIuq6581gprTMACMJ1ofIIv5aV23RETWqAwKqW80YIZi0dNzii ah9caOFU8+dGO0AZ6zI4okIu5VaNSyZ4q0+TDrrxoF2a5T77wPsEyf587BfabpgiROhfBbma P7r8xzBFDV4cAukMIKFqk+xr2ZAB0X7gIphYtgLJ/bXG/6gmzQAAAAAAAA== --------------ms010604010106050004060605--