[dnssd] SRP: Name Conflicts Handling
Kangping Dong <wgtdkp@google.com> Fri, 15 January 2021 06:03 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 29BCB3A0CEE for <dnssd@ietfa.amsl.com>; Thu, 14 Jan 2021 22:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.973
X-Spam-Level:
X-Spam-Status: No, score=-16.973 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, 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 hiYVvFQa5rpW for <dnssd@ietfa.amsl.com>; Thu, 14 Jan 2021 22:03:51 -0800 (PST)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 C733F3A0CEB for <dnssd@ietf.org>; Thu, 14 Jan 2021 22:03:51 -0800 (PST)
Received: by mail-yb1-xb2b.google.com with SMTP id z1so4068254ybr.4 for <dnssd@ietf.org>; Thu, 14 Jan 2021 22:03:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=U89/QQObtVP5ae+AhjNp0LMgrdcgjC8dZnNjy5DMGhg=; b=NpNWU7LCbwrttqqwAp7sHCtZAnJhekfdz0UJCuiTCqgjS30fFRUqKRV9ZSBlyiZupM 2wBvWkpYcSKDf8Xvhkh2OJSmVd7aefOP0ey3hQ+DKgtqZNr4BoiR5oMuKrnHTRqfm8cF btSb4thxT6IzWDgbGM9E6gGM9Y+ny7H85gHqltGocMAGcXsklFSoEfVWOtuxK86YNwn0 iR+WNhiME5FJHfe08Klf9uCmAyJ0UIc/jL1Iv6e8nBjNZJgAsfGItBMw5yYiD1AgO8hi uO+RZCqY33RuQou+e5NQK1pmOQKRoJZMkfQoc7cRjwV5X80a54XUO6rGBtlqKMU7ZimF ji1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=U89/QQObtVP5ae+AhjNp0LMgrdcgjC8dZnNjy5DMGhg=; b=bYreK8VrD1/TRdk1s4Ovb5OK6hMM9k4jG+nMRVEspehuQleKag38EV7D625bSMNNt8 OTMh32H782mZ3fVjudUgLM9YiTP7BY1hiAywD67bSF92bmVGJl4xh4uUaViGPcnhrthd 0BthvGoTiwnHugOOK5fYFHqieasnJ7KRpUElL0srLBMvLIYFSBGUILuZ2VETswdprw9T cB90Irqb9QT7p88FCG4sOWl5m13et5xLSzs6dpzkiixZ38mYoag4CilTxxv485sXxws1 /4PCl+IIDLpeCnl6EEY2e2+fVTTiA2fWV3tHBy4VXoay75EK5dvQ5uMFv5ZAq+ZQiG4H snqQ==
X-Gm-Message-State: AOAM532fW2IjRQ1iCf4Dio5RqFoCXPrEFWWfwW0kEZhRiSRsevPeYeqL zOyiv/JeXLWQayQavGJlUrWd7qjfkFTohRakE+mmeOrUs5TRnaAM
X-Google-Smtp-Source: ABdhPJwZq7gWCXbehqYWKQBLWXSM+p0lijADlCCjpBvAmJgUzUWKUxhgiEs5SEYisgbGFHGb+Ekc3NxGRhd1BiUX4AM=
X-Received: by 2002:a25:e048:: with SMTP id x69mr16024558ybg.353.1610690630407; Thu, 14 Jan 2021 22:03:50 -0800 (PST)
MIME-Version: 1.0
From: Kangping Dong <wgtdkp@google.com>
Date: Fri, 15 Jan 2021 14:03:14 +0800
Message-ID: <CAJ5Rr7bH1k3mymO=a=YvsoEtXijJKN96k-78J9wGr_sfvbmmfw@mail.gmail.com>
To: DNSSD <dnssd@ietf.org>, Jonathan Hui <jonhui@google.com>, Abtin Keshavarzian <abtink@google.com>, ronglisun-team@google.com, Ted Lemon <mellon@fugue.com>, Yakun Xu <xyk@google.com>
Content-Type: multipart/alternative; boundary="000000000000deda6505b8ea22ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/BUxtJKeKjAKy_IdAyy9v9Y9TyBk>
Subject: [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: Fri, 15 Jan 2021 06:03:54 -0000
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
- [dnssd] SRP: Name Conflicts Handling Kangping Dong
- Re: [dnssd] SRP: Name Conflicts Handling Ted Lemon
- Re: [dnssd] SRP: Name Conflicts Handling Kangping Dong
- Re: [dnssd] SRP: Name Conflicts Handling Ted Lemon
- Re: [dnssd] SRP: Name Conflicts Handling Kangping Dong
- Re: [dnssd] SRP: Name Conflicts Handling Ted Lemon
- Re: [dnssd] SRP: Name Conflicts Handling Kangping Dong
- Re: [dnssd] SRP: Name Conflicts Handling Ted Lemon
- Re: [dnssd] SRP: Name Conflicts Handling Kangping Dong
- Re: [dnssd] SRP: Name Conflicts Handling Ted Lemon
- Re: [dnssd] SRP: Name Conflicts Handling Kangping Dong
- Re: [dnssd] SRP: Name Conflicts Handling Ted Lemon
- Re: [dnssd] SRP: Name Conflicts Handling Kangping Dong