From mpls-bounces@lists.ietf.org Tue Sep 06 15:50:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ECjSG-0000zy-P9; Tue, 06 Sep 2005 15:50:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ECjSE-0000yh-Gl
	for mpls@megatron.ietf.org; Tue, 06 Sep 2005 15:50:02 -0400
Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19078
	for <mpls@lists.ietf.org>; Tue, 6 Sep 2005 15:50:00 -0400 (EDT)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ECjSE-0000Ip-44; Tue, 06 Sep 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ECjSE-0000Ip-44@newodin.ietf.org>
Date: Tue, 06 Sep 2005 15:50:02 -0400
Cc: mpls@ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-lsp-ping-00.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-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 Multiprotocol Label Switching Working Group of the IETF.

	Title		: Detecting Data Plane Failures in 
                          Point-to-Multipoint MPLS Traffic 
                          Engineering - Extensions to LSP Ping
	Author(s)	: S. Yasukawa, et al.
	Filename	: draft-ietf-mpls-p2mp-lsp-ping-00.txt
	Pages		: 18
	Date		: 2005-9-6
	
   Recent proposals have extended the scope of Multi-Protocol Label
   Switching (MPLS) traffic engineered Label Switched Paths (TE LSPs)
   to encompass point-to-multipoint (P2MP) TE LSPs.

   The requirement for a simple and efficient mechanism that can be
   used to detect data plane failures in point-to-point (P2P) MPLS LSPs
   has been recognised and has led to the development of techniques
   for fault detection and isolation commonly referred to as ^LSP Ping^.
   The scope of this document is fault detection and isolation for P2MP
   MPLS TE LSPs. This documents does not replace any of the mechanism of
   LSP Ping, but clarifies their applicability to P2MP MPLS TE LSPs, and
   extends the techniques and mechanisms of LSP Ping to the P2MP TE
   environment.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-lsp-ping-00.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-mpls-p2mp-lsp-ping-00.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-mpls-p2mp-lsp-ping-00.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: <2005-9-6122456.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-p2mp-lsp-ping-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mpls-p2mp-lsp-ping-00.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-6122456.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Tue Sep 06 22:39:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ECpqG-00064M-MF; Tue, 06 Sep 2005 22:39:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ECpqE-000642-7j
	for mpls@megatron.ietf.org; Tue, 06 Sep 2005 22:39:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22322
	for <mpls@ietf.org>; Tue, 6 Sep 2005 22:39:12 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ECptH-0005NS-Tk
	for mpls@ietf.org; Tue, 06 Sep 2005 22:42:26 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-3.cisco.com with ESMTP; 06 Sep 2005 19:39:03 -0700
X-IronPort-AV: i="3.96,173,1122879600"; 
	d="scan'208"; a="339347442:sNHT34628828"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j872co50007550
	for <mpls@ietf.org>; Tue, 6 Sep 2005 19:39:01 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 6 Sep 2005 19:38:53 -0700
Received: from [192.168.1.102] ([10.21.98.205]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Tue, 6 Sep 2005 19:38:53 -0700
Message-ID: <431E52C2.7000508@cisco.com>
Date: Tue, 06 Sep 2005 22:38:58 -0400
From: Vanson Lim <vlim@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'George Swallow'" <swallow@cisco.com>, mpls@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Sep 2005 02:38:53.0332 (UTC)
	FILETIME=[494D4540:01C5B355]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] last call comments for draft-ietf-mpls-lsr-self-test-05.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

George,

My last call comments on the lsr self-test draft sent also to the MPLS 
working group.

Regards,

-Vanson


1) Should the ipv4/6 reply-to object be combined into a single tlv with 
ipv4/6 identified by an address type field?

2) Since the replying router (LSR-D) doesn't bother with performing any 
processing should the default behavior be to return "retcode 0 (No 
return code)".

Here are the return codes which appear to be valid for use in the 
Validation Reply:

    0    No return code
    1    Malformed echo request received
    2    One or more of the TLVs was not understood

3) Should we include the reply Tos TLV and vendor private tlvs in list 
of TLVs that the MPLS Data Plane verification request can contain.   
Currently the draft lists the following as valid tlvs:

         Type #               Object
         ------               -----------
           3                  Pad
           5                  Vendor Enterprise Code
          11 (provisional)    IPv4 Reply-to Object
          12 (provisional)    IPv6 Reply-to Object

4) In Verification Reply list of valid TLVs:

- Remove "type 4" as it's no longer defined in the LSP ping draft
- Add Type 9 "Errored TLVs".
- State that "vendor private TLVs" may also be included.
- Revise the the list to reflect that the IPv4/v6 Interface label stack 
object has been combined into a single TLV.

 >>    The MPLS Data Plane Verification Reply message MAY contain
 >> the following objects:
 >>
 >>        Type #            Object
 >>       ------            -----------
 >>        3               Pad
 >>        4               Error Code
 >>        5               Vendor Enterprise Code
 >>        7               IPv4 Interface and Label Stack Object
 >>        8               IPv6 Interface and Label Stack Object




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



From mpls-bounces@lists.ietf.org Wed Sep 07 11:25:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ED1nN-00009P-FU; Wed, 07 Sep 2005 11:25:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ED1nH-00007H-FO
	for mpls@megatron.ietf.org; Wed, 07 Sep 2005 11:25:01 -0400
Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25749
	for <mpls@lists.ietf.org>; Wed, 7 Sep 2005 11:24:57 -0400 (EDT)
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1ED1nG-0005Xq-PU; Wed, 07 Sep 2005 11:24:58 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1ED1nG-0005Xq-PU@newodin.ietf.org>
Date: Wed, 07 Sep 2005 11:24:58 -0400
Cc: mpls@ietf.org
Subject: [mpls] Last Call: 'Avoiding Equal Cost Multipath Treatment in MPLS
 Networks' to BCP 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

The IESG has received a request from the Multiprotocol Label Switching WG to 
consider the following document:

- 'Avoiding Equal Cost Multipath Treatment in MPLS Networks '
   <draft-ietf-mpls-ecmp-bcp-01.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-09-21.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ecmp-bcp-01.txt


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



From mpls-bounces@lists.ietf.org Thu Sep 08 08:27:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EDLUx-0004Uy-Lq; Thu, 08 Sep 2005 08:27:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EDHsL-00052M-Fn; Thu, 08 Sep 2005 04:35:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07325;
	Thu, 8 Sep 2005 04:35:12 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EDHva-0004sD-5N; Thu, 08 Sep 2005 04:38:42 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j888YnLa020784;
	Thu, 8 Sep 2005 16:34:49 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by 
	rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j888Ymwr020760;
	Thu, 8 Sep 2005 16:34:48 +0800 (SGT)
Received: from i2r.a-star.edu.sg (localhost [127.0.0.1])by 
	mailhost.lit.org.sg (Sun Java System Messaging Server 6.1 HotFix
	0.06(built
	Nov 11 2004)) with ESMTP id <0IMH00AHGP67A1A0@mailhost.lit.org.sg>;
	Thu,08 Sep 2005 16:34:55 +0800 (SGT)
Received: from [192.122.139.152] by mailhost.lit.org.sg (mshttpd); Thu,08 
	Sep 2005 16:34:55 +0800
Date: Thu, 08 Sep 2005 16:34:55 +0800
From: Yeo Boon Sain <yeobs@i2r.a-star.edu.sg>
Message-id: <6ec40be27b5.4320682f@i2r.a-star.edu.sg>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.06 (built Nov 
	112004)
Content-type: text/plain;
	charset=tis-620
Content-language: en
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: en
Priority: normal
X-imss-version: 2.031
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 08 Sep 2005 08:27:22 -0400
Subject: [mpls] CFP -- SensorWare 2005
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

(My apologies if you receive multiple copies of this message)
 =

***********************************************************
1st International Workshop on Software for Sensor Networks (SensorWare) =
=96 CFP
***********************************************************
 =

 =

Welcome to the 1st International Workshop on Software for Sensor Network=
s (SensorWare) to be held on the 8 January 2006=2E The workshop is held =
in conjunction with COMSWARE 2006 in the beautiful and historical city o=
f New Delhi=2E
 =

 =

Advances in technology have made deployment of miniature sensors a reali=
stic proposition=2E These sensors are low-power=2C inexpensive=2C smart =
devices with multiple on-board sensors=2C and are connected through wire=
less links=2C so as to form a collaborative sensor network to perform a =
specific task=2E As a result=2C it opens up a new paradigm of ubiquitous=
 computing and enables a range of applications that are previously unrea=
lizable or too costly to be realized=2E However=2C given the limitation =
of on-board hardware=2C one of the key areas towards achieving superior =
performance is through the software implementation=2E The workshop is in=
tended for the presentation and discussion of novel algorithms and softw=
are implementation for sensor networks=2E This workshop=2C intends to br=
ing together engineering experts and academicians to discuss the current=
 status=2C technical challenges=2C standards=2C fundamental issues=2C an=
d future services and applications in the form of panels and technical p=
resentation=2E
 =

 =

 =

Topics of interest include but are not limited to the following=3A
 =

 =

 =

Operating System =

Efficient algorithms =

Protocol design =

Performance analysis =

Performance related issues =

Sensor applications =

Deployment issues and scenarios =

Middleware =

Sensor security =

Sensor network design and modeling =

 =

 =

Workshop co-chairs=3A
 =

Nirmala Shenoy (ns=40rit=2Eedu)=2C RIT=2C USA
Boon Sain Yeo (boonyeo=40ieee=2Eorg)=2C Institute for Infocomm Research=2C=
 Singapore =

 =

 =

 =

TPC Members=3A
 =

Holger Karl=2C University of Paderborn=2C Germany=2C
Ling-Jyh Chen=2C Academia Sinica=2C Taiwan
Kui Wu=2C University of Victoria=2C Canada=2C
Daeyoung Kim=2C ICU=2C Korea
Leonard Barolli=2C Fukuoka Institute of Technology=2C Japan=2C
Wei-Peng Chen=2C Fujitsu Labs of America=2C USA
Jason Redi=2C BBN Technologies=2C USA      =

Biao Chen=2C Syracuse University=2C USA
Hairong  Qi=2C University of Tennessee=2C USA
Xiaojun Cao=2C Rochester Institute of Technology=2C USA
Xin Wang=2C University of Buffalo=2C USA
James Minseok Kwon=2C RIT=2C USA
Wenye Wang=2C North Carolina State University=2C USA
Fei Hu=2C RIT=2C USA
Robin Chellappa=2C Deakin Univeristy=2C Australia  =

 =

Technical Papers has to be submitted to the co-chairs at boonyeo=40ieee=2E=
org=2E =

 =

Papers should be written in English and should preferably follow the ins=
tructions in template=2Epdf=2E Preferred maximum paper length is 6 print=
ed pages (10-point font) including figures=2E

Important Dates=3A
 =

Paper Submission Deadline=3A 1 October 2005
Notification Acceptance/Rejection=3A 1 November 2005
Final Camera-Ready Paper Submission=3A 1 December 2005
 =

Please visit the workshop website at http=3A//www=2Esensorware=2Eorg for=
 more info=2E
 =

We look forward to seeing you at SensorWare=2E
 =

Many thanks
Best regards=2C
 =

Boon and Nirmala
Workshop co-chairs


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



From mpls-bounces@lists.ietf.org Mon Sep 12 15:50:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EEuJZ-0004Qb-Id; Mon, 12 Sep 2005 15:50:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EEuJX-0004Px-DB
	for mpls@megatron.ietf.org; Mon, 12 Sep 2005 15:50:04 -0400
Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11806
	for <mpls@lists.ietf.org>; Mon, 12 Sep 2005 15:50:01 -0400 (EDT)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EEuJX-0004Eb-0l; Mon, 12 Sep 2005 15:50:03 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EEuJX-0004Eb-0l@newodin.ietf.org>
Date: Mon, 12 Sep 2005 15:50:03 -0400
Cc: mpls@ietf.org
Subject: [mpls] I-D
	ACTION:draft-ietf-mpls-explicit-resource-control-bundle-00.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-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 Multiprotocol Label Switching Working Group of the IETF.

	Title		: Component Link Recording and Resource Control
                          for GMPLS Link Bundles 
	Author(s)	: A. Zamfir, et al.
	Filename	: draft-ietf-mpls-explicit-resource-control-bundle-00.txt
	Pages		: 12
	Date		: 2005-9-12
	
   Record Route is a useful administrative tool that has been used 
   extensively by the service providers. However, when TE links are 
   bundled, identification of label resource in RRO is not enough for 
   the administrative purpose. Network service providers would like to 
   know the component link within a TE link that is being used by a 
   given LSP. In other words, when link bundling is used, resource 
   recording requires mechanisms to specify the component link 
   identifier, along with the TE link identifier and Label. As , it is 
   not possible to record component link in the RRO, this draft defines 
   the extensions to RSVP-TE [RFC3209] and [RFC3473] to specify 
   component link identifiers for resource recording purposes.  
    
   This draft also defines the ERO counterpart of the RRO extension. The 
   ERO extensions are needed to perform explicit label/ resource control 
   over bundled TE link. Hence, this draft defines the extensions to 
   RSVP-TE [RFC3209] and [RFC3473] to specify component link identifiers 
   for explicit resource control and recording over GMPLS link bundles.  

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-explicit-resource-control-bundle-00.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-mpls-explicit-resource-control-bundle-00.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-mpls-explicit-resource-control-bundle-00.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: <2005-9-12130919.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-explicit-resource-control-bundle-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mpls-explicit-resource-control-bundle-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-12130919.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Tue Sep 13 17:45:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFIaX-0001R9-Ka; Tue, 13 Sep 2005 17:45:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EFIaU-0001NC-4p
	for mpls@megatron.ietf.org; Tue, 13 Sep 2005 17:45:11 -0400
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28786
	for <mpls@lists.ietf.org>; Tue, 13 Sep 2005 17:45:01 -0400 (EDT)
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 j8DLhXk03797;
	Tue, 13 Sep 2005 14:43:33 -0700 (PDT)
Message-Id: <200509132143.j8DLhXk03797@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, 13 Sep 2005 14:43:33 -0700
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 4182 on Removing a Restriction on the use of MPLS
	Explicit NULL
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org


--NextPart


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


        RFC 4182

        Title:      Removing a Restriction on the use of
                    MPLS Explicit NULL
        Author(s):  E. Rosen
        Status:     Standards Track
        Date:       September 2005
        Mailbox:    erosen@cisco.com
        Pages:      7
        Characters: 14087
        Updates:    3032

        I-D Tag:    draft-ietf-mpls-explicit-null-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4182.txt


The label stack encoding for Multi-protocol Label Switching (MPLS)
defines a reserved label value known as "IPv4 Explicit NULL" and a
reserved label value known as "IPv6 Explicit NULL".  Previously, these
labels were only legal when they occurred at the bottom of the MPLS
label stack.  This restriction is now removed, so that these label
values may legally occur anywhere in the stack.

This document updates RFC 3032.

This document is a product of the Multiprotocol Label Switching
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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050913144228.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc4182

--OtherAccess
Content-Type: Message/External-body; name="rfc4182.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050913144228.RFC@RFC-EDITOR.ORG>


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

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

--NextPart--




From mpls-bounces@lists.ietf.org Wed Sep 14 09:03:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFWuj-0004Jj-Vh; Wed, 14 Sep 2005 09:03:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EFWuf-0004Hm-3f
	for mpls@megatron.ietf.org; Wed, 14 Sep 2005 09:02:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08945
	for <mpls@ietf.org>; Wed, 14 Sep 2005 09:02:55 -0400 (EDT)
Received: from oberon.imc.kth.se ([193.10.152.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFWzE-0001Lj-H9
	for mpls@ietf.org; Wed, 14 Sep 2005 09:07:43 -0400
Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140])
	by oberon.imc.kth.se (8.11.6/8.11.6) with ESMTP id j8ECxdK21739
	for <mpls@ietf.org>; Wed, 14 Sep 2005 14:59:39 +0200
Received: from [127.0.0.1] ([172.16.2.190])
	by mail1.imc.kth.se; Wed, 14 Sep 2005 15:01:25 +0200
Message-ID: <43281F23.3000102@pi.se>
Date: Wed, 14 Sep 2005 15:01:23 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mpls@ietf.org
References: <430AC987.800@pi.se>
In-Reply-To: <430AC987.800@pi.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: Bill Fenner <fenner@research.att.com>
Subject: [mpls] working group last call on
 draft-ietf-mpls-lsr-self-test-05.txt - ended
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Working group,

his working group last call has ended, there were
a few comments that the author are requested to take care
of and respond to.

/Loa and George

Loa Andersson wrote:
> Working Group,
> 
> this mail initiates a two week working group last call on
> Label Switching Router Self-Test <draft-ietf-mpls-lsr-self-test-05.txt>.
> 
> The last call ends Wednesday September 7 EOB PST. Please send your
> comments to the working group mailing list.
> 
> Loa and George
> 


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.se

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



From mpls-bounces@lists.ietf.org Thu Sep 15 17:52:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EG1es-00009m-ME; Thu, 15 Sep 2005 17:52:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EG1eq-00009S-Te
	for mpls@megatron.ietf.org; Thu, 15 Sep 2005 17:52:40 -0400
Received: from ns1.cpanel.btnaccess.com (ns1.cpanel.btnaccess.com
	[205.177.121.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12615
	for <mpls@lists.ietf.org>; Thu, 15 Sep 2005 17:52:37 -0400 (EDT)
Received: from [65.213.193.26] (helo=ISODELL002)
	by ns1.cpanel.btnaccess.com with esmtp (Exim 4.52)
	id 1EG1ep-0004IW-4y
	for mpls@lists.ietf.org; Thu, 15 Sep 2005 17:52:39 -0400
From: "MPLS 2005" <mpls2005@isocore.com>
To: <mpls@ietf.org>
Date: Thu, 15 Sep 2005 17:52:26 -0400
Message-ID: <000901c5ba3f$c631b6e0$1ac1d541@workgroup>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ns1.cpanel.btnaccess.com
X-AntiAbuse: Original Domain - lists.ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - isocore.com
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] MPLS 2005: Early Registration Deadline in 3 Days
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

MPLS 2005 International Conference
October 16-19, 2005
Omni Shoreham Hotel
Washington, DC 


MPLS 2005 International Conference will be held from Sunday October 16
through Wednesday October 19, 2005 at the Omni Shoreham Hotel in
Washington DC. 
Registration for the MPLS 2005 International Conference is now open,
with only THREE days left to take advantage of the discounted
registration rates [early registration discount cut off date is
September 17]. Go to www.mpls2005.com/registration.htm to register. 
Take advantage of this opportunity and register NOW! 





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



From mpls-bounces@lists.ietf.org Tue Sep 20 04:40:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHdfZ-0003Rz-2F; Tue, 20 Sep 2005 04:40:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EHdfW-0003RU-Fl
	for mpls@megatron.ietf.org; Tue, 20 Sep 2005 04:40:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15844
	for <mpls@ietf.org>; Tue, 20 Sep 2005 04:40:00 -0400 (EDT)
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EHdlG-0005iB-Aq
	for mpls@ietf.org; Tue, 20 Sep 2005 04:46:02 -0400
Received: from [81.183.251.5] (helo=[172.28.43.120])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1EHdf5-0006Da-TA; Tue, 20 Sep 2005 10:39:40 +0200
Message-ID: <432FCA7B.5090704@pi.se>
Date: Tue, 20 Sep 2005 10:38:19 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: gels@rtg.ietf.org, mpls@ietf.org, ccamp@ops.ietf.org, pwe3 <pwe3@ietf.org>,
	l1vpn@ietf.org, L2VPN <l2vpn@ietf.org>,
	"Developing a hybrid router/bridge." <rbridge@postel.org>,
	rtgwg@ietf.org, rtg-dir@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam detection software, running on the system "fw.testbed.se",
	has
	identified this incoming email as possible spam. The original message
	has been attached to this so you can view it (if it isn't spam) or
	label similar future email.  If you have any questions, see
	the administrator of that system for details.
	Content preview:  All, following the discussion in the CCAMP working
	group on the L2SC design team report, the discussion continued off-line
	and the idea to hold a GMPLS Ethernet BoF in Vancouver was born. We
	have collected bits and pieces of the discussion so far and tried to
	come up with a way to proceed. We have put together a more focused
	proposal for GMPLS controled Ethernet Label Switching and have
	requested that a BoF will be held in Vancouver. This request has been
	approved by the Routing Area directors. [...] 
	Content analysis details:   (0.0 points, 5.0 required)
	pts rule name              description
	---- ----------------------
	--------------------------------------------------
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] GMPLS Ethernet in Vancouver
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

All,

following the discussion in the CCAMP working group on the L2SC design
team report, the discussion continued off-line and the idea to hold a
GMPLS Ethernet BoF in Vancouver was born. We have collected bits and
pieces of the discussion so far and tried to come up with a way to
proceed. We have put together a more focused proposal for GMPLS
controled Ethernet Label Switching and have requested that a BoF will
be held in Vancouver. This request has been approved by the Routing
Area directors.

A draft draft-andersson-gels-bof-prep-00.txt has been published to serve
as a starting point for the discussion at the BoF. The intention has
been to reflect the GMPLS Ethernet discussion so far, without any claim
to be complete or "objective", but to specify limited and focused
work that can serve starting as a point for GMPLS controlled Ethernet
Label Switching.

A mailing list has been set up to host the discussion before the BoF to
subscribe to the mailing list send mail to

gels-request@rtg.ietf.org (subsribe) in body or subject

or visit

https://rtg.ietf.org/mailman/listinfo/gels

Looking forward to comments and discussion.



/Loa and Dimitri



-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.se

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



From mpls-bounces@lists.ietf.org Tue Sep 20 15:50:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHo8A-0001Z2-Rz; Tue, 20 Sep 2005 15:50:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EHo7u-0001S3-9f
	for mpls@megatron.ietf.org; Tue, 20 Sep 2005 15:50:03 -0400
Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26881
	for <mpls@lists.ietf.org>; Tue, 20 Sep 2005 15:49:59 -0400 (EDT)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EHo7t-00020g-Ol; Tue, 20 Sep 2005 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EHo7t-00020g-Ol@newodin.ietf.org>
Date: Tue, 20 Sep 2005 15:50:01 -0400
Cc: mpls@ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-ldp-experience-00.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-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 Multiprotocol Label Switching Working Group of the IETF.

	Title		: Experience with the LDP protocol
	Author(s)	: L. Andersson, et al.
	Filename	: draft-ietf-mpls-ldp-experience-00.txt
	Pages		: 
	Date		: 2005-9-20
	
   The purpose of this memo is to document how some of the requirements
   specified in RFC 1264 for advancing protocols developed by working
   groups within the IETF Routing Area to Draft Standard have been
   satisfied by LDP (Label Distribution Protocol).  Specifically, this
   report documents operational experience with LDP, requirement 5 of
   section 5.0 in RFC 1264.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-experience-00.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-mpls-ldp-experience-00.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-mpls-ldp-experience-00.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: <2005-9-20105742.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-ldp-experience-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mpls-ldp-experience-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-20105742.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Wed Sep 21 15:50:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIAbV-00081X-Fu; Wed, 21 Sep 2005 15:50:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIAbS-0007zP-6d
	for mpls@megatron.ietf.org; Wed, 21 Sep 2005 15:50:02 -0400
Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15276
	for <mpls@lists.ietf.org>; Wed, 21 Sep 2005 15:50:00 -0400 (EDT)
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EIAbR-00063x-MR; Wed, 21 Sep 2005 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EIAbR-00063x-MR@newodin.ietf.org>
Date: Wed, 21 Sep 2005 15:50:01 -0400
Cc: mpls@ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-icmp-04.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-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 Multiprotocol Label Switching Working Group of the IETF.

	Title		: ICMP Extensions for MultiProtocol Label Switching
	Author(s)	: R. Bonica, et al.
	Filename	: draft-ietf-mpls-icmp-04.txt
	Pages		: 8
	Date		: 2005-9-21
	
This memo defines an extension to ICMP that permits Label Switching
   Routers to append MPLS information to ICMP messages.  This extension
   has already been widely deployed and this memo is introduced to
   describe existing practice.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-icmp-04.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-mpls-icmp-04.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-mpls-icmp-04.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: <2005-9-21105540.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-icmp-04.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-mpls-icmp-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-21105540.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Wed Sep 21 16:13:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIAyS-0002Hc-3A; Wed, 21 Sep 2005 16:13:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIAyP-0002Cm-9I; Wed, 21 Sep 2005 16:13:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22067;
	Wed, 21 Sep 2005 16:13:43 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EIB4R-0007QV-LH; Wed, 21 Sep 2005 16:20:02 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 21 Sep 2005 21:13:13 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 21 Sep 2005 21:13:21 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Wed, 21 Sep 2005 16:13:19 -0400
Received: from [172.23.8.221] ([172.23.8.221] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 21 Sep 2005 16:14:35 -0400
Message-ID: <4331BEDC.6080609@juniper.net>
Date: Wed, 21 Sep 2005 16:13:16 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mpls@ietf.org, Internet Area <int-area@ietf.org>
X-Enigmail-Version: 0.92.1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Sep 2005 20:14:35.0328 (UTC)
	FILETIME=[15DB5400:01C5BEE9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] ICMP and MPLS
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Folks,

At the request of the Internet Area, I have split
draft-ietf-mpls-icmp-03 into two parts. These are:

- http://www.ietf.org/internet-drafts/draft-bonica-internet-icmp-00.txt
- http://www.ietf.org/internet-drafts/draft-ietf-mpls-icmp-04.txt

The first draft describes the generic syntax for ICMP extensions and
backwards compatibility issues. This draft will probably be owned by the
Internet Area.

The second draft describes MPLS specific extensions. This draft will
probably continue to be owned by the MPLS WG. The second draft
references the first.

Please review and comment on these drafts. Since the resulting
discussion will probably be of interest to both communities, I have
posted this request to both the MPLS and Internet Area mailing lists.

                                     Ron

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



From mpls-bounces@lists.ietf.org Fri Sep 23 11:01:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIp3F-0002GB-Cx; Fri, 23 Sep 2005 11:01:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIp3C-0002G0-Si
	for mpls@megatron.ietf.org; Fri, 23 Sep 2005 11:01:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20087
	for <mpls@ietf.org>; Fri, 23 Sep 2005 11:01:20 -0400 (EDT)
Received: from oberon.imc.kth.se ([193.10.152.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIp9c-0000Vi-6H
	for mpls@ietf.org; Fri, 23 Sep 2005 11:08:03 -0400
Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140])
	by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id j8NF4wUG004487
	for <mpls@ietf.org>; Fri, 23 Sep 2005 17:04:59 +0200
Received: from [127.0.0.1] ([172.16.2.190])
	by mail1.imc.kth.se; Fri, 23 Sep 2005 16:59:54 +0200
Message-ID: <433417E9.50601@pi.se>
Date: Fri, 23 Sep 2005 16:57:45 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mpls@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] [Fwd: Internet-Drafts Submission Cutoff Dates for the 64th
 IETF Meeting in Vancouver, British Columbia, Canada]
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Working Group,

be aware of the Internet Drafts Cutof dates for Vancouver.


/Loa

-------- Original Message --------
Subject: Internet-Drafts Submission Cutoff Dates for the 64th IETF 
Meeting in Vancouver, British Columbia, Canada
Date: Fri, 23 Sep 2005 00:00:02 -0400
From: ietf-secretariat@ietf.org
To: ietf-announce@ietf.org


There are two (2) Internet-Draft cutoff dates for the 64th
IETF Meeting in Vancouver, British Columbia, Canada:

October 17th: Cutoff Date for Initial (i.e., version -00)
Internet-Draft Submissions

All initial Internet-Drafts (version -00) must be submitted by Monday,
October 17th at 9:00 AM ET. 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,
October 10th at 9:00 AM ET.

October 24th: 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, October 24th at 9:00 AM ET.

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, November 7th at 9:00
AM ET, when Internet-Draft posting resumes.  Please do not wait until
the last minute to submit.

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 64th IETF Meeting can be found at 
http://www.ietf.org/meetings/cutoff_dates_64.html.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce



-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.se

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



From mpls-bounces@lists.ietf.org Fri Sep 23 14:32:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIsLK-0002xv-0R; Fri, 23 Sep 2005 14:32:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFlQU-0000Mx-7b; Thu, 15 Sep 2005 00:32:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02833;
	Thu, 15 Sep 2005 00:32:41 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EFlV9-00030r-In; Thu, 15 Sep 2005 00:37:39 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j8F4W2QA010909;
	Thu, 15 Sep 2005 12:32:02 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by 
	rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j8F4W0LF010877;
	Thu, 15 Sep 2005 12:32:00 +0800 (SGT)
Received: from i2r.a-star.edu.sg (localhost [127.0.0.1])by 
	mailhost.lit.org.sg (Sun Java System Messaging Server 6.1 HotFix
	0.06(built
	Nov 11 2004)) with ESMTP id <0IMU005POCL3I8A0@mailhost.lit.org.sg>;
	Thu,15 Sep 2005 12:31:51 +0800 (SGT)
Received: from [192.122.139.152] by mailhost.lit.org.sg (mshttpd); Thu,15 
	Sep 2005 12:31:51 +0800
Date: Thu, 15 Sep 2005 12:31:51 +0800
From: Yeo Boon Sain <yeobs@i2r.a-star.edu.sg>
Message-id: <503e15cb42b3.432969b7@i2r.a-star.edu.sg>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.06 (built Nov 
	112004)
Content-type: text/plain;
	charset=tis-620
Content-language: en
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: en
Priority: normal
X-imss-version: 2.031
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 23 Sep 2005 14:32:15 -0400
Subject: [mpls] CFP -- SensorWare 2006 (Dates changed)
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

(My apologies if you receive multiple copies of this message)
 =

***********************************************************
1st International Workshop on Software for Sensor Networks (SensorWare) =
=96 CFP
***********************************************************
 =

 =

Welcome to the 1st International Workshop on Software for Sensor Network=
s (SensorWare) to be held on the 8 January 2006=2E The workshop is held =
in conjunction with COMSWARE 2006 in the beautiful and historical city o=
f New Delhi=2E
 =

 =

Advances in technology have made deployment of miniature sensors a reali=
stic proposition=2E These sensors are low-power=2C inexpensive=2C smart =
devices with multiple on-board sensors=2C and are connected through wire=
less links=2C so as to form a collaborative sensor network to perform a =
specific task=2E As a result=2C it opens up a new paradigm of ubiquitous=
 computing and enables a range of applications that are previously unrea=
lizable or too costly to be realized=2E However=2C given the limitation =
of on-board hardware=2C one of the key areas towards achieving superior =
performance is through the software implementation=2E The workshop is in=
tended for the presentation and discussion of novel algorithms and softw=
are implementation for sensor networks=2E This workshop=2C intends to br=
ing together engineering experts and academicians to discuss the current=
 status=2C technical challenges=2C standards=2C fundamental issues=2C an=
d future services and applications in the form of panels and technical p=
resentation=2E
 =

 =

 =

Topics of interest include but are not limited to the following=3A
 =

 =

 =

Operating System =

Efficient algorithms =

Protocol design =

Performance analysis =

Performance related issues =

Sensor applications =

Deployment issues and scenarios =

Middleware =

Sensor security =

Sensor network design and modeling =

 =

 =

Workshop co-chairs=3A
 =

Nirmala Shenoy (ns=40rit=2Eedu)=2C RIT=2C USA
Boon Sain Yeo (boonyeo=40ieee=2Eorg)=2C Institute for Infocomm Research=2C=
 Singapore =

 =

 =

 =

TPC Members=3A
 =

Holger Karl=2C University of Paderborn=2C Germany=2C
Ling-Jyh Chen=2C Academia Sinica=2C Taiwan
Kui Wu=2C University of Victoria=2C Canada=2C
Daeyoung Kim=2C ICU=2C Korea
Leonard Barolli=2C Fukuoka Institute of Technology=2C Japan=2C
Wei-Peng=2C Fujitsu Labs of America=2C USA
Jason Redi=2C BBN Technologies=2C USA      =

Biao Chen=2C Syracuse University=2C USA
Hairong  Qi=2C University of Tennessee=2C USA
Xiaojun Cao=2C Rochester Institute of Technology=2C USA
Xin Wang=2C University of Buffalo=2C USA
James Minseok Kwon=2C RIT=2C USA
Wenye Wang=2C North Carolina State University=2C USA
Fei Hu=2C RIT=2C USA
Robin Chellappa=2C Deakin Univeristy=2C Australia  =

 =

Technical Papers has to be submitted to the co-chairs at boonyeo=40ieee=2E=
org=2E =

 =

Papers should be written in English and should preferably follow the ins=
tructions in template=2Epdf=2E Preferred maximum paper length is 6 print=
ed pages (10-point font) including figures=2E
 =


Important Dates=3A
 =

Paper Submission Deadline=3A 1 Oct 2005
Notification Acceptance/Rejection=3A 1 Nov 2005
Final Camera-Ready Paper Submission=3A 1 Dec 2005
 =

Please visit the workshop website at http=3A//www=2Esensorware=2Eorg for=
 more info=2E
 =

We look forward to seeing you at SensorWare=2E
 =

Many thanks
Best regards=2C
 =

Boon and Nirmala
Workshop co-chairs


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



From mpls-bounces@lists.ietf.org Sun Sep 25 12:56:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EJZUv-000444-WA; Sun, 25 Sep 2005 12:37:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EJZUi-0003wY-E4
	for mpls@megatron.ietf.org; Sun, 25 Sep 2005 12:36:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18474
	for <mpls@ietf.org>; Sun, 25 Sep 2005 12:36:37 -0400 (EDT)
Received: from relay1.mail.uk.clara.net ([80.168.70.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EJZbO-0001Vn-1u
	for mpls@ietf.org; Sun, 25 Sep 2005 12:43:47 -0400
Received: from du-069-0011.access.clara.net ([217.158.132.11] helo=Puppy)
	by relay1.mail.uk.clara.net with smtp (Exim 4.46) id 1EJZUL-0009xx-IN
	for mpls@ietf.org; Sun, 25 Sep 2005 17:36:30 +0100
Message-ID: <153501c5c1ef$b2a1cd60$28849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mpls@ietf.org>
Date: Sun, 25 Sep 2005 17:35:33 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] Questions about P2MP LSP Ping
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Hi,

In Paris we asked two questions about P2MP LSP Ping (now
draft-ietf-mpls-p2mp-lsp-ping-00.txt)

1. Is there a requirement to be able to ping a subset of the total set of
leaves?

Currently the draft allows you to ping one or all of the leaves. If you
ping all of the leaves you may specify a jitter to reduce the stress on
the ingress LSR and its surrounding network.

An earlier version of the draft included the ability to specify a subset
of leaves that were being pinged. We removed this feature because we felt
that it placed significant processing overhead leaves during ping
processing and on branches during traceroute processing.

We would like to hear from you if you believe that we should reintroduce
this feature.

2. Should we include support for multicast-LDP in this I-D?

It is clear that many of the features of P2MP LSP Ping will be the same
for P2MP MPLS-TE and mLDP. However, several features will be considerably
different, not least the fact that the ingress of an mLDP LSP is unlikely
to know the identities of the egresses. This might put ping for mLDP LSPs
into the same arena as ping for multicast IP.

Given these considerations and the fact that P2MP MPLS-TE is considerably
more advanced through the specification process than mLDP, should we aim
to include both in this I-D, or should we separate them?

Thanks for any opinions.

Adrian


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



From mpls-bounces@lists.ietf.org Mon Sep 26 05:34:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EJpNw-0002Eh-E4; Mon, 26 Sep 2005 05:34:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EJkOa-0007MJ-Jm
	for mpls@megatron.ietf.org; Mon, 26 Sep 2005 00:15:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19227
	for <mpls@ietf.org>; Mon, 26 Sep 2005 00:15:13 -0400 (EDT)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EJkVY-0008Vd-JD
	for mpls@ietf.org; Mon, 26 Sep 2005 00:22:29 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.2499); 
	Sun, 25 Sep 2005 21:15:06 -0700
Received: from RED-MSG-42.redmond.corp.microsoft.com ([157.54.12.202]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 25 Sep 2005 21:15:06 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 25 Sep 2005 21:15:01 -0700
Message-ID: <B2A3566DA98E7B4E84B14709B640A19307A7F8BD@RED-MSG-42.redmond.corp.microsoft.com>
Thread-Topic: Call For Papers: Workshop on emerging services delivery
	platforms and software models for Next Generation Network
	Services
Thread-Index: AcXCUN0qf/1D8SiMSVGtCf9hpn+Ivg==
From: "Joshy Joseph" <Joshy.Joseph@microsoft.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 26 Sep 2005 04:15:06.0241 (UTC)
	FILETIME=[E0128710:01C5C250]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 715d0e6950aaebd45af78ef9318d0186
X-Mailman-Approved-At: Mon, 26 Sep 2005 05:34:54 -0400
Cc: 
Subject: [mpls] Call For Papers: Workshop on emerging services delivery
	platforms and software models for Next Generation Network Services
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2050758901=="
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============2050758901==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5C250.DFCB2C37"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5C250.DFCB2C37
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

Apologies, if you receive multiple copies of this request.

=20

Call For Papers:  Workshop on emerging services delivery platforms and
software models for Next Generation Network Services
(http://www.softplatforms.org)

This workshop will be held in conjunction with the FIRST International
Conference on COMmunication System softWAre and MiddlewaRE (COMSWARE
2006) at New Delhi, India (http://www.comsware.org/) from Jan 8-12 2006.


=20

The exact date of the workshop will be made available on the workshop's
Web site http://www.softplatforms.org.

=20

Workshop Objectives:=20

The next generation services networks deliver enhanced business
capabilities such as data, video, messaging and business functions for
wired and wireless consumers. These new sets of services enhance the
business opportunities by integrating with core business services,
including: supply chain management, customer management, and consumer
applications. This workshop aims to discuss topics related to emerging
next generation services and service delivery platforms to host/support
such complex application environments.=20

=20

The workshop focuses on:

* How next generation service delivery platforms deliver enhanced QoS
management, operational efficiencies, flexible services composability,
faster time-to-market, efficient trust models and flexible pricing
models.

* Technical and business factors influencing the services composability
and network services delivery environments. The associated revenue and
cost models for consumers, suppliers and application providers.

* The influences of emerging distributed computing architecture styles
(loosely-coupled, asynchronous, compos able, collaborative,
decentralized and parallel services) related to service delivery models.

* Emerging middleware platforms for network services, service
composability, distributed architecture models and programming models.

* New services models (communication services, presence-enabled
services, content/media services and enterprise/legacy services) and
value creation environments that represents new business opportunities
for operators and providers.

=20

This workshop invites papers from research and business communities on
the different aspects of service delivery platforms and emerging
services models. The workshop will include papers that examine
interesting practical problems, case studies, best practices, middleware
platforms and innovative messaging architectures.=20

=20

Submission Guidelines:

All papers are limited to 5 pages and must be in standard IEEE
double-column format. All submissions must be sent by email to the
workshops co-chairs with the e-mail addresses given above.=20

=20

Important Dates:=20

Paper Submission Deadline: October 21, 2005=20

Notification of Acceptance: November 11, 2005=20

Camera-Ready Papers: December 4, 2005=20

=20

Contact and organization:

For any questions regarding the workshop feel free to contact=20

1. Craig Fellenstein, IBM (cfellen@us.ibm.com)=20

2. Joshy Joseph, Microsoft (jojoseph@microsoft.com)=20

=20

Submission requirements:

All papers are limited to 5 pages and must be in standard IEEE
double-column format. All submissions must be sent by email to the
workshops co-chairs.


------_=_NextPart_001_01C5C250.DFCB2C37
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Apologies, if you receive multiple copies of this =
request.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Call For Papers:&nbsp; Workshop on emerging services =
delivery
platforms and software models for Next Generation Network Services
(http://www.softplatforms.org)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This workshop will be held in conjunction with the =
FIRST
International Conference on COMmunication System softWAre and MiddlewaRE
(COMSWARE 2006) at <st1:place w:st=3D"on"><st1:City w:st=3D"on">New =
Delhi</st1:City>,
 <st1:country-region w:st=3D"on">India</st1:country-region></st1:place>
(http://www.comsware.org/) from Jan 8-12 2006. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The exact date of the workshop will be made available =
on the
workshop's Web site =
http://www.softplatforms.org.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Workshop Objectives: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The next generation services networks deliver =
enhanced
business capabilities such as data, video, messaging and business =
functions for
wired and wireless consumers. These new sets of services enhance the =
business
opportunities by integrating with core business services, including: =
supply
chain management, customer management, and consumer applications. This =
workshop
aims to discuss topics related to emerging next generation services and =
service
delivery platforms to host/support such complex application =
environments. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The workshop focuses on:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* How next generation service delivery platforms =
deliver
enhanced QoS management, operational efficiencies, flexible services
composability, faster time-to-market, efficient trust models and =
flexible
pricing models.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* Technical and business factors influencing the =
services
composability and network services delivery environments. The associated
revenue and cost models for consumers, suppliers and application =
providers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* The influences of emerging distributed computing =
architecture
styles (loosely-coupled, asynchronous, compos able, collaborative,
decentralized and parallel services) related to service delivery =
models.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* Emerging middleware platforms for network services,
service composability, distributed architecture models and programming =
models.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* New services models (communication services,
presence-enabled services, content/media services and enterprise/legacy
services) and value creation environments that represents new business
opportunities for operators and providers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This workshop invites papers from research and =
business
communities on the different aspects of service delivery platforms and =
emerging
services models. The workshop will include papers that examine =
interesting
practical problems, case studies, best practices, middleware platforms =
and
innovative messaging architectures. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Submission Guidelines:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>All papers are limited to 5 pages and must be in =
standard
IEEE double-column format. All submissions must be sent by email to the
workshops co-chairs with the e-mail addresses given above. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Important Dates: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Paper Submission Deadline: October 21, 2005 =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Notification of Acceptance: November 11, 2005 =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Camera-Ready Papers: December 4, 2005 =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Contact and =
organization:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>For any questions regarding the workshop feel free to =
contact
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>1. Craig Fellenstein, IBM (cfellen@us.ibm.com) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>2. <st1:PersonName w:st=3D"on">Joshy =
Joseph</st1:PersonName>,
Microsoft (jojoseph@microsoft.com) <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Submission requirements:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>All papers are limited to 5 pages and must be in =
standard
IEEE double-column format. All submissions must be sent by email to the
workshops co-chairs.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C5C250.DFCB2C37--


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

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

--===============2050758901==--




From mpls-bounces@lists.ietf.org Mon Sep 26 20:24:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EK3Gg-0007fd-11; Mon, 26 Sep 2005 20:24:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EK3Ge-0007fV-Kg; Mon, 26 Sep 2005 20:24:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20604;
	Mon, 26 Sep 2005 20:24:19 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EK3Nm-0003cS-QG; Mon, 26 Sep 2005 20:31:44 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 27 Sep 2005 01:24:09 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 27 Sep 2005 01:24:09 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Mon, 26 Sep 2005 20:24:08 -0400
Received: from [172.23.1.20] ([172.23.1.20] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 26 Sep 2005 20:25:25 -0400
Message-ID: <43389123.4060808@juniper.net>
Date: Mon, 26 Sep 2005 20:24:03 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mpls@ietf.org, Internet Area <int-area@ietf.org>
Subject: Re: [mpls] ICMP and MPLS
References: <4331BEDC.6080609@juniper.net>
In-Reply-To: <4331BEDC.6080609@juniper.net>
X-Enigmail-Version: 0.92.1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Sep 2005 00:25:26.0125 (UTC)
	FILETIME=[F4E571D0:01C5C2F9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org


Still monitoring for comments.....


Ron Bonica wrote:
> Folks,
> 
> At the request of the Internet Area, I have split
> draft-ietf-mpls-icmp-03 into two parts. These are:
> 
> - http://www.ietf.org/internet-drafts/draft-bonica-internet-icmp-00.txt
> - http://www.ietf.org/internet-drafts/draft-ietf-mpls-icmp-04.txt
> 
> The first draft describes the generic syntax for ICMP extensions and
> backwards compatibility issues. This draft will probably be owned by the
> Internet Area.
> 
> The second draft describes MPLS specific extensions. This draft will
> probably continue to be owned by the MPLS WG. The second draft
> references the first.
> 
> Please review and comment on these drafts. Since the resulting
> discussion will probably be of interest to both communities, I have
> posted this request to both the MPLS and Internet Area mailing lists.
> 
>                                      Ron
> 
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
> 

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



From mpls-bounces@lists.ietf.org Tue Sep 27 09:48:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKFp3-0004vc-Pv; Tue, 27 Sep 2005 09:48:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKFp1-0004vS-Or
	for mpls@megatron.ietf.org; Tue, 27 Sep 2005 09:48:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08952
	for <mpls@ietf.org>; Tue, 27 Sep 2005 09:48:38 -0400 (EDT)
Received: from ns1.cpanel.btnaccess.com ([205.177.121.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKFwE-0005o1-2j
	for mpls@ietf.org; Tue, 27 Sep 2005 09:56:10 -0400
Received: from cpanel by ns1.cpanel.btnaccess.com with local (Exim 4.52)
	id 1EKFon-0004Wt-Jt
	for mpls@ietf.org; Tue, 27 Sep 2005 09:48:25 -0400
Received: from 68.228.14.164 ([68.228.14.164]) by isocore.com (Horde MIME
	library) with HTTP; Tue, 27 Sep 2005 09:48:25 -0400
Message-ID: <20050927094825.radamzmn9m8s0csk@isocore.com>
Date: Tue, 27 Sep 2005 09:48:25 -0400
From: Kavita Khanna <kkhanna@isocore.com>
To: mpls@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ns1.cpanel.btnaccess.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [32001 502] / [47 12]
X-AntiAbuse: Sender Address Domain - isocore.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] MPLS 2005: Oct 16-19, 2005; Washington DC
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

=================================================
     MPLS 2005 International Conference
     Omni Shoreham Hotel, Washington DC
     October 16-19, 2005
     http://www.mpls2005.com
=================================================

You are cordially invited to attend the MPLS 2005 International Conference to be
held in Washington, DC from October 16-19, 2005. The 4-day event consists of
highly technical sessions, tutorials, panel discussions, and exhibits. Program
details are available at:
  <http://www.mpls2005.com/program.htm>

Registration for the conference is open. The online registration deadline is
October 14, 2005. To register, go to:
  <http://www.mpls2005.com/registration.htm>

Important Dates:
------------------
Online Registration deadline: October 14

Tutorials:
  Sun Oct 16: 10:30am - 6:00pm

Technical Tracks:
  Mon Oct 17: 8:30am - 6:00pm
  Tues Oct 18: 8:30am - 6:00pm
  Wed Oct 19: 8:30am - 4:45pm

Exhibits:
  Mon Oct 17: 10:00am - 7:30pm
  Tues Oct 18: 10:00am - 7:30pm
  Wed Oct 19: 10:00am - 2:00pm

Inter-Op Demo:
  Thu Oct 20 (visit <http://www.mpls2005.com/program.htm#interop> for details)

Thank you for your support in making this conference series a premier event in
the industry.




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



From mpls-bounces@lists.ietf.org Tue Sep 27 16:41:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKMGT-0002kW-NE; Tue, 27 Sep 2005 16:41:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKMGS-0002kL-2e
	for mpls@megatron.ietf.org; Tue, 27 Sep 2005 16:41:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19332
	for <mpls@ietf.org>; Tue, 27 Sep 2005 16:41:22 -0400 (EDT)
Received: from mail121.messagelabs.com ([216.82.241.195])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EKMNk-0004nS-T0
	for mpls@ietf.org; Tue, 27 Sep 2005 16:48:58 -0400
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-6.tower-121.messagelabs.com!1127853170!6206731!143
X-StarScan-Version: 5.4.15; banners=-,-,-
X-Originating-IP: [192.128.133.132]
Received: (qmail 26868 invoked from network); 27 Sep 2005 20:41:11 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (192.128.133.132)
	by server-6.tower-121.messagelabs.com with SMTP;
	27 Sep 2005 20:41:11 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by
	attrh3i.attrh.att.com (7.2.052)
	id 4336CAB70005D367 for mpls@ietf.org; Tue, 27 Sep 2005 16:41:11 -0400
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
Date: Tue, 27 Sep 2005 15:41:11 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA93CD@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-01.txt 
Thread-Index: AcXDnxAfy6zuIC1aQoG6mM5BclbvdQAABUhAAAEfSBAAAAV68A==
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <mpls@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [mpls] RE: I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-01.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Hi All,

Please review and comment on the updated draft "Protocol Extensions for
Header Compression over MPLS"
(http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protoco
l-01.txt).

The updates are based primarily on comments from Stewart Bryant, see
http://www1.ietf.org/mail-archive/web/avt/current/msg05722.html
http://www1.ietf.org/mail-archive/web/avt/current/msg05721.html
http://www1.ietf.org/mail-archive/web/avt/current/msg05723.html

The main changes include the following:

1. Section 4.1: Noted the need for IANA to allocate two Pseudowire
Interface Parameter Sub-TLV type values, one for IPCP and the other for
IPV6TP.
2. Section 4.1: Clarified the encoding of the header compression
setup/parameter-negotiation TLVs identified in RFC 3251 and RFC 3544.
3. Section 4.2: Noted the need for IANA to establish a Registry to
assign PW Control Octet values 10-15.
4. Section 7: Text clarified to conform with RFC 2434 requirements and
specified the need for the two new interface parameter sub-TLVs.  Also
specified the need for a Registry for PW Control Octet values 10-15.

Once again, please review and comment on the updated draft. =20

Thanks,
Jerry=20

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Internet-Drafts@ietf.org
Sent: Tuesday, September 27, 2005 3:50 PM
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-01.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Audio/Video Transport Working Group of
the IETF.

	Title		: Protocol Extensions for Header Compression
over MPLS
	Author(s)	: J. Ash, et al.
	Filename	: draft-ietf-avt-hc-over-mpls-protocol-01.txt
	Pages		: 19
	Date		: 2005-9-27
=09
VoIP typically uses the encapsulation voice/RTP/UDP/IP. When MPLS
   labels are added, this becomes voice/RTP/UDP/IP/MPLS-labels. For an
   MPLS VPN, the packet header is typically 48 bytes, while the voice
   payload is often no more than 30 bytes, for example. Header
   compression can significantly reduce the overhead through various
   compression mechanisms.  MPLS is used to route header-compressed (HC)
   packets over an MPLS LSP without compression/decompression cycles at
   each router.  Such an HC over MPLS capability increases the bandwidth
   efficiency as well as processing scalability of the maximum number of
   simultaneous compressed flows that use HC at each router.  MPLS
   pseudowires are used to transport the HC context and other control
   messages between the ingress and egress MPLS label switched router
   (LSR), and the pseudowires define one or more point-to-point
   instances corresponding to each HC session at the header
   decompressor.  Standard HC methods (e.g., ECRTP, ROHC, etc.) are
   re-used to determine the context.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol
-01.txt

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



From mpls-bounces@lists.ietf.org Wed Sep 28 09:45:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKcF6-0000po-Id; Wed, 28 Sep 2005 09:45:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKcF4-0000os-6N
	for mpls@megatron.ietf.org; Wed, 28 Sep 2005 09:45:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07708
	for <mpls@ietf.org>; Wed, 28 Sep 2005 09:45:00 -0400 (EDT)
Received: from relay3.mail.uk.clara.net ([80.168.70.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKcMV-0005bs-SK
	for mpls@ietf.org; Wed, 28 Sep 2005 09:52:45 -0400
Received: from du-069-0014.access.clara.net ([217.158.132.14] helo=Puppy)
	by relay3.mail.uk.clara.net with smtp (Exim 4.46)
	id 1EKcEr-000BBN-DQ; Wed, 28 Sep 2005 14:44:50 +0100
Message-ID: <020801c5c433$3358f010$be849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mpls@ietf.org>
Date: Wed, 28 Sep 2005 13:45:12 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: ccamp@ops.ietf.org
Subject: [mpls] GMPLS MIBs are related to MPLS-TE
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Hi,

During MIB Doctor review of the GMPLS MIB modules it was pointed out that
we have introduced new objects that may be useful extensions to the
management of MPLS-TE systems that used the existing MPLS MIB modules
(RFC3811 onwards).

For example, we have the ability to configure/examine the Hello interval
on a per-interface basis in an extension to the LSR MIB's
mplsInterfaceTable.

Since there will be a brief hiatus while the I-Ds are updated after MIB
Doctor review, now would be a good opportunity for members of the MPLS
community who have not been following the development of the GMPLS MIB
modules within the CCAMP working group to comment on the documents. Of
particular interest to the authors are two questions:
- Are the MPLS-TE features that we have covered handled correctly?
- Are there any MPLS-TE features that we have not included that you feel
should be included?

You can see the three GMPLS MIB documents at:

http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-tc-mib-07.txt
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-lsr-mib-08.txt
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-te-mib-09.txt

You can see the MIB Doctor's comments in the CCAMP mailing list archive.

Many thanks,
Adrian


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



From mpls-bounces@lists.ietf.org Wed Sep 28 14:37:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKgoO-0005Tt-Qo; Wed, 28 Sep 2005 14:37:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKgoM-0005Tl-Hu
	for mpls@megatron.ietf.org; Wed, 28 Sep 2005 14:37:46 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com
	[169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27890
	for <mpls@lists.ietf.org>; Wed, 28 Sep 2005 14:37:45 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
	[169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id
	j8SIbBUk004699; Wed, 28 Sep 2005 14:37:11 -0400 (EDT)
Received: from [169.144.136.107] (usvisdad104641.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA20627; 
	Wed, 28 Sep 2005 14:37:10 -0400 (EDT)
Message-ID: <433AE2D5.5060405@marconi.com>
Date: Wed, 28 Sep 2005 14:37:09 -0400
From: David Charlap <David.Charlap@marconi.com>
Organization: Marconi, Vienna VA
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF MPLS List <mpls@ietf.org>, IETF CCAMP List <ccamp@ops.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Is there any point to implementing RSVP-TE's graceful restart without 
also implementing graceful restart for routing protocols?

On the one hand, RSVP doesn't require routing to recover LSPs.  It knows 
the next-hop interface, because of the preserved data-plane connection. 
  Whatever other information it may need, the switch can either preserve 
this information or recover it from a neighbor using the RecoveryPath 
object (draft-ietf-ccamp-rsvo-restart-ext-03).

On the other hand, nodes more than one hop upstream of the failure will 
detect the loss of routing-connectivity to the failed node if IGP 
graceful restart is not also implemented.  They may reroute the LSP away 
from the failed node, or tear it down altogether, even though the data 
plane is still active and RSVP graceful restart is recovering the 
control-plane state.

An originating node may consider the destination unreachable, as a 
result of losing the routes even though the data-plane for the LSP is 
still up (which can be confirmed via OAM.)

A transit node, when processing an loose ERO-hop, may choose to reroute 
or fail the LSP if its local topology information says that the failed 
(and restarting) node is not available.  It might even choose to do this 
for an established LSP, as a result of Path refresh processing.

My questions are:

1: Does this mean it's pointless to use RSVP graceful restart without
    also using IGP graceful restart (for whatever IGP is active).

2: Is IGP graceful restart sufficient to prevent this problem?  For
    instance, OSPF's restart procedure requires all preserved state to
    be thrown away if a topology change is detected.

3: An originating node can use OAM to validate the data plane of an
    LSP, and choose to ignore what routing tells it about the
    destination's reachability.  But what about transit nodes?  As far
    as I know, MPLS doesn't support segment-OAM, and it would be
    prohibitive for every transit node to run its own OAM streams
    to detect self-to-end connectivity.

4: Are there other solutions to this problem?

One possible solution might be route-pinning, but RSVP doesn't have a 
built-in mechanism for this.  The usual workaround (signal the LSP, 
requesting route-recording, then turn the RRO into an ERO for subsequent 
refreshes) can work, but are there situations where even this would be 
insufficient to prevent a transit node from rerouting/tearing the 
connection in this particular situation (where RSVP is doing a graceful 
restart but the IGP is not)?

-- David

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



From mpls-bounces@lists.ietf.org Thu Sep 29 05:44:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKuxZ-0007sy-6x; Thu, 29 Sep 2005 05:44:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKuxW-0007rQ-Tk
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 05:44:11 -0400
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29352
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 05:44:06 -0400 (EDT)
From: neil.2.harrison@bt.com
Received: from i2km98-ukbr.domain1.systemhost.net ([193.113.197.85]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 29 Sep 2005 10:43:26 +0100
Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by
	i2km98-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(5.0.2195.6713); Thu, 29 Sep 2005 10:43:26 +0100
x-mimeole: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 29 Sep 2005 10:43:26 +0100
Message-ID: <0536FC9B908BEC4597EE721BE6A3538911790669@i2km07-ukbr.domain1.systemhost.net>
Thread-Topic: Graceful restart - inter-protocol dependencies
Thread-Index: AcXEW+1F1lvn6K7+Sf+nx1sLCgITFgAeyW6A
To: <David.Charlap@marconi.com>, <mpls@ietf.org>, <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 29 Sep 2005 09:43:26.0670 (UTC)
	FILETIME=[3DAEAEE0:01C5C4DA]
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [mpls] RE: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

David,

This is a very interesting/thoughtful mail.  When I read it I was
immediately struck by recent discussions some of us have been having on
the topic of unified functional modelling within SG15, ie the underlying
axiomatic truths that stem directly from Shannon/Turing wrt networking
and that show how the co-cs, co-ps and cl-ps networking modes all have a
common root.  However, whilst I don't want to get into that here I do
want to illustrate a key consequence of this work that is particularly
relevant to your observations.

In the co modes we have this rather important object called a trail.  A
trail is, in essence, a concatenated sequence of link-connections and
nodes (which are the smallest subnetwork connections).  However, the key
observation is that at the epoch we create the trail we remove all
further routing choices from the trail.  You can almost think of this as
effectively removing the trail from its parent network topology (there
is a resource accounting issue to deal with, but that is a different
point).....and I guess in IETF speak one would call this
'route-pinning'.

What this means is that it does not matter what happens to the routing
process after this epoch, once the trail is established there is no need
to move it.  And a key example of why this is important is the case of
augmenting the network topology by adding further nodes/links.  Because
the network topology has now changed then future routing decisions are
very likely to alter.  But in the co mode case this does not
matter....once a trail is created it remains faithful to its original
routing choice unless we consciously decide to move it (which may of
course be the result of failures or planned works).

Now contrast this with the cl mode case. If we augment a cl network by
adding new nodes/links then the routing process will update and traffic
will move in accordance with whatever is the optimal path.=20

Note a trail has other key properties, eg it allows one to completely
decouple a survivability semantic from the QoS semantics of client
traffic units.  This property is rather important when one offering a
network builder service to customers.

regards, Neil



> -----Original Message-----
> From: owner-ccamp@ops.ietf.org=20
> [mailto:owner-ccamp@ops.ietf.org] On Behalf Of David Charlap
> Sent: 28 September 2005 19:37
> To: IETF MPLS List; IETF CCAMP List
> Subject: Graceful restart - inter-protocol dependencies
>=20
>=20
> Is there any point to implementing RSVP-TE's graceful restart without=20
> also implementing graceful restart for routing protocols?
>=20
> On the one hand, RSVP doesn't require routing to recover=20
> LSPs.  It knows=20
> the next-hop interface, because of the preserved data-plane=20
> connection.=20
>   Whatever other information it may need, the switch can=20
> either preserve=20
> this information or recover it from a neighbor using the RecoveryPath=20
> object (draft-ietf-ccamp-rsvo-restart-ext-03).
>=20
> On the other hand, nodes more than one hop upstream of the=20
> failure will=20
> detect the loss of routing-connectivity to the failed node if IGP=20
> graceful restart is not also implemented.  They may reroute=20
> the LSP away=20
> from the failed node, or tear it down altogether, even though=20
> the data=20
> plane is still active and RSVP graceful restart is recovering the=20
> control-plane state.
>=20
> An originating node may consider the destination unreachable, as a=20
> result of losing the routes even though the data-plane for the LSP is=20
> still up (which can be confirmed via OAM.)
>=20
> A transit node, when processing an loose ERO-hop, may choose=20
> to reroute=20
> or fail the LSP if its local topology information says that=20
> the failed=20
> (and restarting) node is not available.  It might even choose=20
> to do this=20
> for an established LSP, as a result of Path refresh processing.
>=20
> My questions are:
>=20
> 1: Does this mean it's pointless to use RSVP graceful restart without
>     also using IGP graceful restart (for whatever IGP is active).
>=20
> 2: Is IGP graceful restart sufficient to prevent this problem?  For
>     instance, OSPF's restart procedure requires all preserved state to
>     be thrown away if a topology change is detected.
>=20
> 3: An originating node can use OAM to validate the data plane of an
>     LSP, and choose to ignore what routing tells it about the
>     destination's reachability.  But what about transit nodes?  As far
>     as I know, MPLS doesn't support segment-OAM, and it would be
>     prohibitive for every transit node to run its own OAM streams
>     to detect self-to-end connectivity.
>=20
> 4: Are there other solutions to this problem?
>=20
> One possible solution might be route-pinning, but RSVP doesn't have a=20
> built-in mechanism for this.  The usual workaround (signal the LSP,=20
> requesting route-recording, then turn the RRO into an ERO for=20
> subsequent=20
> refreshes) can work, but are there situations where even this=20
> would be=20
> insufficient to prevent a transit node from rerouting/tearing the=20
> connection in this particular situation (where RSVP is doing=20
> a graceful=20
> restart but the IGP is not)?
>=20
> -- David
>=20
>=20

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



From mpls-bounces@lists.ietf.org Thu Sep 29 10:35:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKzVC-0002X8-6S; Thu, 29 Sep 2005 10:35:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzVA-0002X3-IM
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 10:35:12 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com
	[169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15360
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 10:35:09 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
	[169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id
	j8TEYeUk021488; Thu, 29 Sep 2005 10:34:40 -0400 (EDT)
Received: from [169.144.136.107] (usvisdad104641.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA01186; 
	Thu, 29 Sep 2005 10:34:39 -0400 (EDT)
Message-ID: <433BFB7F.7050107@marconi.com>
Date: Thu, 29 Sep 2005 10:34:39 -0400
From: David Charlap <David.Charlap@marconi.com>
Organization: Marconi, Vienna VA
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'IETF MPLS List'" <mpls@ietf.org>,
	"'IETF CCAMP List'" <ccamp@ops.ietf.org>
References: <OF45604E5E.FAEDEDE4-ON4825708B.00100498@ctbri.com.cn>
In-Reply-To: <OF45604E5E.FAEDEDE4-ON4825708B.00100498@ctbri.com.cn>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] Re: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

But RSVP doesn't work this way.  It is a soft-state protocol.

If the route table changes such that the next-hop interface changes, 
RSVP is supposed to reroute the connection accordingly.

This probably won't happen if the next-hop is a strict-hop in an ERO, 
but it can easily happen if the next-hop is loose or if the LSP is 
signaled without an ERO (meaning routing is consulted to determine the 
next-hop to the egress node.)

If there is a paragraph in an RFC that says RSVP-TE should ignore all 
route-table changes once an LSP comes up, I missed it.

-- David

Jing Ruiquan wrote:
> I think only the  originating node should do the rerouting with RSVP-TE .At
> the same time, all the nodes will converge their IGP routing data base.
> 
> Rick
> 
> -----Original Message-----
> From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On Behalf
> Of David Charlap
> Sent: Thursday, September 29, 2005 2:37 AM
> To: IETF MPLS List; IETF CCAMP List
> Subject: Graceful restart - inter-protocol dependencies
> 
> Is there any point to implementing RSVP-TE's graceful restart without also
> implementing graceful restart for routing protocols?
> 
> On the one hand, RSVP doesn't require routing to recover LSPs.  It knows the
> next-hop interface, because of the preserved data-plane connection. 
>   Whatever other information it may need, the switch can either preserve
> this information or recover it from a neighbor using the RecoveryPath object
> (draft-ietf-ccamp-rsvo-restart-ext-03).
> 
> On the other hand, nodes more than one hop upstream of the failure will
> detect the loss of routing-connectivity to the failed node if IGP graceful
> restart is not also implemented.  They may reroute the LSP away from the
> failed node, or tear it down altogether, even though the data plane is still
> active and RSVP graceful restart is recovering the control-plane state.
> 
> An originating node may consider the destination unreachable, as a result of
> losing the routes even though the data-plane for the LSP is still up (which
> can be confirmed via OAM.)
> 
> A transit node, when processing an loose ERO-hop, may choose to reroute or
> fail the LSP if its local topology information says that the failed (and
> restarting) node is not available.  It might even choose to do this for an
> established LSP, as a result of Path refresh processing.
> 
> My questions are:
> 
> 1: Does this mean it's pointless to use RSVP graceful restart without
>     also using IGP graceful restart (for whatever IGP is active).
> 
> 2: Is IGP graceful restart sufficient to prevent this problem?  For
>     instance, OSPF's restart procedure requires all preserved state to
>     be thrown away if a topology change is detected.
> 
> 3: An originating node can use OAM to validate the data plane of an
>     LSP, and choose to ignore what routing tells it about the
>     destination's reachability.  But what about transit nodes?  As far
>     as I know, MPLS doesn't support segment-OAM, and it would be
>     prohibitive for every transit node to run its own OAM streams
>     to detect self-to-end connectivity.
> 
> 4: Are there other solutions to this problem?
> 
> One possible solution might be route-pinning, but RSVP doesn't have a
> built-in mechanism for this.  The usual workaround (signal the LSP,
> requesting route-recording, then turn the RRO into an ERO for subsequent
> refreshes) can work, but are there situations where even this would be
> insufficient to prevent a transit node from rerouting/tearing the connection
> in this particular situation (where RSVP is doing a graceful restart but the
> IGP is not)?
> 
> -- David


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



From mpls-bounces@lists.ietf.org Thu Sep 29 10:40:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKzaG-0004rH-8n; Thu, 29 Sep 2005 10:40:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzaE-0004r1-2C
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 10:40:26 -0400
Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15991
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 10:40:23 -0400 (EDT)
Received: by xproxy.gmail.com with SMTP id s18so60767wxc
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 07:39:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type;
	b=ES6i/eLkOWAqtKuthxmUrVVhMK8DZDAb6eILlYzuBt5b6JKePqlC6F0jzULZ/4boV7Spu2IjwTmecVMLdrYAUenhXlsuXdMU79m6w0/z/ATNHTEBAGhWjJDzdYDXox16SBShxAB5Fgnvb3kygvf0iBR9o/8PCYupSQ5f6tXD2p4=
Received: by 10.70.132.20 with SMTP id f20mr451874wxd;
	Thu, 29 Sep 2005 07:39:55 -0700 (PDT)
Received: by 10.70.19.1 with HTTP; Thu, 29 Sep 2005 07:39:54 -0700 (PDT)
Message-ID: <cd48822005092907393d7da0cc@mail.gmail.com>
Date: Thu, 29 Sep 2005 19:39:55 +0500
From: Fahad Dogar <fahad.dogar@gmail.com>
To: mpls@ietf.org
MIME-Version: 1.0
Cc: 
Subject: [mpls] Multi layer control plane models
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Fahad Dogar <fahad.dogar@gmail.com>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0002839311=="
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

--===============0002839311==
Content-Type: multipart/alternative; 
	boundary="----=_Part_2920_10849188.1128004795012"

------=_Part_2920_10849188.1128004795012
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,
 I am interested in knowing the difference between Peer and Overlay models
for multi-layer control planes. Also, is there any hybrid model as well? An=
y
reference to an introductory material on this would be highly appreciated.
 Thanks in advance,
Fahad

------=_Part_2920_10849188.1128004795012
Content-Type: text/html; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

<div>Hi,</div>
<div>&nbsp;</div>
<div>I am interested in knowing the difference between Peer and Overlay mod=
els for multi-layer control planes. Also, is there any hybrid&nbsp;model as=
 well? Any reference to an introductory material on this would be highly ap=
preciated.
</div>
<div>&nbsp;</div>
<div>Thanks in advance,</div>
<div>Fahad</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>

------=_Part_2920_10849188.1128004795012--


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

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

--===============0002839311==--




From mpls-bounces@lists.ietf.org Thu Sep 29 10:40:30 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKzaH-0004s1-Tq; Thu, 29 Sep 2005 10:40:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzaF-0004r6-Rh
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 10:40:27 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com
	[169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15993
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 10:40:25 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
	[169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id
	j8TEduUk021677; Thu, 29 Sep 2005 10:39:56 -0400 (EDT)
Received: from [169.144.136.107] (usvisdad104641.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA01878; 
	Thu, 29 Sep 2005 10:39:56 -0400 (EDT)
Message-ID: <433BFCBC.70002@marconi.com>
Date: Thu, 29 Sep 2005 10:39:56 -0400
From: David Charlap <David.Charlap@marconi.com>
Organization: Marconi, Vienna VA
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mpls@ietf.org, ccamp@ops.ietf.org
References: <0536FC9B908BEC4597EE721BE6A3538911790669@i2km07-ukbr.domain1.systemhost.net>
In-Reply-To: <0536FC9B908BEC4597EE721BE6A3538911790669@i2km07-ukbr.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] Re: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

You're absolutely right that this is how co networks should operate.  I 
would agree that there is little point to rerouting an LSP that has 
data-plane connectivity, even if routing says the path is invalid or 
suboptimal.

Unfortunately, I don't think current MPLS signaling protocols (RSVP-TE 
and LDP) work this way.  LDP is explicitly designed to dynamically 
change as routing changes.

RSVP-TE seems (to my best understanding) to also react to routing 
changes, except for special cases (like when signaled with an ERO 
consisting entirely of strict nodes whose addresses can be resolved from 
interface-neighbor information instead of from routing.)

-- David


neil.2.harrison@bt.com wrote:
> David,
> 
> This is a very interesting/thoughtful mail.  When I read it I was
> immediately struck by recent discussions some of us have been having on
> the topic of unified functional modelling within SG15, ie the underlying
> axiomatic truths that stem directly from Shannon/Turing wrt networking
> and that show how the co-cs, co-ps and cl-ps networking modes all have a
> common root.  However, whilst I don't want to get into that here I do
> want to illustrate a key consequence of this work that is particularly
> relevant to your observations.
> 
> In the co modes we have this rather important object called a trail.  A
> trail is, in essence, a concatenated sequence of link-connections and
> nodes (which are the smallest subnetwork connections).  However, the key
> observation is that at the epoch we create the trail we remove all
> further routing choices from the trail.  You can almost think of this as
> effectively removing the trail from its parent network topology (there
> is a resource accounting issue to deal with, but that is a different
> point).....and I guess in IETF speak one would call this
> 'route-pinning'.
> 
> What this means is that it does not matter what happens to the routing
> process after this epoch, once the trail is established there is no need
> to move it.  And a key example of why this is important is the case of
> augmenting the network topology by adding further nodes/links.  Because
> the network topology has now changed then future routing decisions are
> very likely to alter.  But in the co mode case this does not
> matter....once a trail is created it remains faithful to its original
> routing choice unless we consciously decide to move it (which may of
> course be the result of failures or planned works).
> 
> Now contrast this with the cl mode case. If we augment a cl network by
> adding new nodes/links then the routing process will update and traffic
> will move in accordance with whatever is the optimal path. 
> 
> Note a trail has other key properties, eg it allows one to completely
> decouple a survivability semantic from the QoS semantics of client
> traffic units.  This property is rather important when one offering a
> network builder service to customers.
> 
> regards, Neil
> 
> 
> 
> 
>>-----Original Message-----
>>From: owner-ccamp@ops.ietf.org 
>>[mailto:owner-ccamp@ops.ietf.org] On Behalf Of David Charlap
>>Sent: 28 September 2005 19:37
>>To: IETF MPLS List; IETF CCAMP List
>>Subject: Graceful restart - inter-protocol dependencies
>>
>>
>>Is there any point to implementing RSVP-TE's graceful restart without 
>>also implementing graceful restart for routing protocols?
>>
>>On the one hand, RSVP doesn't require routing to recover 
>>LSPs.  It knows 
>>the next-hop interface, because of the preserved data-plane 
>>connection. 
>>  Whatever other information it may need, the switch can 
>>either preserve 
>>this information or recover it from a neighbor using the RecoveryPath 
>>object (draft-ietf-ccamp-rsvo-restart-ext-03).
>>
>>On the other hand, nodes more than one hop upstream of the 
>>failure will 
>>detect the loss of routing-connectivity to the failed node if IGP 
>>graceful restart is not also implemented.  They may reroute 
>>the LSP away 
>>from the failed node, or tear it down altogether, even though 
>>the data 
>>plane is still active and RSVP graceful restart is recovering the 
>>control-plane state.
>>
>>An originating node may consider the destination unreachable, as a 
>>result of losing the routes even though the data-plane for the LSP is 
>>still up (which can be confirmed via OAM.)
>>
>>A transit node, when processing an loose ERO-hop, may choose 
>>to reroute 
>>or fail the LSP if its local topology information says that 
>>the failed 
>>(and restarting) node is not available.  It might even choose 
>>to do this 
>>for an established LSP, as a result of Path refresh processing.
>>
>>My questions are:
>>
>>1: Does this mean it's pointless to use RSVP graceful restart without
>>    also using IGP graceful restart (for whatever IGP is active).
>>
>>2: Is IGP graceful restart sufficient to prevent this problem?  For
>>    instance, OSPF's restart procedure requires all preserved state to
>>    be thrown away if a topology change is detected.
>>
>>3: An originating node can use OAM to validate the data plane of an
>>    LSP, and choose to ignore what routing tells it about the
>>    destination's reachability.  But what about transit nodes?  As far
>>    as I know, MPLS doesn't support segment-OAM, and it would be
>>    prohibitive for every transit node to run its own OAM streams
>>    to detect self-to-end connectivity.
>>
>>4: Are there other solutions to this problem?
>>
>>One possible solution might be route-pinning, but RSVP doesn't have a 
>>built-in mechanism for this.  The usual workaround (signal the LSP, 
>>requesting route-recording, then turn the RRO into an ERO for 
>>subsequent 
>>refreshes) can work, but are there situations where even this 
>>would be 
>>insufficient to prevent a transit node from rerouting/tearing the 
>>connection in this particular situation (where RSVP is doing 
>>a graceful 
>>restart but the IGP is not)?
>>
>>-- David
>>
>>


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



From mpls-bounces@lists.ietf.org Thu Sep 29 10:51:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKzkd-0008Dv-PR; Thu, 29 Sep 2005 10:51:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzkb-0008Dn-EA
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 10:51:09 -0400
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16872
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 10:51:06 -0400 (EDT)
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 29 Sep 2005 07:50:39 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,157,1125903600"; 
	d="scan'208"; a="11753940:sNHT22937740"
Received: from cisco.com (shaqzilla.cisco.com [161.44.70.33])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8TEoaQl011271; 
	Thu, 29 Sep 2005 10:50:36 -0400 (EDT)
Received: from shaqzilla.cisco.com (localhost.localdomain [127.0.0.1])
	by cisco.com (8.12.11/8.12.11) with ESMTP id j8TEoa5v018894;
	Thu, 29 Sep 2005 10:50:36 -0400
Received: (from ashokn@localhost)
	by shaqzilla.cisco.com (8.12.11/8.12.11/Submit) id j8TEoZpj018892;
	Thu, 29 Sep 2005 10:50:35 -0400
Date: Thu, 29 Sep 2005 10:50:35 -0400
From: Ashok Narayanan <ashokn@cisco.com>
To: David Charlap <David.Charlap@marconi.com>
Message-ID: <20050929145035.GP28771@cisco.com>
References: <OF45604E5E.FAEDEDE4-ON4825708B.00100498@ctbri.com.cn>
	<433BFB7F.7050107@marconi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <433BFB7F.7050107@marconi.com>
User-Agent: Mutt/1.4.2.1i
Cc: 'IETF CCAMP List' <ccamp@ops.ietf.org>, 'IETF MPLS List' <mpls@ietf.org>
Subject: [mpls] Re: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Strict EROs are used in the vast majority of MPLS/TE deployments. Even
Loose ERO hops tend to get expanded into strict EROs (e.g at ASBRs);
and extensions such as PCE are all designed to move path calculation
to a single point rather than doing it hop-by-hop. The problem with
hop-by-hop routing is that you can only have LSPs track the best IP
route, rather than the best "engineered" route through the network.

However, the problem you've described is an interesting one for
regular IPv4 RSVP (for QoS), though not necessarily for MPLS/TE.

-Ashok

On Thu, Sep 29, 2005 at 10:34:39AM -0400, David Charlap wrote:
> But RSVP doesn't work this way.  It is a soft-state protocol.
> 
> If the route table changes such that the next-hop interface changes, 
> RSVP is supposed to reroute the connection accordingly.
> 
> This probably won't happen if the next-hop is a strict-hop in an ERO, 
> but it can easily happen if the next-hop is loose or if the LSP is 
> signaled without an ERO (meaning routing is consulted to determine the 
> next-hop to the egress node.)
> 
> If there is a paragraph in an RFC that says RSVP-TE should ignore all 
> route-table changes once an LSP comes up, I missed it.
> 
> -- David
> 
> Jing Ruiquan wrote:
> >I think only the  originating node should do the rerouting with RSVP-TE .At
> >the same time, all the nodes will converge their IGP routing data base.
> >
> >Rick
> >
> >-----Original Message-----
> >From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On Behalf
> >Of David Charlap
> >Sent: Thursday, September 29, 2005 2:37 AM
> >To: IETF MPLS List; IETF CCAMP List
> >Subject: Graceful restart - inter-protocol dependencies
> >
> >Is there any point to implementing RSVP-TE's graceful restart without also
> >implementing graceful restart for routing protocols?
> >
> >On the one hand, RSVP doesn't require routing to recover LSPs.  It knows 
> >the
> >next-hop interface, because of the preserved data-plane connection. 
> >  Whatever other information it may need, the switch can either preserve
> >this information or recover it from a neighbor using the RecoveryPath 
> >object
> >(draft-ietf-ccamp-rsvo-restart-ext-03).
> >
> >On the other hand, nodes more than one hop upstream of the failure will
> >detect the loss of routing-connectivity to the failed node if IGP graceful
> >restart is not also implemented.  They may reroute the LSP away from the
> >failed node, or tear it down altogether, even though the data plane is 
> >still
> >active and RSVP graceful restart is recovering the control-plane state.
> >
> >An originating node may consider the destination unreachable, as a result 
> >of
> >losing the routes even though the data-plane for the LSP is still up (which
> >can be confirmed via OAM.)
> >
> >A transit node, when processing an loose ERO-hop, may choose to reroute or
> >fail the LSP if its local topology information says that the failed (and
> >restarting) node is not available.  It might even choose to do this for an
> >established LSP, as a result of Path refresh processing.
> >
> >My questions are:
> >
> >1: Does this mean it's pointless to use RSVP graceful restart without
> >    also using IGP graceful restart (for whatever IGP is active).
> >
> >2: Is IGP graceful restart sufficient to prevent this problem?  For
> >    instance, OSPF's restart procedure requires all preserved state to
> >    be thrown away if a topology change is detected.
> >
> >3: An originating node can use OAM to validate the data plane of an
> >    LSP, and choose to ignore what routing tells it about the
> >    destination's reachability.  But what about transit nodes?  As far
> >    as I know, MPLS doesn't support segment-OAM, and it would be
> >    prohibitive for every transit node to run its own OAM streams
> >    to detect self-to-end connectivity.
> >
> >4: Are there other solutions to this problem?
> >
> >One possible solution might be route-pinning, but RSVP doesn't have a
> >built-in mechanism for this.  The usual workaround (signal the LSP,
> >requesting route-recording, then turn the RRO into an ERO for subsequent
> >refreshes) can work, but are there situations where even this would be
> >insufficient to prevent a transit node from rerouting/tearing the 
> >connection
> >in this particular situation (where RSVP is doing a graceful restart but 
> >the
> >IGP is not)?
> >
> >-- David

-- 



--- Asok the Intern ----------------------------------------
Ashok Narayanan
IOS Network Protocols, Cisco Systems
1414 Mass Ave, Boxborough MA 01719
Ph: 978-936-1608.  Fax: 978-936-2218 (Attn: Ashok Narayanan)

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



From mpls-bounces@lists.ietf.org Thu Sep 29 11:37:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EL0Td-0003YB-14; Thu, 29 Sep 2005 11:37:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EL0Tb-0003Y5-NS
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 11:37:39 -0400
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19049
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 11:37:36 -0400 (EDT)
From: neil.2.harrison@bt.com
Received: from i2km99-ukbr.domain1.systemhost.net ([193.113.197.31]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 29 Sep 2005 16:37:04 +0100
Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by
	i2km99-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(5.0.2195.6713); Thu, 29 Sep 2005 16:37:04 +0100
x-mimeole: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 29 Sep 2005 16:37:04 +0100
Message-ID: <0536FC9B908BEC4597EE721BE6A35389118004E7@i2km07-ukbr.domain1.systemhost.net>
Thread-Topic: Graceful restart - inter-protocol dependencies
Thread-Index: AcXFA/+QPkt5glu/Qzm6K/i6F7bBbgAAQZew
To: <David.Charlap@marconi.com>, <mpls@ietf.org>, <ccamp@ops.ietf.org>
X-OriginalArrivalTime: 29 Sep 2005 15:37:04.0658 (UTC)
	FILETIME=[A496B720:01C5C50B]
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [mpls] RE: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Thanks David....it's not simply how they *should* work its how they
*must* work if one wants to be able to offer network services to
customers that have deterministic behaviour, ie one has precise (and it
also should be simple) control over traffic/fault/performance management
facets.

A full service operator like BT needs all 3 networking modes working in
concert...and they are for sure different.  Understanding *why* they are
different at fundamental level has taken us a while to properly figure
out.  However, the stuff we knew was intuitively right is now getting
placed on a far stronger foundation of underlying 'truths' because of
the unified modelling work I mentioned (this goes right back to Shannon
and Turing stuff...indeed a network is precisely the union of
Information Theory and a computing machine).

The GMPLS co-cs stuff is largely self-protecting of abuse.....this is
down to the nature of the constraints that define this mode (esp the
labelling).  Same can be said for the cl-ps mode.  The major risks arise
with the co-ps mode....and one can make life very complex here if one is
not careful.....I'll resist the strong temptation to flesh this out wrt
comments on MPLS and the PW stuff.=20

However, we do need a correctly specified co-ps mode networking
capability because as we sun-set many of our legacy co-cs and co-ps
technologies there is a major gap opening for a lower granularity (than
SDH VC4) network builder capability....and we have many customers who
demand such a network service.

regards, Neil

> -----Original Message-----
> From: owner-ccamp@ops.ietf.org=20
> [mailto:owner-ccamp@ops.ietf.org] On Behalf Of David Charlap
> Sent: 29 September 2005 15:40
> To: mpls@lists.ietf.org; ccamp@ops.ietf.org
> Subject: Re: Graceful restart - inter-protocol dependencies
>=20
>=20
> You're absolutely right that this is how co networks should=20
> operate.  I=20
> would agree that there is little point to rerouting an LSP that has=20
> data-plane connectivity, even if routing says the path is invalid or=20
> suboptimal.
>=20
> Unfortunately, I don't think current MPLS signaling protocols=20
> (RSVP-TE=20
> and LDP) work this way.  LDP is explicitly designed to dynamically=20
> change as routing changes.
>=20
> RSVP-TE seems (to my best understanding) to also react to routing=20
> changes, except for special cases (like when signaled with an ERO=20
> consisting entirely of strict nodes whose addresses can be=20
> resolved from=20
> interface-neighbor information instead of from routing.)
>=20
> -- David
>=20
>=20
> neil.2.harrison@bt.com wrote:
> > David,
> >=20
> > This is a very interesting/thoughtful mail.  When I read it I was=20
> > immediately struck by recent discussions some of us have=20
> been having=20
> > on the topic of unified functional modelling within SG15, ie the=20
> > underlying axiomatic truths that stem directly from=20
> Shannon/Turing wrt=20
> > networking and that show how the co-cs, co-ps and cl-ps networking=20
> > modes all have a common root.  However, whilst I don't want to get=20
> > into that here I do want to illustrate a key consequence of=20
> this work=20
> > that is particularly relevant to your observations.
> >=20
> > In the co modes we have this rather important object called=20
> a trail. =20
> > A trail is, in essence, a concatenated sequence of link-connections=20
> > and nodes (which are the smallest subnetwork connections). =20
> However,=20
> > the key observation is that at the epoch we create the=20
> trail we remove=20
> > all further routing choices from the trail.  You can almost=20
> think of=20
> > this as effectively removing the trail from its parent network=20
> > topology (there is a resource accounting issue to deal=20
> with, but that=20
> > is a different point).....and I guess in IETF speak one would call=20
> > this 'route-pinning'.
> >=20
> > What this means is that it does not matter what happens to=20
> the routing=20
> > process after this epoch, once the trail is established there is no=20
> > need to move it.  And a key example of why this is important is the=20
> > case of augmenting the network topology by adding further=20
> nodes/links. =20
> > Because the network topology has now changed then future routing=20
> > decisions are very likely to alter.  But in the co mode=20
> case this does=20
> > not matter....once a trail is created it remains faithful to its=20
> > original routing choice unless we consciously decide to=20
> move it (which=20
> > may of course be the result of failures or planned works).
> >=20
> > Now contrast this with the cl mode case. If we augment a cl=20
> network by=20
> > adding new nodes/links then the routing process will update and=20
> > traffic will move in accordance with whatever is the optimal path.
> >=20
> > Note a trail has other key properties, eg it allows one to=20
> completely=20
> > decouple a survivability semantic from the QoS semantics of client=20
> > traffic units.  This property is rather important when one=20
> offering a=20
> > network builder service to customers.
> >=20
> > regards, Neil
> >=20
> >=20
> >=20
> >=20
> >>-----Original Message-----
> >>From: owner-ccamp@ops.ietf.org
> >>[mailto:owner-ccamp@ops.ietf.org] On Behalf Of David Charlap
> >>Sent: 28 September 2005 19:37
> >>To: IETF MPLS List; IETF CCAMP List
> >>Subject: Graceful restart - inter-protocol dependencies
> >>
> >>
> >>Is there any point to implementing RSVP-TE's graceful=20
> restart without
> >>also implementing graceful restart for routing protocols?
> >>
> >>On the one hand, RSVP doesn't require routing to recover
> >>LSPs.  It knows=20
> >>the next-hop interface, because of the preserved data-plane=20
> >>connection.=20
> >>  Whatever other information it may need, the switch can=20
> >>either preserve=20
> >>this information or recover it from a neighbor using the=20
> RecoveryPath=20
> >>object (draft-ietf-ccamp-rsvo-restart-ext-03).
> >>
> >>On the other hand, nodes more than one hop upstream of the
> >>failure will=20
> >>detect the loss of routing-connectivity to the failed node if IGP=20
> >>graceful restart is not also implemented.  They may reroute=20
> >>the LSP away=20
> >>from the failed node, or tear it down altogether, even though=20
> >>the data=20
> >>plane is still active and RSVP graceful restart is recovering the=20
> >>control-plane state.
> >>
> >>An originating node may consider the destination unreachable, as a
> >>result of losing the routes even though the data-plane for=20
> the LSP is=20
> >>still up (which can be confirmed via OAM.)
> >>
> >>A transit node, when processing an loose ERO-hop, may choose
> >>to reroute=20
> >>or fail the LSP if its local topology information says that=20
> >>the failed=20
> >>(and restarting) node is not available.  It might even choose=20
> >>to do this=20
> >>for an established LSP, as a result of Path refresh processing.
> >>
> >>My questions are:
> >>
> >>1: Does this mean it's pointless to use RSVP graceful=20
> restart without
> >>    also using IGP graceful restart (for whatever IGP is active).
> >>
> >>2: Is IGP graceful restart sufficient to prevent this problem?  For
> >>    instance, OSPF's restart procedure requires all=20
> preserved state to
> >>    be thrown away if a topology change is detected.
> >>
> >>3: An originating node can use OAM to validate the data plane of an
> >>    LSP, and choose to ignore what routing tells it about the
> >>    destination's reachability.  But what about transit=20
> nodes?  As far
> >>    as I know, MPLS doesn't support segment-OAM, and it would be
> >>    prohibitive for every transit node to run its own OAM streams
> >>    to detect self-to-end connectivity.
> >>
> >>4: Are there other solutions to this problem?
> >>
> >>One possible solution might be route-pinning, but RSVP=20
> doesn't have a
> >>built-in mechanism for this.  The usual workaround (signal the LSP,=20
> >>requesting route-recording, then turn the RRO into an ERO for=20
> >>subsequent=20
> >>refreshes) can work, but are there situations where even this=20
> >>would be=20
> >>insufficient to prevent a transit node from rerouting/tearing the=20
> >>connection in this particular situation (where RSVP is doing=20
> >>a graceful=20
> >>restart but the IGP is not)?
> >>
> >>-- David
> >>
> >>
>=20
>=20
>=20

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



From mpls-bounces@lists.ietf.org Thu Sep 29 14:01:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EL2ii-00009G-Mf; Thu, 29 Sep 2005 14:01:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EL2ig-00007J-FJ
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 14:01:22 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com
	[169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25411
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 14:01:19 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
	[169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id
	j8TI0oUk026885; Thu, 29 Sep 2005 14:00:50 -0400 (EDT)
Received: from [169.144.136.107] (usvisdad104641.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA01177; 
	Thu, 29 Sep 2005 14:00:50 -0400 (EDT)
Message-ID: <433C2BD1.4010104@marconi.com>
Date: Thu, 29 Sep 2005 14:00:49 -0400
From: David Charlap <David.Charlap@marconi.com>
Organization: Marconi, Vienna VA
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF MPLS List <mpls@ietf.org>, IETF CCAMP List <ccamp@ops.ietf.org>
References: <OF45604E5E.FAEDEDE4-ON4825708B.00100498@ctbri.com.cn>	
	<433BFB7F.7050107@marconi.com>
	<6280db52050929104647919cbe@mail.gmail.com>
In-Reply-To: <6280db52050929104647919cbe@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] Re: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

When processing a loose hop, or even a strict hop with an address that 
is not an interface-neighbor address, RSVP relies on the route table to 
determine the next-hop interface (and possibly also the next-hop address.)

How is it right to ignore route changes after this?  If the route table 
changes such that the selected next-hop interface is no longer the best 
(or is no longer valid), should RSVP ignore this?  It seems to me like 
this could end up blackholing traffic in a way that will not be 
detectable without OAM.

The last I heard, network operators were not required to run OAM on 
every LSP.  Has this changed?

-- David


Alia Atlas wrote:
> David,
> 
> In ref to RSVP-TE, a part of the question is who notices the routing 
> change and does
> the reroute.  In general, the idea of make-before-break and control by 
> the ingress apply.
> 
> For a midpoint, a change to an LSP would be triggered by either the RSVP 
> PATH
> message changing or by the selected next-hop interface no longer being 
> available. 
> Theoretically, a midpoint LSR could register for route changes to the 
> specified next-hop,
> but to what purpose?? Once the midpoint LSR has determined the next-hop 
> interface, I'd
> expect that to be treated as a strict hop, inside the LSR at least.
> 
> Alia
> 
> 
> On 9/29/05, *David Charlap* <David.Charlap@marconi.com 
> <mailto:David.Charlap@marconi.com>> wrote:
> 
>     But RSVP doesn't work this way.  It is a soft-state protocol.
> 
>     If the route table changes such that the next-hop interface changes,
>     RSVP is supposed to reroute the connection accordingly.
> 
>     This probably won't happen if the next-hop is a strict-hop in an ERO,
>     but it can easily happen if the next-hop is loose or if the LSP is
>     signaled without an ERO (meaning routing is consulted to determine the
>     next-hop to the egress node.)
> 
>     If there is a paragraph in an RFC that says RSVP-TE should ignore all
>     route-table changes once an LSP comes up, I missed it.
> 
>     -- David
> 
>     Jing Ruiquan wrote:
>      > I think only the  originating node should do the rerouting with
>     RSVP-TE .At
>      > the same time, all the nodes will converge their IGP routing data
>     base.
>      >
>      > Rick
>      >
>      > -----Original Message-----
>      > From: owner-ccamp@ops.ietf.org <mailto:owner-ccamp@ops.ietf.org>
>     [mailto:owner-ccamp@ops.ietf.org <mailto:owner-ccamp@ops.ietf.org>]
>     On Behalf
>      > Of David Charlap
>      > Sent: Thursday, September 29, 2005 2:37 AM
>      > To: IETF MPLS List; IETF CCAMP List
>      > Subject: Graceful restart - inter-protocol dependencies
>      >
>      > Is there any point to implementing RSVP-TE's graceful restart
>     without also
>      > implementing graceful restart for routing protocols?
>      >
>      > On the one hand, RSVP doesn't require routing to recover
>     LSPs.  It knows the
>      > next-hop interface, because of the preserved data-plane connection.
>      >   Whatever other information it may need, the switch can either
>     preserve
>      > this information or recover it from a neighbor using the
>     RecoveryPath object
>      > (draft-ietf-ccamp-rsvo-restart-ext-03).
>      >
>      > On the other hand, nodes more than one hop upstream of the
>     failure will
>      > detect the loss of routing-connectivity to the failed node if IGP
>     graceful
>      > restart is not also implemented.  They may reroute the LSP away
>     from the
>      > failed node, or tear it down altogether, even though the data
>     plane is still
>      > active and RSVP graceful restart is recovering the control-plane
>     state.
>      >
>      > An originating node may consider the destination unreachable, as
>     a result of
>      > losing the routes even though the data-plane for the LSP is still
>     up (which
>      > can be confirmed via OAM.)
>      >
>      > A transit node, when processing an loose ERO-hop, may choose to
>     reroute or
>      > fail the LSP if its local topology information says that the
>     failed (and
>      > restarting) node is not available.  It might even choose to do
>     this for an
>      > established LSP, as a result of Path refresh processing.
>      >
>      > My questions are:
>      >
>      > 1: Does this mean it's pointless to use RSVP graceful restart
>     without
>      >     also using IGP graceful restart (for whatever IGP is active).
>      >
>      > 2: Is IGP graceful restart sufficient to prevent this problem?  For
>      >     instance, OSPF's restart procedure requires all preserved
>     state to
>      >     be thrown away if a topology change is detected.
>      >
>      > 3: An originating node can use OAM to validate the data plane of an
>      >     LSP, and choose to ignore what routing tells it about the
>      >     destination's reachability.  But what about transit
>     nodes?  As far
>      >     as I know, MPLS doesn't support segment-OAM, and it would be
>      >     prohibitive for every transit node to run its own OAM streams
>      >     to detect self-to-end connectivity.
>      >
>      > 4: Are there other solutions to this problem?
>      >
>      > One possible solution might be route-pinning, but RSVP doesn't have a
>      > built-in mechanism for this.  The usual workaround (signal the LSP,
>      > requesting route-recording, then turn the RRO into an ERO for
>     subsequent
>      > refreshes) can work, but are there situations where even this
>     would be
>      > insufficient to prevent a transit node from rerouting/tearing the
>     connection
>      > in this particular situation (where RSVP is doing a graceful
>     restart but the
>      > IGP is not)?
>      >
>      > -- David
> 
> 
> 


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



From mpls-bounces@lists.ietf.org Thu Sep 29 14:03:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EL2kX-0000sv-OM; Thu, 29 Sep 2005 14:03:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EL2kW-0000sl-Bu
	for mpls@megatron.ietf.org; Thu, 29 Sep 2005 14:03:16 -0400
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25520
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 14:03:14 -0400 (EDT)
Received: by wproxy.gmail.com with SMTP id 36so109685wra
	for <mpls@lists.ietf.org>; Thu, 29 Sep 2005 11:02:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=HjQP2MnP/SN71Sd9s3wAtszYaE4qPzq/TEd3TGOlz2RQI3JuYPT3RcEG2QcCPRuT3gqMZug8cxbSQhoM4lpalXJqY1RssaIwobKvnyWLHI/qfpkNsRc8N7qbRWzUDZDlpHkoVQGOX+uTSXn1qM3S5go8nt1yoIMGPvHs+4Tw6QY=
Received: by 10.54.150.18 with SMTP id x18mr560905wrd;
	Thu, 29 Sep 2005 11:02:45 -0700 (PDT)
Received: by 10.54.148.1 with HTTP; Thu, 29 Sep 2005 11:02:45 -0700 (PDT)
Message-ID: <6280db5205092911021bfba866@mail.gmail.com>
Date: Thu, 29 Sep 2005 11:02:45 -0700
From: Alia Atlas <akatlas@gmail.com>
To: David Charlap <David.Charlap@marconi.com>
In-Reply-To: <433BFB7F.7050107@marconi.com>
MIME-Version: 1.0
References: <OF45604E5E.FAEDEDE4-ON4825708B.00100498@ctbri.com.cn>
	<433BFB7F.7050107@marconi.com>
Cc: IETF CCAMP List <ccamp@ops.ietf.org>, IETF MPLS List <mpls@ietf.org>
Subject: [mpls] Re: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alia Atlas <akatlas@gmail.com>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2086337029=="
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

--===============2086337029==
Content-Type: multipart/alternative; 
	boundary="----=_Part_2893_19294142.1128016965563"

------=_Part_2893_19294142.1128016965563
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

David,

In ref to RSVP-TE, a part of the question is who notices the routing change
and does
the reroute. In general, the idea of make-before-break and control by the
ingress apply.

For a midpoint, a change to an LSP would be triggered by either the RSVP
PATH
message changing or by the selected next-hop interface no longer being
available.
Theoretically, a midpoint LSR could register for route changes to the
specified next-hop,
but to what purpose?? Once the midpoint LSR has determined the next-hop
interface, I'd
expect that to be treated as a strict hop, inside the LSR at least.

Alia

On 9/29/05, David Charlap <David.Charlap@marconi.com> wrote:
>
> But RSVP doesn't work this way. It is a soft-state protocol.
>
> If the route table changes such that the next-hop interface changes,
> RSVP is supposed to reroute the connection accordingly.
>
> This probably won't happen if the next-hop is a strict-hop in an ERO,
> but it can easily happen if the next-hop is loose or if the LSP is
> signaled without an ERO (meaning routing is consulted to determine the
> next-hop to the egress node.)
>
> If there is a paragraph in an RFC that says RSVP-TE should ignore all
> route-table changes once an LSP comes up, I missed it.
>
> -- David
>
> Jing Ruiquan wrote:
> > I think only the originating node should do the rerouting with RSVP-TE
> .At
> > the same time, all the nodes will converge their IGP routing data base.
> >
> > Rick
> >
> > -----Original Message-----
> > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On
> Behalf
> > Of David Charlap
> > Sent: Thursday, September 29, 2005 2:37 AM
> > To: IETF MPLS List; IETF CCAMP List
> > Subject: Graceful restart - inter-protocol dependencies
> >
> > Is there any point to implementing RSVP-TE's graceful restart without
> also
> > implementing graceful restart for routing protocols?
> >
> > On the one hand, RSVP doesn't require routing to recover LSPs. It knows
> the
> > next-hop interface, because of the preserved data-plane connection.
> > Whatever other information it may need, the switch can either preserve
> > this information or recover it from a neighbor using the RecoveryPath
> object
> > (draft-ietf-ccamp-rsvo-restart-ext-03).
> >
> > On the other hand, nodes more than one hop upstream of the failure will
> > detect the loss of routing-connectivity to the failed node if IGP
> graceful
> > restart is not also implemented. They may reroute the LSP away from the
> > failed node, or tear it down altogether, even though the data plane is
> still
> > active and RSVP graceful restart is recovering the control-plane state.
> >
> > An originating node may consider the destination unreachable, as a
> result of
> > losing the routes even though the data-plane for the LSP is still up
> (which
> > can be confirmed via OAM.)
> >
> > A transit node, when processing an loose ERO-hop, may choose to reroute
> or
> > fail the LSP if its local topology information says that the failed (an=
d
> > restarting) node is not available. It might even choose to do this for
> an
> > established LSP, as a result of Path refresh processing.
> >
> > My questions are:
> >
> > 1: Does this mean it's pointless to use RSVP graceful restart without
> > also using IGP graceful restart (for whatever IGP is active).
> >
> > 2: Is IGP graceful restart sufficient to prevent this problem? For
> > instance, OSPF's restart procedure requires all preserved state to
> > be thrown away if a topology change is detected.
> >
> > 3: An originating node can use OAM to validate the data plane of an
> > LSP, and choose to ignore what routing tells it about the
> > destination's reachability. But what about transit nodes? As far
> > as I know, MPLS doesn't support segment-OAM, and it would be
> > prohibitive for every transit node to run its own OAM streams
> > to detect self-to-end connectivity.
> >
> > 4: Are there other solutions to this problem?
> >
> > One possible solution might be route-pinning, but RSVP doesn't have a
> > built-in mechanism for this. The usual workaround (signal the LSP,
> > requesting route-recording, then turn the RRO into an ERO for subsequen=
t
> > refreshes) can work, but are there situations where even this would be
> > insufficient to prevent a transit node from rerouting/tearing the
> connection
> > in this particular situation (where RSVP is doing a graceful restart bu=
t
> the
> > IGP is not)?
> >
> > -- David
>
>
>

------=_Part_2893_19294142.1128016965563
Content-Type: text/html; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

David,<br>

<br>

In ref to RSVP-TE, a part of the question is who notices the routing change=
 and does<br>

the reroute.&nbsp; In general, the idea of make-before-break and control by=
 the ingress apply.<br>

<br>

For a midpoint, a change to an LSP would be triggered by either the RSVP PA=
TH <br>

message changing or by the selected next-hop interface no longer being avai=
lable.&nbsp; <br>

Theoretically, a midpoint LSR could register for route changes to the speci=
fied next-hop, <br>

but to what purpose?? Once the midpoint LSR has determined the next-hop int=
erface, I'd <br>

expect that to be treated as a strict hop, inside the LSR at least.<br>
<span class=3D"sg">
<br>
Alia</span><br><br><div><span class=3D"gmail_quote">On 9/29/05, <b class=3D=
"gmail_sendername">David Charlap</b> &lt;<a href=3D"mailto:David.Charlap@ma=
rconi.com">David.Charlap@marconi.com</a>&gt; wrote:</span><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
But RSVP doesn't work this way.&nbsp;&nbsp;It is a soft-state protocol.<br>=
<br>If the route table changes such that the next-hop interface changes,<br=
>RSVP is supposed to reroute the connection accordingly.<br><br>This probab=
ly won't happen if the next-hop is a strict-hop in an ERO,
<br>but it can easily happen if the next-hop is loose or if the LSP is<br>s=
ignaled without an ERO (meaning routing is consulted to determine the<br>ne=
xt-hop to the egress node.)<br><br>If there is a paragraph in an RFC that s=
ays RSVP-TE should ignore all
<br>route-table changes once an LSP comes up, I missed it.<br><br>-- David<=
br><br>Jing Ruiquan wrote:<br>&gt; I think only the&nbsp;&nbsp;originating =
node should do the rerouting with RSVP-TE .At<br>&gt; the same time, all th=
e nodes will converge their IGP routing data base.
<br>&gt;<br>&gt; Rick<br>&gt;<br>&gt; -----Original Message-----<br>&gt; Fr=
om: <a href=3D"mailto:owner-ccamp@ops.ietf.org">owner-ccamp@ops.ietf.org</a=
> [mailto:<a href=3D"mailto:owner-ccamp@ops.ietf.org">owner-ccamp@ops.ietf.=
org
</a>] On Behalf<br>&gt; Of David Charlap<br>&gt; Sent: Thursday, September =
29, 2005 2:37 AM<br>&gt; To: IETF MPLS List; IETF CCAMP List<br>&gt; Subjec=
t: Graceful restart - inter-protocol dependencies<br>&gt;<br>&gt; Is there =
any point to implementing RSVP-TE's graceful restart without also
<br>&gt; implementing graceful restart for routing protocols?<br>&gt;<br>&g=
t; On the one hand, RSVP doesn't require routing to recover LSPs.&nbsp;&nbs=
p;It knows the<br>&gt; next-hop interface, because of the preserved data-pl=
ane connection.
<br>&gt;&nbsp;&nbsp; Whatever other information it may need, the switch can=
 either preserve<br>&gt; this information or recover it from a neighbor usi=
ng the RecoveryPath object<br>&gt; (draft-ietf-ccamp-rsvo-restart-ext-03).<=
br>&gt;
<br>&gt; On the other hand, nodes more than one hop upstream of the failure=
 will<br>&gt; detect the loss of routing-connectivity to the failed node if=
 IGP graceful<br>&gt; restart is not also implemented.&nbsp;&nbsp;They may =
reroute the LSP away from the
<br>&gt; failed node, or tear it down altogether, even though the data plan=
e is still<br>&gt; active and RSVP graceful restart is recovering the contr=
ol-plane state.<br>&gt;<br>&gt; An originating node may consider the destin=
ation unreachable, as a result of
<br>&gt; losing the routes even though the data-plane for the LSP is still =
up (which<br>&gt; can be confirmed via OAM.)<br>&gt;<br>&gt; A transit node=
, when processing an loose ERO-hop, may choose to reroute or<br>&gt; fail t=
he LSP if its local topology information says that the failed (and
<br>&gt; restarting) node is not available.&nbsp;&nbsp;It might even choose=
 to do this for an<br>&gt; established LSP, as a result of Path refresh pro=
cessing.<br>&gt;<br>&gt; My questions are:<br>&gt;<br>&gt; 1: Does this mea=
n it's pointless to use RSVP graceful restart without
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; also using IGP graceful restart (for whate=
ver IGP is active).<br>&gt;<br>&gt; 2: Is IGP graceful restart sufficient t=
o prevent this problem?&nbsp;&nbsp;For<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; inst=
ance, OSPF's restart procedure requires all preserved state to
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; be thrown away if a topology change is det=
ected.<br>&gt;<br>&gt; 3: An originating node can use OAM to validate the d=
ata plane of an<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; LSP, and choose to ignore w=
hat routing tells it about the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; destination'=
s reachability.&nbsp;&nbsp;But what about transit nodes?&nbsp;&nbsp;As far
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; as I know, MPLS doesn't support segment-OA=
M, and it would be<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; prohibitive for every tr=
ansit node to run its own OAM streams<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; to de=
tect self-to-end connectivity.<br>&gt;<br>&gt; 4: Are there other solutions=
 to this problem?
<br>&gt;<br>&gt; One possible solution might be route-pinning, but RSVP doe=
sn't have a<br>&gt; built-in mechanism for this.&nbsp;&nbsp;The usual worka=
round (signal the LSP,<br>&gt; requesting route-recording, then turn the RR=
O into an ERO for subsequent
<br>&gt; refreshes) can work, but are there situations where even this woul=
d be<br>&gt; insufficient to prevent a transit node from rerouting/tearing =
the connection<br>&gt; in this particular situation (where RSVP is doing a =
graceful restart but the
<br>&gt; IGP is not)?<br>&gt;<br>&gt; -- David<br><br><br></blockquote></di=
v><br>

------=_Part_2893_19294142.1128016965563--


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

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

--===============2086337029==--




From mpls-bounces@lists.ietf.org Fri Sep 30 10:03:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELLU5-0005Zi-5R; Fri, 30 Sep 2005 10:03:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELLU2-0005ZO-LK
	for mpls@megatron.ietf.org; Fri, 30 Sep 2005 10:03:30 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com
	[169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12097
	for <mpls@lists.ietf.org>; Fri, 30 Sep 2005 10:03:28 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
	[169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id
	j8UE2wUk017045; Fri, 30 Sep 2005 10:02:58 -0400 (EDT)
Received: from [169.144.136.107] (usvisdad104641.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA12647; 
	Fri, 30 Sep 2005 10:02:58 -0400 (EDT)
Message-ID: <433D4591.4080308@marconi.com>
Date: Fri, 30 Sep 2005 10:02:57 -0400
From: David Charlap <David.Charlap@marconi.com>
Organization: Marconi, Vienna VA
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'IETF MPLS List'" <mpls@ietf.org>,
	"'IETF CCAMP List'" <ccamp@ops.ietf.org>
References: <OF603BDC4C.FF916B57-ON4825708C.000B1829@ctbri.com.cn>
In-Reply-To: <OF603BDC4C.FF916B57-ON4825708C.000B1829@ctbri.com.cn>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [mpls] Re: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Then we are talking about different protocols.  I'm specifically 
referring to RSVP-TE, as defined by RFC 3209.

I am aware that RSVP-TE's signaling mechanism (even just a PathErr 
message) will probably reach the ingress node long before routing can 
reconverge.  But that's not the question.

The question is, if the node failure is due to a restart, and it has 
implemented RSVP-TE restart (yes, I'm aware that this is a GMPLS 
extnsion), but has not implemented graceful restart for any routing 
protocols, then the originating node won't receive any RSVP-level 
information about the restarting node.  But the IGP will.

We want to prevent the reroute that would normally happen as a result of 
the route change.  Originating nodes can test the LSP using OAM, if 
there is no other choice, but transit nodes don't have that option.

Ultimately, this comes down to my original questions:

	Does it make any sense to use RSVP graceful restart in a
	network where graceful restart is not being used for any
	routing protocols?

	If the answer to the previous question is yes, what can be
	done (if anything) to prevent originating and transit nodes
	from rerouting LSPs as a result of the route-table change?

-- David

Jing Ruiquan wrote:
> Hi David,
> 
> We should specify which version of RSVP we are talking. What I have said is
> about GMPLS RSVP-TE as used in ASON. 
> 
> When there is a failed link within the network, the ingress node will know
> the failure by transport plan OAM mechanism such as SDH path layer AIS, or
> by RSVP-TE Notify message. And usually these mechanisms are faster than
> routing protocol convergence speed. After the ingress node knows which link
> or route has failed, it will do the rerouting while excluding the failed
> link or route. 
> 
> Hope I say it clearly :-)
> 
> Rick 
> 
> -----Original Message-----
> From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On Behalf
> Of David Charlap
> Sent: Thursday, September 29, 2005 10:35 PM
> To: 'IETF MPLS List'; 'IETF CCAMP List'
> Subject: Re: Graceful restart - inter-protocol dependencies
> 
> But RSVP doesn't work this way.  It is a soft-state protocol.
> 
> If the route table changes such that the next-hop interface changes, RSVP is
> supposed to reroute the connection accordingly.
> 
> This probably won't happen if the next-hop is a strict-hop in an ERO, but it
> can easily happen if the next-hop is loose or if the LSP is signaled without
> an ERO (meaning routing is consulted to determine the next-hop to the egress
> node.)
> 
> If there is a paragraph in an RFC that says RSVP-TE should ignore all
> route-table changes once an LSP comes up, I missed it.
> 
> -- David
> 
> Jing Ruiquan wrote:
> 
>>I think only the  originating node should do the rerouting with 
>>RSVP-TE .At the same time, all the nodes will converge their IGP routing
> 
> data base.
> 
>>Rick
>>
>>-----Original Message-----
>>From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On 
>>Behalf Of David Charlap
>>Sent: Thursday, September 29, 2005 2:37 AM
>>To: IETF MPLS List; IETF CCAMP List
>>Subject: Graceful restart - inter-protocol dependencies
>>
>>Is there any point to implementing RSVP-TE's graceful restart without 
>>also implementing graceful restart for routing protocols?
>>
>>On the one hand, RSVP doesn't require routing to recover LSPs.  It 
>>knows the next-hop interface, because of the preserved data-plane
> 
> connection.
> 
>>  Whatever other information it may need, the switch can either 
>>preserve this information or recover it from a neighbor using the 
>>RecoveryPath object (draft-ietf-ccamp-rsvo-restart-ext-03).
>>
>>On the other hand, nodes more than one hop upstream of the failure 
>>will detect the loss of routing-connectivity to the failed node if IGP 
>>graceful restart is not also implemented.  They may reroute the LSP 
>>away from the failed node, or tear it down altogether, even though the 
>>data plane is still active and RSVP graceful restart is recovering the
> 
> control-plane state.
> 
>>An originating node may consider the destination unreachable, as a 
>>result of losing the routes even though the data-plane for the LSP is 
>>still up (which can be confirmed via OAM.)
>>
>>A transit node, when processing an loose ERO-hop, may choose to 
>>reroute or fail the LSP if its local topology information says that 
>>the failed (and
>>restarting) node is not available.  It might even choose to do this 
>>for an established LSP, as a result of Path refresh processing.
>>
>>My questions are:
>>
>>1: Does this mean it's pointless to use RSVP graceful restart without
>>    also using IGP graceful restart (for whatever IGP is active).
>>
>>2: Is IGP graceful restart sufficient to prevent this problem?  For
>>    instance, OSPF's restart procedure requires all preserved state to
>>    be thrown away if a topology change is detected.
>>
>>3: An originating node can use OAM to validate the data plane of an
>>    LSP, and choose to ignore what routing tells it about the
>>    destination's reachability.  But what about transit nodes?  As far
>>    as I know, MPLS doesn't support segment-OAM, and it would be
>>    prohibitive for every transit node to run its own OAM streams
>>    to detect self-to-end connectivity.
>>
>>4: Are there other solutions to this problem?
>>
>>One possible solution might be route-pinning, but RSVP doesn't have a 
>>built-in mechanism for this.  The usual workaround (signal the LSP, 
>>requesting route-recording, then turn the RRO into an ERO for 
>>subsequent
>>refreshes) can work, but are there situations where even this would be 
>>insufficient to prevent a transit node from rerouting/tearing the 
>>connection in this particular situation (where RSVP is doing a 
>>graceful restart but the IGP is not)?
>>
>>-- David
> 
> 


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



From mpls-bounces@lists.ietf.org Fri Sep 30 10:51:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELMEe-0003DS-2l; Fri, 30 Sep 2005 10:51:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELMEb-0003DN-Rc
	for mpls@megatron.ietf.org; Fri, 30 Sep 2005 10:51:37 -0400
Received: from jera.movaz.com (webmail.movaz.com [70.158.43.219])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15400
	for <mpls@lists.ietf.org>; Fri, 30 Sep 2005 10:51:35 -0400 (EDT)
From: ibryskin@movaz.com
Received: by jera.movaz.com (Postfix, from userid 30)
	id 603D5144EB; Fri, 30 Sep 2005 10:51:06 -0400 (EDT)
Received: from 68.100.80.11 (SquirrelMail authenticated user ibryskin)
	by webmail.movaz.com with HTTP; Fri, 30 Sep 2005 10:51:06 -0400 (EDT)
Message-ID: <3648.68.100.80.11.1128091866.squirrel@webmail.movaz.com>
In-Reply-To: <433D4591.4080308@marconi.com>
References: <OF603BDC4C.FF916B57-ON4825708C.000B1829@ctbri.com.cn>
	<433D4591.4080308@marconi.com>
Date: Fri, 30 Sep 2005 10:51:06 -0400 (EDT)
To: "David Charlap" <David.Charlap@marconi.com>
User-Agent: SquirrelMail/1.4.1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3
Importance: Normal
Content-Transfer-Encoding: 8bit
Cc: 'IETF CCAMP List' <ccamp@ops.ietf.org>, 'IETF MPLS List' <mpls@ietf.org>
Subject: [mpls] Re: Graceful restart - inter-protocol dependencies
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

David,

I think your view on the RSVP-TE is a bit obsolete. The signaling
subsystem should only react on the *data plane* events (e.g. detected data
plane failures) rather than on the events that happen in routing. Routing
events may at maximum cause the LSP ingress (or more precisely path
computation entity that performed path computation for the LSP) to
re-evaluate the path. Note also that TE paths are computed based on IGP-TE
advertisings rather than on IGP advertisings and a failure of a an IP link
does not necessarily change the latter. This is more obvious in non-packet
switched networks, but is very true in IP networks as well

The bottom line:

a) An intermediate LSR should never attempt to re-route TE LSP based on
IGP events

b) Detected data plane failures should be signaled (via data or control
plane) to the LSP ingress LSR or other LSR(s) responsible for recovery,
and recovery action may (restoration) or may not (protection) result in
the LSP rerouting. The latter may happen even if there were no changes
detected by IGP (in fact, operation is completely orthogonal to what
happens in IP routing)

c) It is perfectly reasonable to implement the RSVP-TE graceful restart
without implementing OSPF graceful restart. Again, the two are not
related.

Igor



> Then we are talking about different protocols.  I'm specifically
> referring to RSVP-TE, as defined by RFC 3209.
>
> I am aware that RSVP-TE's signaling mechanism (even just a PathErr
> message) will probably reach the ingress node long before routing can
> reconverge.  But that's not the question.
>
> The question is, if the node failure is due to a restart, and it has
> implemented RSVP-TE restart (yes, I'm aware that this is a GMPLS
> extnsion), but has not implemented graceful restart for any routing
> protocols, then the originating node won't receive any RSVP-level
> information about the restarting node.  But the IGP will.
>
> We want to prevent the reroute that would normally happen as a result of
> the route change.  Originating nodes can test the LSP using OAM, if
> there is no other choice, but transit nodes don't have that option.
>
> Ultimately, this comes down to my original questions:
>
> 	Does it make any sense to use RSVP graceful restart in a
> 	network where graceful restart is not being used for any
> 	routing protocols?
>
> 	If the answer to the previous question is yes, what can be
> 	done (if anything) to prevent originating and transit nodes
> 	from rerouting LSPs as a result of the route-table change?
>
> -- David
>
> Jing Ruiquan wrote:
>> Hi David,
>>
>> We should specify which version of RSVP we are talking. What I have said
>> is
>> about GMPLS RSVP-TE as used in ASON.
>>
>> When there is a failed link within the network, the ingress node will
>> know
>> the failure by transport plan OAM mechanism such as SDH path layer AIS,
>> or
>> by RSVP-TE Notify message. And usually these mechanisms are faster than
>> routing protocol convergence speed. After the ingress node knows which
>> link
>> or route has failed, it will do the rerouting while excluding the failed
>> link or route.
>>
>> Hope I say it clearly :-)
>>
>> Rick
>>
>> -----Original Message-----
>> From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On
>> Behalf
>> Of David Charlap
>> Sent: Thursday, September 29, 2005 10:35 PM
>> To: 'IETF MPLS List'; 'IETF CCAMP List'
>> Subject: Re: Graceful restart - inter-protocol dependencies
>>
>> But RSVP doesn't work this way.  It is a soft-state protocol.
>>
>> If the route table changes such that the next-hop interface changes,
>> RSVP is
>> supposed to reroute the connection accordingly.
>>
>> This probably won't happen if the next-hop is a strict-hop in an ERO,
>> but it
>> can easily happen if the next-hop is loose or if the LSP is signaled
>> without
>> an ERO (meaning routing is consulted to determine the next-hop to the
>> egress
>> node.)
>>
>> If there is a paragraph in an RFC that says RSVP-TE should ignore all
>> route-table changes once an LSP comes up, I missed it.
>>
>> -- David
>>
>> Jing Ruiquan wrote:
>>
>>>I think only the  originating node should do the rerouting with
>>>RSVP-TE .At the same time, all the nodes will converge their IGP routing
>>
>> data base.
>>
>>>Rick
>>>
>>>-----Original Message-----
>>>From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On
>>>Behalf Of David Charlap
>>>Sent: Thursday, September 29, 2005 2:37 AM
>>>To: IETF MPLS List; IETF CCAMP List
>>>Subject: Graceful restart - inter-protocol dependencies
>>>
>>>Is there any point to implementing RSVP-TE's graceful restart without
>>>also implementing graceful restart for routing protocols?
>>>
>>>On the one hand, RSVP doesn't require routing to recover LSPs.  It
>>>knows the next-hop interface, because of the preserved data-plane
>>
>> connection.
>>
>>>  Whatever other information it may need, the switch can either
>>>preserve this information or recover it from a neighbor using the
>>>RecoveryPath object (draft-ietf-ccamp-rsvo-restart-ext-03).
>>>
>>>On the other hand, nodes more than one hop upstream of the failure
>>>will detect the loss of routing-connectivity to the failed node if IGP
>>>graceful restart is not also implemented.  They may reroute the LSP
>>>away from the failed node, or tear it down altogether, even though the
>>>data plane is still active and RSVP graceful restart is recovering the
>>
>> control-plane state.
>>
>>>An originating node may consider the destination unreachable, as a
>>>result of losing the routes even though the data-plane for the LSP is
>>>still up (which can be confirmed via OAM.)
>>>
>>>A transit node, when processing an loose ERO-hop, may choose to
>>>reroute or fail the LSP if its local topology information says that
>>>the failed (and
>>>restarting) node is not available.  It might even choose to do this
>>>for an established LSP, as a result of Path refresh processing.
>>>
>>>My questions are:
>>>
>>>1: Does this mean it's pointless to use RSVP graceful restart without
>>>    also using IGP graceful restart (for whatever IGP is active).
>>>
>>>2: Is IGP graceful restart sufficient to prevent this problem?  For
>>>    instance, OSPF's restart procedure requires all preserved state to
>>>    be thrown away if a topology change is detected.
>>>
>>>3: An originating node can use OAM to validate the data plane of an
>>>    LSP, and choose to ignore what routing tells it about the
>>>    destination's reachability.  But what about transit nodes?  As far
>>>    as I know, MPLS doesn't support segment-OAM, and it would be
>>>    prohibitive for every transit node to run its own OAM streams
>>>    to detect self-to-end connectivity.
>>>
>>>4: Are there other solutions to this problem?
>>>
>>>One possible solution might be route-pinning, but RSVP doesn't have a
>>>built-in mechanism for this.  The usual workaround (signal the LSP,
>>>requesting route-recording, then turn the RRO into an ERO for
>>>subsequent
>>>refreshes) can work, but are there situations where even this would be
>>>insufficient to prevent a transit node from rerouting/tearing the
>>>connection in this particular situation (where RSVP is doing a
>>>graceful restart but the IGP is not)?
>>>
>>>-- David
>>
>>
>
>
>


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



From mpls-bounces@lists.ietf.org Fri Sep 30 18:33:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELTRd-0001yr-9h; Fri, 30 Sep 2005 18:33:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELTRY-0001xd-Gj
	for mpls@megatron.ietf.org; Fri, 30 Sep 2005 18:33:28 -0400
Received: from ns1.cpanel.btnaccess.com (ns1.cpanel.btnaccess.com
	[205.177.121.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23187
	for <mpls@lists.ietf.org>; Fri, 30 Sep 2005 18:33:25 -0400 (EDT)
Date: Fri, 30 Sep 2005 18:33:25 -0400 (EDT)
Message-Id: <200509302233.SAA23187@ietf.org>
Received: from [65.213.193.13] (helo=)
	by ns1.cpanel.btnaccess.com with smtp (Exim 4.52) id 1ELTRW-0006q7-8R
	for mpls@lists.ietf.org; Fri, 30 Sep 2005 18:33:26 -0400
MIME-Version: 1.0
From: "MPLS 2005" <mpls2005@isocore.com>
To: mpls@ietf.org
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ns1.cpanel.btnaccess.com
X-AntiAbuse: Original Domain - lists.ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - isocore.com
Cc: 
Subject: [mpls] Register Now to Attend MPLS 2005 (Oct 16-19) Washington, DC
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1083101207=="
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

NOTE: You are reading this note because your email program does not
support messages in multi-part "MIME" format (you can see the plain
text version of the message, but the HTML version is garbled).  The 
best solution to this problem is to upgrade to an email program that
supports MIME.  If you can't do that, then just ignore the part
of this message that is improperly displayed by your current email
program.

--===============1083101207==
Content-Type: multipart/alternative; boundary="==========_ALT_1451519089_====="

NOTE: You are reading this note because your email program does not
support messages in multi-part "MIME" format (you can see the plain
text version of the message, but the HTML version is garbled).  The 
best solution to this problem is to upgrade to an email program that
supports MIME.  If you can't do that, then just ignore the part
of this message that is improperly displayed by your current email
program.

--==========_ALT_1451519089_=====
Content-Type: text/plain; charset=us-ascii

MPLS 2005 International Conference - Washington, DC
OCTOBER 16-19, 2005
8th Annual International Conference on MPLS and Related Technologies


Book your hotel today, the special conference rates end 10/4!

Register now to secure your seat today

Register online to save $200.00 

http://www.mpls2005.com/registration.htm
===================================================================
 
===============================================================
Key next generation Internet technologies in one event
===============================================================

Dear Colleague,


===========================================================
MPLS 2005 International Conference
Conference: October 16-19, 2005
Exhibits: October 17-19, 2005
Omni Shoreham Hotel-Washington, DC

www.mpls2005.com

===========================================================

 

****************************************************

6th Public Interoperability Demonstration 

October 20

http://www.mpls2005.com/program.htm

To attend send a message to anusha@isocore.com

****************************************************


		
--==========_ALT_1451519089_=====
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id SAA23187

a{text-decoration:none;}
a:hover{text-decoration:none;}
</style><title>MPLS 2005 International Conference</title>

<style type=3D"text/css">
			.copyrightText {font-size: 9px; font-weight: bold; font-family: verdan=
a; color: #000000;}
</style>


<script language=3D"JavaScript">
function SwitchMenu(obj){
	if(document.getElementById){
	var el =3D document.getElementById(obj);
	var ar =3D document.getElementById("cont").getElementsByTagName("DIV");
		if(el.style.display =3D=3D "none"){
			for (var i=3D0; i<ar.length; i++){
				ar[i].style.display =3D "none";
			}
			el.style.display =3D "block";
		}else{
			el.style.display =3D "none";
		}
	}
}
function ChangeClass(menu, newClass) {=20
	 if (document.getElementById) {=20
	 	document.getElementById(menu).className =3D newClass;
	 }=20
}

document.onselectstart =3D new Function("return false");

</script>

<link href=3D"http://www.isocore.com/mpls2005/style1.css" type=3D"text/cs=
s" rel=3D"stylesheet">
<script language=3D"JavaScript">
var browser     =3D '';
var version     =3D '';
var entrance    =3D '';
var cond        =3D '';
// BROWSER
if (browser =3D=3D ''){
if (navigator.appName.indexOf('Microsoft') !=3D -1)
browser =3D 'IE'
else if (navigator.appName.indexOf('Netscape') !=3D -1)
browser =3D 'Netscape'
else browser =3D 'NN';
}
// VERSION?
if (version =3D=3D ''){
version=3D navigator.appVersion;
paren =3D version.indexOf('(');
whole_version =3D navigator.appVersion.substring(0,paren-1);
version         =3D parseInt(whole_version);
}
// BROWSER & VERSION
if (browser =3D=3D 'IE' && version >=3D 4) entrance =3D 'yes';
if (browser =3D=3D 'IE' && version < 4) entrance =3D 'no';
if (browser =3D=3D 'Netscape' && version >=3D 2.02) entrance =3D 'yes';
if (browser =3D=3D 'Netscape' && version < 2.02) entrance =3D 'no';
if (entrance=3D=3D'yes'){
name0a=3Dnew Image;name0a.src=3D"reg_btn_off.gif";
name0b=3Dnew Image;name0b.src=3D"reg_btn_on.gif";
name0c=3Dnew Image;name0c.src=3D"reg_btn_off.gif";
}
function lighten(imgName) {
if (entrance =3D=3D 'yes'){
imgOn =3D eval(imgName + 'b.src');
document[imgName].src =3D imgOn;
}
}
function darken(imgName) {
if (entrance =3D=3D 'yes'){
imgOff =3D eval(imgName + 'a.src');
document[imgName].src =3D imgOff;
}
}
function darken2(imgName) {
if (entrance =3D=3D 'yes'){
imgClick =3D eval(imgName + 'c.src');
document[imgName].src =3D imgClick;
}
}
</script></head>


<body bgcolor=3D"#b9b9b9" topmargin=3D"0">
<noscript>Your browser does not support script</noscript>=20

<center>

<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" width=3D"845" bgc=
olor=3D"#ffffff">
<!--MAIN TABLE ROW 1, top graphic-->
<tbody><tr>
    <td valign=3D"center" align=3D"left" width=3D"845" background=3D"http=
://www.isocore.com/mpls2005/top_bar.gif" colspan=3D"5" height=3D"100">
    =A0 </td>
</tr>

<!--MAIN TABLE ROW 2, blank gray-->
<tr>
    <td align=3D"right" height=3D"5" valign=3D"middle" colspan=3D"5" bgco=
lor=3D"#b9b9b9">

    </td>
</tr>


<!--MAIN TABLE ROW 3, menu and content, sp supporters-->
  <tr>
  	<!--COLUMN 1, menu-->
    <td align=3D"left" width=3D"200" valign=3D"top"><br>
      		<div id=3D"cont"><a href=3D"http://www.isocore.com/mpls2005/index=
.htm" target=3D"_self">
			<p id=3D"menu1" class=3D"menuOut" onmouseover=3D"ChangeClass('menu1','=
menuOver')" onmouseout=3D"ChangeClass('menu1','menuOut')">=A0 Home</p></a=
>

			<a href=3D"http://www.isocore.com/mpls2005/program.htm#tutorials" targ=
et=3D"_self"><p id=3D"menu2" class=3D"menuOut" onclick=3D"SwitchMenu('sub=
2')" onmouseover=3D"ChangeClass('menu2','menuOver')" onmouseout=3D"Change=
Class('menu2','menuOut')">=A0 Program</p></a>
			<div class=3D"submenu" id=3D"sub2" style=3D"display: none;" onmouseove=
r=3D"ChangeClass('menu2','menuOver')" onmouseout=3D"ChangeClass('menu2','=
menuOut')">
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/program.htm#tutoria=
ls" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls20=
05/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Tutorials</a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/program.htm#technic=
al" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls20=
05/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Technical Sessions<=
/a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/sponsors.htm" title=
=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005/arrow_=
right.gif" border=3D"0" align=3D"middle">=A0 Exhibits</a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/program.htm#interop=
" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005=
/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Inter-Op Demo</a><br>
			</div>

			<a href=3D"http://www.isocore.com/mpls2005/sponsors.htm" target=3D"_se=
lf"><p id=3D"menu3" class=3D"menuOut" onclick=3D"SwitchMenu('sub3')" onmo=
useover=3D"ChangeClass('menu3','menuOver')" onmouseout=3D"ChangeClass('me=
nu3','menuOut')">=A0 Sponsors</p></a>
			<div class=3D"submenu" id=3D"sub3" style=3D"display: none;" onmouseove=
r=3D"ChangeClass('menu3','menuOver')" onmouseout=3D"ChangeClass('menu3','=
menuOut')">
				=A0=A0 <img src=3D"http://www.isocore.com/mpls2005/arrow_right.gif" b=
order=3D"0" align=3D"middle">=A0 <a href=3D"http://www.isocore.com/mpls20=
05/sponsors.htm" title=3D"" target=3D"_self">MPLS 2005 Sponsors</a><br>
				=A0=A0 <img src=3D"http://www.isocore.com/mpls2005/arrow_right.gif" b=
order=3D"0" align=3D"middle">=A0 <a href=3D"http://www.isocore.com/mpls20=
05/sponsorship.htm" title=3D"" target=3D"_self">Exhibiting @ MPLS 2005</a=
><br>
				=A0=A0 <img src=3D"http://www.isocore.com/mpls2005/arrow_right.gif" b=
order=3D"0" align=3D"middle">=A0 <a href=3D"http://www.isocore.com/mpls20=
05/exh_pkg.htm" title=3D"" target=3D"_self">Exhibitor Package</a><br>
			</div>

			<a href=3D"http://www.isocore.com/mpls2005/registration.htm#attendee" =
target=3D"_self"><p id=3D"menu4" class=3D"menuOut" onclick=3D"SwitchMenu(=
'sub4')" onmouseover=3D"ChangeClass('menu4','menuOver')" onmouseout=3D"Ch=
angeClass('menu4','menuOut')">=A0 Registration</p></a>
			<div class=3D"submenu" id=3D"sub4" style=3D"display: none;" onmouseove=
r=3D"ChangeClass('menu4','menuOver')" onmouseout=3D"ChangeClass('menu4','=
menuOut')">
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/registration.htm#at=
tendee" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mp=
ls2005/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Attendees</a><b=
r>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/registration.htm#sp=
eaker" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpl=
s2005/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Speakers</a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/registration.htm#pr=
ess" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2=
005/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Press/Media</a><br=
>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/registration.htm#ex=
hibitor" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/m=
pls2005/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Exhibitor Staf=
f</a><br>
			</div>

			<a href=3D"http://www.isocore.com/mpls2005/pr.htm" target=3D"_self"><p=
 id=3D"menu5" class=3D"menuOut" onclick=3D"SwitchMenu('sub5')" onmouseove=
r=3D"ChangeClass('menu5','menuOver')" onmouseout=3D"ChangeClass('menu5','=
menuOut')">=A0 Press &amp; Media</p>
			<div class=3D"submenu" id=3D"sub5" style=3D"display: none;" onmouseove=
r=3D"ChangeClass('menu5','menuOver')" onmouseout=3D"ChangeClass('menu4','=
menuOut')">
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/pr.htm" title=3D"" =
target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005/arrow_right.=
gif" border=3D"0" align=3D"middle">=A0 Press Releases</a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/registration.htm#pr=
ess" title=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2=
005/arrow_right.gif" border=3D"0" align=3D"middle">=A0 Registration</a><b=
r>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/about.htm" title=3D=
"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005/arrow_rig=
ht.gif" border=3D"0" align=3D"middle">=A0 Press Package</a><br>
			</div>

			<a href=3D"http://www.isocore.com/mpls2005/hotel.htm" target=3D"_self"=
 title=3D"">

			<p id=3D"menu6" class=3D"menuOut" onmouseover=3D"ChangeClass('menu6','=
menuOver')" onmouseout=3D"ChangeClass('menu6','menuOut')">=A0 Hotel &amp;=
 Travel</p></a>
		=09
			<a href=3D"http://www.isocore.com/mpls2005/about.htm" title=3D"" targe=
t=3D"_self"><p id=3D"menu7" class=3D"menuOut" onclick=3D"SwitchMenu('sub7=
')" onmouseover=3D"ChangeClass('menu7','menuOver')" onmouseout=3D"ChangeC=
lass('menu7','menuOut')">=A0 About</p></a>
			<div class=3D"submenu" id=3D"sub7" style=3D"display: none;" onmouseove=
r=3D"ChangeClass('menu7','menuOver')" onmouseout=3D"ChangeClass('menu4','=
menuOut')">
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/about.htm" title=3D=
"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005/arrow_rig=
ht.gif" border=3D"0" align=3D"middle">=A0 About the Conference</a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/tpc.htm" title=3D""=
 target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005/arrow_right=
.gif" border=3D"0" align=3D"middle">=A0 Technical Committee</a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/speakers.htm" title=
=3D"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005/arrow_=
right.gif" border=3D"0" align=3D"middle">=A0 Speakers</a><br>
				=A0=A0 <a href=3D"http://www.isocore.com/mpls2005/contact.htm" title=3D=
"" target=3D"_self"><img src=3D"http://www.isocore.com/mpls2005/arrow_rig=
ht.gif" border=3D"0" align=3D"middle">=A0 Contact Info</a><br>
			</div>=09
		</div>
	<p></p>=09
	<iframe src=3D"http://www.isocore.com/mpls2005/sponlist.htm" width=3D"19=
5" height=3D"125" frameborder=3D"1" scrolling=3D"auto">
If you can see this, your browser doesn't=20
understand IFRAME.  However, you can access the content of the frame by
&lt;a&gt;clicking here&lt;/a&gt;=20
you to the file.
</iframe>
<p>
=A0 =A0
<a href=3D"http://www.isocore.com/mpls2005/Speaker_Area/index.htm" target=
=3D"_blank"><img src=3D"http://www.isocore.com/mpls2005/icon12.gif" borde=
r=3D"0" align=3D"middle">=20
<b><u>Speaker Area</u></b></a><br>=A0 =A0 (password required)</p><hr>
<p></p>
<p>
<b>Tel:</b><br> =A0 =A0  703.860.1777<br>
<b>Email:</b><br> =A0 =A0 <a href=3D"mailto:mpls2005-info@isocore.com">mp=
ls2005-info@isocore.com</a>
</p>


	</td>
   =20
  	<!--COLUMN 2, blank gray-->   =20
	<td width=3D"10" bgcolor=3D"#b9b9b9">=A0=20
	</td>
   =20
    <!--COLUMN 3, content-->
	<td valign=3D"top" width=3D"480"><strong>
	<center>

  =20
     <p> <font color=3D"#FF0000"><b>Book your hotel today, the special co=
nference rates end 10/4!</b></font> <br>
	<CENTER>
      <P>MPLS 2005 INTERNATIONAL CONFERENCE
      <BR>
      OCTOBER 16-19, 2005<br>
      <A HREF=3D"hotel.htm" TARGET=3D"_self">OMNI SHOREHAM HOTEL</a><br>
      WASHINGTON, DC
      </STRONG><BR>8th Annual International=20
      Conference on <BR>MPLS and Related Technologies</P>
  =20
     <P></P>
    =20
      <CENTER>
=09
      <center>
	<!--Registration Button-->
	  </strong><div align=3D"right">
<strong>	  <a href=3D"http://www.isocore.com/mpls2005/registration.htm">
      <img alt=3D"Registration" src=3D"http://www.isocore.com/mpls2005/re=
g_btn_off.gif" border=3D"0" name=3D"name0"></a>=20
      </strong></div><strong><br>
      </strong>
     =20
      <table cellpadding=3D"0" cellspacing=3D"0" border=3D"0">
      <tbody><tr>
      		<td colspan=3D"2" bgcolor=3D"#ff9900">
       		<center><b><p>Conference Chair</p></b></center>
       		</td>
       		<td bgcolor=3D"#ffffff">=A0</td>
      		<td colspan=3D"2" bgcolor=3D"#ff9900">
       		<center><b><p>Technical Co-Chairs</p></b></center>
       		</td>
      </tr>
     =20
      <tr>
      		<td VALIGN=3D"top" ALIGN=3D"left" COLSPAN=3D2><A HREF=3D"http://w=
ww.isocore.com/mpls2005/bio.htm" TARGET=3D"_blank">
      		<IMG SRC=3D"http://www.isocore.com/mpls2005/cochairs.gif" ALT=3D"=
T. Okada & J. Agogbua" BORDER=3D"0" ALIGN=3D"MIDDLE"></a>
      		</td>
       		<td BGCOLOR=3D"#ffffff">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
		=09
			<td>
      			<table cellpadding=3D"0" cellspacing=3D"0" border=3D"0">
	  			  <tbody><tr>     =20
      				<td valign=3D"middle" align=3D"right"><a href=3D"http://www.iso=
core.com/mpls2005/tpc.htm" target=3D"_self"><br>
           			<img src=3D"http://www.isocore.com/mpls2005/adrian.gif" alt=
=3D"Adrian Farrel" border=3D"0" width=3D"50" align=3D"middle">
      				</a>
      				</td>
      				<td valign=3D"bottom"><a href=3D"http://www.isocore.com/mpls200=
5/tpc.htm" target=3D"_self">
      				<p>Adrian Farrel<br>
      				<b>Old Dog Consulting,<br>
					Co-chair IETF's CCAMP, PCE and L1VPN WGs</b>
	  				</p></a>
	  				</td>
      			  </tr>
			      <tr>
      				<td valign=3D"middle" align=3D"right"><br><a href=3D"http://www=
.isocore.com/mpls2005/tpc.htm" target=3D"_self">
      				<img src=3D"http://www.isocore.com/mpls2005/david_mcdysan.gif" =
alt=3D"David McDysan" border=3D"0" width=3D"50" align=3D"middle">
      				</a>
      				</td>
      				<td valign=3D"bottom" align=3D"left"><a href=3D"http://www.isoc=
ore.com/mpls2005/tpc.htm" target=3D"_self">
      				<p>David McDysan<br>
      				<b>MCI</b>
	  				</p></a>
	  				</td>
	  			  </tr>
      			</tbody></table>
      		</td>
      </tr>
      </tbody></table>
     =20
     =20
      </center></center>
<p></p>

<hr>
<p> <img src=3D"http://www.isocore.com/mpls2005/arrow_right.gif" align=3D=
"middle" border=3D"0"> <a href=3D"http://www.isocore.com/mpls2005/program=
.htm" target=3D"_self">
<u><b>Conference Program</b></u></a>=20
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
<img src=3D"http://www.isocore.com/mpls2005/arrow_right.gif" align=3D"mid=
dle" border=3D"0"> <a href=3D"http://www.isocore.com/mpls2005/program.htm=
#interop" target=3D"_self">
<u><b>Inter-Op Demo</b></u></a>=20
</p><hr>
<center>
      <table border=3D"0" cellpadding=3D"2" cellspacing=3D"0" width=3D"10=
0%">
      <tbody><tr> <td colspan=3D"2"> <font face=3D"Arial" size=3D"1" colo=
r=3D"#990000"><h5>
     <br>
      <b>PLATINUM SPONSORS:</b></h5></font></td></tr>
      <tr>
      <td align=3D"center">
      <img src=3D"http://www.isocore.com/mpls2005/logos/adc.gif" alt=3D"A=
DC"> =A0 =A0=20
      <img src=3D"http://www.isocore.com/mpls2005/logos/avicilogo.gif" al=
t=3D"Avici">=20
      =A0 =A0  <img src=3D"http://www.isocore.com/mpls2005/logos/chiarolo=
go.gif" alt=3D"Chiaro">
      =A0 =A0  <img src=3D"http://www.isocore.com/mpls2005/logos/ciscolog=
o.gif" alt=3D"Cisco">
      =A0 =A0  <img src=3D"http://www.isocore.com/mpls2005/logos/Iso_logo=
3.jpg" alt=3D"Isocore" width=3D"130">
      =A0 =A0  <a href=3D"http://www.isocore.com/mpls2005/juniper.htm" ta=
rget=3D"_blank"><img src=3D"http://www.isocore.com/mpls2005/logos/juniper=
logo.gif" alt=3D"Juniper" border=3D"0"></a>
      =A0 =A0  <img src=3D"http://www.isocore.com/mpls2005/logos/lucentlo=
go.gif" alt=3D"Lucent">
      =A0 =A0  <img src=3D"http://www.isocore.com/mpls2005/logos/nortello=
go.jpg" alt=3D"Nortel" width=3D"150">
      =A0 =A0  <img src=3D"http://www.isocore.com/mpls2005/logos/quarry_l=
ogo.jpg" alt=3D"Reef Point">
      =A0 =A0  <img src=3D"http://www.isocore.com/mpls2005/logos/tellabsl=
ogo.gif" alt=3D"Tellabs"><p></p>
      <img src=3D"http://www.isocore.com/mpls2005/logos/keihanna.gif" alt=
=3D"Keihanna">
      </td>
      </tr>
            <tr> <td colspan=3D"2"> <font face=3D"Arial" size=3D"1" color=
=3D"#990000">=A0 =A0 <h5><b>GOLD SPONSORS:</b></h5></font></td></tr>
      <tr>
      <td align=3D"center">
      <a href=3D"http://www.isocore.com/mpls2005/alcatel.htm" target=3D"_=
blank"><img src=3D"http://www.isocore.com/mpls2005/logos/alcatellogo.jpg"=
 alt=3D"Alcatel" width=3D"150" border=3D"0"> </a>
      =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/cienalo=
go.gif" alt=3D"Ciena" width=3D"150">
      =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/extreme=
logo.gif" alt=3D"Extreme Networks" width=3D"150">
      =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/fujitsu=
.gif" alt=3D"Fujitsu" width=3D"150">
      =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/ixialog=
o.gif" alt=3D"IXIA">
	  =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/ECI.gif" a=
lt=3D"ECI Telecom">
      =A0 =A0   <a href=3D"http://www.isocore.com/mpls2005/mangrove.htm" =
target=3D"_blank"><img src=3D"http://www.isocore.com/mpls2005/logos/mangr=
ovelogo.jpg" alt=3D"Mangrove" border=3D"0"></a>
      =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/redback=
logo.gif" alt=3D"Redback">
      =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/spirent=
logo.gif" alt=3D"Spirent Communications" width=3D"150">
      =A0 =A0   <img src=3D"http://www.isocore.com/mpls2005/logos/wandl_l=
ogo.gif" alt=3D"WANDL">
      </td>
      </tr>

	  </tbody></table> </center>

     =20
      </td>

  	<!--COLUMN 4, blank gray-->
	<td width=3D"10" bgcolor=3D"#b9b9b9">=A0=20
	</td>


  	<!--COLUMN 5, supporters-->
	<td valign=3D"top" width=3D"140" align=3D"center"><p></p>
	<img src=3D"http://www.isocore.com/mpls2005/logos/carrier_logos.gif" bor=
der=3D"0">
	</td>
</tr>

<!--MAIN TABLE ROW 4, blank gray-->
<tr>
<td align=3D"right" height=3D"5" valign=3D"middle" colspan=3D"5" bgcolor=3D=
"#b9b9b9">
</td>
</tr>

<!--MAIN TABLE ROW 5, rights reserved-->
<tr bgcolor=3D"#ff9900">
<td colspan=3D"5" align=3D"right">
<span class=3D"copyrightText">=A9 2005 ISOCORE CORP. ALL RIGHTS RESERVED=A0=
</span></td>
</tr>

</tbody></table>





</center></body></html>
--==========_ALT_1451519089_=====--




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

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

--===============1083101207==--






From mpls-bounces@lists.ietf.org Fri Sep 30 20:47:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELVWv-0004CO-1G; Fri, 30 Sep 2005 20:47:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELVWt-0004CJ-5i
	for mpls@megatron.ietf.org; Fri, 30 Sep 2005 20:47:07 -0400
Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.76.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01451
	for <mpls@lists.ietf.org>; Fri, 30 Sep 2005 20:47:05 -0400 (EDT)
From: va4me@comcast.net
Received: from 204.127.205.145 ([204.127.205.145])
	by comcast.net (sccrmhc13) with SMTP
	id <2005100100463401300fm5ile>; Sat, 1 Oct 2005 00:46:35 +0000
Received: from [68.48.113.87] by 204.127.205.145;
	Sat, 01 Oct 2005 00:46:34 +0000
To: mpls@ietf.org
Date: Sat, 01 Oct 2005 00:46:34 +0000
Message-Id: <100120050046.29742.433DDC6A00015FD30000742E22007623020A03CB0E90@comcast.net>
X-Mailer: AT&T Message Center Version 1 (Dec 17 2004)
X-Authenticated-Sender: dmE0bWVAY29tY2FzdC5uZXQ=
Cc: fenner@research.att.com, 
Subject: [mpls] MPLS 2005 Conference 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Is there any way you can get these guys to stop spamming the various PPVPN/MPLS mailing lists?

Unless they are giving free admission to list members, they should not be using IETF mailing lists to advertise their conference. 

Thank you!!


---------

-----Original Message-----
From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org]On Behalf Of MPLS 2005
Sent: Friday, September 30, 2005 4:33 PM
To: mpls@ietf.org
Subject: [mpls] Register Now to Attend MPLS 2005 (Oct 16-19) Washington, DC


a{text-decoration:none;} a:hover{text-decoration:none;} Your browser does not support script 
  



  Home  Program     Tutorials
     Technical Sessions
     Exhibits
     Inter-Op Demo
  Sponsors     MPLS 2005 Sponsors
     Exhibiting @ MPLS 2005
     Exhibitor Package
  Registration     Attendees
     Speakers
     Press/Media
     Exhibitor Staff
  Press & Media     Press Releases
     Registration
     Press Package
  Hotel & Travel  About     About the Conference
     Technical Committee
     Speakers
     Contact Info

     Speaker Area
    (password required)



Tel:
    703.860.1777
Email:
    mpls2005-info@isocore.com   Book your hotel today, the special conference rates end 10/4! 

MPLS 2005 INTERNATIONAL CONFERENCE 
OCTOBER 16-19, 2005
OMNI SHOREHAM HOTEL
WASHINGTON, DC 
8th Annual International Conference on 
MPLS and Related Technologies
 

Conference Chair Technical Co-Chairs
           
 Adrian Farrel
Old Dog Consulting,
Co-chair IETF's CCAMP, PCE and L1VPN WGs 

 David McDysan
MCI 





 Conference Program                              Inter-Op Demo 




PLATINUM SPONSORS:
                                             
 
    
GOLD SPONSORS:
                                              
   

© 2005 ISOCORE CORP. ALL RIGHTS RESERVED 

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



From mpls-bounces@lists.ietf.org Fri Sep 30 22:50:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELXSc-0001lm-BI; Fri, 30 Sep 2005 22:50:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELXSa-0001lh-26
	for mpls@megatron.ietf.org; Fri, 30 Sep 2005 22:50:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04956
	for <mpls@ietf.org>; Fri, 30 Sep 2005 22:50:45 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ELXaX-0006vr-Vx
	for mpls@ietf.org; Fri, 30 Sep 2005 22:59:03 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-2.cisco.com with ESMTP; 30 Sep 2005 19:50:38 -0700
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j912oX4u016102;
	Fri, 30 Sep 2005 19:50:33 -0700 (PDT)
Received: from [192.168.1.21] (hkidc-vpn-client-234-51.cisco.com
	[10.75.234.51])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j91323JE021483;
	Fri, 30 Sep 2005 20:02:05 -0700
In-Reply-To: <100120050046.29742.433DDC6A00015FD30000742E22007623020A03CB0E90@comcast.net>
References: <100120050046.29742.433DDC6A00015FD30000742E22007623020A03CB0E90@comcast.net>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <082C0844-2705-4201-82D7-A1A330D1DB32@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Fred Baker <fred@cisco.com>
Subject: Re: [mpls] MPLS 2005 Conference 
Date: Sun, 2 Oct 2005 07:18:29 +0430
To: va4me@comcast.net
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=1680; t=1128135729; x=1128567929;
	c=nowsp; s=nebraska;
	h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; 
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Re=3A=20[mpls]=20MPLS=202005=20Conference=20|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Sun,=202=20Oct=202005=2007=3A18=3A29=20+0430|
	Content-Type:text/plain=3B=20charset=3DUTF-8=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:quoted-printable;
	b=WC9cNBH35o1Sc9L9INWJYFdBwY8l8mC+hHDp+jTZHXXg4g6gAuUWutkZSqLqydkak7HwLfoR
	8L9PWRvIS/MB0M8QhZILs/x1mCNBxkqyMS+D051FmH4y5nq4pl3rD1MIBET5REONM87d6jR1l6x
	8+ik9JaXb+dhm5hun54staiE=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( message from cisco.com verified; ); 
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: quoted-printable
Cc: fenner@research.att.com, mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

the chairs have the capability of blocking the sender's addresses. =20
That might be taken unkindly, but it would get the point across.

On Oct 1, 2005, at 5:16 AM, va4me@comcast.net wrote:

> Is there any way you can get these guys to stop spamming the =20
> various PPVPN/MPLS mailing lists?
>
> Unless they are giving free admission to list members, they should =20
> not be using IETF mailing lists to advertise their conference.
>
> Thank you!!
>
>
> ---------
>
> -----Original Message-----
> From: mpls-bounces@lists.ietf.org [mailto:mpls-=20
> bounces@lists.ietf.org]On Behalf Of MPLS 2005
> Sent: Friday, September 30, 2005 4:33 PM
> To: mpls@ietf.org
> Subject: [mpls] Register Now to Attend MPLS 2005 (Oct 16-19) =20
> Washington, DC
>
>
> a{text-decoration:none;} a:hover{text-decoration:none;} Your =20
> browser does not support script
>
>
>
>
>   Home  Program     Tutorials
>      Technical Sessions
>      Exhibits
>      Inter-Op Demo
>   Sponsors     MPLS 2005 Sponsors
>      Exhibiting @ MPLS 2005
>      Exhibitor Package
>   Registration     Attendees
>      Speakers
>      Press/Media
>      Exhibitor Staff
>   Press & Media     Press Releases
>      Registration
>      Press Package
>   Hotel & Travel  About     About the Conference
>      Technical Committee
>      Speakers
>      Contact Info
>
>      Speaker Area
>     (password required)
>
>
>
> Tel:
>     703.860.1777
> Email:
>     mpls2005-info@isocore.com   Book your hotel today, the special =20
> conference rates end 10/4!
>
> MPLS 2005 INTERNATIONAL CONFERENCE
> OCTOBER 16-19, 2005
> OMNI SHOREHAM HOTEL
> WASHINGTON, DC
> 8th Annual International Conference on
> MPLS and Related Technologies
>
>
> Conference Chair Technical Co-Chairs
>
>  Adrian Farrel
> Old Dog Consulting,
> Co-chair IETF's CCAMP, PCE and L1VPN WGs
>
>  David McDysan
> MCI
>
>
>
>
>
>  Conference Program                              Inter-Op Demo
>
>
>
>
> PLATINUM SPONSORS:
>
>
>
> GOLD SPONSORS:
>
>
>
> =EF=BF=BD 2005 ISOCORE CORP. ALL RIGHTS RESERVED
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>

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



