From pce-bounces@lists.ietf.org Mon Jan 07 20:15:00 2008
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JC33F-0007uJ-7b; Mon, 07 Jan 2008 20:14:45 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43)
	id 1JC33D-0007uA-Qq
	for pce-confirm+ok@megatron.ietf.org; Mon, 07 Jan 2008 20:14:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JC33D-0007u2-Ge; Mon, 07 Jan 2008 20:14:43 -0500
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JC33D-0004Ix-2r; Mon, 07 Jan 2008 20:14:43 -0500
Received: by bosco.isi.edu (Postfix, from userid 70)
	id C69A21075B8; Mon,  7 Jan 2008 17:14:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080108011442.C69A21075B8@bosco.isi.edu>
Date: Mon,  7 Jan 2008 17:14:42 -0800 (PST)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 5088 on OSPF Protocol Extensions for Path Computation
	Element (PCE) Discovery
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5088

        Title:      OSPF Protocol Extensions for Path 
                    Computation Element (PCE) Discovery 
        Author:     JL. Le Roux, Ed.,
                    JP. Vasseur, Ed.,
                    Y. Ikejiri, R. Zhang
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    jeanlouis.leroux@orange-ftgroup.com, 
                    jpv@cisco.com, 
                    y.ikejiri@ntt.com,  raymond.zhang@bt.com
        Pages:      20
        Characters: 40936
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-disco-proto-ospf-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5088.txt

There are various circumstances where it is highly desirable for a
Path Computation Client (PCC) to be able to dynamically and
automatically discover a set of Path Computation Elements (PCEs),
along with information that can be used by the PCC for PCE selection.
When the PCE is a Label Switching Router (LSR) participating in the
Interior Gateway Protocol (IGP), or even a server participating
passively in the IGP, a simple and efficient way to announce PCEs
consists of using IGP flooding.  For that purpose, this document
defines extensions to the Open Shortest Path First (OSPF) routing
protocol for the advertisement of PCE Discovery information within an
OSPF area or within the entire OSPF routing domain.  [STANDARDS TRACK]

This document is a product of the Path Computation Element
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.


The RFC Editor Team
USC/Information Sciences Institute

...




_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Mon Jan 07 20:15:08 2008
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JC33c-0007zn-IZ; Mon, 07 Jan 2008 20:15:08 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43)
	id 1JC33b-0007zf-F7
	for pce-confirm+ok@megatron.ietf.org; Mon, 07 Jan 2008 20:15:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JC33b-0007zX-5E; Mon, 07 Jan 2008 20:15:07 -0500
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JC33a-0004JV-NX; Mon, 07 Jan 2008 20:15:07 -0500
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 6EEE51075BA; Mon,  7 Jan 2008 17:15:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080108011506.6EEE51075BA@bosco.isi.edu>
Date: Mon,  7 Jan 2008 17:15:06 -0800 (PST)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 5089 on IS-IS Protocol Extensions for Path Computation
	Element (PCE) Discovery
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5089

        Title:      IS-IS Protocol Extensions for Path 
                    Computation Element (PCE) Discovery 
        Author:     JL. Le Roux, Ed.,
                    JP. Vasseur, Ed.,
                    Y. Ikejiri, R. Zhang
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    jeanlouis.leroux@orange-ftgroup.com, 
                    jpv@cisco.com, 
                    y.ikejiri@ntt.com,  raymond.zhang@bt.com
        Pages:      17
        Characters: 34257
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-disco-proto-isis-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5089.txt

There are various circumstances where it is highly desirable for a
Path Computation Client (PCC) to be able to dynamically and
automatically discover a set of Path Computation Elements (PCEs),
along with information that can be used by the PCC for PCE selection.
When the PCE is a Label Switching Router (LSR) participating in the
Interior Gateway Protocol (IGP), or even a server participating
passively in the IGP, a simple and efficient way to announce PCEs
consists of using IGP flooding.  For that purpose, this document
defines extensions to the Intermediate System to Intermediate System
(IS-IS) routing protocol for the advertisement of PCE Discovery
information within an IS-IS area or within the entire IS-IS routing
domain.  [STANDARDS TRACK]

This document is a product of the Path Computation Element
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.


The RFC Editor Team
USC/Information Sciences Institute

...




_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Thu Jan 17 14:14:12 2008
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFaBe-00056d-LF; Thu, 17 Jan 2008 14:14:02 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43)
	id 1JFaBd-00051d-Pm
	for pce-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 14:14:01 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFaBd-0004pf-DW
	for pce@ietf.org; Thu, 17 Jan 2008 14:14:01 -0500
Received: from asmtp1.iomartmail.com ([62.128.201.248])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFaBY-0001lt-5P
	for pce@ietf.org; Thu, 17 Jan 2008 14:13:56 -0500
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m0HJDmgj004272 for <pce@ietf.org>; Thu, 17 Jan 2008 19:13:48 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m0HJDZRU004175 for <pce@ietf.org>; Thu, 17 Jan 2008 19:13:48 GMT
Message-ID: <0a1101c8593d$0fca1c40$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Thu, 17 Jan 2008 19:13:33 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: 
Subject: [Pce] Review of v9 of PCEP
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi,

I just completed a detailed review of draft-ietf-pce-pcep-09.txt

Most of the comments are typos, language, etc.
Some small technical issues and questions.

I've sent this to the editors but am not posting here because of the size of 
the resulting file.

If anyone wants to see it, I'll post it somewhere.

Cheers,
Adrian 




_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Fri Jan 18 13:21:43 2008
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFvqW-0007RO-J4; Fri, 18 Jan 2008 13:21:40 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43)
	id 1JFvqV-0007RI-Us
	for pce-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 13:21:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFvqV-0007RA-L3
	for pce@ietf.org; Fri, 18 Jan 2008 13:21:39 -0500
Received: from asmtp2.iomartmail.com ([62.128.201.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFvqT-0008Hr-B7
	for pce@ietf.org; Fri, 18 Jan 2008 13:21:39 -0500
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m0IILZ5b032481 for <pce@ietf.org>; Fri, 18 Jan 2008 18:21:35 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m0IILXeA032459 for <pce@ietf.org>; Fri, 18 Jan 2008 18:21:34 GMT
Message-ID: <0c8d01c859fe$f3a39b50$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Fri, 18 Jan 2008 18:21:10 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
Subject: [Pce] New IPR Disclosure Posted
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi,

Please be aware of the following IPR Disclosure posted with respect of 
draft-ietf-pce-brpc-06.txt.

The WG chairs cannot give (or receive!) advice about the relevance of the 
claim or the nature of its terms. You are invited to examine them for 
yourselves and take legal or technical advice as appropriate.

If anyone feels that the working group should investigate alternative 
approaches that may be free of IPR claims, they should bring their ideas 
forward.

Thanks,
Adrian

> An IPR disclosure that pertains to your Internet-Draft entitled "A 
> Backward
> Recursive PCE-based Computation (BRPC) procedure to compute shortest
> inter-domain Traffic Engineering Label Switched Paths" 
> (draft-ietf-pce-brpc) was
> submitted to the IETF Secretariat and has been posted on the "IETF
> Page of Intellectual Property Rights Disclosures"
> (https://datatracker.ietf.org/public/ipr_list.cgi). The title of the IPR
> disclosure is "Cisco's Statement about IPR claimed in
> draft-ietf-pce-brpc-06.txt."




_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Mon Jan 21 15:15:05 2008
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JH32u-0000OF-RM; Mon, 21 Jan 2008 15:15:04 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43)
	id 1JH32t-0000Jd-5c
	for pce-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 15:15:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JH32s-0000JU-Mh; Mon, 21 Jan 2008 15:15:02 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JH32s-0003b7-9E; Mon, 21 Jan 2008 15:15:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 259D326E66;
	Mon, 21 Jan 2008 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1JH32s-0008DO-1Q; Mon, 21 Jan 2008 15:15:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1JH32s-0008DO-1Q@stiedprstage1.ietf.org>
Date: Mon, 21 Jan 2008 15:15:02 -0500
X-Spam-Score: -1.4 (-)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-inter-layer-frwk-06.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering
	Author(s)	: E. Oki, et al.
	Filename	: draft-ietf-pce-inter-layer-frwk-06.txt
	Pages		: 1
	Date		: 2008-1-21
	
A network may comprise multiple layers. It is important to 
     globally optimize network resource utilization, taking into 
     account all layers, rather than optimizing resource utilization at 
     each layer independently. This allows better network efficiency to 
     be achieved through a process that we call inter-layer traffic 
     engineering. The Path Computation Element (PCE) can be a powerful 
     tool to achieve inter-layer traffic engineering. 
     This document describes a framework for applying the PCE-based 
     architecture to inter-layer Multiprotocol Label Switching (MPLS) 
     and Generalized MPLS (GMPLS) traffic engineering. It provides 
     suggestions for the deployment of PCE in support of multi-layer 
     networks. This document also describes network models where PCE 
     performs inter-layer traffic engineering, and the relationship 
     between PCE and a functional component called the Virtual Network 
     Topology Manager (VNTM).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-frwk-06.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-pce-inter-layer-frwk-06.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-pce-inter-layer-frwk-06.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: <2008-1-21140909.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pce-inter-layer-frwk-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pce-inter-layer-frwk-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-1-21140909.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--NextPart--





From pce-bounces@lists.ietf.org Fri Jan 25 12:30:35 2008
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JISNs-00020V-1d; Fri, 25 Jan 2008 12:30:32 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43)
	id 1JISNr-00020Q-Jz
	for pce-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 12:30:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JISNr-00020A-8J
	for pce@ietf.org; Fri, 25 Jan 2008 12:30:31 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JISNq-0004M4-Ku
	for pce@ietf.org; Fri, 25 Jan 2008 12:30:31 -0500
X-IronPort-AV: E=Sophos;i="4.25,251,1199682000"; d="scan'208";a="84408737"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 25 Jan 2008 12:30:31 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m0PHUUif027849
	for <pce@ietf.org>; Fri, 25 Jan 2008 12:30:30 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m0PHU8JT021663
	for <pce@ietf.org>; Fri, 25 Jan 2008 17:30:30 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 25 Jan 2008 12:30:26 -0500
Received: from 161.44.71.157 ([161.44.71.157]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 25 Jan 2008 17:30:26 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Fri, 25 Jan 2008 12:30:12 -0500
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C3BF86D4.22430%jvasseur@cisco.com>
Thread-Topic: Internet-Drafts Submission Cutoff Dates for the 71st IETF 
	Meeting in Philadelphia, PA, USA 
Thread-Index: Achfd/B0Luq7A8trEdyD6gANk8WjQA==
In-Reply-To: <E1JIGfa-0003mt-97@stiedprstage1.ietf.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 25 Jan 2008 17:30:26.0299 (UTC)
	FILETIME=[F8FAC4B0:01C85F77]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2910; t=1201282230;
	x=1202146230; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20FW=3A=20Internet-Drafts=20Submission=20Cutoff=2
	0Dates=20for=20the=2071st=20IETF=20=0A=20Meeting=20in=20Phil
	adelphia,=20PA,=20USA=20 |Sender:=20 |To:=20<pce@ietf.org>;
	bh=Fer9nz4UxPsW0jno64YmJDpuuz25RBHz9OGT9lX0P0I=;
	b=TS/QLsudAGqKdEXNIXlTROUo7FHXoFC6wy4UhsAgRTogOlTB4N2N89UeDQ
	Ny5n/JCfOsavjdhoAuTlHRUO0E/Dvc/PzDRa5f7sqcAobZaHoFGUxtiB6NYL
	L0JUFnvStT;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
Subject: [Pce] FW: Internet-Drafts Submission Cutoff Dates for the 71st IETF
 Meeting in Philadelphia, PA, USA 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org



------ Forwarded Message
> From: <ietf-secretariat@ietf.org>
> Date: Fri, 25 Jan 2008 00:00:02 -0500
> To: <ietf-announce@ietf.org>
> Subject: Internet-Drafts Submission Cutoff Dates for the 71st IETF  Meeting in
> Philadelphia, PA, USA
> 
> 
> There are two (2) Internet-Draft cutoff dates for the 71st
> IETF Meeting in Philadelphia, PA, USA:
> 
> February 18th: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
> 
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> February 18th at 9:00 AM ET (14:00 UTC/GMT).The only exception is for
> version -00 WG drafts that replace existing non-WG drafts.  Such drafts
> may be submitted until the cutoff date for version -01 and higher
> drafts.
> As always, all initial submissions with a filename beginning with
> "draft-ietf" must be approved by the appropriate WG Chair before they
> can be processed or announced.  The Secretariat would appreciate
> receiving WG Chair approval by Monday, February 11th at 9:00 AM ET (14:00
> UTC/GMT).
> 
> February  (14:00 UTC/GMT): Cutoff Date for Revised (i.e., version -01 and
> higher) 
> Internet-Draft Submissions
> 
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, February 25th at 9:00 AM ET (14:00 UTC/GMT).
> 
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, March 10th at 9:00
> AM ET (13:00 UTC/GMT), when Internet-Draft posting resumes.  Please do not
> wait until 
> the last minute to submit.
> 
> The Secretariat encourages you to submit your Internet-Drafts via the
> Internet-Draft Submission Tool (IDST)
> https://datatracker.ietf.org/idst/upload.cgi.
> If you are unable to do so, then you may still submit your Internet-
> Drafts manually by sending them to internet-drafts@ietf.org.  If you
> are submitting a version -00 WG draft that replaces non-WG draft, then
> you must submit it manually as the current IDST cannot handle
> replacements.  Please be sure to state that one draft replaces another
> in the cover note that accompanies your submission.  Also, please note
> that the IDST will not accept drafts submitted after their respective
> cutoff dates.
> 
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
> 
> The IETF Secretariat
> 
> FYI: The Internet-Draft cutoff dates as well as other significant dates
> for the 71st IETF Meeting can be found at
> http://www.ietf.org/meetings/71-cutoff_dates.html.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce

------ End of Forwarded Message



_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From windbreaksg166@yamatoji.com  Thu Jan 31 18:58:27 2008
Return-Path: <windbreaksg166@yamatoji.com>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3139F28C101;
	Thu, 31 Jan 2008 18:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: YES
X-Spam-Score: 83.379
X-Spam-Level: ****************************************************************
X-Spam-Status: Yes, score=83.379 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, HELO_EQ_IP_ADDR=1.119,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_NONE=0.1,
	SARE_SUB_MEDS=1.666, STOX_REPLY_TYPE=0.001, SUBJECT_FUZZY_MEDS=3.799,
	TRACKER_ID=2.003, TVD_SPACE_RATIO=2.219, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083,
	URIBL_SC_SURBL=10, URIBL_WS_SURBL=10]
X-Spam-Report:
 *  3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
 *      [score: 1.0000]
 *  1.1 HELO_EQ_IP_ADDR HELO using IP Address (not private)
 *  1.5 FH_RELAY_NODNS We could not determine your Reverse DNS
 *  3.8 SUBJECT_FUZZY_MEDS Attempt to obfuscate words in Subject:
 *  1.7 SARE_SUB_MEDS Common spammer subject header -- Medical
 *  0.0 STOX_REPLY_TYPE STOX_REPLY_TYPE
 *  2.0 TRACKER_ID BODY: Incorporates a tracking ID number
 *  2.2 TVD_SPACE_RATIO BODY: TVD_SPACE_RATIO
 *  1.5 RAZOR2_CF_RANGE_E8_51_100 Razor2 gives engine 8 confidence level
 *      above 50%
 *      [cf: 100]
 *  0.5 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/)
 *  0.5 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50%
 *      [cf: 100]
 *   20 URIBL_BLACK Contains an URL listed in the URIBL blacklist
 *      [URIs: replydown.com]
 *   10 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
 *      [URIs: replydown.com]
 *   10 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist
 *      [URIs: replydown.com]
 *   10 URIBL_OB_SURBL Contains an URL listed in the OB SURBL blocklist
 *      [URIs: replydown.com]
 *   10 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist
 *      [URIs: replydown.com]
 *  1.1 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread)
 *      [URIs: replydown.com]
 *  0.9 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
 *      [117.4.156.188 listed in zen.spamhaus.org]
 *  3.0 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
 *  0.1 RDNS_NONE Delivered to trusted network by a host with no rDNS
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CNC3uG9p6Ewq; Thu, 31 Jan 2008 18:58:26 -0800 (PST)
Received: from [117.4.156.188] (unknown [117.4.156.188])
	by core3.amsl.com (Postfix) with ESMTP id 80B1728C0E1;
	Thu, 31 Jan 2008 18:58:24 -0800 (PST)
Received: from [117.4.156.188] by www.yamatoji.com; Thu, 31 Jan 2008 18:59:58 -0800
Message-ID: <01c8643b$793dcb00$bc9c0475@windbreaksg166>
From: "Rosalind Bingham" <windbreaksg166@yamatoji.com>
To: <architecture-discuss@ietf.org>
Subject: ***SPAM*** 83.379 (5) OnlineDrugstoreThankYouMeds
Date: Thu, 31 Jan 2008 18:59:58 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-2";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506

SoftTabsNewOfferCanadian
http://replydown.com

From reistass1986@skinsationsspa.com  Thu Jan 31 22:07:56 2008
Return-Path: <reistass1986@skinsationsspa.com>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B0293A67AE
	for <ietfarch-pce-archive@core3.amsl.com>; Thu, 31 Jan 2008 22:07:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: YES
X-Spam-Score: 116.603
X-Spam-Level: ****************************************************************
X-Spam-Status: Yes, score=116.603 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, DATE_IN_PAST_96_XX=1.69, DOS_OE_TO_MX=2.75,
	FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999,
	HELO_DYNAMIC_IPADDR2=4.395, HTML_MESSAGE=1,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10,
	URIBL_RHS_DOB=1.083, URIBL_SBL=20, URIBL_SC_SURBL=10,
	URIBL_WS_SURBL=10]
X-Spam-Report:
 *  3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
 *      [score: 1.0000]
 *  0.8 FH_HOST_EQ_D_D_D_D Host starts with d-d-d-d
 *  0.9 FH_HOST_EQ_D_D_D_DB Host is d-d-d-d
 *  4.4 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP addr
 *       2)
 *  1.6 FH_HELO_EQ_D_D_D_D Helo is d-d-d-d
 *  1.9 TVD_RCVD_IP TVD_RCVD_IP
 *  1.7 DATE_IN_PAST_96_XX Date: is 96 hours or more before Received: date
 *  1.0 HTML_MESSAGE BODY: HTML included in message
 *  1.5 RAZOR2_CF_RANGE_E8_51_100 Razor2 gives engine 8 confidence level
 *      above 50%
 *      [cf: 100]
 *  0.5 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/)
 *  1.5 RAZOR2_CF_RANGE_E4_51_100 Razor2 gives engine 4 confidence level
 *      above 50%
 *      [cf:  91]
 *  0.5 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50%
 *      [cf: 100]
 *   10 URIBL_AB_SURBL Contains an URL listed in the AB SURBL blocklist
 *      [URIs: decidecompany.com]
 *   10 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
 *      [URIs: decidecompany.com]
 *   10 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist
 *      [URIs: decidecompany.com]
 *   10 URIBL_OB_SURBL Contains an URL listed in the OB SURBL blocklist
 *      [URIs: decidecompany.com]
 *   10 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist
 *      [URIs: decidecompany.com]
 *  1.1 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread)
 *      [URIs: decidecompany.com]
 *  0.9 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
 *      [68.240.60.191 listed in zen.spamhaus.org]
 *   20 URIBL_BLACK Contains an URL listed in the URIBL blacklist
 *      [URIs: decidecompany.com]
 *   20 URIBL_SBL Contains an URL listed in the SBL blocklist
 *      [URIs: decidecompany.com]
 *  2.0 FM_DDDD_TIMES_2 Dual helo + host eq d_d_d_d
 *  0.1 RDNS_DYNAMIC Delivered to trusted network by host with
 *      dynamic-looking rDNS
 *  2.8 DOS_OE_TO_MX Delivered direct to MX with OE headers
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dmabAoGcxRwq for <ietfarch-pce-archive@core3.amsl.com>;
	Thu, 31 Jan 2008 22:07:55 -0800 (PST)
Received: from 68-240-60-191.area5.spcsdns.net (68-240-60-191.area5.spcsdns.net [68.240.60.191])
	by core3.amsl.com (Postfix) with ESMTP id 29EA03A6804
	for <pce-archive@ietf.org>; Thu, 31 Jan 2008 22:07:46 -0800 (PST)
Message-ID: <000601c84bd8$ffee8520$bf3cf044@na86763f0864b6>
From: "Arles Greenlaw" <reistass1986@skinsationsspa.com>
To: pce-archive@ietf.org
Subject: ***SPAM*** 116.603 (5) regorger
Date: Mon, 31 Dec 2007 12:14:35 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="--------=_NextPart_000_0002_01C84BA6.B5541520"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198

----------=_NextPart_000_0002_01C84BA6.B5541520
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Piece and Fantasy in Mind.
Improves Focus;
----------=_NextPart_000_0002_01C84BA6.B5541520
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3199" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT Arial size=3D2>Piece and Fantasy in Mind.</FONT></DIV>
<A href=3D"http://decidecompany.com">Improves Focus;</A></BODY></HTML>
----------=_NextPart_000_0002_01C84BA6.B5541520--
