RFC 3838 on Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)
rfc-editor@rfc-editor.org Wed, 01 September 2004 00:14 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16056; Tue, 31 Aug 2004 20:14:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Io9-0003dh-58; Tue, 31 Aug 2004 20:17:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2IdM-0004SI-81; Tue, 31 Aug 2004 20:05:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2IOC-0008JL-RB for ietf-announce@megatron.ietf.org; Tue, 31 Aug 2004 19:50:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13595 for <ietf-announce@ietf.org>; Tue, 31 Aug 2004 19:50:09 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2IQF-0002qn-RE for ietf-announce@ietf.org; Tue, 31 Aug 2004 19:52:21 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i7VNnEJ02971; Tue, 31 Aug 2004 16:49:14 -0700 (PDT)
Message-Id: <200408312349.i7VNnEJ02971@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 31 Aug 2004 16:49:14 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: ietf-openproxy@imc.org, rfc-editor@rfc-editor.org
Subject: RFC 3838 on Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
A new Request for Comments is now available in online RFC libraries.
RFC 3838
Title: Policy, Authorization, and Enforcement
Requirements of the Open Pluggable Edge Services
(OPES)
Author(s): A. Barbir, O. Batuner, A. Beck, T. Chan, H. Orman
Status: Informational
Date: August 2004
Mailbox: abbieb@nortelnetworks.com, batuner@attbi.com,
abeck@bell-labs.com, Tat.Chan@nokia.com,
ho@alum.mit.edu
Pages: 17
Characters: 38739
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-opes-authorization-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3838.txt
This document describes policy, authorization, and enforcement
requirements for the selection of the services to be applied to a
given Open Pluggable Edge Services (OPES) flow.
This document is a product of the Open Pluggable Edge 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.
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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce