From owner-ipsec-policy@mail.vpnc.org Thu Oct 21 16:22:11 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17783 for ; Thu, 21 Oct 2004 16:22:11 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9LJuDnp082338; Thu, 21 Oct 2004 12:56:13 -0700 (PDT) (envelope-from owner-ipsec-policy@mail.vpnc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i9LJuDvl082337; Thu, 21 Oct 2004 12:56:13 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ipsec-policy@mail.vpnc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9LJuBZ3082325 for ; Thu, 21 Oct 2004 12:56:12 -0700 (PDT) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13744; Thu, 21 Oct 2004 15:56:13 -0400 (EDT) Message-Id: <200410211956.PAA13744@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: ipsec-policy@vpnc.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ipsp-ipsecaction-mib-01.txt Date: Thu, 21 Oct 2004 15:56:13 -0400 Sender: owner-ipsec-policy@mail.vpnc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Security Policy Working Group of the IETF. Title : IPsec Security Policy IPsec Action MIB Author(s) : W. Hardaker, et al. Filename : draft-ietf-ipsp-ipsecaction-mib-01.txt Pages : 44 Date : 2004-10-21 This document defines a SMIv2 Management Information Base (MIB) module for configuring IPsec actions for the security policy database (SPD) of a device that uses the IPsec Security Policy Database Configuration MIB for configuring the IPSec protocol actions on that device. The IPSP IPsec Action MIB integrates directly with the IPsec Security Policy Database Configuration MIB and it is meant to work within the framework of an action referenced by that MIB. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipsp-ipsecaction-mib-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipsp-ipsecaction-mib-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipsp-ipsecaction-mib-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-21154632.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipsp-ipsecaction-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipsp-ipsecaction-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-21154632.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ipsec-policy@mail.vpnc.org Thu Oct 21 16:25:32 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18919 for ; Thu, 21 Oct 2004 16:25:32 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9LJtSY3082139; Thu, 21 Oct 2004 12:55:28 -0700 (PDT) (envelope-from owner-ipsec-policy@mail.vpnc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i9LJtSGx082138; Thu, 21 Oct 2004 12:55:28 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ipsec-policy@mail.vpnc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9LJtR6e082130 for ; Thu, 21 Oct 2004 12:55:27 -0700 (PDT) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13652; Thu, 21 Oct 2004 15:55:29 -0400 (EDT) Message-Id: <200410211955.PAA13652@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: ipsec-policy@vpnc.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ipsp-spd-mib-01.txt Date: Thu, 21 Oct 2004 15:55:28 -0400 Sender: owner-ipsec-policy@mail.vpnc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Security Policy Working Group of the IETF. Title : IPsec Security Policy Database Configuration MIB Author(s) : W. Hardaker, et al. Filename : draft-ietf-ipsp-spd-mib-01.txt Pages : 65 Date : 2004-10-21 This document defines a SMIv2 Management Information Base (MIB) module for configuring the security policy database of a device implementing the IPSec protocol. The policy-based packet filtering and the corresponding execution of actions is of a more general nature than for IPsec configuration only, such as for configuration of a firewall. This MIB module is designed with future extensibility in mind. It is thus possible to externally add other packet filters and actions to the policy-based packet filtering system defined in this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipsp-spd-mib-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipsp-spd-mib-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipsp-spd-mib-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-21154620.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipsp-spd-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipsp-spd-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-21154620.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ipsec-policy@mail.vpnc.org Thu Oct 21 16:27:04 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19268 for ; Thu, 21 Oct 2004 16:27:03 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9LJtrrU082246; Thu, 21 Oct 2004 12:55:53 -0700 (PDT) (envelope-from owner-ipsec-policy@mail.vpnc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i9LJtrli082244; Thu, 21 Oct 2004 12:55:53 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ipsec-policy@mail.vpnc.org using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9LJtqkX082238 for ; Thu, 21 Oct 2004 12:55:53 -0700 (PDT) (envelope-from dinaras@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13720; Thu, 21 Oct 2004 15:55:54 -0400 (EDT) Message-Id: <200410211955.PAA13720@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: ipsec-policy@vpnc.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ipsp-ikeaction-mib-01.txt Date: Thu, 21 Oct 2004 15:55:54 -0400 Sender: owner-ipsec-policy@mail.vpnc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Security Policy Working Group of the IETF. Title : IPsec Security Policy IKE Action MIB Author(s) : W. Hardaker, et al. Filename : draft-ietf-ipsp-ikeaction-mib-01.txt Pages : 64 Date : 2004-10-21 This document defines a SMIv2 Management Information Base (MIB) module for configuring IKE actions for the security policy database (SPD) of a device that uses the IPsec Security Policy Database Configuration MIB for configuring the IKE protocol actions on that device. The IPSP IKE Action MIB integrates directly with the IPsec Security Policy Database Configuration MIB and it is meant to work within the framework of an action referenced by that MIB. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipsp-ikeaction-mib-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipsp-ikeaction-mib-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipsp-ikeaction-mib-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-21154626.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipsp-ikeaction-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipsp-ikeaction-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-21154626.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ipsec-policy@mail.vpnc.org Wed Oct 27 14:07:41 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28212 for ; Wed, 27 Oct 2004 14:07:40 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9RHZP5p016931; Wed, 27 Oct 2004 10:35:25 -0700 (PDT) (envelope-from owner-ipsec-policy@mail.vpnc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i9RHZPUB016930; Wed, 27 Oct 2004 10:35:25 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ipsec-policy@mail.vpnc.org using -f Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9RHZNDX016914 for ; Wed, 27 Oct 2004 10:35:24 -0700 (PDT) (envelope-from Man.M.Li@nokia.com) Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9RHZOw17209; Wed, 27 Oct 2004 20:35:24 +0300 (EET DST) X-Scanned: Wed, 27 Oct 2004 20:33:36 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i9RHXa1Z012802; Wed, 27 Oct 2004 20:33:36 +0300 Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks003.ntc.nokia.com 008JjnEY; Wed, 27 Oct 2004 20:33:35 EEST Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com [10.241.35.122]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9RHXZS07361; Wed, 27 Oct 2004 20:33:35 +0300 (EET DST) Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 27 Oct 2004 12:33:16 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: Deleting ipSecPolicyTimePeriod related classes from IPsec PIB Date: Wed, 27 Oct 2004 13:33:16 -0400 Message-ID: Thread-Topic: Deleting ipSecPolicyTimePeriod related classes from IPsec PIB Thread-Index: AcS8SwrwBwKW4jOoSHS238YXbYvPvg== From: To: , X-OriginalArrivalTime: 27 Oct 2004 17:33:16.0485 (UTC) FILETIME=[0AE95750:01C4BC4B] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id i9RHZODX016916 Sender: owner-ipsec-policy@mail.vpnc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8bit Hi Bert, In March, we received your comments on IPsec PIB and made modifications accordingly. The only remaining issue is about the ipSecPolicyTimePeriod classes. You and I discussed two solutions and both seemed to have some drawback: Solution #1. Put the ipSecPolicyTImePeriod classes into a separate module within the IPsec PIB document. The drawback is that since the title of the draft is IPsec PIB, it should not contain a separate module that is not IPsec related. People will probably not look into this draft to find time related PIB classes Solution #2. Put the ipSecPolicyTime Period classes into a separate module in a separate IETF draft. The drawback is that it seems to me that IETF does not want to entertain another PIB draft. At the end of our April e-mail discussions, you were going to check if the TimePeriod classes are the only ones that should be separate from the IPsec PIB. I am now proposing another simpler solution as follows. If, after checking the document, you also think that the TimePeriod classes are the only ones that are not IPsec specific, what about we delete the ipSecPolicyTimePeriod classes from the IPsec PIB so that we can move on? If on the other hand, you think that there are other stuff that are not IPsec specific, please let use know. Thanks. Best regards Man Li