|
Loading...
|
sieve@ietf.org
[Prev] Thread [Next] | [Prev] Date [Next]
[sieve] Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) SM Thu Feb 02 21:04:55 2012
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 of IETF policy, and the potential legal consequences to companies are considerable).
For context: "Qian Sun is apparently no longer an active IETF participant, and his co-workers who are active IETF participants asked their company to disclose against the two documents as soon as they discovered what had happened. That's where were are now." Regards,-sm
_______________________________________________ sieve mailing list [EMAIL PROTECTED] https://www.ietf.org/mailman/listinfo/sieve
- [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard The IESG 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Adam Roach 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Pete Resnick 2012/02/02
- [sieve] Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) SM 2012/02/02 <=
- Re: [sieve] Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) Adrian Farrel 2012/02/02
- Re: [sieve] Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) SM 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Adrian Farrel 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Peter Saint-Andre 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Thomas Nadeau 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Worley, Dale R (Dale) 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Pete Resnick 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard John C Klensin 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard Harald Alvestrand 2012/02/02
- Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Not ifica tion Mechanism: SIP MESSAGE) to Proposed Standard John C Klensin 2012/02/02