Re: [Gen-art] Gen-art LC review of draft-cheshire-dnsext-nbp-09.txt

Stuart Cheshire <cheshire@apple.com> Wed, 15 December 2010 02:17 UTC

Return-Path: <cheshire@apple.com>
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3960D28C147 for <gen-art@core3.amsl.com>; Tue, 14 Dec 2010 18:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.932
X-Spam-Level:
X-Spam-Status: No, score=-106.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XhqzGqB+0mSi for <gen-art@core3.amsl.com>; Tue, 14 Dec 2010 18:17:56 -0800 (PST)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 50AF528C0F3 for <gen-art@ietf.org>; Tue, 14 Dec 2010 18:17:56 -0800 (PST)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 661F7BFA46A3 for <gen-art@ietf.org>; Tue, 14 Dec 2010 18:19:37 -0800 (PST)
X-AuditID: 11807137-b7bafae00000075a-b0-4d0825b97da4
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay16.apple.com (Apple SCV relay) with SMTP id A4.12.01882.9B5280D4; Tue, 14 Dec 2010 18:19:37 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Received: from [10.0.1.201] ([173.164.252.149]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LDG00JDB6GONW50@elliott.apple.com> for gen-art@ietf.org; Tue, 14 Dec 2010 18:19:37 -0800 (PST)
In-reply-to: <1290525315.4284.7622.camel@mightyatom.folly.org.uk>
References: <1290525315.4284.7622.camel@mightyatom.folly.org.uk>
Message-id: <E87C25DE-BFF5-44CE-B5F5-C44337DFD145@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Tue, 14 Dec 2010 18:19:44 -0800
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Reviwing Team <gen-art@ietf.org>, draft-cheshire-dnsext-nbp.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-cheshire-dnsext-nbp-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Dec 2010 02:17:57 -0000

On 23 Nov 2010, at 7:15 AM, Elwyn Davies wrote:

> Summary:
> This document has at least one open issue that I believe needs  
> fixing, either by altering the scope of the applicability of the  
> solution or fixing the requirements.  The requirements envisage a  
> protocol that could be used in an enterprise environment but it  
> does not address issues of visibility and accessibility.

The document describes AppleTalk NBP, and what would be required in  
an IP-based equivalent. It does not claim to document all possible  
requirements of all possible service discovery protocols.

> This issue is clearly related to the security requirements that  
> have been discussed elsewhere but differs from the authentication  
> and general authorization aspects that have been the focus there.   
> I believe that there needs to be discussion of how the service  
> discovery can be controlled so that individual users/machines are  
> only informed of services that they might be allowed to use.

The document describes AppleTalk NBP, and what would be required in  
an IP-based equivalent. AppleTalk NBP would find you (for example)  
all file servers on the network, not all file servers for which you  
know the password. We do not believe it is feasible in general to tie  
service discovery to access control. Nor is it useful: Discovering  
there's a printer for which you do know the password allows you to  
ask someone for the password. Discovering only resources to which you  
already have access (and therefore probably already know about) is  
significantly less useful.

> Nits:
> [refreshingly free of nits!]
> The only comment might be that a pointer to some publically  
> available definition or discussion of the existing Appletalk NBP  
> miight be helpful if such a thing exists.

There is not, which is why I wrote this document.

> Also idnits suggests that RFC 2462 should be replaced by RFC4862  
> which obsoleted it.

Fixed.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org