From mailman-admin@ietf.org Sat Feb 1 10:16:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07833 for ; Sat, 1 Feb 2003 10:16:37 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11FKdJ03830 for ; Sat, 1 Feb 2003 10:20:39 -0500 Date: Sat, 01 Feb 2003 10:20:39 -0500 Message-ID: <20030201152039.8821.38659.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: agentx-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, agentx-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for agentx-archive@lists.ietf.org: List Password // URL ---- -------- agentx@ietf.org atabhu https://www1.ietf.org/mailman/options/agentx/agentx-archive%40lists.ietf.org From agentx-admin@ietf.org Wed Feb 19 15:25:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07766 for ; Wed, 19 Feb 2003 15:25:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKVRp07770; Wed, 19 Feb 2003 15:31:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKTep07723 for ; Wed, 19 Feb 2003 15:29:40 -0500 Received: from swan.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07623 for ; Wed, 19 Feb 2003 15:22:55 -0500 (EST) Received: from h-69-3-244-38.snvacaid.covad.net ([69.3.244.38] helo=oemcomputer) by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 18lani-0004Yk-00; Wed, 19 Feb 2003 12:26:42 -0800 Message-ID: <01cc01c2d855$d503a1c0$7f1afea9@oemcomputer> From: "Randy Presuhn" To: Cc: X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [Agentx] AgentX and draft-ietf-v6ops-ipv4survey-ops-00.txt Sender: agentx-admin@ietf.org Errors-To: agentx-admin@ietf.org X-BeenThere: agentx@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: SNMP Agent Extensibility List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 19 Feb 2003 12:31:07 -0800 Hi - The analysis of AgentX protocol in this I-D is incorrect. The ability to represent an IPv4-specific data type is necessary to the protocol's operation, and has no bearing whatsover on its ability to represent IPv6 addresses or operate in IPv6 environments. Section 5.091 should be replaced with "There are no IPv4 dependencies in this protocol." Section 7.3.26 should state that there are no issues. Randy > From: > To: > Cc: > Sent: Wednesday, February 19, 2003 4:11 AM > Subject: I-D ACTION:draft-ietf-v6ops-ipv4survey-ops-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the IPv6 Operations Working Group of the IETF. > > Title : Survey of IPv4 Addresses in Currently Deployed IETF > Operations & Management Area Standards > Author(s) : P. Nesser II > Filename : draft-ietf-v6ops-ipv4survey-ops-00.txt > Pages : 0 > Date : 2003-2-14 > > This document seeks to document all usage of IPv4 addresses in currently > deployed IETF Operations & Management Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-ipv4survey-ops-00.txt > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body of the message. > > Internet-Drafts are also 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-v6ops-ipv4survey-ops-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-v6ops-ipv4survey-ops-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. > From mailnull@www1.ietf.org Wed Feb 19 15:25:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07789 for ; Wed, 19 Feb 2003 15:25:57 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JKWBr07805 for agentx-archive@odin.ietf.org; Wed, 19 Feb 2003 15:32:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKWBp07802 for ; Wed, 19 Feb 2003 15:32:11 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07780 for ; Wed, 19 Feb 2003 15:25:26 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKVRp07770; Wed, 19 Feb 2003 15:31:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKTep07723 for ; Wed, 19 Feb 2003 15:29:40 -0500 Received: from swan.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07623 for ; Wed, 19 Feb 2003 15:22:55 -0500 (EST) Received: from h-69-3-244-38.snvacaid.covad.net ([69.3.244.38] helo=oemcomputer) by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 18lani-0004Yk-00; Wed, 19 Feb 2003 12:26:42 -0800 Message-ID: <01cc01c2d855$d503a1c0$7f1afea9@oemcomputer> From: "Randy Presuhn" To: Cc: X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [Agentx] AgentX and draft-ietf-v6ops-ipv4survey-ops-00.txt Sender: agentx-admin@ietf.org Errors-To: agentx-admin@ietf.org X-BeenThere: agentx@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: SNMP Agent Extensibility List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 19 Feb 2003 12:31:07 -0800 Hi - The analysis of AgentX protocol in this I-D is incorrect. The ability to represent an IPv4-specific data type is necessary to the protocol's operation, and has no bearing whatsover on its ability to represent IPv6 addresses or operate in IPv6 environments. Section 5.091 should be replaced with "There are no IPv4 dependencies in this protocol." Section 7.3.26 should state that there are no issues. Randy > From: > To: > Cc: > Sent: Wednesday, February 19, 2003 4:11 AM > Subject: I-D ACTION:draft-ietf-v6ops-ipv4survey-ops-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the IPv6 Operations Working Group of the IETF. > > Title : Survey of IPv4 Addresses in Currently Deployed IETF > Operations & Management Area Standards > Author(s) : P. Nesser II > Filename : draft-ietf-v6ops-ipv4survey-ops-00.txt > Pages : 0 > Date : 2003-2-14 > > This document seeks to document all usage of IPv4 addresses in currently > deployed IETF Operations & Management Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-ipv4survey-ops-00.txt > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body of the message. > > Internet-Drafts are also 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-v6ops-ipv4survey-ops-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-v6ops-ipv4survey-ops-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. > From agentx-admin@ietf.org Thu Feb 20 15:16:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28076 for ; Thu, 20 Feb 2003 15:16:52 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KKNUp12281; Thu, 20 Feb 2003 15:23:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JMJ9p14944 for ; Wed, 19 Feb 2003 17:19:09 -0500 Received: from arda.Nesser.COM (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10903 for ; Wed, 19 Feb 2003 17:12:20 -0500 (EST) Received: from A30P ([192.104.59.191]) by arda.Nesser.COM (8.12.6/8.12.6) with ESMTP id h1JMWPao024913; Wed, 19 Feb 2003 14:32:25 -0800 (PST) Reply-To: From: "Philip J. Nesser II" To: "'Randy Presuhn'" , Organization: Nesser & Nesser Consulting Message-ID: <071301c2d864$81b77b90$bf3b68c0@A30P> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-reply-to: <01cc01c2d855$d503a1c0$7f1afea9@oemcomputer> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [Agentx] RE: AgentX and draft-ietf-v6ops-ipv4survey-ops-00.txt Sender: agentx-admin@ietf.org Errors-To: agentx-admin@ietf.org X-BeenThere: agentx@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: SNMP Agent Extensibility List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 19 Feb 2003 14:16:10 -0800 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randy, Thanks. I will make updates in the -01 version. The whole goal is to solicit input from the people who have a much more intimate knowledge of individual protocols than I do. It has been a daunting task and it is hard to fit everything together when you are trying to digest 900 or so protocol documents. I really appreciate your time to read through the document and make your comments. I am currently taking input from (hopefully) a lot of independent sources and putting then all together. - ---> Phil > -----Original Message----- > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com] > Sent: Wednesday, February 19, 2003 12:31 PM > To: agentx@ietf.org > Cc: phil@nesser.com > Subject: AgentX and draft-ietf-v6ops-ipv4survey-ops-00.txt > > Hi - > > The analysis of AgentX protocol in this I-D is incorrect. > The ability to represent an IPv4-specific data type is necessary > to the protocol's operation, and has no bearing whatsover on > its ability to represent IPv6 addresses or operate in IPv6 > environments. > > Section 5.091 should be replaced with "There are no IPv4 > dependencies in this protocol." Section 7.3.26 should state that > there are no issues. > > Randy > > > From: > > To: > > Cc: > > Sent: Wednesday, February 19, 2003 4:11 AM > > Subject: I-D ACTION:draft-ietf-v6ops-ipv4survey-ops-00.txt > > > > > A New Internet-Draft is available from the on-line > > Internet-Drafts > directories. > > This draft is a work item of the IPv6 Operations Working Group of > > the > IETF. > > > > Title : Survey of IPv4 Addresses in Currently Deployed IETF > > Operations & Management Area Standards > > Author(s) : P. Nesser II > > Filename : draft-ietf-v6ops-ipv4survey-ops-00.txt > > Pages : 0 > > Date : 2003-2-14 > > > > This document seeks to document all usage of IPv4 addresses in > > currently deployed IETF Operations & Management Area documented > > standards. In > order to successfully transition from an all IPv4 Internet to > an all IPv6 Internet, many interim steps will be taken. One of > these steps is the evolution of current protocols that have IPv4 > dependencies. It is hoped that these protocols (and their > implementations) will be redesigned to be network address > independent, but failing that will at least dually support IPv4 and > IPv6. To this end, all Standards (Full, Draft, and Proposed) as > well as > Experimental RFCs will be surveyed and any dependencies will be > documented. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-ipv4survey-op > > s- > 00.txt > > > > To remove yourself from the IETF Announcement list, send a > > message to ietf-announce-request with the word unsubscribe in the > > body of the > message. > > > > Internet-Drafts are also 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-v6ops-ipv4survey-ops-00.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-v6ops-ipv4survey-ops-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. > > -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use iQA/AwUBPlQCKg6aViIxlRuuEQL8qgCg4FtKe+38Y/r8/8us6Fl8yJI85aEAoOJb +DyLh8jdNyVY+BlEZfAq4OEy =b6K/ -----END PGP SIGNATURE----- From mailnull@www1.ietf.org Thu Feb 20 15:17:26 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28094 for ; Thu, 20 Feb 2003 15:17:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KKO9c12330 for agentx-archive@odin.ietf.org; Thu, 20 Feb 2003 15:24:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KKO9p12327 for ; Thu, 20 Feb 2003 15:24:09 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28090 for ; Thu, 20 Feb 2003 15:16:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KKNUp12281; Thu, 20 Feb 2003 15:23:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JMJ9p14944 for ; Wed, 19 Feb 2003 17:19:09 -0500 Received: from arda.Nesser.COM (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10903 for ; Wed, 19 Feb 2003 17:12:20 -0500 (EST) Received: from A30P ([192.104.59.191]) by arda.Nesser.COM (8.12.6/8.12.6) with ESMTP id h1JMWPao024913; Wed, 19 Feb 2003 14:32:25 -0800 (PST) Reply-To: From: "Philip J. Nesser II" To: "'Randy Presuhn'" , Organization: Nesser & Nesser Consulting Message-ID: <071301c2d864$81b77b90$bf3b68c0@A30P> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-reply-to: <01cc01c2d855$d503a1c0$7f1afea9@oemcomputer> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [Agentx] RE: AgentX and draft-ietf-v6ops-ipv4survey-ops-00.txt Sender: agentx-admin@ietf.org Errors-To: agentx-admin@ietf.org X-BeenThere: agentx@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: SNMP Agent Extensibility List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 19 Feb 2003 14:16:10 -0800 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randy, Thanks. I will make updates in the -01 version. The whole goal is to solicit input from the people who have a much more intimate knowledge of individual protocols than I do. It has been a daunting task and it is hard to fit everything together when you are trying to digest 900 or so protocol documents. I really appreciate your time to read through the document and make your comments. I am currently taking input from (hopefully) a lot of independent sources and putting then all together. - ---> Phil > -----Original Message----- > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com] > Sent: Wednesday, February 19, 2003 12:31 PM > To: agentx@ietf.org > Cc: phil@nesser.com > Subject: AgentX and draft-ietf-v6ops-ipv4survey-ops-00.txt > > Hi - > > The analysis of AgentX protocol in this I-D is incorrect. > The ability to represent an IPv4-specific data type is necessary > to the protocol's operation, and has no bearing whatsover on > its ability to represent IPv6 addresses or operate in IPv6 > environments. > > Section 5.091 should be replaced with "There are no IPv4 > dependencies in this protocol." Section 7.3.26 should state that > there are no issues. > > Randy > > > From: > > To: > > Cc: > > Sent: Wednesday, February 19, 2003 4:11 AM > > Subject: I-D ACTION:draft-ietf-v6ops-ipv4survey-ops-00.txt > > > > > A New Internet-Draft is available from the on-line > > Internet-Drafts > directories. > > This draft is a work item of the IPv6 Operations Working Group of > > the > IETF. > > > > Title : Survey of IPv4 Addresses in Currently Deployed IETF > > Operations & Management Area Standards > > Author(s) : P. Nesser II > > Filename : draft-ietf-v6ops-ipv4survey-ops-00.txt > > Pages : 0 > > Date : 2003-2-14 > > > > This document seeks to document all usage of IPv4 addresses in > > currently deployed IETF Operations & Management Area documented > > standards. In > order to successfully transition from an all IPv4 Internet to > an all IPv6 Internet, many interim steps will be taken. One of > these steps is the evolution of current protocols that have IPv4 > dependencies. It is hoped that these protocols (and their > implementations) will be redesigned to be network address > independent, but failing that will at least dually support IPv4 and > IPv6. To this end, all Standards (Full, Draft, and Proposed) as > well as > Experimental RFCs will be surveyed and any dependencies will be > documented. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-ipv4survey-op > > s- > 00.txt > > > > To remove yourself from the IETF Announcement list, send a > > message to ietf-announce-request with the word unsubscribe in the > > body of the > message. > > > > Internet-Drafts are also 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-v6ops-ipv4survey-ops-00.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-v6ops-ipv4survey-ops-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. > > -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use iQA/AwUBPlQCKg6aViIxlRuuEQL8qgCg4FtKe+38Y/r8/8us6Fl8yJI85aEAoOJb +DyLh8jdNyVY+BlEZfAq4OEy =b6K/ -----END PGP SIGNATURE-----