Subject: [PCN] [Fwd: New Version Notification for draft-briscoe-pcn-boundary-behav-00]

From: Tom Taylor <[email-masked]>
Date: Tue, 13 Nov 2007 21:36:45 -0500

This is a start on the work of defining boundary node behaviour. At the moment 
it is more of a survey than a prescription. It addresses a few issues, among 
them the question of how boundary nodes can get the information needed to 
classify flows into aggregates, and what strategy egress nodes should use to 
send congestion level information back to the ingress nodes.

Comments are welcome.

-------- Original Message --------
Subject: New Version Notification for draft-briscoe-pcn-boundary-behav-00
Date: Mon, 12 Nov 2007 08:47:32 -0500
From: IETF I-D Submission Tool <[email-masked]>
To: [email-masked]
CC: [email-masked], [email-masked]

A new version of I-D, draft-briscoe-pcn-boundary-behav-00.txt has been 
successfuly submitted by Tom Taylor and posted to the IETF repository.

Filename:	 draft-briscoe-pcn-boundary-behav
Revision:	 00
Title:		 PCN Boundary Node Behaviour
Creation_date:	 2007-11-11
WG ID:		 Independent Submission
Number_of_pages: 18

Abstract:
The Pre-Congestion Notification Architecture document defines a PCN
domain and the PCN-ingress and PCN-egress nodes that form its
boundary.  The present document is an attempt to describe the
detailed behaviour of the PCN boundary nodes.  It is a contribution
toward the PCN WG milestone: "Suggested Flow Admission and
Termination Boundary Mechanisms".  This first version is expected to
evolve with discussion and further thought toward a more precise and
prescriptive view of boundary node behaviour.

The IETF Secretariat.

_______________________________________________
PCN mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/pcn