When is a 3933 experiment necessary? [Was: Last Call: draft-farrell-ft-03.txt (A Fast-Track way to RFC with Running Code) to Experimental RFC]

2013-01-30 Thread Adrian Farrel
Well, is that a meta-judgment call? I took the view that the full process expressed in draft-farrell-ft could not be done by the IESG at their discretion. That is, that some of the steps proposed constituted a significant variation from documented processes or well-established behavior. Thus, it

RE: When is a 3933 experiment necessary? [Was: Last Call: draft-farrell-ft-03.txt (A Fast-Track way to RFC with Running Code) to Experimental RFC]

2013-01-30 Thread Romascanu, Dan (Dan)
I believe that Adrian did right in this case. This was IMO one of the situations which in Spencer's language was 'middle path between lightweight IESG decisions and full process BCP revisions' and a 3933 experiment could have proved it right or wrong, useful or not. The community could not

Re: When is a 3933 experiment necessary? [Was: Last Call: draft-farrell-ft-03.txt (A Fast-Track way to RFC with Running Code) to Experimental RFC]

2013-01-30 Thread SM
Hi Adrian, At 01:15 30-01-2013, Adrian Farrel wrote: I do not take quite the same negative view as Stephen, but I do agree with Spencer that getting consensus for a process change always looks like a formidable task. Small changes never address enough of the problem or the right piece of the

Re: When is a 3933 experiment necessary? [Was: Last Call: draft-farrell-ft-03.txt (A Fast-Track way to RFC with Running Code) to Experimental RFC]

2013-01-30 Thread Dave Crocker
On 1/30/2013 1:15 AM, Adrian Farrel wrote: I do agree with Spencer that getting consensus for a process change always looks like a formidable task. Small changes never address enough of the problem or the right piece of the problem. Large changes are too much in one go. :-) So, it seems to

Re: Call for Comment: 'Privacy Considerations for Internet Protocols'

2013-01-30 Thread SM
At 14:30 16-01-2013, IAB Chair wrote: This is an announcement of an IETF-wide Call for Comment on 'Privacy Considerations for Internet Protocols'. The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here:

[ietf-privacy] Ongoing Call for Comments

2013-01-30 Thread Bernard Aboba
This is a note about two ongoing Call for Comments that may interest participants on this list. Comments on these documents can be sent to i...@iab.org or entered in TRAC. 1. Privacy Considerations for Internet Protocols. This Call for Comment ends on February 18, 2013. The document is

WG Action: Conclusion of IMAP MOVE extension (imapmove)

2013-01-30 Thread IESG Secretary
The IMAP MOVE extension (imapmove) working group in the Applications Area has concluded. The IESG contact persons are Barry Leiba and Pete Resnick. With the publication of RFC 6851 and the recording of implementation data on the working group wiki, the work of the imapmove working group is

Protocol Action: '464XLAT: Combination of Stateful and Stateless Translation' to Best Current Practice (draft-ietf-v6ops-464xlat-09.txt)

2013-01-30 Thread The IESG
The IESG has approved the following document: - '464XLAT: Combination of Stateful and Stateless Translation' (draft-ietf-v6ops-464xlat-09.txt) as Best Current Practice This document is the product of the IPv6 Operations Working Group. The IESG contact persons are Ronald Bonica and Benoit