Shepherd writeup
draft-ietf-dnssd-push-16

draft-ietf-dnssd-push-shepherd.txt

(1) Document reviewed: h-shepherd
    This document is Standards Track.

(2)

Technical Summary

   The Domain Name System (DNS) was designed to return matching records
   efficiently for queries for data that is relatively static.  When
   those records change frequently, DNS is still efficient at returning
   the updated results when polled, as long as the polling rate is not
   too high.  But there exists no mechanism for a client to be
   asynchronously notified when these changes occur.  This document
   defines a mechanism for a client to be notified of such changes to
   DNS records, called DNS Push Notifications.


Working Group Summary

  The significant thing was the initial version of the draft had both protocols
  and process.  The decision was made after discussion with DNSOP, to split
  this work into a separate draft and the protocol work into
  draft-ietf-dnsop-session-signal, currently working its way through DNSOP.

Document Quality

  The documents is of good quality.  There currently is some non-published
  implementations.  The reviews on this document were vigorous and thorough.

Personnel:

  Document Shepherd is Tim Wicinski
  Area Director is Terry Manderson

(3) The Document Shepherd did a through review looking for editorial issues, as
well as technical issues.

(4) The Document Shepherd has no concerns about the depth or breath of reviews.

(5) This document was reviewed by DNSOP working group, as there is some overlap
in working group participants.  The major outcome was to split the document into
two drafts, this one and the ietf-dnsop-session-signaling draft which is working
its way through DNSOP.

 (6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

(7)  The Authors have confirmed that any and all IPR disclosures have
    been filed, which are currently none.

(8) There are No IPR disclosures on this document


(9) WG Consensus of this document is solid.

(10)  No Appeals have been filed and no extreme discontent has been registered.


(11) There are some outdated references to:

  == Outdated reference: A later version (-21) exists of
     draft-ietf-tls-tls13-20

     Currently in WGLC

  == Outdated reference: A later version (-03) exists of
     draft-ietf-dnsop-session-signal-02

     Currently in process

(12) No formal reviews needed

(13) All references have been identified as either normative or informative

(14) There are currently normative references to *two* unpublished drafts:

  - draft-ietf-tls-tls13  : moving along

  - draft-ietf-dnsop-session-signal  : Currently STALLED in DNSOP around dissent
  between the authos.

(15) There are downward normative references in this document. Currently
this document references two drafts which are still in process and have not
completed:

  draft-ietf-tls-tls13
  draft-ietf-dnsop-session-signal


  -- Possible downref: Non-RFC (?) normative reference: ref. 'SN'

    "Service Name and Transport Protocol Port Number
              Registry", <http://www.iana.org/assignments/
              service-names-port-numbers/>.


(16) Publication of this document will not change the status of any RFCs.


(17) The IANA section references creating DNS Session Signaling TLV types,
however, these are defined in draft-ietf-dnsop-session-signal and the authors
have not made a final decision at this time.

(18) No new IANA registries.

(19) No Automated checks other than NITs
Back