From owner-rap@ops.ietf.org Thu Dec 08 17:38:30 2005 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkUPG-0004Vh-Cj for rap-archive@megatron.ietf.org; Thu, 08 Dec 2005 17:38:30 -0500 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01040 for ; Thu, 8 Dec 2005 17:37:35 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EkUNR-0002UP-MC for rap-data@psg.com; Thu, 08 Dec 2005 22:36:37 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_POST autolearn=no version=3.1.0 Received: from [134.134.136.16] (helo=orsfmr002.jf.intel.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EkUNO-0002Tx-RF for rap@ops.ietf.org; Thu, 08 Dec 2005 22:36:34 +0000 Received: from orsfmr101.jf.intel.com (orsfmr101.jf.intel.com [10.7.209.17]) by orsfmr002.jf.intel.com (8.12.10/8.12.10/d: major-outer.mc,v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id jB8MaYqC007307 for ; Thu, 8 Dec 2005 22:36:34 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by orsfmr101.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id jB8MaNwH015030 for ; Thu, 8 Dec 2005 22:36:34 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.7.47) with SMTP id M2005120814363405852 for ; Thu, 08 Dec 2005 14:36:34 -0800 Received: from orsmsx401.amr.corp.intel.com ([192.168.65.207]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 8 Dec 2005 14:36:34 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RFC 4261 on Common Open Policy Service (COPS) Over Transport Layer Security (TLS) Date: Thu, 8 Dec 2005 14:36:14 -0800 Message-ID: Thread-Topic: RFC 4261 on Common Open Policy Service (COPS) Over Transport Layer Security (TLS) thread-index: AcX6AOnc11jqbsoSQTKOOxZGlUFSGQCRm9jA From: "Hahn, Scott" To: X-OriginalArrivalTime: 08 Dec 2005 22:36:34.0015 (UTC) FILETIME=[D79C4EF0:01C5FC47] X-Scanned-By: MIMEDefang 2.52 on 10.7.209.17 Sender: owner-rap@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: quoted-printable =20 (Note: this was the last open work item for the RAP working Group. -- Scott) A new Request for Comments is now available in online RFC libraries. RFC 4261 Title: Common Open Policy Service (COPS) Over Transport Layer Security (TLS) Author(s): J. Walker, A. Kulkarni, Ed. Status: Standards Track Date: December 2005 Mailbox: jesse.walker@intel.com, amol.kulkarni@intel.com Pages: 14 Characters: 28662 Updates: 2748 I-D Tag: draft-ietf-rap-cops-tls-11.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4261.txt This document describes how to use Transport Layer Security (TLS) to secure Common Open Policy Service (COPS) connections over the Internet. This document also updates RFC 2748 by modifying the contents of the Client-Accept message. This document is a product of the Resource Allocation 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=20 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. 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 ... From owner-rap@ops.ietf.org Fri Dec 09 21:49:59 2005 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekuo7-00089k-H5 for rap-archive@megatron.ietf.org; Fri, 09 Dec 2005 21:49:59 -0500 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00621 for ; Fri, 9 Dec 2005 21:48:53 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EkumW-0009h8-9M for rap-data@psg.com; Sat, 10 Dec 2005 02:48:16 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.0 Received: from [192.11.222.161] (helo=ihemail1.lucent.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EkumV-0009gr-FP for rap@ops.ietf.org; Sat, 10 Dec 2005 02:48:15 +0000 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBA2mAbo015435; Fri, 9 Dec 2005 20:48:11 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Sat, 10 Dec 2005 03:48:09 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508CD37E0@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Hahn, Scott" , rap@ops.ietf.org Subject: RE: RFC 4261 on Common Open Policy Service (COPS) Over Transport Layer Security (TLS) Date: Sat, 10 Dec 2005 03:48:02 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-rap@ops.ietf.org Precedence: bulk Congrats. Bert > -----Original Message----- > From: owner-rap@ops.ietf.org > [mailto:owner-rap@ops.ietf.org]On Behalf Of > Hahn, Scott > Sent: Thursday, December 08, 2005 23:36 > To: rap@ops.ietf.org > Subject: RFC 4261 on Common Open Policy Service (COPS) Over Transport > Layer Security (TLS) > > > > > (Note: this was the last open work item for the RAP working Group. -- > Scott) > > A new Request for Comments is now available in online RFC libraries. > > > RFC 4261 > > Title: Common Open Policy Service (COPS) > Over Transport Layer Security (TLS) > Author(s): J. Walker, A. Kulkarni, Ed. > Status: Standards Track > Date: December 2005 > Mailbox: jesse.walker@intel.com, amol.kulkarni@intel.com > Pages: 14 > Characters: 28662 > Updates: 2748 > > I-D Tag: draft-ietf-rap-cops-tls-11.txt > > URL: ftp://ftp.rfc-editor.org/in-notes/rfc4261.txt > > > This document describes how to use Transport Layer Security (TLS) > to secure Common Open Policy Service (COPS) connections over the > Internet. > > This document also updates RFC 2748 by modifying the contents of > the Client-Accept message. > > This document is a product of the Resource Allocation 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. > > 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 > > ... >