From nea-bounces@ietf.org  Wed Jun  4 14:16:08 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 464D43A6D19;
	Wed,  4 Jun 2008 14:16:08 -0700 (PDT)
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 968653A6CBB
	for <nea@core3.amsl.com>; Wed,  4 Jun 2008 14:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[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 xiovMTb8WMRR for <nea@core3.amsl.com>;
	Wed,  4 Jun 2008 14:16:05 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167])
	by core3.amsl.com (Postfix) with ESMTP id 840F73A6A75
	for <nea@ietf.org>; Wed,  4 Jun 2008 14:16:01 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob107.postini.com
	([64.18.6.12]) with SMTP; Wed, 04 Jun 2008 14:15:59 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp55.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Jun 2008 14:15:36 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 4 Jun 2008 17:14:45 -0400
Message-ID: <A6398B0DB62A474C82F61554EE937287057D007B@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Process for comments on PA-TNC and PB-TNC
Thread-Index: AcjFnacPWSiKQycCSlytG88ju+fSrgAyisPwAAfdYrA=
From: "Stephen Hanna" <shanna@juniper.net>
To: <nea@ietf.org>
X-OriginalArrivalTime: 04 Jun 2008 21:15:36.0402 (UTC)
	FILETIME=[21BE2320:01C8C688]
Subject: [Nea] Process for comments on PA-TNC and PB-TNC
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

Now that the PA-TNC and PB-TNC drafts are WG drafts,
it's time to start beating them into shape: gathering
comments, discussing them and agreeing on resolutions,
and so forth.

We have already received several very good comments
on these specifications (sent to the NEA list back in
February and March). The spec editors will kick off
the discussion process by starting some discussion
threads based on these comments. Please participate
in these threads so we can reach consensus on the
best way to resolve these comments.

If you have more comments on the specs, please send
them to the NEA list by July 1. That will give us
two weeks to discuss your comments and reach WG
consensus on them before the July 14 deadline for
non -00 submissions in advance of IETF 72.

Thanks,

Steve
_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea


From nea-bounces@ietf.org  Thu Jun  5 17:12:23 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91F7A3A6A42;
	Thu,  5 Jun 2008 17:12:23 -0700 (PDT)
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 547A13A67A5
	for <nea@core3.amsl.com>; Thu,  5 Jun 2008 17:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[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 HI2oS24C1blD for <nea@core3.amsl.com>;
	Thu,  5 Jun 2008 17:12:22 -0700 (PDT)
Received: from extu-mxob-2.symantec.com (extu-mxob-2.symantec.com
	[216.10.194.135])
	by core3.amsl.com (Postfix) with ESMTP id 8754A3A6A9F
	for <nea@ietf.org>; Thu,  5 Jun 2008 17:11:41 -0700 (PDT)
Received: from tus1opsmtapin02.ges.symantec.com
	(tus1opsmtapin02.ges.symantec.com [192.168.214.44])
	by extu-mxob-2.symantec.com (8.14.1/8.14.1) with ESMTP id
	m560BkCR022104
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 5 Jun 2008 17:11:49 -0700
Received: from reserved-155-64-230-18.ges.symantec.com ([155.64.230.18]
	helo=TUS1XCHECNPIN01.enterprise.veritas.com)
	by tus1opsmtapin02.ges.symantec.com with esmtp (Exim 4.67)
	(envelope-from <Paul_Sangster@symantec.com>)
	id 1K4PYY-0001yd-TH; Thu, 05 Jun 2008 17:11:46 -0700
Received: from TUS1XCHEVSPIN05.enterprise.veritas.com ([155.64.231.27]) by
	TUS1XCHECNPIN01.enterprise.veritas.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 5 Jun 2008 17:11:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 5 Jun 2008 17:11:25 -0700
Message-ID: <AB96CED633A7C246BDC661DBEE1CF01F03C8D1A2@TUS1XCHCLUPIN11.enterprise.veritas.com>
In-Reply-To: <C3EDA1A7.1B23%gtomlinson@SonicWALL.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Nea] Comments on draft-sangster-nea-pa-tnc-00..txt
Thread-Index: Ach7DB3PXIZmOOb/EdyVBwAbY6BmHBMWCTPw
References: <C3EDA1A7.1B23%gtomlinson@SonicWALL.com>
From: "Paul Sangster" <Paul_Sangster@symantec.com>
To: "Gary Tomlinson" <gtomlinson@SonicWALL.com>, <nea@ietf.org>
X-OriginalArrivalTime: 06 Jun 2008 00:11:47.0196 (UTC)
	FILETIME=[E8D70BC0:01C8C769]
Subject: Re: [Nea] Comments on draft-sangster-nea-pa-tnc-00..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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

Gary,

Thanks for the quick feedback on the spec.  I've provided some in-lined
comments and answers to some of your questions. 

> -----Original Message-----
> From: nea-bounces@ietf.org [mailto:nea-bounces@ietf.org] On 
> Behalf Of Gary Tomlinson
> Sent: Friday, February 29, 2008 11:49 AM
> To: nea@ietf.org
> Subject: [Nea] Comments on draft-sangster-nea-pa-tnc-00..txt
> 
> The following comments are regarding the individual 
> submission draft-sangster-nea-pa-tnc-00.txt of a PA protocol 
> for consideration by the NEA WG as a base to develop the PA 
> protocol from.
> 
> Again, I am impressed (like I was with the PB submission from 
> TNC) with the level of completeness in this proposal (no 
> doubt due to the maturity of the TNC work) and think it 
> warrants strong consideration by the WG as a starting point.

Thanks

> 
> As usual, I do have a number of specific comments.
> 
> First, I have a general comment regarding the IETF Vendor Id 
> value 0 as it is applied in this document.  I found having 
> repeated per IETF name space PA subtype (all those defined in 
> this specification) qualification to the IETF Vendor Id to be 
> redundant and make it harder to get to the chase of each PA 
> subtype structure.  Given section 2.4 clearly states all PA 
> subtypes defined in this document are applicable to only the 
> IETF vendor ID, I think it would be good to simplify the 
> prose per PA subtype and eliminate the interpretation of name 
> space qualification to Vendor Id 0. This comment does not 
> apply to Vendor ID usage within attribute types as there is a 
> need to distinguish at this level in cases such as page 36, 
> section 3.2.8.

So you're suggesting not repeatedly mentioning in the prose that vendor
id of 0 is IETF so save spec bloat?  We were trying to be complete in
the normative part of the spec (protocol definition) but if others agree
this is causing issues we could emphasize it more earlier in the spec
and remove those repeated comments.  Thoughts?

> 
> Page 10, section 2.4.  I can't find any definitions for the 
> PA subtypes in this document nor in any of the references.  
> Given these are being defined in the IETF name space, I think 
> it is necessary to eliminate ambiguity as I'd guess not 
> everyone in the WG has a consistent definition of them let 
> alone people outside this work group.  Ideally from my point 
> of view, a set informative references can be found that address this.

Do you have a reference in mind?  Clearly column 3 gives a very terse
definition of each one so it sounds like you would like something more
developed.  Suggestions are welcome particularly if they are used in
other standards (not sure wikipedia entries count :)).

> 
> Page 12, section 2.5 Message Identifier.  Why is the PA 
> protocol state machine not required to check for duplicate 
> identifiers if this is a protocol violation?  Not requiring 
> this seems like a recipe for trouble.

This was really just leaving it open for implementations to make this
decision.  I'm fine with removing that sentence if other agree with your
comment.  However the identifier is really for use by the sender so if
it mistakenly repeats an identifier its causing problems just for itself
(not the recipient).  For example if a sender incorrectly sends 2
messages during an assessment that have the same message identifier and
one causes an error, then when the sender gets the error message it
won't be able to properly use the identifier to know which message
caused the problem.  The recipients state machine isn't affected by this
number so thus doesn't need to check it.  However a robust
implementation may choose to check it to avoid potential assessment
issue by a poorly implemented peer.

> 
> Page 30, section 3.2.6.  Why is the Port Filter attribute 
> support restriction applied to VPN subtypes?  I can see it 
> being applied to layer 4 firewall collectors, but find VPN a 
> little muddy.  I realize many VPN clients do provide layer 4 
> port filtering, however I see that as a firewall service that 
> is being provided in addition to VPN, and as such would think 
> these components should register themselves as both a VPN and 
> a Firewall subtype.

The short answer is that the spec tries to identify what kinds of
attributes (e.g. Port Filter) are applicable to each type of component
type (e.g. VPN).  Many attributes don't make sense with certain types of
components so we call out the ones where we do believe they are
compatible.  This doesn't require that collectors for VPN components
MUST support this attribute but if the VPN supports a firewall (as many
do - and all IPsec VPNs MUST) then this attribute is applicable to the
VPN and therefore should be supported.

> 
> Page 32, section 3.2.6.  Why is there a restriction on mixed 
> blocked and non-blocked protocol/port pairs in a single port 
> filter list attribute?
> Each protocol/port element has its own flags field and thus 
> is capable of being unambiguously qualified as blocked or 
> non-blocked in the protocol.

See the following sentence which says: 

"To be more precise, a Posture Collector MUST NOT include two
Protocol/Port Number pairs in a single Port Filter attribute where the
protocol number is the same but the B flag is different."

This is requesting that there not be a entry saying "TCP port 80 is
allowed" followed by an entry saying "TCP port 80 is blocked" thus
creating an ambiguous policy (depends on how policy matching happens
during enforcement).

> 
> Pages 40-43, section 3.2.8.1. Just a nit here, but there is 
> inconsistency in the labeling of copied fields in the 
> diagrams.  Some are labeled "Copy of ..." and other and 
> simply "...".  All of them that are copies should be labeled 
> "Copy of...".

We can probably remove that rather then having "Copy of" all over the
place.  We were trying to emphasize that this reserved field is
different from the others (which need to be set of 0 and ignored).  I'll
remove "Copy of" if its too inconsistent.

> 
> Page 46, section 4.8.  What is the definition of typical 
> here?  Is it an observation from systems deployed in the 
> field today; and if so are they using a protocol similar to 
> PA-TNC?  Also, given PA-TNC allows vendor defined attributes 
> with who knows how much size, like say X.509 chains, I 
> suggest any mention of typical be qualified by use of PA-TNC 
> defined IETF name space attributes.

We'll drop the word "typical".  The idea was trying to describe an
expected result based on today's deployment experience.

> 
> Page 60, reference 8.  Why is this informative and not 
> speculatively normative?

We wanted to limit the normative reference to specification that are
contributing normative requirements to the spec.  Since this is a
standards track spec we want to limit normative references to other
non-standards track documents (such as 6 and 7).

> 
> Gary
> 
> _______________________________________________
> 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


From nea-bounces@ietf.org  Thu Jun  5 17:48:42 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 76EC03A69B1;
	Thu,  5 Jun 2008 17:48:42 -0700 (PDT)
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 00AB93A6819
	for <nea@core3.amsl.com>; Thu,  5 Jun 2008 17:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	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 IeeRvO4OBy7D for <nea@core3.amsl.com>;
	Thu,  5 Jun 2008 17:48:29 -0700 (PDT)
Received: from extu-mxob-1.symantec.com (extu-mxob-1.symantec.com
	[216.10.194.28])
	by core3.amsl.com (Postfix) with ESMTP id 8808B3A6A5E
	for <nea@ietf.org>; Thu,  5 Jun 2008 17:48:29 -0700 (PDT)
Received: from tus1opsmtapin02.ges.symantec.com
	(tus1opsmtapin02.ges.symantec.com [192.168.214.44])
	by extu-mxob-1.symantec.com (8.14.1/8.14.1) with ESMTP id
	m560mVtH002306
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 5 Jun 2008 17:48:36 -0700
Received: from reserved-155-64-230-19.ges.symantec.com ([155.64.230.19]
	helo=TUS1XCHECNPIN02.enterprise.veritas.com)
	by tus1opsmtapin02.ges.symantec.com with esmtp (Exim 4.67)
	(envelope-from <Paul_Sangster@symantec.com>)
	id 1K4Q81-0005oL-La; Thu, 05 Jun 2008 17:48:25 -0700
Received: from TUS1XCHEVSPIN05.enterprise.veritas.com ([155.64.231.27]) by
	TUS1XCHECNPIN02.enterprise.veritas.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 5 Jun 2008 17:48:25 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 5 Jun 2008 17:48:22 -0700
Message-ID: <AB96CED633A7C246BDC661DBEE1CF01F03C8D1C9@TUS1XCHCLUPIN11.enterprise.veritas.com>
In-Reply-To: <C3F6A9E7.14966%kaushik@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Nea] Comments on NEA TNC PA & PB protocol specifications
Thread-Index: AciAblMokb+MC+xhEdyBtQAX8tamGRG/AqnA
References: <C3F6A9E7.14966%kaushik@cisco.com>
From: "Paul Sangster" <Paul_Sangster@symantec.com>
To: "Kaushik Narayan" <kaushik@cisco.com>, <nea@ietf.org>
X-OriginalArrivalTime: 06 Jun 2008 00:48:25.0450 (UTC)
	FILETIME=[0719FCA0:01C8C76F]
Subject: Re: [Nea] Comments on NEA TNC PA & PB protocol specifications
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0837989842=="
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0837989842==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8C76E.F15AEBFE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8C76E.F15AEBFE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Kaushik,
=20
Thanks for the comments, my responses are in-lined with [PS] prefix...


________________________________

	From: nea-bounces@ietf.org [mailto:nea-bounces@ietf.org] On
Behalf Of Kaushik Narayan
	Sent: Friday, March 07, 2008 8:15 AM
	To: nea@ietf.org
	Subject: [Nea] Comments on NEA TNC PA & PB protocol
specifications
=09
=09
=09
=09
	Here are my comments on the NEA TNC PA & PB protocol
specifications
=09
	Overall (This applies to both PA & PB protocol specifications)
=09
	It might be useful to have a section that describes any protocol
design considerations above and beyond the NEA Reference model; some
examples of such considerations could include=20
=09

	*	Motivation for signaling state transitions over-the-wire
using PB batch messages.=20
	*	PA Message Delivery/Routing -  subscription & explicit
identification=20
	*	Design considerations for performance, scale &
extensibility - optimization of round trips, PA/PB protocol header
overhead, vendor identification included in various PB & PA
message/attribute headers.
		=20
		[PS] I agree we could use a design considerations
section to discuss how we got to the end design and how these issues
factored into the decision. =20

	Some of the considerations have been called out in various
sections but it might help elevate that to the start of the document.
	=20
	[PS] Agreed, many are discussed farther down in the spec, so we
could move up those that will help the reader understand the chosen
direction at a higher level before going into the design itself.=20
=09
	Lack of packet processing details or protocol flows makes it
difficult to evaluate various protocol specifics such as structuring of
various headers or presence  of certain fields in certain headers.=20
	=20
	[PS] Would a high level example that ties into the protocol
flows help?  Maybe something like the use cases from the requirements
spec? Would you be willing to help contribute some text for this?=20
=09
	The description for some of the common fields in various
protocol headers such as vendor-id  has common text but does not specify
why that field is present in that specific header. =20
	=20
	[PS] Ok. Generally the vendor ids are used to scope the
subsequent field where we want to allow either a standard value or a
vendor defined value to be present.  We could describe this in the
design considerations section (maybe you could provide some input into
that section as well).=20
=09
	PA Protocol
=09
	A syntax for the attributes needs to be defined; it is necessary
to explain how various types of text and binary data will by
represented.
	=20
	[PS] I believe we do call out encodings for text and binary in
the normative description of each field.  Did you have something else in
mind?
	=20
	The specification does specify the definition of result or
assertion attributes.
	=20
	[PS] I presume you mean it "... does not specify ..." These are
known open areas of the spec that require additional work that we had
hoped would occur in the NEA WG.  The original TNC spec does include
some examples of these types of attributes (e.g. "IMV Assessment
Results" and "Remediation Instructions" attributes) that we had hoped
would get some discussion in NEA before being added to the spec.  We
hope to discuss these types of attributes in Dublin.
	=20
	There is vendor-id field in the Attribute header but I am not
sure whether this vendor-id needs to be carried over-the-wire for every
attribute since this vendor-id is not expected to be different from the
vendor-id in the PB-PA message. Is there a reason to have vendor-id
inside each attribute ? I would recommend removing the vendor-id from
the attribute if it is not needed since it will save 3 bytes of data per
attribute and that can be significant in an assessment that involves a
large number of attributes.
	=20
	[PS] The vendor-id is needed in both the PB protocol and the PA
attributes.  In both cases it is scoping orthogonal fields.  You can
have PB vendor-id/subtype of IETF/Firewall containing PA attributes with
a mix of IETF (Product Information) and Vendor defined (stateful
inspection features) attributes.  You also could have a PB
vendor-id/subtype of Vendor/NFS Server containing PA attributes with a
mix of Vendor (kernel state) and IETF (String Version).   The 3 bytes is
the price we pay for this flexibility.
=09
	The need for co-relation id is not very clear since in most
cases products should be differentiated using PA message type, i.e.
Component type + vendor id. Is this to handle the case where different
versions of the same product are installed on the endpoint ?
	=20
	[PS] Yes and no (more the later :)).  It could be used for
multiple version of the same product but is more needed for when a
single collector is reporting on multiple products of the same type.
For instance, if Symantec and McAfee's anti-virus packages were both
installed on a system (one might be active and the other came with the
PC).  When an AV validator requests the Product Information and String
Version attributes for the IETF/AV component on the system, it would get
back 4 attributes (Product Information and String Version for each
installed AV product).  In order to deterministically correlate which
String Version goes with which Product Information attribute you would
need this ID.  Note that this is should not be very common case (single
posture collector knowing how to report posture on multiple existing
products) so normally these 4 bytes are not present.  The COR bit
indicates whether this field is present in the attribute header so there
is no wasted bits on the wire (besides the flag :)).
=09
	The "port filter" seems to be an odd attribute to include in the
standard schema, the rest of the attributes seem to be associated with
general OS+application information whereas port filter seems like an
attribute associated with a  specific component.
	=20
	[PS] I believe the WG will need to define more of the attribute
and component type lists over time and the port filter attribute is a
good example of the more component specific type of attribute that might
be needed.  The goal is to build up a list over time of common
capabilities that might generically apply to a large number of OSes,
applications and environment so they can be included in a standard way
in an assessment.  This attribute allows an assessor to understand the
firewall policy being enforced on an endpoint as part of its assessment.
Without the attribute this couldn't be part of a standard assessment.
=09
	PB protocol
	=20
	[PS] I'll leave this to the PB editors
	=20
=09
	The term "message" used to represent various PB layer attributes
is very confusing; wondering why we can't use the term "attribute"
since that term is already used within the NEA Reference model to
represent PB layer information.
=09
	The use of PB vendor id is not clear since the NEA Reference
model does not describe behavior with multiple posture broker
client(s)/server(s), not sure how vendor specific message types at the
PB layer will be handled.
=09
	It is not clear which PB message types will processed by the PB
Client or Server whilst in different states described in Section 2.2. A
table summarizing the various states and messages that can be received
in that state would be helpful.
	=20
	The need to create a new PT connection if the server is required
to send a SDATA after the server has sent a RESULT as described at the
end of Section 2.2. seems like an artificial limitation placed. This
behavior should be left open to implementations so that they can
optimize in case a PT is more capable than just a half-duplex behavior.
=09
	regards,
	 kaushik
=09
=09
=09
=09
=09
=09
=09


------_=_NextPart_001_01C8C76E.F15AEBFE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Comments on NEA TNC PA & PB protocol =
specifications</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515031500-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Kaushik,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515031500-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515031500-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks for the comments, my responses are =
in-lined with=20
[PS] prefix...</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> nea-bounces@ietf.org=20
  [mailto:nea-bounces@ietf.org] <B>On Behalf Of </B>Kaushik=20
  Narayan<BR><B>Sent:</B> Friday, March 07, 2008 8:15 AM<BR><B>To:</B>=20
  nea@ietf.org<BR><B>Subject:</B> [Nea] Comments on NEA TNC PA &amp; PB =
protocol=20
  specifications<BR></FONT><BR></DIV>
  <DIV></DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  style=3D"FONT-SIZE: 12px"><BR><BR>Here are my comments on the NEA TNC =
PA &amp;=20
  PB protocol specifications<BR><BR>Overall (This applies to both PA =
&amp; PB=20
  protocol specifications)<BR><BR>It might be useful to have a section =
that=20
  describes any protocol design considerations above and beyond the NEA=20
  Reference model; some examples of such considerations could include=20
  <BR></SPAN></FONT>
  <UL>
    <LI><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
    style=3D"FONT-SIZE: 12px">Motivation for signaling state transitions =

    over-the-wire using PB batch messages. </SPAN></FONT>
    <LI><FONT face=3D"Verdana, Helvetica, Arial"><SPAN =
style=3D"FONT-SIZE: 12px">PA=20
    Message Delivery/Routing &#8211; &nbsp;subscription &amp; explicit =
identification=20
    </SPAN></FONT>
    <LI><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
    style=3D"FONT-SIZE: 12px">Design considerations for performance, =
scale &amp;=20
    extensibility &#8211; optimization of round trips, PA/PB protocol =
header overhead,=20
    vendor identification included in various PB &amp; PA =
message/attribute=20
    headers.<BR></SPAN></FONT><FONT face=3D"Verdana, Helvetica, =
Arial"><SPAN=20
    style=3D"FONT-SIZE: 12px"><SPAN=20
    class=3D515031500-06062008>&nbsp;</SPAN><BR><SPAN=20
    class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[PS]&nbsp;I=20
    agree we could use a design considerations section to discuss how we =
got to=20
    the end design and how these issues&nbsp;factored into the =
decision.&nbsp;=20
    </FONT></SPAN></LI></UL>
  <DIV></SPAN></FONT><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  style=3D"FONT-SIZE: 12px">Some of the considerations have been called =
out in=20
  various sections but it might help elevate that to the start of the=20
  document.<BR><SPAN class=3D515031500-06062008><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN><BR><SPAN =
class=3D515031500-06062008><FONT face=3DArial=20
  color=3D#0000ff size=3D2>[PS]&nbsp;Agreed, many are discussed farther =
down in the=20
  spec, so we could move up&nbsp;those that will help the reader =
understand=20
  the&nbsp;chosen direction at a higher level before going into the =
design=20
  itself.&nbsp;</FONT></SPAN><BR><BR>Lack of packet processing details =
or=20
  protocol flows makes it difficult to evaluate various protocol =
specifics such=20
  as structuring of various headers or presence &nbsp;of certain fields =
in=20
  certain headers.&nbsp;<BR><SPAN class=3D515031500-06062008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN><BR><SPAN=20
  class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[PS]&nbsp;Would=20
  a high level example&nbsp;that ties into the protocol flows =
help?&nbsp; Maybe=20
  something like the use cases from the requirements spec?&nbsp;Would =
you be=20
  willing to help contribute some text for =
this?&nbsp;</FONT></SPAN><BR><BR>The=20
  description for some of the common fields in various protocol headers =
such as=20
  vendor-id &nbsp;has common text but does not specify why that field is =
present=20
  in that specific header.&nbsp;&nbsp;<BR><SPAN =
class=3D515031500-06062008><FONT=20
  face=3DArial color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN><BR><SPAN=20
  class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[PS]&nbsp;Ok.=20
  Generally the vendor ids are used to scope the subsequent field where=20
  we&nbsp;want to allow either a standard value or a vendor defined =
value to be=20
  present.&nbsp; We could describe this in the design considerations =
section=20
  (maybe you could provide some input into that section as=20
  well).&nbsp;</FONT></SPAN><BR><BR>PA Protocol<BR><BR>A syntax for the=20
  attributes needs to be defined; it is necessary to explain how various =
types=20
  of text and binary data will by represented.<BR><SPAN=20
  class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN><BR><SPAN =
class=3D515031500-06062008><FONT face=3DArial=20
  color=3D#0000ff size=3D2>[PS]&nbsp;I believe we do call out encodings =
for text and=20
  binary in the normative description of each field.&nbsp; Did you have=20
  something else in mind?</FONT></SPAN><BR>&nbsp;<BR>The specification =
does=20
  specify the definition of result or assertion attributes.<BR><SPAN=20
  class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN><BR><SPAN =
class=3D515031500-06062008><FONT face=3DArial=20
  color=3D#0000ff size=3D2>[PS]&nbsp;I presume you mean it "... does not =
specify=20
  ..."&nbsp;These are known open areas of the spec that require=20
  additional&nbsp;work that we had hoped would occur in the NEA =
WG.&nbsp; The=20
  original TNC spec does include some examples of these types of =
attributes=20
  (e.g.&nbsp;"IMV Assessment Results" and "Remediation Instructions" =
attributes)=20
  that we had hoped would get some discussion in NEA before being added =
to the=20
  spec.&nbsp; We hope to discuss these types of attributes in=20
  Dublin.</FONT></SPAN><BR>&nbsp;<BR>There is vendor-id field in the =
Attribute=20
  header but I am not sure whether this vendor-id needs to be carried=20
  over-the-wire for every attribute since this vendor-id is not expected =
to be=20
  different from the vendor-id in the PB-PA message. Is there a reason =
to have=20
  vendor-id inside each attribute ? I would recommend removing the =
vendor-id=20
  from the attribute if it is not needed since it will save 3 bytes of =
data per=20
  attribute and that can be significant in an assessment that involves a =
large=20
  number of attributes.<BR><SPAN class=3D515031500-06062008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN><BR><SPAN=20
  class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[PS]&nbsp;The=20
  vendor-id is needed&nbsp;in both the PB protocol and the&nbsp;PA=20
  attributes.&nbsp; In both cases it is scoping&nbsp;orthogonal =
fields.&nbsp;=20
  You can have PB vendor-id/subtype of IETF/Firewall&nbsp;containing PA=20
  attributes with a mix of IETF (Product Information)&nbsp;and Vendor =
defined=20
  (stateful inspection features) attributes.&nbsp; You also could have a =
PB=20
  vendor-id/subtype of Vendor/NFS Server containing PA attributes with a =
mix=20
  of&nbsp;Vendor (kernel state) and IETF (String Version).&nbsp;&nbsp; =
The 3=20
  bytes is the price we pay for this =
flexibility.</FONT></SPAN><BR><BR>The need=20
  for co-relation id is not very clear since in most cases products =
should be=20
  differentiated using PA message type, i.e. Component type + vendor id. =
Is this=20
  to handle the case where different versions of the same product are =
installed=20
  on the endpoint ?<BR><SPAN class=3D515031500-06062008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN><BR><SPAN=20
  class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[PS]&nbsp;Yes=20
  and no (more the later :)).&nbsp; It could be used for multiple =
version of the=20
  same product but is more needed for when a single&nbsp;collector is =
reporting=20
  on multiple products&nbsp;of the same type.&nbsp; For instance, if =
Symantec=20
  and McAfee's anti-virus packages were both installed on a system (one =
might be=20
  active and the other came with the PC).&nbsp; When an AV validator =
requests=20
  the Product Information and String Version attributes for the IETF/AV=20
  component&nbsp;on the system, it would get back 4 attributes (Product=20
  Information and String Version for each installed AV product).&nbsp; =
In order=20
  to deterministically correlate which String Version goes with which =
Product=20
  Information attribute you would need this ID.&nbsp; Note that this is =
should=20
  not be very common case (single posture collector knowing how to =
report=20
  posture on multiple existing products) so normally&nbsp;these 4 bytes =
are not=20
  present.&nbsp; The COR bit indicates whether this field is present in =
the=20
  attribute header so there is no wasted bits on the wire (besides the =
flag=20
  :)).</FONT></SPAN></SPAN></FONT><FONT face=3D"Verdana, Helvetica, =
Arial"><SPAN=20
  style=3D"FONT-SIZE: 12px"><BR><FONT color=3D#0000ff><BR></FONT>The =
&#8220;port filter&#8221;=20
  seems to be an odd attribute to include in the standard schema, the =
rest of=20
  the attributes seem to be associated with general OS+application =
information=20
  whereas port filter seems like an attribute associated with a =
&nbsp;specific=20
  component.<BR><SPAN class=3D515031500-06062008><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN><BR><SPAN =
class=3D515031500-06062008><FONT face=3DArial=20
  color=3D#0000ff size=3D2>[PS]&nbsp;I believe the WG will need to =
define more=20
  of&nbsp;the attribute and component type lists over time and the port =
filter=20
  attribute is a good example of the more component specific type of =
attribute=20
  that might be needed.&nbsp;&nbsp;The goal is to build up&nbsp;a list =
over time=20
  of common capabilities that might generically apply to a large number =
of OSes,=20
  applications and environment so they can be included in a standard way =
in an=20
  assessment.&nbsp; This attribute allows an assessor to understand the =
firewall=20
  policy being enforced on an endpoint as part of its assessment.&nbsp; =
Without=20
  the attribute this couldn't be part of a standard=20
  assessment.</FONT></SPAN><BR><BR>PB protocol<BR><SPAN=20
  class=3D515031500-06062008><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN><BR><SPAN =
class=3D515031500-06062008><FONT face=3DArial=20
  color=3D#0000ff size=3D2>[PS]&nbsp;I'll leave this to the PB=20
  editors</FONT></SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  style=3D"FONT-SIZE: 12px"><SPAN =
class=3D515031500-06062008>&nbsp;</SPAN><BR><FONT=20
  color=3D#0000ff><BR></FONT>The term &#8220;message&#8221; used to =
represent various PB layer=20
  attributes is very confusing; wondering why we can&#8217;t use the =
term &#8220;attribute&#8221;=20
  &nbsp;since that term is already used within the NEA Reference model =
to=20
  represent PB layer information.<BR><BR>The use of PB vendor id is not =
clear=20
  since the NEA Reference model does not describe behavior with multiple =
posture=20
  broker client(s)/server(s), not sure how vendor specific message types =
at the=20
  PB layer will be handled.<BR><BR>It is not clear which PB message =
types will=20
  processed by the PB Client or Server whilst in different states =
described in=20
  Section 2.2. A table summarizing the various states and messages that =
can be=20
  received in that state would be helpful.<BR>&nbsp;<BR>The need to =
create a new=20
  PT connection if the server is required to send a SDATA after the =
server has=20
  sent a RESULT as described at the end of Section 2.2. seems like an =
artificial=20
  limitation placed. This behavior should be left open to =
implementations so=20
  that they can optimize in case a PT is more capable than just a =
half-duplex=20
  behavior.<BR><FONT =
color=3D#0000ff><BR></FONT>regards,<BR>&nbsp;kaushik<BR><FONT=20
  =
color=3D#0000ff><BR></FONT><BR><BR><BR><BR><BR></DIV></BLOCKQUOTE></SPAN>=
</FONT></BODY></HTML>

------_=_NextPart_001_01C8C76E.F15AEBFE--

--===============0837989842==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea

--===============0837989842==--


From nea-bounces@ietf.org  Fri Jun  6 12:05:08 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BCBA3A6C1C;
	Fri,  6 Jun 2008 12:05:08 -0700 (PDT)
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 192473A6A68
	for <nea@core3.amsl.com>; Fri,  6 Jun 2008 12:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	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 WcCqr5cyKI8J for <nea@core3.amsl.com>;
	Fri,  6 Jun 2008 12:04:49 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 28DDB3A6A43
	for <nea@ietf.org>; Fri,  6 Jun 2008 12:04:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,601,1204531200"; d="scan'208,217";a="76895021"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 06 Jun 2008 12:04:59 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m56J4xV0014058; 
	Fri, 6 Jun 2008 12:04:59 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m56J4u6S007024;
	Fri, 6 Jun 2008 19:04:56 GMT
Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jun 2008 12:04:56 -0700
Received: from 10.21.119.223 ([10.21.119.223]) by xmb-sjc-22d.amer.cisco.com
	([128.107.191.68]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri,  6 Jun 2008 19:04:55 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Fri, 06 Jun 2008 12:04:55 -0700
From: Kaushik Narayan <kaushik@cisco.com>
To: Paul Sangster <Paul_Sangster@symantec.com>, <nea@ietf.org>
Message-ID: <C46ED867.19F22%kaushik@cisco.com>
Thread-Topic: [Nea] Comments on NEA TNC PA & PB protocol specifications
Thread-Index: AciAblMokb+MC+xhEdyBtQAX8tamGRG/AqnAACd1u7Q=
In-Reply-To: <AB96CED633A7C246BDC661DBEE1CF01F03C8D1C9@TUS1XCHCLUPIN11.enterprise.veritas.com>
Mime-version: 1.0
X-OriginalArrivalTime: 06 Jun 2008 19:04:56.0232 (UTC)
	FILETIME=[3576A280:01C8C808]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=27789; t=1212779099;
	x=1213643099; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kaushik@cisco.com;
	z=From:=20Kaushik=20Narayan=20<kaushik@cisco.com>
	|Subject:=20Re=3A=20[Nea]=20Comments=20on=20NEA=20TNC=20PA=
	20&=20PB=20protocol=20specifications |Sender:=20;
	bh=HG9FpEHp4kkc1k8qvq3aJi86jhWAVLv+Flq/1h1Q6QU=;
	b=IhzHVVyP2G+Mu2CqMT8ZnGjQSyqZnAmNHpPP3z07p5vbkhRcPiozONy9RM
	oF9FyjWhUDeeNDt58Wl3e4d9sr0v/I2B00CrX7sIofNWFmXKXx3UDhJBabIJ
	E52ZnbR1pu;
Authentication-Results: sj-dkim-4; header.From=kaushik@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [Nea] Comments on NEA TNC PA & PB protocol specifications
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0263326708=="
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0263326708==
Content-type: multipart/alternative;
	boundary="B_3295598695_22146681"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3295598695_22146681
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi Paul,

Please find response inline.

<snipped>
>>=20
>> It might be useful to have a section that  describes any protocol design
>> considerations above and beyond the NEA  Reference model; some examples =
of
>> such considerations could include
>> =20
>> * Motivation for signaling state transitions  over-the-wire using PB bat=
ch
>> messages. =20
>> * PA  Message Delivery/Routing =AD  subscription & explicit identification
>> * Design considerations for performance, scale &  extensibility =AD
>> optimization of round trips, PA/PB protocol header overhead,  vendor
>> identification included in various PB & PA message/attribute  headers.
>> * =20
>> * [PS] I  agree we could use a design considerations section to discuss =
how
>> we got to  the end design and how these issues factored into the decisio=
n.
>> =20
> Some of the considerations have been called out in  various sections but =
it
> might help elevate that to the start of the  document.
> =20
> [PS] Agreed, many are discussed farther down in the  spec, so we could mo=
ve up
> those that will help the reader understand  the chosen direction at a hig=
her
> level before going into the design  itself.
>=20
> Lack of packet processing details or  protocol flows makes it difficult t=
o
> evaluate various protocol specifics such  as structuring of various heade=
rs or
> presence  of certain fields in  certain headers.
> =20
> [PS] Would  a high level example that ties into the protocol flows help?
> Maybe  something like the use cases from the requirements spec? Would you=
 be
> willing to help contribute some text for this?
>=20
>=20
> <Kaushik> I think it would be good to use se cases from the requirements
> document to illustrate the flows. I can help with drawing out the example
> flows </Kaushik>
>=20
> The  description for some of the common fields in various protocol header=
s
> such as  vendor-id  has common text but does not specify why that field i=
s
> present  in that specific header.
> =20
> [PS] Ok.  Generally the vendor ids are used to scope the subsequent field
> where  we want to allow either a standard value or a vendor defined value=
 to
> be  present.  We could describe this in the design considerations section
> (maybe you could provide some input into that section as  well).
>=20
> <Kaushik> =20
>=20
> I think it would be useful for the design considerations to cover
>=20
> 1. Considerations for Independent Namespaces that amongst other things ca=
n
> highlight choices around vendor identification fields in various PA proto=
col
> headers.=20
> 2. Considerations for extensibility and Scale to support dynamic addition=
 of
> new vendor types and scale to a large number of vendor namespaces
> 3. Considerations for efficiency considerations for transport over low
> bandwidth links and processing on low horsepower devices (mobile)
> 4. Considerations for component typing and extensibility considerations.
> 5. Considerations for choice of attributes in the IETF vs Vendor specific
> namespaces for various components (AV, OS, Host FW etc.)
>=20
> This might not be a complete list but can be used as a starting point. I =
can
> certainly help express these considerations from a requirements perspecti=
ve, I
> will need your help to expand these considerations to include choices you=
 made
> as part of protocol design & potentially co-relate the considerations to
> design decisions that are reflected in the PA protocol.
>=20
> </Kaushik>
>=20
>=20
>=20
>=20
> PA Protocol
>=20
> A syntax for the  attributes needs to be defined; it is necessary to expl=
ain
> how various types  of text and binary data will by represented.
> =20
> [PS] I believe we do call out encodings for text and  binary in the norma=
tive
> description of each field.  Did you have  something else in mind?
>=20
>=20
> <Kaushik>
>=20
> I was thinking of along the lines of the description of the attribute val=
ue
> field in the RADIUS RFC (RFC2865) copied below
>=20
> From RFC2865=20
>=20
> =B3Value
>=20
>       The Value field is zero or more octets and contains information
>       specific to the Attribute.  The format and length of the Value
>       field is determined by the Type and Length fields.
>=20
>       Note that none of the types in RADIUS terminate with a NUL (hex
>       00).  In particular, types "text" and "string" in RADIUS do not
>       terminate with a NUL (hex 00).  The Attribute has a length field
>       and does not use a terminator.  Text contains UTF-8 encoded 10646
>       [7] characters and String contains 8-bit binary data.  Servers and
>       servers and clients MUST be able to deal with embedded nulls.
>       RADIUS implementers using C are cautioned not to use strcpy() when
>       handling strings.
>=20
>       The format of the value field is one of five data types.  Note
>       that type "text" is a subset of type "string".
>=20
>       text      1-253 octets containing UTF-8 encoded 10646 [7]
>                 characters.  Text of length zero (0) MUST NOT be sent;
>                 omit the entire attribute instead.
>=20
>       string    1-253 octets containing binary data (values 0 through
>                 255 decimal, inclusive).  Strings of length zero (0)
>                 MUST NOT be sent; omit the entire attribute instead.
>=20
>       address   32 bit value, most significant octet first.
>=20
>       integer   32 bit unsigned value, most significant octet first.
>=20
>       time      32 bit unsigned value, most significant octet first --
>                 seconds since 00:00:00 UTC, January 1, 1970.  The
>                 standard Attributes do not use this data type but it is
>                 presented here for possible use in future attributes.=B2
>=20
>=20
> regards,
>  kaushik
>=20
> </Kaushik>
>=20
> The specification does  specify the definition of result or assertion
> attributes.
> =20
> [PS] I presume you mean it "... does not specify  ..." These are known op=
en
> areas of the spec that require  additional work that we had hoped would o=
ccur
> in the NEA WG.  The  original TNC spec does include some examples of thes=
e
> types of attributes  (e.g. "IMV Assessment Results" and "Remediation
> Instructions" attributes)  that we had hoped would get some discussion in=
 NEA
> before being added to the  spec.  We hope to discuss these types of attri=
butes
> in  Dublin.
> =20
> There is vendor-id field in the Attribute  header but I am not sure wheth=
er
> this vendor-id needs to be carried  over-the-wire for every attribute sin=
ce
> this vendor-id is not expected to be  different from the vendor-id in the
> PB-PA message. Is there a reason to have  vendor-id inside each attribute=
 ? I
> would recommend removing the vendor-id  from the attribute if it is not n=
eeded
> since it will save 3 bytes of data per  attribute and that can be signifi=
cant
> in an assessment that involves a large  number of attributes.
> =20
> [PS] The  vendor-id is needed in both the PB protocol and the PA  attribu=
tes.
> In both cases it is scoping orthogonal fields.   You can have PB
> vendor-id/subtype of IETF/Firewall containing PA  attributes with a mix o=
f
> IETF (Product Information) and Vendor defined  (stateful inspection featu=
res)
> attributes.  You also could have a PB  vendor-id/subtype of Vendor/NFS Se=
rver
> containing PA attributes with a mix  of Vendor (kernel state) and IETF (S=
tring
> Version).   The 3  bytes is the price we pay for this flexibility.
>=20
> The need  for co-relation id is not very clear since in most cases produc=
ts
> should be  differentiated using PA message type, i.e. Component type + ve=
ndor
> id. Is this  to handle the case where different versions of the same prod=
uct
> are installed  on the endpoint ?
> =20
> [PS] Yes  and no (more the later :)).  It could be used for multiple vers=
ion
> of the  same product but is more needed for when a single collector is
> reporting  on multiple products of the same type.  For instance, if Syman=
tec
> and McAfee's anti-virus packages were both installed on a system (one mig=
ht be
> active and the other came with the PC).  When an AV validator requests  t=
he
> Product Information and String Version attributes for the IETF/AV  compon=
ent
> on the system, it would get back 4 attributes (Product  Information and S=
tring
> Version for each installed AV product).  In order  to deterministically
> correlate which String Version goes with which Product  Information attri=
bute
> you would need this ID.  Note that this is should  not be very common cas=
e
> (single posture collector knowing how to report  posture on multiple exis=
ting
> products) so normally these 4 bytes are not  present.  The COR bit indica=
tes
> whether this field is present in the  attribute header so there is no was=
ted
> bits on the wire (besides the flag  :)).
>=20
> The =B3port filter=B2  seems to be an odd attribute to include in the standar=
d
> schema, the rest of  the attributes seem to be associated with general
> OS+application information  whereas port filter seems like an attribute
> associated with a  specific  component.
> =20
> [PS] I believe the WG will need to define more  of the attribute and comp=
onent
> type lists over time and the port filter  attribute is a good example of =
the
> more component specific type of attribute  that might be needed.  The goa=
l is
> to build up a list over time  of common capabilities that might generical=
ly
> apply to a large number of OSes,  applications and environment so they ca=
n be
> included in a standard way in an  assessment.  This attribute allows an
> assessor to understand the firewall  policy being enforced on an endpoint=
 as
> part of its assessment.  Without  the attribute this couldn't be part of =
a
> standard  assessment.
>=20
> PB protocol
> =20
> [PS] I'll leave this to the PB  editors
> =20
> =20
>=20
> The term =B3message=B2 used to represent various PB layer  attributes is very
> confusing; wondering why we can=B9t use the term =B3attribute=B2   since that t=
erm
> is already used within the NEA Reference model to  represent PB layer
> information.
>=20
> The use of PB vendor id is not clear  since the NEA Reference model does =
not
> describe behavior with multiple posture  broker client(s)/server(s), not =
sure
> how vendor specific message types at the  PB layer will be handled.
>=20
> It is not clear which PB message types will  processed by the PB Client o=
r
> Server whilst in different states described in  Section 2.2. A table
> summarizing the various states and messages that can be  received in that
> state would be helpful.
> =20
> The need to create a new  PT connection if the server is required to send=
 a
> SDATA after the server has  sent a RESULT as described at the end of Sect=
ion
> 2.2. seems like an artificial  limitation placed. This behavior should be=
 left
> open to implementations so  that they can optimize in case a PT is more
> capable than just a half-duplex  behavior.
>=20
> regards,
>  kaushik
>=20
>=20
>=20
>=20
>=20
>=20
>=20



--B_3295598695_22146681
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Nea] Comments on NEA TNC PA &amp; PB protocol specifications</T=
ITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>Hi Pa=
ul,<BR>
<BR>
Please find response inline.<BR>
<BR>
&lt;snipped&gt;<BR>
</SPAN></FONT><BLOCKQUOTE><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:12.0px'><BR>
It might be useful to have a section that &nbsp;describes any protocol desi=
gn considerations above and beyond the NEA &nbsp;Reference model; some examp=
les of such considerations could include &nbsp;<BR>
&nbsp;<BR>
</SPAN></FONT><UL><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'f=
ont-size:12.0px'>Motivation for signaling state transitions &nbsp;over-the-w=
ire using PB batch messages. &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-=
size:12.0px'>PA &nbsp;Message Delivery/Routing &#8211; &nbsp;subscription &a=
mp; explicit identification &nbsp;&nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-=
size:12.0px'>Design considerations for performance, scale &amp; &nbsp;extens=
ibility &#8211; optimization of round trips, PA/PB protocol header overhead,=
 &nbsp;vendor identification included in various PB &amp; PA message/attribu=
te &nbsp;headers.
</SPAN></FONT><LI><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-=
size:12.0px'>=20
</SPAN></FONT><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FF"><FON=
T FACE=3D"Arial">[PS] I &nbsp;agree we could use a design considerations secti=
on to discuss how we got to &nbsp;the end design and how these issues factor=
ed into the decision. &nbsp;&nbsp;<BR>
</FONT></FONT></SPAN></UL><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdan=
a, Helvetica, Arial"> <BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verda=
na, Helvetica, Arial">Some of the considerations have been called out in &nb=
sp;various sections but it might help elevate that to the start of the &nbsp=
;document.<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"> <BR>
[PS] Agreed, many are discussed farther down in the &nbsp;spec, so we could=
 move up those that will help the reader understand &nbsp;the chosen directi=
on at a higher level before going into the design &nbsp;itself. <BR>
<BR>
</FONT></FONT><FONT FACE=3D"Arial">Lack of packet processing details or &nbsp=
;protocol flows makes it difficult to evaluate various protocol specifics su=
ch &nbsp;as structuring of various headers or presence &nbsp;of certain fiel=
ds in &nbsp;certain headers. <BR>
<FONT COLOR=3D"#0000FF"> <BR>
[PS] Would &nbsp;a high level example that ties into the protocol flows hel=
p? &nbsp;Maybe &nbsp;something like the use cases from the requirements spec=
? Would you be &nbsp;willing to help contribute some text for this? <BR>
<BR>
<BR>
&lt;Kaushik&gt; I think it would be good to use se cases from the requireme=
nts document to illustrate the flows. I can help with drawing out the exampl=
e flows &lt;/Kaushik&gt;<BR>
<BR>
</FONT>The &nbsp;description for some of the common fields in various proto=
col headers such as &nbsp;vendor-id &nbsp;has common text but does not speci=
fy why that field is present &nbsp;in that specific header. &nbsp;<BR>
<FONT COLOR=3D"#0000FF"> <BR>
[PS] Ok. &nbsp;Generally the vendor ids are used to scope the subsequent fi=
eld where &nbsp;we want to allow either a standard value or a vendor defined=
 value to be &nbsp;present. &nbsp;We could describe this in the design consi=
derations section &nbsp;(maybe you could provide some input into that sectio=
n as &nbsp;well). <BR>
<BR>
&lt;Kaushik&gt; &nbsp;<BR>
<BR>
I think it would be useful for the design considerations to cover<BR>
<BR>
</FONT></FONT></SPAN><OL><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Ari=
al"><FONT COLOR=3D"#0000FF">Considerations for Independent Namespaces that amo=
ngst other things can highlight choices around vendor identification fields =
in various PA protocol headers.
</FONT></FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial">=
<FONT COLOR=3D"#0000FF">Considerations for extensibility and Scale to support =
dynamic addition of new vendor types and scale to a large number of vendor n=
amespaces
</FONT></FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial">=
<FONT COLOR=3D"#0000FE">Considerations for </FONT><FONT COLOR=3D"#0000FF">effici=
ency considerations for transport over low bandwidth links and processing on=
 low horsepower devices (mobile)
</FONT></FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial">=
<FONT COLOR=3D"#0000FE">Considerations for</FONT><FONT COLOR=3D"#0000FF"> compon=
ent typing and extensibility considerations.
</FONT></FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial">=
<FONT COLOR=3D"#0000FE">Considerations for</FONT><FONT COLOR=3D"#0000FF"> choice=
 of attributes in the IETF vs Vendor specific namespaces for various compone=
nts (AV, OS, Host FW etc.)<BR>
</FONT></FONT></SPAN></OL><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial"=
><FONT COLOR=3D"#0000FF"><BR>
This might not be a complete list but can be used as a starting point. I ca=
n certainly help express these considerations from a requirements perspectiv=
e, I will need your help to expand these considerations to include choices y=
ou made as part of protocol design &amp; potentially co-relate the considera=
tions to design decisions that are reflected in the PA protocol.<BR>
<BR>
&lt;/Kaushik&gt;<BR>
<BR>
<BR>
<BR>
</FONT><BR>
PA Protocol<BR>
<BR>
A syntax for the &nbsp;attributes needs to be defined; it is necessary to e=
xplain how various types &nbsp;of text and binary data will by represented.<=
BR>
<FONT COLOR=3D"#0000FF"> <BR>
[PS] I believe we do call out encodings for text and &nbsp;binary in the no=
rmative description of each field. &nbsp;Did you have &nbsp;something else i=
n mind?<BR>
<BR>
<BR>
&lt;Kaushik&gt;<BR>
<BR>
I was thinking of along the lines of the description of the attribute value=
 field in the RADIUS RFC (RFC2865) copied below<BR>
<BR>
>From RFC2865 <BR>
<BR>
&#8220;Value<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The Value field is zero or more octets =
and contains information<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;specific to the Attribute. &nbsp;The fo=
rmat and length of the Value<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;field is determined by the Type and Len=
gth fields.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Note that none of the types in RADIUS t=
erminate with a NUL (hex<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;00). &nbsp;In particular, types &quot;t=
ext&quot; and &quot;string&quot; in RADIUS do not<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;terminate with a NUL (hex 00). &nbsp;Th=
e Attribute has a length field<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and does not use a terminator. &nbsp;Te=
xt contains UTF-8 encoded 10646<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7] characters and String contains 8-bi=
t binary data. &nbsp;Servers and<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;servers and clients MUST be able to dea=
l with embedded nulls.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RADIUS implementers using C are caution=
ed not to use strcpy() when<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;handling strings.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The format of the value field is one of=
 five data types. &nbsp;Note<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;that type &quot;text&quot; is a subset =
of type &quot;string&quot;.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;text &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1-25=
3 octets containing UTF-8 encoded 10646 [7]<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;characters. &nbsp;Text of length zero (0) MUST NOT be s=
ent;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;omit the entire attribute instead.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string &nbsp;&nbsp;&nbsp;1-253 octets c=
ontaining binary data (values 0 through<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;255 decimal, inclusive). &nbsp;Strings of length zero (=
0)<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;MUST NOT be sent; omit the entire attribute instead.<BR=
>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address &nbsp;&nbsp;32 bit value, most =
significant octet first.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;integer &nbsp;&nbsp;32 bit unsigned val=
ue, most significant octet first.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;32 b=
it unsigned value, most significant octet first --<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;seconds since 00:00:00 UTC, January 1, 1970. &nbsp;The<=
BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;standard Attributes do not use this data type but it is=
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;presented here for possible use in future attributes.&#=
8221;<BR>
<BR>
<BR>
regards,<BR>
&nbsp;kaushik<BR>
<BR>
&lt;/Kaushik&gt;<BR>
<BR>
</FONT>The specification does &nbsp;specify the definition of result or ass=
ertion attributes.<BR>
<FONT COLOR=3D"#0000FF"> <BR>
[PS] I presume you mean it &quot;... does not specify &nbsp;...&quot; These=
 are known open areas of the spec that require &nbsp;additional work that we=
 had hoped would occur in the NEA WG. &nbsp;The &nbsp;original TNC spec does=
 include some examples of these types of attributes &nbsp;(e.g. &quot;IMV As=
sessment Results&quot; and &quot;Remediation Instructions&quot; attributes) =
&nbsp;that we had hoped would get some discussion in NEA before being added =
to the &nbsp;spec. &nbsp;We hope to discuss these types of attributes in &nb=
sp;Dublin.<BR>
</FONT> <BR>
There is vendor-id field in the Attribute &nbsp;header but I am not sure wh=
ether this vendor-id needs to be carried &nbsp;over-the-wire for every attri=
bute since this vendor-id is not expected to be &nbsp;different from the ven=
dor-id in the PB-PA message. Is there a reason to have &nbsp;vendor-id insid=
e each attribute ? I would recommend removing the vendor-id &nbsp;from the a=
ttribute if it is not needed since it will save 3 bytes of data per &nbsp;at=
tribute and that can be significant in an assessment that involves a large &=
nbsp;number of attributes.<BR>
<FONT COLOR=3D"#0000FF"> <BR>
[PS] The &nbsp;vendor-id is needed in both the PB protocol and the PA &nbsp=
;attributes. &nbsp;In both cases it is scoping orthogonal fields. &nbsp;&nbs=
p;You can have PB vendor-id/subtype of IETF/Firewall containing PA &nbsp;att=
ributes with a mix of IETF (Product Information) and Vendor defined &nbsp;(s=
tateful inspection features) attributes. &nbsp;You also could have a PB &nbs=
p;vendor-id/subtype of Vendor/NFS Server containing PA attributes with a mix=
 &nbsp;of Vendor (kernel state) and IETF (String Version). &nbsp;&nbsp;The 3=
 &nbsp;bytes is the price we pay for this flexibility.<BR>
</FONT><BR>
The need &nbsp;for co-relation id is not very clear since in most cases pro=
ducts should be &nbsp;differentiated using PA message type, i.e. Component t=
ype + vendor id. Is this &nbsp;to handle the case where different versions o=
f the same product are installed &nbsp;on the endpoint ?<BR>
<FONT COLOR=3D"#0000FF"> <BR>
[PS] Yes &nbsp;and no (more the later :)). &nbsp;It could be used for multi=
ple version of the &nbsp;same product but is more needed for when a single c=
ollector is reporting &nbsp;on multiple products of the same type. &nbsp;For=
 instance, if Symantec &nbsp;and McAfee's anti-virus packages were both inst=
alled on a system (one might be &nbsp;active and the other came with the PC)=
. &nbsp;When an AV validator requests &nbsp;the Product Information and Stri=
ng Version attributes for the IETF/AV &nbsp;component on the system, it woul=
d get back 4 attributes (Product &nbsp;Information and String Version for ea=
ch installed AV product). &nbsp;In order &nbsp;to deterministically correlat=
e which String Version goes with which Product &nbsp;Information attribute y=
ou would need this ID. &nbsp;Note that this is should &nbsp;not be very comm=
on case (single posture collector knowing how to report &nbsp;posture on mul=
tiple existing products) so normally these 4 bytes are not &nbsp;present. &n=
bsp;The COR bit indicates whether this field is present in the &nbsp;attribu=
te header so there is no wasted bits on the wire (besides the flag &nbsp;:))=
.<BR>
</FONT></FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Verdana, Helvetica, Arial">=
<BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial">The &#8220;port filter=
&#8221; &nbsp;seems to be an odd attribute to include in the standard schema=
, the rest of &nbsp;the attributes seem to be associated with general OS+app=
lication information &nbsp;whereas port filter seems like an attribute assoc=
iated with a &nbsp;specific &nbsp;component.<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"> <BR>
[PS] I believe the WG will need to define more &nbsp;of the attribute and c=
omponent type lists over time and the port filter &nbsp;attribute is a good =
example of the more component specific type of attribute &nbsp;that might be=
 needed. &nbsp;The goal is to build up a list over time &nbsp;of common capa=
bilities that might generically apply to a large number of OSes, &nbsp;appli=
cations and environment so they can be included in a standard way in an &nbs=
p;assessment. &nbsp;This attribute allows an assessor to understand the fire=
wall &nbsp;policy being enforced on an endpoint as part of its assessment. &=
nbsp;Without &nbsp;the attribute this couldn't be part of a standard &nbsp;a=
ssessment.<BR>
</FONT></FONT><FONT FACE=3D"Arial"><BR>
PB protocol<BR>
<FONT COLOR=3D"#0000FF"> <BR>
[PS] I'll leave this to the PB &nbsp;editors<BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
<FONT COLOR=3D"#0000FF"><BR>
</FONT>The term &#8220;message&#8221; used to represent various PB layer &n=
bsp;attributes is very confusing; wondering why we can&#8217;t use the term =
&#8220;attribute&#8221; &nbsp;&nbsp;since that term is already used within t=
he NEA Reference model to &nbsp;represent PB layer information.<BR>
<BR>
The use of PB vendor id is not clear &nbsp;since the NEA Reference model do=
es not describe behavior with multiple posture &nbsp;broker client(s)/server=
(s), not sure how vendor specific message types at the &nbsp;PB layer will b=
e handled.<BR>
<BR>
It is not clear which PB message types will &nbsp;processed by the PB Clien=
t or Server whilst in different states described in &nbsp;Section 2.2. A tab=
le summarizing the various states and messages that can be &nbsp;received in=
 that state would be helpful.<BR>
&nbsp;<BR>
The need to create a new &nbsp;PT connection if the server is required to s=
end a SDATA after the server has &nbsp;sent a RESULT as described at the end=
 of Section 2.2. seems like an artificial &nbsp;limitation placed. This beha=
vior should be left open to implementations so &nbsp;that they can optimize =
in case a PT is more capable than just a half-duplex &nbsp;behavior.<BR>
<FONT COLOR=3D"#0000FF"><BR>
</FONT>regards,<BR>
&nbsp;kaushik<BR>
<FONT COLOR=3D"#0000FF"><BR>
</FONT><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verda=
na, Helvetica, Arial"><BR>
</FONT></SPAN>
</BODY>
</HTML>


--B_3295598695_22146681--


--===============0263326708==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea

--===============0263326708==--



From nea-bounces@ietf.org  Fri Jun  6 14:45:59 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67DEF3A6BEF;
	Fri,  6 Jun 2008 14:45:59 -0700 (PDT)
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 9B0793A68B7
	for <nea@core3.amsl.com>; Fri,  6 Jun 2008 14:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	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 UKlDy79X9DBA for <nea@core3.amsl.com>;
	Fri,  6 Jun 2008 14:45:37 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171])
	by core3.amsl.com (Postfix) with ESMTP id 9EE5B3A6BEF
	for <nea@ietf.org>; Fri,  6 Jun 2008 14:45:36 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob109.postini.com
	([64.18.6.12]) with SMTP; Fri, 06 Jun 2008 14:45:22 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 6 Jun 2008 14:45:09 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 6 Jun 2008 17:44:15 -0400
Message-ID: <A6398B0DB62A474C82F61554EE937287057D0864@proton.jnpr.net>
In-Reply-To: <C46ED867.19F22%kaushik@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Nea] Comments on NEA TNC PA & PB protocol specifications
Thread-Index: AciAblMokb+MC+xhEdyBtQAX8tamGRG/AqnAACd1u7QAADLzsA==
References: <AB96CED633A7C246BDC661DBEE1CF01F03C8D1C9@TUS1XCHCLUPIN11.enterprise.veritas.com>
	<C46ED867.19F22%kaushik@cisco.com>
From: "Stephen Hanna" <shanna@juniper.net>
To: "Kaushik Narayan" <kaushik@cisco.com>,
	"Paul Sangster" <Paul_Sangster@symantec.com>, <nea@ietf.org>
X-OriginalArrivalTime: 06 Jun 2008 21:45:09.0928 (UTC)
	FILETIME=[97AC3A80:01C8C81E]
Subject: Re: [Nea] Comments on NEA TNC PA & PB protocol specifications
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0911971221=="
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0911971221==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8C81E.96EB80DE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8C81E.96EB80DE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Let me speak up on the issues relevant to PB-TNC in Kaushik's email.
I'll mark my comments with [SH] below and snip out the sections that
pertain to PA-TNC.
=20
Thanks,
=20
Steve

________________________________

=20
 It might be useful to have a section that  describes any protocol
design considerations above and beyond the NEA  Reference model; some
examples of such considerations could include

		*	Motivation for signaling state transitions
over-the-wire using PB batch messages.  =20
		*	PA  Message Delivery/Routing -  subscription &
explicit identification   =20
		*	Design considerations for performance, scale &
extensibility - optimization of round trips, PA/PB protocol header
overhead,  vendor identification included in various PB & PA
message/attribute  headers.=20
		*=09
		*	[PS] I  agree we could use a design
considerations section to discuss how we got to  the end design and how
these issues factored into the decision.  =20
			[SH] Yes, this would be useful for PB-TNC also.
I'm willing to draft something for PB-TNC.

	=09

	Some of the considerations have been called out in  various
sections but it might help elevate that to the start of the  document.
=09
	[PS] Agreed, many are discussed farther down in the  spec, so we
could move up those that will help the reader understand  the chosen
direction at a higher level before going into the design  itself.=20
=09
	Lack of packet processing details or  protocol flows makes it
difficult to evaluate various protocol specifics such  as structuring of
various headers or presence  of certain fields in  certain headers.=20
=09
	[PS] Would  a high level example that ties into the protocol
flows help?  Maybe  something like the use cases from the requirements
spec? Would you be  willing to help contribute some text for this?=20
=09
	<Kaushik> I think it would be good to use se cases from the
requirements document to illustrate the flows. I can help with drawing
out the example flows </Kaushik>
	=20
	[SH] Are you willing to do this for PB-TNC also?
	=20
	The  description for some of the common fields in various
protocol headers such as  vendor-id  has common text but does not
specify why that field is present  in that specific header. =20
=09
	[PS] Ok.  Generally the vendor ids are used to scope the
subsequent field where  we want to allow either a standard value or a
vendor defined value to be  present.  We could describe this in the
design considerations section  (maybe you could provide some input into
that section as  well).=20
=09
	<Kaushik> =20
=09
	I think it would be useful for the design considerations to
cover
=09
=09

	1.	Considerations for Independent Namespaces that amongst
other things can highlight choices around vendor identification fields
in various PA protocol headers.=20
	2.	Considerations for extensibility and Scale to support
dynamic addition of new vendor types and scale to a large number of
vendor namespaces=20
	3.	Considerations for efficiency considerations for
transport over low bandwidth links and processing on low horsepower
devices (mobile)=20
	4.	Considerations for component typing and extensibility
considerations.=20
	5.	Considerations for choice of attributes in the IETF vs
Vendor specific namespaces for various components (AV, OS, Host FW etc.)
	=09

=09

	This might not be a complete list but can be used as a starting
point. I can certainly help express these considerations from a
requirements perspective, I will need your help to expand these
considerations to include choices you made as part of protocol design &
potentially co-relate the considerations to design decisions that are
reflected in the PA protocol.
=09
	</Kaushik>
=09
	 [SH] As noted above, I'd be glad to work on something similar
with you for PB-TNC.
=09
	PB protocol
=09
	The term "message" used to represent various PB layer
attributes is very confusing; wondering why we can't use the term
"attribute"   since that term is already used within the NEA Reference
model to  represent PB layer information.=20
	=20
	[SH] Maybe this change would be helpful. I'm afraid we would end
up with a similar problem: layers of different attributes (vs.
messages).
=09
	The use of PB vendor id is not clear  since the NEA Reference
model does not describe behavior with multiple posture  broker
client(s)/server(s), not sure how vendor specific message types at the
PB layer will be handled.=20
	=20
	[SH] We weren't trying to support multiple PBCs or PBSs on one
device. We just wanted to allow vendors to create extensions in a
compatible and standardized manner.
=09
	It is not clear which PB message types will  processed by the PB
Client or Server whilst in different states described in  Section 2.2. A
table summarizing the various states and messages that can be  received
in that state would be helpful.=20
	=20
	[SH] Yes, a table is a good idea.=20
	=20
	The need to create a new  PT connection if the server is
required to send a SDATA after the server has  sent a RESULT as
described at the end of Section 2.2. seems like an artificial
limitation placed. This behavior should be left open to implementations
so  that they can optimize in case a PT is more capable than just a
half-duplex  behavior.
=09
	 [SH] As currently defined, PB-TNC is a half-duplex protocol.
While this is necessary when the underlying transport is half-duplex
(EAP, for example), it is not necessary when the transport is
full-duplex. I suggest that we explore ways to ameliorate this problem.
For example, we should allow PB-TNC to take advantage of full-duplex
transports but still ensure that it functions over half-duplex
transports. We can't really just leave the behavior open to
implementations. That won't get us to interoperability.
	=20


------_=_NextPart_001_01C8C81E.96EB80DE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [Nea] Comments on NEA TNC PA & PB protocol =
specifications</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D015371019-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Let me speak up on the issues relevant to =
PB-TNC in=20
Kaushik's email. I'll mark my comments with [SH] below and snip out the =
sections=20
that pertain to PA-TNC.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D015371019-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D015371019-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D015371019-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D015371019-06062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Steve</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3D"Verdana, Helvetica, Arial"><SPAN style=3D"FONT-SIZE: 12px"><SPAN =

class=3D015371019-06062008><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></SPAN></FONT></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3D"Verdana, Helvetica, Arial"><SPAN style=3D"FONT-SIZE: 12px"><SPAN =

class=3D015371019-06062008>&nbsp;</SPAN>It might be useful to have a =
section that=20
&nbsp;describes any protocol design considerations above and beyond the =
NEA=20
&nbsp;Reference model; some examples of such considerations could=20
include</DIV></SPAN></FONT>
<BLOCKQUOTE>
  <BLOCKQUOTE>
    <UL>
      <LI><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
      style=3D"FONT-SIZE: 12px">Motivation for signaling state =
transitions=20
      &nbsp;over-the-wire using PB batch messages. &nbsp; </SPAN></FONT>
      <LI><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
      style=3D"FONT-SIZE: 12px">PA &nbsp;Message Delivery/Routing =
&#8211;=20
      &nbsp;subscription &amp; explicit identification &nbsp;&nbsp;=20
      </SPAN></FONT>
      <LI><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
      style=3D"FONT-SIZE: 12px">Design considerations for performance, =
scale &amp;=20
      &nbsp;extensibility &#8211; optimization of round trips, PA/PB =
protocol header=20
      overhead, &nbsp;vendor identification included in various PB &amp; =
PA=20
      message/attribute &nbsp;headers. </SPAN></FONT>
      <LI><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
      style=3D"FONT-SIZE: 12px"></SPAN></FONT>
      <LI><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial><FONT=20
      color=3D#0000ff>[PS] I &nbsp;agree we could use a design =
considerations=20
      section to discuss how we got to &nbsp;the end design and how =
these issues=20
      factored into the decision.&nbsp;&nbsp;&nbsp;<BR><SPAN=20
      class=3D015371019-06062008><FONT size=3D2>[SH] Yes, this would be =
useful for=20
      PB-TNC also. I'm willing to&nbsp;draft something for=20
      PB-TNC.</FONT></SPAN></FONT></FONT></SPAN></LI></UL><SPAN=20
    style=3D"FONT-SIZE: 12px"><FONT=20
  face=3D"Verdana, Helvetica, Arial"></FONT></SPAN></BLOCKQUOTE>
  <DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3D"Verdana, Helvetica, =
Arial">Some=20
  of the considerations have been called out in &nbsp;various sections =
but it=20
  might help elevate that to the start of the =
&nbsp;document.<BR></FONT><FONT=20
  color=3D#0000ff><FONT face=3DArial><BR>[PS] Agreed, many are discussed =
farther=20
  down in the &nbsp;spec, so we could move up those that will help the =
reader=20
  understand &nbsp;the chosen direction at a higher level before going =
into the=20
  design &nbsp;itself. <BR><BR></FONT></FONT><FONT face=3DArial>Lack of =
packet=20
  processing details or &nbsp;protocol flows makes it difficult to =
evaluate=20
  various protocol specifics such &nbsp;as structuring of various =
headers or=20
  presence &nbsp;of certain fields in &nbsp;certain headers.=20
  <BR></FONT><BR><FONT face=3DArial color=3D#0000ff>[PS] Would &nbsp;a =
high level=20
  example that ties into the protocol flows help? &nbsp;Maybe =
&nbsp;something=20
  like the use cases from the requirements spec? Would you be =
&nbsp;willing to=20
  help contribute some text for this? <BR><BR>&lt;Kaushik&gt; I think it =
would=20
  be good to use se cases from the requirements document to illustrate =
the=20
  flows. I can help with drawing out the example flows =
&lt;/Kaushik&gt;<BR><SPAN=20
  class=3D015371019-06062008><FONT =
size=3D2>&nbsp;</FONT></SPAN></FONT></SPAN></DIV>
  <DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial =
color=3D#0000ff><SPAN=20
  class=3D015371019-06062008>[SH] Are you willing to do this for PB-TNC=20
  also?</SPAN></FONT></SPAN></DIV>
  <DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial =
color=3D#0000ff><SPAN=20
  class=3D015371019-06062008>&nbsp;</SPAN><BR></FONT><FONT =
face=3DArial>The=20
  &nbsp;description for some of the common fields in various protocol =
headers=20
  such as &nbsp;vendor-id &nbsp;has common text but does not specify why =
that=20
  field is present &nbsp;in that specific header. &nbsp;<BR></FONT><FONT =

  color=3D#0000ff><BR><FONT face=3DArial>[PS] Ok. &nbsp;Generally the =
vendor ids are=20
  used to scope the subsequent field where &nbsp;we want to allow either =
a=20
  standard value or a vendor defined value to be &nbsp;present. &nbsp;We =
could=20
  describe this in the design considerations section &nbsp;(maybe you =
could=20
  provide some input into that section as &nbsp;well). =
<BR><BR>&lt;Kaushik&gt;=20
  &nbsp;<BR><BR>I think it would be useful for the design considerations =
to=20
  cover<BR><BR></DIV></FONT></FONT></SPAN>
  <OL>
    <LI><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial><FONT=20
    color=3D#0000ff>Considerations for Independent Namespaces that =
amongst other=20
    things can highlight choices around vendor identification fields in =
various=20
    PA protocol headers. </FONT></FONT></SPAN>
    <LI><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial><FONT=20
    color=3D#0000ff>Considerations for extensibility and Scale to =
support dynamic=20
    addition of new vendor types and scale to a large number of vendor=20
    namespaces </FONT></FONT></SPAN>
    <LI><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial><FONT=20
    color=3D#0000fe>Considerations for </FONT><FONT =
color=3D#0000ff>efficiency=20
    considerations for transport over low bandwidth links and processing =
on low=20
    horsepower devices (mobile) </FONT></FONT></SPAN>
    <LI><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial><FONT=20
    color=3D#0000fe>Considerations for</FONT><FONT color=3D#0000ff> =
component typing=20
    and extensibility considerations. </FONT></FONT></SPAN>
    <LI><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial><FONT=20
    color=3D#0000fe>Considerations for</FONT><FONT color=3D#0000ff> =
choice of=20
    attributes in the IETF vs Vendor specific namespaces for various =
components=20
    (AV, OS, Host FW etc.)<BR></FONT></FONT></SPAN></LI></OL><SPAN=20
  style=3D"FONT-SIZE: 12px">
  <DIV><BR><FONT face=3DArial color=3D#0000ff>This might not be a =
complete list but=20
  can be used as a starting point. I can certainly help express these=20
  considerations from a requirements perspective, I will need your help =
to=20
  expand these considerations to include choices you made as part of =
protocol=20
  design &amp; potentially co-relate the considerations to design =
decisions that=20
  are reflected in the PA protocol.<BR><BR>&lt;/Kaushik&gt;<BR><BR><SPAN =

  class=3D015371019-06062008><FONT size=3D2>&nbsp;[SH] As noted above, =
I'd be glad=20
  to work on something similar with you for=20
  PB-TNC.</FONT></SPAN><BR></FONT><FONT face=3DArial><BR>PB =
protocol<BR><FONT=20
  color=3D#0000ff><BR></FONT></FONT><FONT face=3D"Verdana, Helvetica, =
Arial">The=20
  term &#8220;message&#8221; used to represent various PB layer =
&nbsp;attributes is very=20
  confusing; wondering why we can&#8217;t use the term =
&#8220;attribute&#8221; &nbsp;&nbsp;since=20
  that term is already used within the NEA Reference model to =
&nbsp;represent PB=20
  layer information.<SPAN class=3D015371019-06062008><FONT face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  class=3D015371019-06062008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  class=3D015371019-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[SH] Maybe this=20
  change would be helpful. I'm afraid we would end up with&nbsp;a =
similar=20
  problem: layers of different attributes (vs.=20
  messages).</FONT></SPAN><BR><BR>The use of PB vendor id is not clear=20
  &nbsp;since the NEA Reference model does not describe behavior with =
multiple=20
  posture &nbsp;broker client(s)/server(s), not sure how vendor specific =
message=20
  types at the &nbsp;PB layer will be handled.<SPAN=20
  class=3D015371019-06062008><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  class=3D015371019-06062008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  class=3D015371019-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[SH] We weren't=20
  trying to support multiple PBCs or PBSs on one device. We just wanted =
to allow=20
  vendors to create extensions in a compatible and standardized=20
  manner.</FONT></SPAN><BR><BR>It is not clear which PB message types =
will=20
  &nbsp;processed by the PB Client or Server whilst in different states=20
  described in &nbsp;Section 2.2. A table summarizing the various states =
and=20
  messages that can be &nbsp;received in that state would be =
helpful.<SPAN=20
  class=3D015371019-06062008><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  class=3D015371019-06062008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  class=3D015371019-06062008><FONT face=3DArial color=3D#0000ff =
size=3D2>[SH] Yes, a=20
  table is a good idea.</FONT>&nbsp;</SPAN><BR>&nbsp;<BR>The need to =
create a=20
  new &nbsp;PT connection if the server is required to send a SDATA =
after the=20
  server has &nbsp;sent a RESULT as described at the end of Section 2.2. =
seems=20
  like an artificial &nbsp;limitation placed. This behavior should be =
left open=20
  to implementations so &nbsp;that they can optimize in case a PT is =
more=20
  capable than just a half-duplex &nbsp;behavior.<BR><BR><SPAN=20
  class=3D015371019-06062008><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;[SH]&nbsp;As currently defined, PB-TNC is a half-duplex =

  protocol.&nbsp;While this is necessary when the underlying transport =
is=20
  half-duplex (EAP, for example),&nbsp;it is not necessary when the =
transport is=20
  full-duplex. I suggest that we explore ways to ameliorate this =
problem. For=20
  example, we&nbsp;should allow PB-TNC to take advantage of full-duplex=20
  transports but still&nbsp;ensure that it&nbsp;functions over =
half-duplex=20
  transports. We can't really just leave the behavior open to =
implementations.=20
  That won't get us to interoperability.</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  =
class=3D015371019-06062008></SPAN></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE>=
</BODY></HTML>

------_=_NextPart_001_01C8C81E.96EB80DE--

--===============0911971221==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea

--===============0911971221==--


From nea-bounces@ietf.org  Sat Jun  7 21:35:36 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED8D83A679F;
	Sat,  7 Jun 2008 21:35:35 -0700 (PDT)
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 653F228C0DD
	for <nea@core3.amsl.com>; Sat,  7 Jun 2008 21:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	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 zWyVu5KN6f7W for <nea@core3.amsl.com>;
	Sat,  7 Jun 2008 21:35:24 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 08C173A679F
	for <nea@ietf.org>; Sat,  7 Jun 2008 21:35:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,607,1204531200"; 
	d="scan'208,217";a="110139587"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 07 Jun 2008 21:35:36 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m584Zawi017198; 
	Sat, 7 Jun 2008 21:35:36 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m584ZaZ0016952;
	Sun, 8 Jun 2008 04:35:36 GMT
Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 7 Jun 2008 21:35:36 -0700
Received: from 10.21.115.110 ([10.21.115.110]) by xmb-sjc-22d.amer.cisco.com
	([128.107.191.68]) with Microsoft Exchange Server HTTP-DAV ; 
	Sun,  8 Jun 2008 04:35:35 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Sat, 07 Jun 2008 21:35:34 -0700
From: Kaushik Narayan <kaushik@cisco.com>
To: Stephen Hanna <shanna@juniper.net>,
	Paul Sangster <Paul_Sangster@symantec.com>, <nea@ietf.org>
Message-ID: <C470AFA6.19FA5%kaushik@cisco.com>
Thread-Topic: [Nea] Comments on NEA TNC PA & PB protocol specifications
Thread-Index: AciAblMokb+MC+xhEdyBtQAX8tamGRG/AqnAACd1u7QAADLzsABGBaro
In-Reply-To: <A6398B0DB62A474C82F61554EE937287057D0864@proton.jnpr.net>
Mime-version: 1.0
X-OriginalArrivalTime: 08 Jun 2008 04:35:36.0317 (UTC)
	FILETIME=[188EBAD0:01C8C921]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=20002; t=1212899736;
	x=1213763736; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kaushik@cisco.com;
	z=From:=20Kaushik=20Narayan=20<kaushik@cisco.com>
	|Subject:=20Re=3A=20[Nea]=20Comments=20on=20NEA=20TNC=20PA=
	20&=20PB=20protocol=20specifications |Sender:=20;
	bh=fzCDcGWbotHfylko53R7f1PKYQPbkrfl+DFz4MJSKGs=;
	b=VBVAFtEh6DxwoPX1aZ1tevLHRgtdH1Arfur9k6iiJu3b4UZixHhRRAoYlk
	teRRqgB2pVAA2CSK5G+XbkFYEL69XsuHwAvdi3BXE9oHI2qpIWusbIIka08P
	/0gGrk5oJ7;
Authentication-Results: sj-dkim-2; header.From=kaushik@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [Nea] Comments on NEA TNC PA & PB protocol specifications
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0627353996=="
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0627353996==
Content-type: multipart/alternative;
	boundary="B_3295719334_23293576"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3295719334_23293576
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi Steve,

Thanks for your response. Please find my response inline tagged
<Kaushik-Response>

> <snipped>
>=20
> =20
>  It might be useful to have a section that  describes any protocol design
> considerations above and beyond the NEA  Reference model; some examples o=
f
> such considerations could include
>> =20
>>> =20
>>> * Motivation for signaling state transitions   over-the-wire using PB b=
atch
>>> messages.   =20
>>> * PA  Message Delivery/Routing =AD   subscription & explicit identificati=
on
>>> * Design considerations for performance, scale &   extensibility =AD
>>> optimization of round trips, PA/PB protocol header  overhead,  vendor
>>> identification included in various PB & PA  message/attribute  headers.
>>> * =20
>>> * [PS] I  agree we could use a design considerations  section to discus=
s how
>>> we got to  the end design and how these issues  factored into the decis=
ion.
>>> * [SH] Yes, this would be useful for  PB-TNC also. I'm willing to draft
>>> something for  PB-TNC.
>> =20
>> Some  of the considerations have been called out in  various sections bu=
t it
>> might help elevate that to the start of the  document.
>>=20
>> [PS] Agreed, many are discussed farther  down in the  spec, so we could =
move
>> up those that will help the reader  understand  the chosen direction at =
a
>> higher level before going into the  design  itself.
>>=20
>> Lack of packet  processing details or  protocol flows makes it difficult=
 to
>> evaluate  various protocol specifics such  as structuring of various hea=
ders
>> or  presence  of certain fields in  certain headers.
>>=20
>> [PS] Would  a high level  example that ties into the protocol flows help=
?
>> Maybe  something  like the use cases from the requirements spec? Would y=
ou be
>> willing to  help contribute some text for this?
>>=20
>> <Kaushik> I think it would  be good to use se cases from the requirement=
s
>> document to illustrate the  flows. I can help with drawing out the examp=
le
>> flows </Kaushik>
>> =20
>> =20
>> [SH] Are you willing to do this for PB-TNC  also?
>>=20
>>=20
>> <Kaushik-Response>
>>=20
>> Sure. I can take a crack at that; the flows will need to encompass both =
PA
>> and PB protocol. I will try to pick use cases that exemplify PA and PB
>> aspects to include in the respective protocol specifications.
>>=20
>> </Kaushik-Response>
>>=20
>>=20
>> =20
>> =20
>> The   description for some of the common fields in various protocol head=
ers
>> such as  vendor-id  has common text but does not specify why that  field=
 is
>> present  in that specific header.
>>=20
>> [PS] Ok.  Generally the vendor ids are  used to scope the subsequent fie=
ld
>> where  we want to allow either a  standard value or a vendor defined val=
ue to
>> be  present.  We could  describe this in the design considerations secti=
on
>> (maybe you could  provide some input into that section as  well).
>>=20
>> <Kaushik>  =20
>>=20
>> I think it would be useful for the design considerations to  cover
>>=20
> =20
> 1. Considerations for Independent Namespaces that amongst other  things c=
an
> highlight choices around vendor identification fields in various  PA prot=
ocol
> headers. =20
> 2. Considerations for extensibility and Scale to support dynamic  additio=
n of
> new vendor types and scale to a large number of vendor  namespaces
> 3. Considerations for efficiency  considerations for transport over low
> bandwidth links and processing on low  horsepower devices (mobile)
> 4. Considerations for component typing  and extensibility considerations.
> 5. Considerations for choice of  attributes in the IETF vs Vendor specifi=
c
> namespaces for various components  (AV, OS, Host FW etc.)
> =20
>=20
> This might not be a complete list but  can be used as a starting point. I=
 can
> certainly help express these  considerations from a requirements perspect=
ive,
> I will need your help to  expand these considerations to include choices =
you
> made as part of protocol  design & potentially co-relate the consideratio=
ns to
> design decisions that  are reflected in the PA protocol.
>=20
> </Kaushik>
>=20
>  [SH] As noted above, I'd be glad  to work on something similar with you =
for
> PB-TNC.
>=20
> <Kaushik-Response>
>=20
> That sounds good.
>=20
> </Kaushik-Response>
>=20
>=20
>=20
>=20
> PB protocol
>=20
> The  term =B3message=B2 used to represent various PB layer  attributes is ver=
y
> confusing; wondering why we can=B9t use the term =B3attribute=B2   since  that =
term
> is already used within the NEA Reference model to  represent PB  layer
> information.=20
> =20
> =20
> =20
> [SH] Maybe this  change would be helpful. I'm afraid we would end up with=
 a
> similar  problem: layers of different attributes (vs.  messages).
>=20
>=20
> <Kaushik-Response>
>=20
> I am not sure that there is a difference between attributes at the PA vs =
PB
> layers, they are just TLVs and in some cases might be similar in nature, =
for
> e.g. Posture assessment result at the PA layer and the global assessment
> result at the PB layer.
>=20
> </Kaushik-Response>
>=20
>=20
>=20
> The use of PB vendor id is not clear   since the NEA Reference model does=
 not
> describe behavior with multiple  posture  broker client(s)/server(s), not=
 sure
> how vendor specific message  types at the  PB layer will be handled.
> =20
> =20
> =20
> [SH] We weren't  trying to support multiple PBCs or PBSs on one device. W=
e
> just wanted to allow  vendors to create extensions in a compatible and
> standardized  manner.
>=20
> <Kaushik-Response>
>=20
> I think it might be helpful to articulate with examples the use of the
> vendor-id at the PB layer and the nature of such extensions.
>=20
> </Kaushik-Response>
>=20
>=20
>=20
> It is not clear which PB message types will   processed by the PB Client =
or
> Server whilst in different states  described in  Section 2.2. A table
> summarizing the various states and  messages that can be  received in tha=
t
> state would be helpful.
> =20
> =20
> =20
> [SH] Yes, a  table is a good idea.
> =20
> The need to create a  new  PT connection if the server is required to sen=
d a
> SDATA after the  server has  sent a RESULT as described at the end of Sec=
tion
> 2.2. seems  like an artificial  limitation placed. This behavior should b=
e
> left open  to implementations so  that they can optimize in case a PT is =
more
> capable than just a half-duplex  behavior.
>=20
>  [SH] As currently defined, PB-TNC is a half-duplex  protocol. While this=
 is
> necessary when the underlying transport is  half-duplex (EAP, for example=
), it
> is not necessary when the transport is  full-duplex. I suggest that we ex=
plore
> ways to ameliorate this problem. For  example, we should allow PB-TNC to =
take
> advantage of full-duplex  transports but still ensure that it functions o=
ver
> half-duplex  transports. We can't really just leave the behavior open to
> implementations.  That won't get us to interoperability.
>=20
>=20
> <Kaushik-Response>
>=20
> Were you thinking about including an initial proposal/options of addressi=
ng
> this in the next revision  ?
>=20
> regards,
>  kaushik
>=20
> </Kaushik-Response>
> =20
> =20
>=20



--B_3295719334_23293576
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Nea] Comments on NEA TNC PA &amp; PB protocol specifications</T=
ITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>Hi St=
eve,<BR>
<BR>
Thanks for your response. Please find my response inline tagged &lt;Kaushik=
-Response&gt;<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>&lt;snipped&gt;<BR>
<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FF"><FONT FA=
CE=3D"Arial"> <BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> It might be useful to=
 have a section that &nbsp;describes any protocol design considerations abov=
e and beyond the NEA &nbsp;Reference model; some examples of such considerat=
ions could include<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdan=
a, Helvetica, Arial"> <BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdan=
a, Helvetica, Arial"> <BR>
</FONT></SPAN><UL><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdana, H=
elvetica, Arial">Motivation for signaling state transitions &nbsp;&nbsp;over=
-the-wire using PB batch messages. &nbsp;&nbsp;&nbsp;
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdana, Helve=
tica, Arial">PA &nbsp;Message Delivery/Routing &#8211; &nbsp;&nbsp;subscript=
ion &amp; explicit identification &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdana, Helve=
tica, Arial">Design considerations for performance, scale &amp; &nbsp;&nbsp;=
extensibility &#8211; optimization of round trips, PA/PB protocol header &nb=
sp;overhead, &nbsp;vendor identification included in various PB &amp; PA &nb=
sp;message/attribute &nbsp;headers. &nbsp;
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdana, Helve=
tica, Arial">=20
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FF"><FON=
T FACE=3D"Arial">[PS] I &nbsp;agree we could use a design considerations &nbsp=
;section to discuss how we got to &nbsp;the end design and how these issues =
&nbsp;factored into the decision. &nbsp;&nbsp;
</FONT></FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000F=
F"><FONT FACE=3D"Arial">[SH] Yes, this would be useful for &nbsp;PB-TNC also. =
I'm willing to draft something for &nbsp;PB-TNC.<BR>
</FONT></FONT></SPAN></UL></BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT=
 FACE=3D"Verdana, Helvetica, Arial"> <BR>
Some &nbsp;of the considerations have been called out in &nbsp;various sect=
ions but it &nbsp;might help elevate that to the start of the &nbsp;document=
.<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"><BR>
[PS] Agreed, many are discussed farther &nbsp;down in the &nbsp;spec, so we=
 could move up those that will help the reader &nbsp;understand &nbsp;the ch=
osen direction at a higher level before going into the &nbsp;design &nbsp;it=
self. <BR>
<BR>
</FONT></FONT><FONT FACE=3D"Arial">Lack of packet &nbsp;processing details or=
 &nbsp;protocol flows makes it difficult to evaluate &nbsp;various protocol =
specifics such &nbsp;as structuring of various headers or &nbsp;presence &nb=
sp;of certain fields in &nbsp;certain headers. &nbsp;<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial">[PS] Would &nbsp;a high lev=
el &nbsp;example that ties into the protocol flows help? &nbsp;Maybe &nbsp;s=
omething &nbsp;like the use cases from the requirements spec? Would you be &=
nbsp;willing to &nbsp;help contribute some text for this? <BR>
<BR>
&lt;Kaushik&gt; I think it would &nbsp;be good to use se cases from the req=
uirements document to illustrate the &nbsp;flows. I can help with drawing ou=
t the example flows &lt;/Kaushik&gt;<BR>
&nbsp;<BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial">[SH] Are you willing to do =
this for PB-TNC &nbsp;also?<BR>
<BR>
<BR>
&lt;Kaushik-Response&gt;<BR>
<BR>
Sure. I can take a crack at that; the flows will need to encompass both PA =
and PB protocol. I will try to pick use cases that exemplify PA and PB aspec=
ts to include in the respective protocol specifications.<BR>
<BR>
&lt;/Kaushik-Response&gt;<BR>
<BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><BR>
&nbsp;<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"> <BR>
</FONT></FONT><FONT FACE=3D"Arial">The &nbsp;&nbsp;description for some of th=
e common fields in various protocol headers &nbsp;such as &nbsp;vendor-id &n=
bsp;has common text but does not specify why that &nbsp;field is present &nb=
sp;in that specific header. &nbsp;<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Verdana, Helvetica, Arial"><BR>
</FONT><FONT FACE=3D"Arial">[PS] Ok. &nbsp;Generally the vendor ids are &nbsp=
;used to scope the subsequent field where &nbsp;we want to allow either a &n=
bsp;standard value or a vendor defined value to be &nbsp;present. &nbsp;We c=
ould &nbsp;describe this in the design considerations section &nbsp;(maybe y=
ou could &nbsp;provide some input into that section as &nbsp;well). <BR>
<BR>
&lt;Kaushik&gt; &nbsp;&nbsp;<BR>
<BR>
I think it would be useful for the design considerations to &nbsp;cover<BR>
<BR>
</FONT></FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=
=3D"Verdana, Helvetica, Arial"> <BR>
</FONT></SPAN><OL><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FF">=
<FONT FACE=3D"Arial">Considerations for Independent Namespaces that amongst ot=
her &nbsp;things can highlight choices around vendor identification fields i=
n various &nbsp;PA protocol headers. </FONT></FONT><FONT FACE=3D"Verdana, Helv=
etica, Arial">=20
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FF"><FON=
T FACE=3D"Arial">Considerations for extensibility and Scale to support dynamic=
 &nbsp;addition of new vendor types and scale to a large number of vendor &n=
bsp;namespaces </FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial">=20
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FE"><FON=
T FACE=3D"Arial">Considerations for </FONT></FONT><FONT FACE=3D"Arial"><FONT COL=
OR=3D"#0000FF">efficiency &nbsp;considerations for transport over low bandwidt=
h links and processing on low &nbsp;horsepower devices (mobile) </FONT></FON=
T><FONT FACE=3D"Verdana, Helvetica, Arial">=20
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FE"><FON=
T FACE=3D"Arial">Considerations for</FONT></FONT><FONT FACE=3D"Arial"><FONT COLO=
R=3D"#0000FF"> component typing &nbsp;and extensibility considerations. </FONT=
></FONT><FONT FACE=3D"Verdana, Helvetica, Arial">=20
</FONT></SPAN><LI><SPAN STYLE=3D'font-size:12.0px'><FONT COLOR=3D"#0000FE"><FON=
T FACE=3D"Arial">Considerations for</FONT></FONT><FONT FACE=3D"Arial"><FONT COLO=
R=3D"#0000FF"> choice of &nbsp;attributes in the IETF vs Vendor specific names=
paces for various components &nbsp;(AV, OS, Host FW etc.)<BR>
</FONT></FONT></SPAN></OL><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdan=
a, Helvetica, Arial"> <BR>
<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial">This might not be a complet=
e list but &nbsp;can be used as a starting point. I can certainly help expre=
ss these &nbsp;considerations from a requirements perspective, I will need y=
our help to &nbsp;expand these considerations to include choices you made as=
 part of protocol &nbsp;design &amp; potentially co-relate the consideration=
s to design decisions that &nbsp;are reflected in the PA protocol.<BR>
<BR>
&lt;/Kaushik&gt;<BR>
<BR>
&nbsp;[SH] As noted above, I'd be glad &nbsp;to work on something similar w=
ith you for &nbsp;PB-TNC.<BR>
<BR>
&lt;Kaushik-Response&gt;<BR>
<BR>
That sounds good. <BR>
<BR>
&lt;/Kaushik-Response&gt;<BR>
<BR>
<BR>
<BR>
</FONT></FONT><FONT FACE=3D"Arial"><BR>
PB protocol<BR>
<FONT COLOR=3D"#0000FF"><BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial">The &nbsp;term &#8220;=
message&#8221; used to represent various PB layer &nbsp;attributes is very &=
nbsp;confusing; wondering why we can&#8217;t use the term &#8220;attribute&#=
8221; &nbsp;&nbsp;since &nbsp;that term is already used within the NEA Refer=
ence model to &nbsp;represent PB &nbsp;layer information.</FONT><FONT COLOR=3D=
"#0000FF"><FONT FACE=3D"Arial"> <BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
&nbsp;<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial">[SH] Maybe this &nbsp;chang=
e would be helpful. I'm afraid we would end up with a similar &nbsp;problem:=
 layers of different attributes (vs. &nbsp;messages).<BR>
<BR>
<BR>
&lt;Kaushik-Response&gt;<BR>
<BR>
I am not sure that there is a difference between attributes at the PA vs PB=
 layers, they are just TLVs and in some cases might be similar in nature, fo=
r e.g. Posture assessment result at the PA layer and the global assessment r=
esult at the PB layer. <BR>
<BR>
&lt;/Kaushik-Response&gt;<BR>
<BR>
</FONT></FONT><FONT FACE=3D"Arial"><BR>
<BR>
The use of PB vendor id is not clear &nbsp;&nbsp;since the NEA Reference mo=
del does not describe behavior with multiple &nbsp;posture &nbsp;broker clie=
nt(s)/server(s), not sure how vendor specific message &nbsp;types at the &nb=
sp;PB layer will be handled.<FONT COLOR=3D"#0000FF"> <BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
&nbsp;<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial">[SH] We weren't &nbsp;tryin=
g to support multiple PBCs or PBSs on one device. We just wanted to allow &n=
bsp;vendors to create extensions in a compatible and standardized &nbsp;mann=
er.<BR>
<BR>
&lt;Kaushik-Response&gt;<BR>
<BR>
I think it might be helpful to articulate with examples the use of the vend=
or-id at the PB layer and the nature of such extensions.<BR>
<BR>
&lt;/Kaushik-Response&gt;<BR>
<BR>
</FONT></FONT><FONT FACE=3D"Arial"><BR>
<BR>
It is not clear which PB message types will &nbsp;&nbsp;processed by the PB=
 Client or Server whilst in different states &nbsp;described in &nbsp;Sectio=
n 2.2. A table summarizing the various states and &nbsp;messages that can be=
 &nbsp;received in that state would be helpful.<FONT COLOR=3D"#0000FF"> <BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
&nbsp;<BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial">[SH] Yes, a &nbsp;table is =
a good idea.</FONT></FONT><FONT FACE=3D"Arial"> <BR>
&nbsp;<BR>
The need to create a &nbsp;new &nbsp;PT connection if the server is require=
d to send a SDATA after the &nbsp;server has &nbsp;sent a RESULT as describe=
d at the end of Section 2.2. seems &nbsp;like an artificial &nbsp;limitation=
 placed. This behavior should be left open &nbsp;to implementations so &nbsp=
;that they can optimize in case a PT is more &nbsp;capable than just a half-=
duplex &nbsp;behavior.<BR>
<BR>
<FONT COLOR=3D"#0000FF"> [SH] As currently defined, PB-TNC is a half-duplex &=
nbsp;protocol. While this is necessary when the underlying transport is &nbs=
p;half-duplex (EAP, for example), it is not necessary when the transport is =
&nbsp;full-duplex. I suggest that we explore ways to ameliorate this problem=
. For &nbsp;example, we should allow PB-TNC to take advantage of full-duplex=
 &nbsp;transports but still ensure that it functions over half-duplex &nbsp;=
transports. We can't really just leave the behavior open to implementations.=
 &nbsp;That won't get us to interoperability.<BR>
<BR>
<BR>
&lt;Kaushik-Response&gt;<BR>
<BR>
Were you thinking about including an initial proposal/options of addressing=
 this in the next revision &nbsp;?<BR>
<BR>
regards,<BR>
&nbsp;kaushik<BR>
<BR>
&lt;/Kaushik-Response&gt;<BR>
</FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verda=
na, Helvetica, Arial"><BR>
</FONT></SPAN>
</BODY>
</HTML>


--B_3295719334_23293576--


--===============0627353996==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea

--===============0627353996==--



From nea-bounces@ietf.org  Sun Jun  8 04:32:14 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 348933A6B9C;
	Sun,  8 Jun 2008 04:32:14 -0700 (PDT)
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 75A183A6B98
	for <nea@core3.amsl.com>; Sun,  8 Jun 2008 04:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	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 obcnRmymlI+m for <nea@core3.amsl.com>;
	Sun,  8 Jun 2008 04:32:04 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7ob116.obsmtp.com [64.18.2.218])
	by core3.amsl.com (Postfix) with ESMTP id 97BC03A6BA5
	for <nea@ietf.org>; Sun,  8 Jun 2008 04:32:04 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob116.postini.com
	([64.18.6.12]) with SMTP; Sun, 08 Jun 2008 04:31:59 PDT
Received: from antipi.jnpr.net ([10.10.2.34]) by p-emsmtp03.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Sun, 8 Jun 2008 04:31:03 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by antipi.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Sun, 8 Jun 2008 07:31:01 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 8 Jun 2008 07:21:26 -0400
Message-ID: <A6398B0DB62A474C82F61554EE937287057D08C4@proton.jnpr.net>
In-Reply-To: <C470AFA6.19FA5%kaushik@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Nea] Comments on NEA TNC PA & PB protocol specifications
Thread-Index: AciAblMokb+MC+xhEdyBtQAX8tamGRG/AqnAACd1u7QAADLzsABGBaroAA1/2VA=
References: <A6398B0DB62A474C82F61554EE937287057D0864@proton.jnpr.net>
	<C470AFA6.19FA5%kaushik@cisco.com>
From: "Stephen Hanna" <shanna@juniper.net>
To: "Kaushik Narayan" <kaushik@cisco.com>,
	"Paul Sangster" <Paul_Sangster@symantec.com>, <nea@ietf.org>
X-OriginalArrivalTime: 08 Jun 2008 11:31:01.0566 (UTC)
	FILETIME=[2129E5E0:01C8C95B]
Subject: Re: [Nea] Comments on NEA TNC PA & PB protocol specifications
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0894509321=="
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0894509321==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8C959.EBE5E264"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8C959.EBE5E264
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks, Kaushik. My responses below are marked [SH2]. To be honest, I
must say that I find this tagging mechanism more difficult to follow
than the old practice of using "> " in a plain text email. But here we
are in an HTML thread so I will continue in kind. I will remove as much
text as I can so we can focus on the few remaining open issues.
=20
Thanks,
=20
Steve

________________________________

From: Kaushik Narayan [mailto:kaushik@cisco.com]=20
Sent: Sunday, June 08, 2008 12:36 AM
To: Stephen Hanna; Paul Sangster; nea@ietf.org
Subject: Re: [Nea] Comments on NEA TNC PA & PB protocol specifications


Hi Steve,

Thanks for your response. Please find my response inline tagged
<Kaushik-Response>



	<snipped>
=09
=09
=09

		[PS] Would  a high level  example that ties into the
protocol flows help?  Maybe  something  like the use cases from the
requirements spec? Would you be  willing to  help contribute some text
for this?=20
	=09
		<Kaushik> I think it would  be good to use se cases from
the requirements document to illustrate the  flows. I can help with
drawing out the example flows </Kaushik>
		=20
	=09
		[SH] Are you willing to do this for PB-TNC  also?
	=09
		<Kaushik-Response>
	=09
		Sure. I can take a crack at that; the flows will need to
encompass both PA and PB protocol. I will try to pick use cases that
exemplify PA and PB aspects to include in the respective protocol
specifications.
	=09
		</Kaushik-Response>
	=09
		 [SH2]  Great! Thanks for volunteering for this task.
		=20
	=09

	PB protocol
=09
	The  term "message" used to represent various PB layer
attributes is very  confusing; wondering why we can't use the term
"attribute"   since  that term is already used within the NEA Reference
model to  represent PB  layer information.=20
=09
	[SH] Maybe this  change would be helpful. I'm afraid we would
end up with a similar  problem: layers of different attributes (vs.
messages).
=09
	 <Kaushik-Response>
=09
	I am not sure that there is a difference between attributes at
the PA vs PB layers, they are just TLVs and in some cases might be
similar in nature, for e.g. Posture assessment result at the PA layer
and the global assessment result at the PB layer.=20
=09
	</Kaushik-Response>
	=20
	[SH2] We used the term "message" for the outermost component of
a particular protocol. Since this is only a wording change and there are
lots of other changes coming in -01, I suggest that we set aside this
matter and revisit it when -01 has been published. We can ask WG
participants to weigh in with an opinion on this after they review -01.
It shouldn't be hard to make the change if that's WG consensus.
=09
	The use of PB vendor id is not clear   since the NEA Reference
model does not describe behavior with multiple  posture  broker
client(s)/server(s), not sure how vendor specific message  types at the
PB layer will be handled.=20
	=20
	[SH] We weren't  trying to support multiple PBCs or PBSs on one
device. We just wanted to allow  vendors to create extensions in a
compatible and standardized  manner.
=09
	<Kaushik-Response>
=09
	I think it might be helpful to articulate with examples the use
of the vendor-id at the PB layer and the nature of such extensions.
=09
	</Kaushik-Response>
=09
	[SH2] Good idea. I'll plan to add this in -01.=20
=09
	The need to create a  new  PT connection if the server is
required to send a SDATA after the  server has  sent a RESULT as
described at the end of Section 2.2. seems  like an artificial
limitation placed. This behavior should be left open  to implementations
so  that they can optimize in case a PT is more  capable than just a
half-duplex  behavior.
=09
	[SH] As currently defined, PB-TNC is a half-duplex  protocol.
While this is necessary when the underlying transport is  half-duplex
(EAP, for example), it is not necessary when the transport is
full-duplex. I suggest that we explore ways to ameliorate this problem.
For  example, we should allow PB-TNC to take advantage of full-duplex
transports but still ensure that it functions over half-duplex
transports. We can't really just leave the behavior open to
implementations.  That won't get us to interoperability.
=09
=09
	<Kaushik-Response>
=09
	Were you thinking about including an initial proposal/options of
addressing this in the next revision  ?
=09
	regards,
	 kaushik
=09
	</Kaushik-Response>
=09
	 [SH2] Yes, let's try to address this in -01. Let me start a
separate thread on this topic.
=09
	=20




------_=_NextPart_001_01C8C959.EBE5E264
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [Nea] Comments on NEA TNC PA & PB protocol =
specifications</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D890050211-08062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks, Kaushik. My responses below are marked =
[SH2]. To be=20
honest, I must say that I find this tagging mechanism more difficult to =
follow=20
than the old practice of using "&gt; " in a plain text email. But here =
we are in=20
an HTML thread so I will continue in kind. I will remove as much text as =
I can=20
so we can focus on the few remaining open issues.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D890050211-08062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D890050211-08062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D890050211-08062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D890050211-08062008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Steve</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Kaushik Narayan =
[mailto:kaushik@cisco.com]=20
<BR><B>Sent:</B> Sunday, June 08, 2008 12:36 AM<BR><B>To:</B> Stephen =
Hanna;=20
Paul Sangster; nea@ietf.org<BR><B>Subject:</B> Re: [Nea] Comments on NEA =
TNC PA=20
&amp; PB protocol specifications<BR></FONT><BR></DIV>
<DIV></DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
style=3D"FONT-SIZE: 12px">Hi Steve,<BR><BR>Thanks for your response. =
Please find=20
my response inline tagged &lt;Kaushik-Response&gt;<BR><BR></SPAN></FONT>
<BLOCKQUOTE><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  style=3D"FONT-SIZE: 12px">&lt;snipped&gt;<BR><BR></SPAN></FONT><SPAN=20
  style=3D"FONT-SIZE: 12px"><FONT color=3D#0000ff><FONT=20
  face=3DArial><BR></FONT></FONT></SPAN>
  <BLOCKQUOTE><SPAN style=3D"FONT-SIZE: 12px"><FONT =
color=3D#0000ff><FONT=20
    face=3DArial>[PS] Would &nbsp;a high level &nbsp;example that ties =
into the=20
    protocol flows help? &nbsp;Maybe &nbsp;something &nbsp;like the use =
cases=20
    from the requirements spec? Would you be &nbsp;willing to &nbsp;help =

    contribute some text for this? <BR><BR>&lt;Kaushik&gt; I think it =
would=20
    &nbsp;be good to use se cases from the requirements document to =
illustrate=20
    the &nbsp;flows. I can help with drawing out the example flows=20
    &lt;/Kaushik&gt;<BR>&nbsp;<BR></FONT></FONT><FONT=20
    face=3D"Verdana, Helvetica, Arial"><BR></FONT><FONT face=3DArial=20
    color=3D#0000ff>[SH] Are you willing to do this for PB-TNC=20
    &nbsp;also?<BR><BR>&lt;Kaushik-Response&gt;<BR><BR>Sure. I can take =
a crack=20
    at that; the flows will need to encompass both PA and PB protocol. I =
will=20
    try to pick use cases that exemplify PA and PB aspects to include in =
the=20
    respective protocol=20
    specifications.<BR><BR>&lt;/Kaushik-Response&gt;<BR><BR></FONT><FONT =

    face=3D"Verdana, Helvetica, Arial"><SPAN =
class=3D890050211-08062008><FONT=20
    face=3DArial color=3D#0000ff size=3D2>&nbsp;[SH2] =
&nbsp;Great!&nbsp;Thanks=20
    for&nbsp;volunteering for this=20
    task.</FONT></SPAN><BR>&nbsp;<BR></FONT></SPAN></BLOCKQUOTE>
  <DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial>PB =
protocol<BR><FONT=20
  color=3D#0000ff><BR></FONT></FONT><FONT face=3D"Verdana, Helvetica, =
Arial">The=20
  &nbsp;term &#8220;message&#8221; used to represent various PB layer =
&nbsp;attributes is=20
  very &nbsp;confusing; wondering why we can&#8217;t use the term =
&#8220;attribute&#8221;=20
  &nbsp;&nbsp;since &nbsp;that term is already used within the NEA =
Reference=20
  model to &nbsp;represent PB &nbsp;layer information.</FONT><FONT=20
  color=3D#0000ff><FONT face=3DArial>&nbsp;<BR></FONT></FONT><FONT=20
  face=3D"Verdana, Helvetica, Arial"><BR></FONT><FONT face=3DArial><FONT =

  color=3D#0000ff>[SH] Maybe this &nbsp;change would be helpful. I'm =
afraid we=20
  would end up with a similar &nbsp;problem: layers of different =
attributes (vs.=20
  &nbsp;messages).<BR><BR><SPAN class=3D890050211-08062008><FONT=20
  size=3D2>&nbsp;&lt;</FONT></SPAN>Kaushik-Response&gt;<BR><BR>I am not =
sure that=20
  there is a difference between attributes at the PA vs PB layers, they =
are just=20
  TLVs and in some cases might be similar in nature, for e.g. Posture =
assessment=20
  result at the PA layer and the global assessment result at the PB =
layer.=20
  <BR><BR>&lt;/Kaushik-Response&gt;<BR><SPAN =
class=3D890050211-08062008><FONT=20
  size=3D2>&nbsp;</FONT></SPAN></FONT></FONT></SPAN></DIV>
  <DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3DArial><FONT =
color=3D#0000ff><SPAN=20
  class=3D890050211-08062008><FONT size=3D2>[SH2] We used the term =
"message" for the=20
  outermost&nbsp;component of a particular protocol. Since this is only =
a=20
  wording change and there are lots of other changes coming in -01, I =
suggest=20
  that we set aside this matter and revisit it when -01 has been =
published. We=20
  can ask WG participants to weigh in with an opinion on this after they =
review=20
  -01. It shouldn't be hard to make the change if that's WG=20
  consensus.</FONT></SPAN><BR></FONT><BR>The use of PB vendor id is not =
clear=20
  &nbsp;&nbsp;since the NEA Reference model does not describe behavior =
with=20
  multiple &nbsp;posture &nbsp;broker client(s)/server(s), not sure how =
vendor=20
  specific message &nbsp;types at the &nbsp;PB layer will be=20
  handled.</FONT><FONT face=3DArial =
color=3D#0000ff>&nbsp;<BR></FONT><FONT=20
  face=3D"Verdana, Helvetica, Arial">&nbsp;<BR></FONT><FONT =
face=3DArial><FONT=20
  color=3D#0000ff>[SH] We weren't &nbsp;trying to support multiple PBCs =
or PBSs on=20
  one device. We just wanted to allow &nbsp;vendors to create extensions =
in a=20
  compatible and standardized=20
  &nbsp;manner.<BR><BR>&lt;Kaushik-Response&gt;<BR><BR>I think it might =
be=20
  helpful to articulate with examples the use of the vendor-id at the PB =
layer=20
  and the nature of such=20
  extensions.<BR><BR>&lt;/Kaushik-Response&gt;<BR><BR></FONT><SPAN=20
  class=3D890050211-08062008><FONT color=3D#0000ff =
size=3D2>[SH2]&nbsp;Good idea. I'll=20
  plan to add this in -01.&nbsp;</FONT></SPAN><BR><BR>The need to create =
a=20
  &nbsp;new &nbsp;PT connection if the server is required to send a =
SDATA after=20
  the &nbsp;server has &nbsp;sent a RESULT as described at the end of =
Section=20
  2.2. seems &nbsp;like an artificial &nbsp;limitation placed. This =
behavior=20
  should be left open &nbsp;to implementations so &nbsp;that they can =
optimize=20
  in case a PT is more &nbsp;capable than just a half-duplex=20
  &nbsp;behavior.<BR><BR></FONT><FONT face=3DArial color=3D#0000ff>[SH] =
As currently=20
  defined, PB-TNC is a half-duplex &nbsp;protocol. While this is =
necessary when=20
  the underlying transport is &nbsp;half-duplex (EAP, for example), it =
is not=20
  necessary when the transport is &nbsp;full-duplex. I suggest that we =
explore=20
  ways to ameliorate this problem. For &nbsp;example, we should allow =
PB-TNC to=20
  take advantage of full-duplex &nbsp;transports but still ensure that =
it=20
  functions over half-duplex &nbsp;transports. We can't really just =
leave the=20
  behavior open to implementations. &nbsp;That won't get us to=20
  interoperability.<BR><BR><BR>&lt;Kaushik-Response&gt;<BR><BR>Were you =
thinking=20
  about including an initial proposal/options of addressing this in the =
next=20
  revision=20
  =
&nbsp;?<BR><BR>regards,<BR>&nbsp;kaushik<BR><BR>&lt;/Kaushik-Response&gt;=
<BR></FONT><FONT=20
  face=3D"Verdana, Helvetica, Arial"><BR><SPAN =
class=3D890050211-08062008><FONT=20
  face=3DArial color=3D#0000ff size=3D2>&nbsp;[SH2] Yes, let's try to=20
  address&nbsp;this in -01.&nbsp;Let me start a separate thread on this=20
  topic.</FONT></SPAN></FONT></SPAN></DIV>
  <DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT=20
  face=3D"Verdana, Helvetica, Arial"><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT><BR>&nbsp;</DIV></FONT></SPAN></BLOCKQUOTE><SPAN=20
style=3D"FONT-SIZE: 12px"><FONT=20
face=3D"Verdana, Helvetica, Arial"><BR></FONT></SPAN></BODY></HTML>

------_=_NextPart_001_01C8C959.EBE5E264--

--===============0894509321==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea

--===============0894509321==--


From nea-bounces@ietf.org  Mon Jun  9 15:31:18 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E8B5A3A680D;
	Mon,  9 Jun 2008 15:31:18 -0700 (PDT)
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 265E13A67EF
	for <nea@core3.amsl.com>; Mon,  9 Jun 2008 15:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.532
X-Spam-Level: 
X-Spam-Status: No, score=-4.532 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
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 COJHS-w33UPb for <nea@core3.amsl.com>;
	Mon,  9 Jun 2008 15:31:17 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 536F43A68B7
	for <nea@ietf.org>; Mon,  9 Jun 2008 15:31:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,614,1204531200"; d="scan'208";a="77789307"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 09 Jun 2008 15:31:37 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m59MVbb1008170; 
	Mon, 9 Jun 2008 15:31:37 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m59MVbaw025666;
	Mon, 9 Jun 2008 22:31:37 GMT
Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jun 2008 15:31:37 -0700
Received: from 171.69.75.173 ([171.69.75.173]) by xmb-sjc-22d.amer.cisco.com
	([128.107.191.68]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  9 Jun 2008 22:31:36 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Mon, 09 Jun 2008 15:31:38 -0700
From: Kaushik Narayan <kaushik@cisco.com>
To: Paul Sangster <Paul_Sangster@symantec.com>,
	Stephen Hanna <shanna@juniper.net>, "Sahita, Ravi" <ravi.sahita@intel.com>,
	Ryan Hurst <Ryan.Hurst@microsoft.com>, "nea@ietf.org" <nea@ietf.org>,
	"Susan Thomson (sethomso)" <sethomso@cisco.com>
Message-ID: <C472FD5A.1A0FF%kaushik@cisco.com>
Thread-Topic: Protocol names, titles & filenames for PA & PB protocol
 drafts
Thread-Index: AcjKgJS70xym/jZzEd2TpQAX8tamGQ==
Mime-version: 1.0
X-OriginalArrivalTime: 09 Jun 2008 22:31:37.0337 (UTC)
	FILETIME=[94565690:01C8CA80]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=429; t=1213050697; x=1213914697;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kaushik@cisco.com;
	z=From:=20Kaushik=20Narayan=20<kaushik@cisco.com>
	|Subject:=20Protocol=20names,=20titles=20&=20filenames=20fo
	r=20PA=20&=20PB=20protocol=20drafts |Sender:=20;
	bh=rl+YzLbTcv6GGjdS8wWREo/LX3p0SA6P0GFngntysQw=;
	b=XOXGI9GgKDezpM0Te55RlyLKIvaFn0ZJzjdQ1za9GrmkeeNSveHt+qJT7V
	FohaplNqMbI2SDmfW7x8kElgq3yAF4IU2D1aIqFb1NjozU9bJclJxD70xmWA
	T0shL3fX0u;
Authentication-Results: sj-dkim-4; header.From=kaushik@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: [Nea] Protocol names, titles & filenames for PA & PB protocol drafts
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

Hi,

The current names of the PA & PB protocol drafts are PA-TNC and PB-TNC and
the title of both drafts includes "Compatible with TNC". The file names also
currently include tnc.

I am wondering whether we need a change to titles/names to clarify that the
WG is not adopting the TNC protocols but using the TNC protocols as an
initial definition (-00 version) to create the NEA PA & PB protocols.

Regards,
 kaushik


_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea


From nea-bounces@ietf.org  Mon Jun  9 17:49:31 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B1453A6875;
	Mon,  9 Jun 2008 17:49:31 -0700 (PDT)
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 0B16E3A6875
	for <nea@core3.amsl.com>; Mon,  9 Jun 2008 17:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	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 y+Dm1bq8veSe for <nea@core3.amsl.com>;
	Mon,  9 Jun 2008 17:49:28 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157])
	by core3.amsl.com (Postfix) with ESMTP id 19CC43A681A
	for <nea@ietf.org>; Mon,  9 Jun 2008 17:49:23 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob102.postini.com
	([64.18.6.12]) with SMTP; Mon, 09 Jun 2008 17:49:36 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp02.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 9 Jun 2008 17:49:12 -0700
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb01-sac.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Jun 2008 17:49:12 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by emailwf1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jun 2008 20:49:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 9 Jun 2008 20:48:10 -0400
Message-ID: <A6398B0DB62A474C82F61554EE9372870586F650@proton.jnpr.net>
In-Reply-To: <C472FD5A.1A0FF%kaushik@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Protocol names, titles & filenames for PA & PB protocol drafts
Thread-Index: AcjKgJS70xym/jZzEd2TpQAX8tamGQAERFOA
References: <C472FD5A.1A0FF%kaushik@cisco.com>
From: "Stephen Hanna" <shanna@juniper.net>
To: "Kaushik Narayan" <kaushik@cisco.com>,
	"Paul Sangster" <Paul_Sangster@symantec.com>,
	"Sahita, Ravi" <ravi.sahita@intel.com>,
	"Ryan Hurst" <Ryan.Hurst@microsoft.com>, <nea@ietf.org>,
	"Susan Thomson (sethomso)" <sethomso@cisco.com>
X-OriginalArrivalTime: 10 Jun 2008 00:49:11.0357 (UTC)
	FILETIME=[CC1DD6D0:01C8CA93]
Subject: Re: [Nea] Protocol names,
	titles & filenames for PA & PB protocol drafts
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

I don't see a problem here. As stated in the drafts, the TCG is planning
to
adopt TNC protocols equivalent to PA-TNC and PB-TNC when PA-TNC and
PB-TNC
are approved as RFCs by the IETF. So the end result will be that the
IETF
RFCs and the TNC protocols will be equivalent. That is the goal and it's
a good one, I think. Customers want to have one set of standard
protocols,
approved by and agreed on by all parties.  So when we're done, we'll
have
IETF protocols that are compatible with TNC. That's what the titles say.

I do think that the background on TCG and TNC in section 1 of the specs
should be scaled back substantially but I think that we should include
some explanatory text saying that these specs are equivalent to the TNC
specs IF-M 1.0 and IF-TNCCS 2.0 and giving informative references to
those. This will help people who want to find the TNC specs to do so.

What do other people think?

Thanks,

Steve

-----Original Message-----
From: Kaushik Narayan [mailto:kaushik@cisco.com] 
Sent: Monday, June 09, 2008 6:32 PM
To: Paul Sangster; Stephen Hanna; Sahita, Ravi; Ryan Hurst;
nea@ietf.org; Susan Thomson (sethomso)
Subject: Protocol names, titles & filenames for PA & PB protocol drafts

Hi,

The current names of the PA & PB protocol drafts are PA-TNC and PB-TNC
and
the title of both drafts includes "Compatible with TNC". The file names
also
currently include tnc.

I am wondering whether we need a change to titles/names to clarify that
the
WG is not adopting the TNC protocols but using the TNC protocols as an
initial definition (-00 version) to create the NEA PA & PB protocols.

Regards,
 kaushik


_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea


From nea-bounces@ietf.org  Tue Jun 10 07:58:25 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E8E023A6A2A;
	Tue, 10 Jun 2008 07:58:25 -0700 (PDT)
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 E755C3A6A0F
	for <nea@core3.amsl.com>; Tue, 10 Jun 2008 07:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	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 dLQ9+G7aeR3Q for <nea@core3.amsl.com>;
	Tue, 10 Jun 2008 07:58:24 -0700 (PDT)
Received: from extu-mxob-1.symantec.com (extu-mxob-1.symantec.com
	[216.10.194.28])
	by core3.amsl.com (Postfix) with ESMTP id D3BA73A6993
	for <nea@ietf.org>; Tue, 10 Jun 2008 07:58:23 -0700 (PDT)
Received: from tus1opsmtapin01.ges.symantec.com
	(tus1opsmtapin01.ges.symantec.com [192.168.214.43])
	by extu-mxob-1.symantec.com (8.14.1/8.14.1) with ESMTP id
	m5AEwckR013251
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Jun 2008 07:58:43 -0700
Received: from reserved-155-64-230-18.ges.symantec.com ([155.64.230.18]
	helo=TUS1XCHECNPIN01.enterprise.veritas.com)
	by tus1opsmtapin01.ges.symantec.com with esmtp (Exim 4.67)
	(envelope-from <Paul_Sangster@symantec.com>)
	id 1K65Iq-0001ID-4z; Tue, 10 Jun 2008 07:58:28 -0700
Received: from TUS1XCHEVSPIN05.enterprise.veritas.com ([155.64.231.28]) by
	TUS1XCHECNPIN01.enterprise.veritas.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 10 Jun 2008 07:58:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 10 Jun 2008 07:58:13 -0700
Message-ID: <AB96CED633A7C246BDC661DBEE1CF01F03D19C6D@TUS1XCHCLUPIN12.enterprise.veritas.com>
In-Reply-To: <A6398B0DB62A474C82F61554EE9372870586F650@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Protocol names, titles & filenames for PA & PB protocol drafts
thread-index: AcjKgJS70xym/jZzEd2TpQAX8tamGQAERFOAAAkNhJA=
References: <C472FD5A.1A0FF%kaushik@cisco.com>
	<A6398B0DB62A474C82F61554EE9372870586F650@proton.jnpr.net>
From: "Paul Sangster" <Paul_Sangster@symantec.com>
To: "Stephen Hanna" <shanna@juniper.net>,
	"Kaushik Narayan" <kaushik@cisco.com>,
	"Sahita, Ravi" <ravi.sahita@intel.com>,
	"Ryan Hurst" <Ryan.Hurst@microsoft.com>, <nea@ietf.org>,
	"Susan Thomson (sethomso)" <sethomso@cisco.com>
X-OriginalArrivalTime: 10 Jun 2008 14:58:28.0542 (UTC)
	FILETIME=[70F735E0:01C8CB0A]
Subject: Re: [Nea] Protocol names,
	titles & filenames for PA & PB protocol drafts
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

I too wondered about the names (PA-TNC, PB-TNC) whether these make sense
for IETF specs.  I too think the strategy makes good sense as does
stating the linkage between the org's standards in the specs so
customers know we're addressing their concern and working together.  It
also makes sense to credit the origin of the specs and including an
informal ref.  Not sure we need to do a lot more.

I suspect the core question is PA or PA-TNC (right?).  I don't have a
strong preference since they are just names. 

> -----Original Message-----
> From: Stephen Hanna [mailto:shanna@juniper.net] 
> Sent: Monday, June 09, 2008 5:48 PM
> To: Kaushik Narayan; Paul Sangster; Sahita, Ravi; Ryan Hurst; 
> nea@ietf.org; Susan Thomson (sethomso)
> Subject: RE: Protocol names, titles & filenames for PA & PB 
> protocol drafts
> 
> I don't see a problem here. As stated in the drafts, the TCG 
> is planning to adopt TNC protocols equivalent to PA-TNC and 
> PB-TNC when PA-TNC and PB-TNC are approved as RFCs by the 
> IETF. So the end result will be that the IETF RFCs and the 
> TNC protocols will be equivalent. That is the goal and it's a 
> good one, I think. Customers want to have one set of standard 
> protocols, approved by and agreed on by all parties.  So when 
> we're done, we'll have IETF protocols that are compatible 
> with TNC. That's what the titles say.
> 
> I do think that the background on TCG and TNC in section 1 of 
> the specs should be scaled back substantially but I think 
> that we should include some explanatory text saying that 
> these specs are equivalent to the TNC specs IF-M 1.0 and 
> IF-TNCCS 2.0 and giving informative references to those. This 
> will help people who want to find the TNC specs to do so.
> 
> What do other people think?
> 
> Thanks,
> 
> Steve
> 
> -----Original Message-----
> From: Kaushik Narayan [mailto:kaushik@cisco.com]
> Sent: Monday, June 09, 2008 6:32 PM
> To: Paul Sangster; Stephen Hanna; Sahita, Ravi; Ryan Hurst; 
> nea@ietf.org; Susan Thomson (sethomso)
> Subject: Protocol names, titles & filenames for PA & PB 
> protocol drafts
> 
> Hi,
> 
> The current names of the PA & PB protocol drafts are PA-TNC 
> and PB-TNC and the title of both drafts includes "Compatible 
> with TNC". The file names also currently include tnc.
> 
> I am wondering whether we need a change to titles/names to 
> clarify that the WG is not adopting the TNC protocols but 
> using the TNC protocols as an initial definition (-00 
> version) to create the NEA PA & PB protocols.
> 
> Regards,
>  kaushik
> 
> 
> 
_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea


From nea-bounces@ietf.org  Mon Jun 16 12:02:38 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 65CD13A6B24;
	Mon, 16 Jun 2008 12:02:38 -0700 (PDT)
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 5B1783A6B29
	for <nea@core3.amsl.com>; Mon, 16 Jun 2008 12:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[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 qNZu2OKive2G for <nea@core3.amsl.com>;
	Mon, 16 Jun 2008 12:02:32 -0700 (PDT)
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
	by core3.amsl.com (Postfix) with ESMTP id C60083A6B27
	for <nea@ietf.org>; Mon, 16 Jun 2008 12:01:09 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19])
	by fmsmga101.fm.intel.com with ESMTP; 16 Jun 2008 11:58:23 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.27,654,1204531200"; d="scan'208";a="261334127"
Received: from orsmsx334.amr.corp.intel.com (HELO orsmsx334.jf.intel.com)
	([10.22.226.45])
	by azsmga001.ch.intel.com with ESMTP; 16 Jun 2008 12:01:39 -0700
Received: from orsmsx418.amr.corp.intel.com ([10.22.226.87]) by
	orsmsx334.jf.intel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Jun 2008 12:01:39 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 16 Jun 2008 12:01:38 -0700
Message-ID: <71AEC96DF4AAD9409103ECD04F70D48004EEF13B@orsmsx418.amr.corp.intel.com>
In-Reply-To: <C3EC90EE.1B0C%gtomlinson@SonicWALL.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Nea] Comments on draft-sahita-nea-pb-tnc-00.txt
Thread-Index: Ach6aY+izjCeMuZcEdyVBwAbY6BmHBNvwWrQ
References: <C3EC90EE.1B0C%gtomlinson@SonicWALL.com>
From: "Sahita, Ravi" <ravi.sahita@intel.com>
To: <nea@ietf.org>,
	"Gary Tomlinson" <gtomlinson@SonicWALL.com>
X-OriginalArrivalTime: 16 Jun 2008 19:01:39.0227 (UTC)
	FILETIME=[682B8EB0:01C8CFE3]
Subject: Re: [Nea] Comments on draft-sahita-nea-pb-tnc-00.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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org


Thanks to Gary for his detailed review and comments on the PB-TNC draft
- 
I have some replies inline prefixed by Ravi>

Regards,
Ravi

-----Original Message-----
From: nea-bounces@ietf.org [mailto:nea-bounces@ietf.org] On Behalf Of
Gary Tomlinson
Sent: Thursday, February 28, 2008 4:25 PM
To: nea@ietf.org
Subject: [Nea] Comments on draft-sahita-nea-pb-tnc-00.txt

The following comments are regarding the individual submission
draft-sahita-nea-pb-tnc-00.txt of a PB protocol for consideration by the
NEA
working group as a base to develop the PB protocol from.

First, an overall comment is this is a very well written document and in
my
opinion should be be strongly considered by the WG as its scope covers
all
of the PB requirements specified to date.

Ravi> Thanks!


Of course I do have some specific comments.  Here they are:

Page 12, section 3.2. PB-TNC Message Length description, last sentence
...
SHOULD send an Invalid Parameter ...  For a protocol violation, why is
this
a SHOULD and not a MUST?

Ravi> Agree - this will be changed to a MUST



Page 19,  section 3.6.Posture Collector Identifier.  My first reaction
to
this being assigned by the Posture Broker Client as a local node scoped
address was how can a Posture Broker Server know how to discover it in
order
to initiate a message to it.  Upon reviewing the PA-TNC protocol
submission
I learned a PA Attribute Request addressed to ANY Posture Collector of a
PA
subtype can be used to discover specific Posture Collector Identifiers.
Since I was unable to derive this strictly from the PB-TNC draft, it
occurs
to me some clarification might be in order that states the dependence
upon
the PA protocol for discovery of Posture Collector Identifiers by
Posture
Server Brokers/Validators.

Ravi> The assumption here is that, the PB Client assigns the unique
Posture Collector Identifiers (PCI) and the PB server assigns the unique
Posture Validator Identifiers (PVI) to be able to multiplex and
de-multiplex messages that are exclusively meant for specific Posture
Collectors or Posture Validators. In the case you mentioned, where the
PB server sends the initial message, the expected behavior is that the
PB server will use the standard PA Message Vendor ID (0) and all f's PCI
to route PA-attribute request messages to the Posture Collectors, and
the Collectors that provide the requested posture information will
respond, which the PB Client will package with the currently allocated
PCIs. After this response the PB server can name the appropriate PCI as
required.



Page 20, section 3.6. PN-TNC Posture Validator Identifier.  This is
essentially the same comment as I made regarding the Posture Collector
Identifier but from the inverse relationship of the Posture Broker
Client
discovering specific Posture Validators; however I was unable to derive
a
condoned method since PA-TNC Attribute Requests aren't supposed to be
sent
by Posture Collectors except for PA-TNC Security crypto algorithm
support
discovery.  With this in mind, how can a Posture Broker Client direct a
message to a specific Posture Validotor without having had previous
communication with it?

Ravi> The PA vendor Id could always be used to route information to a
specific vendors Posture Validator. In the case the message is an IETF
standardized PA attribute exchange, the standard PA Message Vendor id
(0) and the standard set of PA sub-types will be used with an all f's
PVI, which will cause the message to be routed by the PB server to all
the Posture Validators on the PB server that claim to be belonging to
the "standard sub-types" listed in PA-TNC. The contacted Validator's
will respond with the response which will be packaged by the PB Server
with the appropriate PVI so that further communication can continue with
specific Validators if required.  



Page 22, section 3.7 Access Recommendation code.  For the access code
value
Access Allowed=1, I was unable to determine in the protocol at large how
to
support the reassessment use case where the Posture Broker Server needs
to
control the reassessment interval but can't initiate a new connection to
restart the state machine.  This is a common problem when TLS is used as
PT
and intermediary security devices such as firewalls and NATs block
connections to the end point device. One new solution that occurred to
me
was the reserved field could become a flags field with a reassessment
flag
bit and an additional 32 bit field could be added with the number of
seconds
until a reassessment is required.  The reassessment bit if set would
enable
the value in the reassessment field to be used by the Posture Broker
Client
to initiate a new assessment sequence.  This capability would also
address
the reassessment points made on page 35 section 4.2.

Ravi> good point - as you suggest we should add a timer field such that
the Posture Client can reconnect after the timer expires. I think this
will address the issue you highlight above. Another note - It may be
useful to also have a new command code to allow for a server initiated
re-assessment - this is for cases when an event occurs in the network
(for example, detected by some intrusion detection system) that causes
the NEA server to reevaluate the posture of the NEA client.



Page 25, Section 3.8 Remediation Parameters last paragraph.  The
ambiguity
faced with a protocol error needs to be resolved.  I would argue that a
malformed RESULT message from the Posture Server Broker doesn't
constitute a
proper transition to the DECIDED state and that we need the capability
to
issue a Parameter Error message as reply to any transition in the state
machine and transition back to the callers previous state.

Ravi> Agree also - We should add in the next rev.



Page 38, section 4.11.  In addition to carrying attributes, PB-TNC
provides
explicit attribute support for posture decision and remediation aid
notification.

Ravi> thanks for the good clarification to the section - we should add
it in the next rev.


Regards,
Ravi

_______________________________________________
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


From nea-bounces@ietf.org  Tue Jun 17 10:42:06 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8B9E3A6932;
	Tue, 17 Jun 2008 10:42:06 -0700 (PDT)
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 324373A6932
	for <nea@core3.amsl.com>; Tue, 17 Jun 2008 10:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_56=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 6tUn1Ds3g2Lq for <nea@core3.amsl.com>;
	Tue, 17 Jun 2008 10:42:03 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7ob116.obsmtp.com [64.18.2.218])
	by core3.amsl.com (Postfix) with ESMTP id 868C63A685D
	for <nea@ietf.org>; Tue, 17 Jun 2008 10:42:03 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob116.postini.com
	([64.18.6.12]) with SMTP; Tue, 17 Jun 2008 10:42:31 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp03.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 17 Jun 2008 10:41:51 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 17 Jun 2008 10:41:51 -0700
Received: from antimuon.jnpr.net ([172.24.60.32]) by emailsmtp55.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 17 Jun 2008 10:41:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 17 Jun 2008 10:41:24 -0700
Message-ID: <1039CD74656F7B42816FE6532F32C19406253DA7@antimuon.jnpr.net>
In-Reply-To: <AB96CED633A7C246BDC661DBEE1CF01F03D19C6D@TUS1XCHCLUPIN12.enterprise.veritas.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Nea] Protocol names,
	titles & filenames for PA & PB protocol drafts
Thread-Index: AcjKgJS70xym/jZzEd2TpQAX8tamGQAERFOAAAkNhJABeruBEA==
From: "Lisa Lorenzin" <llorenzin@juniper.net>
To: <nea@ietf.org>
X-OriginalArrivalTime: 17 Jun 2008 17:41:51.0538 (UTC)
	FILETIME=[6CE5F120:01C8D0A1]
Subject: Re: [Nea] Protocol names,
	titles & filenames for PA & PB protocol drafts
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org

Hi all,

Paul wrote:

> I suspect the core question is PA or PA-TNC (right?).  I 
> don't have a strong preference since they are just names. 

Is future expansion a consideration?  The TNC-based PA and 
PB are one set of NEA PA & PB protocols; in the future, there
could be additional PA and PB protocols defined.  If we keep
the PA-TNC and PB-TNC names, we have a clear naming convention
differentiating possible future PA & PB protocols from other 
origins.

						Regards,

							Lisa

--
Lisa Lorenzin / 919-384-7275 / llorenzin@juniper.net 
Principal Solutions Architect - Security Solutions
Juniper Networks            http://www.juniper.net
_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea


From nea-bounces@ietf.org  Thu Jun 26 15:43:46 2008
Return-Path: <nea-bounces@ietf.org>
X-Original-To: nea-archive@megatron.ietf.org
Delivered-To: ietfarch-nea-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18F8E3A6A08;
	Thu, 26 Jun 2008 15:43:46 -0700 (PDT)
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 A75FD3A67EF;
	Thu, 26 Jun 2008 15:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.285
X-Spam-Level: 
X-Spam-Status: No, score=-17.285 tagged_above=-999 required=5
	tests=[AWL=0.314, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 rXr1eu9Bxi3e; Thu, 26 Jun 2008 15:43:42 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 87D393A67CF;
	Thu, 26 Jun 2008 15:43:42 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 4F1291390E3; Thu, 26 Jun 2008 15:43:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080626224346.4F1291390E3@bosco.isi.edu>
Date: Thu, 26 Jun 2008 15:43:46 -0700 (PDT)
Cc: nea@ietf.org, rfc-editor@rfc-editor.org
Subject: [Nea] RFC 5209 on Network Endpoint Assessment (NEA): Overview and
	Requirements
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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nea-bounces@ietf.org
Errors-To: nea-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5209

        Title:      Network Endpoint Assessment (NEA): Overview 
                    and Requirements 
        Author:     P. Sangster, H. Khosravi,
                    M. Mani, K. Narayan,
                    J. Tardo
        Status:     Informational
        Date:       June 2008
        Mailbox:    Paul_Sangster@symantec.com, 
                    hormuzd.m.khosravi@intel.com, 
                    mmani@avaya.com,  kaushik@cisco.com, 
                    joseph.tardo@nevisnetworks.com
        Pages:      53
        Characters: 132227
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nea-requirements-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5209.txt

This document defines the problem statement, scope, and protocol
requirements between the components of the NEA (Network Endpoint
Assessment) reference model.  NEA provides owners of networks (e.g.,
an enterprise offering remote access) a mechanism to evaluate the
posture of a system.  This may take place during the request for
network access and/or subsequently at any time while connected to the
network.  The learned posture information can then be applied to a
variety of compliance-oriented decisions.  The posture information is
frequently useful for detecting systems that are lacking or have
out-of-date security protection mechanisms such as: anti-virus and
host-based firewall software.  In order to provide context for the
requirements, a reference model and terminology are introduced.  This memo provides information for the Internet community.

This document is a product of the Network Endpoint Assessment Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
USC/Information Sciences Institute


_______________________________________________
Nea mailing list
Nea@ietf.org
https://www.ietf.org/mailman/listinfo/nea


