Re: [Nea] Judging consensus on NEA protocol proposals
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nea] Judging consensus on NEA protocol proposals
I was present at IETF 71 and participated in the room consensus check. My
position there was and still is.
Agree with the room consensus draft-sahita-nea-pb-tnc-00 be accepted as the
starting point for PB protocol work.
Agree with the room consensus draft-sangster-nea-pa-tnc-00 be accepted as
the starting point for PA protocol works.
Agree with the room consensus draft-sangster-ne-tnc-security-00 not be
considered at this time by the work group.
Gary
On 3/25/08 12:00 PM, "nea-request at ietf.org" <nea-request at ietf.org> wrote:
> 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. Re: Judging consensus on NEA protocol proposals (Stefan Winter)
> 2. Re: Judging consensus on NEA protocol proposals (Wei Jiwei)
> 3. Re: Judging consensus on NEA protocol proposals
> (Gene Chang (genchang))
> 4. Re: Judging consensus on NEA protocol proposals (Han Yin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 25 Mar 2008 07:39:53 +0100
> From: Stefan Winter <stefan.winter at restena.lu>
> Subject: Re: [Nea] Judging consensus on NEA protocol proposals
> To: nea at ietf.org
> Message-ID: <200803250739.58302.stefan.winter at restena.lu>
> Content-Type: text/plain; charset="iso-8859-1"
>
> agree with all three decisions
_______________________________________________
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.