Skip to main content

Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
RFC 6648

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 steering group member) Yes

Yes ()

                            

(Jari Arkko; former steering group member) Yes

Yes (for -04)

                            

(Pete Resnick; former steering group member) Yes

Yes (for -03)

                            

(Robert Sparks; former steering group member) (was Discuss) Yes

Yes ()

                            

(Adrian Farrel; former steering group member) No Objection

No Objection (for -04)

                            

(Benoît Claise; former steering group member) No Objection

No Objection ()

                            

(Brian Haberman; former steering group member) No Objection

No Objection ()

                            

(Dan Romascanu; former steering group member) No Objection

No Objection (2012-03-15 for -04)
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 steering group member) No Objection

No Objection (for -04)

                            

(Martin Stiemerling; former steering group member) No Objection

No Objection ()

                            

(Ralph Droms; former steering group member) No Objection

No Objection (2012-03-12 for -03)
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 steering group member) No Objection

No Objection (for -03)

                            

(Russ Housley; former steering group member) No Objection

No Objection (for -04)

                            

(Sean Turner; former steering group member) No Objection

No Objection (for -04)

                            

(Stephen Farrell; former steering group member) No Objection

No Objection (for -03)

                            

(Stewart Bryant; former steering group member) No Objection

No Objection (for -03)

                            

(Wesley Eddy; former steering group member) No Objection

No Objection (for -04)

                            

(Peter Saint-Andre; former steering group member) Recuse

Recuse (for -03)