Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)
draft-daigle-unaptr-02
Yes
(Ted Hardie)
No Objection
(Bill Fenner)
(Brian Carpenter)
(Cullen Jennings)
(Jari Arkko)
(Jon Peterson)
(Magnus Westerlund)
(Ross Callon)
(Russ Housley)
(Sam Hartman)
Note: This ballot was opened for revision 02 and is now closed.
Ted Hardie Former IESG member
Yes
Yes
()
Unknown
Bill Fenner Former IESG member
No Objection
No Objection
()
Unknown
Brian Carpenter Former IESG member
No Objection
No Objection
()
Unknown
Cullen Jennings Former IESG member
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
(2007-01-22)
Unknown
1. The text in the Introduction section seems to indicate that this document updates RFC 3858. If this is accurate, the header of the document should indicate 'Updates RFC 3858 (if approved) 2. I could not find in the docunent any use of capitalized keywords although the introduction mentions RFC 2119, and the Normative References section includes it
David Kessens Former IESG member
No Objection
No Objection
(2007-01-25)
Unknown
I wonder how many times you have to repeat that 'U-NAPTR is effectively an extension of S-NAPTR' before the reader gets it ;-): In 'Abstract': Although defined as a new DDDS application, dubbed U-NAPTR, this is effectively an extension of the Straightforward NAPTR (S-NAPTR) DDDS application. In 'Introduction': Although defined as a new DDDS application, dubbed U-NAPTR, this is effectively an extension of the Straightforward NAPTR (S-NAPTR) application, specified in [3]. ... This U-NAPTR is effectively a modest extension to S-NAPTR, to accommodate the use of URIs as targets, without allowing the full range of possible regular expressions in NAPTR records. And in section '2.2. Permitted Regular Expressions': With this limited form of regular expression, applications using U-NAPTR need not implement full regular expression parsers. I might would have nearly shipped my implentation with a complete regular expression library! I am glad the following text explains that a limited form of regular expressions means that I only have to implement a limited form of regular expressions ;-).
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
(was Discuss)
No Objection
No Objection
(2007-01-25)
Unknown
Section 1., paragraph 2: > Although defined as a new DDDS application, dubbed U-NAPTR, this is > effectively an extension of the Straightforward NAPTR (S-NAPTR) > application, specified in [3]. Does it update [3]? If so, add to the first page boilerplate.
Magnus Westerlund Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Sam Hartman Former IESG member
No Objection
No Objection
()
Unknown