From rfc-editor at rfc-editor.org Tue Apr 1 09:58:08 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 1 Apr 2008 09:58:08 -0700 (PDT) Subject: [rfc-dist] RFC 5242 on A Generalized Unified Character Code: Western European and CJK Sections Message-ID: <20080401165808.16F38121FAE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5242 Title: A Generalized Unified Character Code: Western European and CJK Sections Author: J. Klensin, H. Alvestrand Status: Informational Date: 1 April 2008 Mailbox: john+ietf at jck.com, harald at alvestrand.no Pages: 14 Characters: 31314 Updates/Obsoletes/SeeAlso: None URL: http://www.rfc-editor.org/rfc/rfc5242.txt Many issues have been identified with the use of general-purpose character sets for internationalized domain names and similar purposes. This memo describes a fully unified coded character set for scripts based on Latin, Greek, Cyrillic, and Chinese (CJK) characters. It is not a complete specification of that character set. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Tue Apr 1 09:58:02 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 1 Apr 2008 09:58:02 -0700 (PDT) Subject: [rfc-dist] RFC 5241 on Naming Rights in IETF Protocols Message-ID: <20080401165802.6602C121FAC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5241 Title: Naming Rights in IETF Protocols Author: A. Falk, S. Bradner Status: Informational Date: 1 April 2008 Mailbox: falk at bbn.com, sob at harvard.edu Pages: 12 Characters: 25304 Updates/Obsoletes/SeeAlso: None URL: http://www.rfc-editor.org/rfc/rfc5241.txt This document proposes a new revenue source for the IETF to support standardization activities: protocol field naming rights, i.e., the association of commercial brands with protocol fields. This memo describes a process for assignment of rights and explores some of the issues associated with the process. Individuals or organizations that wish to purchase naming rights for one or more protocol fields are expected to follow this process. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-ed at ISI.EDU Tue Apr 1 21:18:57 2008 From: rfc-ed at ISI.EDU (rfc-ed) Date: Wed, 02 Apr 2008 06:18:57 +0200 Subject: [rfc-dist] ¿ La inflació n y los cursos de las divisas afectan sus economí as? Sabemos como luchar contra eso. Message-ID: <01cc01c89470$49b05500$4d437b59@speedtouch.lan> qypkb -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.rfc-editor.org/pipermail/rfc-dist/attachments/20080402/b1059d0e/attachment.html From rfc-editor at rfc-editor.org Wed Apr 2 16:29:57 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 2 Apr 2008 16:29:57 -0700 (PDT) Subject: [rfc-dist] RFC 5156 on Special-Use IPv6 Addresses Message-ID: <20080402232957.68A0812232C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5156 Title: Special-Use IPv6 Addresses Author: M. Blanchet Status: Informational Date: April 2008 Mailbox: Marc.Blanchet at viagenie.ca Pages: 7 Characters: 11931 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-rfc3330-for-ipv6-04.txt URL: http://www.rfc-editor.org/rfc/rfc5156.txt This document is a compilation of special IPv6 addresses defined in other RFCs. It can be used as a checklist of invalid routing prefixes for developing filtering policies for routes and IP packets. It does not discuss addresses that are assigned to operators and users through the Regional Internet Registries. This memo provides information for the Internet community. This document is a product of the IPv6 Operations Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Apr 9 14:46:19 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 9 Apr 2008 14:46:19 -0700 (PDT) Subject: [rfc-dist] RFC 5147 on URI Fragment Identifiers for the text/plain Media Type Message-ID: <20080409214619.B9C9012368B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5147 Title: URI Fragment Identifiers for the text/plain Media Type Author: E. Wilde, M. Duerst Status: Standards Track Date: April 2008 Mailbox: dret at berkeley.edu, duerst at it.aoyama.ac.jp Pages: 17 Characters: 37422 Updates: RFC2046 I-D Tag: draft-wilde-text-fragment-09.txt URL: http://www.rfc-editor.org/rfc/rfc5147.txt This memo defines URI fragment identifiers for text/plain MIME entities. These fragment identifiers make it possible to refer to parts of a text/plain MIME entity, either identified by character position or range, or by line position or range. Fragment identifiers may also contain information for integrity checks to make them more robust. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Apr 9 14:46:26 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 9 Apr 2008 14:46:26 -0700 (PDT) Subject: [rfc-dist] RFC 5154 on IP over IEEE 802.16 Problem Statement and Goals Message-ID: <20080409214626.3342912368D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5154 Title: IP over IEEE 802.16 Problem Statement and Goals Author: J. Jee, Ed., S. Madanapalli, J. Mandin Status: Informational Date: April 2008 Mailbox: jhjee at etri.re.kr, smadanapalli at gmail.com, j_mandin at yahoo.com Pages: 14 Characters: 29853 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-16ng-ps-goals-04.txt URL: http://www.rfc-editor.org/rfc/rfc5154.txt This document specifies problems in running IP over IEEE 802.16 networks by identifying specific gaps in the IEEE 802.16 Media Access Control (MAC) for IPv4 and IPv6 support. This document also provides an overview of IEEE 802.16 network characteristics and convergence sublayers. Common terminology used for the base guideline while defining the solution framework is also presented. This memo provides information for the Internet community. This document is a product of the IP over IEEE 802.16 Networks Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 11 15:24:39 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 11 Apr 2008 15:24:39 -0700 (PDT) Subject: [rfc-dist] RFC 5165 on A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC) Message-ID: <20080411222439.07A55123B20@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5165 Title: A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC) Author: C. Reed Status: Informational Date: April 2008 Mailbox: creed at opengeospatial.org Pages: 7 Characters: 14681 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-creed-ogc-urn-03.txt URL: http://www.rfc-editor.org/rfc/rfc5165.txt This document describes a Uniform Resource Name (URN) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace IDentifier (NID) is "ogc". This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:03:04 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:03:04 -0700 (PDT) Subject: [rfc-dist] RFC 5153 on IPFIX Implementation Guidelines Message-ID: <20080418230304.52B83124F63@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5153 Title: IPFIX Implementation Guidelines Author: E. Boschi, L. Mark, J. Quittek, M. Stiemerling, P. Aitken Status: Informational Date: April 2008 Mailbox: elisa.boschi at hitachi-eu.com, lutz.mark at fokus.fraunhofer.de, quittek at nw.neclab.eu, stiemerling at nw.neclab.eu, paitken at cisco.com Pages: 35 Characters: 82845 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipfix-implementation-guidelines-08.txt URL: http://www.rfc-editor.org/rfc/rfc5153.txt The IP Flow Information Export (IPFIX) protocol defines how IP Flow information can be exported from routers, measurement probes, or other devices. This document provides guidelines for the implementation and use of the IPFIX protocol. Several sets of guidelines address Template management, transport-specific issues, implementation of Exporting and Collecting Processes, and IPFIX implementation on middleboxes (such as firewalls, network address translators, tunnel endpoints, packet classifiers, etc.). This memo provides information for the Internet community. This document is a product of the IP Flow Information Export Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:03:14 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:03:14 -0700 (PDT) Subject: [rfc-dist] RFC 5201 on Host Identity Protocol Message-ID: <20080418230314.A39A8124F65@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5201 Title: Host Identity Protocol Author: R. Moskowitz, P. Nikander, P. Jokela, Ed., T. Henderson Status: Experimental Date: April 2008 Mailbox: rgm at icsalabs.com, pekka.nikander at nomadiclab.com, petri.jokela at nomadiclab.com, thomas.r.henderson at boeing.com Pages: 104 Characters: 240492 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-base-10.txt URL: http://www.rfc-editor.org/rfc/rfc5201.txt This memo specifies the details of the Host Identity Protocol (HIP). HIP allows consenting hosts to securely establish and maintain shared IP-layer state, allowing separation of the identifier and locator roles of IP addresses, thereby enabling continuity of communications across IP address changes. HIP is based on a Sigma-compliant Diffie- Hellman key exchange, using public key identifiers from a new Host Identity namespace for mutual peer authentication. The protocol is designed to be resistant to denial-of-service (DoS) and man-in-the- middle (MitM) attacks. When used together with another suitable security protocol, such as the Encapsulated Security Payload (ESP), it provides integrity protection and optional encryption for upper- layer protocols, such as TCP and UDP. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:03:37 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:03:37 -0700 (PDT) Subject: [rfc-dist] RFC 5203 on Host Identity Protocol (HIP) Registration Extension Message-ID: <20080418230337.B5FB0124F69@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5203 Title: Host Identity Protocol (HIP) Registration Extension Author: J. Laganier, T. Koponen, L. Eggert Status: Experimental Date: April 2008 Mailbox: julien.ietf at laposte.net, teemu.koponen at iki.fi, lars.eggert at nokia.com Pages: 13 Characters: 26620 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-registration-02.txt URL: http://www.rfc-editor.org/rfc/rfc5203.txt This document specifies a registration mechanism for the Host Identity Protocol (HIP) that allows hosts to register with services, such as HIP rendezvous servers or middleboxes. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:03:28 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:03:28 -0700 (PDT) Subject: [rfc-dist] RFC 5202 on Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) Message-ID: <20080418230328.B2840124F67@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5202 Title: Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) Author: P. Jokela, R. Moskowitz, P. Nikander Status: Experimental Date: April 2008 Mailbox: petri.jokela at nomadiclab.com, rgm at icsalabs.com, pekka.nikander at nomadiclab.com Pages: 30 Characters: 68195 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-esp-06.txt URL: http://www.rfc-editor.org/rfc/rfc5202.txt This memo specifies an Encapsulated Security Payload (ESP) based mechanism for transmission of user data packets, to be used with the Host Identity Protocol (HIP). This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:03:44 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:03:44 -0700 (PDT) Subject: [rfc-dist] RFC 5204 on Host Identity Protocol (HIP) Rendezvous Extension Message-ID: <20080418230344.0E15E124F6B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5204 Title: Host Identity Protocol (HIP) Rendezvous Extension Author: J. Laganier, L. Eggert Status: Experimental Date: April 2008 Mailbox: julien.ietf at laposte.net, lars.eggert at nokia.com Pages: 15 Characters: 30233 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-rvs-05.txt URL: http://www.rfc-editor.org/rfc/rfc5204.txt This document defines a rendezvous extension for the Host Identity Protocol (HIP). The rendezvous extension extends HIP and the HIP registration extension for initiating communication between HIP nodes via HIP rendezvous servers. Rendezvous servers improve reachability and operation when HIP nodes are multi-homed or mobile. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:03:49 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:03:49 -0700 (PDT) Subject: [rfc-dist] RFC 5205 on Host Identity Protocol (HIP) Domain Name System (DNS) Extensions Message-ID: <20080418230349.B18C7124F6D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5205 Title: Host Identity Protocol (HIP) Domain Name System (DNS) Extensions Author: P. Nikander, J. Laganier Status: Experimental Date: April 2008 Mailbox: pekka.nikander at nomadiclab.com, julien.ietf at laposte.net Pages: 17 Characters: 34799 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-dns-09.txt URL: http://www.rfc-editor.org/rfc/rfc5205.txt This document specifies a new resource record (RR) for the Domain Name System (DNS), and how to use it with the Host Identity Protocol (HIP). This RR allows a HIP node to store in the DNS its Host Identity (HI, the public component of the node public-private key pair), Host Identity Tag (HIT, a truncated hash of its public key), and the Domain Names of its rendezvous servers (RVSs). This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:03:56 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:03:56 -0700 (PDT) Subject: [rfc-dist] RFC 5206 on End-Host Mobility and Multihoming with the Host Identity Protocol Message-ID: <20080418230356.E069B124F6F@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5206 Title: End-Host Mobility and Multihoming with the Host Identity Protocol Author: P. Nikander, T. Henderson, Ed., C. Vogt, J. Arkko Status: Experimental Date: April 2008 Mailbox: pekka.nikander at nomadiclab.com, thomas.r.henderson at boeing.com, christian.vogt at ericsson.com, jari.arkko at ericsson.com Pages: 40 Characters: 99430 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-mm-05.txt URL: http://www.rfc-editor.org/rfc/rfc5206.txt This document defines mobility and multihoming extensions to the Host Identity Protocol (HIP). Specifically, this document defines a general "LOCATOR" parameter for HIP messages that allows for a HIP host to notify peers about alternate addresses at which it may be reached. This document also defines elements of procedure for mobility of a HIP host -- the process by which a host dynamically changes the primary locator that it uses to receive packets. While the same LOCATOR parameter can also be used to support end-host multihoming, detailed procedures are left for further study. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Apr 18 16:04:07 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Apr 2008 16:04:07 -0700 (PDT) Subject: [rfc-dist] RFC 5207 on NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication Message-ID: <20080418230407.19A0B124F71@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5207 Title: NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication Author: M. Stiemerling, J. Quittek, L. Eggert Status: Informational Date: April 2008 Mailbox: stiemerling at netlab.nec.de, quittek at nw.neclab.eu, lars.eggert at nokia.com Pages: 13 Characters: 27873 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-hiprg-nat-04.txt URL: http://www.rfc-editor.org/rfc/rfc5207.txt The Host Identity Protocol (HIP) changes the way in which two Internet hosts communicate. One key advantage over other schemes is that HIP does not require modifications to the traditional network- layer functionality of the Internet, i.e., its routers. In the current Internet, however, many devices other than routers modify the traditional network-layer behavior of the Internet. These "middleboxes" are intermediary devices that perform functions other than the standard functions of an IP router on the datagram path between source and destination hosts. Whereas some types of middleboxes may not interfere with HIP at all, others can affect some aspects of HIP communication, and others can render HIP communication impossible. This document discusses the problems associated with HIP communication across network paths that include specific types of middleboxes, namely, network address translators and firewalls. It identifies and discusses issues in the current HIP specifications that affect communication across these types of middleboxes. This document is a product of the IRTF HIP Research Group. This memo provides information for the Internet community. This document is a product of the IRTF Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Apr 23 16:47:19 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 23 Apr 2008 16:47:19 -0700 (PDT) Subject: [rfc-dist] RFC 5171 on Cisco Systems UniDirectional Link Detection (UDLD) Protocol Message-ID: <20080423234719.C839C125D12@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5171 Title: Cisco Systems UniDirectional Link Detection (UDLD) Protocol Author: M. Foschiano Status: Informational Date: April 2008 Mailbox: foschia at cisco.com Pages: 13 Characters: 28149 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-foschiano-udld-03.txt URL: http://www.rfc-editor.org/rfc/rfc5171.txt This document describes a Cisco Systems protocol that can be used to detect and disable unidirectional Ethernet fiber or copper links caused, for instance, by mis-wiring of fiber strands, interface malfunctions, media converters' faults, etc. It operates at Layer 2 in conjunction with IEEE 802.3's existing Layer 1 fault detection mechanisms. This document explains the protocol objectives and applications, illustrates the specific premises the protocol was based upon, and describes the protocol architecture and related deployment issues to serve as a possible base for future standardization. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Apr 23 16:47:17 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 23 Apr 2008 16:47:17 -0700 (PDT) Subject: [rfc-dist] RFC 5163 on Extension Formats for Unidirectional Lightweight Encapsulation (ULE) and the Generic Stream Encapsulation (GSE) Message-ID: <20080423234717.817DF125D10@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5163 Title: Extension Formats for Unidirectional Lightweight Encapsulation (ULE) and the Generic Stream Encapsulation (GSE) Author: G. Fairhurst, B. Collini-Nocker Status: Standards Track Date: April 2008 Mailbox: gorry at erg.abdn.ac.uk, bnocker at cosy.sbg.ac.at Pages: 18 Characters: 42935 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipdvb-ule-ext-07.txt URL: http://www.rfc-editor.org/rfc/rfc5163.txt This document describes a set of Extension Headers for the Unidirectional Lightweight Encapsulation (ULE), RFC 4326. The Extension Header formats specified in this document define extensions appropriate to both ULE and the Generic Stream Encapsulation (GSE) for the second-generation framing structure defined by the Digital Video Broadcasting (DVB) family of specifications. [STANDARDS TRACK] This document is a product of the IP over DVB Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Apr 23 16:47:21 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 23 Apr 2008 16:47:21 -0700 (PDT) Subject: [rfc-dist] RFC 5177 on Network Mobility (NEMO) Extensions for Mobile IPv4 Message-ID: <20080423234721.5C847125D14@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5177 Title: Network Mobility (NEMO) Extensions for Mobile IPv4 Author: K. Leung, G. Dommety, V. Narayanan, A. Petrescu Status: Standards Track Date: April 2008 Mailbox: kleung at cisco.com, gdommety at cisco.com, vidyan at qualcomm.com, alexandru.petrescu at motorola.com Pages: 26 Characters: 56094 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip4-nemo-v4-base-11.txt URL: http://www.rfc-editor.org/rfc/rfc5177.txt This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the Mobile Network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. [STANDARDS TRACK] This document is a product of the Mobility for IPv4 Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-ed at ISI.EDU Sun Apr 27 13:57:22 2008 From: rfc-ed at ISI.EDU (rfc-ed) Date: Sun, 27 Apr 2008 22:57:22 +0200 Subject: [rfc-dist] Me dirijo a Vd. con una oferta de labor ventajosa en mi compañ í a. Message-ID: <009801c8a8a0$e8644be0$77c3f458@dsl88.24253088.ttnet.net.tr> dyhg -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.rfc-editor.org/pipermail/rfc-dist/attachments/20080427/636f2265/attachment.html From rfc-editor at rfc-editor.org Tue Apr 29 17:25:04 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 29 Apr 2008 17:25:04 -0700 (PDT) Subject: [rfc-dist] RFC 5225 on RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite Message-ID: <20080430002504.2451C127B82@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5225 Title: RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite Author: G. Pelletier, K. Sandlund Status: Standards Track Date: April 2008 Mailbox: ghyslain.pelletier at ericsson.com, kristofer.sandlund at ericsson.com Pages: 124 Characters: 246120 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rohc-rfc3095bis-rohcv2-profiles-06.txt URL: http://www.rfc-editor.org/rfc/rfc5225.txt This document specifies ROHC (Robust Header Compression) profiles that efficiently compress RTP/UDP/IP (Real-Time Transport Protocol, User Datagram Protocol, Internet Protocol), RTP/UDP-Lite/IP (User Datagram Protocol Lite), UDP/IP, UDP-Lite/IP, IP and ESP/IP (Encapsulating Security Payload) headers. This specification defines a second version of the profiles found in RFC 3095, RFC 3843 and RFC 4019; it supersedes their definition, but does not obsolete them. The ROHCv2 profiles introduce a number of simplifications to the rules and algorithms that govern the behavior of the compression endpoints. It also defines robustness mechanisms that may be used by a compressor implementation to increase the probability of decompression success when packets can be lost and/or reordered on the ROHC channel. Finally, the ROHCv2 profiles define their own specific set of header formats, using the ROHC formal notation. [STANDARDS TRACK] This document is a product of the Robust Header Compression Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Apr 30 18:17:17 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 30 Apr 2008 18:17:17 -0700 (PDT) Subject: [rfc-dist] RFC 5173 on Sieve Email Filtering: Body Extension Message-ID: <20080501011717.B7109127EE2@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5173 Title: Sieve Email Filtering: Body Extension Author: J. Degener, P. Guenther Status: Standards Track Date: April 2008 Mailbox: jutta at pobox.com, guenther at sendmail.com Pages: 10 Characters: 17429 Updates: RFC5229 I-D Tag: draft-ietf-sieve-body-09.txt URL: http://www.rfc-editor.org/rfc/rfc5173.txt This document defines a new command for the "Sieve" email filtering language that tests for the occurrence of one or more strings in the body of an email message. [STANDARDS TRACK] This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ...