[dhcwg] dhcpv6-24: compression in DNS names

Thomas Narten <narten@us.ibm.com> Wed, 15 May 2002 17:11 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 NAA13773 for <dhcwg-archive@odin.ietf.org>; Wed, 15 May 2002 13:11:14 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA13582 for dhcwg-archive@odin.ietf.org; Wed, 15 May 2002 13:11:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA12869; Wed, 15 May 2002 13:01:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA12836 for <dhcwg@ns.ietf.org>; Wed, 15 May 2002 13:01:11 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (cichlid.adsl.duke.edu [152.16.64.203]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13371 for <dhcwg@ietf.org>; Wed, 15 May 2002 13:00:57 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.11.6) with ESMTP id g4FGxlj02153 for <dhcwg@ietf.org>; Wed, 15 May 2002 12:59:47 -0400
Message-Id: <200205151659.g4FGxlj02153@cichlid.adsl.duke.edu>
To: dhcwg@ietf.org
Date: Wed, 15 May 2002 12:59:47 -0400
From: Thomas Narten <narten@us.ibm.com>
Subject: [dhcwg] dhcpv6-24: compression in DNS names
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

[Note: the IESG is starting to review this document, and I'm getting
questions comments on the ID].

This document specifies that DNS Names are represented in DNS
on-the-wire formate, and compression MUST be supported. I understand
that DHCPv4 supports this now (with recent options).

But there is also complexity associated with the compression part. In
DHCPv4, options were limited in size (255 bytes). DHCPv6 doesn't have
this restriction. So the need for compression is reduced.

How about just removing the requirement to support compression. This
will simplify implementations and doesn't appear to result in any real
loss of functionality.

Thomas

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