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

Tim Wattenberg <mail@timwattenberg.de> Wed, 18 July 2018 16:14 UTC

Return-Path: <mail@timwattenberg.de>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A682F130F67 for <dnssd@ietfa.amsl.com>; Wed, 18 Jul 2018 09:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=timwattenberg-de.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sz5BwomOCkB2 for <dnssd@ietfa.amsl.com>; Wed, 18 Jul 2018 09:14:18 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C3F6130F17 for <dnssd@ietf.org>; Wed, 18 Jul 2018 09:14:17 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id s16-v6so4716647edq.12 for <dnssd@ietf.org>; Wed, 18 Jul 2018 09:14:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timwattenberg-de.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s4VJ/xWTAlnBiQZFmdXCLNHo52HE4TAvTuagBHVa2ws=; b=P5iUpGyH9Eq1T6GT0H94uoDO70Uohg0Ol0npgtbtrJLRDMvo4iYOlpYKKXGqOXJWeb GlQn3h7gq3nb4dqAWXrgyyVyy256bASZtJGRcMvCEBBDtfELrq/aKPxknEeoK3leZ2Bu ZF5BdIBUKgBpZHSnR/71NT5GH00XilDBEJEclWc651bC7AHoNvfavWB5y/6A5+NJixXO PHPyBT2QJbfN223szX010JvY+8VC1SCeSq8YzXBiS/wsrliHU+aqbm4hrwbwF2Y4cXy0 5bS3SW1VPJb0iSlQvLnweSi1fRdiTeE151JZ1+vOUw7iJqBwjcyKFriP0OT1k1o45YsS hTVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s4VJ/xWTAlnBiQZFmdXCLNHo52HE4TAvTuagBHVa2ws=; b=WH5EoHwayeYAVOsI+JnU8BiXJi2w+xN3yXPHkUyxPAKNEifQ9BNAOpYPAVikAnM7fs xN2VLxV48+Iq2NgwxRZxFQ39mXHAuQ0FbcGujtPQCpsKuW5iOjh3nnps8YMXRw7r0UWe J1x1Tts/weVj7QYFCMyqWWScZ0nnQktu+YOryUjmS5OoTBxYbOMnQdd2lspeKCwG9t0J EgmMTmqUCPdXIiOObyJY8/MN321kuvgaNA6GG3Z1nGYPlx4SDNT2lwsyQYSv85s6tAhp ZA/7E0BUEJhM/W5O5yj9xw1B4NVS4EdNnFZ0iLVOIElWPvqbwVGSkiLP6CpkyPMjMFRi zsrQ==
X-Gm-Message-State: AOUpUlGtetZK4w3HyoSm6ZbaZjwoRjc1yiexRn/mged8ukRtbPDCQDb6 XH/xWZkwWXD7K4BQA9YyTVw2q8MEDCJi1U+hbChugv6iL/U=
X-Google-Smtp-Source: AAOMgpfbUgL7+EhBH6he9wv9sb3KE5XMzdf1Ei4UIZW+VOw0PqOEVTh/R2mmfq/D9OSn9m09taVyO85wHmziFBg/0GE=
X-Received: by 2002:a50:a846:: with SMTP id j64-v6mr7748764edc.210.1531930456135; Wed, 18 Jul 2018 09:14:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a50:8266:0:0:0:0:0 with HTTP; Wed, 18 Jul 2018 09:14:15 -0700 (PDT)
X-Originating-IP: [2001:67c:370:128:e4f0:45b9:44f8:16a6]
In-Reply-To: <8BC77FD3-B2E6-4980-A315-7595D250C49E@bangj.com>
References: <153168722035.21892.2695151923270049902.idtracker@ietfa.amsl.com> <CAPt1N1mYtPRxP6F-JwKbWey3r_vSaNP5srbkf314gdjfdNe8mw@mail.gmail.com> <87d0vn7b5t.fsf@toke.dk> <CALX6+rAjz2FtsQkhNyp=xYjXovUJUMN5Bg5iRHSWzMTJaZtCjg@mail.gmail.com> <CAPt1N1kODz72aHwF0z-uhYo4tojwsLEQJwLyzP8zeUYXduFkyQ@mail.gmail.com> <87a7qq6fdk.fsf@toke.dk> <CAPt1N1k59CM8WG4HoqXkG-crUEJbk+KNppX_pgkVFdwbSxNDpw@mail.gmail.com> <CAPt1N1khnMaRE2oe5WEQmonB8AJcLeBm=OB=i1trbEuc=XiL5Q@mail.gmail.com> <B88554CD-2117-44CC-ACA0-F5ACB3F48F88@bangj.com> <CAPt1N1=42Wum5x0s4dJZUB1t2i7g-UUJwcmWKQV5HMM5mAYyQQ@mail.gmail.com> <0542F0E1-88BB-4EF5-9897-CB608E5792C9@bangj.com> <CAPt1N1mrr=od-HBEDoS+Bs7fHuHj1Kc0HU-+6+NvhCyWDywYLg@mail.gmail.com> <CAPt1N1nFj5DpkRepLQ=Jmk=Spx87tNcfUMGyJRuAT=26givYKw@mail.gmail.com> <8BC77FD3-B2E6-4980-A315-7595D250C49E@bangj.com>
From: Tim Wattenberg <mail@timwattenberg.de>
Date: Wed, 18 Jul 2018 18:14:15 +0200
Message-ID: <CALX6+rDhf778yBbbK=cNKDrdO1Svwm2qBZjVkDDHAdD=-nKysw@mail.gmail.com>
To: Tom Pusateri <pusateri@bangj.com>
Cc: Ted Lemon <mellon@fugue.com>, dnssd <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a8a82b0571485a68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/XJBW7DsMGc6F96Khp2kveWpca-0>
Subject: Re: [dnssd] New Version Notification for draft-sctl-service-registration-02.txt
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 16:14:22 -0000

Well, the draft references to use regular DNS update messages as of RFC
2136 -- sec. 2.1 says to use UDP if it fits and switch to TCP otherwise.
However I agree that the "search domain" (dr._dns-sd._udp and
_dns-update._udp) mentioning UDP might me confusing.

Tim

Tim Wattenberg
mail@timwattenberg.de
+49 1578 8248731

2018-07-18 18:05 GMT+02:00 Tom Pusateri <pusateri@bangj.com>om>:

> If you are adding more KEY records, you will certainly exceed the UDP
> update size of 512 bytes. The draft doesn’t mention transport but maybe
> this should be restricted to TCP.
> The draft does mention searching for the update server using
> _dns-update._udp.<domain>. But then it won’t be able to use UDP for
> updates.
>
> Thanks,
> Tom
>
> On Jul 17, 2018, at 4:12 PM, Ted Lemon <mellon@fugue.com> wrote:
>
> Tim pointed out that we need to protect the Service Instance Name as well
> as the Host Description with a KEY record, because FCFS naming has to
> protect both the service description and the host description.   Here are
> the changes:
>
> https://github.com/StuartCheshire/draft-sctl-service-registration/compare/
> ae53618d8231733701ccdda4d336692a529c9f6b...5c85181881b84ed1132d544e157df8
> da85874597
>
> On Mon, Jul 16, 2018 at 6:42 PM, Ted Lemon <mellon@fugue.com> wrote:
>
>> The question of whether we update RFC6763 is basically "is there text
>> that is in RFC6763 that is no longer correct because of this document."  I
>> think the answer is no.
>>
>> On Mon, Jul 16, 2018 at 6:41 PM, Tom Pusateri <pusateri@bangj.com> wrote:
>>
>>> Ok, just checking. So given that 6763 semi-defines service registration
>>> protocol as DNS Dynamic Update, should this document claim it updates 6763?
>>>
>>> Thanks,
>>> Tom
>>>
>>> On Jul 16, 2018, at 6:01 PM, Ted Lemon <mellon@fugue.com> wrote:
>>>
>>> The title of RFC 6763 is DNS-Based Service Discovery.   So I tried to
>>> harmonize the document toward that—did I miss something?
>>>
>>> On Mon, Jul 16, 2018 at 5:59 PM, Tom Pusateri <pusateri@bangj.com>
>>> wrote:
>>>
>>>> How is DNS-Based Service Discovery different from DNS Service
>>>> Discovery?
>>>>
>>>> Is this meant to distinguish from RFC 6763?
>>>>
>>>> Thanks,
>>>> Tom
>>>>
>>>> On Jul 16, 2018, at 5:46 PM, Ted Lemon <mellon@fugue.com> wrote:
>>>>
>>>> BTW, the current version of the document on github now includes fixes
>>>> for all the points that have been raised other than the ones I said I
>>>> wasn't going to fix: https://github.com/Stuart
>>>> Cheshire/draft-sctl-service-registration
>>>>
>>>> On Mon, Jul 16, 2018 at 5:29 PM, Ted Lemon <mellon@fugue.com> wrote:
>>>>
>>>>> On Mon, Jul 16, 2018 at 5:27 PM, Toke Høiland-Jørgensen <toke@toke.dk>
>>>>> wrote:
>>>>>
>>>>>> Ted Lemon <mellon@fugue.com> writes:
>>>>>>
>>>>>> Why can't it be just a Host Description? Might be useful for a device
>>>>>> that just wants to register its name but doesn't (currently, or ever)
>>>>>> advertise any services...
>>>>>>
>>>>>> Good question.   What does the working group think?   :)
>>>>>
>>>>>
>>>> _______________________________________________
>>>> dnssd mailing list
>>>> dnssd@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dnssd
>>>>
>>>>
>>> _______________________________________________
>>> dnssd mailing list
>>> dnssd@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dnssd
>>>
>>>
>>>
>>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>
>
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>
>