From daemon Sat Nov 22 12:16:38 1997 Delivery-Date: Sat, 22 Nov 1997 12:22:39 -0500 Return-Path: daemon Received: (from daemon@localhost) by ns.ietf.org (8.8.7/8.8.7a) id MAA08609 for ietf-123-outbound.10@ietf.org; Sat, 22 Nov 1997 12:16:26 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id MAA08578; Sat, 22 Nov 1997 12:16:21 -0500 (EST) Message-Id: <199711221716.MAA08578@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-6bone-routing-issues-00.txt Date: Sat, 22 Nov 1997 12:16:20 -0500 Sender: scoya@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : IPv6 routing issues Author(s) : A. Durand Filename : draft-ietf-ngtrans-6bone-routing-issues-00.txt Pages : 4 Date : 21-Nov-97 6bone routes have sometimes provide examples of bogus routes who introduced serious operational issues. This memo identifies some pathological cases and try to give some guidelines how 6bone nodes should handle them. This is ongoing work and lots of changes should be made to this text. It is only published as a starting point for a discussion. It will cover: 1) link local addresses 2) site local addresses 3) special case addresses: loopback addresses & unspecified addresses 4) multicast addresses 5) IPv4-mapped addresses 6) IPv4-compatible addresses 7) Yet undefined unicast addresses (from a different /3 prefix) 8) default routes 9) aggregation issues 10) tunnel issues Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-6bone-routing-issues-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971122121329.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-6bone-routing-issues-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971122121329.I-D@ietf.org> --OtherAccess-- --NextPart-- From daemon Sat Nov 22 12:17:44 1997 Delivery-Date: Sat, 22 Nov 1997 12:23:14 -0500 Return-Path: daemon Received: (from daemon@localhost) by ns.ietf.org (8.8.7/8.8.7a) id MAA08716 for ietf-123-outbound.10@ietf.org; Sat, 22 Nov 1997 12:17:33 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id MAA08686; Sat, 22 Nov 1997 12:17:28 -0500 (EST) Message-Id: <199711221717.MAA08686@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-nnat-00.txt Date: Sat, 22 Nov 1997 12:17:28 -0500 Sender: scoya@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : No Network Address Translation (NNAT) for IPv6 Author(s) : J. Bound Filename : draft-ietf-ngtrans-nnat-00.txt Pages : 10 Date : 21-Nov-97 The initial deployment of IPv6 will require a tightly coupled use of IPv4 addresses to support the interoperation of IPv6 and IPv4. Nodes will be able to be deployed with IPv6 addresses, but will still need to communicate with IPv4 nodes that do not have a dual IP layer supporting both IPv4 and IPv6. This specification defines a mechanism called No Network Address Translation (NNAT), which will assign an IPv6 node a temporary IPv4 address, which can be used to communicate with a node that supports only IPv4. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-nnat-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ngtrans-nnat-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-nnat-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971122121347.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-nnat-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-nnat-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971122121347.I-D@ietf.org> --OtherAccess-- --NextPart-- From daemon Sat Nov 22 12:18:10 1997 Delivery-Date: Sat, 22 Nov 1997 12:23:38 -0500 Return-Path: daemon Received: (from daemon@localhost) by ns.ietf.org (8.8.7/8.8.7a) id MAA08774 for ietf-123-outbound.10@ietf.org; Sat, 22 Nov 1997 12:17:55 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id MAA08746; Sat, 22 Nov 1997 12:17:49 -0500 (EST) Message-Id: <199711221717.MAA08746@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-header-trans-01.txt Date: Sat, 22 Nov 1997 12:17:48 -0500 Sender: scoya@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Stateless IP/ICMP Translator (SIIT) Author(s) : E. Nordmark Filename : draft-ietf-ngtrans-header-trans-01.txt Pages : 22 Date : 21-Nov-97 This document specifies a transition mechanism in addition to those already specified in RFC 1933. The new mechanism can be used as part of a solution that allows IPv6 hosts that do not have a permanently assigned IPv4 address to communication with IPv4-only hosts. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-header-trans-01.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ngtrans-header-trans-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-header-trans-01.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971122114855.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-header-trans-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-header-trans-01.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971122114855.I-D@ietf.org> --OtherAccess-- --NextPart-- From daemon Sat Nov 22 12:18:33 1997 Delivery-Date: Sat, 22 Nov 1997 12:25:45 -0500 Return-Path: daemon Received: (from daemon@localhost) by ns.ietf.org (8.8.7/8.8.7a) id MAA08843 for ietf-123-outbound.10@ietf.org; Sat, 22 Nov 1997 12:18:20 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id MAA08813; Sat, 22 Nov 1997 12:18:16 -0500 (EST) Message-Id: <199711221718.MAA08813@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-mech-00.txt Date: Sat, 22 Nov 1997 12:18:16 -0500 Sender: scoya@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Transition Mechanisms for IPv6 Hosts and Routers Author(s) : Filename : draft-ietf-ngtrans-mech-00.txt Pages : 22 Date : 21-Nov-97 This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. These mechanisms include pro- viding complete implementations of both versions of the Internet Pro- tocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4 routing infrastructures. They are designed to allow IPv6 nodes to maintain complete compatibility with IPv4, which should greatly simplify the deployment of IPv6 in the Internet, and facilitate the eventual tran- sition of the entire Internet to IPv6. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-mech-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ngtrans-mech-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-mech-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971122115021.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-mech-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-mech-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971122115021.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Tue Dec 30 11:42:15 1997 Delivery-Date: Tue, 30 Dec 1997 11:49:31 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id LAA05981 for ietf-123-outbound.10@ietf.org; Tue, 30 Dec 1997 11:42:03 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id LAA04934; Tue, 30 Dec 1997 11:13:39 -0500 (EST) Message-Id: <199712301613.LAA04934@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-natpt-00.txt Date: Tue, 30 Dec 1997 11:13:38 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Network Address Translation - Protocol Translation (NAT-PT] Author(s) : G. Tsirtsis Filename : draft-ietf-ngtrans-natpt-00.txt Pages : 4 Date : 29-Dec-97 This document specifies a transition mechanism in addition to those already specified in RFC 1933. The new mechanism can be used to allow IPv6-only hosts to communicate with IPv4-only hosts using Network Address Translation, for efficient use of the IPv4 address space, and Protocol Translation, in order to avoid implementing dual-stack in every machine that migrates to IPv6. This proposal attempts to reuse as much functionality as possible from existing proposals like [NAT], [NNAT] and [SIIT]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-natpt-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ngtrans-natpt-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-natpt-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971229153452.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-natpt-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-natpt-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971229153452.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Wed Jan 28 11:27:17 1998 Delivery-Date: Wed, 28 Jan 1998 11:31:34 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id LAA02907 for ietf-123-outbound.10@ietf.org; Wed, 28 Jan 1998 11:27:03 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id KAA29817; Wed, 28 Jan 1998 10:15:29 -0500 (EST) Message-Id: <199801281515.KAA29817@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-6bone-routing-issues-01.txt Date: Wed, 28 Jan 1998 10:15:28 -0500 Sender: cclark@cnri.reston.va.us --NextPart A Revised Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : IPv6 routing issues Author(s) : A. Durand Filename : draft-ietf-ngtrans-6bone-routing-issues-01.txt Pages : 4 Date : 27-Jan-98 The 6bone provides examples of bogus routes which introduced serious operational issues. This memo identifies some pathological cases and gives some guidelines on how 6bone sites should handle them. It defines the 'best current practise' acceptable in the 6bone for the config- uration of both Interior Gateway Protocols (like RIPng) and Exterior Gateway Protocols (like BGP4+). NB: Core routers used in pTLA sites MUST use BGP4+. This memo will cover: 1) link local prefixes 2) site local prefixes 3) special case prefixes: loopback prefix & unspecified prefix 4) multicast prefixes 5) IPv4-mapped prefixes 6) IPv4-compatible prefixes 7) Yet undefined unicast prefixes (from a different /3 prefix) 8) default routes 9) aggregation issues 10) Inter site tunnel issues Internet-Drafts are available by anonymous FTP. Login wih the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-6bone-routing-issues-01.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-01.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19980127102126.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-6bone-routing-issues-01.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980127102126.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Wed Feb 4 09:33:36 1998 Delivery-Date: Wed, 04 Feb 1998 09:38:20 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id JAA10699 for ietf-123-outbound.10@ietf.org; Wed, 4 Feb 1998 09:32:02 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id JAA10110; Wed, 4 Feb 1998 09:17:16 -0500 (EST) Message-Id: <199802041417.JAA10110@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-6bone-multi-00.txt Date: Wed, 04 Feb 1998 09:17:15 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Multihomed routing domain issues for IPv6 aggregatable scheme Author(s) : F. Dupont Filename : draft-ietf-ngtrans-6bone-multi-00.txt Pages : 12 Date : 03-Feb-98 This document exposes some issues for multihomed routing domains using the aggregatable addressing and routing scheme. A routing domain is multihomed when it uses two or more providers of the upper level. Most of these issues are not specific to IPv6 but are consequences of the addressing and routing scheme. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-6bone-multi-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ngtrans-6bone-multi-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-6bone-multi-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19980203154852.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-6bone-multi-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-6bone-multi-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980203154852.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-nat@livingston.com Mon Feb 9 14:47:45 1998 Delivery-Date: Mon, 09 Feb 1998 14:47:45 -0500 Return-Path: owner-nat@livingston.com Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id OAA28520 for ; Mon, 9 Feb 1998 14:47:44 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id LAA27112; Mon, 9 Feb 1998 11:38:12 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id LAA20678 for nat-outgoing; Mon, 9 Feb 1998 11:39:46 -0800 (PST) From: bound@zk3.dec.com Message-Id: <199802091937.AA27020@wasted.zk3.dec.com> To: nat@livingston.com, ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, 6bone@isi.edu, dhcp-v4@bucknell.edu, dhcp-v6@bucknell.edu, mobile-ip@SmallWorks.com, ipsec@tis.com Subject: (NAT) AATN (alternatives to NAT) Mail List Set up........................ Date: Mon, 09 Feb 1998 14:37:11 -0500 X-Mts: smtp Sender: owner-nat@livingston.com Precedence: bulk Reply-To: bound@zk3.dec.com DO NOT RESPOND TO THIS MAIL IT IS INFORMATION per a new Mail List. If you have comment please send to me privately or get on the aatn list and send it to aatn... I have submitted a request and description for a BOF to the IETF Internet ADs to discuss alternatives to NAT. But I set up a mail list as interim place to discuss this technology. My mail is attached to the ADs....Comments on description and agenda welcome the more we do before L.A. the better we can determine if this work should move forward. send mail to - majordomo@alpha.zk3.dec.com subscribe aatn your-email-addr THose of you who sent me mail to be on this are already subscribed if you sent me mail before Noon today everyone else please subscribe directly yourself. Apology for this interruption but folks on these mail lists have expresssed an interest in alternatives to NAT and I wanted to let them know, we have a place to discuss it. /jim -------------- Return-Path: bound Received: from bywasted.zk3.dec.com by mailhub2.zk3.dec.com (5.65v3.2/1.1.10.5/24Sep96-0323PM) id AA12327; Mon, 9 Feb 1998 13:14:29 -0500 Received: from localhost by wasted.zk3.dec.com (5.65v4.0/1.1.8.2/18Feb95-1123AM) id AA16538; Mon, 9 Feb 1998 13:14:12 -0500 Message-Id: <199802091814.AA16538@wasted.zk3.dec.com> To: narten@vnet.ibm.com, burgan@home.net Cc: agenda@ietf.org, bound@zk3.dec.com, Erik.Nordmark@eng.sun.com, gabriel.montenergo@eng.sun.com, vipul.gupta@eng.sun.com, george@gideon.bt.co.uk, alan.oneill@bt-sys.bt.co.uk Subject: Request for AATN BOF at L.A. IETF Meeting Date: Mon, 09 Feb 1998 13:14:12 -0500 From: bound X-Mts: smtp Thomas and Jeff, I would like to request a 2 hour BOF for the subject "Avoidance of Address Translation in Networks" (AATN), for the L.A. Meeting. I have to request this BOF not happen during the following events so I may lead it. IPng, NGTRANS, DHCPv6, or NAT BOF meetings. Evening is fine too, but day is better. I feel this BOF should be sponsored by the Internet Area as it affects the Internet Layer of the IP model. If it should become a WG then that is up to the IESG to decide clearly where that should be located. I enlist your leadership and support to get this discussed. I am already setting up an initial mail list now. It could take two BOFs to determine what this work would entail and if it should be a working group, I just don't know right now. Description of BOF: To address the limitations of the IPv4 address space the Internet community needs to adopt variant technologies until IPv6 can be deployed giving the Internet a new address space. Three such technologies are Network Address Translation (NAT), Link Tunnel Protocols like L2TP, and the use of address translation in Firwall products. This BOF would like to investigate and discover if there is valid work to do, which can be used to assist this IPv4 problem thru the Avoidance of Network Address Translation on Networks (AATN). This work would address todays need for IPv4 and some of the needs for IPv6 which are not addressed by the existing NGTRANS WG. Because this work includes work specific just to IPv4 it should not be part of NGTRANS, but there will be some overlap clearly. Engineers in our community have begun to work on AATN in various manners and from several IETF WG mail lists this work appears to have a growing interest. This is also not part of the NAT work on going as that function is to define and specifiy parts to do NAT. One objective of this work is to provide and insure that end-to-end host connectivity is supported for mobility and IPSEC, without network address translation. Examples of work in our community to support AATN exist today: draft-tsirtisi-nat-bypass-00.txt George Tsirtisi and ALan O'Neill (British Telecom Labs) draft-montenegro-firewall-sup-03.txt G. Montenegro and V. Gupta (Sun Microsystems) draft-ngtrans-header-trans-01.txt Erik Nordmark (Sun Microsystems) draft-ngtrans-nnat-00.txt Jim Bound (Digital Equipment Corporation) A tentative agenda would look as follows: - What is the taxonomy AATN and what are some examples. - Specific Overviews of AATN (the above draft examples possibly) - What would be the objectives and charter of such a WG - What would be the deliverables of such a WG - Do we want to start a working group for AATN Sincerely, /jim Jim Bound IPv6 Technical Director Consulting Engineer UNIX Internet Group Digital Equipment Corporation 1+(603) 884-0400 bound@zk3.dec.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message. From owner-mobile-ip@smallworks.com Mon Feb 9 15:35:34 1998 Delivery-Date: Mon, 09 Feb 1998 15:35:36 -0500 Return-Path: owner-mobile-ip@smallworks.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id PAA29400 for ; Mon, 9 Feb 1998 15:35:29 -0500 (EST) Received: from hosaka.smallworks.com (hosaka.SmallWorks.COM [192.207.126.1]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA04486 for ; Mon, 9 Feb 1998 15:38:11 -0500 (EST) Received: (from majordomo@localhost) by hosaka.smallworks.com (8.8.7/8.8.7) id NAA10132 for mobile-ip-dist; Mon, 9 Feb 1998 13:38:41 -0600 (CST) X-Authentication-Warning: hosaka.smallworks.com: majordomo set sender to owner-mobile-ip using -f Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by hosaka.smallworks.com (8.8.7/8.8.7) with ESMTP id NAA10127 for ; Mon, 9 Feb 1998 13:38:05 -0600 (CST) From: bound@zk3.dec.com Received: from wasted.zk3.dec.com (abelia.zk3.dec.com [16.140.64.63]) by mail13.digital.com (8.8.8/8.8.8/WV1.0c) with SMTP id OAA25408; Mon, 9 Feb 1998 14:36:16 -0500 (EST) Received: from localhost by wasted.zk3.dec.com (5.65v4.0/1.1.8.2/18Feb95-1123AM) id AA27020; Mon, 9 Feb 1998 14:37:11 -0500 Message-Id: <199802091937.AA27020@wasted.zk3.dec.com> To: nat@livingston.com, ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, 6bone@isi.edu, dhcp-v4@bucknell.edu, dhcp-v6@bucknell.edu, mobile-ip@smallworks.com, ipsec@tis.com Subject: (mobile-ip) AATN (alternatives to NAT) Mail List Set up........................ Date: Mon, 09 Feb 1998 14:37:11 -0500 X-Mts: smtp Sender: owner-mobile-ip@smallworks.com Precedence: bulk Reply-To: bound@zk3.dec.com DO NOT RESPOND TO THIS MAIL IT IS INFORMATION per a new Mail List. If you have comment please send to me privately or get on the aatn list and send it to aatn... I have submitted a request and description for a BOF to the IETF Internet ADs to discuss alternatives to NAT. But I set up a mail list as interim place to discuss this technology. My mail is attached to the ADs....Comments on description and agenda welcome the more we do before L.A. the better we can determine if this work should move forward. send mail to - majordomo@alpha.zk3.dec.com subscribe aatn your-email-addr THose of you who sent me mail to be on this are already subscribed if you sent me mail before Noon today everyone else please subscribe directly yourself. Apology for this interruption but folks on these mail lists have expresssed an interest in alternatives to NAT and I wanted to let them know, we have a place to discuss it. /jim -------------- Return-Path: bound Received: from bywasted.zk3.dec.com by mailhub2.zk3.dec.com (5.65v3.2/1.1.10.5/24Sep96-0323PM) id AA12327; Mon, 9 Feb 1998 13:14:29 -0500 Received: from localhost by wasted.zk3.dec.com (5.65v4.0/1.1.8.2/18Feb95-1123AM) id AA16538; Mon, 9 Feb 1998 13:14:12 -0500 Message-Id: <199802091814.AA16538@wasted.zk3.dec.com> To: narten@vnet.ibm.com, burgan@home.net Cc: agenda@ietf.org, bound@zk3.dec.com, Erik.Nordmark@eng.sun.com, gabriel.montenergo@eng.sun.com, vipul.gupta@eng.sun.com, george@gideon.bt.co.uk, alan.oneill@bt-sys.bt.co.uk Subject: Request for AATN BOF at L.A. IETF Meeting Date: Mon, 09 Feb 1998 13:14:12 -0500 From: bound X-Mts: smtp Thomas and Jeff, I would like to request a 2 hour BOF for the subject "Avoidance of Address Translation in Networks" (AATN), for the L.A. Meeting. I have to request this BOF not happen during the following events so I may lead it. IPng, NGTRANS, DHCPv6, or NAT BOF meetings. Evening is fine too, but day is better. I feel this BOF should be sponsored by the Internet Area as it affects the Internet Layer of the IP model. If it should become a WG then that is up to the IESG to decide clearly where that should be located. I enlist your leadership and support to get this discussed. I am already setting up an initial mail list now. It could take two BOFs to determine what this work would entail and if it should be a working group, I just don't know right now. Description of BOF: To address the limitations of the IPv4 address space the Internet community needs to adopt variant technologies until IPv6 can be deployed giving the Internet a new address space. Three such technologies are Network Address Translation (NAT), Link Tunnel Protocols like L2TP, and the use of address translation in Firwall products. This BOF would like to investigate and discover if there is valid work to do, which can be used to assist this IPv4 problem thru the Avoidance of Network Address Translation on Networks (AATN). This work would address todays need for IPv4 and some of the needs for IPv6 which are not addressed by the existing NGTRANS WG. Because this work includes work specific just to IPv4 it should not be part of NGTRANS, but there will be some overlap clearly. Engineers in our community have begun to work on AATN in various manners and from several IETF WG mail lists this work appears to have a growing interest. This is also not part of the NAT work on going as that function is to define and specifiy parts to do NAT. One objective of this work is to provide and insure that end-to-end host connectivity is supported for mobility and IPSEC, without network address translation. Examples of work in our community to support AATN exist today: draft-tsirtisi-nat-bypass-00.txt George Tsirtisi and ALan O'Neill (British Telecom Labs) draft-montenegro-firewall-sup-03.txt G. Montenegro and V. Gupta (Sun Microsystems) draft-ngtrans-header-trans-01.txt Erik Nordmark (Sun Microsystems) draft-ngtrans-nnat-00.txt Jim Bound (Digital Equipment Corporation) A tentative agenda would look as follows: - What is the taxonomy AATN and what are some examples. - Specific Overviews of AATN (the above draft examples possibly) - What would be the objectives and charter of such a WG - What would be the deliverables of such a WG - Do we want to start a working group for AATN Sincerely, /jim Jim Bound IPv6 Technical Director Consulting Engineer UNIX Internet Group Digital Equipment Corporation 1+(603) 884-0400 bound@zk3.dec.com ----------------------------------------------------------------------------- IETF Mobile IP Working Group Mailing List - Archives: software.watson.ibm.com Unsubscribe: unsubscribe mobile-ip (as message body, not subject) Direct all administrative requests to majordomo@smallworks.com From adm Tue Mar 3 09:18:28 1998 Delivery-Date: Tue, 03 Mar 1998 09:22:45 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id JAA19305 for ietf-123-outbound.10@ietf.org; Tue, 3 Mar 1998 09:17:03 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id IAA18742; Tue, 3 Mar 1998 08:59:19 -0500 (EST) Message-Id: <199803031359.IAA18742@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-assgn-ipv4-addrs-00.txt Date: Tue, 03 Mar 1998 08:59:18 -0500 Sender: scoya@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Assignment of IPv4 Global Addresses to IPv6 Hosts (AIIH) Author(s) : J. Bound Filename : draft-ietf-ngtrans-assgn-ipv4-addrs-00.txt Pages : 17 Date : 02-Mar-98 The initial deployment of IPv6 will require a tightly coupled use of IPv4 addresses to support the interoperation of IPv6 and IPv4. Nodes will be able to be deployed with IPv6 addresses, but will still need to communicate with IPv4 nodes that do not have a dual IP layer supporting both IPv4 and IPv6. This specification defines a mechanism called Assignment of IPv4 Global Addresses to IPv6 Hosts (AIIH), which will assign an IPv6 Host a temporary IPv4 Global Address, which can be used to communicate with a Host that supports IPv4 or IPv4/IPv6. An objective of this specification is to avoid the use of address translation for the deployment of IPv6 in a network. Another objective is to demonstrate that IPv6 Addresses can be deployed now instead of non-Global IPv4 Addresses within an Intranet. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-assgn-ipv4-addrs-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-assgn-ipv4-addrs-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-assgn-ipv4-addrs-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980303085046.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-assgn-ipv4-addrs-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-assgn-ipv4-addrs-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980303085046.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Mon Mar 9 12:57:50 1998 Delivery-Date: Mon, 09 Mar 1998 13:02:02 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id MAA04058 for ietf-123-outbound.10@ietf.org; Mon, 9 Mar 1998 12:55:03 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id KAA26183; Mon, 9 Mar 1998 10:44:40 -0500 (EST) Message-Id: <199803091544.KAA26183@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-natpt-01.txt Date: Mon, 09 Mar 1998 10:44:39 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : Network Address Translation - Protocol Translation (NAT-PT] Author(s) : P. Srisuresh, G. Tsirtsis Filename : draft-ietf-ngtrans-natpt-01.txt Pages : 22 Date : 06-Mar-98 This document specifies a transition mechanism in addition to those already specified in RFC 1933. The new mechanism provides an end-to-end solution to allow IPv6-only hosts to communicate with IPv4-only hosts and vice versa using Network Address Translation and Protocol Translation. The scheme described does not require du- al-stack hosts; nor does it mandate any routing related changes on the hosts. The scheme is based on a combination of address transla- tion theme as described in [NAT] and V6/V4 protocol translation theme as described in [SIIT]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-natpt-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-natpt-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-natpt-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980306140439.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-natpt-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-natpt-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980306140439.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Mon Apr 27 10:36:31 1998 Delivery-Date: Mon, 27 Apr 1998 10:46:33 -0400 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.5/8.8.7a) id KAA28290 for ietf-123-outbound.10@ietf.org; Mon, 27 Apr 1998 10:35:02 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id KAA27075; Mon, 27 Apr 1998 10:13:30 -0400 (EDT) Message-Id: <199804271413.KAA27075@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-6bone-routing-issues-02.txt Date: Mon, 27 Apr 1998 10:13:30 -0400 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : IPv6 routing issues Author(s) : A. Durand, B. Buclin Filename : draft-ietf-ngtrans-6bone-routing-issues-02.txt Pages : 4 Date : 24-Apr-98 Operation of the 6bone backbone is a challenge due to the frequent insertion of bogus routes by leaf or even backbone sites. This memo identifies some pathological cases and gives some guidelines on how 6bone sites should handle them. It defines the 'best current practice' acceptable in the 6bone for the config- uration of both Interior Gateway Protocols (like RIPng) and Exterior Gateway Protocols (like BGP4+). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-6bone-routing-issues-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980424171544.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-issues-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-6bone-routing-issues-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980424171544.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Thu May 28 10:38:38 1998 Delivery-Date: Thu, 28 May 1998 10:48:52 -0400 Return-Path: adm Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id KAA00049 for ietf-123-outbound.10@ietf.org; Thu, 28 May 1998 10:35:01 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA29749; Thu, 28 May 1998 10:27:49 -0400 (EDT) Message-Id: <199805281427.KAA29749@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ngtrans@sunroof.eng.sun.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ngtrans-6bone-routing-01.txt Date: Thu, 28 May 1998 10:27:49 -0400 Sender: cclark@CNRI.RESTON.VA.US --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Generation Transition Working Group of the IETF. Title : 6Bone Routing Practice Author(s) : A. Durand, B. Buclin Filename : draft-ietf-ngtrans-6bone-routing-01.txt Pages : 4 Date : 27-May-98 The 6Bone is an environment supporting experimentation with the IPv6 protocols and products implementing it. As the network grows, the need for common operation rules emerged. In particular, operation of the 6Bone backbone is a challenge due to the frequent insertion of bogus routes by leaf or even backbone sites. This memo identifies guidelines on how 6Bone sites might operate, so that the 6Bone can remain a quality experimentation environment and to avoid pathological situations that have been encountered in the past. It defines the 'best current practice' acceptable in the 6Bone for the configuration of both Interior Gateway Protocols (such as RIPng [RFC 2080]) and Exterior Gateway Protocols (like BGP4+ [RFC 2283]). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ngtrans-6bone-routing-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-6bone-routing-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980527135514.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-6bone-routing-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ngtrans-6bone-routing-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980527135514.I-D@ietf.org> --OtherAccess-- --NextPart--