vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group
RFC 6715

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

(Pete Resnick) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Benoît Claise) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

(Stephen Farrell) No Objection

Comment (2012-06-18)
No email
send info
- 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

- 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:-).

(Brian Haberman) No Objection

(Russ Housley) No Objection

Comment (2012-06-18)
No email
send info
  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.

(Robert Sparks) No Objection

(Martin Stiemerling) No Objection

(Sean Turner) No Objection

Barry Leiba Recuse