Internet Message Access Protocol (IMAP) - URL Access Identifier Extension
RFC 5593

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

(Jari Arkko) Yes

Comment (2009-05-07)
No email
send info
The text "and should be taken as the master in the event of any differences or discrepancies" sounds a bit weird, we do not usually emphasize that for updates relationship, as its so clear. Or maybe I'm reacting to the word "master". I'd just delete the text.

Alexey Melnikov Yes

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Ralph Droms) No Objection

(Lisa Dusseault) No Objection

Comment (2009-05-05)
No email
send info
The URLAUTH RFC says:
  "The URLAUTH component overrides the second purpose of the enc-user in
   the IMAP URI and by default permits the URI to be resolved by any
   user permitted by the <access> identifier."

The 'stream' value doesn't seem to fit this definition, because 'stream' doesn't identify a user or a class of users.  Since this draft is updating RFC5092, it would be appropriate (though a little obsessive) to update the definition given above with a new one.  

Since this has been discussed in LEMONADE where URLAUTH mostly originated, I'm making this a COMMENT and don't object to the approach taken.

(Lars Eggert) No Objection

(Pasi Eronen) No Objection

(Adrian Farrel) No Objection

(Russ Housley) (was Discuss) No Objection

(Cullen Jennings) No Objection

(Tim Polk) (was No Record, Discuss) No Objection

(Dan Romascanu) No Objection

(Robert Sparks) No Objection

Magnus Westerlund No Objection