RFC 3809 on Generic Requirements for Provider Provisioned Virtual Private Networks (PPVPN)
rfc-editor@rfc-editor.org Thu, 10 June 2004 12:55 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00279 for <ietf-announce-archive@ietf.org>; Thu, 10 Jun 2004 08:55:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYP5f-0005Pg-IA for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 08:55:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYP4A-0004S0-00 for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 08:53:59 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BYP2x-0003jj-00; Thu, 10 Jun 2004 08:52:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYOpW-0003Go-8C; Thu, 10 Jun 2004 08:38:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYD4o-0000y1-PZ for ietf-announce@megatron.ietf.org; Wed, 09 Jun 2004 20:05:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05009 for <ietf-announce@ietf.org>; Wed, 9 Jun 2004 20:05:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYD4n-0006vX-5I for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:05:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYD3n-000602-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:04:48 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BYD1S-0003Ke-00; Wed, 09 Jun 2004 20:02:22 -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 i5A01SJ06893; Wed, 9 Jun 2004 17:01:28 -0700 (PDT)
Message-Id: <200406100001.i5A01SJ06893@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 09 Jun 2004 17:01:28 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Thu, 10 Jun 2004 08:38:44 -0400
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 3809 on Generic Requirements for Provider Provisioned Virtual Private Networks (PPVPN)
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-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
A new Request for Comments is now available in online RFC libraries.
RFC 3809
Title: Generic Requirements for Provider Provisioned
Virtual Private Networks (PPVPN)
Author(s): A. Nagarajan, Ed.
Status: Informational
Date: June 2004
Mailbox: ananth@juniper.net
Pages: 25
Characters: 60576
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l3vpn-generic-reqts-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3809.txt
This document describes generic requirements for Provider Provisioned
Virtual Private Networks (PPVPN). The requirements are categorized
into service requirements, provider requirements and engineering
requirements. These requirements are not specific to any particular
type of PPVPN technology, but rather apply to all PPVPN technologies.
All PPVPN technologies are expected to meet the umbrella set of
requirements described in this document.
This document is a product of the Layer 3 Virtual Private Networks
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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce