vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group
RFC 6715
Yes
No Objection
Recuse
Note: This ballot was opened for revision 02 and is now closed.
(Pete Resnick; former steering group member) Yes
(Adrian Farrel; former steering group member) No Objection
(Benoît Claise; former steering group member) No Objection
(Brian Haberman; former steering group member) No Objection
(Gonzalo Camarillo; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
In the Gen-ART Review by Joel Halpern on 8-Jun-2012, it was pointed out that a reference two RFC 2119 is needed since there is one MUST.
(Sean Turner; former steering group member) No Objection
(Stephen Farrell; former steering group member) No Objection
- The INDEX parameter in 3.1 seems different from the others. I wondered if it really caused this to update 6530, since presumably it could make sense with any multi-valued thing? I assume the argument that it doesn't is that 6530 implementations will ignore it if they don't also support this spec, and I'm ok with that, but just wanted to check. - Is LEVEL (3.2) only supposed to be used with hobby, etc.? If so, then maybe you need some 2119 language for that? If not, then maybe say that. I could imagine LEVEL being used e.g. with ROLE or TITLE or maybe even SOUND (at a stretch:-).
(Stewart Bryant; former steering group member) No Objection
(Wesley Eddy; former steering group member) No Objection
(Barry Leiba; former steering group member) Recuse