[dhcwg] Re: DDNS-DHCP [4]: 12 bit RCODEs in DHCP FQDN option
Ralph Droms <rdroms@cisco.com> Wed, 02 July 2003 17:04 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01833; Wed, 2 Jul 2003 13:04:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xl1U-0007rd-Rb; Wed, 02 Jul 2003 13:04:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xl0g-0007Ze-K8 for dhcwg@optimus.ietf.org; Wed, 02 Jul 2003 13:03:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01622 for <dhcwg@ietf.org>; Wed, 2 Jul 2003 13:03:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xl0e-00046r-00 for dhcwg@ietf.org; Wed, 02 Jul 2003 13:03:09 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19Xl0e-00045d-00 for dhcwg@ietf.org; Wed, 02 Jul 2003 13:03:08 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h62H2Ofq027784; Wed, 2 Jul 2003 13:02:24 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (rtp-vpn2-24.cisco.com [10.82.240.24]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR) with ESMTP id AAJ54587; Wed, 2 Jul 2003 13:02:12 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030702125011.04878e10@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 02 Jul 2003 13:01:19 -0400
To: dhcwg@ietf.org, namedroppers@ops.ietf.org
From: Ralph Droms <rdroms@cisco.com>
Cc: olaf@ripe.net, Bernard Aboba <aboba@internaut.com>, Rob Austein <sra@hactrn.net>, Thomas Narten <narten@us.ibm.com>, Erik.Nordmark@eng.sun.com
In-Reply-To: <Pine.GSO.4.53.0306060647330.29143@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Re: DDNS-DHCP [4]: 12 bit RCODEs in DHCP FQDN option
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
Summary of discussion of this issue: We need more discussion of this issue to determine WG consensus. Mark Stapp responded (see http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg02074.html) that there are many clients that expect the 8 bit RCODE format in draft-ietf-dhc-fqdn-option-05.txt, and the RCODE values of interest to DDNS-DHCP interaction can be carried in an 8 bit field. The WG consensus was that backward compatibility with deployed clients is more important than compatibility with EDNS0 12 bit RCODES. Please review Mark's input and respond to the mailing list... - Ralph At 06:53 AM 6/6/2003 -0400, Ralph Droms wrote: >DDNS-DHCP issue: > > The DHCP FQDN option should carry 12 bit RCODEs, for > consistency with the extended RCODEs defined by EDNS0. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg