IANA Registration for vCard Enumservice
RFC 4969

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

(Ted Hardie) Discuss

Discuss (2007-03-06 for -)
I agree with Cullen's discuss, and I'll point to this text within the note:

"This document is a NOTE made available by the W3C for discussion only. Publication of this Note by W3C indicates no endorsement by W3C or the W3C Team, or any W3C Members. W3C has had no editorial control over the preparation of this Note. This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time."

I believe that this makes the normative reference a downref, even if it is the consensus of the community that this should be published.

I also note that some discussion of DNSSEC's interaction with this mechanism may be in order.
One of the motivated reasons for the creation of NSEC3 was to limit zone walking.  Given that this enumservice contains pointers to personally identifiable information, the policy limitations
on making this available may require considering NSEC3 if the zone will use DNSSEC.
Comment (2007-03-06 for -)
No email
send info
I agree with Sam that the use of HTTP authentication to limit access to this data or
to manage the identities for the purposes of synthesis seems unlikley to scale for
public deployment.  In deployments where it might work, other forms of discovery
seem more likely.

(Jon Peterson) Yes

(Jari Arkko) No Objection

(Ross Callon) No Objection

(Brian Carpenter) No Objection

(Lars Eggert) No Objection

(Bill Fenner) No Objection

(Sam Hartman) No Objection

Comment (2007-03-06 for -)
No email
send info
This is not a blocking discuss.  However I wonder how useful the http
authentication is going to be.  How likely is it that the person
retrieving an enum vcard is going to have a close enough relationship
with the person publishing the vcard that they share an authentication
infrastructure?  If so, is enum really a best fit for distributing the

(Russ Housley) No Objection

(Cullen Jennings) (was Discuss) No Objection

(David Kessens) No Objection

(Chris Newman) No Objection

Comment (2007-04-13)
No email
send info
Looks like -06 removed the problematic downref.  The description of the authentication mechanisms is fairly weak and could be made more useful, but it should be adequate for common use cases.

(Dan Romascanu) No Objection

(Mark Townsley) No Objection

Magnus Westerlund No Objection