MIKEY-IBAKE: Identity-Based Authenticated Key Exchange (IBAKE) Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)
RFC 6267

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

(Tim Polk) Yes

(Jari Arkko) (was Discuss) No Objection

Comment (2010-09-09)
No email
send info
The document needs to define and expand terms that it uses, for instance there are many IMS related terms that are used without introduction (IMS, CSCF).

> a huge burden 

I would just say "a burden", for better style in these types of documents

> Moreover, since the keys are created and
> distributed by the KMS, these servers are de-facto escrow points
> leading to increased vulnerability and operational discomfort on the
> part of end-users.

I am the last person on this planet to argue in favor of legal interception, but I did find it odd that the document talks about public voice communication systems such as IMS that have government requirements for legal interception. And at the same time argues that somehow the specified solution is less vulnerable to escrow/interception. Either the specified system is capable of such interception as well, or it isn't. If the authors want to make a claim that there is no way to provide legal interception in their system then the argument seems fair, otherwise... I would just delete it.

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Adrian Farrel) (was Discuss) No Objection

(Russ Housley) (was Discuss) No Objection

(Alexey Melnikov) (was Discuss) No Objection

(Dan Romascanu) No Objection

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

Comment (2010-09-23 for -)
No email
send info
Support Jari's discuss and Adrian's discuss on whether this should be an Informational document.

Should this (and its related documents) be going through a working group instead?

(Sean Turner) (was Discuss) No Objection

Comment (2010-09-08)
No email
send info
1) Sec 4.2.1.1: r/Otherwise, this payload SHALL not be used./Otherwise, this payload SHALL NOT be used.  ?

2) Sec 4.2.2.2: r/ If
   the received message is correctly parsed, the Responder shall use / If
   the received message is correctly parsed, the Responder SHALL use