[Nea] Consensus check on Assertion Attributes

[Stephen Hanna <shanna at juniper.net>]

At the NEA WG meeting at IETF 73, there was a
discussion about assertion attributes. I want
to check consensus on our email list for the
results of that discussion.

First, some background. RFC 5209 defines assertion
attributes as "attributes that include reusable
information about the success of a prior
assessment of the endpoint". RFC 5209 does not
contain any requirement that PA-TNC and PB-TNC
support assertion attributes but it would be
good to support these attributes since they can
be used to skip a full assessment when one has
recently been done. The current PA-TNC and PB-TNC
specs do not include explicit support for assertion
attributes but they are extensible enough that
support for these attributes could be added later.

At the end of the NEA WG discussion on this topic
at IETF 73, there was consensus in the room to not
hold up the current protocol documents to include
assertion attributes. Rather, support for assertion
attributes would be specified in a separate document.
This will allow for proposals to be solicited and
properly considered without further delaying the
base protocol specifications, which are already
behind schedule.

So please send email to the nea at ietf.org list
indicating whether you support or oppose the
proposal to decouple assertion attributes from
the base protocol specifications.

In light of the holiday season, this consensus
check will end in two weeks, at 5 PM EST (2200 GMT)
on Friday, January 9.

Thanks,

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