From falk@ISI.EDU Tue May 7 09:23:35 2002 Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g47GNZF24863 for ; Tue, 7 May 2002 09:23:35 -0700 (PDT) Date: Tue, 07 May 2002 09:23:35 -0700 From: Aaron Falk To: rfc-dist@rfc-editor.org Message-ID: <3650000.1020788615@nit.isi.edu> X-Mailer: Mulberry/2.2.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [rfc-dist] test -- please ignore Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: test From falk@ISI.EDU Tue May 7 09:28:31 2002 Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g47GSVF28691 for ; Tue, 7 May 2002 09:28:31 -0700 (PDT) Date: Tue, 07 May 2002 09:28:31 -0700 From: Aaron Falk To: rfc-dist@rfc-editor.org Message-ID: <4690000.1020788911@nit.isi.edu> X-Mailer: Mulberry/2.2.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [rfc-dist] another test -- please ignore Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: test From falk@ISI.EDU Tue May 7 10:32:11 2002 Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g47HWAF13873 for ; Tue, 7 May 2002 10:32:10 -0700 (PDT) Date: Tue, 07 May 2002 10:32:10 -0700 From: Aaron Falk To: rfc-dist@rfc-editor.org Message-ID: <6180000.1020792730@nit.isi.edu> X-Mailer: Mulberry/2.2.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [rfc-dist] test -- please ignore Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: test From rfc-ed@ISI.EDU Thu May 9 09:16:53 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g49GGrF07054; Thu, 9 May 2002 09:16:53 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g49GGrm02146; Thu, 9 May 2002 09:16:53 -0700 (PDT) Message-Id: <200205091616.g49GGrm02146@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 09 May 2002 09:16:53 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3241 on ROHC over PPP Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3241 Title: Robust Header Compression (ROHC) over PPP Author(s): C. Bormann Status: Standards Track Date: April 2002 Mailbox: cabo@tzi.org Pages: 12 Characters: 24424 Updates: 1332 I-D Tag: draft-ietf-rohc-over-ppp-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3241.txt This document describes an option for negotiating the use of robust header compression (ROHC) on IP datagrams transmitted over the Point-to-Point Protocol (PPP). It defines extensions to the PPP Control Protocols for IPv4 and IPv6. This document is a product of the Robust Header Compression Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020509091413.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3241 --OtherAccess Content-Type: Message/External-body; name="rfc3241.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020509091413.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu May 9 16:33:06 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g49NX6F15598; Thu, 9 May 2002 16:33:06 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g49NX6m17320; Thu, 9 May 2002 16:33:06 -0700 (PDT) Message-Id: <200205092333.g49NX6m17320@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 09 May 2002 16:33:06 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3269 on RMT Author Guidelines Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3269 Title: Author Guidelines for Reliable Multicast Transport (RMT) Building Blocks and Protocol Instantiation documents Author(s): R. Kermode, L. Vicisano Status: Informational Date: April 2002 Mailbox: Roger.Kermode@motorola.com, lorenzo@cisco.com Pages: 12 Characters: 25258 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmt-author-guidelines-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3269.txt This document provides general guidelines to assist the authors of Reliable Multicast Transport (RMT) building block and protocol instantiation definitions. The purpose of these guidelines is to ensure that any building block and protocol instantiation definitions produced contain sufficient information to fully explain their operation and use. In addition these guidelines provide directions to specify modular and clearly defined RMT building blocks and protocol instantiations that can be refined and augmented to safely create new protocols for use in new scenarios for which any existing protocols were not designed. This document is a product of the Reliable Multicast Transport Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020509163118.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3269 --OtherAccess Content-Type: Message/External-body; name="rfc3269.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020509163118.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri May 10 16:58:11 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4ANwBF19131; Fri, 10 May 2002 16:58:11 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4ANwBm08409; Fri, 10 May 2002 16:58:11 -0700 (PDT) Message-Id: <200205102358.g4ANwBm08409@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 10 May 2002 16:58:11 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3278 on Use of ECC Algorithms in CMS Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3278 Title: Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) Author(s): S. Blake-Wilson, D. Brown, P. Lambert Status: Informational Date: April 2002 Mailbox: sblakewi@certicom.com, dbrown@certicom.com, plambert@sprintmail.com Pages: 16 Characters: 33779 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-ecc-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3278.txt This document describes how to use Elliptic Curve Cryptography (ECC) public-key algorithms in the Cryptographic Message Syntax (CMS). The ECC algorithms support the creation of digital signatures and the exchange of keys to encrypt or authenticate content. The definition of the algorithm processing is based on the ANSI X9.62 standard, developed by the ANSI X9F1 working group, the IEEE 1363 standard, and the SEC 1 standard. The readers attention is called to the Intellectual Property Rights section at the end of this document. This document is a product of the S/MIME Mail Security Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020510164433.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3278 --OtherAccess Content-Type: Message/External-body; name="rfc3278.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020510164433.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri May 10 17:00:44 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4B00iF21490; Fri, 10 May 2002 17:00:44 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4B00im09581; Fri, 10 May 2002 17:00:44 -0700 (PDT) Message-Id: <200205110000.g4B00im09581@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 10 May 2002 17:00:43 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3279 on Algorithms and Identifiers Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3279 Title: Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Author(s): L. Bassham, W. Polk, R. Housley Status: Standards Track Date: April 2002 Mailbox: lbassham@nist.gov, rhousley@rsasecurity.com, tim.polk@nist.gov Pages: 26 Characters: 53833 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-ipki-pkalgs-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3279.txt This document specifies algorithm identifiers and ASN.1 encoding formats for digital signatures and subject public keys used in the Internet X.509 Public Key Infrastructure (PKI). Digital signatures are used to sign certificates and certificate revocation list (CRLs). Certificates include the public key of the named subject. This document is a product of the Internet X.509 Public Key Infrastructure (PKIX) Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020510165840.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3279 --OtherAccess Content-Type: Message/External-body; name="rfc3279.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020510165840.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri May 10 17:04:48 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4B04mF25811; Fri, 10 May 2002 17:04:48 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4B04lm10528; Fri, 10 May 2002 17:04:47 -0700 (PDT) Message-Id: <200205110004.g4B04lm10528@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 10 May 2002 17:04:47 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3280 on Internet X.509 Public Key Infrastructure Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3280 Title: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Author(s): R. Housley, W. Polk, W. Ford, D. Solo Status: Standards Track Date: April 2002 Mailbox: rhousley@rsasecurity.com, wford@verisign.com, wpolk@nist.gov, dsolo@alum.mit.edu Pages: 129 Characters: 295556 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-new-part1-12.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3280.txt This memo profiles the X.509 v3 certificate and X.509 v2 Certificate Revocation List (CRL) for use in the Internet. An overview of this approach and model are provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms. Standard certificate extensions are described and two Internet-specific extensions are defined. A set of required certificate extensions is specified. The X.509 v2 CRL format is described in detail, and required extensions are defined. An algorithm for X.509 certification path validation is described. An ASN.1 module and examples are provided in the appendices. This document is a product of the Internet X.509 Public Key Infrastructure (PKIX) Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020510170140.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3280 --OtherAccess Content-Type: Message/External-body; name="rfc3280.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020510170140.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri May 10 17:09:48 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4B09mF29664; Fri, 10 May 2002 17:09:48 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4B09mm12151; Fri, 10 May 2002 17:09:48 -0700 (PDT) Message-Id: <200205110009.g4B09mm12151@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 10 May 2002 17:09:48 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3281 on An Internet Attribute Certificate Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3281 Title: An Internet Attribute Certificate Profile for Authorization Author(s): S. Farrell, R. Housley Status: Standards Track Date: April 2002 Mailbox: stephen.farrell@baltimore.ie, rhousley@rsasecurity.com Pages: 40 Characters: 90580 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-ac509prof-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3281.txt This specification defines a profile for the use of X.509 Attribute Certificates in Internet Protocols. Attribute certificates may be used in a wide range of applications and environments covering a broad spectrum of interoperability goals and a broader spectrum of operational and assurance requirements. The goal of this document is to establish a common baseline for generic applications requiring broad interoperability as well as limited special purpose requirements. The profile places emphasis on attribute certificate support for Internet electronic mail, IPSec, and WWW security applications. This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020510170609.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3281 --OtherAccess Content-Type: Message/External-body; name="rfc3281.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020510170609.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon May 13 12:02:11 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4DJ2BF26942; Mon, 13 May 2002 12:02:11 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4DJ2Bm17170; Mon, 13 May 2002 12:02:11 -0700 (PDT) Message-Id: <200205131902.g4DJ2Bm17170@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 13 May 2002 12:02:10 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3259 on A Message Bus for Local Coordination Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3259 Title: A Message Bus for Local Coordination Author(s): J. Ott, C. Perkins, D. Kutscher Status: Informational Date: April 2002 Mailbox: jo@tzi.uni-bremen.de, csp@isi.edu, dku@tzi.uni-bremen.de Pages: 39 Characters: 84125 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mmusic-mbus-transport-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3259.txt The local Message Bus (Mbus) is a light-weight message-oriented coordination protocol for group communication between application components. The Mbus provides automatic location of communication peers, subject based addressing, reliable message transfer and different types of communication schemes. The protocol is layered on top of IP multicast and is specified for IPv4 and IPv6. The IP multicast scope is limited to link-local multicast. This document specifies the Mbus protocol, i.e., message syntax, addressing and transport mechanisms. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020513120018.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3259 --OtherAccess Content-Type: Message/External-body; name="rfc3259.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020513120018.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri May 17 13:04:10 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4HK4AF19354; Fri, 17 May 2002 13:04:10 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4HK49E13304; Fri, 17 May 2002 13:04:09 -0700 (PDT) Message-Id: <200205172004.g4HK49E13304@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 17 May 2002 13:04:09 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3291 on TCs for Internet Network Addresses Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3291 Title: Textual Conventions for Internet Network Addresses Author(s): M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder Status: Standards Track Date: May 2002 Mailbox: md@world.std.com, bkhabs@nc.rr.com, sar@epilogue.com, schoenw@ibr.cs.tu-bs.de Pages: 20 Characters: 43564 Obsoletes: 2851 I-D Tag: draft-ietf-ops-rfc2851-update-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3291.txt This MIB module defines textual conventions to represent commonly used Internet network layer addressing information. The intent is that these textual conventions (TCs) will be imported and used in MIB modules that would otherwise define their own representations. This document obsoletes RFC 2851. This document is a product of the Operations and Management Open Area Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020517130208.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3291 --OtherAccess Content-Type: Message/External-body; name="rfc3291.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020517130208.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue May 21 10:50:31 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4LHoVe08656; Tue, 21 May 2002 10:50:31 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LHoVE12908; Tue, 21 May 2002 10:50:31 -0700 (PDT) Message-Id: <200205211750.g4LHoVE12908@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 21 May 2002 10:50:31 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3270 on Multi-Protocol Label Switching (MPLS) Support of Differentiated Services Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3270 Title: Multi-Protocol Label Switching (MPLS) Support of Differentiated Services Author(s): F. Le Faucheur, L. Wu, B. Davie, S. Davari, P. Vaananen, R. Krishnan, P. Cheval, J. Heinanen Status: Standards Track Date: May 2002 Mailbox: flefauch@cisco.com, liwwu@cisco.com, bsd@cisco.com, davari@ieee.org, pasi.vaananen@nokia.com, ram@axiowave.com, pierrick.cheval@space.alcatel.fr, jh@song.fi Pages: 64 Characters: 137960 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-diff-ext-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3270.txt This document defines a flexible solution for support of Differentiated Services (Diff-Serv) over Multi-Protocol Label Switching (MPLS) networks. This solution allows the MPLS network administrator to select how Diff-Serv Behavior Aggregates (BAs) are mapped onto Label Switched Paths (LSPs) so that he/she can best match the Diff-Serv, Traffic Engineering and protection objectives within his/her particular network. For instance, this solution allows the network administrator to decide whether different sets of BAs are to be mapped onto the same LSP or mapped onto separate LSPs. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020521104817.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3270 --OtherAccess Content-Type: Message/External-body; name="rfc3270.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020521104817.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue May 21 16:08:31 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4LN8Ue08112; Tue, 21 May 2002 16:08:30 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LN8UE15656; Tue, 21 May 2002 16:08:30 -0700 (PDT) Message-Id: <200205212308.g4LN8UE15656@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 21 May 2002 16:08:30 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3272 on Overview and Principles of Internet Traffic Engineering Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3272 Title: Overview and Principles of Internet Traffic Engineering Author(s): D. Awduche, A. Chiu, A. Elwalid, I. Widjaja, X. Xiao Status: Informational Date: May 2002 Mailbox: awduche@movaz.com, angela.chiu@celion.com, anwar@lucent.com, iwidjaja@research.bell-labs.com, xipeng@redback.com Pages: 71 Characters: 190384 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tewg-principles-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3272.txt This memo describes the principles of Traffic Engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks, and to provide a common basis for the development of traffic engineering capabilities for the Internet. The principles, architectures, and methodologies for performance evaluation and performance optimization of operational IP networks are discussed throughout this document. This document is a product of the Internet Traffic Engineering Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020521160633.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3272 --OtherAccess Content-Type: Message/External-body; name="rfc3272.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020521160633.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed May 22 17:02:01 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4N020e14930; Wed, 22 May 2002 17:02:00 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4N020E28429; Wed, 22 May 2002 17:02:00 -0700 (PDT) Message-Id: <200205230002.g4N020E28429@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 22 May 2002 17:02:00 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3276 on Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3276 Title: Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines Author(s): B. Ray, R. Abbi Status: Standards Track Date: May 2002 Mailbox: rray@pesa.com, Rajesh.Abbi@alcatel.com Pages: 66 Characters: 122991 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-adslmib-hds12-12.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3276.txt This document defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. This document is a product of the ADSL MIB Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020522165825.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3276 --OtherAccess Content-Type: Message/External-body; name="rfc3276.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020522165825.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu May 23 16:09:16 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4NN9Ge01943; Thu, 23 May 2002 16:09:16 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NN9GE16375; Thu, 23 May 2002 16:09:16 -0700 (PDT) Message-Id: <200205232309.g4NN9GE16375@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 23 May 2002 16:09:16 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3114 on Implementing Company Classification Policy Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3114 Title: Implementing Company Classification Policy with the S/MIME Security Label Author(s): W. Nicolls Status: Informational Date: May 2002 Mailbox: wnicolls@forsythesolutions.com Pages: 14 Characters: 27764 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-seclabel-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3114.txt This document discusses how company security policy for data classification can be mapped to the S/MIME security label. Actual policies from three companies provide worked examples. This document is a product of the S/MIME Mail Security Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020523160703.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3114 --OtherAccess Content-Type: Message/External-body; name="rfc3114.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020523160703.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed May 29 11:38:53 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4TIcre04471; Wed, 29 May 2002 11:38:53 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4TIcrE23015; Wed, 29 May 2002 11:38:53 -0700 (PDT) Message-Id: <200205291838.g4TIcrE23015@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 29 May 2002 11:38:52 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3286 on An Introduction to the Stream Control Transmission Protocol (SCTP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3286 Title: An Introduction to the Stream Control Transmission Protocol (SCTP) Author(s): L. Ong, J. Yoakum Status: Informational Date: May 2002 Mailbox: lyong@ciena.com, yoakum@nortelnetworks.com Pages: 10 Characters: 22644 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ong-sigtran-sctpover-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3286.txt This document provides a high level introduction to the capabilities supported by the Stream Control Transmission Protocol (SCTP). It is intended as a guide for potential users of SCTP as a general purpose transport protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020529113753.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3286 --OtherAccess Content-Type: Message/External-body; name="rfc3286.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020529113753.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu May 30 16:10:04 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4UNA4e09120; Thu, 30 May 2002 16:10:04 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4UNA4E08688; Thu, 30 May 2002 16:10:04 -0700 (PDT) Message-Id: <200205302310.g4UNA4E08688@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 30 May 2002 16:10:04 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3282 on Content Language Headers Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3282 Title: Content Language Headers Author(s): H. Alvestrand Status: Standards Track Date: May 2002 Mailbox: Harald@Alvestrand.no Pages: 8 Characters: 14022 Updates: 1766 I-D Tag: draft-alvestrand-content-language-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3282.txt This document defines a "Content-language:" header, for use in cases where one desires to indicate the language of something that has RFC 822-like headers, like MIME body parts or Web documents, and an "Accept-Language:" header for use in cases where one wishes to indicate one's preferences with regard to language. This is now a Draft Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020530160850.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3282 --OtherAccess Content-Type: Message/External-body; name="rfc3282.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020530160850.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu May 30 16:12:25 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g4UNCPe10508; Thu, 30 May 2002 16:12:25 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4UNCOE08909; Thu, 30 May 2002 16:12:24 -0700 (PDT) Message-Id: <200205302312.g4UNCOE08909@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 30 May 2002 16:12:24 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3285 on Using Microsoft Word to create Internet Drafts and RFCs Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3285 Title: Using Microsoft Word to create Internet Drafts and RFCs Author(s): M. Gahrns, T. Hain Status: Informational Date: May 2002 Mailbox: mikega@microsoft.com, ahain@cisco.com Pages: 19 Characters: 34556 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-hain-msword-template-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3285.txt This document describes the steps to configure the Microsoft Word application to produce documents in Internet Draft and RFC format. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020530161110.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3285 --OtherAccess Content-Type: Message/External-body; name="rfc3285.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020530161110.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Jun 7 16:23:23 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g57NNNr26243; Fri, 7 Jun 2002 16:23:23 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g57NNNE13708; Fri, 7 Jun 2002 16:23:23 -0700 (PDT) Message-Id: <200206072323.g57NNNE13708@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 07 Jun 2002 16:23:22 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3289 on Management Information Base for the Differentiated Services Architecture Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3289 Title: Management Information Base for the Differentiated Services Architecture Author(s): F. Baker, K. Chan, A. Smith Status: Standards Track Date: May 2002 Mailbox: fred@cisco.com, khchan@nortelnetworks.com, ah_smith@acm.org Pages: 116 Characters: 239041 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-diffserv-mib-16.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3289.txt This memo describes an SMIv2 (Structure of Management Information version 2) MIB for a device implementing the Differentiated Services Architecture. It may be used both for monitoring and configuration of a router or switch capable of Differentiated Services functionality. This document is a product of the Differentiated Services Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020607162120.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3289 --OtherAccess Content-Type: Message/External-body; name="rfc3289.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020607162120.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Jun 7 16:25:37 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g57NPbr28255; Fri, 7 Jun 2002 16:25:37 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g57NPbE14171; Fri, 7 Jun 2002 16:25:37 -0700 (PDT) Message-Id: <200206072325.g57NPbE14171@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 07 Jun 2002 16:25:36 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3290 on An Informal Management Model for Diffserv Routers Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3290 Title: An Informal Management Model for Diffserv Routers Author(s): Y. Bernet, S. Blake, D. Grossman, A. Smith Status: Informational Date: May 2002 Mailbox: ybernet@msn.com, steven.blake@ericsson.com, dan@dma.isg.mot.com, ah_smith@acm.org Pages: 56 Characters: 129443 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-diffserv-model-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3290.txt This document proposes an informal management model of Differentiated Services (Diffserv) routers for use in their management and configuration. This model defines functional datapath elements (e.g., classifiers, meters, actions, marking, absolute dropping, counting, multiplexing), algorithmic droppers, queues and schedulers. It describes possible configuration parameters for these elements and how they might be interconnected to realize the range of traffic conditioning and per-hop behavior (PHB) functionalities described in the Diffserv Architecture. This document is a product of the Differentiated Services Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020607162401.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3290 --OtherAccess Content-Type: Message/External-body; name="rfc3290.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020607162401.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Jun 11 14:18:53 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g5BLIrr11164; Tue, 11 Jun 2002 14:18:53 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5BLIrE02191; Tue, 11 Jun 2002 14:18:53 -0700 (PDT) Message-Id: <200206112118.g5BLIrE02191@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 11 Jun 2002 14:18:52 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3274 on Compressed Data Content Type for Cryptographic Message Syntax (CMS) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3274 Title: Compressed Data Content Type for Cryptographic Message Syntax (CMS) Author(s): P. Gutmann Status: Standards Track Date: June 2002 Mailbox: pgut001@cs.auckland.ac.nz Pages: 6 Characters: 11276 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-compression-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3274.txt This document defines a format for using compressed data as a Cryptographic Message Syntax (CMS) content type. Compressing data before transmission provides a number of advantages, including the elimination of data redundancy which could help an attacker, speeding up processing by reducing the amount of data to be processed by later steps (such as signing or encryption), and reducing overall message size. Although there have been proposals for adding compression at other levels (for example at the MIME or SSL level), these don't address the problem of compression of CMS content unless the compression is supplied by an external means (for example by intermixing MIME and CMS). This document is a product of the S/MIME Mail Security Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020611141659.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3274 --OtherAccess Content-Type: Message/External-body; name="rfc3274.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020611141659.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Jun 13 10:35:25 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHZOr08158; Thu, 13 Jun 2002 10:35:24 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHZOE29659; Thu, 13 Jun 2002 10:35:24 -0700 (PDT) Message-Id: <200206131735.g5DHZOE29659@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 13 Jun 2002 10:35:23 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3292 on General Switch Management Protocol V3 Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3292 Title: General Switch Management Protocol (GSMP) V3 Author(s): A. Doria, F. Hellstrand, K. Sundell, T. Worster Status: Standards Track Date: June 2002 Mailbox: avri@acm.org, fiffi@nortelnetworks.com, ksundell@nortelnetworks.com, fsb@thefsb.org Pages: 137 Characters: 318983 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-gsmp-11.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3292.txt This document describes the General Switch Management Protocol Version 3 (GSMPv3). The GSMPv3 is an asymmetric protocol that allows one or more external switch controllers to establish and maintain the state of a label switch such as, an ATM, frame relay or MPLS switch. The GSMPv3 allows control of both unicast and multicast switch connection state as well as control of switch system resources and QoS features. This document is a product of the General Switch Management Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020613103251.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3292 --OtherAccess Content-Type: Message/External-body; name="rfc3292.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020613103251.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Jun 13 10:38:07 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHc7r10079; Thu, 13 Jun 2002 10:38:07 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHc6E00456; Thu, 13 Jun 2002 10:38:06 -0700 (PDT) Message-Id: <200206131738.g5DHc6E00456@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 13 Jun 2002 10:38:06 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3293 on General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3293 Title: General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP) Author(s): T. Worster, A. Doria, J. Buerkle Status: Standards Track Date: June 2002 Mailbox: fsb@thefsb.org, avri@acm.org, Joachim.Buerkle@nortelnetworks.com Pages: 9 Characters: 18206 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-gsmp-encaps-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3293.txt This memo specifies the encapsulation of GSMP (General Switch Management Protocol) packets in ATM (Asynchronous Transfer Mode), Ethernet and TCP (Transmission Control Protocol). This document is a product of the General Switch Management Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020613103601.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3293 --OtherAccess Content-Type: Message/External-body; name="rfc3293.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020613103601.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Jun 13 10:40:59 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHexr11475; Thu, 13 Jun 2002 10:40:59 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHexE01765; Thu, 13 Jun 2002 10:40:59 -0700 (PDT) Message-Id: <200206131740.g5DHexE01765@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 13 Jun 2002 10:40:58 -0700 Subject: [rfc-dist] RFC 3294 on General Switch Management Protocol (GSMP) Applicability Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3294 Title: General Switch Management Protocol (GSMP) Applicability Author(s): A. Doria, K. Sundell Status: Informational Date: June 2002 Mailbox: avri@acm.org, sundell@nortelnetworks.com Pages: 9 Characters: 18294 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-gsmp-applicability-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3294.txt This memo provides an overview of the GSMP (General Switch Management Protocol) and includes information relating to its deployment in a IP network in an MPLS environment. It does not discuss deployment in an ATM (Asynchronous Transfer Mode) network or in a raw ethernet configuration. This document is a product of the General Switch Management Protocol Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020613103830.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3294 --OtherAccess Content-Type: Message/External-body; name="rfc3294.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020613103830.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Jun 13 10:43:19 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHhJr15002; Thu, 13 Jun 2002 10:43:19 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5DHhJE02625; Thu, 13 Jun 2002 10:43:19 -0700 (PDT) Message-Id: <200206131743.g5DHhJE02625@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 13 Jun 2002 10:43:18 -0700 From: RFC Editor Subject: [rfc-dist] RFC 3295 on Definitions of Managed Objects for the General Switch Management Protocol (GSMP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3295 Title: Definitions of Managed Objects for the General Switch Management Protocol (GSMP) Author(s): H. Sjostrand, J. Buerkle, B. Srinivasan Status: Standards Track Date: June 2002 Mailbox: hans@ipunplugged.com, joachim.buerkle@nortelnetworks.com, balaji@cplane.com Pages: 46 Characters: 95516 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-gsmp-mib-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3295.txt This memo defines a portion of the Management Information Base (MIB) for the use with the network management protocols in the Internet community. In particular, it describes managed objects for the General Switch Management Protocol (GSMP). This document is a product of the General Switch Management Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020613104126.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3295 --OtherAccess Content-Type: Message/External-body; name="rfc3295.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020613104126.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jun 19 10:17:38 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g5JHHcr22631; Wed, 19 Jun 2002 10:17:38 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5JHHcE21497; Wed, 19 Jun 2002 10:17:38 -0700 (PDT) Message-Id: <200206191717.g5JHHcE21497@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 19 Jun 2002 10:17:37 -0700 Subject: [rfc-dist] RFC 3301 on Layer Two Tunnelling Protocol (L2TP): ATM access network extensions Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3301 Title: Layer Two Tunnelling Protocol (L2TP): ATM access network extensions Author(s): Y. T'Joens, P. Crivellari, B. Sales Status: Standards Track Date: June 2002 Mailbox: yves.tjoens@alcatel.be, paolo.crivellari@alcatel.be, bernard.sales@alcatel.be Pages: 19 Characters: 42756 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2tpext-atmext-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3301.txt This document augments the procedures described in RFC 2661 to further support ATM SVC (Switched Virtual Circuits) or PVC (Permanent Virtual Circuits) based access networks. L2TP (Layer 2 Tunneling Protocol) specifies a protocol for tunnelling PPP packets over packet based networks and over IP networks in particular. L2TP supports remote access by ISDN and PSTN networks. The extensions defined within this document allow for asymmetric bi-directional call establishment and service selection in the ATM access network. This document is a product of the Layer Two Tunneling Protocol Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020619101511.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3301 --OtherAccess Content-Type: Message/External-body; name="rfc3301.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020619101511.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Jun 27 14:45:20 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g5RLjJr15254; Thu, 27 Jun 2002 14:45:19 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5RLjJE01214; Thu, 27 Jun 2002 14:45:19 -0700 (PDT) Message-Id: <200206272145.g5RLjJE01214@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 27 Jun 2002 14:45:19 -0700 Subject: [rfc-dist] RFC 3288 on Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3288 Title: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) Author(s): E. O'Tuathail, M. Rose Status: Standards Track Date: June 2002 Mailbox: eamon.otuathail@clipcode.com, mrose@dbc.mtview.ca.us Pages: 20 Characters: 27434 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-etal-beep-soap-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3288.txt This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol core (BEEP). A SOAP binding describes how SOAP messages are transmitted in the network. The SOAP is an XML-based (extensible markup language) messaging protocol used to implement a wide variety of distributed messaging models. It defines a message format and describes a variety of message patterns, including, but not limited to, RPC, asynchronous event notification, unacknowledged messages, and forwarding via SOAP intermediaries. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020627144258.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3288 --OtherAccess Content-Type: Message/External-body; name="rfc3288.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020627144258.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Jul 1 17:25:08 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g620P8r07394; Mon, 1 Jul 2002 17:25:08 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g620P7E21097; Mon, 1 Jul 2002 17:25:08 -0700 (PDT) Message-Id: <200207020025.g620P7E21097@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 01 Jul 2002 17:25:07 -0700 Subject: [rfc-dist] RFC 3283 on Guide to Internet Calendaring Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3283 Title: Guide to Internet Calendaring Author(s): B. Mahoney, G. Babics, A. Taler Status: Informational Date: June 2002 Mailbox: bobmah@mit.edu, georgeb@steltor.com, alex@0--0.org Pages: 16 Characters: 31768 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-calsch-inetcal-guide-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3283.txt This document describes the various Internet calendaring and scheduling standards and works in progress, and the relationships between them. Its intent is to provide a context for these documents, assist in their understanding, and potentially aid in the design of standards-based calendaring and scheduling systems. The standards addressed are RFC 2445 (iCalendar), RFC 2446 (iTIP), and RFC 2447 (iMIP). The work in progress addressed is "Calendar Access Protocol" (CAP). This document also describes issues and problems that are not solved by these protocols, and that could be targets for future work. This document is a product of the Calendaring and Scheduling Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020701172051.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3283 --OtherAccess Content-Type: Message/External-body; name="rfc3283.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020701172051.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Jul 1 17:29:49 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g620Tnr10993; Mon, 1 Jul 2002 17:29:49 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g620TnE22915; Mon, 1 Jul 2002 17:29:49 -0700 (PDT) Message-Id: <200207020029.g620TnE22915@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 01 Jul 2002 17:29:48 -0700 Subject: [rfc-dist] RFC 3284 on The VCDIFF Generic Differencing and Compression Data Format Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3284 Title: The VCDIFF Generic Differencing and Compression Data Format Author(s): D. Korn, J. MacDonald, J. Mogul, K. Vo Status: Standards Track Date: June 2002 Mailbox: kpv@research.att.com, dgk@research.att.com, JeffMogul@acm.org, jmacd@cs.berkeley.edu Pages: 29 Characters: 64035 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-korn-vcdiff-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3284.txt This memo describes VCDIFF, a general, efficient and portable data format suitable for encoding compressed and/or differencing data so that they can be easily transported among computers. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020701172820.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3284 --OtherAccess Content-Type: Message/External-body; name="rfc3284.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020701172820.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 12:47:43 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63Jlgr22783; Wed, 3 Jul 2002 12:47:42 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63JlgE22630; Wed, 3 Jul 2002 12:47:42 -0700 (PDT) Message-Id: <200207031947.g63JlgE22630@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 12:47:42 -0700 Subject: [rfc-dist] RFC 3261 on SIP: Session Initiation Protocol Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3261 Title: SIP: Session Initiation Protocol Author(s): J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, E. Schooler Status: Standards Track Date: June 2002 Mailbox: jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu, Gonzalo.Camarillo@ericsson.com, alan.johnston@wcom.com, jon.peterson@neustar.com, rsparks@dynamicsoft.com, mjh@icir.org, schooler@research.att.com Pages: 266 Characters: 647976 Obsoletes: 2543 I-D Tag: draft-ietf-sip-rfc2543bis-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3261.txt This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. SIP invitations used to create sessions carry session descriptions that allow participants to agree on a set of compatible media types. SIP makes use of elements called proxy servers to help route requests to the user's current location, authenticate and authorize users for services, implement provider call-routing policies, and provide features to users. SIP also provides a registration function that allows users to upload their current locations for use by proxy servers. SIP runs on top of several different transport protocols. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703124440.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3261 --OtherAccess Content-Type: Message/External-body; name="rfc3261.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703124440.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 12:50:04 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63Jo3r24647; Wed, 3 Jul 2002 12:50:03 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63Jo3E25123; Wed, 3 Jul 2002 12:50:03 -0700 (PDT) Message-Id: <200207031950.g63Jo3E25123@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 12:50:03 -0700 Subject: [rfc-dist] RFC 3262 on Reliability of Provisional Responses in the Session Initiation Protocol (SIP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3262 Title: Reliability of Provisional Responses in Session Initiation Protocol (SIP) Author(s): jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu Status: Standards Track Date: June 2002 Mailbox: jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu Pages: 14 Characters: 29643 Obsoletes: 2543 I-D Tag: draft-ietf-sip-100rel-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3262.txt This document specifies an extension to the Session Initiation Protocol (SIP) providing reliable provisional response messages. This extension uses the option tag 100rel and defines the Provisional Response ACKnowledgement (PRACK) method. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703124812.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3262 --OtherAccess Content-Type: Message/External-body; name="rfc3262.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703124812.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 12:52:13 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63JqDr26658; Wed, 3 Jul 2002 12:52:13 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63JqDE25826; Wed, 3 Jul 2002 12:52:13 -0700 (PDT) Message-Id: <200207031952.g63JqDE25826@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 12:52:12 -0700 Subject: [rfc-dist] RFC 3263 on Session Initiation Protocol (SIP): Locating SIP Servers Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3263 Title: Session Initiation Protocol (SIP): Locating SIP Servers Author(s): J. Rosenberg, H. Schulzrinne Status: Standards Track Date: June 2002 Mailbox: jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu Pages: 17 Characters: 42310 Obsoletes: 2543 I-D Tag: draft-ietf-sip-srv-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3263.txt The Session Initiation Protocol (SIP) uses DNS procedures to allow a client to resolve a SIP Uniform Resource Identifier (URI) into the IP address, port, and transport protocol of the next hop to contact. It also uses DNS to allow a server to send a response to a backup client if the primary client has failed. This document describes those DNS procedures in detail. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703125030.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3263 --OtherAccess Content-Type: Message/External-body; name="rfc3263.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703125030.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 12:54:24 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63JsOr28511; Wed, 3 Jul 2002 12:54:24 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63JsNE26631; Wed, 3 Jul 2002 12:54:23 -0700 (PDT) Message-Id: <200207031954.g63JsNE26631@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 12:54:23 -0700 Subject: [rfc-dist] RFC 3264 on An Offer/Answer Model with the Session Description Protocol (SDP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3264 Title: An Offer/Answer Model with Session Description Protocol (SDP) Author(s): J. Rosenberg, H. Schulzrinne Status: Standards Track Date: June 2002 Mailbox: jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu Pages: 25 Characters: 60854 Obsoletes: 2543 I-D Tag: draft-ietf-mmusic-sdp-offer-answer-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3264.txt This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them. In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective. This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session. The offer/answer model is used by protocols like the Session Initiation Protocol (SIP). This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703125236.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3264 --OtherAccess Content-Type: Message/External-body; name="rfc3264.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703125236.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 12:56:23 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63JuNr02222; Wed, 3 Jul 2002 12:56:23 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63JuNE26965; Wed, 3 Jul 2002 12:56:23 -0700 (PDT) Message-Id: <200207031956.g63JuNE26965@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 12:56:23 -0700 Subject: [rfc-dist] RFC 3265 on Session Initiation Protocol (SIP)-Specific Event Notification Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3265 Title: Session Initiation Protocol (SIP)-Specific Event Notification Author(s): A. B. Roach Status: Standards Track Date: June 2002 Mailbox: adam@dynamicsoft.com Pages: 38 Characters: 89005 Obsoletes: 2543 I-D Tag: draft-ietf-sip-events-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3265.txt This document describes an extension to the Session Initiation Protocol (SIP). The purpose of this extension is to provide an extensible framework by which SIP nodes can request notification from remote nodes indicating that certain events have occurred. Concrete uses of the mechanism described in this document may be standardized in the future. Note that the event notification mechanisms defined herein are NOT intended to be a general-purpose infrastructure for all classes of event subscription and notification. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703125449.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3265 --OtherAccess Content-Type: Message/External-body; name="rfc3265.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703125449.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 13:11:52 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63KBqr14111; Wed, 3 Jul 2002 13:11:52 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63KBqE03080; Wed, 3 Jul 2002 13:11:52 -0700 (PDT) Message-Id: <200207032011.g63KBqE03080@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 13:11:51 -0700 Subject: [rfc-dist] RFC 3266 on Support for IPv6 in Session Description Protocol Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3266 Title: Support for IPv6 in Session Description Protocol (SDP) Author(s): S. Olson, G. Camarillo, A. B. Roach Status: Standards Track Date: June 2002 Mailbox: seanol@microsoft.com, Gonzalo.Camarillo@ericsson.com, adam@dynamicsoft.com Pages: 5 Characters: 8693 Updates: 2327 I-D Tag: draft-ietf-mmusic-sdp-ipv6-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3266.txt This document describes the use of Internet Protocol Version 6 (IPv6) addresses in conjunction with the Session Description Protocol (SDP). Specifically, this document clarifies existing text in SDP with regards to the syntax of IPv6 addresses. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703131008.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3266 --OtherAccess Content-Type: Message/External-body; name="rfc3266.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703131008.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 13:14:36 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63KEar17020; Wed, 3 Jul 2002 13:14:36 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63KEaE04267; Wed, 3 Jul 2002 13:14:36 -0700 (PDT) Message-Id: <200207032014.g63KEaE04267@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 13:14:36 -0700 Subject: [rfc-dist] RFC 3267 on Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3267 Title: Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs Author(s): J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie Status: Standards Track Date: June 2002 Mailbox: Johan.Sjoberg@ericsson.com, Magnus.Westerlund@ericsson.com, ari.lakaniemi@nokia.com, qxie1@email.mot.com Pages: 49 Characters: 110652 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rtp-amr-13.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3267.txt This document specifies a real-time transport protocol (RTP) payload format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) encoded speech signals. The payload format is designed to be able to interoperate with existing AMR and AMR-WB transport formats on non-IP networks. In addition, a file format is specified for transport of AMR and AMR-WB speech data in storage mode applications such as email. Two separate MIME type registrations are included, one for AMR and one for AMR-WB, specifying use of both the RTP payload format and the storage format. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703131216.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3267 --OtherAccess Content-Type: Message/External-body; name="rfc3267.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703131216.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 13:17:36 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63KHZr20242; Wed, 3 Jul 2002 13:17:35 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63KHZE05772; Wed, 3 Jul 2002 13:17:35 -0700 (PDT) Message-Id: <200207032017.g63KHZE05772@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 13:17:35 -0700 Subject: [rfc-dist] RFC 3268 on Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3268 Title: Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS) Author(s): P. Chown Status: Standards Track Date: June 2002 Mailbox: pc@skygate.co.uk Pages: 6 Characters: 13530 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tls-ciphersuite-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3268.txt This document proposes several new ciphersuites. At present, the symmetric ciphers supported by Transport Layer Security (TLS) are RC2, RC4, International Data Encryption Algorithm (IDEA), Data Encryption Standard (DES), and triple DES. The protocol would be enhanced by the addition of Advanced Encryption Standard (AES) ciphersuites. This document is a product of the Transport Layer Security Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703131443.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3268 --OtherAccess Content-Type: Message/External-body; name="rfc3268.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703131443.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 3 13:19:41 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g63KJfr22572; Wed, 3 Jul 2002 13:19:41 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g63KJeE06799; Wed, 3 Jul 2002 13:19:40 -0700 (PDT) Message-Id: <200207032019.g63KJeE06799@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 03 Jul 2002 13:19:40 -0700 Subject: [rfc-dist] Correction: RFC 3267 on Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3267 Title: Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs Author(s): J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie Status: Standards Track Date: June 2002 Mailbox: Johan.Sjoberg@ericsson.com, Magnus.Westerlund@ericsson.com, ari.lakaniemi@nokia.com, qxie1@email.mot.com Pages: 49 Characters: 110652 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rtp-amr-13.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3267.txt This document specifies a real-time transport protocol (RTP) payload format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) encoded speech signals. The payload format is designed to be able to interoperate with existing AMR and AMR-WB transport formats on non-IP networks. In addition, a file format is specified for transport of AMR and AMR-WB speech data in storage mode applications such as email. Two separate MIME type registrations are included, one for AMR and one for AMR-WB, specifying use of both the RTP payload format and the storage format. This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020703131758.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3267 --OtherAccess Content-Type: Message/External-body; name="rfc3267.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020703131758.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Jul 8 15:02:09 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g68M28r08668; Mon, 8 Jul 2002 15:02:09 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g68M28E00476; Mon, 8 Jul 2002 15:02:08 -0700 (PDT) Message-Id: <200207082202.g68M28E00476@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 08 Jul 2002 15:02:08 -0700 Subject: [rfc-dist] RFC 3287 on Remote Monitoring MIB Extensions for Differentiated Services Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3287 Title: Remote Monitoring MIB Extensions for Differentiated Services Author(s): A. Bierman Status: Standards Track Date: July 2002 Mailbox: abierman@cisco.com Pages: 120 Characters: 249622 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmonmib-dsmon-mib-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3287.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for monitoring Differentiated Services (DS) Codepoint usage in packets which contain a DS field, utilizing the monitoring framework defined in the RMON-2 (Remote Network Monitoring Management Version 2) MIB. This document is a product of the Remote Network Monitoring Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020708145947.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3287 --OtherAccess Content-Type: Message/External-body; name="rfc3287.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020708145947.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Jul 15 11:13:34 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6FIDYr13053; Mon, 15 Jul 2002 11:13:34 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6FIDUE12354; Mon, 15 Jul 2002 11:13:30 -0700 (PDT) Message-Id: <200207151813.g6FIDUE12354@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 15 Jul 2002 11:13:30 -0700 Subject: [rfc-dist] RFC 3273 on Remote Network Monitoring Management Information Base for High Capacity Networks Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3273 Title: Remote Network Monitoring Management Information Base for High Capacity Networks Author(s): S. Waldbusser Status: Standards Track Date: July 2002 Mailbox: waldbusser@nextbeacon.com Pages: 77 Characters: 150924 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmonmib-hcrmon-10.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3273.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring (RMON) devices for use on high speed networks. This document contains a MIB Module that defines these new objects and also contains definitions of some updated objects from the RMON-MIB in RFC 2819 and the RMON2-MIB in RFC 2021. This document is a product of the Remote Network Monitoring Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020715111014.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3273 --OtherAccess Content-Type: Message/External-body; name="rfc3273.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020715111014.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Jul 22 14:53:54 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6MLrrr26075; Mon, 22 Jul 2002 14:53:53 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6MLrrE13750; Mon, 22 Jul 2002 14:53:53 -0700 (PDT) Message-Id: <200207222153.g6MLrrE13750@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 22 Jul 2002 14:53:53 -0700 Subject: [rfc-dist] RFC 3296 on Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3296 Title: Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories Author(s): K. Zeilenga Status: Standards Track Date: July 2002 Mailbox: Kurt@OpenLDAP.org Pages: 14 Characters: 27389 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-zeilenga-ldap-namedref-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3296.txt This document details schema and protocol elements for representing and managing named subordinate references in Lightweight Directory Access Protocol (LDAP) Directories. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020722145214.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3296 --OtherAccess Content-Type: Message/External-body; name="rfc3296.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020722145214.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Jul 23 16:51:56 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6NNpur10632; Tue, 23 Jul 2002 16:51:56 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6NNpuE06715; Tue, 23 Jul 2002 16:51:56 -0700 (PDT) Message-Id: <200207232351.g6NNpuE06715@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 23 Jul 2002 16:51:56 -0700 Subject: [rfc-dist] RFC 3348 on The Internet Message Action Protocol (IMAP4) Child Mailbox Extension Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3348 Title: The Internet Message Action Protocol (IMAP4) Child Mailbox Extension Author(s): M. Gahrns, R. Cheng Status: Informational Date: July 2002 Mailbox: mikega@microsoft.com, raych@microsoft.com Pages: 6 Characters: 11868 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-gahrns-imap-child-mailbox-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3348.txt The Internet Message Action Protocol (IMAP4) CHILDREN extension provides a mechanism for a client to efficiently determine if a particular mailbox has children, without issuing a LIST "" * or a LIST "" % for each mailbox. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020723165032.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3348 --OtherAccess Content-Type: Message/External-body; name="rfc3348.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020723165032.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 24 16:14:12 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONEBr18795; Wed, 24 Jul 2002 16:14:11 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONEBE16384; Wed, 24 Jul 2002 16:14:11 -0700 (PDT) Message-Id: <200207242314.g6ONEBE16384@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Jul 2002 16:14:11 -0700 Subject: [rfc-dist] RFC 3297 on Content Negotiation for Messaging Services based on Email Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3297 Title: Content Negotiation for Messaging Services based on Email Author(s): G. Klyne, R. Iwazaki, D. Crocker Status: Standards Track Date: July 2002 Mailbox: GK@ACM.ORG, iwa@rdl.toshibatec.co.jp, dcrocker@brandenburg.com Pages: 47 Characters: 97094 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-fax-content-negotiation-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3297.txt This memo describes a content negotiation mechanism for facsimile, voice and other messaging services that use Internet email. Services such as facsimile and voice messaging need to cope with new message content formats, yet need to ensure that the content of any given message is renderable by the receiving agent. The mechanism described here aims to meet these needs in a fashion that is fully compatible with the current behaviour and expectations of Internet email. This document is a product of the Internet Fax Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020724161051.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3297 --OtherAccess Content-Type: Message/External-body; name="rfc3297.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020724161051.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 24 16:16:47 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONGlr20850; Wed, 24 Jul 2002 16:16:47 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONGkE17887; Wed, 24 Jul 2002 16:16:46 -0700 (PDT) Message-Id: <200207242316.g6ONGkE17887@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Jul 2002 16:16:46 -0700 Subject: [rfc-dist] RFC 3339 on Content Negotiation for Messaging Services based on Email Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3339 Title: Date and Time on the Internet: Timestamps Author(s): G. Klyne, C. Newman Status: Standards Track Date: July 2002 Mailbox: GK@ACM.ORG, chris.newman@sun.com Pages: 18 Characters: 35064 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-impp-datetime-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3339.txt This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar. This document is a product of the Instant Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020724161446.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3339 --OtherAccess Content-Type: Message/External-body; name="rfc3339.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020724161446.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 24 16:19:04 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONJ4r23618; Wed, 24 Jul 2002 16:19:04 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONJ4E20498; Wed, 24 Jul 2002 16:19:04 -0700 (PDT) Message-Id: <200207242319.g6ONJ4E20498@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Jul 2002 16:19:03 -0700 Subject: [rfc-dist] RFC 3340 on The Application Exchange Core Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3340 Title: The Application Exchange Core Author(s): M. Rose, G. Klyne, D. Crocker Status: Standards Track Date: July 2002 Mailbox: mrose@dbc.mtview.ca.us, Graham.Klyne@MIMEsweeper.com, dcrocker@brandenburg.com Pages: 40 Characters: 74266 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-apex-core-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3340.txt This memo describes Application Exchange (APEX) Core, an extensible, asynchronous message relaying service for application layer programs. This document is a product of the Application Exchange Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020724161712.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3340 --OtherAccess Content-Type: Message/External-body; name="rfc3340.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020724161712.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 24 16:21:03 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONL3r26261; Wed, 24 Jul 2002 16:21:03 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONL2E21151; Wed, 24 Jul 2002 16:21:02 -0700 (PDT) Message-Id: <200207242321.g6ONL2E21151@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Jul 2002 16:21:02 -0700 Subject: [rfc-dist] RFC 3341 on The Application Exchange (APEX) Access Service Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3341 Title: The Application Exchange (APEX) Access Service Author(s): M. Rose, G. Klyne, D. Crocker Status: Standards Track Date: July 2002 Mailbox: mrose@dbc.mtview.ca.us, Graham.Klyne@MIMEsweeper.com, dcrocker@brandenburg.com Pages: 24 Characters: 46675 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-apex-access-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3341.txt This memo describes the Application Exchange (APEX) access service, addressed as the well-known endpoint "apex=access". The access service is used to control use of both the APEX "relaying mesh" and other APEX services. This document is a product of the Application Exchange Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020724161929.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3341 --OtherAccess Content-Type: Message/External-body; name="rfc3341.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020724161929.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 24 16:23:56 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONNur00600; Wed, 24 Jul 2002 16:23:56 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONNtE22048; Wed, 24 Jul 2002 16:23:55 -0700 (PDT) Message-Id: <200207242323.g6ONNtE22048@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Jul 2002 16:23:55 -0700 Subject: [rfc-dist] RFC 3342 on The Application Exchange (APEX) Option Party Pack, Part Deux! Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3342 Title: The Application Exchange (APEX) Option Party Pack, Part Deux! Author(s): E. Dixon, H. Franklin, J. Kint, G. Klyne, D. New, S. Pead, M. Rose, M. Schwartz Status: Standards Track Date: July 2002 Mailbox: edixon@myrealbox.com, huston@franklin.ro, d20@icosahedron.org, Graham.Klyne@MIMEsweeper.com, dnew@san.rr.com, spead@fiber.net, mrose@dbc.mtview.ca.us, schwartz@CodeOnTheRoad.com Pages: 19 Characters: 34300 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-apex-party-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3342.txt Application Exchange (APEX), at its core, provides a best-effort application-layer datagram service. Options are used to alter the semantics of the core service. This memo defines various options to change the default behavior of APEX's "relaying mesh". This document is a product of the Application Exchange Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020724162216.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3342 --OtherAccess Content-Type: Message/External-body; name="rfc3342.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020724162216.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Jul 24 16:25:52 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONPqr02830; Wed, 24 Jul 2002 16:25:52 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONPpE22625; Wed, 24 Jul 2002 16:25:51 -0700 (PDT) Message-Id: <200207242325.g6ONPpE22625@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Jul 2002 16:25:50 -0700 Subject: [rfc-dist] RFC 3347 on Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3347 Title: Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations Author(s): M. Krueger, R. Haagens Status: Informational Date: July 2002 Mailbox: marjorie_krueger@hp.com, Randy_Haagens@hp.com, csapuntz@cisco.com, mbakke@cisco.com Pages: 25 Characters: 58097 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ips-iscsi-reqmts-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3347.txt This document specifies the requirements iSCSI and its related infrastructure should satisfy and the design considerations guiding the iSCSI protocol development efforts. In the interest of timely adoption of the iSCSI protocol, the IPS group has chosen to focus the first version of the protocol to work with the existing SCSI architecture and commands, and the existing TCP/IP transport layer. Both these protocols are widely-deployed and well-understood. The thought is that using these mature protocols will entail a minimum of new invention, the most rapid possible adoption, and the greatest compatibility with Internet architecture, protocols, and equipment. This document is a product of the IP Storage Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020724162420.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3347 --OtherAccess Content-Type: Message/External-body; name="rfc3347.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020724162420.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Jul 25 09:06:53 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g6PG6rr10233; Thu, 25 Jul 2002 09:06:53 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6PG6qE16047; Thu, 25 Jul 2002 09:06:52 -0700 (PDT) Message-Id: <200207251606.g6PG6qE16047@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 25 Jul 2002 09:06:52 -0700 Subject: [rfc-dist] Corrected: RFC 3339 on Date and Time on the Internet: Timestamps Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3339 Title: Date and Time on the Internet: Timestamps Author(s): G. Klyne, C. Newman Status: Standards Track Date: July 2002 Mailbox: GK@ACM.ORG, chris.newman@sun.com Pages: 18 Characters: 35064 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-impp-datetime-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3339.txt This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar. This document is a product of the Instant Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020725090519.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3339 --OtherAccess Content-Type: Message/External-body; name="rfc3339.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020725090519.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Aug 1 14:43:55 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g71Lhtr05472; Thu, 1 Aug 2002 14:43:55 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g71LhsE05090; Thu, 1 Aug 2002 14:43:54 -0700 (PDT) Message-Id: <200208012143.g71LhsE05090@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 01 Aug 2002 14:43:54 -0700 Subject: [rfc-dist] BCP 59, RFC 3349 on A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. BCP 59 RFC 3349 Title: A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force Author(s): M. Rose Status: Best Current Practice Date: July 2002 Mailbox: mrose@dbc.mtview.ca.us Pages: 6 Characters: 7916 SeeAlso: BCP 59 I-D Tag: draft-mrose-beep-transientid-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3349.txt As a part of their deliverables, working groups of the IETF may develop BEEP profiles. During the development process, it is desirable to assign a transient identifier to each profile. If the profile is subsequently published as an RFC, then a permanent identifier is subsequently assigned by the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020801144201.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3349 --OtherAccess Content-Type: Message/External-body; name="rfc3349.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020801144201.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Aug 1 14:45:45 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g71Ljir07654; Thu, 1 Aug 2002 14:45:45 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g71LjiE06379; Thu, 1 Aug 2002 14:45:44 -0700 (PDT) Message-Id: <200208012145.g71LjiE06379@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 01 Aug 2002 14:45:44 -0700 Subject: [rfc-dist] RFC 3345 on Border Gateway Protocol (BGP) Persistent Route Oscillation Condition Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3345 Title: Border Gateway Protocol (BGP) Persistent Route Oscillation Condition Author(s): D. McPherson, V. Gill, D. Walton, A. Retana Status: Informational Date: August 2002 Mailbox: danny@tcb.net, vijay@umbc.edu, dwalton@cisco.com, aretana@cisco.com Pages: 19 Characters: 38137 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idr-route-oscillation-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3345.txt In particular configurations, the BGP scaling mechanisms defined in "BGP Route Reflection - An Alternative to Full Mesh IBGP" and "Autonomous System Confederations for BGP" will introduce persistent BGP route oscillation. This document discusses the two types of persistent route oscillation that have been identified, describes when these conditions will occur, and provides some network design guidelines to avoid introducing such occurrences. This document is a product of the Inter-Domain Routing Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020801144423.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3345 --OtherAccess Content-Type: Message/External-body; name="rfc3345.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020801144423.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Aug 14 11:35:03 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7EIZ3r24027; Wed, 14 Aug 2002 11:35:03 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7EIZ3E16413; Wed, 14 Aug 2002 11:35:03 -0700 (PDT) Message-Id: <200208141835.g7EIZ3E16413@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 14 Aug 2002 11:35:02 -0700 Subject: [rfc-dist] RFC 3344 on IP Mobility Support for IPv4 Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3344 Title: IP Mobility Support for IPv4 Author(s): C. Perkins, Ed. Status: Standards Track Date: August 2002 Mailbox: charliep@iprg.nokia.com Pages: 99 Characters: 241041 Obsoletes: 3220 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3344.txt This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about its current point of attachment to the Internet. The protocol provides for registering the care-of address with a home agent. The home agent sends datagrams destined for the mobile node through a tunnel to the care-of address. After arriving at the end of the tunnel, each datagram is then delivered to the mobile node. This document is a product of the IP Routing for Wireless/Mobile Hosts Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020814112915.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3344 --OtherAccess Content-Type: Message/External-body; name="rfc3344.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020814112915.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Aug 14 11:38:28 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7EIcSr27000; Wed, 14 Aug 2002 11:38:28 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7EIcSE17398; Wed, 14 Aug 2002 11:38:28 -0700 (PDT) Message-Id: <200208141838.g7EIcSE17398@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 14 Aug 2002 11:38:27 -0700 Subject: [rfc-dist] RFC 3354 on Internet Open Trading Protocol Version 2 Requirements Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3354 Title: Internet Open Trading Protocol Version 2 Requirements Author(s): D. Eastlake, III Status: Informational Date: August 2002 Mailbox: Donald.Eastlake@motorola.com Pages: 6 Characters: 9671 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trade-iotp2-rep-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3354.txt This document gives requirements for the Internet Open Trading Protocol (IOTP) Version 2 by describing design principles and scope and dividing features into those which will, may, or will not be included. Version 2 of the IOTP will extend the interoperable framework for Internet commerce capabilities of Version 1 while replacing the XML messaging and digital signature part of IOTP v1 with standards based mechanisms. This document is a product of the Open Trading Protocol Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020814113631.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3354 --OtherAccess Content-Type: Message/External-body; name="rfc3354.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020814113631.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Aug 14 11:40:22 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7EIeMr00233; Wed, 14 Aug 2002 11:40:22 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7EIeME18058; Wed, 14 Aug 2002 11:40:22 -0700 (PDT) Message-Id: <200208141840.g7EIeME18058@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 14 Aug 2002 11:40:22 -0700 Subject: [rfc-dist] BCP 60, RFC 3360 on Inappropriate TCP Resets Considered Harmful Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. BCP 60 RFC 3360 Title: Inappropriate TCP Resets Considered Harmful Author(s): S. Floyd Status: Best Current Practice Date: August 2002 Mailbox: floyd@icir.org Pages: 19 Characters: 46748 SeeAlso: BCP 60 I-D Tag: draft-floyd-tcp-reset-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3360.txt This document is being written because there are a number of firewalls in the Internet that inappropriately reset a TCP connection upon receiving certain TCP SYN packets, in particular, packets with flags set in the Reserved field of the TCP header. In this document we argue that this practice is not conformant with TCP standards, and is an inappropriate overloading of the semantics of the TCP reset. We also consider the longer-term consequences of this and similar actions as obstacles to the evolution of the Internet infrastructure. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020814113851.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3360 --OtherAccess Content-Type: Message/External-body; name="rfc3360.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020814113851.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Aug 15 09:12:39 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7FGCdr04038; Thu, 15 Aug 2002 09:12:39 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7FGCcE11429; Thu, 15 Aug 2002 09:12:38 -0700 (PDT) Message-Id: <200208151612.g7FGCcE11429@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 15 Aug 2002 09:12:38 -0700 Subject: [rfc-dist] Corrected: RFC 3354 on Internet Open Trading Protocol Version 2 Requirements Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3354 Title: Internet Open Trading Protocol Version 2 Requirements Author(s): D. Eastlake, III Status: Informational Date: August 2002 Mailbox: Donald.Eastlake@motorola.com Pages: 6 Characters: 9671 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trade-iotp2-req-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3354.txt This document gives requirements for the Internet Open Trading Protocol (IOTP) Version 2 by describing design principles and scope and dividing features into those which will, may, or will not be included. Version 2 of the IOTP will extend the interoperable framework for Internet commerce capabilities of Version 1 while replacing the XML messaging and digital signature part of IOTP v1 with standards based mechanisms. This document is a product of the Open Trading Protocol Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020815091116.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3354 --OtherAccess Content-Type: Message/External-body; name="rfc3354.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020815091116.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Aug 15 16:46:34 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNkXr25390; Thu, 15 Aug 2002 16:46:33 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNkXE05355; Thu, 15 Aug 2002 16:46:33 -0700 (PDT) Message-Id: <200208152346.g7FNkXE05355@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 15 Aug 2002 16:46:33 -0700 Subject: [rfc-dist] RFC 3346 on Applicability Statement for Traffic Engineering with MPLS Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3346 Title: Applicability Statement for Traffic Engineering with MPLS Author(s): J. Boyle, V. Gill, A. Hannan, D. Cooper, D. Awduche, B. Christian, W.S. Lai Status: Informational Date: August 2002 Mailbox: jboyle@pdnets.com, vijay@umbc.edu, alan@routingloop.net, dcooper@gblx.net, awduche@movaz.com, blaine@uu.net, wlai@att.com Pages: 14 Characters: 33754 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tewg-te-applicability-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3346.txt This document describes the applicability of Multiprotocol Label Switching (MPLS) to traffic engineering in IP networks. Special considerations for deployment of MPLS for traffic engineering in operational contexts are discussed and the limitations of the MPLS approach to traffic engineering are highlighted. This document is a product of the Internet Traffic Engineering Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020815164424.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3346 --OtherAccess Content-Type: Message/External-body; name="rfc3346.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020815164424.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Aug 15 16:48:09 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNm9r26389; Thu, 15 Aug 2002 16:48:09 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNm9E05454; Thu, 15 Aug 2002 16:48:09 -0700 (PDT) Message-Id: <200208152348.g7FNm9E05454@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 15 Aug 2002 16:48:09 -0700 Subject: [rfc-dist] RFC 3357 on One-way Loss Pattern Sample Metrics Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3357 Title: One-way Loss Pattern Sample Metrics Author(s): R. Koodli, R. Ravikanth Status: Informational Date: August 2002 Mailbox: rajeev.koodli@nokia.com, rravikanth@axiowave.com Pages: 15 Characters: 30570 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ippm-loss-pattern-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3357.txt Using the base loss metric defined in RFC 2680, this document defines two derived metrics "loss distance" and "loss period", and the associated statistics that together capture loss patterns experienced by packet streams on the Internet. The Internet exhibits certain specific types of behavior (e.g., bursty packet loss) that can affect the performance seen by the users as well as the operators. The loss pattern or loss distribution is a key parameter that determines the performance observed by the users for certain real-time applications such as packet voice and video. For the same loss rate, two different loss distributions could potentially produce widely different perceptions of performance. This document is a product of the IP Performance Metrics Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020815164652.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3357 --OtherAccess Content-Type: Message/External-body; name="rfc3357.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020815164652.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Aug 15 16:50:41 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNoer27978; Thu, 15 Aug 2002 16:50:40 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNoeE07004; Thu, 15 Aug 2002 16:50:40 -0700 (PDT) Message-Id: <200208152350.g7FNoeE07004@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 15 Aug 2002 16:50:40 -0700 Subject: [rfc-dist] RFC 3351 on SIP for Deaf, Hard of Hearing and Speech Impaired Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3351 Title: User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals Author(s): N. Charlton, M. Gasson, G. Gybels, M. Spanner, A. van Wijk Status: Informational Date: August 2002 Mailbox: nathan@millpark.com, michael.gasson@korusolutions.com, Guido.Gybels@rnid.org.uk, mike.spanner@rnid.org.uk, Arnoud.van.Wijk@eln.ericsson.se Pages: 17 Characters: 33894 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sipping-deaf-req-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3351.txt This document presents a set of Session Initiation Protocol (SIP) user requirements that support communications for deaf, hard of hearing and speech-impaired individuals. These user requirements address the current difficulties of deaf, hard of hearing and speech-impaired individuals in using communications facilities, while acknowledging the multi-functional potential of SIP-based communications. A number of issues related to these user requirements are further raised in this document. Also included are some real world scenarios and some technical requirements to show the robustness of these requirements on a concept-level. This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020815164833.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3351 --OtherAccess Content-Type: Message/External-body; name="rfc3351.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020815164833.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Aug 15 16:52:17 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNqHr01117; Thu, 15 Aug 2002 16:52:17 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7FNqGE07042; Thu, 15 Aug 2002 16:52:16 -0700 (PDT) Message-Id: <200208152352.g7FNqGE07042@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 15 Aug 2002 16:52:16 -0700 Subject: [rfc-dist] RFC 3356 on Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3356 Title: Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines Author(s): G. Fishman, S. Bradner Status: Informational Date: August 2002 Mailbox: garyfishman@lucent.com, sob@Harvard.edu Pages: 12 Characters: 27068 Obsoletes: 2436 I-D Tag: draft-fishman-2436bis-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3356.txt This document provides guidance to aid in the understanding of collaboration on standards development between the International Telecommunication Union -- Telecommunication Standardization Sector (ITU-T) and the Internet Society (ISOC) / Internet Engineering Task Force (IETF). It is an update of and obsoletes RFC 2436. The updates reflect changes in the IETF and ITU-T since RFC 2436 was written. The bulk of this document is common text with ITU-T Supplement 3 to the ITU-T A-Series Recommendations. Note: This was approved by ITU-T TSAG on 30 November 2001 as a Supplement to the ITU-T A-Series of Recommendations (will be numbered as A-Series Supplement 3). 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020815165058.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3356 --OtherAccess Content-Type: Message/External-body; name="rfc3356.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020815165058.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Aug 19 16:49:21 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7JNnK713810; Mon, 19 Aug 2002 16:49:20 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7JNnKd21011; Mon, 19 Aug 2002 16:49:20 -0700 (PDT) Message-Id: <200208192349.g7JNnKd21011@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 19 Aug 2002 16:49:20 -0700 Subject: [rfc-dist] RFC 3303 on Middlebox communication architecture and framework Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3303 Title: Middlebox communication architecture and framework Author(s): P. Srisuresh, J. Kuthan, J. Rosenberg, A. Molitor, A. Rayhan Status: Informational Date: August 2002 Mailbox: srisuresh@yahoo.com, kuthan@fokus.fhg.de, jdrosen@dynamicsoft.com, amolitor@visi.com, rayhan@ee.ryerson.ca Pages: 34 Characters: 91209 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-midcom-framework-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3303.txt A principal objective of this document is to describe the underlying framework of middlebox communications (MIDCOM) to enable complex applications through the middleboxes, seamlessly using a trusted third party. This document and a companion document on MIDCOM requirements ([REQMTS]) have been created as a precursor to rechartering the MIDCOM working group. There are a variety of intermediate devices in the Internet today that require application intelligence for their operation. Datagrams pertaining to real-time streaming applications, such as SIP and H.323, and peer-to-peer applications, such as Napster and NetMeeting, cannot be identified by merely examining packet headers. Middleboxes implementing Firewall and Network Address Translator services typically embed application intelligence within the device for their operation. The document specifies an architecture and framework in which trusted third parties can be delegated to assist the middleboxes to perform their operation, without resorting to embedding application intelligence. Doing this will allow a middlebox to continue to provide the services, while keeping the middlebox application agnostic. This document is a product of the Middlebox Communication Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020819164742.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3303 --OtherAccess Content-Type: Message/External-body; name="rfc3303.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020819164742.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Aug 19 16:51:13 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7JNpD715507; Mon, 19 Aug 2002 16:51:13 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7JNpDd21319; Mon, 19 Aug 2002 16:51:13 -0700 (PDT) Message-Id: <200208192351.g7JNpDd21319@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 19 Aug 2002 16:51:12 -0700 Subject: [rfc-dist] RFC 3304 on Middlebox Communications (midcom) Protocol Requirements Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3304 Title: Middlebox Communications (midcom) Protocol Requirements Author(s): R. P. Swale, P. A. Mart, P. Sijben, S. Brim, M. Shore Status: Informational Date: August 2002 Mailbox: richard.swale@bt.com, paul.sijben@picopoint.com, philip.mart@marconi.com, sbrim@cisco.com, mshore@cisco.com Pages: 9 Characters: 16187 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-midcom-requirements-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3304.txt This document specifies the requirements that the Middlebox Communication (midcom) protocol must satisfy in order to meet the needs of applications wishing to influence the middlebox function. These requirements were developed with a specific focus on network address translation and firewall middleboxes. This document is a product of the Middlebox Communication Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020819164951.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3304 --OtherAccess Content-Type: Message/External-body; name="rfc3304.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020819164951.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Aug 21 15:55:01 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7LMt1J25302; Wed, 21 Aug 2002 15:55:01 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7LMsjd09923; Wed, 21 Aug 2002 15:54:50 -0700 (PDT) Message-Id: <200208212254.g7LMsjd09923@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 21 Aug 2002 15:54:45 -0700 Subject: [rfc-dist] RFC 3358 on Optional Checksums in Intermediate System to Intermediate System (ISIS) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3358 Title: Optional Checksums in Intermediate System to Intermediate System (ISIS) Author(s): T. Przygienda Status: Informational Date: August 2002 Mailbox: prz@xebeo.com Pages: 4 Characters: 8266 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-wg-snp-checksum-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3358.txt This document describes an optional extension to the Intermediate System to Intermediate System (ISIS) protocol, used today by several Internet Service Proviers (ISPs) for routing within their clouds. ISIS is an interior gateway routing protocol developed originally by OSI and used with IP extensions as Interior Gateway Protocol (IGP). ISIS originally does not provide Complete Sequence Numbers Protocol Data (CSNP) and Partial Sequence Numbers Protocol Data Unit (PSNP) checksums, relying on the underlying layers to verify the integrity of information provided. Experience with the protocol shows that this precondition does not always hold and scenarios can be imagined that impact protocol functionality. This document introduces a new optional Type, Length and Value (TLV) providing checksums. This document is a product of the IS-IS for IP Internets Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020821155240.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3358 --OtherAccess Content-Type: Message/External-body; name="rfc3358.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020821155240.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Aug 21 15:56:37 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7LMuaJ27314; Wed, 21 Aug 2002 15:56:36 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7LMuZd10913; Wed, 21 Aug 2002 15:56:35 -0700 (PDT) Message-Id: <200208212256.g7LMuZd10913@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 21 Aug 2002 15:56:35 -0700 Subject: [rfc-dist] RFC 3359 on Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3359 Title: Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System Author(s): T. Przygienda Status: Informational Date: August 2002 Mailbox: prz@xebeo.com Pages: 5 Characters: 7843 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-wg-tlv-codepoints-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3359.txt This document describes implementation codepoints within Intermediate System to Intermediate System (IS-IS) used today by several ISPs for routing within their clouds. IS-IS is an interior gateway routing protocol developed originally by OSI and used with IP extensions as Interior Gateway Protocol (IGP). This document summarizes all Table, Length and Value (TLV) codepoints that are being used by the protocol and its pending extensions. This document is a product of the IS-IS for IP Internets Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020821155510.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3359 --OtherAccess Content-Type: Message/External-body; name="rfc3359.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020821155510.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Aug 21 15:58:55 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7LMwtJ29652; Wed, 21 Aug 2002 15:58:55 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7LMwrd13123; Wed, 21 Aug 2002 15:58:53 -0700 (PDT) Message-Id: <200208212258.g7LMwrd13123@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 21 Aug 2002 15:58:53 -0700 Subject: [rfc-dist] RFC 3363 on Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3363 Title: Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS) Author(s): R. Bush, A. Durand, B. Fink, O. Gudmundsson, T. Hain Status: Informational Date: August 2002 Mailbox: randy@psg.com, alain.durand@sun.com, fink@es.net, ogud@ogud.com, hain@tndh.net Pages: 6 Characters: 11055 Updates: 2673, 2874 I-D Tag: draft-ietf-dnsext-ipv6-addresses-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3363.txt This document clarifies and updates the standards status of RFCs that define direct and reverse map of IPv6 addresses in DNS. This document moves the A6 and Bit label specifications to experimental status. This document is a product of the DNS Extensions Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020821155708.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3363 --OtherAccess Content-Type: Message/External-body; name="rfc3363.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020821155708.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Aug 21 16:02:19 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7LN2JJ03995; Wed, 21 Aug 2002 16:02:19 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7LN2Id14842; Wed, 21 Aug 2002 16:02:18 -0700 (PDT) Message-Id: <200208212302.g7LN2Id14842@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 21 Aug 2002 16:02:18 -0700 Subject: [rfc-dist] RFC 3364 on Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3364 Title: Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) Author(s): R. Austein Status: Informational Date: August 2002 Mailbox: sra@hactrn.net Pages: 11 Characters: 26544 Obsoletes: 2673, 2874 I-D Tag: draft-ietf-dnsext-ipv6-dns-tradeoffs-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3364.txt The IETF has two different proposals on the table for how to do DNS support for IPv6, and has thus far failed to reach a clear consensus on which approach is better. This note attempts to examine the pros and cons of each approach, in the hope of clarifying the debate so that we can reach closure and move on. This document is a product of the DNS Extensions Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020821160043.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3364 --OtherAccess Content-Type: Message/External-body; name="rfc3364.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020821160043.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Aug 27 15:38:08 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7RMc8K21265; Tue, 27 Aug 2002 15:38:08 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7RMc2d25770; Tue, 27 Aug 2002 15:38:02 -0700 (PDT) Message-Id: <200208272238.g7RMc2d25770@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 27 Aug 2002 15:38:01 -0700 Subject: [rfc-dist] RFC 3353 on Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3353 Title: Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment Author(s): D. Ooms, B. Sales, W. Livens, A. Acharya, F. Griffoul, F. Ansari Status: Informational Date: August 2002 Mailbox: Dirk.Ooms@alcatel.be, Bernard.Sales@alcatel.be, WLivens@colt-telecom.be, arup@us.ibm.com, griffoul@ulticom.com, furquan@dnrc.bell-labs.com Pages: 30 Characters: 65860 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-multicast-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3353.txt This document offers a framework for IP multicast deployment in an MPLS environment. Issues arising when MPLS techniques are applied to IP multicast are overviewed. The pros and cons of existing IP multicast routing protocols in the context of MPLS are described and the relation to the different trigger methods and label distribution modes are discussed. The consequences of various layer 2 (L2) technologies are listed. Both point-to-point and multi-access networks are considered. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020827153623.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3353 --OtherAccess Content-Type: Message/External-body; name="rfc3353.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020827153623.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Aug 27 15:40:06 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7RMe6K22668; Tue, 27 Aug 2002 15:40:06 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7RMe5d26956; Tue, 27 Aug 2002 15:40:05 -0700 (PDT) Message-Id: <200208272240.g7RMe5d26956@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 27 Aug 2002 15:40:05 -0700 Subject: [rfc-dist] RFC 3361 on Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3361 Title: Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers Author(s): H. Schulzrinne Status: Standards Track Date: August 2002 Mailbox: schulzrinne@cs.columbia.edu Pages: 7 Characters: 12549 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sip-dhcp-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3361.txt This document defines a Dynamic Host Configuration Protocol (DHCP-for-IPv4) option that contains a list of domain names or IPv4 addresses that can be mapped to one or more Session Initiation Protocol (SIP) outbound proxy servers. This is one of the many methods that a SIP client can use to obtain the addresses of such a local SIP server. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020827153826.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3361 --OtherAccess Content-Type: Message/External-body; name="rfc3361.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020827153826.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Aug 30 14:51:06 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g7ULp6K10359; Fri, 30 Aug 2002 14:51:06 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g7ULp5D21782; Fri, 30 Aug 2002 14:51:05 -0700 (PDT) Message-Id: <200208302151.g7ULp5D21782@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 30 Aug 2002 14:51:05 -0700 Subject: [rfc-dist] RFC 3305 on Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3305 Title: Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations Author(s): M. Mealling, Ed., R. Denenberg, Ed. Status: Informational Date: August 2002 Mailbox: michael@verisignlabs.com, rden@loc.gov Pages: 11 Characters: 21793 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mealling-uri-ig-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3305.txt This document, a product of the W3C Uniform Resource Identifier (URI) Interest Group, addresses and attempts to clarify issues pertaining to URIs. This document addresses how URI space is partitioned and the relationship between URIs, URLs, and URNs, describes how URI schemes and URN namespaces ids are registered, and presents recommendations for continued work on this subject. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020830144926.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3305 --OtherAccess Content-Type: Message/External-body; name="rfc3305.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020830144926.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Sep 3 16:54:30 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g83NsUC06820; Tue, 3 Sep 2002 16:54:30 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g83NsTD02044; Tue, 3 Sep 2002 16:54:29 -0700 (PDT) Message-Id: <200209032354.g83NsTD02044@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 03 Sep 2002 16:54:29 -0700 Subject: [rfc-dist] RFC 3298 on SPIRITS Protocol Requirements Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3298 Title: Service in the Public Switched Telephone Network/Intelligent Network (PSTN/IN) Requesting InTernet Service (SPIRITS) Protocol Requirements Author(s): I. Faynberg, J. Gato, H. Lu, L. Slutsman Status: Informational Date: August 2002 Mailbox: faynberg@lucent.com, jgato@airtel.es, huilanlu@lucent.com, lslutsman@att.com Pages: 17 Characters: 36560 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-spirits-reqs-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3298.txt This document describes the SPIRITS protocol requirements, based on the architecture presented in RFC 3136. (SPIRITS stands for "Service in the PSTN/IN Requesting InTernet Service".) The purpose of the protocol is to support services that originate in the Public Switched Telephone Network (PSTN) and necessitate the interactions between the PSTN and the Internet. Similarly, such services are called SPIRITS services. (Internet Call Waiting, Internet Caller-ID Delivery, and Internet Call Forwarding are examples of SPIRIT services, but the protocol is to define the building blocks from which many other services can be built.) On the PSTN side, the SPIRITS services are initiated from the Intelligent Network (IN) entities; the earlier IETF work on the PSTN/Internet Interworking (PINT) resulted in the protocol (RFC 2848) in support of the services initiated the other way around--from the Internet to PSTN. To this end, this document lists general requirements for the SPIRITS protocol as well as those pertinent to IN, Wireless IN, and PINT building blocks. The document also presents the SPIRITS WG consensus on the choice of the SPIRITS signaling protocol. This document is a product of the Service in the PSTN/IN Requesting InTernet Service Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020903165114.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3298 --OtherAccess Content-Type: Message/External-body; name="rfc3298.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020903165114.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Sep 3 16:56:26 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g83NuQC09304; Tue, 3 Sep 2002 16:56:26 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g83NuQD02909; Tue, 3 Sep 2002 16:56:26 -0700 (PDT) Message-Id: <200209032356.g83NuQD02909@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 03 Sep 2002 16:56:26 -0700 Subject: [rfc-dist] RFC 3306 on Unicast-Prefix-based IPv6 Multicast Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3306 Title: Unicast-Prefix-based IPv6 Multicast Addresses Author(s): B. Haberman, D. Thaler Status: Standards Track Date: August 2002 Mailbox: bkhabs@nc.rr.com, dthaler@microsoft.com Pages: 7 Characters: 12713 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ipngwg-uni-based-mcast-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3306.txt This specification defines an extension to the multicast addressing architecture of the IP Version 6 protocol. The extension presented in this document allows for unicast-prefix-based allocation of multicast addresses. By delegating multicast addresses at the same time as unicast prefixes, network operators will be able to identify their multicast addresses without needing to run an inter-domain allocation protocol. This document is a product of the IPNG Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020903165435.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3306 --OtherAccess Content-Type: Message/External-body; name="rfc3306.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020903165435.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Sep 3 16:58:32 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g83NwWC12053; Tue, 3 Sep 2002 16:58:32 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g83NwVD03376; Tue, 3 Sep 2002 16:58:31 -0700 (PDT) Message-Id: <200209032358.g83NwVD03376@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 03 Sep 2002 16:58:31 -0700 Subject: [rfc-dist] RFC 3307 on IPv6 Multicast Addresses Guidelines Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3307 Title: Allocation Guidelines for IPv6 Multicast Addresses Author(s): B. Haberman Status: Standards Track Date: August 2002 Mailbox: bkhabs@nc.rr.com Pages: 8 Characters: 15742 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-malloc-ipv6-guide-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3307.txt This document specifies guidelines that must be implemented by any entity responsible for allocating IPv6 multicast addresses. This includes, but is not limited to, any documents or entities wishing to assign permanent IPv6 multicast addresses, allocate dynamic IPv6 multicast addresses, and define permanent IPv6 multicast group identifiers. The purpose of these guidelines is to reduce the probability of IPv6 multicast address collision, not only at the IPv6 layer, but also at the link-layer of media that encode portions of the IP layer address into the MAC layer address. This document is a product of the Multicast-Address Allocation Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020903165634.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3307 --OtherAccess Content-Type: Message/External-body; name="rfc3307.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020903165634.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Sep 3 17:00:21 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8400LC14465; Tue, 3 Sep 2002 17:00:21 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8400KD04557; Tue, 3 Sep 2002 17:00:20 -0700 (PDT) Message-Id: <200209040000.g8400KD04557@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 03 Sep 2002 17:00:20 -0700 Subject: [rfc-dist] RFC 3362 on MIME Sub-type image/t38 Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3362 Title: Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration Author(s): G. Parsons Status: Standards Track Date: August 2002 Mailbox: gparsons@nortelnetworks.com Pages: 5 Characters: 8301 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-parsons-itu-t38-reg-00.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3362.txt This document describes the registration of the MIME sub-type image/t38. The encoding is defined by ITU Recommendation T.38 and is intended for use as an Session Description Protocol (SDP) media descriptor. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020903165908.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3362 --OtherAccess Content-Type: Message/External-body; name="rfc3362.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020903165908.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Sep 5 09:39:44 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g85GdiC08724; Thu, 5 Sep 2002 09:39:44 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g85GdiD08610; Thu, 5 Sep 2002 09:39:44 -0700 (PDT) Message-Id: <200209051639.g85GdiD08610@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 05 Sep 2002 09:39:43 -0700 Subject: [rfc-dist] BCP 62, RFC 3366 on Advice to link designers on link Automatic Repeat reQuest (ARQ) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. BCP 62 RFC 3366 Title: Advice to link designers on link Automatic Repeat reQuest (ARQ) Author(s): G. Fairhurst, L. Wood Status: Best Current Practice Date: August 2002 Mailbox: gorry@erg.abdn.ac.uk, lwood@cisco.com Pages: 27 Characters: 66097 SeeAlso: BCP 62 I-D Tag: draft-ietf-pilc-link-arq-issues-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3366.txt This document provides advice to the designers of digital communication equipment and link-layer protocols employing link-layer Automatic Repeat reQuest (ARQ) techniques. This document presumes that the designers wish to support Internet protocols, but may be unfamiliar with the architecture of the Internet and with the implications of their design choices for the performance and efficiency of Internet traffic carried over their links. ARQ is described in a general way that includes its use over a wide range of underlying physical media, including cellular wireless, wireless LANs, RF links, and other types of channel. This document also describes issues relevant to supporting IP traffic over physical-layer channels where performance varies, and where link ARQ is likely to be used. This document is a product of the Performance Implications of Link Characteristics Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020905093740.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3366 --OtherAccess Content-Type: Message/External-body; name="rfc3366.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020905093740.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Sep 5 09:51:08 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g85Gp8C17833; Thu, 5 Sep 2002 09:51:08 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g85Gp7D16387; Thu, 5 Sep 2002 09:51:08 -0700 (PDT) Message-Id: <200209051651.g85Gp7D16387@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 05 Sep 2002 09:51:07 -0700 Subject: [rfc-dist] RFC 3369 on Cryptographic Message Syntax (CMS) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3369 Title: Cryptographic Message Syntax (CMS) Author(s): R. Housley Status: Standards Track Date: August 2002 Mailbox: rhousley@rsasecurity.com Pages: 52 Characters: 113975 Obsoletes: 2630, 3211 I-D Tag: draft-ietf-smime-rfc2630bis-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3369.txt This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. This document is a product of the S/MIME Mail Security Working Group of the IETF. This is now a Proposed Standard Protcol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020905094000.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3369 --OtherAccess Content-Type: Message/External-body; name="rfc3369.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020905094000.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Sep 5 09:53:23 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g85GrNC19639; Thu, 5 Sep 2002 09:53:23 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g85GrLD18293; Thu, 5 Sep 2002 09:53:21 -0700 (PDT) Message-Id: <200209051653.g85GrLD18293@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 05 Sep 2002 09:53:20 -0700 Subject: [rfc-dist] RFC 3370 on Cryptographic Message Syntax (CMS) Algorithms Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3370 Title: Cryptographic Message Syntax (CMS) Algorithms Author(s): R. Housley Status: Standards Track Date: August 2002 Mailbox: rhousley@rsasecurity.com Pages: 24 Characters: 51001 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-cmsalg-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3370.txt This document describes the conventions for using several cryptographic algorithms with the Cryptographic Message Syntax (CMS). The CMS is used to digitally sign, digest, authenticate, or encrypt arbitrary message contents. This document is a product of the S/MIME Mail Security Working Group of the IETF. This is now a Proposed Standard. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020905095135.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3370 --OtherAccess Content-Type: Message/External-body; name="rfc3370.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020905095135.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Sep 5 16:38:18 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g85NcIC16765; Thu, 5 Sep 2002 16:38:18 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g85NcHD28523; Thu, 5 Sep 2002 16:38:17 -0700 (PDT) Message-Id: <200209052338.g85NcHD28523@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 05 Sep 2002 16:38:17 -0700 Subject: [rfc-dist] RFC 3355 on Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3355 Title: Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5) Author(s): A. Singh, R. Turner, R. Tio, S. Nanji Status: Standards Track Date: August 2002 Mailbox: rturner@eng.paradyne.com, tor@redback.com, asingh1@motorola.com, suhail@redback.com Pages: 13 Characters: 25114 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2tpext-l2tp-atm-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3355.txt The Layer Two Tunneling Protocol (L2TP) provides a standard method for transporting the link layer of the Point-to-Point Protocol (PPP) between a dial-up server and a Network Access Server, using a network connection in lieu of a physical point-to-point connection. This document describes the use of an Asynchronous Transfer Mode (ATM) network for the underlying network connection. ATM User-Network Interface (UNI) Signaling Specification Version 4.0 or Version 3.1 with ATM Adaptation Layer 5 (AAL5) are supported as interfaces to the ATM network. This document is a product of the Layer Two Tunneling Protocol Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020905163615.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3355 --OtherAccess Content-Type: Message/External-body; name="rfc3355.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020905163615.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Sep 5 16:40:46 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g85NejC18933; Thu, 5 Sep 2002 16:40:45 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g85NejD29654; Thu, 5 Sep 2002 16:40:45 -0700 (PDT) Message-Id: <200209052340.g85NejD29654@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 05 Sep 2002 16:40:45 -0700 Subject: [rfc-dist] RFC 3367 on Common Name Resolution Protocol (CNRP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3367 Title: Common Name Resolution Protocol (CNRP) Author(s): N. Popp, M. Mealling, M. Moseley Status: Standards Track Date: August 2002 Mailbox: npopp@verisign.com, michael@verisignlabs.com, marshall@netword.com Pages: 42 Characters: 86889 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-cnrp-12.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3367.txt People often refer to things in the real world by a common name or phrase, e.g., a trade name, company name, or a book title. These names are sometimes easier for people to remember and type than URLs. Furthermore, because of the limited syntax of URLs, companies and individuals are finding that the ones that might be most reasonable for their resources are being used elsewhere and so are unavailable. For the purposes of this document, a "common name" is a word or a phrase, without imposed syntactic structure, that may be associated with a resource. This effort is about the creation of a protocol for client applications to communicate with common name resolution services, as exemplified in both the browser enhancement and search site paradigms. Although the protocol's primary function is resolution, it is also intended to address issues of internationalization and localization. Name resolution services are not generic search services and thus do not need to provide complex Boolean query, relevance ranking or similar capabilities. The protocol is a simple, minimal interoperable core. Mechanisms for extension are provided, so that additional capabilities can be added. This document is a product of the Common Name Resolution Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020905163854.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3367 --OtherAccess Content-Type: Message/External-body; name="rfc3367.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020905163854.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Sep 5 16:45:53 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g85NjqC23991; Thu, 5 Sep 2002 16:45:52 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g85NjpD01669; Thu, 5 Sep 2002 16:45:52 -0700 (PDT) Message-Id: <200209052345.g85NjpD01669@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 05 Sep 2002 16:45:51 -0700 Subject: [rfc-dist] RFC 3371 on Layer Two Tunneling Protocol "L2TP" Management Information Base Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3371 Title: Layer Two Tunneling Protocol "L2TP" Management Information Base Author(s): E. Caves, P. Calhoun, R. Wheeler Status: Standards Track Date: August 2002 Mailbox: evan@occamnetworks.com, pcalhoun@bstormnetworks.com, ross@doublewidesoft.com Pages: 70 Characters: 139974 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2tpext-l2tp-mib-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3371.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing networks using Layer 2 Tunneling Protocol (L2TP). This document is a product of the Layer Two Tunneling Protocol Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020905164339.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3371 --OtherAccess Content-Type: Message/External-body; name="rfc3371.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020905164339.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 16 10:18:51 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8GHIpC00127; Mon, 16 Sep 2002 10:18:51 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8GHIpD04019; Mon, 16 Sep 2002 10:18:51 -0700 (PDT) Message-Id: <200209161718.g8GHIpD04019@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 16 Sep 2002 10:18:51 -0700 Subject: [rfc-dist] RFC 3344 on IP Mobility Support for IPv4 Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3344 Title: IP Mobility Support for IPv4 Author(s): C. Perkins, Ed. Status: Standards Track Date: August 2002 Mailbox: charliep@iprg.nokia.com Pages: 99 Characters: 241041 Obsoletes: 3220 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3344.txt This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about its current point of attachment to the Internet. The protocol provides for registering the care-of address with a home agent. The home agent sends datagrams destined for the mobile node through a tunnel to the care-of address. After arriving at the end of the tunnel, each datagram is then delivered to the mobile node. This document is a product of the IP Routing for Wireless/Mobile Hosts Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020916101720.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3344 --OtherAccess Content-Type: Message/External-body; name="rfc3344.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020916101720.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 16 16:52:47 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNqlC22576; Mon, 16 Sep 2002 16:52:47 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNqkD20270; Mon, 16 Sep 2002 16:52:46 -0700 (PDT) Message-Id: <200209162352.g8GNqkD20270@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 16 Sep 2002 16:52:46 -0700 Subject: [rfc-dist] RFC 3335 on MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3335 Title: MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet Author(s): T. Harding, R. Drummond, C. Shih Status: Standards Track Date: September 2002 Mailbox: tharding@cyclonecommerce.com, chuck.shih@gartner.com, rik@drummondgroup.com Pages: 29 Characters: 59687 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ediint-asl-17.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3335.txt This document describes how to exchange structured business data securely using SMTP transport for Electronic Data Interchange, (EDI - either the American Standards Committee X12 or UN/EDIFACT, Electronic Data Interchange for Administration, Commerce and Transport), XML or other data used for business to business data interchange. The data is packaged using standard MIME content-types. Authentication and privacy are obtained by using Cryptographic Message Syntax (S/MIME) or OpenPGP security body parts. Authenticated acknowledgements make use of multipart/signed replies to the original SMTP message. This document is a product of the Electronic Data Interchange-Internet Integration Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020916165050.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3335 --OtherAccess Content-Type: Message/External-body; name="rfc3335.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020916165050.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 16 16:54:59 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNsxC24818; Mon, 16 Sep 2002 16:54:59 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNsxD21211; Mon, 16 Sep 2002 16:54:59 -0700 (PDT) Message-Id: <200209162354.g8GNsxD21211@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 16 Sep 2002 16:54:58 -0700 Subject: [rfc-dist] BCP 63, RFC 3372 on Session Initiation Protocol for Telephones (SIP-T): Context and Architectures Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. BCP 63 RFC 3372 Title: Session Initiation Protocol (SIP) for Telephones (SIP-T): Context and Architectures Author(s): A. Vemuri, J. Peterson Status: Best Current Practice Date: September 2002 Mailbox: Aparna.Vemuri@Qwest.com, jon.peterson@neustar.biz Pages: 22 Characters: 49893 SeeAlso: BCP 63 I-D Tag: draft-ietf-sipping-sipt-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3372.txt The popularity of gateways that interwork between the PSTN (Public Switched Telephone Network) and SIP networks has motivated the publication of a set of common practices that can assure consistent behavior across implementations. This document taxonomizes the uses of PSTN-SIP gateways, provides uses cases, and identifies mechanisms necessary for interworking. The mechanisms detail how SIP provides for both 'encapsulation' (bridging the PSTN signaling across a SIP network) and 'translation' (gatewaying). This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020916165310.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3372 --OtherAccess Content-Type: Message/External-body; name="rfc3372.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020916165310.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 16 16:57:28 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNvSC26691; Mon, 16 Sep 2002 16:57:28 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNvSD22029; Mon, 16 Sep 2002 16:57:28 -0700 (PDT) Message-Id: <200209162357.g8GNvSD22029@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 16 Sep 2002 16:57:28 -0700 Subject: [rfc-dist] RFC 3374 on Context Transfer Problem Statement Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3374 Title: Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network Author(s): J. Kempf, Ed. Status: Informational Date: September 2002 Mailbox: kempf@docomolabs-usa.com Pages: 14 Characters: 28245 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-seamoby-context-transfer-problem-stat-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3374.txt In IP access networks that support host mobility, the routing paths between the host and the network may change frequently and rapidly. In some cases, the host may establish certain context transfer candidate services on subnets that are left behind when the host moves. Examples of such services are Authentication, Authorization, and Accounting (AAA), header compression, and Quality of Service (QoS). In order for the host to obtain those services on the new subnet, the host must explicitly re-establish the service by performing the necessary signaling flows from scratch. In some cases, this process would considerably slow the process of establishing the mobile host on the new subnet. An alternative is to transfer information on the existing state associated with these services, or context, to the new subnet, a process called "context transfer". This document discusses the desirability of context transfer for facilitating seamless IP mobility. This document is a product of the Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting Working Group. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020916165535.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3374 --OtherAccess Content-Type: Message/External-body; name="rfc3374.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020916165535.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 16 16:59:21 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNxLC28231; Mon, 16 Sep 2002 16:59:21 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8GNxLD22362; Mon, 16 Sep 2002 16:59:21 -0700 (PDT) Message-Id: <200209162359.g8GNxLD22362@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 16 Sep 2002 16:59:20 -0700 Subject: [rfc-dist] RFC 3375 on Generic Registry-Registrar Protocol Requirements Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3375 Title: Generic Registry-Registrar Protocol Requirements Author(s): S. Hollenbeck Status: Informational Date: September 2002 Mailbox: shollenbeck@verisign.com Pages: 21 Characters: 46022 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-provreg-grrp-reqs-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3375.txt This document describes high-level functional and interface requirements for a client-server protocol for the registration and management of Internet domain names in shared registries. Specific technical requirements detailed for protocol design are not presented here. Instead, this document focuses on the basic functions and interfaces required of a protocol to support multiple registry and registrar operational models. This document is a product of the Provisioning Registry Protocl Working Group. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020916165757.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3375 --OtherAccess Content-Type: Message/External-body; name="rfc3375.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020916165757.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Sep 18 17:19:17 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8J0JGC03655; Wed, 18 Sep 2002 17:19:17 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8J0JGD00067; Wed, 18 Sep 2002 17:19:16 -0700 (PDT) Message-Id: <200209190019.g8J0JGD00067@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org, ietf-ldapbis@openldap.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 18 Sep 2002 17:19:16 -0700 Subject: [rfc-dist] RFC 3377 on Lightweight Directory Access Protocol (v3): Technical Specification Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3377 Title: Lightweight Directory Access Protocol (v3): Technical Specification Author(s): J. Hodges, R. Morgan Status: Standards Track Date: September 2002 Mailbox: Jeff.Hodges@sun.com, rlmorgan@washington.edu Pages: 6 Characters: 9981 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ldapbis-ldapv3-ts-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3377.txt This document specifies the set of RFCs comprising the Lightweight Directory Access Protocol Version 3 (LDAPv3), and addresses the "IESG Note" attached to RFCs 2251 through 2256. This document is a product of the LDAP (v3) Revision Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020916165947.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3377 --OtherAccess Content-Type: Message/External-body; name="rfc3377.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020916165947.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Sep 18 17:21:37 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8J0LaC06181; Wed, 18 Sep 2002 17:21:37 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8J0LaD01536; Wed, 18 Sep 2002 17:21:36 -0700 (PDT) Message-Id: <200209190021.g8J0LaD01536@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 18 Sep 2002 17:21:36 -0700 Subject: [rfc-dist] RFC 3379 on Delegated Path Validation and Delegated Path Discovery Protocol Requirements Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3379 Title: Delegated Path Validation and Delegated Path Discovery Protocol Requirements Author(s): D. Pinkas, R. Housley Status: Informational Date: September 2002 Mailbox: Denis.Pinkas@bull.net, rhousley@rsasecurity.com Pages: 15 Characters: 32455 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-dpv-dpd-req-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3379.txt This document specifies the requirements for Delegated Path Validation (DPV) and Delegated Path Discovery (DPD) for Public Key Certificates. It also specifies the requirements for DPV and DPD policy management. This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020918171928.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3379 --OtherAccess Content-Type: Message/External-body; name="rfc3379.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020918171928.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 20 09:44:10 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8KGiAC14752; Fri, 20 Sep 2002 09:44:10 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KGiAD01341; Fri, 20 Sep 2002 09:44:10 -0700 (PDT) Message-Id: <200209201644.g8KGiAD01341@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 20 Sep 2002 09:44:10 -0700 Subject: [rfc-dist] RFC 3373 on Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3373 Title: Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies Author(s): D. Katz, R. Saluja Status: Informational Date: September 2002 Mailbox: dkatz@juniper.net, rajesh.saluja@tenetindia.com Pages: 9 Characters: 19522 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-3way-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3373.txt The IS-IS routing protocol (ISO 10589) requires reliable protocols at the link layer for point-to-point links. As a result, it does not use a three-way handshake when establishing adjacencies on point-to-point media. This paper defines a backward-compatible extension to the protocol that provides for a three-way handshake. It is fully interoperable with systems that do not support the extension. Additionally, the extension allows the robust operation of more than 256 point-to-point links on a single router. This extension has been implemented by multiple router vendors; this paper is provided as information to the Internet community in order to allow interoperable implementations to be built by other vendors. This document is a product of the IS-IS for IP Internets Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020920094220.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3373 --OtherAccess Content-Type: Message/External-body; name="rfc3373.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020920094220.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 20 09:48:59 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8KGmxC19938; Fri, 20 Sep 2002 09:48:59 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KGmxD03907; Fri, 20 Sep 2002 09:48:59 -0700 (PDT) Message-Id: <200209201648.g8KGmxD03907@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 20 Sep 2002 09:48:59 -0700 Subject: [rfc-dist] BCP 64, RFC 3383 on Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. BCP 64 RFC 3383 Title: Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) Author(s): K. Zeilenga Status: Best Current Practice Date: September 2002 Mailbox: Kurt@OpenLDAP.org Pages: 22 Characters: 45893 SeeAlso: BCP 64 I-D Tag: draft-ietf-ldapbis-iana-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3383.txt This document provides procedures for registering extensible elements of the Lightweight Directory Access Protocol (LDAP). This document also provides guidelines to the Internet Assigned Numbers Authority (IANA) describing conditions under which new values can be assigned. This document is a product of the LDAP (v3) Revision Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020920094515.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3383 --OtherAccess Content-Type: Message/External-body; name="rfc3383.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020920094515.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 20 15:21:37 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMLaC23203; Fri, 20 Sep 2002 15:21:36 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMLaD24234; Fri, 20 Sep 2002 15:21:36 -0700 (PDT) Message-Id: <200209202221.g8KMLaD24234@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 20 Sep 2002 15:21:36 -0700 Subject: [rfc-dist] RFC 3310 on Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3310 Title: Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Author(s): A. Niemi, J. Arkko, V. Torvinen Status: Informational Date: September 2002 Mailbox: aki.niemi@nokia.com, jari.arkko@ericsson.com, vesa.torvinen@ericsson.fi Pages: 18 Characters: 36985 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sip-digest-aka-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3310.txt This memo specifies an Authentication and Key Agreement (AKA) based one-time password generation mechanism for Hypertext Transfer Protocol (HTTP) Digest access authentication. The HTTP Authentication Framework includes two authentication schemes: Basic and Digest. Both schemes employ a shared secret based mechanism for access authentication. The AKA mechanism performs user authentication and session key distribution in Universal Mobile Telecommunications System (UMTS) networks. AKA is a challenge-response based mechanism that uses symmetric cryptography. This document is a product of the Session Initiation Protocol Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020920151959.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3310 --OtherAccess Content-Type: Message/External-body; name="rfc3310.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020920151959.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 20 15:23:38 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMNcC24735; Fri, 20 Sep 2002 15:23:38 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMNcD25092; Fri, 20 Sep 2002 15:23:38 -0700 (PDT) Message-Id: <200209202223.g8KMNcD25092@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 20 Sep 2002 15:23:38 -0700 Subject: [rfc-dist] RFC 3314 on Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3314 Title: Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards Author(s): M. Wasserman, Ed. Status: Informational Date: September 2002 Mailbox: mrw@windriver.com Pages: 23 Characters: 48168 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipv6-3gpp-recommend-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3314.txt This document contains recommendations from the Internet Engineering Task Force (IETF) IPv6 Working Group to the Third Generation Partnership Project (3GPP) community regarding the use of IPv6 in the 3GPP standards. Specifically, this document recommends that the 3GPP specify that multiple prefixes may be assigned to each primary PDP context, require that a given prefix must not be assigned to more than one primary PDP context, and allow 3GPP nodes to use multiple identifiers within those prefixes, including randomly generated identifiers. The IPv6 Working Group supports the use of IPv6 within 3GPP and offers these recommendations in a spirit of open cooperation between the IPv6 Working Group and the 3GPP community. Since the original publication of this document as an Internet-Draft, the 3GPP has adopted the primary recommendations of this document. This document is a product of the IP Version 6 Working Group Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020920152204.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3314 --OtherAccess Content-Type: Message/External-body; name="rfc3314.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020920152204.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 20 15:25:46 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMPkC27436; Fri, 20 Sep 2002 15:25:46 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMPkD25822; Fri, 20 Sep 2002 15:25:46 -0700 (PDT) Message-Id: <200209202225.g8KMPkD25822@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 20 Sep 2002 15:25:46 -0700 Subject: [rfc-dist] RFC 3331 on Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3331 Title: Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer Author(s): K. Morneault, R. Dantu, G. Sidebottom, B. Bidulock, J. Heitz Status: Standards Track Date: September 2002 Mailbox: kmorneau@cisco.com, rdantu@netrake.com, greg@signatustechnologies.com, bidulock@openss7.org, jheitz@lucent.com Pages: 94 Characters: 210807 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sigtran-m2ua-15.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3331.txt This document defines a protocol for the backhauling of Signaling System 7 Message Transfer Part 2 (SS7 MTP2) User signalling messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol would be used between a Signalling Gateway (SG) and Media Gateway Controller (MGC). It is assumed that the SG receives SS7 signalling over a standard SS7 interface using the SS7 Message Transfer Part (MTP) to provide transport. The Signalling Gateway would act as a Signalling Link Terminal. This document is a product of the Signaling Transport Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020920152402.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3331 --OtherAccess Content-Type: Message/External-body; name="rfc3331.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020920152402.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 20 15:28:41 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMSfC00532; Fri, 20 Sep 2002 15:28:41 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMSfD26852; Fri, 20 Sep 2002 15:28:41 -0700 (PDT) Message-Id: <200209202228.g8KMSfD26852@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 20 Sep 2002 15:28:40 -0700 Subject: [rfc-dist] RFC 3332 on Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3332 Title: Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA) Author(s): G. Sidebottom, K. Morneault, J. Pastor-Balbas Status: Standards Track Date: September 2002 Mailbox: greg@signatustechnologies.com, kmorneau@cisco.com, j.javier.pastor@ericsson.com Pages: 120 Characters: 265055 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sigtran-m3ua-12.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3332.txt This memo defines a protocol for supporting the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services of the Stream Control Transmission Protocol. Also, provision is made for protocol elements that enable a seamless operation of the MTP3-User peers in the SS7 and IP domains. This protocol would be used between a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP-resident Database, or between two IP-based applications. It is assumed that the SG receives SS7 signalling over a standard SS7 interface using the SS7 Message Transfer Part (MTP) to provide transport. This document is a product of the Signaling Transport Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020920152607.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3332 --OtherAccess Content-Type: Message/External-body; name="rfc3332.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020920152607.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 20 15:30:32 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMUWC02453; Fri, 20 Sep 2002 15:30:32 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMUWD27084; Fri, 20 Sep 2002 15:30:32 -0700 (PDT) Message-Id: <200209202230.g8KMUWD27084@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 20 Sep 2002 15:30:32 -0700 Subject: [rfc-dist] RFC 3378 on EtherIP: Tunneling Ethernet Frames in IP Datagrams Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3378 Title: EtherIP: Tunneling Ethernet Frames in IP Datagrams Author(s): R. Housley, S. Hollenbeck Status: Informational Date: September 2002 Mailbox: rhousley@rsasecurity.com, shollenbeck@verisign.com Pages: 9 Characters: 18803 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-housley-etherip-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3378.txt This document describes the EtherIP, an early tunneling protocol, to provide informational and historical context for the assignment of IP protocol 97. EtherIP tunnels Ethernet and IEEE 802.3 media access control frames in IP datagrams so that non-IP traffic can traverse an IP internet. The protocol is very lightweight, and it does not provide protection against infinite loops. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020920152902.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3378 --OtherAccess Content-Type: Message/External-body; name="rfc3378.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020920152902.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Sep 25 17:30:11 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8Q0UAC28877; Wed, 25 Sep 2002 17:30:10 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8Q0UAD23184; Wed, 25 Sep 2002 17:30:10 -0700 (PDT) Message-Id: <200209260030.g8Q0UAD23184@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 25 Sep 2002 17:30:10 -0700 Subject: [rfc-dist] RFC 3249 on Implementers Guide for Facsimile Using Internet Mail Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3249 Title: Implementers Guide for Facsimile Using Internet Mail Author(s): V. Cancio, M. Moldovan, H. Tamura, D. Wing Status: Informational Date: September 2002 Mailbox: vcancio@pacbell.net, mmoldovan@g3nova.com, tamura@toda.ricoh.co.jp, dwing@cisco.com Pages: 21 Characters: 40413 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-fax-implementers-guide-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3249.txt This document is intended for the implementers of software that use email to send to facsimiles using RFC 2305 and 2532. This is an informational document and its guidelines do not supersede the referenced documents. This document is a product of the Internet Fax Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020925172727.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3249 --OtherAccess Content-Type: Message/External-body; name="rfc3249.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020925172727.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Sep 25 17:32:10 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8Q0W9C00054; Wed, 25 Sep 2002 17:32:09 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8Q0W9D23823; Wed, 25 Sep 2002 17:32:09 -0700 (PDT) Message-Id: <200209260032.g8Q0W9D23823@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 25 Sep 2002 17:32:09 -0700 Subject: [rfc-dist] RFC 3250 on Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3250 Title: Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration Author(s): L. McIntyre, G. Parsons, J. Rafferty Status: Standards Track Date: September 2002 Mailbox: lmcintyre@pahv.xerox.com, gparsons@nortelnetworks.com, jraff@brooktrout.com Pages: 7 Characters: 17876 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-fax-tiff-fx-reg-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3250.txt This document describes the registration of the MIME sub-type image/tiff-fx. The encodings are defined by File Format for Internet Fax and its extensions. This document is a product of the Internet Fax Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020925173029.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3250 --OtherAccess Content-Type: Message/External-body; name="rfc3250.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020925173029.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Sep 27 16:13:41 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8RNDfC21504; Fri, 27 Sep 2002 16:13:41 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8RNDfD16463; Fri, 27 Sep 2002 16:13:41 -0700 (PDT) Message-Id: <200209272313.g8RNDfD16463@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 27 Sep 2002 16:13:41 -0700 Subject: [rfc-dist] RFC 3302 on Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3302 Title: Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration Author(s): G. Parsons, J. Rafferty Status: Standards Track Date: September 2002 Mailbox: gparsons@nortelnetworks.com, jraff@brooktrout.com Pages: 8 Characters: 15183 Obsoletes: 2302 I-D Tag: draft-ietf-fax-tiff-regbis-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3302.txt This document describes the registration of the MIME sub-type image/tiff. This document refines an earlier sub-type registration in RFC 1528. This document obsoletes RFC 2302. This document is a product of the Internet Fax Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020927161038.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3302 --OtherAccess Content-Type: Message/External-body; name="rfc3302.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020927161038.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 30 15:22:31 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8UMMVC05946; Mon, 30 Sep 2002 15:22:31 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8UMMVD10413; Mon, 30 Sep 2002 15:22:31 -0700 (PDT) Message-Id: <200209302222.g8UMMVD10413@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 30 Sep 2002 15:22:30 -0700 Subject: [rfc-dist] RFC 3309 on Stream Control Transmission Protocol (SCTP) Checksum Change Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3309 Title: Stream Control Transmission Protocol (SCTP) Checksum Change Author(s): J. Stone, R. Stewart, D. Otis Status: Standards Track Date: September 2002 Mailbox: jonathan@dsg.stanford.edu, rrs@cisco.com, dotis@sanlight.net Pages: 17 Characters: 34670 Updates: 2960 I-D Tag: draft-ietf-tsvwg-sctpcsum-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3309.txt Stream Control Transmission Protocol (SCTP) currently uses an Adler-32 checksum. For small packets Adler-32 provides weak detection of errors. This document changes that checksum and updates SCTP to use a 32 bit CRC checksum. This document is a product of the Transport Area Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020930152029.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3309 --OtherAccess Content-Type: Message/External-body; name="rfc3309.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020930152029.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 30 15:29:51 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8UMTpC12249; Mon, 30 Sep 2002 15:29:51 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8UMTpD12502; Mon, 30 Sep 2002 15:29:51 -0700 (PDT) Message-Id: <200209302229.g8UMTpD12502@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 30 Sep 2002 15:29:51 -0700 Subject: [rfc-dist] RFC 3395 on Remote Network Monitoring MIB Protocol Identifier Reference Extensions Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3395 Title: Remote Network Monitoring MIB Protocol Identifier Reference Extensions Author(s): A. Bierman, C. Bucci, R. Dietz, A. Warth Status: Standards Track Date: September 2002 Mailbox: abierman@cisco.com, cbucci@cisco.com, rdietz@hifn.com, dahoss@earthlink.net Pages: 21 Characters: 43862 Updates: 2895 I-D Tag: draft-ietf-rmonmib-appverbs-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3395.txt This memo defines extensions to the Protocol Identifier Reference document for the identification of application verb information. It updates the Protocol Identifier Reference document but does not obsolete any portion of that document. In particular, it describes the algorithms required to identify protocol operations (verbs) within the protocol encapsulations managed with MIBs such as the Remote Network Monitoring MIB Version 2, RFC 2021. This document is a product of the Remote Network Monitoring Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020930152618.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3395 --OtherAccess Content-Type: Message/External-body; name="rfc3395.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020930152618.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Mon Sep 30 15:25:02 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8UMP2C08005; Mon, 30 Sep 2002 15:25:02 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8UMP2D11255; Mon, 30 Sep 2002 15:25:02 -0700 (PDT) Message-Id: <200209302225.g8UMP2D11255@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 30 Sep 2002 15:25:02 -0700 Subject: [rfc-dist] RFC 3385 on Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3385 Title: Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations Author(s): D. Sheinwald, J. Satran, P. Thaler, V. Cavanna Status: Informational Date: September 2002 Mailbox: julian_satran@il.ibm.com, Dafna_Sheinwald@il.ibm.com, pat_thaler@agilent.com, vince_cavanna@agilent.com, Pages: 23 Characters: 53450 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-sheinwald-iscsi-crc-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3385.txt In this memo, we attempt to give some estimates for the probability of undetected errors to facilitate the selection of an error detection code for the Internet Protocol Small Computer System Interface (iSCSI). We will also attempt to compare Cyclic Redundancy Checks (CRCs) with other checksum forms (e.g., Fletcher, Adler, weighted checksums), as permitted by available data. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020930152258.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3385 --OtherAccess Content-Type: Message/External-body; name="rfc3385.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020930152258.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Oct 1 15:37:50 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g91MboC05521; Tue, 1 Oct 2002 15:37:50 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g91MboD11917; Tue, 1 Oct 2002 15:37:50 -0700 (PDT) Message-Id: <200210012237.g91MboD11917@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 01 Oct 2002 15:37:50 -0700 Subject: [rfc-dist] RFC 3380 Internet Printing Protocol (IPP): Job and Printer Set Operations Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3380 Title: Internet Printing Protocol (IPP): Job and Printer Set Operations Author(s): T. Hastings, R. Herriot, C. Kugler, H. Lewis Status: Standards Track Date: September 2002 Mailbox: hastings@cp10.es.xerox.com, bob@Herriot.com, kugler@us.ibm.com, harryl@us.ibm.com Pages: 58 Characters: 131635 Updates: 2910, 2911 I-D Tag: draft-ietf-ipp-job-printer-set-ops-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3380.txt This document is an OPTIONAL extension to the Internet Printing Protocol (IPP/1.0 and IPP/1.1). This document specifies 3 additional OPTIONAL operations for use with the Internet Printing Protocol/1.0 (IPP) and IPP/1.1. The end user, operator, and administrator Set-Job-Attributes and Set-Printer-Attributes operations are used to modify IPP Job objects and Printer objects, respectively. The Get-Printer-Supported-Values administrative operation returns values that the IPP Printer will accept for setting its "xxx-supported" attributes. This document is a product of the Internet Printing Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021001152742.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3380 --OtherAccess Content-Type: Message/External-body; name="rfc3380.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021001152742.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Oct 1 16:38:25 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g91NcOC20121; Tue, 1 Oct 2002 16:38:24 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g91NcOD12332; Tue, 1 Oct 2002 16:38:24 -0700 (PDT) Message-Id: <200210012338.g91NcOD12332@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 01 Oct 2002 16:38:24 -0700 Subject: [rfc-dist] RFC 3389 on Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3389 Title: Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) Author(s): R. Zopf Status: Standards Track Date: September 2002 Mailbox: zopf@lucent.com Pages: 8 Characters: 17018 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rtp-cn-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3389.txt This document describes a Real-time Transport Protocol (RTP) payload format for transporting comfort noise (CN). The CN payload type is primarily for use with audio codecs that do not support comfort noise as part of the codec itself such as ITU-T Recommendations G.711, G.726, G.727, G.728, and G.722. This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proopsed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021001163609.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3389 --OtherAccess Content-Type: Message/External-body; name="rfc3389.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021001163609.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Oct 1 16:42:11 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g91NgBC23574; Tue, 1 Oct 2002 16:42:11 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g91NgBD13750; Tue, 1 Oct 2002 16:42:11 -0700 (PDT) Message-Id: <200210012342.g91NgBD13750@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 01 Oct 2002 16:42:11 -0700 Subject: [rfc-dist] RFC 3394 on Advanced Encryption Standard (AES) Key Wrap Algorithm Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3394 Title: Advanced Encryption Standard (AES) Key Wrap Algorithm Author(s): J. Schaad, R. Housley Status: Informational Date: September 2002 Mailbox: jimsch@exmsft.com, rhousley@rsasecurity.com Pages: 40 Characters: 73072 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-aes-keywrap-00.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3394.txt The purpose of this document is to make the Advanced Encryption Standard (AES) Key Wrap algorithm conveniently available to the Internet community. The United States of America has adopted AES as the new encryption standard. The AES Key Wrap algorithm will probably be adopted by the USA for encryption of AES keys. The authors took most of the text in this document from the draft AES Key Wrap posted by NIST. This document is a product of the S/MIME Mail Security Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021001163900.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3394 --OtherAccess Content-Type: Message/External-body; name="rfc3394.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021001163900.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Oct 2 15:43:32 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g92MhWC29642; Wed, 2 Oct 2002 15:43:32 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g92MhWD08237; Wed, 2 Oct 2002 15:43:32 -0700 (PDT) Message-Id: <200210022243.g92MhWD08237@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 02 Oct 2002 15:43:32 -0700 Subject: [rfc-dist] RFC 3330 on Special-Use IPv4 Addresses Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3330 Title: Special-Use IPv4 Addresses Author(s): IANA Status: Informational Date: September 2002 Mailbox: iana@iana.org Pages: 7 Characters: 16200 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iana-special-ipv4-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3330.txt This document describes the global and other specialized IPv4 address blocks that have been assigned by the Internet Assigned Numbers Authority (IANA). It does not address IPv4 address space assigned to operators and users through the Regional Internet Registries. It also does not address allocations or assignments of IPv6 addresses or autonomous system numbers. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021002154204.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3330 --OtherAccess Content-Type: Message/External-body; name="rfc3330.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021002154204.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Oct 2 15:50:17 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g92MoHC07300; Wed, 2 Oct 2002 15:50:17 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g92MoHD10524; Wed, 2 Oct 2002 15:50:17 -0700 (PDT) Message-Id: <200210022250.g92MoHD10524@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 02 Oct 2002 15:50:16 -0700 Subject: [rfc-dist] RFC 3380 on Internet Printing Protocol (IPP): Job and Printer Set Operations Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3380 Title: Internet Printing Protocol (IPP): Job and Printer Set Operations Author(s): T. Hastings, R. Herriot, C. Kugler, H. Lewis Status: Standards Track Date: September 2002 Mailbox: hastings@cp10.es.xerox.com, bob@Herriot.com, kugler@us.ibm.com, harryl@us.ibm.com Pages: 58 Characters: 132044 Updates: 2910, 2911 I-D Tag: draft-ietf-ipp-job-printer-set-ops-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3380.txt This document is an OPTIONAL extension to the Internet Printing Protocol (IPP/1.0 and IPP/1.1). This document specifies 3 additional OPTIONAL operations for use with the Internet Printing Protocol/1.0 (IPP) and IPP/1.1. The end user, operator, and administrator Set-Job-Attributes and Set-Printer-Attributes operations are used to modify IPP Job objects and Printer objects, respectively. The Get-Printer-Supported-Values administrative operation returns values that the IPP Printer will accept for setting its "xxx-supported" attributes. This document is a product of the Internet Printing Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021002154413.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3380 --OtherAccess Content-Type: Message/External-body; name="rfc3380.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021002154413.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Oct 2 15:53:48 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g92MrmC12217; Wed, 2 Oct 2002 15:53:48 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g92MrmD13459; Wed, 2 Oct 2002 15:53:48 -0700 (PDT) Message-Id: <200210022253.g92MrmD13459@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 02 Oct 2002 15:53:47 -0700 Subject: [rfc-dist] RFC 3381 on Internet Printing Protocol (IPP): Job Progress Attributes Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3381 Title: Internet Printing Protocol (IPP): Job Progress Attributes Author(s): T. Hastings, H. Lewis, R. Bergman Status: Standards Track Date: September 2002 Mailbox: hastings@cp10.es.xerox.com, harryl@us.ibm.com, rbergma@hitachi-hkis.com Pages: 16 Characters: 34859 Updates: 2910 I-D Tag: draft-ietf-ipp-job-prog-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3381.txt This document defines four new Job Description attributes for monitoring job progress to be registered as OPTIONAL extensions to the Internet Printing Protocol (IPP/1.0 and IPP/1.1). These attributes are drawn from the PWG Job Monitoring MIB. This document also defines a new "sheet-collate" Job Template attribute to control sheet collation and to help with the interpretation of the job progress attributes. This document is a product of the Internet Printing Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021002155058.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3381 --OtherAccess Content-Type: Message/External-body; name="rfc3381.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021002155058.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Oct 2 15:57:00 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g92Mv0C15868; Wed, 2 Oct 2002 15:57:00 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g92Mv0D14664; Wed, 2 Oct 2002 15:57:00 -0700 (PDT) Message-Id: <200210022257.g92Mv0D14664@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 02 Oct 2002 15:57:00 -0700 Subject: [rfc-dist] RFC 3382 on Internet Printing Protocol (IPP): The 'collection' attribute syntax Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3382 Title: Internet Printing Protocol (IPP): The 'collection' attribute syntax Author(s): R. deBry, T. Hastings, R. Herriot, K. Ocke, P. Zehler Status: Standards Track Date: September 2002 Mailbox: debryro@uvsc.edu, hastings@cp10.es.xerox.com, bob@herriot.com, KOcke@crt.xerox.com, PZehler@crt.xerox.com Pages: 38 Characters: 78173 Updates: 2910, 2911 I-D Tag: draft-ietf-ipp-collection-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3382.txt This document specifies an OPTIONAL attribute syntax called 'collection' for use with the Internet Printing Protocol (IPP/1.0 and IPP/1.1). A 'collection' is a container holding one or more named values, which are called "member" attributes. A collection allows data to be grouped like a PostScript dictionary or a Java Map. This document also specifies the conformance requirements for a definition document that defines a collection attribute. Finally, this document gives some illustrative example collection attribute definitions that are not intended as actual attribute specifications. This document is a product of the Internet Printing Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021002155418.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3382 --OtherAccess Content-Type: Message/External-body; name="rfc3382.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021002155418.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Fri Oct 4 09:29:13 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g94GTDC02106; Fri, 4 Oct 2002 09:29:13 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g94GTCD15033; Fri, 4 Oct 2002 09:29:12 -0700 (PDT) Message-Id: <200210041629.g94GTCD15033@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 04 Oct 2002 09:29:12 -0700 Subject: [rfc-dist] RFC 3387 on Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3387 Title: Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network Author(s): M. Eder, H. Chaskar, S. Nag Status: Informational Date: September 2002 Mailbox: Michael.eder@nokia.com, thinker@monmouth.com, hemant.chaskar@nokia.com Pages: 19 Characters: 52693 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-smrg-ipsmf-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3387.txt The guiding principles in the design of IP network management were simplicity and no centralized control. The best effort service paradigm was a result of the original management principles and the other way around. New methods to distinguish the service given to one set of packets or flows relative to another are well underway. However, as IP networks evolve the management approach of the past may not apply to the Quality of Service (QoS)-capable network envisioned by some for the future. This document examines some of the areas of impact that QoS is likely to have on management and look at some questions that remain to be addressed. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021004092704.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3387 --OtherAccess Content-Type: Message/External-body; name="rfc3387.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021004092704.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Wed Oct 9 16:06:39 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g99N6dC04751; Wed, 9 Oct 2002 16:06:39 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g99N6dD23126; Wed, 9 Oct 2002 16:06:39 -0700 (PDT) Message-Id: <200210092306.g99N6dD23126@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 09 Oct 2002 16:06:38 -0700 Subject: [rfc-dist] RFC 3338 on Dual Stack Hosts Using "Bump-in-the-API" (BIA) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3338 Title: Dual Stack Hosts Using "Bump-in-the-API" (BIA) Author(s): S. Lee, M-K. Shin, Y-J. Kim, E. Nordmark, A. Durand Status: Experimental Date: October 2002 Mailbox: syl@pec.etri.re.kr, mkshin@pec.etri.re.kr, yjkim@pec.etri.re.kr, Alain.Durand@sun.com, erik.nordmark@sun.com Pages: 16 Characters: 34480 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ngtrans-bia-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3338.txt This document specifies a mechanism of dual stack hosts using a technique called "Bump-in-the-API"(BIA) which allows for the hosts to communicate with other IPv6 hosts using existing IPv4 applications. The goal of this mechanism is the same as that of the Bump-in-the-stack mechanism, but this mechanism provides the translation method between the IPv4 APIs and IPv6 APIs. Thus, the goal is simply achieved without IP header translation. This document is a product of the Next Generation Transition Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021009160431.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3338 --OtherAccess Content-Type: Message/External-body; name="rfc3338.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021009160431.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Oct 15 11:55:39 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9FItcC23825; Tue, 15 Oct 2002 11:55:38 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9FItcD19598; Tue, 15 Oct 2002 11:55:38 -0700 (PDT) Message-Id: <200210151855.g9FItcD19598@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 15 Oct 2002 11:55:38 -0700 Subject: [rfc-dist] RFC 3311 on The Session Initiation Protocol (SIP) UPDATE Method Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3311 Title: The Session Initiation Protocol (SIP) UPDATE Method Author(s): J. Rosenberg Status: Standards Track Date: October 2002 Mailbox: jdrosen@dynamicsoft.com Pages: 13 Characters: 28125 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sip-update-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3311.txt This specification defines the new UPDATE method for the Session Initiation Protocol (SIP). UPDATE allows a client to update parameters of a session (such as the set of media streams and their codecs) but has no impact on the state of a dialog. In that sense, it is like a re-INVITE, but unlike re-INVITE, it can be sent before the initial INVITE has been completed. This makes it very useful for updating session parameters within early dialogs. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021015115326.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3311 --OtherAccess Content-Type: Message/External-body; name="rfc3311.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021015115326.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Tue Oct 15 11:57:28 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9FIvSC25450; Tue, 15 Oct 2002 11:57:28 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9FIvSD21200; Tue, 15 Oct 2002 11:57:28 -0700 (PDT) Message-Id: <200210151857.g9FIvSD21200@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 15 Oct 2002 11:57:27 -0700 Subject: [rfc-dist] RFC 3334 on Policy-Based Accounting Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3334 Title: Policy-Based Accounting Author(s): T. Zseby, S. Zander, C. Carle Status: Experimental Date: October 2002 Mailbox: zseby@fokus.fhg.de, zander@fokus.fhg.de, carle@fokus.fhg.de Pages: 44 Characters: 103014 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-aaaarch-pol-acct-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3334.txt This document describes policy-based accounting which is an approach to provide flexibility to accounting architectures. Accounting policies describe the configuration of an accounting architecture in a standardized way. They are used to instrument the accounting architecture and can be exchanged between Authentication, Authorization and Accounting (AAA) entities in order to share configuration information. This document describes building blocks and message sequences for policy-based accounting in the generic AAA architecture (RFC 2903). Examples are given for the usage of accounting policies in different scenarios. It is also shown how accounting components can be integrated into the AAA authorization framework (RFC 2904). This document does not propose a language for the description of accounting policies. Rather, it is assumed that a suitable policy language can be chosen from existing or upcoming standards. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021015115602.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3334 --OtherAccess Content-Type: Message/External-body; name="rfc3334.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021015115602.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Oct 17 16:22:27 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNMQC01265; Thu, 17 Oct 2002 16:22:26 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNMQD11287; Thu, 17 Oct 2002 16:22:26 -0700 (PDT) Message-Id: <200210172322.g9HNMQD11287@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 17 Oct 2002 16:22:26 -0700 Subject: [rfc-dist] RFC 3312 on Integration of Resource Management and Session Initiation Protocol (SIP) Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3312 Title: Integration of Resource Management and Session Initiation Protocol (SIP) Author(s): G. Camarillo, Ed., W. Marshall, Ed., J. Rosenberg Status: Standards Track Date: October 2002 Mailbox: Gonzalo.Camarillo@ericsson.com, wtm@research.att.com, jdrosen@dynamicsoft.com Pages: 30 Characters: 65757 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sip-manyfolks-resource-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3312.txt This document defines a generic framework for preconditions, which are extensible through IANA registration. This document also discusses how network quality of service can be made a precondition for establishment of sessions initiated by the Session Initiation Protocol (SIP). These preconditions require that the participant reserve network resources before continuing with the session. We do not define new quality of service reservation mechanisms; these preconditions simply require a participant to use existing resource reservation mechanisms before beginning the session. This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017162036.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3312 --OtherAccess Content-Type: Message/External-body; name="rfc3312.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017162036.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Oct 17 16:24:31 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNOVC03394; Thu, 17 Oct 2002 16:24:31 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNOVD12279; Thu, 17 Oct 2002 16:24:31 -0700 (PDT) Message-Id: <200210172324.g9HNOVD12279@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 17 Oct 2002 16:24:30 -0700 Subject: [rfc-dist] RFC 3376 on Internet Group Management Protocol, Version 3 Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3376 Title: Internet Group Management Protocol, Version 3 Author(s): B. Cain, S. Deering, I. Kouvelas, B. Fenner, A. Thyagarajan Status: Standards Track Date: October 2002 Mailbox: deering@cisco.com, fenner@research.att.com, kouvelas@cisco.com Pages: 53 Characters: 119726 Obsoletes: 2236 I-D Tag: draft-ietf-idmr-igmp-v3-11.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3376.txt This document specifies Version 3 of the Internet Group Management Protocol, IGMPv3. IGMP is the protocol used by IPv4 systems to report their IP multicast group memberships to neighboring multicast routers. Version 3 of IGMP adds support for "source filtering", that is, the ability for a system to report interest in receiving packets *only* from specific source addresses, or from *all but* specific source addresses, sent to a particular multicast address. That information may be used by multicast routing protocols to avoid delivering multicast packets from specific sources to networks where there are no interested receivers. This document obsoletes RFC 2236. This document is a product of the Inter-Domain Multicast Routing Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017162240.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3376 --OtherAccess Content-Type: Message/External-body; name="rfc3376.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017162240.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Oct 17 16:53:06 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNr5C24431; Thu, 17 Oct 2002 16:53:06 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNr5D25206; Thu, 17 Oct 2002 16:53:05 -0700 (PDT) Message-Id: <200210172353.g9HNr5D25206@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 17 Oct 2002 16:53:05 -0700 Subject: [rfc-dist] RFC 3401 on Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3401 Title: Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS Author(s): M. Mealling Status: Informational Date: October 2002 Mailbox: michael@neonym.net Pages: 6 Characters: 10172 Updates: 2276 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-ddds-toc-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3401.txt This document specifies the exact documents that make up the complete Dynamic Delegation Discovery System (DDDS). DDDS is an abstract algorithm for applying dynamically retrieved string transformation rules to an application-unique string. This document along with RFC 3402, RFC 3403 and RFC 3404 obsolete RFC 2168 and RFC 2915, as well as updates RFC 2276. This document is a product of the Uniform Resource Names Working Group of the IETF. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017165023.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3401 --OtherAccess Content-Type: Message/External-body; name="rfc3401.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017165023.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Oct 17 16:55:23 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNtNC27053; Thu, 17 Oct 2002 16:55:23 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNtMD26357; Thu, 17 Oct 2002 16:55:22 -0700 (PDT) Message-Id: <200210172355.g9HNtMD26357@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 17 Oct 2002 16:55:22 -0700 Subject: [rfc-dist] RFC 3402 on Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3402 Title: Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm Author(s): M. Mealling Status: Standards Track Date: October 2002 Mailbox: michael@neonym.net Pages: 17 Characters: 38925 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-ddds-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3402.txt This document describes the Dynamic Delegation Discovery System (DDDS) algorithm for applying dynamically retrieved string transformation rules to an application-unique string. Well-formed transformation rules will reflect the delegation of management of information associated with the string. This document is also part of a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. This document is a product of the Uniform Resource Names Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017165329.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3402 --OtherAccess Content-Type: Message/External-body; name="rfc3402.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017165329.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Oct 17 16:57:56 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNvuC00720; Thu, 17 Oct 2002 16:57:56 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNvuD27046; Thu, 17 Oct 2002 16:57:56 -0700 (PDT) Message-Id: <200210172357.g9HNvuD27046@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 17 Oct 2002 16:57:56 -0700 Subject: [rfc-dist] RFC 3403 on Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3403 Title: Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database Author(s): M. Mealling Status: Standards Track Date: October 2002 Mailbox: michael@neonym.net Pages: 14 Characters: 31058 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-dns-ddds-database-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3403.txt This document describes a Dynamic Delegation Discovery System (DDDS) Database using the Domain Name System (DNS) as a distributed database of Rules. The Keys are domain-names and the Rules are encoded using the Naming Authority Pointer (NAPTR) Resource Record (RR). Since this document obsoletes RFC 2915, it is the official specification for the NAPTR DNS Resource Record. It is also part of a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. This document is a product of the Uniform Resource Names Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017165555.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3403 --OtherAccess Content-Type: Message/External-body; name="rfc3403.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017165555.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From rfc-ed@ISI.EDU Thu Oct 17 17:00:25 2002 Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g9I00OC04047; Thu, 17 Oct 2002 17:00:24 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9I00OD28381; Thu, 17 Oct 2002 17:00:24 -0700 (PDT) Message-Id: <200210180000.g9I00OD28381@gamma.isi.edu> To: rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 17 Oct 2002 17:00:24 -0700 Subject: [rfc-dist] RFC 3404 on Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application Sender: rfc-dist-admin@mailman.rfc-editor.org Errors-To: rfc-dist-admin@mailman.rfc-editor.org X-BeenThere: rfc-dist@mailman.rfc-editor.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: RFC Announcements List-Unsubscribe: , List-Archive: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3404 Title: Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application Author(s): M. Mealling Status: Standards Track Date: October 2002 Mailbox: michael@neonym.net Pages: 18 Characters: 40124 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-uri-res-ddds-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3404.txt This document describes a specification for taking Uniform Resource Identifiers (URI) and locating an authoritative server for information about that URI. The method used to locate t