Re: [dhcwg] RFC2131 - option multiple times - which ones ?

Ted Lemon <mellon@fugue.com> Fri, 11 March 2005 22:56 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15489 for <dhcwg-web-archive@ietf.org>; Fri, 11 Mar 2005 17:56:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9t6n-0007Cq-S9 for dhcwg-web-archive@ietf.org; Fri, 11 Mar 2005 17:59:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9t3K-0001JO-Re; Fri, 11 Mar 2005 17:56:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9t3I-0001JB-MD for dhcwg@megatron.ietf.org; Fri, 11 Mar 2005 17:56:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15452 for <dhcwg@ietf.org>; Fri, 11 Mar 2005 17:56:14 -0500 (EST)
Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9t6N-0007CU-CW for dhcwg@ietf.org; Fri, 11 Mar 2005 17:59:28 -0500
Received: from [127.0.0.1] (shell-ng.nominum.com [81.200.64.181]) by shell-ng.nominum.com (Postfix) with ESMTP id 1C23056840; Fri, 11 Mar 2005 14:55:57 -0800 (PST) (envelope-from mellon@fugue.com)
In-Reply-To: <20050311164910.GA61141@isc.org>
References: <4D50D5110555D5119F270800062B41650532AD00@viee10pa.erd.siemens.at> <20050311164910.GA61141@isc.org>
Mime-Version: 1.0 (Apple Message framework v712)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <C2149DFD-4AF7-46C9-A9EF-5D259A46855F@fugue.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] RFC2131 - option multiple times - which ones ?
Date: Fri, 11 Mar 2005 16:54:57 -0600
To: "David W. Hankins" <David_Hankins@isc.org>
X-Mailer: Apple Mail (2.712)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Cc: "Dhcwg (dhcwg@ietf.org)" <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit

On Mar 11, 2005, at 10:49 AM, David W. Hankins wrote:
> Here's the way I wish it read:

RFC3396 updates RFC2131/2132, so you can in fact read it the way you 
describe.   However, you can't count on all implementations being 
compliant with that reading.



_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg