Hey Melinda,
I’ve been involved with the IETF from the beginning, over 30 years now, and
there are a lot of ways to contribute to the process.  There was a call for 
opinions
on the list, and I offered an opinion.  This is about the only thing that makes 
the
IETF the IETF, the ability to contribute through the mailing list.  Chair 
didn’t like
my response and asked others to chime in.  Great, but no one has taken up the
call, except you and David with aspirations to make good protocols but not
do too much work, and strange confrontational statements about how charters
don’t matter and that HTTP is a great protocol.

It would be nice to hear from others on this topic.

Carter

> On Feb 7, 2015, at 2:12 PM, Melinda Shore <[email protected]> wrote:
> 
> On 2/7/15 9:52 AM, Carter Bullard wrote:
>> David,
>> And it is still pretty simple.  Want to do something different from what
>> is in the charter, change the charter.
>> But as long as the charter specifies a process, the WG should follow
>> that process.
> 
> The charter is negotiable as the working group makes (or doesn't
> make) progress, and despite your assertions to the contrary, there
> are other documents that govern working group process.  If I had
> to put it in standards language, the charter is informative and
> the process RFCs are normative.
> 
> Out of curiosity, I went to look at what your experience with the
> IETF has been, and I found that you've submitted no drafts
> (and consequently have no working group drafts, which means that
> you haven't gotten a document through the working group process),
> and if you've attended a meeting it hasn't been in the last year
> and a half.  The reason that I was curious about this is that your
> understanding about what the process is is significantly
> different from those with substantial experience with IETF
> process.  You've been making an awful lot of assertions about what
> it is - what's your basis for it?
> 
> Melinda
> 
> _______________________________________________
> nvo3 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nvo3
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to