Re: draft-ietf-nat-protocol-complications-02.txt

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Wed, 12 July 2000 22:30 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id SAA17189 for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 18:30:04 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17107 for <ietf@ietf.org>; Wed, 12 Jul 2000 18:24:17 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007122216.HAA27122@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1) id HAA27122; Thu, 13 Jul 2000 07:16:36 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200007120112.SAA03427@shell5.ba.best.com> from Greg Skinner at "Jul 11, 2000 06:12:21 pm"
To: Greg Skinner <gds@best.com>
Date: Thu, 13 Jul 2000 07:16:35 +0859
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Greg;

> I could make the argument that they provide Internet access, in the
> sense that one can use these providers to gain access to a subset of
> content and services that is "traditionally" called Internet service.
> I would support them being classified as Internet Access Providers
> (IAPs).  In some circles, that's what they're called.

Your points are taken that you can call them WASP (Web Access Service
Providers).


							Masakaka Ohta