Re: [dnssd] SRP: Name Conflicts Handling

Kangping Dong <wgtdkp@google.com> Mon, 18 January 2021 03:46 UTC

Return-Path: <wgtdkp@google.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 146823A0CCD for <dnssd@ietfa.amsl.com>; Sun, 17 Jan 2021 19:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.972
X-Spam-Level:
X-Spam-Status: No, score=-16.972 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.998, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 QkXKpyfLF-By for <dnssd@ietfa.amsl.com>; Sun, 17 Jan 2021 19:46:09 -0800 (PST)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 A91433A0CCC for <dnssd@ietf.org>; Sun, 17 Jan 2021 19:46:09 -0800 (PST)
Received: by mail-yb1-xb34.google.com with SMTP id x78so6944322ybe.11 for <dnssd@ietf.org>; Sun, 17 Jan 2021 19:46:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qv8FM04rIen8XFTSpAU9DArzPvzI1baM1LrKMmqqKh4=; b=c4vvK9zT7dMx403Py8C5hQoVRafdLKSpmZcyZv8gAi+gFhV+wcdW1BcWb7NS5xoj+I +x5TeVP05CLYXmWG/W1cWl3sT8EvQmIpdr6JcJqzlBUZcTsxauzni2+FrqvtX7iw9KL9 SmzbgTdEw/IhElquPTRZOd35Ej76q7mtB3EQIUmV9UVHp6uhZ1298+XAIXQMswBmaLyw Fx1YKA2owKfM+z04gNLg9nwgMwLc5UoKVmzsdSZfmyNpPC1LcEAyS6zDQZ+3/5qLVDEp q5oQ1qjsi2qxf3JfS01xBOIbdqssO1Lj99/ejMVzgm3N4hURX/2dGxwdAo6HefOtVaEq rKMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Qv8FM04rIen8XFTSpAU9DArzPvzI1baM1LrKMmqqKh4=; b=oiK45N5Csz8GJYg6qiP1M6e9hFL8KHSfDIVEcTQ2N4yBrLsvww6LX+Dzen6GpxQd5g l3dmWCMA5r4dF81o7JYRejOfVy7/EmeNyulpEkxojIZ2CWqXWpHkHQtkUiwEVPA7kMFV OjIHhKDgFjGx+h2rt8e0Eu+QMEtiP4m4LJ6ZZPjO0DhwUNwnyX08v/yUiUhnRqrAvH5v kzfFNW1hrW3yaFeRt9JtHhaSmoZGVC2W56Z/78vrnTTY8VWIOq5Di6rfCs8o9nGde1w2 RDDt92Fpnzkshs15zELfft3Y9r2fTN1Y+O8XzlfnplzYLo3HhBqAbQJD9ciLPuPsQ2be frfw==
X-Gm-Message-State: AOAM531hc09jk3SKGsiu3CEKpMKNgRG/uH1MULHELMUF2KxFgTGcnMnX oTayJwb/p4cKIQFB21xV+FhHBnwvA7UTF1W+clik3g==
X-Google-Smtp-Source: ABdhPJzh7ObZFFdKHZS7aaJvtS90MA+Jk6EKP88PsqR+LVe+L6mjEh/KZFFfN6N+e2OlLWRpv+szVYfeJg/7JXrxyUI=
X-Received: by 2002:a25:2fd7:: with SMTP id v206mr34262183ybv.420.1610941568519; Sun, 17 Jan 2021 19:46:08 -0800 (PST)
MIME-Version: 1.0
References: <CAJ5Rr7bH1k3mymO=a=YvsoEtXijJKN96k-78J9wGr_sfvbmmfw@mail.gmail.com> <30F1E517-3A0E-4BCF-B2F9-DE3346570B9B@fugue.com>
In-Reply-To: <30F1E517-3A0E-4BCF-B2F9-DE3346570B9B@fugue.com>
From: Kangping Dong <wgtdkp@google.com>
Date: Mon, 18 Jan 2021 11:45:32 +0800
Message-ID: <CAJ5Rr7Zc-Yma9EVXw1OeEKP+H1ZkPxB48Q5U45zoERX7=gNLJA@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: DNSSD <dnssd@ietf.org>, Jonathan Hui <jonhui@google.com>, Abtin Keshavarzian <abtink@google.com>, ronglisun-team@google.com, Yakun Xu <xyk@google.com>
Content-Type: multipart/alternative; boundary="000000000000f2966805b9248ff5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/labOEdLQUHmPONZzcrCIqBN7F6U>
Subject: Re: [dnssd] SRP: Name Conflicts Handling
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Jan 2021 03:46:11 -0000

Should we use one RR with ANY type (and zero rdata) for one conflicted
name? Because the conflict applies to all RRs of this name.

Or just pointing to the root?
>
Sorry, I am not following. Do you mean including exactly the original RR
that has name conflict?


BRs,
Kangping

On Fri, Jan 15, 2021 at 10:30 PM Ted Lemon <mellon@fugue.com> wrote:

> How about including an additional section on the response that includes
> the conflicted names and rrtypes with zero length data? Or just pointing to
> the root?
>
> On Jan 15, 2021, at 01:03, Kangping Dong <wgtdkp@google.com> wrote:
>
> 
> Hi DNSSD enthusiasts,
>
> For Service Registration Protocol (SRP), when a SRP server receives a
> registration with names
> that have already been taken by another client, it responds with a
> YXDOMAIN error code to indicate
> name conflicts. When the client receives such a response, it typically
> will re-generate a new host or
> service instance name and re-register with the new name.
>
> The problem is that a typical SRP update will include one Host Description
> Instruction and one (or more)
> Service Description Instructions (zero Service Description Instruction is
> allowed but it is more common
> that the client registers the host with some service instances). Name
> conflicts can happen on both Host
> Description instruction and Service Description Instruction, but there is
> no description of how to tell the
> client which instruction includes the conflict (or both include
> conflicts). Currently, the client needs to re-new
> both host name and service instance name or re-new a single name and
> starts a trial-and-error process
> until it finally succeeds.
>
> One solution is, the server/registry responds with the *Instruction(s)* which
> has name conflicts. For the
> client, it should check the RRs in the response to get the conflicting
> name if a YXDOMAIN response
> code is received. To Reduce data transported between the server & client,
> the server may just include
> one RR, but not the entire *Instruction*, that contains the conflicting
> name.
>
> Thoughts?
>
>
> BRs,
> Kangping
>
>