Re: [dnssd] Second WGLC for draft-ietf-dnssd-srp

Qiaoyu Deng <deng.qiaoyu@gmail.com> Mon, 22 August 2022 23:43 UTC

Return-Path: <deng.qiaoyu@gmail.com>
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 A0A98C14CF1D for <dnssd@ietfa.amsl.com>; Mon, 22 Aug 2022 16:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.11
X-Spam-Level:
X-Spam-Status: No, score=-0.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HK_RANDOM_ENVFROM=0.998, HK_RANDOM_FROM=0.998, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbex_oR4KBd4 for <dnssd@ietfa.amsl.com>; Mon, 22 Aug 2022 16:43:36 -0700 (PDT)
Received: from mail-yw1-x112a.google.com (mail-yw1-x112a.google.com [IPv6:2607:f8b0:4864:20::112a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40D5DC14F727 for <dnssd@ietf.org>; Mon, 22 Aug 2022 16:43:36 -0700 (PDT)
Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-333b049f231so337618727b3.1 for <dnssd@ietf.org>; Mon, 22 Aug 2022 16:43:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc; bh=Y0Ri+S0Y3bLa1UaXa4nKnPp/XzUa4uXpIPkxkL2xLF0=; b=FcchlHYSQ4xxEmgd/ukynQwW7jkIMNL4jLuozUqJ8jvLQF4zsgXd3DfyQre53aH7mt qYF5U8qOFu6BzpLmT579nqw2n4OxeWg8g2Lz5dKysrLBwBA4IAJWNOXTV3gEE0EVazxu 4QOGdOU6KTGCe2LF0iWlz2ttX4aYYO6LVAzOSYtJM1kHRHdpcGXKK3MF3p7/4TNijn8l X+khkps758mrHIBjQHNPplM1g2zONZs9RxB89kHydiP5JboOVtpxU4wsAQjxd32alukV AfgMe7WHJFXNucUDWtfGjhxkahHYrzEUaX/D7DAMlt/5P8JR09XxzW9rSbRqSW35yL2n bWOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc; bh=Y0Ri+S0Y3bLa1UaXa4nKnPp/XzUa4uXpIPkxkL2xLF0=; b=q1Tq0XNoRY79qs+KReEpMY2LZDXh7mt6kKg06yzeyjsCc/Ay8W2jya6jvCer9F9+uM hfj0KripmIzve/DsFe8vpHUIhP2f94qq7wXFO/wp4aSYXPQwJYnwgpulUZRpXX/pVVUN x2KvuxPLhiNjTEALhxk0jDR5dTsWJ0bBLuQVuRYWeTKbPPKoCtb+XS9oU1Gv2TbfTtpZ vBunIBJrlEHwkPjYfYgiBrW3gB8pbvQszCoME/Ia0Gma9RfLDRLfDuc2bGqCKSBD45hS n6FClw77EPJ/vrCfcS3kHhrDRXG1yyK5Aq3cZZdK/ax6Gc8dU4J4W1JYh7BAwr4kMjf8 kGGg==
X-Gm-Message-State: ACgBeo2ZbkdM/ex/2DKTtkR4ajl/CyYh+loGMQH0FUA0uZ1eM+3Oj7w/ q9ClexkxoXlHfjT2fZ6L2kKWVkQPRPn8VyTk1ZOT1EQ7+JbpNQ==
X-Google-Smtp-Source: AA6agR4jnqAo/9p85U6eUrRts4tuwmIeFlQHhIBAzd1uvM3YGKNIQl+GuggUfjekXEAe9kFnTVnrMRQkzDy7S5qCTug=
X-Received: by 2002:a25:5051:0:b0:68f:f31f:b590 with SMTP id e78-20020a255051000000b0068ff31fb590mr19689033ybb.569.1661211815203; Mon, 22 Aug 2022 16:43:35 -0700 (PDT)
MIME-Version: 1.0
From: Qiaoyu Deng <deng.qiaoyu@gmail.com>
Date: Mon, 22 Aug 2022 16:42:59 -0700
Message-ID: <CANsbLvxUBxDR68dden1q4k=Taj0CuYzmHY-1QM+vKK485QDoiA@mail.gmail.com>
To: DNSSD <dnssd@ietf.org>, David Schinazi <dschinazi.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000002458ea05e6dd04af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/rBowKoidApFw0_E6-xGEpxEXn7Y>
Subject: Re: [dnssd] Second WGLC for draft-ietf-dnssd-srp
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 22 Aug 2022 23:43:36 -0000

Hi,

I have read the draft-ietf-dnssd-srp document and think it is ready for the
next step.

I do have one suggestion about the wording though:

2.2.1. What to publish
> We refer to the DNS Update message sent by *servers* using SRP as an SRP
> Update. Three types of updates appear in an SRP update: Service Discovery
> records, Service Description records, and Host Description records.


Here the "servers" actually means the device (the requestor) that provides
the service and wants to register a service with SRP. My first impression
is that the "servers" here means the registrar. From the context, it
actually means the requestor (the client side in the SRP).

Therefore, I want to suggest that we change the text to the following:
We refer to the DNS Update message sent *on behalf of a service by an SRP
requestor* as an SRP update.

Thanks to Ted and Stuart for all the work they have done for this document.

---
Qiaoyu (Joey) Deng