IETF Logo Mail Archive

Re: [homenet] Introduction to draft-ietf-homenet-simple-naming

Ted Lemon <mellon@fugue.com> Wed, 30 May 2018 20:38 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFC0129BBF for <homenet@ietfa.amsl.com>; Wed, 30 May 2018 13:38:39 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.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 SAURkVnSk2jf for <homenet@ietfa.amsl.com>; Wed, 30 May 2018 13:38:37 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 911AE1200E5 for <homenet@ietf.org>; Wed, 30 May 2018 13:38:37 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id c10-v6so9586946pfi.12 for <homenet@ietf.org>; Wed, 30 May 2018 13:38:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=SSDfzWPBUKt2epJmND8sN8Hxq+rUxHEx3vMCLDVswzQ=; b=fjpFxxugO4uwGGoZQ5aYd5B0zkBcGDQFd+IdvgPmQQlE2TyTxZaK8gS1prsA8eE0pr caNP22wIOJUQtNdDqW17xl9O0IAEyQBF/Wnp6hcN+T6OhvLPDfOdH9s8oJ4phgMfCNol H6KukZ0iXUN9QvokMEyac7o7hlUJb2VqYZJ3xV2db4FfdDvMfNSwMR0uFb0Mrsfa0JHD Fdm6I3FpTpHcLkBninRJWa8B4S8N/kM/Qvp0qZLhegho6DsLpzJwV14wO/ldESMgg5Ou BFkUzmJW8FE6xRNetPgaf0q2QvG0hZ+uVw9c2raIkAROIR0uoZC2YXuzq1E3YVI8SEL7 QTow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=SSDfzWPBUKt2epJmND8sN8Hxq+rUxHEx3vMCLDVswzQ=; b=sZ44kHWbK1cuZVgFNrsgcfGzQkwCB4pHNxh4WvVsDMbCe+G97di+k7ZUl+0eGwZOUB 9Xuq8nb7UvAV7GmyuKW6j3XlcJ2Pxuaz+EA65+hd01wUlSNG1kswkAZ8CVk8IOZ2GA5P xkYz1bM2+/p5A54HtAmfnbEsR+mkIK4i+181OoU+RDZsjI9pqNRveonECKu0cjCfGejK BCdZGrKLY18PYYfQQL3Cv39IcnPr6IUqpxhSsGu0PjqL70ZhTL3n+fYDntL9A9G8gTU5 mmttp3Onuh5OGY9w+db6fODHMXkMDqawgJWCAUSbQUS6SBxPnwi/h9nVkRvbsngQs8I5 /lgw==
X-Gm-Message-State: ALKqPwf0ZFyvQfEOrIglpdHh73BbuxSRVzbNkyYe6DT99z81e2QKhFzl eTWkhbWgaUoOE7K0sH6OK6BTvu0ktjM=
X-Google-Smtp-Source: ADUXVKLPl3DdNotSxcX1naeB2DlkEVtDwWz5Uv3XYQGwJ3Ti4xiAAg6U2r/kDkFkNLwQM9Uso0OnZg==
X-Received: by 2002:a65:5686:: with SMTP id v6-v6mr3367193pgs.141.1527712717110; Wed, 30 May 2018 13:38:37 -0700 (PDT)
Received: from cavall.scim-upper-hall-ap ([65.153.119.10]) by smtp.gmail.com with ESMTPSA id b29-v6sm65163879pfh.155.2018.05.30.13.38.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 May 2018 13:38:36 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <37902D77-2528-4D9E-815A-DFF83905EB83@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C5CAB4B6-C6B4-4EB9-80C0-C656EF0320AF"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Wed, 30 May 2018 13:38:31 -0700
In-Reply-To: <29be80e3-bd65-bcd3-5db2-c2ef0a084f12@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet@ietf.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <CAPt1N1kcuDBxK1=RN=_Q4YM7L_-YDNaEt4WS-sh2YDeJgvMgRw@mail.gmail.com> <20180528180538.GF12038@mx4.yitter.info> <CADZyTkmAc+CUdFxaur=qfFagtrUx64vv7QGFocgdHM1rXqJB7Q@mail.gmail.com> <762d4d6d-38d3-05ac-7cd6-fc87b2f1b042@gmail.com> <10568.1527686230@localhost> <29be80e3-bd65-bcd3-5db2-c2ef0a084f12@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Flowj6_qFzcldELfuoJTx5u5a5M>
Subject: Re: [homenet] Introduction to draft-ietf-homenet-simple-naming
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2018 20:38:40 -0000

On May 30, 2018, at 1:32 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> Well, let me invent something. I throw together my network and it names
> the printers as printer1 and printer2. Being a stickler, I decide to
> rename them as Printer 1 and Printer 2. I mess around and find a config file
> somewhere and manually edit it. My printers no longer work.

It would be good if you could come up with a real example.   This isn't going to happen in practice, because in practice there is no file to edit—printers are discovered using DNSSD.   If we have a successful DNSSD implementation, then printers will work, and nobody will ever even go looking for that nonexistent config file.   If we don't have a successful DNSSD implementation, we have failed.

Does the working group need a walk-through of how this works?   It Can Be Done!   :)

v2.23.0 | Report a Bug | By Email