[dnssd] Fwd: New Version Notification for draft-sctl-service-registration-02.txt

[Ted Lemon <[e-mail]>]

I just submitted an updated version of the service registration document.
 If you were planning to read this prior to the meeting and haven't read it
yet, you should definitely read the new version.   I think it's more
understandable than the old version, but more importantly, it's also more
correct.

This version contains significant updates from the version that Toke
reviewed last week.   Things move fast at the IETF...

---------- Forwarded message ----------
From: <[e-mail]>
Date: Sun, Jul 15, 2018 at 4:40 PM
Subject: New Version Notification for draft-sctl-service-registration-02.txt
To: Stuart Cheshire <[e-mail]>, Ted Lemon <[e-mail]>



A new version of I-D, draft-sctl-service-registration-02.txt
has been successfully submitted by Ted Lemon and posted to the
IETF repository.

Name:           draft-sctl-service-registration
Revision:       02
Title:          Service Registration Protocol for DNS-Based Service
Discovery
Document date:  2018-07-14
Group:          dnssd
Pages:          16
URL:            https://www.ietf.org/internet-drafts/draft-sctl-service-
registration-02.txt
Status:         https://datatracker.ietf.org/doc/draft-sctl-service-
registration/
Htmlized:       https://tools.ietf.org/html/draft-sctl-service-
registration-02
Htmlized:       https://datatracker.ietf.org/doc/html/draft-sctl-service-
registration
Diff:           https://www.ietf.org/rfcdiff?url2=draft-sctl-service-
registration-02

Abstract:
   The DNS-SD Service Registration Protocol uses the standard DNS Update
   mechanism to enable DNS-Based Service Discovery using only unicast
   packets.  This eliminates the dependency on Multicast DNS as the
   foundation layer, which greatly improves scalability and improves
   performance on networks where multicast service is not an optimal
   choice, particularly 802.11 (Wi-Fi) and 802.15.4 (IoT) networks.
   DNS-SD Service registration uses public keys and SIG(0) to allow
   services to defend their registrations against attack.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat