Re: draft-ietf-dnsext-nsid issues to be reviewed
Rob Austein <sra@isc.org> Fri, 02 June 2006 04:55 UTC
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm1gk-0007vo-6W for dnsext-archive@lists.ietf.org; Fri, 02 Jun 2006 00:55:10 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fm1gi-00043b-TO for dnsext-archive@lists.ietf.org; Fri, 02 Jun 2006 00:55:10 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Fm1bn-000HRW-2J for namedroppers-data@psg.com; Fri, 02 Jun 2006 04:50:03 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level: *
X-Spam-Status: No, score=1.0 required=5.0 tests=BAYES_00,DATE_IN_PAST_03_06, FORGED_RCVD_HELO,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_SORBS_WEB autolearn=no version=3.1.1
Received: from [147.28.0.18] (helo=dragaera.hactrn.net) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from <sra@hactrn.net>) id 1Fm1bm-000HR4-5E for namedroppers@ops.ietf.org; Fri, 02 Jun 2006 04:50:02 +0000
Received: from thangorodrim.hactrn.net (m010f36d0.tmodns.net [208.54.15.1]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "thangorodrim.hactrn.net", Issuer "Grunchweather Associates" (verified OK)) by dragaera.hactrn.net (Postfix) with ESMTP id 724F114C46; Fri, 2 Jun 2006 04:50:00 +0000 (GMT)
Received: from thangorodrim.hactrn.net (localhost [IPv6:::1]) by thangorodrim.hactrn.net (Postfix) with ESMTP id 6CFDB116B7; Fri, 2 Jun 2006 00:14:27 +0000 (UTC)
Date: Thu, 01 Jun 2006 20:14:27 -0400
From: Rob Austein <sra@isc.org>
To: Namedroppers <namedroppers@ops.ietf.org>, Mark Townsley <townsley@cisco.com>
Subject: Re: draft-ietf-dnsext-nsid issues to be reviewed
In-Reply-To: <1A9A27DF-B365-4F02-80EE-D499DC3449AA@nlnetlabs.nl>
References: <1A9A27DF-B365-4F02-80EE-D499DC3449AA@nlnetlabs.nl>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20060602001427.6CFDB116B7@thangorodrim.hactrn.net>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
At Tue, 23 May 2006 10:50:48 +0200, Olaf M Kolkman wrote: > > NEW: > > 3.1. The NSID Payload > > The syntax and semantics of the content of the NSID option is > deliberately left outside the scope of this specification. It is > the prerogative of the server administrator to choose the NSID > content as long as the content is unique and the server administrator > is able to match the NSID to server instances. This > section describe some of the kinds of data that server administrators > might choose to provide as the content of the NSID option, and > explains the reasoning behind choosing a simple opaque byte string. I do not see the need for content to be unique. All that matters is that the name server which provides the NSID payload be able to understand it; the rest is nobody else's business. > Is there consensus to add such a "MUST implement a specific automated > method"? I do not see the need for a "MUST implement" method. -- to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/namedroppers/>
- Re: draft-ietf-dnsext-nsid issues to be reviewed Rob Austein
- Re: draft-ietf-dnsext-nsid issues to be reviewed Dean Anderson