[dnsext] was Re: historical question re WKS

Edward Lewis <Ed.Lewis@neustar.biz> Wed, 07 March 2012 17:27 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1995F21E808A; Wed, 7 Mar 2012 09:27:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1331141266; bh=gAlTiqGP4QU5McjUkesG6L4X1M3PE5GXKtzAJR1SCno=; h=Mime-Version:Message-Id:In-Reply-To:References:Date:To:From:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Transfer-Encoding:Content-Type:Sender; b=UKmW9xedGhu6gKmOUavvNn5HzVdebRpqCAUGMG3r5s5env9fu7vttbzVEmmdFdGyX XM2jaW+YlBwSHO0iSygWnkFsiH2e2NHuHMxT9JPDv7TbqQ63+V2Wn05o6ry9DKAUm6 c/X5rVtVWNwwOzCH/rLDP7nGi2f6dUDk8vpsd42A=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 871D221E808A for <dnsext@ietfa.amsl.com>; Wed, 7 Mar 2012 09:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.324
X-Spam-Level:
X-Spam-Status: No, score=-106.324 tagged_above=-999 required=5 tests=[AWL=0.275, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3fkAhBpqR1Zj for <dnsext@ietfa.amsl.com>; Wed, 7 Mar 2012 09:27:44 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1BCE121E8035 for <dnsext@ietf.org>; Wed, 7 Mar 2012 09:27:43 -0800 (PST)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id q27HRdoY062391; Wed, 7 Mar 2012 12:27:40 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.178] by Work-Laptop-2.local (PGP Universal service); Wed, 07 Mar 2012 12:27:40 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Wed, 07 Mar 2012 12:27:40 -0500
Mime-Version: 1.0
Message-Id: <a06240800cb7d49c8d1c1@[10.31.204.178]>
In-Reply-To: <alpine.LSU.2.00.1203071432140.2756@hermes-2.csi.cam.ac.uk>
References: <alpine.LSU.2.00.1203071432140.2756@hermes-2.csi.cam.ac.uk>
Date: Wed, 07 Mar 2012 12:27:34 -0500
To: Tony Finch <dot@dotat.at>
From: Edward Lewis <Ed.Lewis@neustar.biz>
X-Scanned-By: MIMEDefang 2.72 on 10.20.30.4
Cc: dnsext@ietf.org
Subject: [dnsext] was Re: historical question re WKS
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

off-list...because it's not all that useful a reply

Generally I know DNS history, but for this I don't.  I'd say that 
1035 implies there should be only one per IP/protocol from this in 
3.4.2:

"The WKS record is used to describe the well known services supported by
a particular protocol on a particular internet address."

Admittedly, that isn't a smoking gun, but it does talk about 
"particular" protocol and address.  You've read the rest.  No other 
hint.  I'd chalk this up to the poor documentation native to RFCs.

I'd bug Vixie directly if you want to know.

At 14:39 +0000 3/7/12, Tony Finch wrote:
>RFC 2136 specifies some odd special case handling of WKS records, to
>prevent a name from having more than one WKS record for a given IP address
>and protocol pair. Where did this requirement come from? I can't find
>anything along those lines in RFC 1035.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis             
NeuStar                    You can leave a voice message at +1-571-434-5468

2012...time to reuse those 1984 calendars!
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext