> Date:Thu, 30 Jun 2005 21:12:07 -0400
> From:Jeffrey Hutzelman <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
>
> | Note that I would consider it entirely reasonable for the IESG to say
> that
> | something "conflicts with work in the IETF" on the grounds
> "John" == John C Klensin <[EMAIL PROTECTED]> writes:
>> Yes, the IESG could abuse its power in the future. For example
>> if it failed to charter work for one of the previous options in
>> the presence of significant community support, then the IESG
>> would be abusing its po
kre;
> | Note that I would consider it entirely reasonable for the IESG to say
> that
> | something "conflicts with work in the IETF" on the grounds that its
> | deployment would break the Internet, since preserving the stability of
> the
> | Internet is a fundamental part of _all_ IE
Date:Thu, 30 Jun 2005 21:12:07 -0400
From:Jeffrey Hutzelman <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| Note that I would consider it entirely reasonable for the IESG to say that
| something "conflicts with work in the IETF" on the grounds that its
|
Date:Thu, 30 Jun 2005 17:21:10 -0400
From:Sam Hartman <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| The RFc 2780 procedures are a sparse. We'd all be happier if the
| community had given us more advice on what criteria to use when
| evaluating hop-by-ho
On Thursday, June 30, 2005 06:50:30 PM -0400 John C Klensin
<[EMAIL PROTECTED]> wrote:
It seems to me that the key text in 3932 is
In March 2004, the IESG decided to make a major change
in this review model. The new review model will have
the
--On Thursday, 30 June, 2005 17:21 -0400 Sam Hartman
<[EMAIL PROTECTED]> wrote:
>> "John" == John C Klensin <[EMAIL PROTECTED]> writes:
>
> John> Hans, I think this formulation is consistent with
> what I, John> and others, have been trying to say. I
> would, however, add John>
> "John" == John C Klensin <[EMAIL PROTECTED]> writes:
John> Hans, I think this formulation is consistent with what I,
John> and others, have been trying to say. I would, however, add
John> one element.
John> However, especially since the IETF maintains liaisons with
John>
