Skip to main content

Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
draft-ietf-appsawg-xdash-05

Yes

(Barry Leiba)
(Jari Arkko)
(Pete Resnick)
(Robert Sparks)

No Objection

(Adrian Farrel)
(Benoît Claise)
(Brian Haberman)
(Gonzalo Camarillo)
(Martin Stiemerling)
(Ron Bonica)
(Russ Housley)
(Sean Turner)
(Stephen Farrell)
(Stewart Bryant)
(Wesley Eddy)

Recuse

(Peter Saint-Andre)

Note: This ballot was opened for revision 03 and is now closed.

Barry Leiba Former IESG member
Yes
Yes () Unknown

                            
Jari Arkko Former IESG member
Yes
Yes (for -04) Unknown

                            
Pete Resnick Former IESG member
Yes
Yes (for -03) Unknown

                            
Robert Sparks Former IESG member
(was Discuss) Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
No Objection
No Objection (for -04) Unknown

                            
Benoît Claise Former IESG member
No Objection
No Objection () Unknown

                            
Brian Haberman Former IESG member
No Objection
No Objection () Unknown

                            
Dan Romascanu Former IESG member
No Objection
No Objection (2012-03-15 for -04) Unknown
I agree with Ralph terminology comment. I also find confusing the repeated usage of the phrase 'deprecating a convention (or construct)' where in fact there is no specific place in standard-track or BCP RFCs where such a convention or construct was clearly articulated. I would have found more clear if instead of this the document would have pointed to an explicit list of conventions or constructs that are NOT RECOMMENDED.
Gonzalo Camarillo Former IESG member
No Objection
No Objection (for -04) Unknown

                            
Martin Stiemerling Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
No Objection
No Objection (2012-03-12 for -03) Unknown
This text:

2.  Recommendations for Implementers of Application Protocols

   Implementers of application protocols MUST NOT treat the general
   categories of "standard" and "non-standard" parameters in
   programatically different ways within their applications.

while probably not harmful, is sufficiently vague and refers to
undefined terms in a way as to contribute, perhaps, more confusion
than value.
Ron Bonica Former IESG member
No Objection
No Objection (for -03) Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection (for -04) Unknown

                            
Sean Turner Former IESG member
No Objection
No Objection (for -04) Unknown

                            
Stephen Farrell Former IESG member
No Objection
No Objection (for -03) Unknown

                            
Stewart Bryant Former IESG member
No Objection
No Objection (for -03) Unknown

                            
Wesley Eddy Former IESG member
No Objection
No Objection (for -04) Unknown

                            
Peter Saint-Andre Former IESG member
Recuse
Recuse (for -03) Unknown