Re: [Nea] Nea Digest, Vol 38, Issue 3
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nea] Nea Digest, Vol 38, Issue 3



I support the proposal to  the proposal to decouple assertion attributes from
the base protocol specifications.

Thank you
Beza


Quoting nea-request at ietf.org:

> Send Nea mailing list submissions to
> 	nea at ietf.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/nea
> or, via email, send a message with subject or body 'help' to
> 	nea-request at ietf.org
> 
> You can reach the person managing the list at
> 	nea-owner at ietf.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Nea digest..."
> 
> 
> Today's Topics:
> 
>    1. Consensus check on NEA IANA Considerations (Stephen Hanna)
>    2. Consensus check on Assertion Attributes (Stephen Hanna)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 26 Dec 2008 16:15:14 -0500
> From: Stephen Hanna <shanna at juniper.net>
> Subject: [Nea] Consensus check on NEA IANA Considerations
> To: <nea at ietf.org>
> Message-ID: <A6398B0DB62A474C82F61554EE93728706D1037D at proton.jnpr.net>
> Content-Type: text/plain; charset="us-ascii"
> 
> At the NEA WG meeting at IETF 73, there was a
> discussion about IANA Considerations for PA-TNC
> and PB-TNC. At the meeting, there was consensus
> in the room for this proposal:
> 
> ----------
> 
> For all IANA registries defined in PA-TNC and
> PB-TNC, the following requirements must be met
> to add an entry to the registry:
> 
> - Expert Review
> - Specification Publically Available (RFC or other
>   IANA archived document)
> - Specification must be clear and ensure interoperability
> - Must be judged useful and not harmful to the Internet
> 
> Values with PEN <> 0 could also be registered. The same
> requirements would apply except that the "useful and not
> harmful" requirement would be waived.
> 
> ----------
> 
> I want to check consensus on our email list for this
> proposal. Please send email to the nea at ietf.org list
> indicating whether you support or oppose the proposal.
> 
> 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
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 26 Dec 2008 16:15:15 -0500
> From: Stephen Hanna <shanna at juniper.net>
> Subject: [Nea] Consensus check on Assertion Attributes
> To: <nea at ietf.org>
> Message-ID: <A6398B0DB62A474C82F61554EE93728706D1037E at proton.jnpr.net>
> Content-Type: text/plain; charset="us-ascii"
> 
> 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
> 
> 
> End of Nea Digest, Vol 38, Issue 3
> **********************************
> 


Find Botswana with bezab.biz
_______________________________________________
Nea mailing list
Nea at ietf.org
https://www.ietf.org/mailman/listinfo/nea



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.