Re: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-01.txt
RJ Atkinson <rja.lists@gmail.com> Wed, 19 September 2012 12:43 UTC
Return-Path: <rja.lists@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2733521F8620 for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 05:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTQSq-qAwr3F for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 05:43:45 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 865F221F867C for <renum@ietf.org>; Wed, 19 Sep 2012 05:43:45 -0700 (PDT)
Received: by qcac10 with SMTP id c10so870632qca.31 for <renum@ietf.org>; Wed, 19 Sep 2012 05:43:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=fixprU0gXyBbScQ7waU0PH4Ms14CfB7Xb319Mbn7VoM=; b=iJVXbWuEMvQdxqigaXZeBN43sUsbHDfHIohUTWVzASGfj5Npar/ryNyvnvHwB/iXJP SyMw/AbIt4P1vX8+B5PoSeoc2+1Yp17cgh9+vC+aBVPCMAghCy/BSOTkXkh4e3CRoArv 8/EHF2em8jLRdkYnfLI12YBfroWdirdFKXJySVMoUgPnbclBkP4j3+6iiiGTmVf9IGqX wnanKVpURCHUNDH2SadMUQvf85CdrLcCMCJnQ8V12TnwLlvJLNk1j5tEOIemJQXFr/fO oFdqxvDNv7NrQyERh5GB9WHkbNfnIJQAxZaRZqHsf5cUPRESOIkg9NX3fATMyMLBQsWW xgPg==
Received: by 10.224.180.7 with SMTP id bs7mr6884969qab.37.1348058617325; Wed, 19 Sep 2012 05:43:37 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id y18sm3861646qaa.15.2012.09.19.05.43.35 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 05:43:36 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Wed, 19 Sep 2012 08:43:34 -0400
Message-Id: <D1800D0A-95CA-4EFE-8841-391156232607@gmail.com>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-01.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 12:43:46 -0000
Hi, While I am not a subscriber to this WG list, I have a few comments on draft-ietf-6renum-static-problem-01. I have tried to organise the comments by Section. Section 2.2, 1st Paragraph: For about a decade now, most network-capable printers have silently and automatically enabled SLP without requiring any user interaction. Such printers often use a factory-default algorithm to generate a printer name, unless a user has explicitly configured a printer name. Hosts that are SLP-aware, automatically discover such printers and can use them, without requiring the printer to have a preconfigured fixed IP address. Many deployed hosts have supported SLP for the past decade. So, the statement that "It is also unusual to enable the Service Location Protocol for the same purpose..." is not correct in the deployed world. It was correct in the 1990s. It has not been correct for about a decade, however. Section 2.2, Last Paragraph: The DNS Service Discovery (DNS-SD) technology described in draft-cheshire-dnsext-dns-sd-11.txt is directly relevant and should be both mentioned and referenced in this paragraph. mDNS is great, but for the problems of Section 2.2, mDNS really works much more effectively in combination with DNS-SD. The RFC Editor web site indicates that both DNS-SD and mDNS are IN-QUEUE for publication on the IETF standards track. Also, since around 2005/2006, many printers have shipped with mDNS/DNS-SD silently and automatically enabled (in addition to SLP). Further, many Windows PCs, all Apple Macs, and many UNIX systems have silently enabled mDNS/DNS-SD support for printing. (NOTE: I'm told that when one installs "iTunes" onto MS Windows, the installer silently installs mDNS/DNS-SD support also, since mDNS/DNS-SD is how iTunes finds "shared libraries" of digital content.) So the last paragraph also needs to be edited to clarify that the mDNS/DNS-SD combination is now widely supported and widely deployed for a range of services, including location of network printers. Otherwise the I-D seems fine to me. Yours, Ran
- [renum] Working Group Last Call: draft-ietf-6renu… Howard, Lee
- Re: [renum] Working Group Last Call: draft-ietf-6… George, Wes
- Re: [renum] Working Group Last Call: draft-ietf-6… Liubing (Leo)
- Re: [renum] Working Group Last Call: draft-ietf-6… Brian E Carpenter
- Re: [renum] Working Group Last Call: draft-ietf-6… RJ Atkinson
- Re: [renum] Working Group Last Call: draft-ietf-6… Brian E Carpenter
- Re: [renum] Working Group Last Call: draft-ietf-6… Fuyu (Eleven)