
From rturner@amalfisystems.com  Mon Sep  7 21:51:38 2009
Return-Path: <rturner@amalfisystems.com>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69C523A67B1 for <nea@core3.amsl.com>; Mon,  7 Sep 2009 21:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qckOhQ8S8tBg for <nea@core3.amsl.com>; Mon,  7 Sep 2009 21:51:37 -0700 (PDT)
Received: from omr1.networksolutionsemail.com (omr1.networksolutionsemail.com [205.178.146.51]) by core3.amsl.com (Postfix) with ESMTP id 65D3728C113 for <nea@ietf.org>; Mon,  7 Sep 2009 21:51:37 -0700 (PDT)
Received: from mail.networksolutionsemail.com (ns-omr1.mgt.netsol.com [10.49.6.64]) by omr1.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id n884q4cV031166 for <nea@ietf.org>; Tue, 8 Sep 2009 00:52:04 -0400
Received: (qmail 21673 invoked by uid 78); 8 Sep 2009 04:52:03 -0000
Received: from unknown (HELO ?10.0.1.4?) (72.37.183.204) by ns-omr1.lb.hosting.dc2.netsol.com with SMTP; 8 Sep 2009 04:52:03 -0000
Message-Id: <8AA6B948-DA3D-4271-BF04-632225D8C09F@amalfisystems.com>
From: Randy Turner <rturner@amalfisystems.com>
To: NEA <nea@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 7 Sep 2009 21:52:03 -0700
X-Mailer: Apple Mail (2.936)
Subject: [Nea] Request for guidance on PA-subtypes for Multi-function hardcopy devices
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Sep 2009 04:51:38 -0000

Hello NEA List,

The Printer Working Group is finalizing a set of attributes to be used  
exclusively with imaging devices, and these attributes will be rooted  
under the PWG's private enterprise SMI number.

The PWG has utilized the extensibility mechanism provided by the PA- 
TNC document to create SMI-specific attributes.

The specific question I had was regarding attribute request "routing".

Attribute requests within the NEA/TNC protocols are routed to logical  
components within a device based on PA-subtype.

Like the attribute extensibility feature, PA-subtypes seem to allow  
the same type of SMI-specific extensibility.

Currently, the PWG has NOT created any new PA-subtypes specific to  
imaging/hardcopy devices.

The absence of any new PWG-specific PA-subtypes implies the PWG would  
have to route PWG-specific attributes using existing "standard" NEA PA- 
subtypes. For example, one of:

Testing
Operating System
Anti-Virus
Anti-Spyware
Anti-Malware
Firewall
IDPS
VPN
NEA Client

Many imaging (especially high-end multifunction devices) have started  
using Linux as their OS platform. In these cases, it's possible that  
the proposed NEA standard PA-subtypes would be appropriate. Even when  
the OS platform is a traditional embedded operating system such as  
VxWorks, it's possible that these devices could use a subset of the  
same NEA proposed standard PA-subtypes.

Given all the "level-setting" information I have described above, I  
was curious about a very common product architectural scenario that is  
prevalent in the marketplace for high-end multi-function imaging  
devices that provide multiple "hardware" services to the network,  
typically:

1. Printing
2. Scanning
3. Faxing (both traditional analog fax, as well as fax over VoIP)
4. Copying (a logical service consisting of scanning+printing in  
digital copier/printers)

It is quite normal in this industry to have separate "computers" to  
provide each of these functions. By "computers", I mean a separate CPU  
and separate memory space (really a separate board).  These separate  
computers have their own firmware/software version and patch  
information that might need to be assessed for security posture.

The Multifunction  product only has one network interface over which  
it communicates.  And in some cases (like HP's products), even this  
network device is one of the "separate computing devices" within the  
overall product, and has a separate firmware and operating system  
"version".

In the absence of PWG-specific PA-subtypes, I'm curious how a  
validator could request software version & patch information from each  
of these separate computing spaces?  For example, if I have 3 separate  
"computers" in my multifunction product, and I want to retrieve the OS  
version of each separate OS running on each "computer", how would I  
target my requests?

I can think of ways to "overload attribute values" or "cheat" using  
the current model, but it seems to me like a PA-subtype of "Fax  
Subsystem" (as an example) might be a better way to really represent  
what I'm trying to do.

When I proposed creating new PA-subtypes like this to the PWG, they  
noticed that none of the existing NEA proposed PA-subtypes represent  
"hardware" subsystems, and that my proposal might violate some NEA  
design guideline.  As an example, they posed the question "Why didn't  
the NEA (or TNC group) provide a PA-subtype for "BIOS", since this  
subsystem is versioned and remediated independently of the "Operating  
System", and is a standard component within desktop PCs? I didn't have  
an answer for this question since I'm not a TCG member and wasn't  
present when these subtypes were possibly discussed.

Comments or Suggestions as to how we might proceed are greatly  
appreciated!  My own personal opinion at the moment is that we  
probably need PA-subtypes defined under the PWG SMI.

Thanks
Randy




From shanna@juniper.net  Wed Sep  9 08:03:00 2009
Return-Path: <shanna@juniper.net>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 298D628C22D for <nea@core3.amsl.com>; Wed,  9 Sep 2009 08:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xf3u1KSJ4tAx for <nea@core3.amsl.com>; Wed,  9 Sep 2009 08:02:59 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id C554B3A699E for <nea@ietf.org>; Wed,  9 Sep 2009 08:02:58 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKSqfDw9dlOqU6bbYCBM8tHT/7lnPkCcU5@postini.com; Wed, 09 Sep 2009 08:03:31 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 9 Sep 2009 07:56:10 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 9 Sep 2009 10:56:10 -0400
From: Stephen Hanna <shanna@juniper.net>
To: NEA <nea@ietf.org>
Date: Wed, 9 Sep 2009 10:54:24 -0400
Thread-Topic: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available
Thread-Index: AcoxW3x0itr054ovT3Oh2zchhv74PgAALA6gAAA9klA=
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AE8E7851E6AE@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Nea] FW: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2009 15:03:00 -0000

If you have any ideas for IAB, IESG, or IAOC nominations,
please submit them as described below. Apparently, more
nominations are desperately needed!

Thanks,

Steve

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of Barnes, Mary
(RICH2:AR00)
Sent: Wednesday, September 09, 2009 9:38 AM
To: IETF Announcement list
Cc: ietf@ietf.org
Subject: Nomcom 2009-10: Important Reminder: Call for Nominations, Local
Office hours, Nominee Questionnaires available=20

Hi all,

This is a 2nd reminder of the Call for Nominations that is underway.  We
*really* need more nominations in order to properly execute the task of
selecting candidates for the open positions. At this time, the number of
nominations for all the positions is about 1/2 of what is necessary for
the Nomcom to do a conscientious job of evaluating the nominees and we
are over 2/3 of the way through the nominations period. Nomcom cannot do
their job without this important input from the community.=20

So, please consider making nominations for the open positions - it takes
just a few minutes of your time - the details are below.  Right now, we
just need the names/email addresses for the nominees - we'll be
soliciting feedback later. Also, consider that over 1/2 the nominees are
not able to accept the nominations for a variety of reasons - e.g., lack
of funding, lack of sponsor support, etc. Thus, please consider
nominating more than one individual for each of the positions. =20

As well as the reminder for the call for nominations, this email also
serves as a reminder for:
2) Local Office Hours
3) Questionnaires available for nominees=20

Best Regards,
Mary Barnes
nomcom-chair@ietf.org
mary.h.barnes@gmail.com
mary.barnes@nortel.com


=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=3D=3D
=3D

1) Call for Nominations
------------------------
The nomination period ends in less than 2 weeks on Sept. 18th, 2009. We
appreciate the folks that have taken the time to make nominations thus
far. But, we do need more nominations. Please use the online tool to
nominate - it's fast, easy and secure:
https://wiki.tools.ietf.org/group/nomcom/09/nominate

Details on the open positions, as well as other details and options for
making nominations are available on the Nomcom homepage:
https://wiki.tools.ietf.org/group/nomcom/09/

Please consider that the sooner you make the nominations, the more time
your nominee(s) will have to complete the necessary questionnaire (item
3
below).  As well, please consider nominating more than one person for a
particular position. You will have the opportunity to provide additional
feedback later and it's important to consider that not all nominees will
be able to accept the nomination.=20


2) Local office hours
-----------------------

In order facilitate additional feedback, the Nomcom has decided to make
themselves available for office areas at various geographic locations
for
3 weeks in September, starting on the 8th.=20

Below please find the list of locations where Nomcom members will be
available for these f2f meetings . Unless dates are identified below,
the
Nomcom member is generally available for part of the day during the
weeks
of Sept 8-11, Sept 14-18 and Sept 21-25. Also, languages other than
English in which the Nomcom member is fluent are identfied. =20

Please contact a Nomcom member in a specific geographic location to
arrange a convenient meeting time and place. Most Nomcom members are
flexible as to meeting locations - i.e., we can travel to your office,
meet at our offices or somewhere in between. =20

As a reminder folks can always contact any Nomcom member to provide
feedback at anytime - i.e., you don't need to participate in these f2f
sessions to provide feedback.=20


Belgium:=20
     Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept
21-25) (Languages: French)=20

Boston, Mass, USA: =20
     Stephen Kent - kent@bbn.com  (Sept 16-18)=20

Boulder, CO, USA:=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 14-18)

Dallas/Ft. Worth, TX, USA: =20
     Mary Barnes  - mary.h.barnes@gmail.com=20
     Lucy Yong - lucyyong@huawei.com  (Languages: Chinese)=20

Helsinki, Finland:=20
      Simo Veikkolainen - simo.veikkolainen@nokia.com (Languages:
Finnish)
=20

Ithaca, NY, USA:=20
      Scott Brim - scott.brim@gmail.com

Montevideo, Uruguay:=20
      Roque Gagliano - roque@lacnic.net (Sept 14-18, 21-25) (Languages:
Spanish, Portuguese)=20

Montreal, Quebec, Canada=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 8-11)
     -- Can also be available in Ottawa if folks are interested=20

Paris, France:=20
      Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept 15-18)  (Languages: French)

San Diego, CA, USA:=20
      Randall Gellens - rg+ietf@qualcomm.com  =20
      Dave Crocker - dcrocker@bbiw.net  (Sept 16-18)

Silicon Valley/SF Bay,  CA, USA:=20
      Dave Crocker - dcrocker@bbiw.net  (Sept 8-11, Sept 14-15, Sept
21-25)  =20
      Dorothy Gellert - Dorothy.gellert@gmail.com

3) Questionnaires available for nominees:=20

For folks that have been notified that they have been nominated for any
of the positions, the questionnaires are now available on the Nomcom09
tools website:
https://wiki.tools.ietf.org/group/nomcom/09/iab-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iaoc-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iesg-questionnaire

If you have any questions, please let me know. I will be contacting
everyone individually, as well as sending reminders.=20


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From root@core3.amsl.com  Tue Sep 15 11:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: nea@ietf.org
Delivered-To: nea@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 6EFBA28C130; Tue, 15 Sep 2009 11:00:01 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090915180001.6EFBA28C130@core3.amsl.com>
Date: Tue, 15 Sep 2009 11:00:01 -0700 (PDT)
Cc: nea@ietf.org
Subject: [Nea] WG Review: Recharter of Network Endpoint Assessment (nea)
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 18:00:01 -0000

A modified charter has been submitted for the Network Endpoint Assessment
(nea) working group in the Security Area of the IETF.  The IESG has not
made any determination as yet.  The modified charter is provided below for
informational purposes only.  Please send your comments to the IESG
mailing list (iesg@ietf.org) by Tuesday, September 22, 2009.

Network Endpoint Assessment (nea)
------------------------------------------------------------
Last Modified: 2009-08-24

Additional information is available at tools.ietf.org/wg/nea
Chair(s):

    * Stephen Hanna (shanna@juniper.net)
    * Susan Thomson (sethomso@cisco.com)

Security Area Director(s):

    * Tim Polk (tim.polk@nist.gov)
    * Pasi Eronen (pasi.eronen@nokia.com)

Security Area Advisor:

    * Tim Polk (tim.polk@nist.gov)

Mailing Lists:
General Discussion: nea@ietf.org
To Subscribe: http://www.ietf.org/mailman/listinfo/nea
Archive: http://www.ietf.org/mail-archive/web/nea

Description of Working Group:

Network Endpoint Assessment (NEA) architectures have been implemented
in the industry to assess the "posture" of endpoint devices for the
purposes of monitoring compliance to an organization's posture policy
and optionally restricting access until the endpoint has been updated
to satisfy the posture requirements. An endpoint that does not comply
with posture policy may be vulnerable to a number of known threats 
that may exist on the network. The intent of NEA is to facilitate 
corrective actions to address these known vulnerabilities before a 
host is exposed to potential attack. Note that an endpoint that is 
deemed compliant may still be vulnerable to threats that may exist on 
the network. The network may thus continue to be exposed to such 
threats as well as the range of other threats not addressed by 
maintaining endpoint compliance.

Posture refers to the hardware or software configuration of an endpoint
as it pertains to an organization's security policy. Posture may
include knowledge that software installed to protect the machine (e.g.
patch management software, anti-virus software, host firewall software,
host intrusion protection software or any custom software) is enabled
and up-to-date. An endpoint supporting NEA protocols can be queried for
posture information.

An organization may make a range of policy decisions based on the
posture of an endpoint. NEA is not intended to be prescriptive in this
regard. Supported deployment scenarios will include, but are not
limited to, providing normal access regardless of compliance result
along with any recommendations for remediation ("advisory mode"), as
well as providing restricted access sufficient for remediation purposes
and any essential services until an endpoint is in compliance
("mandatory mode"). Specifying mechanisms for providing restricted
access is outside the scope of the NEA WG.

Since NEA involves many different components from different vendors,
interoperability is important. The NEA working group will
develop standard protocols at the following three  layers in the 
architecture: the Posture Attribute protocol (PA),  the Posture Broker 
protocol (PB), and the Posture Transport protocol (PT). PA and PB will 
be  designed to support a variety of PT protocols. Together,  PA, PB 
and the mandatory to implement PT protocols will allow interoperability 
between an NEA Client from one vendor and an NEA Server from another.

Since there are already several non-standard protocols at these
layers, the NEA working group will consider these existing protocols as
candidates for the standard protocols. A requirements document will be
written and used as a basis for evaluating the candidate protocols. The
working group may decide to standardize one of the candidate protocols,
use one of them as a basis for a new or revised protocol, or decide
that a new protocol is needed.

The NEA Requirements document will include a problem statement,
definition of terms, requirements for the PA and PB protocols, and an
overall security analysis. It will also include generic requirements
for the protocol transporting PA, PB: the Posture Transport protocol
(PT).

The PA (Posture Attribute) protocol consists of posture attributes that
are carried between a particular Posture Collector in a NEA client and
a particular Posture Validator in a NEA Server. The PA protocol is
carried inside the PB protocol. A base set of standard posture
attributes will be specified that are expected to address many common
posture policies. Vendor-specific attributes will also be supported;
vendor-specific attributes will be identified by a private enterprise
number and a vendor assigned value. Vendors are strongly encouraged to
document vendor-specific attributes in an RFC. The NEA WG will
investigate the use of a standard syntax for all attributes.

The PB (Posture Broker) protocol aggregates posture attributes from one
or more Posture Collectors in an NEA client and sends them to the NEA
server for assessment by one or more Posture Validators.

The PT (Posture Transport) protocol carries the PB protocol. The 
expectation is that the PT protocol is a shim protocol that defines an 
encapsulation of PB within an existing standard transport protocol. 
Existing standard transport protocols will be leveraged to the extent 
possible. The NEA WG may specify more than one PT to meet the 
requirements of different deployment scenarios. The NEA WG will specify 
at least one mandatory to implement PT protocol. PT protocol 
specifications must describe any limitations that they impose on PB and 
PA (e.g. half duplex).

One commonly discussed issue with NEA systems is how to handle
compromised endpoints, whose reports of their own posture may not be
accurate. Detecting or handling such endpoints is out of scope of the
NEA WG. Work on PA will focus on attributes useful for assessing
posture of those endpoints reporting accurate information. However, the
protocols developed by the NEA WG must be designed to accommodate
emerging technologies for identifying and dealing with lying endpoints.

Note that NEA is not chartered to develop standard protocols for
remediation. NEA is intended to be used with new or existing tools that
can be used in the absence of NEA. NEA is applicable to computing
enterprise environments, where endpoints accessing the enterprise's
network are owned and/or expected to conform to the policies set forth
by the organization that owns and operates the network. All other
cases are outside the scope of the NEA charter, since we do not know
that NEA would be useful in such cases. NEA applicability and security
considerations will be described in the appropriate NEA documents.

Further work in the NEA WG will be considered via the rechartering
process after the completion of these milestones.


Milestones

Done      At IETF 67, discuss issues with NEA Requirements I-D
Done      Submit first draft of NEA Requirements I-D
Done      At IETF 68, resolve any open issues with requirements I-D
Done      Submit revised NEA requirements I-D
Done      Discuss NEA Requirements I-D
Done      Submit revised NEA requirements I-D
Done      WGLC on NEA requirements I-D
Done      At IETF 69, resolve any remaining issues raised at Last Call
Done      Submit revised NEA requirements I-D
Done      Submit NEA Requirements I-D to the IESG for IETF Last Call as 
           Informational RFC
Done      Submit revised NEA requirements I-D
Done      Proposals for PA and PB due
Done      Review and resolve proposals at IETF 71
Done      Post first WG version of PA and PB
Done      Post second version of PA and PB
Done      Resolve issues at IETF 72
Done      Post third version of PA and PB
Done      WGLC on PA and PB
Done      Resolve WGLC comments at IETF 73
Done      Post fourth version of PA and PB
Done      IETF LC for PA and PB
Done      IESG considers PA and PB for Proposed Standard
Sep 2009  Call for proposals for the PT protocol(s)
Oct 2009  Proposals due
Nov 2009  Review PT protocol proposals at IETF 76
          Decide how to resolve differences and issues
Dec 2009  Post first WG version of PT protocol(s)
Jan 2010  Review and resolve issues
Feb 2010  Post second WG version of PT protocol(s)
Mar 2010  WG Last Call on PT protocol(s)
          Resolve issues from WG Last Call at IETF 77
Apr 2010  Post third WG version of PT protocol(s)
May 2010  Submit PT protocol(s) to IESG

From root@core3.amsl.com  Wed Sep 16 13:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: nea@ietf.org
Delivered-To: nea@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B95A03A6894; Wed, 16 Sep 2009 13:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090916201501.B95A03A6894@core3.amsl.com>
Date: Wed, 16 Sep 2009 13:15:01 -0700 (PDT)
Cc: nea@ietf.org
Subject: [Nea] I-D Action:draft-ietf-nea-pb-tnc-05.txt
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2009 20:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Endpoint Assessment Working Group of the IETF.


	Title           : PB-TNC: A Posture Broker Protocol (PB) Compatible with TNC
	Author(s)       : R. Sahita, et al.
	Filename        : draft-ietf-nea-pb-tnc-05.txt
	Pages           : 79
	Date            : 2009-09-16

This document specifies PB-TNC, a Posture Broker Protocol identical 
to the Trusted Computing Group's IF-TNCCS 2.0 protocol.  The document 
then evaluates PB-TNC against the requirements defined in the NEA 
Requirements specification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nea-pb-tnc-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-nea-pb-tnc-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-09-16130506.I-D@ietf.org>


--NextPart--

From shanna@juniper.net  Wed Sep 16 13:23:19 2009
Return-Path: <shanna@juniper.net>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AC623A6805 for <nea@core3.amsl.com>; Wed, 16 Sep 2009 13:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rdXcA4+Lkphl for <nea@core3.amsl.com>; Wed, 16 Sep 2009 13:23:18 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by core3.amsl.com (Postfix) with ESMTP id 4C5563A681D for <nea@ietf.org>; Wed, 16 Sep 2009 13:23:18 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKSrFJZZetZ7EOPSWUfgEoVQ8wykNFscyN@postini.com; Wed, 16 Sep 2009 13:24:08 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 16 Sep 2009 13:22:41 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 16 Sep 2009 16:22:40 -0400
From: Stephen Hanna <shanna@juniper.net>
To: NEA <nea@ietf.org>
Date: Wed, 16 Sep 2009 16:20:55 -0400
Thread-Topic: New version of PB-TNC posted (-05)
Thread-Index: Aco3CzGcqexqKz8aRQyl/1CYMSTYQw==
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D257A1@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Nea] New version of PB-TNC posted (-05)
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2009 20:23:19 -0000

I just posted a new version of PB-TNC: draft-ietf-nea-pb-tnc-05.txt.
This version includes a variety of changes to address IESG comments.
The list of changes is below. As you can see, the IESG and the
document editors have been busy for the last few months!

Since some of these changes are significant, we plan to run another
WGLC on this draft to make sure that the NEA Working Group has
consensus that these changes should be made. However, we will
not start the WGLC until we have heard from the IESG that their
concerns have been addressed. There's no reason to call on all
WG members to review the -05 version if we're just going to
need to post a -06 version shortly with more changes!

So look out for another email in a few weeks, asking for a WGLC.
And thanks to the IESG for bringing some new perspectives to
the document review. The document is certainly improved because
of their review.

Thanks,

Steve

--------

Summary of differences between PB-TNC -04 and -05

* Tightened up error handling, changing many SHOULDs to MUSTs
* Added CLOSE batch type to gracefully signal close and
  carry fatal errors
* Added additional PT requirements in new section 3.3.1
* Removed Retry-Acknowledge bit since no longer needed
* Added language tag to Remediation-String
* Changed language tag length from 32 bits to 8 bits
* Fixed to allow several IDs per Posture Collector/Validator
* Minor clarifications and fixes
* Added normative reference for RFC 3629 (UTF-8)
* Added acknowledgment for Trusted Computing Group (TCG)
* Removed discussion of relationship with TCG
* Fixed IANA Considerations

From shanna@juniper.net  Thu Sep 17 09:59:56 2009
Return-Path: <shanna@juniper.net>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B86C428C194 for <nea@core3.amsl.com>; Thu, 17 Sep 2009 09:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level: 
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MC1Wd5LZafdn for <nea@core3.amsl.com>; Thu, 17 Sep 2009 09:59:45 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 1BA213A6BBC for <nea@ietf.org>; Thu, 17 Sep 2009 09:59:45 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKSrJrM0Gv9xwZhXnDTY8qYVWTENuITAvl@postini.com; Thu, 17 Sep 2009 10:00:37 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.1.375.2; Thu, 17 Sep 2009 09:58:24 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 17 Sep 2009 12:58:24 -0400
From: Stephen Hanna <shanna@juniper.net>
To: NEA <nea@ietf.org>
Date: Thu, 17 Sep 2009 12:56:39 -0400
Thread-Topic: IESG query re Expert Review
Thread-Index: Aco3t9Lo9ZUC6SRoT+GVXyI6k+aB4A==
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D2601B@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: [Nea] IESG query re Expert Review
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2009 16:59:56 -0000

Alexey Melnikov (APP AD) has provided many useful comments
on PA-TNC and PB-TNC. One issue that he has raised is
whether Expert Review should be required for IANA registration
of vendor-specific values in the NEA registries and, if so,
what the expert guidelines should be. Alexey has asked the
NEA WG to reconsider and discuss this matter. Therefore,
I'm raising this topic on the NEA list and cc'ing Alexey.

The text in draft-ietf-nea-pb-tnc-05.txt on this matter
is in section 7.1:

>    For all of the IANA registries defined by this specification, =20
>    new values are added to the registry by Expert Review with =20
>    Specification Required, using the Designated Expert process =20
>    defined in RFC 5226 [3]. =20
>
>    This section provides guidance to designated experts so that =20
>    they may make decisions using a philosophy appropriate for these =20
>    registries.
>
> [snip]
>
>    All values in these IANA registries MUST be =20
>    documented in a specification that is clear, permanently and =20
>    publicly available, and likely to ensure interoperability. IETF =20
>    standard values MUST be useful and not harmful to the Internet. =20
>
>    Designated experts should encourage vendors to avoid defining =20
>    similar but incompatible values and instead agree on a single =20
>    IETF standard value.  However, it is beneficial to document =20
>    existing practice. =20

I will let Alexey make the full case for removing the requirement
for expert review of vendor-specific values. I think that the main
thrust of the argument is that we should encourage vendors to
document the values that they use.

Thanks,

Steve

From shanna@juniper.net  Thu Sep 17 10:03:36 2009
Return-Path: <shanna@juniper.net>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BD9C28C166 for <nea@core3.amsl.com>; Thu, 17 Sep 2009 10:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.272
X-Spam-Level: 
X-Spam-Status: No, score=-6.272 tagged_above=-999 required=5 tests=[AWL=-0.273, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fswz6OPdZmd2 for <nea@core3.amsl.com>; Thu, 17 Sep 2009 10:03:35 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id 644EF3A6BC6 for <nea@ietf.org>; Thu, 17 Sep 2009 10:03:35 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKSrJsGOTUsYewKpsTg2hLZ+U9quOlASEk@postini.com; Thu, 17 Sep 2009 10:04:27 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.1.375.2; Thu, 17 Sep 2009 10:03:21 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 17 Sep 2009 13:03:20 -0400
From: Stephen Hanna <shanna@juniper.net>
To: NEA <nea@ietf.org>
Date: Thu, 17 Sep 2009 13:01:35 -0400
Thread-Topic: IESG query re Expert Review
Thread-Index: Aco3t9Lo9ZUC6SRoT+GVXyI6k+aB4AAAHU+w
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D26031@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: [Nea] IESG query re Expert Review
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2009 17:03:36 -0000

One correction to my email. The text that I quoted is in
section 6.1 of PB-TNC. It's also in section 7.1 of PA-TNC.
I got mixed up because both documents have the same text.

Thanks,

Steve

> -----Original Message-----
> From: Stephen Hanna=20
> Sent: Thursday, September 17, 2009 12:57 PM
> To: NEA
> Cc: 'Alexey Melnikov'
> Subject: IESG query re Expert Review
>=20
> Alexey Melnikov (APP AD) has provided many useful comments
> on PA-TNC and PB-TNC. One issue that he has raised is
> whether Expert Review should be required for IANA registration
> of vendor-specific values in the NEA registries and, if so,
> what the expert guidelines should be. Alexey has asked the
> NEA WG to reconsider and discuss this matter. Therefore,
> I'm raising this topic on the NEA list and cc'ing Alexey.
>=20
> The text in draft-ietf-nea-pb-tnc-05.txt on this matter
> is in section 7.1:
>=20
> >    For all of the IANA registries defined by this specification, =20
> >    new values are added to the registry by Expert Review with =20
> >    Specification Required, using the Designated Expert process =20
> >    defined in RFC 5226 [3]. =20
> >
> >    This section provides guidance to designated experts so that =20
> >    they may make decisions using a philosophy appropriate=20
> for these =20
> >    registries.
> >
> > [snip]
> >
> >    All values in these IANA registries MUST be =20
> >    documented in a specification that is clear, permanently and =20
> >    publicly available, and likely to ensure interoperability. IETF =20
> >    standard values MUST be useful and not harmful to the Internet. =20
> >
> >    Designated experts should encourage vendors to avoid defining =20
> >    similar but incompatible values and instead agree on a single =20
> >    IETF standard value.  However, it is beneficial to document =20
> >    existing practice. =20
>=20
> I will let Alexey make the full case for removing the requirement
> for expert review of vendor-specific values. I think that the main
> thrust of the argument is that we should encourage vendors to
> document the values that they use.
>=20
> Thanks,
>=20
> Steve
> =

From tglassey@earthlink.net  Thu Sep 17 11:49:10 2009
Return-Path: <tglassey@earthlink.net>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12E423A6851; Thu, 17 Sep 2009 11:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level: 
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjleeQ1d-Ec1; Thu, 17 Sep 2009 11:49:09 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id 27B343A69B1; Thu, 17 Sep 2009 11:48:57 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=qDZi7ddlGVXoNxnHRgIM+XMuKy9BfSNpPZLAOecqr5SR667tpMJBJuIicRh1cRYE; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.66] (helo=[192.168.1.100]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1MoM3A-0007AG-Vs; Thu, 17 Sep 2009 14:49:49 -0400
Message-ID: <4AB284CD.1080500@earthlink.net>
Date: Thu, 17 Sep 2009 11:49:49 -0700
From: Todd Glassey <tglassey@earthlink.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Stephen Hanna <shanna@juniper.net>
References: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D2601B@EMBX01-WF.jnpr.net>
In-Reply-To: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D2601B@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79d95e8d357e96996b664335bfbcf49e59350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.66
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, NEA <nea@ietf.org>, "ipr-wg@ietf.org" <ipr-wg@ietf.org>
Subject: Re: [Nea] IESG query re Expert Review
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2009 18:49:10 -0000

Stephen Hanna wrote:
> Alexey Melnikov (APP AD) has provided many useful comments
> on PA-TNC and PB-TNC. One issue that he has raised is
> whether Expert Review should be required for IANA registration
> of vendor-specific values in the NEA registries and, if so,
> what the expert guidelines should be. Alexey has asked the
> NEA WG to reconsider and discuss this matter. Therefore,
> I'm raising this topic on the NEA list and cc'ing Alexey.
>
> The text in draft-ietf-nea-pb-tnc-05.txt on this matter
> is in section 7.1:
>   
Sorry not possible... the type of thing that Alexey is asking for is 
legally impossible for the IETF to do with the Use License in the 
current state its in and since all of NEA to date has been published 
under that its a bit late to be thinking about doing anything to 
interfere with how people use IETF protocols.

A simpler way to do this would be to change the IETF copyright so that 
it forces the implementor to implement the standard per the Use 
Statement which is really what Alexey is talking about but since most 
all IETF protocols dont have best-practice use models with their 
specifications this also would be a pain.

The problem for NEA and all other WG's today is that NO ONE is forced to 
implement the entire part of a IETF standard to declare they are IETF 
compliant because of the ANY AND ALL USES clause in the license. They 
dont even have to claim their product passed interoperability testing to 
claim their IETF compliant because of that specific language.

Todd Glassey
>   
>>    For all of the IANA registries defined by this specification,  
>>    new values are added to the registry by Expert Review with  
>>    Specification Required, using the Designated Expert process  
>>    defined in RFC 5226 [3].  
>>
>>    This section provides guidance to designated experts so that  
>>    they may make decisions using a philosophy appropriate for these  
>>    registries.
>>
>> [snip]
>>
>>    All values in these IANA registries MUST be  
>>    documented in a specification that is clear, permanently and  
>>    publicly available, and likely to ensure interoperability. IETF  
>>    standard values MUST be useful and not harmful to the Internet.  
>>
>>    Designated experts should encourage vendors to avoid defining  
>>    similar but incompatible values and instead agree on a single  
>>    IETF standard value.  However, it is beneficial to document  
>>    existing practice.  
>>     
>
> I will let Alexey make the full case for removing the requirement
> for expert review of vendor-specific values. I think that the main
> thrust of the argument is that we should encourage vendors to
> document the values that they use.
>
> Thanks,
>
> Steve
> _______________________________________________
> Nea mailing list
> Nea@ietf.org
> https://www.ietf.org/mailman/listinfo/nea
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.409 / Virus Database: 270.13.103/2378 - Release Date: 09/17/09 06:18:00
>
>   


From alexey.melnikov@isode.com  Thu Sep 17 14:43:36 2009
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 027983A6AF1 for <nea@core3.amsl.com>; Thu, 17 Sep 2009 14:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gln35W9t6vZo for <nea@core3.amsl.com>; Thu, 17 Sep 2009 14:43:35 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 771063A6AB2 for <nea@ietf.org>; Thu, 17 Sep 2009 14:43:30 -0700 (PDT)
Received: from [94.197.226.87] (94.197.226.87.threembb.co.uk [94.197.226.87])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SrKtqwB9YROb@rufus.isode.com>; Thu, 17 Sep 2009 22:44:11 +0100
Message-ID: <4AB2AD9F.7030107@isode.com>
Date: Thu, 17 Sep 2009 22:43:59 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Stephen Hanna <shanna@juniper.net>
References: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D2601B@EMBX01-WF.jnpr.net>
In-Reply-To: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D2601B@EMBX01-WF.jnpr.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 17 Sep 2009 14:58:15 -0700
Cc: NEA <nea@ietf.org>
Subject: Re: [Nea] IESG query re Expert Review
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2009 21:43:36 -0000

Stephen Hanna wrote:

>Alexey Melnikov (APP AD) has provided many useful comments
>on PA-TNC and PB-TNC. One issue that he has raised is
>whether Expert Review should be required for IANA registration
>of vendor-specific values in the NEA registries and, if so,
>what the expert guidelines should be. Alexey has asked the
>NEA WG to reconsider and discuss this matter. Therefore,
>I'm raising this topic on the NEA list and cc'ing Alexey.
>  
>
I am actually don't have a strong opinion on this, but I want to make 
sure that the WG has considered consequences of the choice.

>The text in draft-ietf-nea-pb-tnc-05.txt on this matter
>is in section 7.1:
>  
>
>>   For all of the IANA registries defined by this specification,  
>>   new values are added to the registry by Expert Review with  
>>   Specification Required, using the Designated Expert process  
>>   defined in RFC 5226 [3].  
>>
>>   This section provides guidance to designated experts so that  
>>   they may make decisions using a philosophy appropriate for these  
>>   registries.
>>
>>[snip]
>>
>>   All values in these IANA registries MUST be  
>>   documented in a specification that is clear, permanently and  
>>   publicly available, and likely to ensure interoperability. IETF  
>>   standard values MUST be useful and not harmful to the Internet.  
>>
>>   Designated experts should encourage vendors to avoid defining  
>>   similar but incompatible values and instead agree on a single  
>>   IETF standard value.  However, it is beneficial to document  
>>   existing practice.  
>>    
>>
>I will let Alexey make the full case for removing the requirement
>for expert review of vendor-specific values. I think that the main
>thrust of the argument is that we should encourage vendors to
>document the values that they use.
>  
>
Indeed.

The situation I have in mind is as follows: Assume a vendor A implements 
some vendor specific attributes. The implementation becomes widespread 
and other implementations would like to implement it as well. Then 
somebody not working for vendor A convinces an A's representative to 
register the attributes as a favor to the community. The A's 
representative tries to do that, but either the documentation is not 
quite clear on some details, or it is not always interoperable.
At this point the registration procedure says that the expert should 
reject the registration. The A's representative doesn't feel obligated 
to fix documentation, because the registration was submitted as a 
service to the community. So, would rejecting the registration in such a 
case be worse than registering something which is not perfect?

If the WG group agrees that this might be a problem, then there are 2 
ways to fix this:
a). you update the text to relax instructions for the designated Expert 
Reviewer
or
b). the WG can select an Expert Reviewer who is quite relaxed about the 
rules and would be flexible about allowing not-fully-compliant vendor 
specific registrations. In this case you don't need to change the 
document, but there is a small risk that the designated expert wouldn't 
be as flexible.

Best Regards,
Alexey


From paul.hoffman@vpnc.org  Fri Sep 25 09:34:29 2009
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: nea@core3.amsl.com
Delivered-To: nea@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91C1A3A68D4 for <nea@core3.amsl.com>; Fri, 25 Sep 2009 09:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.161
X-Spam-Level: 
X-Spam-Status: No, score=-5.161 tagged_above=-999 required=5 tests=[AWL=0.885,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eR2gYM42fkI for <nea@core3.amsl.com>; Fri, 25 Sep 2009 09:34:28 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id B4B233A67D8 for <nea@ietf.org>; Fri, 25 Sep 2009 09:34:28 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8PGZben095191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Sep 2009 09:35:39 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240846c6e29d572d85@[10.20.30.158]>
In-Reply-To: <4AB2AD9F.7030107@isode.com>
References: <AC6674AB7BC78549BB231821ABF7A9AE8FF1D2601B@EMBX01-WF.jnpr.net> <4AB2AD9F.7030107@isode.com>
Date: Fri, 25 Sep 2009 09:35:36 -0700
To: Alexey Melnikov <alexey.melnikov@isode.com>, Stephen Hanna <shanna@juniper.net>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: NEA <nea@ietf.org>
Subject: Re: [Nea] IESG query re Expert Review
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 16:34:29 -0000

Alexey makes some very good points here.

At 10:43 PM +0100 9/17/09, Alexey Melnikov wrote:
>The situation I have in mind is as follows: Assume a vendor A implements some vendor specific attributes. The implementation becomes widespread and other implementations would like to implement it as well. Then somebody not working for vendor A convinces an A's representative to register the attributes as a favor to the community. The A's representative tries to do that, but either the documentation is not quite clear on some details, or it is not always interoperable.
>At this point the registration procedure says that the expert should reject the registration. The A's representative doesn't feel obligated to fix documentation, because the registration was submitted as a service to the community. So, would rejecting the registration in such a case be worse than registering something which is not perfect?

>From the experience in other Security WGs, this scenario is both possible and unfortunate. Worse, people will disagree with the answer to the last question and will waste a lot of time that could be used more productively.

>If the WG group agrees that this might be a problem, then there are 2 ways to fix this:
>a). you update the text to relax instructions for the designated Expert Reviewer
>or
>b). the WG can select an Expert Reviewer who is quite relaxed about the rules and would be flexible about allowing not-fully-compliant vendor specific registrations. In this case you don't need to change the document, but there is a small risk that the designated expert wouldn't be as flexible.

Relying on (b) for the long term is not a good strategy. I think (a) is much better. Really, the stability of the vendor's text is way more important than the correctness. If the text is bad, anyone who cares will reverse-engineer it through testing with the vendor's product, and if they're really nice, will encourage the vendor to update it.

--Paul Hoffman, Director
--VPN Consortium

From root@core3.amsl.com  Tue Sep 29 11:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: nea@ietf.org
Delivered-To: nea@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 91E233A6910; Tue, 29 Sep 2009 11:45:01 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090929184501.91E233A6910@core3.amsl.com>
Date: Tue, 29 Sep 2009 11:45:01 -0700 (PDT)
Cc: nea@ietf.org
Subject: [Nea] WG Action: RECHARTER: Network Endpoint Assessment (nea)
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2009 18:45:01 -0000

The charter of the Network Endpoint Assessment (nea) working group in the
Security Area of the IETF has been updated.  For additional information,
please contact the Area Directors or the working group Chairs.

Network Endpoint Assessment (nea)
---------------------------------
Last Modified: 2009-09-29

Additional information is available at tools.ietf.org/wg/nea
Chair(s):

Stephen Hanna <shanna@juniper.net>
Susan Thomson <sethomso@cisco.com>

Security Area Director(s):

Tim Polk <tim.polk@nist.gov>
Pasi Eronen <pasi.eronen@nokia.com>

Security Area Advisor:

Tim Polk <tim.polk@nist.gov>

Mailing Lists:
General Discussion: nea@ietf.org
To Subscribe: http://www.ietf.org/mailman/listinfo/nea
Archive: http://www.ietf.org/mail-archive/web/nea

Description of Working Group:

Network Endpoint Assessment (NEA) architectures have been implemented
in the industry to assess the "posture" of endpoint devices for the
purposes of monitoring compliance to an organization's posture policy
and optionally restricting access until the endpoint has been updated
to satisfy the posture requirements. An endpoint that does not comply
with posture policy may be vulnerable to a number of known threats that
may exist on the network. The intent of NEA is to facilitate corrective
actions to address these known vulnerabilities before a host is exposed
to potential attack. Note that an endpoint that is deemed compliant may
still be vulnerable to threats that may exist on the network. The
network may thus continue to be exposed to such threats as well as the
range of other threats not addressed by maintaining endpoint
compliance.

Posture refers to the hardware or software configuration of an endpoint
as it pertains to an organization's security policy. Posture may
include knowledge that software installed to protect the machine (e.g.
patch management software, anti-virus software, host firewall software,
host intrusion protection software or any custom software) is enabled
and up-to-date. An endpoint supporting NEA protocols can be queried for
posture information.

An organization may make a range of policy decisions based on the
posture of an endpoint. NEA is not intended to be prescriptive in this
regard. Supported deployment scenarios will include, but are not
limited to, providing normal access regardless of compliance result
along with any recommendations for remediation ("advisory mode"), as
well as providing restricted access sufficient for remediation purposes
and any essential services until an endpoint is in compliance
("mandatory mode"). Specifying mechanisms for providing restricted
access is outside the scope of the NEA WG.

Since NEA involves many different components from different vendors,
interoperability is important. The NEA working group will
develop standard protocols at the following three  layers in the
architecture:
the Posture Attribute protocol (PA),  the Posture Broker protocol
(PB), and the Posture Transport protocol (PT). PA and PB will be
designed to
support a variety of PT protocols. Together,  PA, PB and the mandatory to
implement PT protocols will allow interoperability between an NEA Client
from one vendor and an NEA Server from another.

Since there are already several non-standard protocols at these
layers, the NEA working group will consider these existing protocols as
candidates for the standard protocols. A requirements document will be
written and used as a basis for evaluating the candidate protocols. The
working group may decide to standardize one of the candidate protocols,
use one of them as a basis for a new or revised protocol, or decide
that a new protocol is needed.

The NEA Requirements document will include a problem statement,
definition of terms, requirements for the PA and PB protocols, and an
overall security analysis. It will also include generic requirements
for the protocol transporting PA, PB: the Posture Transport protocol
(PT).

The PA (Posture Attribute) protocol consists of posture attributes that
are carried between a particular Posture Collector in a NEA client and
a particular Posture Validator in a NEA Server. The PA protocol is
carried inside the PB protocol. A base set of standard posture
attributes will be specified that are expected to address many common
posture policies. Vendor-specific attributes will also be supported;
vendor-specific attributes will be identified by a private enterprise
number and a vendor assigned value. Vendors are strongly encouraged to
document vendor-specific attributes in an RFC. The NEA WG will
investigate the use of a standard syntax for all attributes.

The PB (Posture Broker) protocol aggregates posture attributes from one
or more Posture Collectors in an NEA client and sends them to the NEA
server for assessment by one or more Posture Validators.

The PT (Posture Transport) protocol carries the PB protocol. The
expectation
is that the PT protocol is a shim protocol that defines an
encapsulation of PB
within an existing standard transport protocol. Existing standard
transport
protocols will be leveraged to the extent possible. The NEA WG may specify
more than one PT to meet the requirements of different deployment
scenarios.
The NEA WG will specify at least one mandatory to implement PT protocol.
PT protocol specifications must describe any limitations
that they impose on PB and PA (e.g. half duplex).

One commonly discussed issue with NEA systems is how to handle
compromised endpoints, whose reports of their own posture may not be
accurate. Detecting or handling such endpoints is out of scope of the
NEA WG. Work on PA will focus on attributes useful for assessing
posture of those endpoints reporting accurate information. However, the
protocols developed by the NEA WG must be designed to accommodate
emerging technologies for identifying and dealing with lying endpoints.

Note that NEA is not chartered to develop standard protocols for
remediation. NEA is intended to be used with new or existing tools that
can be used in the absence of NEA. NEA is applicable to computing
enterprise environments, where endpoints accessing the enterprise's
network are owned and/or expected to conform to the policies set forth
by the organization that owns and operates the network. All other
cases are outside the scope of the NEA charter, since we do not know
that NEA would be useful in such cases. NEA applicability and security
considerations will be described in the appropriate NEA documents.

Further work in the NEA WG will be considered via the rechartering
process after the completion of these milestones.
Goals and Milestones:
Done At IETF 67, discuss issues with NEA Requirements I-D
Done Submit first draft of NEA Requirements I-D
Done At IETF 68, resolve any open issues with requirements I-D
Done Submit revised NEA requirements I-D
Done Discuss NEA Requirements I-D
Done Submit revised NEA requirements I-D
Done WGLC on NEA requirements I-D
Done At IETF 69, resolve any remaining issues raised at Last Call
Done Submit revised NEA requirements I-D
Done Submit NEA Requirements I-D to the IESG for IETF Last Call as
Informational RFC
Done Submit revised NEA requirements I-D
Done Proposals for PA and PB due
Done Review and resolve proposals at IETF 71
Done Post first WG version of PA and PB
Done Post second version of PA and PB
Done Resolve issues at IETF 72
Done Post third version of PA and PB
Done WGLC on PA and PB
Done Resolve WGLC comments at IETF 73
Done Post fourth version of PA and PB
Done IETF LC for PA and PB
Done IESG considers PA and PB for Proposed Standard
Sep 2009 Call for proposals for the PT protocol(s)
Oct 2009 Proposals due
Nov 2009 Review PT protocol proposals at IETF 76 Decide how to resolve
differences and issues
Dec 2009 Post first WG version of PT protocol(s)
Jan 2010 Review and resolve issues
Feb 2010 Post second WG version of PT protocol(s)
Mar 2010 WG Last Call on PT protocol(s) Resolve issues from WG Last Call
at IETF 77
Apr 2010 Post third WG version of PT protocol(s)
May 2010 Submit PT protocol(s) to IESG
