Skip to main content

Telephone Number Mapping (ENUM) Service Registration for Presence Services
draft-ietf-enum-pres-01

Yes

(Allison Mankin)

No Objection

(Alex Zinin)
(Bill Fenner)
(David Kessens)
(Margaret Cullen)
(Steven Bellovin)
(Ted Hardie)
(Thomas Narten)

Recuse

(Jon Peterson)

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

Allison Mankin Former IESG member
Yes
Yes () Unknown

                            
Alex Zinin Former IESG member
No Objection
No Objection () Unknown

                            
Bert Wijnen Former IESG member
No Objection
No Objection (2004-05-26) Unknown
Abstract needs to expand the acronyms

On page 3 sect 1 need to use proper example fqdn:
OLD:
  like 'pres:user@host.com'.
NEW:
  like 'pres:user@example.com'.

There are several other places where an Acronym is used without
being expanded with the first time use.

You may want to check for consistency. 
Sometimes I see: 'pres' URI
other times just: pres URI
Bill Fenner Former IESG member
No Objection
No Objection () Unknown

                            
David Kessens Former IESG member
No Objection
No Objection () Unknown

                            
Harald Alvestrand Former IESG member
No Objection
No Objection (2004-05-27) Unknown
Reviewed by Kent Crispin, Gen-ART
His review:

This draft is one of the many areas where I have little expertise. 
That said, in my non-expert opinion, it's on the right track, but it
needs more.  In particular, I would have found it quite helpful if the
example section was expanded, and some explanation thrown in.

References not split into normative/informative...
Margaret Cullen Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection (2004-05-26) Unknown
  In section 5: s/neustar.biz/example.com/

  I would prefer a stronger statement in Section 6, 2nd paragraph,
  last sentence.  How about:

    Any presence protocol that is used in conjunction with the
    'pres' URI scheme must meet the privacy requirements detailed
    in RFC2779.
Scott Hollenbeck Former IESG member
No Objection
No Objection (2004-05-24) Unknown
The example provided in section 5 uses domain "neustar.biz" instead of example.(com|net|org) or <something>.example as described in RFC 2606.  The example line is a little long, too, and will need to be wrapped to fit the page boundary.
Steven Bellovin Former IESG member
No Objection
No Objection () Unknown

                            
Ted Hardie Former IESG member
No Objection
No Objection () Unknown

                            
Thomas Narten Former IESG member
No Objection
No Objection () Unknown

                            
Jon Peterson Former IESG member
Recuse
Recuse () Unknown