IETF Logo Mail Archive

Re: Static IP addresses for Dial-up

Piet Beertema <Piet.Beertema@cwi.nl> Mon, 29 January 1996 19:00 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28724; 29 Jan 96 14:00 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa28719; 29 Jan 96 14:00 EST
Received: from nico.aarnet.edu.au by CNRI.Reston.VA.US id aa12961; 29 Jan 96 13:59 EST
Received: from charon.cwi.nl (charon.cwi.nl [192.16.184.142]) by nico.aarnet.edu.au (8.6.10/8.6.10) with SMTP id DAA15196 for <cidrd@iepg.org>; Tue, 30 Jan 1996 03:18:55 +1100
Received: from kraai.cwi.nl by charon.cwi.nl with SMTP id <AA03953@cwi.nl>; Mon, 29 Jan 1996 17:18:36 +0100
Received: by kraai.cwi.nl with SMTP id <AA05650@cwi.nl>; Mon, 29 Jan 1996 17:18:36 +0100
Message-Id: <9601291618.AA05650=piet@kraai.cwi.nl>
To: Paul Ferguson <pferguso@cisco.com>
In-Reply-To: "Your message of Mon, 29 Jan 1996 08:12:37 -0500 " <199601291311.FAA04274@lint.cisco.com>
Subject: Re: Static IP addresses for Dial-up
Cc: Brian Carpenter CERN-CN <brian@dxcoms.cern.ch>, peter@unipalm.pipex.com, nanog@merit.edu, cidrd@iepg.org, iab@isi.edu, Robert Elz <kre@munnari.oz.au>
Date: Mon, 29 Jan 1996 17:18:35 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Piet Beertema <Piet.Beertema@cwi.nl>

    I can certainly understand the need for access control & security,
    but with the use of a smart-card one-time password system, this is
    a moot point. 
Huh? How are you going to stop a system from "illegally"
(in the sense of the provider, contracts, or whatever)
acting as -say- www, ftp, or whatever server with such
a one-time password system? You'll need access control
*based on IP addresses* to reach that goal!


	Piet

v2.23.0 | Report a Bug | By Email