LineId option
Manu Kaycee <mjk@mtnms.att.com> Mon, 20 May 1996 15:46 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16564;
20 May 96 11:46 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16560;
20 May 96 11:46 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa08723;
20 May 96 11:46 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA15813; Mon, 20 May 1996 11:41:03 -0400
Date: Mon, 20 May 1996 11:41:03 -0400
Message-Id: <Pine.SUN.3.91.960520100033.326I-100000@mtnms>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Manu Kaycee <mjk@mtnms.att.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: LineId option
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
G'day, While providing "Internet Access" services to end-users, my customers have a need to restrict such users to selected incoming ports/interfaces. I realize that DHCP authentication might be used, but I don't believe it would allow such a provider to control the spatial scope of clients. On that premise, I have just started writing up an ID for a LineId option in DHCP options. To which end, a DHCP relay would use this option to specify the inbound port or interface, and a consenting server would use it appropriately. I have looked at the base documents and before I get too far, I'd like to confirm that there is no other way to achieve this today. Comments? Manu
- LineId option Manu Kaycee