[dhcwg] RE: WG last call on draft-ietf-dhc-subscriber-id-01.txt

Ralph Droms <rdroms@cisco.com> Fri, 29 August 2003 11:46 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 HAA14327 for <dhcwg-archive@odin.ietf.org>; Fri, 29 Aug 2003 07:46:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sgO9-0006v2-MC for dhcwg-archive@odin.ietf.org; Fri, 29 Aug 2003 06:21:53 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7TALq8n026578 for dhcwg-archive@odin.ietf.org; Fri, 29 Aug 2003 06:21:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sdwT-0005lk-F9 for dhcwg-web-archive@optimus.ietf.org; Fri, 29 Aug 2003 03:45:09 -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 DAA23136 for <dhcwg-web-archive@ietf.org>; Fri, 29 Aug 2003 03:45:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sdwQ-0003fu-00 for dhcwg-web-archive@ietf.org; Fri, 29 Aug 2003 03:45:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19sdwQ-0003fq-00 for dhcwg-web-archive@ietf.org; Fri, 29 Aug 2003 03:45:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sdVF-0003y6-Sx; Fri, 29 Aug 2003 03:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sd4P-0002eL-Om for dhcwg@optimus.ietf.org; Fri, 29 Aug 2003 02:49:17 -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 CAA18418 for <dhcwg@ietf.org>; Fri, 29 Aug 2003 02:49:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sd4L-0002Wq-00 for dhcwg@ietf.org; Fri, 29 Aug 2003 02:49:13 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19sd4J-0002Vm-00 for dhcwg@ietf.org; Fri, 29 Aug 2003 02:49:13 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h7T6mfCb026341 for <dhcwg@ietf.org>; Thu, 28 Aug 2003 23:48:41 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (rtp-vpn1-133.cisco.com [10.82.224.133]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ABY10927; Fri, 29 Aug 2003 02:48:40 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030828082336.021c2518@localhost>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 29 Aug 2003 02:48:36 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] RE: WG last call on draft-ietf-dhc-subscriber-id-01.txt
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>

Issues:

1) The motivation could for this option could be explained more completely.
It comes from the observation that, in some scenarios, the relay agent
supplying identification information like a circuit ID or remote ID may be
in a different administrative domain from the DHCP servers that receive the
relay agent option.  When the administrator of the relay agent makes a change
to the network configuration that changes the circuit ID or remote ID for
the subscriber, the MSP must contact each of the administrators of the DHCP
servers to update the corresponding entry in the DHCP servers.

For example, in a managed service provider (MSP) deployment, the relay agent
is in the administrative domain of the MSP while the ISPs using that MSP
each control their own independent DHCP server.  If the MSP changes the
attachment point of a subscriber, the MSP must contact each of the ISPs with
the new relay agent option information so that the ISPs can update their
DHCP servers.

The Subscriber ID suboption isolates changes in the network configuration to
the administrative domain of the relay agent.  That is, the administrator
can change the network configuration and the subscriber ID information
simultaneously, so the DHCP servers need not be updated with any new
information about the subscriber.

2) The Abstract states that the data value in a Subscriber ID suboption "can
be interpreted in any form by the DHCP server" and "its intended purpose is
to give additional information which the DHCP server can use in address
allocation".  The Introduction then gives more detail in defining the
contents of the suboption as a subscriber identifier, which seems to me to
be a more specific definition than the one in the Abstract.  it might be
clearer to give the more precise definition in the Abstract, as well.

Nits:

The data in the Subscriber ID suboption is variously described as "an array
of bytes" and a "configurable hexadecimal value".  The description of the
data would be clarified if a uniform describing phrase were used throughout
the document.

In the third paragraph of section 2, the last sentence should be changed to
reflect that the subscriber ID can be considered in the assignment of other
configuration parameters in addition to the assignment of an IP address.

- Ralph


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