From jsalowey@cisco.com Wed Feb 13 15:21:20 2013 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB24521F863C for ; Wed, 13 Feb 2013 15:21:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NLtcQDDPBws for ; Wed, 13 Feb 2013 15:21:20 -0800 (PST) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 8DDDC21F8635 for ; Wed, 13 Feb 2013 15:21:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=835; q=dns/txt; s=iport; t=1360797679; x=1362007279; h=from:to:cc:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=KwVtzdAaXJJSl1VBLc1B2CXG8iTHRmj7lqRC1/TmjFY=; b=f++J20wBwyYh+Uwq/g6rQ8BW2TuOkkyHTWt8NKfTX9NH0ha7Czz7YymO 2oXRkcjha6mDG/sz2rqPuVHj0vi+Td+cdRxzXUW4lCxa5++2xHqy59KeU /5VXQmeuGIx6JNQuNuEcKIWt8GYjZCcSem88/dBk9vRc3Nc9jKtl0h5y4 M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkYFANEeHFGtJXHA/2dsb2JhbABFhgi6ZhZzgh8BAQEDAQEBATc0CwULAgEZAwECCxQQJwsUBwIIAgQOBQiIBAYMv1wEkSNhA6Z3gwaCJw X-IronPort-AV: E=Sophos;i="4.84,660,1355097600"; d="scan'208";a="176841852" Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 13 Feb 2013 23:21:19 +0000 Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r1DNLJ90030824 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Feb 2013 23:21:19 GMT Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Wed, 13 Feb 2013 17:21:18 -0600 From: "Joseph Salowey (jsalowey)" To: "nea@ietf.org" Thread-Topic: [Emu] Last call on draft-ietf-emu-eap-tunnel-method Thread-Index: AQHOCWMjaNlLFu8Ik02844sRUJP/nA== Date: Wed, 13 Feb 2013 23:21:18 +0000 Message-ID: References: <511AABCF.8020807@deployingradius.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.33.248.234] Content-Type: text/plain; charset="us-ascii" Content-ID: <79120290B123624E8A2887AB0D1EC154@cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [Nea] Fwd: [Emu] Last call on draft-ietf-emu-eap-tunnel-method X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 23:21:21 -0000 Please send any comments to the emu (emu@ietf.org) mailing list.=20 Thanks, Joe Begin forwarded message: > From: Alan DeKok > Subject: [Emu] Last call on draft-ietf-emu-eap-tunnel-method > Date: February 12, 2013 12:53:35 PM PST > To: "emu@ietf.org" >=20 > This is a WG last call on the draft-ietf-emu-eap-tunnel-method > document. Please post reviews, comments, feedback, etc. to this list. >=20 > The WG last call will last two weeks, until February 26. >=20 > If there have been no substantive comments or issues, we will take the > document to IETF last call. Minor editorial issues can be resolved then. >=20 > Alan DeKok. > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu From wwwrun@rfc-editor.org Wed Feb 27 11:36:20 2013 Return-Path: X-Original-To: nea@ietfa.amsl.com Delivered-To: nea@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCBCF21F8B1D; Wed, 27 Feb 2013 11:36:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.03 X-Spam-Level: X-Spam-Status: No, score=-102.03 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zDmOcCjZU+Pt; Wed, 27 Feb 2013 11:36:20 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id F00F821F8B19; Wed, 27 Feb 2013 11:36:17 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 632B772E168; Wed, 27 Feb 2013 11:35:01 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20130227193501.632B772E168@rfc-editor.org> Date: Wed, 27 Feb 2013 11:35:01 -0800 (PST) Cc: nea@ietf.org, rfc-editor@rfc-editor.org Subject: [Nea] RFC 6876 on A Posture Transport Protocol over TLS (PT-TLS) X-BeenThere: nea@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Network Endpoint Assessment discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 19:36:21 -0000 A new Request for Comments is now available in online RFC libraries. RFC 6876 Title: A Posture Transport Protocol over TLS (PT-TLS) Author: P. Sangster, N. Cam-Winget, J. Salowey Status: Standards Track Stream: IETF Date: February 2013 Mailbox: paul_sangster@symantec.com, ncamwing@cisco.com, jsalowey@cisco.com Pages: 44 Characters: 109852 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nea-pt-tls-08.txt URL: http://www.rfc-editor.org/rfc/rfc6876.txt This document specifies PT-TLS, a TLS-based Posture Transport (PT) protocol. The PT-TLS protocol carries the Network Endpoint Assessment (NEA) message exchange under the protection of a Transport Layer Security (TLS) secured tunnel. 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/rfcsearch.html. 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