Re: draft-ietf-nat-protocol-complications-02.txt
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 10 July 2000 01:20 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12560 for ietf-outbound.10@ietf.org; Sun, 9 Jul 2000 21:20: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 VAA12515 for <ietf@ietf.org>; Sun, 9 Jul 2000 21:14:34 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007100106.KAA12155@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1) id KAA12155; Mon, 10 Jul 2000 10:06:29 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <7731.957178550@cs.ucl.ac.uk> from Jon Crowcroft at "May 1, 2000 11:55:50 am"
To: ietf@ietf.org
Date: Mon, 10 Jul 2000 10:06:29 +0859
CC: "vinton g. cerf" <vcerf@MCI.NET>, Matt Holdrege <holdrege@lucent.com>, Thomas Narten <narten@raleigh.ibm.com>, ietf@ietf.org, J.Crowcroft@CS.UCL.AC.UK
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org
Dear all; Based on the previous discussion, Jon> In message <200005010842.RAA11363@necom830.hpcl.titech.ac.jp>, Masataka Ohta ty Jon> ped: Jon> Jon> >> Is it fair if providers using iMODE or WAP are advertised Jon> >> to be ISPs? Jon> >> Jon> >> Is it fair if providers using NAT are advertised to be ISPs? Jon> >> Jon> >>My answer to both questions is Jon> >> Jon> >> No, while they may be Internet Service Access Providers and Jon> >> NAT users may be IP Service Providers, they don't provide Jon> >> Internet service and are no ISPs. Jon> Jon> i agree: Jon> in the UK, i would say that someone claiming internet access via WAP Jon> would be in breach of the trades description act. Jon> Jon> >>Any oppositions? Jon> Jon> not from here (for wap - i dont know enough about iMODE to comment) and lack of oppsitions in the thread, I have drafted an attached ID. However, IESG is blocking the publication of the ID (it is just an Internet Draft, NOT an Informational RFC)! IESG says they have not even saw the content, which means a lot of time will be wasted further. So, I post the draft to the Mailing List. Any comments on the content of the draft? Comments for the blockage, if any, should be given with a separate subject? I hope IESG has not taken the obvious next step of the moderation of the Mailing List. Masataka Ohta --- INTERNET DRAFT M. Ohta draft-ohta-isps-00.txt Tokyo Institute of Technology July 2000 The Internet and ISPs Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright (C) The Internet Society (May/1/2000). All Rights Reserved. Abstract This memo gives definitions on the Internet and ISPs (Internet Service Providers). 1. The Internet The Internet is a public IP [1, 2] network globally connected end to end [3] at the Internetworking layer. 2. ISPs A network provider is an ISP, if and only if its network, including access parts of the network to its subscribers, is a part of the Internet. As such, ISPs must preserve the end to end and globally connected principles of the Internet at the Internetworking layer. M. Ohta Expires on January 1, 2001 [Page 1] INTERNET DRAFT ISPs July 2000 A network provider of a private IP or non-IP network, which is connected to the Internet through an application and/or transport gateway is not an ISP. Dispit the requirement of "global connectivity", a network provider may use transparent firewalls to the Internet with no translation to filter out a limited number of problematic well known ports of TCP and/or UDP and can still be an ISP. However, if filtering out is a default and only a limited number of protocols are allowed to pass the firewalls (which means snooping of transport/application layer protocols), it can not be regarded as full connectivity to the Internet and the provider is not an ISP. 3. Security Considerations While some people may think that filtering by application/transport gateways offer some sort of security, they should recognize that macro virus in e-mails can pass and are passing through all such gateways. 4. References [1] J. Postel, "Internet Protocol", RFC791, September 1981. [2] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC2460, December 1998. [3] B. Carpenter, "Architectural Principles of the Internet", RFC1958, June 1996. 5. Author's Address Masataka Ohta Computer Center, Tokyo Institute of Technology 2-12-1, O-okayama, Meguro-ku, Tokyo 152-8550, JAPAN Phone: +81-3-5734-3299 Fax: +81-3-5734-3415 EMail: mohta@necom830.hpcl.titech.ac.jp M. Ohta Expires on January 1, 2001 [Page 2] INTERNET DRAFT ISPs July 2000 6. Full Copyright Statement "Copyright (C) The Internet Society (July/1/2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. M. Ohta Expires on January 1, 2001 [Page 3]
- draft-ietf-nat-protocol-complications-02.txt Jeffrey Altman
- Re: draft-ietf-nat-protocol-complications-02.txt Matt Holdrege
- Re: draft-ietf-nat-protocol-complications-02.txt Jeffrey Altman
- Re: draft-ietf-nat-protocol-complications-02.txt Matt Holdrege
- Re: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Robert G. Ferrell
- Re: draft-ietf-nat-protocol-complications-02.txt Jeffrey Altman
- Re: draft-ietf-nat-protocol-complications-02.txt Thomas Narten
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Pyda Srisuresh
- Re: draft-ietf-nat-protocol-complications-02.txt Pyda Srisuresh
- Re: draft-ietf-nat-protocol-complications-02.txt Pyda Srisuresh
- Re: draft-ietf-nat-protocol-complications-02.txt Jeffrey Altman
- Re: draft-ietf-nat-protocol-complications-02.txt Greg Hudson
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Greg Hudson
- Re: draft-ietf-nat-protocol-complications-02.txt Jeffrey Altman
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Paul B. Hill
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Pyda Srisuresh
- Re: draft-ietf-nat-protocol-complications-02.txt Theodore Y. Ts'o
- Re: draft-ietf-nat-protocol-complications-02.txt Pyda Srisuresh
- Re: draft-ietf-nat-protocol-complications-02.txt Henning Schulzrinne
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Richard Shockey
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt vinton g. cerf
- Re: draft-ietf-nat-protocol-complications-02.txt Mark Prior
- RE: draft-ietf-nat-protocol-complications-02.txt Bernard Aboba
- Re: draft-ietf-nat-protocol-complications-02.txt Jon Crowcroft
- Re: draft-ietf-nat-protocol-complications-02.txt Brian Lloyd
- RE: draft-ietf-nat-protocol-complications-02.txt Dick St.Peters
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Randy Bush
- Re: draft-ietf-nat-protocol-complications-02.txt Dick St.Peters
- Re: draft-ietf-nat-protocol-complications-02.txt Peter Johansson
- Re: draft-ietf-nat-protocol-complications-02.txt Richard Shockey
- RE: draft-ietf-nat-protocol-complications-02.txt Ian King
- IPv6: Past mistakes repeated? Anthony Atkielski
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: IPv6: Past mistakes repeated? Jon Crowcroft
- Re: draft-ietf-nat-protocol-complications-02.txt Pyda Srisuresh
- Re: draft-ietf-nat-protocol-complications-02.txt Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt John Stracke
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt John Stracke
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: IPv6: Past mistakes repeated? Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: IPv6: Past mistakes repeated? Anthony Atkielski
- Re: draft-ietf-nat-protocol-complications-02.txt Theodore Y. Ts'o
- Re: IPv6: Past mistakes repeated? John Stracke
- Re: IPv6: Past mistakes repeated? Anthony Atkielski
- correction Re: IPv6: Past mistakes repeated? Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Daniel Senie
- Re: draft-ietf-nat-protocol-complications-02.txt Andrew Partan
- Re: IPv6: Past mistakes repeated? Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Paul Ferguson
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Leonid Yegoshin
- How many IP addresses? Graham Klyne
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Thomas Narten
- Re: draft-ietf-nat-protocol-complications-02.txt Thomas Narten
- Re: draft-ietf-nat-protocol-complications-02.txt Bill Manning
- Re: draft-ietf-nat-protocol-complications-02.txt Bill Manning
- Re: draft-ietf-nat-protocol-complications-02.txt David R. Conrad
- Re: draft-ietf-nat-protocol-complications-02.txt Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt Valdis.Kletnieks
- Re: draft-ietf-nat-protocol-complications-02.txt Jeffrey Altman
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: IPv6: Past mistakes repeated? Joe Touch
- Re: draft-ietf-nat-protocol-complications-02.txt Bill Manning
- Re: draft-ietf-nat-protocol-complications-02.txt Leonid Yegoshin
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt David R. Conrad
- Re: draft-ietf-nat-protocol-complications-02.txt Bill Manning
- Re: IPv6: Past mistakes repeated? Anthony Atkielski
- Re: draft-ietf-nat-protocol-complications-02.txt Bill Manning
- Re: draft-ietf-nat-protocol-complications-02.txt Leonid Yegoshin
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- NAT->IPv6 Matt Holdrege
- Re: draft-ietf-nat-protocol-complications-02.txt Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt David R. Conrad
- Re: IPv6: Past mistakes repeated? Valdis.Kletnieks
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- multihoming (was Re: draft-ietf-nat-protocol-comp… Paul Francis
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Brian Lloyd
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: IPv6: Past mistakes repeated? Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: NAT->IPv6 Charles E. Perkins
- Re: IPv6: Past mistakes repeated? John Stracke
- Re: draft-ietf-nat-protocol-complications-02.txt Valdis.Kletnieks
- Re: draft-ietf-nat-protocol-complications-02.txt Marc Slemko
- Re: IPv6: Past mistakes repeated? Steve Deering
- Re: multihoming (was Re: draft-ietf-nat-protocol-… John Stracke
- Re: IPv6: Past mistakes repeated? Andrew Partan
- Re: multihoming (was Re: draft-ietf-nat-protocol-… Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt George Michaelson
- Re: draft-ietf-nat-protocol-complications-02.txt Leonid Yegoshin
- Re: draft-ietf-nat-protocol-complications-02.txt Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt Bill Manning
- Re: draft-ietf-nat-protocol-complications-02.txt Eliot Lear
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Thomas Narten
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Jon Crowcroft
- Re: draft-ietf-nat-protocol-complications-02.txt Thomas Narten
- RE: draft-ietf-nat-protocol-complications-02.txt Brijesh Kumar
- Re: draft-ietf-nat-protocol-complications-02.txt Matt Holdrege
- Re: draft-ietf-nat-protocol-complications-02.txt Eliot Lear
- Re: multihoming (was Re: draft-ietf-nat-protocol-… Paul Francis
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Tim Salo
- Re: draft-ietf-nat-protocol-complications-02.txt David R. Conrad
- Re: draft-ietf-nat-protocol-complications-02.txt David R. Conrad
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-02.txt Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt Steven M. Bellovin
- Re: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-02.txt Jon Crowcroft
- RE: draft-ietf-nat-protocol-complications-02.txt BookIII, Robert
- RE: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt vinton g. cerf
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Jon Crowcroft
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt John Stracke
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Any comparison Study on MGCP vs H.323, MGCP vs SIP Yixin Zhu
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Jon Crowcroft
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Randy Bush
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Patrik Fältström
- Re: draft-ietf-nat-protocol-complications-02.txt Randy Bush
- RE: draft-ietf-nat-protocol-complications-02.txt mark.paton
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- RE: draft-ietf-nat-protocol-complications-02.txt Randy Bush
- RE: draft-ietf-nat-protocol-complications-02.txt aboba
- RE: draft-ietf-nat-protocol-complications-02.txt Bob Braden
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Greg Skinner
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- RE: draft-ietf-nat-protocol-complications-02.txt Brijesh Kumar
- Re: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- precedence field and mailing lists Keith Moore
- AOL and standards Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Greg Skinner
- AOL's view of the Net versus the rest Anthony Atkielski
- Re: draft-ietf-nat-protocol-complications-02.txt Greg Skinner
- Re: AOL's view of the Net versus the rest Valdis.Kletnieks
- Re: draft-ietf-nat-protocol-complications-02.txt Eli Sanchez
- Re: draft-ietf-nat-protocol-complications-02.txt Robert G. Ferrell
- RE: draft-ietf-nat-protocol-complications-02.txt mark.paton
- Re: draft-ietf-nat-protocol-complications-02.txt Peter Deutsch in Mountain View
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Greg Skinner
- Re: draft-ietf-nat-protocol-complications-02.txt John Stracke