Re: Violation of IETF process

2012-01-26 Thread todd glassey
On 1/25/2012 11:57 PM, SM wrote: > Hi Adrian, > At 21:48 25-01-2012, Adrian Farrel wrote: >> Why is Qian Sun still listed on the front page as an author. Wouldn't >> it be more >> appropriate to move the name to the Acknowledgements section where the >> text >> could read... > > As editorship is a

RE: Violation of IETF process (was: Second Last Call: (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard)

2012-01-26 Thread SM
At 07:25 26-01-2012, Adrian Farrel wrote: I have not made any statement about what the company has done. Ok. I don't view *disclosing* as a problem here. In fact disclosure is to be encouraged. I too don't view disclosing as a problem here. It is possible to compare the statement with oth

RE: Violation of IETF process (was: Second Last Call: (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard)

2012-01-26 Thread Adrian Farrel
> >Why is Qian Sun still listed on the front page as an author. > >Wouldn't it be more > >appropriate to move the name to the Acknowledgements section where the > > text could read... > > As editorship is a WG Chair decision, it is up to the SIEVE WG Chairs > to comment on why Qian Sun is still li

RE: Violation of IETF process (was: Second Last Call: (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard)

2012-01-26 Thread Murray S. Kucherawy
> -Original Message- > From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of SM > Sent: Wednesday, January 25, 2012 11:58 PM > To: adr...@olddog.co.uk > Cc: si...@ietf.org; ietf@ietf.org > Subject: RE: Violation of IETF process (was: Second Last Call:

RE: Violation of IETF process (was: Second Last Call: (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard)

2012-01-26 Thread SM
Hi Adrian, At 21:48 25-01-2012, Adrian Farrel wrote: Why is Qian Sun still listed on the front page as an author. Wouldn't it be more appropriate to move the name to the Acknowledgements section where the text could read... As editorship is a WG Chair decision, it is up to the SIEVE WG Chairs

RE: Violation of IETF process (was: Second Last Call: (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard)

2012-01-25 Thread Adrian Farrel
f.org; ietf@ietf.org > Subject: Violation of IETF process (was: Second Last Call: sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed > Standard) > > At 17:40 25-01-2012, Pete Resnick wrote: > >Correct, except let's call it an "Internet Draft"

Violation of IETF process (was: Second Last Call: (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard)

2012-01-25 Thread SM
At 17:40 25-01-2012, Pete Resnick wrote: Correct, except let's call it an "Internet Draft" for precision's sake. What this thread is actually about is a violation of IETF process (BCP) or IETF policy (Failure to comply with patent disclosure requirements is a violation