IETF Logo Mail Archive

Re: [dnssd] SRP: name conflict while not knowing which name conflicts

Ted Lemon <mellon@fugue.com> Mon, 26 September 2022 16:30 UTC

Return-Path: <mellon@fugue.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 41963C14F728 for <dnssd@ietfa.amsl.com>; Mon, 26 Sep 2022 09:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20210112.gappssmtp.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 Lky1bBjtp1Hk for <dnssd@ietfa.amsl.com>; Mon, 26 Sep 2022 09:30:26 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 11CE8C14F725 for <dnssd@ietf.org>; Mon, 26 Sep 2022 09:30:25 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id h28so4475403qka.0 for <dnssd@ietf.org>; Mon, 26 Sep 2022 09:30:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date; bh=/IMY7/FHvj5a2btA6wS/PpeJH9IHJZUOrwAdwA0hr4o=; b=CDGT1kKEjdMWcefobIemiYcfkeXIkffZBrK2ArWV/z94yRp3QDDghDBhAT23ziBzMI s+R7M45q/E3dKGveSLY/hNXg4qitZaw5PYr68CQTtdm3ZLZTHZFLDBOZ7CtMCZt93FZ8 GM9ESc6GSK2gv8TWSAv6y0IKnvCQ9v9dGTsmquadkD2c2sN7u41eRQS1gzsaJQCXrhSS FHPW1clUWGSHNKg3VYSCk4aA49MoRc5tv8dveSy6itsfVnSZXj7L1a9LOrLfBSGgxRs7 mEFvslQd4SuNcL9Qf4t88r3I4H99tQiZ2fhZxdG2+HS3YLL4MGMTpswtxR7sJjZ234cM jQMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date; bh=/IMY7/FHvj5a2btA6wS/PpeJH9IHJZUOrwAdwA0hr4o=; b=J1kwBNMOkk5gCpTbLHk5VHUiIogm6oS12UfAreHi+pxQKw5VK54xMXBx+YbaFI4tuf zsyB+WIpAcBF4kKY2nnIwktA7nt6xTQcqyOs9WD9yRUxdIkrWribyDmM9LGugw9WVqfQ CAuC/WfKNwzJIUqvbh2MhwmXnMVxUOPWTmuAHJHUpNwGGgeMUXKpgY1E7kdcFaPKqj+8 tUVDtriNXk8ZLrNQEBnF5OAIhFUVTonWje7GQ5jLoHcneTvZwIWg66xDSHzrrwt6QbbL cgeQtilMP7h6zhTwdkIJKvG+xVaznfNEeGeMKW8uSciLSzAboUzQCzyLD2LOFPJesaUB 0YGQ==
X-Gm-Message-State: ACrzQf0FAyXqeSH8x129m+zQqyDdD+k/uQWC+er2zBBZ6KshD7+Jfkfj tKa/4YBvP3ehbkJov+EITKH0bYDBL1GfnA==
X-Google-Smtp-Source: AMsMyM41ydwl7l9ZsPa7uQDq7BWvvBEAV+F8w4B6mm8xsDi81qvAkmeAC4YWc3H3U+xdFFvuudC5ow==
X-Received: by 2002:a05:620a:1318:b0:6ce:e16d:a88 with SMTP id o24-20020a05620a131800b006cee16d0a88mr14619417qkj.161.1664209824300; Mon, 26 Sep 2022 09:30:24 -0700 (PDT)
Received: from smtpclient.apple (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id u14-20020a05620a0c4e00b006cf9381aefesm3378154qki.11.2022.09.26.09.30.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 26 Sep 2022 09:30:23 -0700 (PDT)
Content-Type: multipart/mixed; boundary="Apple-Mail-3826F17D-BA5B-4135-B3C6-53A5A9CE37B3"
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 26 Sep 2022 12:30:22 -0400
Message-Id: <3FACE3ED-F0F0-44E8-8CAB-FAFDFEF63CE2@fugue.com>
References: <131234.1664209767@dooku>
Cc: Esko Dijk <esko.dijk@iotconsultancy.nl>, dnssd@ietf.org
In-Reply-To: <131234.1664209767@dooku>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: iPad Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/jrSHsoSSdLnnNzlHI9kQvpABe8E>
Subject: Re: [dnssd] SRP: name conflict while not knowing which name conflicts
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, 26 Sep 2022 16:30:28 -0000

Well, for some value of “we” I think this is definitely a good thing to do, but the IETF wouldn’t be the “we”, hence the emoticon.

Sent from my iPad

> On Sep 26, 2022, at 12:29 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Ted Lemon <mellon@fugue.com> wrote:
>> Maybe we should write some conformance tests that send unknown
>> options. :)
> 
> I would seriously suggest this, without the :)
> 
> 
> -- 
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
>

v2.23.0 | Report a Bug | By Email