From owner-ietf-ipsra@mail.vpnc.org Fri Jan 31 18:01:07 2003 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21593 for ; Fri, 31 Jan 2003 18:01:06 -0500 (EST) Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0VMjYM24451 for ietf-ipsra-bks; Fri, 31 Jan 2003 14:45:34 -0800 (PST) Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0VMjSo24442 for ; Fri, 31 Jan 2003 14:45:29 -0800 (PST) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h0VMjTD24141; Fri, 31 Jan 2003 14:45:29 -0800 (PST) Message-Id: <200301312245.h0VMjTD24141@gamma.isi.edu> To: IETF-Announce: ; Subject: RFC 3456 on Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode Cc: rfc-editor@rfc-editor.org, ietf-ipsra@vpnc.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 31 Jan 2003 14:45:29 -0800 Sender: owner-ietf-ipsra@mail.vpnc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3456 Title: Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode Author(s): B. Patel, B. Aboba, S. Kelly, V. Gupta Status: Standards Track Date: January 2003 Mailbox: baiju.v.patel@intel.com, bernarda@microsoft.com, scott@hyperthought.com, vipul.gupta@sun.com Pages: 18 Characters: 40340 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipsec-dhcp-13.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3456.txt This memo explores the requirements for host configuration in IPsec tunnel mode, and describes how the Dynamic Host Configuration Protocol (DHCPv4) may be leveraged for configuration. In many remote access scenarios, a mechanism for making the remote host appear to be present on the local corporate network is quite useful. This may be accomplished by assigning the host a "virtual" address from the corporate network, and then tunneling traffic via IPsec from the host's ISP-assigned address to the corporate security gateway. In IPv4, DHCP provides for such remote host configuration. This document is a product of the IPSEC Remote Access (IPSRA) 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: <030131144253.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3456 --OtherAccess Content-Type: Message/External-body; name="rfc3456.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <030131144253.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-ietf-ipsra@mail.vpnc.org Fri Jan 31 18:58:30 2003 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21594 for ; Fri, 31 Jan 2003 18:01:06 -0500 (EST) Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0VMmGi24527 for ietf-ipsra-bks; Fri, 31 Jan 2003 14:48:16 -0800 (PST) Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0VMmAo24518 for ; Fri, 31 Jan 2003 14:48:10 -0800 (PST) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h0VMmAD25011; Fri, 31 Jan 2003 14:48:10 -0800 (PST) Message-Id: <200301312248.h0VMmAD25011@gamma.isi.edu> To: IETF-Announce: ; Subject: RFC 3457 on Requirements for IPsec Remote Access Scenarios Cc: rfc-editor@rfc-editor.org, ietf-ipsra@vpnc.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 31 Jan 2003 14:48:10 -0800 Sender: owner-ietf-ipsra@mail.vpnc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3457 Title: Requirements for IPsec Remote Access Scenarios Author(s): S. Kelly, S. Ramamoorthi Status: Informational Date: January 2003 Mailbox: scott@hyperthought.com, sankarr@juniper.net Pages: 31 Characters: 75167 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipsra-reqmts-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3457.txt IPsec offers much promise as a secure remote access mechanism. However, there are a number of differing remote access scenarios, each having some shared and some unique requirements. A thorough understanding of these requirements is necessary in order to effectively evaluate the suitability of a specific set of mechanisms for any particular remote access scenario. This document enumerates the requirements for a number of common remote access scenarios. This document is a product of the IPSEC Remote Access (IPSRA) 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: <030131144601.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3457 --OtherAccess Content-Type: Message/External-body; name="rfc3457.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <030131144601.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--