IETF Logo Mail Archive

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

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Tue, 11 July 2000 23:30 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id TAA23317 for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 19:30:02 -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 TAA22931 for <ietf@ietf.org>; Tue, 11 Jul 2000 19:14:33 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007112312.IAA22690@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1) id IAA22690; Wed, 12 Jul 2000 08:12:21 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <E13Bdit-000PFI-00@rip.psg.com> from Randy Bush at "Jul 10, 2000 06:35:47 am"
To: Randy Bush <randy@psg.com>
Date: Wed, 12 Jul 2000 08:12:20 +0859
CC: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Randy;

> > My intention is to provide a semi permanent definition as an Informational
> > RFC.
> > 
> > It is important to make the definition protected by bogus opinions
> > of various bodies including IETF.
> 
> of course you will exuse the providers if we continue to be perverse and
> find new business models.

Exuse? If you mean execution or decapitalization, yes, I will.

							Masataka Ohta

v2.23.0 | Report a Bug | By Email