From mpls-bounces@ietf.org  Thu May  1 09:15:05 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C6DC3A6C5E;
	Thu,  1 May 2008 09:15:05 -0700 (PDT)
X-Original-To: mpls@lists.ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id A4BEE3A6AD6; Thu,  1 May 2008 09:15:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080501161501.A4BEE3A6AD6@core3.amsl.com>
Date: Thu,  1 May 2008 09:15:01 -0700 (PDT)
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-multicast-encaps-09.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@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           : MPLS Multicast Encapsulations
	Author(s)       : T. Eckert, et al.
	Filename        : draft-ietf-mpls-multicast-encaps-09.txt
	Pages           : 11
	Date            : 2008-05-01

RFC 3032 established two data link layer codepoints for MPLS, used to
distinguish whether the data link layer frame is carrying an MPLS
unicast or an MPLS multicast packet.  However, this usage was never
deployed.  This specification updates RFC 3032 by redefining the
meaning of these two codepoints.  Both codepoints can now be used to
carry multicast packets.  The second codepoint (formerly the
"multicast codepoint") is now to be used only on multiaccess media,
and it is to mean "the top label of the following label stack is an
upstream-assigned label".

RFC 3032 does not specify the destination address to be placed in the
"MAC DA" field of an ethernet frame which carries an MPLS multicast
packet.  This document provides that specification.

This document updates RFC 3032 and RFC 4023.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-multicast-encaps-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-mpls-multicast-encaps-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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

--NextPart--


From mpls-bounces@ietf.org  Thu May  1 10:51:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E10D228C3FC;
	Thu,  1 May 2008 10:51:02 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B2E63A6A4F
	for <mpls@core3.amsl.com>; Thu,  1 May 2008 10:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Gykf5T+Bp0b4 for <mpls@core3.amsl.com>;
	Thu,  1 May 2008 10:51:00 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 2C77228C430
	for <mpls@lists.ietf.org>; Thu,  1 May 2008 10:49:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id C3425323D62;
	Thu,  1 May 2008 10:49:52 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 30886-09; Thu,  1 May 2008 10:49:52 -0700 (PDT)
Received: from [?*???n?IPv6???1] (login005.redback.com [155.53.12.64])
	by prattle.redback.com (Postfix) with ESMTP id 25F20323D5F;
	Thu,  1 May 2008 10:49:52 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v753)
To: OSPF List <ospf@ietf.org>, mpls@lists.ietf.org
Message-Id: <BE0DB7DB-8297-4180-AE37-11DA759B1299@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Thu, 1 May 2008 13:48:28 -0400
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
Subject: [mpls] Last Chance on draft-ietf-mpls-number-0-bw-te-lsps-09.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0396581011=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


--===============0396581011==
Content-Type: multipart/alternative; boundary=Apple-Mail-273--571325679


--Apple-Mail-273--571325679
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

We have decided to allow for a 1 week last call on the subject MPLS  
WG document in both the OSPF and ISIS WGs. It was previously last  
called but this was some time ago (1-2 years back). If you have any  
comments (other than no draft should be allowed to have a title  
spanning 2 full lines), please send them to this list and the MPLS  
list (mpls@lists.ietf.org) by 12:00 AM EST on Friday, May 9th.

For your convenience:

http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te- 
lsps-09.txt

Thanks,
Acee
--Apple-Mail-273--571325679
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
We have decided to allow for a 1 week last call on the subject MPLS WG =
document in both the OSPF and ISIS WGs. It was previously last called =
but this was some time ago (1-2 years back). If you have any comments =
(other than no draft should be allowed to have a title spanning 2 full =
lines), please send them to this list and the MPLS list (<a =
href=3D"mailto:mpls@lists.ietf.org">mpls@lists.ietf.org</a>) by 12:00 AM =
EST on Friday, May 9th.=A0<div><br></div><div>For your =
convenience:=A0</div><div><br></div><div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica"><a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te=
-lsps-09.txt">http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0=
-bw-te-lsps-09.txt</a></font></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
class=3D"Apple-style-span" face=3D"Helvetica"><br></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Thanks,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Acee</div></div></body></html>=

--Apple-Mail-273--571325679--

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

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

--===============0396581011==--


From mpls-bounces@ietf.org  Thu May  1 10:51:06 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11F9A28C42A;
	Thu,  1 May 2008 10:51:06 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 655923A6D2F
	for <mpls@core3.amsl.com>; Thu,  1 May 2008 10:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id a7FY9GILLWxt for <mpls@core3.amsl.com>;
	Thu,  1 May 2008 10:50:59 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 75AA828C42D
	for <mpls@lists.ietf.org>; Thu,  1 May 2008 10:49:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id EFDFD323D62;
	Thu,  1 May 2008 10:49:51 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 31141-02; Thu,  1 May 2008 10:49:51 -0700 (PDT)
Received: from [?*???n?IPv6???1] (login005.redback.com [155.53.12.64])
	by prattle.redback.com (Postfix) with ESMTP id 7943C323D5F;
	Thu,  1 May 2008 10:49:51 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v753)
To: OSPF List <ospf@ietf.org>, mpls@lists.ietf.org
Message-Id: <630B2D95-54D8-431A-925A-2D9623067F85@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Thu, 1 May 2008 13:48:11 -0400
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
Subject: [mpls] Last Chance on draft-ietf-mpls-number-0-bw-te-lsps-09.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1675452623=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


--===============1675452623==
Content-Type: multipart/alternative; boundary=Apple-Mail-272--571342850


--Apple-Mail-272--571342850
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

We have decided to allow for a 1 week last call on the subject MPLS  
WG document in both the OSPF and ISIS WGs. It was previously last  
called but this was some time ago (1-2 years back). If you have any  
comments (other than no draft should be allowed to have a title  
spanning 2 full lines), please send them to this list and the MPLS  
list (mpls@lists.ietf.org) by 12:00 AM EST on Friday, May 9th.

For your convenience:

http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te- 
lsps-09.txt

Thanks,
Acee
--Apple-Mail-272--571342850
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">We have decided to allow for a =
1 week last call on the subject MPLS WG document in both the OSPF and =
ISIS WGs. It was previously last called but this was some time ago (1-2 =
years back). If you have any comments (other than no draft should be =
allowed to have a title spanning 2 full lines), please send them to this =
list and the MPLS list (<a =
href=3D"mailto:mpls@lists.ietf.org">mpls@lists.ietf.org</a>) by 12:00 AM =
EST on Friday, May 9th.=A0<div><br></div><div>For your =
convenience:=A0</div><div><br></div><div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica"><a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te=
-lsps-09.txt">http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0=
-bw-te-lsps-09.txt</a></font></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
class=3D"Apple-style-span" face=3D"Helvetica"><br></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Thanks,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Acee</div></div></body></html>=

--Apple-Mail-272--571342850--

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

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

--===============1675452623==--


From mpls-bounces@ietf.org  Thu May  1 14:36:50 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E09F73A68AF;
	Thu,  1 May 2008 14:36:49 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6ECD43A68AF
	for <mpls@core3.amsl.com>; Thu,  1 May 2008 14:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.448
X-Spam-Level: 
X-Spam-Status: No, score=-1.448 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, GB_PHARMACY=1, HELO_DYNAMIC_IPADDR2=4.395,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033,
	RDNS_DYNAMIC=0.1, SARE_SUB_YOUR_WOMAN=1.666, STOX_REPLY_TYPE=0.001,
	TVD_FINGER_02=2.134, TVD_RCVD_IP=1.931, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083,
	URIBL_SBL=20, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SG6hB60ejQ31 for <mpls@core3.amsl.com>;
	Thu,  1 May 2008 14:36:48 -0700 (PDT)
Received: from 209-80-229-198.client.mecnet.net
	(209-80-229-198.client.mecnet.net [209.80.229.198])
	by core3.amsl.com (Postfix) with SMTP id 7B3473A68DA
	for <mpls@ietf.org>; Thu,  1 May 2008 14:36:48 -0700 (PDT)
Received: (qmail 18945 invoked from network); Thu, 1 May 2008 17:36:52 -0400
Received: from unknown (HELO ogvk) (59.140.48.95)
	by 209-80-229-198.client.mecnet.net with SMTP;
	Thu, 1 May 2008 17:36:52 -0400
Message-ID: <003101c8abd3$784a8d20$5f308c3b@ogvk>
From: "Bel Mason" <novikov@fnc.fujitsu.com>
To: <mpls@ietf.org>
Date: Thu, 1 May 2008 17:36:52 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2499
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2499
Subject: [mpls] Your woman will be happy!
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

15 Ways to act Longer in bed! http://bestpharmacyprescription.com

Bel Mason

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


From mpls-bounces@ietf.org  Thu May  1 18:37:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A2EB3A6910;
	Thu,  1 May 2008 18:37:03 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4522D3A6963
	for <mpls@core3.amsl.com>; Thu,  1 May 2008 18:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.359
X-Spam-Level: 
X-Spam-Status: No, score=-5.359 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id N7eS6g9FWO2Q for <mpls@core3.amsl.com>;
	Thu,  1 May 2008 18:36:59 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id BF7CC3A684E
	for <mpls@ietf.org>; Thu,  1 May 2008 18:36:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,424,1204520400"; 
   d="scan'208";a="6965575"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 01 May 2008 21:37:01 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m421b0CY024449; 
	Thu, 1 May 2008 21:37:00 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m421b0qO006037;
	Fri, 2 May 2008 01:37:00 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 May 2008 21:37:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 1 May 2008 21:37:00 -0400
Message-ID: <DD7E9F364F33B54881C225192D4872D73D8AA8@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <5A0FF108221C7C4E85738678804B567C060C64A9@ftrdmel3>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
Thread-Index: AciOt90U0PeFnVFrRKeagc1XHaD+UwAc0cPwAVfDT1ACYYyg0AN4p2GA
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: <bruno.decraene@orange-ftgroup.com>
X-OriginalArrivalTime: 02 May 2008 01:37:00.0371 (UTC)
	FILETIME=[04126230:01C8ABF5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11777; t=1209692220;
	x=1210556220; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lufang@cisco.com;
	z=From:=20=22Luyuan=20Fang=20(lufang)=22=20<lufang@cisco.com >
	|Subject:=20RE=3A=20[mpls]=20wg=20last=20call=20on=20draft-
	ietf-mpls-ldp-igp-sync-01.txt |Sender:=20
	|To:=20<bruno.decraene@orange-ftgroup.com>;
	bh=HAWTXVLYR9KWMSTAK6gcENas/jjGCdSPnUmXjvnclPU=;
	b=cJySCY3+zWOhG3AhACS7BeI7jXUF+fNo8xcDj7xMkABZ9z/P8xR5G8LReF
	75SvdmZGJx1zF1SvLn1PD9fr30Uf3AKxQEQeLTslAJvFmSdidguQGEhUxyPT
	/0wltk4E4V;
Authentication-Results: rtp-dkim-2; header.From=lufang@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: mpls@ietf.org
Subject: Re: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Bruno,

Thanks for the discussion again. Please see in-line.  =

Luyuan

> -----Original Message-----
> From: bruno.decraene@orange-ftgroup.com =

> [mailto:bruno.decraene@orange-ftgroup.com] =

> Sent: 14 April 2008 06:18
> To: Luyuan Fang (lufang)
> Cc: loa@pi.se; mpls@ietf.org
> Subject: RE: [mpls] wg last call on =

> draft-ietf-mpls-ldp-igp-sync-01.txt
> =

> Hi Luyuan,
> =

> Thanks for your detailed answers.
> More in-line.
> =

> Bruno
> =

> > De=A0: Luyuan Fang (lufang) [mailto:lufang@cisco.com]
> > =

> > Hi Bruno,
> > =

> > Thank you for the comments. Please see in-line.
> > =

> > > -----Original Message-----
> > >
> > > Hi Markus, Alia, Luyuan, all,
> > >
> > > A few comments:
> > >
> > > 1) May be the document should talk about its interaction with =

> > > graceful restart. (I guess this document should not be =

> used when GR =

> > > is used, unless GR is aborted or failed.).
> > >
> > =

> > Very good point. Let's try to look the relationship between LDP-IGP =

> > synch (LDP-IGP) and Graceful Restart (GR). In fact, LDP-IGP is also =

> > used when GR is used.
> > =

> > There are LDP GR [RFC 3478] and IGP GR - OSPF GR [RFC 3623] =

> and ISIS =

> > GR [RFC 3847].
> > =

> > A. LDP GR and LDP-IGP synch:
> > =

> > LDP GR provides a mechanism to minimize the impact on MPLS labeled =

> > traffic caused by LSR's control plane restart. LDP GR is taking the =

> > proactive approach.
> > =

> > LDP-IGP synch is reactive, it provides the exchange and =

> synch action =

> > between LDP and IGP when LDP is already failed. It prevents router =

> > sending traffic to the path where IGP is up and LDP is down.
> > =

> > There are many occasions you don't have a chance to =

> gracefully restart.
> > E.g. bring up a new link; operational error - missed to =

> configure LDP; =

> > implementation error causes label corruption, etc.
> > =

> > Both LDP GR and LDP-IGP synch provide labeled traffic =

> protection under =

> > different conditions.
> =

> Agreed: both GR and LDP-IGP sync have value and can be =

> enabled on the same router at the same time.
> =

> My point was that for a given failure, only one of mechanism =

> should take care of the failure. So if GR handle the failure, =

> eg LDP session failure, LDP-IGP sync should not change the =

> IGP link cost.
> =

> > B. IGP GR and LDP-IGP synch
> > =

> > IGP GR or non-stop forwarding (NSF) is to keep IGP router =

> stay on the =

> > forwarding path even as its IGP is restarted.
> > =

> > An IGP instance performing NSF should honor the LDP-IGP synch =

> > procedure to check the LDP-IGP synch parameter on the =

> standby routing device.
> =

> Do you mean: what should we do if between two neighbor =

> routers, IGP GR is working but is still underway while LDP GR failed?
> I didn't think of this specific interaction but the subject =

> of interaction between IGP and LDP GR procedures seems broad. =

> I don't have detailed knowledge of IS-IS GR, but in general =

> to stay in the safe area, it seems that the IGP topology =

> should not change during the IGP GR procedure. So in this =

> case, what should be the LDP-IGP sync behavior?
> =

> Note that these GR interactions are not specific to the =

> IGP-LDP sync draft. Eg: what should we do if IGP GR succeed =

> and BGP GR failed? (for a node proving connectivity between =

> two ASBRs of the same AS where tunneling (MPLS or IP) is not used).
> =

> so we can probably keep this out of this draft
> =

> > IGP GR protects traffic during the switch over. LDP-IGP protects =

> > labeled traffic from being blackholed when LDP is faulty for some =

> > reason while IGP is still up.
> > =

> > >
> > > 2) " While the link could still be used for IP =

> forwarding, it is not =

> > > useful for traffic with packets carrying a label stack of =

> more than =

> > > one label or when the IP  address carried in the packet is out of =

> > > the
> > > RFC1918 space."
> > >
> > > It seems that the use of RFC 1918 IP address is just an =

> example. One =

> > > could find others (eg BGP free core).
> > > Proposition to change to " While the link could still be =

> used for IP =

> > > forwarding, it is not useful for MPLS forwarding (e.g.
> > > MPLS VPN, BGP free core.)"
> > >
> > =

> > Agreed. We can used both examples.
> > =

> > How about we say "While the link could still be used for IP =

> > forwarding, it is not useful for MPLS forwarding, e.g., =

> MPLS VPN; BGP =

> > route free core; IP address carried in the packet is out of the =

> > RFC1918 space, etc."?
> =

> Fine, thanks.
> =

> > >
> > > 3) "The LDP protocol itself has currently no means to =

> indicate to a =

> > > service depending on it whether there is an uninterrupted label =

> > > switched path available to the desired destination or not."
> > >
> > > Eventually, it could be useful to say why LDP ordered mode + FEC =

> > > withdraw is not an existing mean.
> > =

> > LDP is not a routing protocol. IGP directs the traffic to =

> the shortest =

> > path regardless there is an established LSP along the path or not. =

> > Under the LDP down and IGP up condition: When LDP Ordered =

> Control is =

> > used, the labeled packets drop happens at the LSR of the ingress of =

> > network as LSP cannot be established on the shortest path =

> selected by =

> > IGP; When Independent Control is used, the labeled packets drop =

> > happens at the LSR where LDP failed (could be a mid point =

> in the LSP) as the LSP is broken.
> > We have seen both blackholing cases in live networks. For =

> more details =

> > on LDP blackholing problems and solution, also see "LDP Failure =

> > Detection and Recovery", by L. Fang, A. Atlas, F. Chiussi, K. =

> > Kompella, and G. Swallow, IEEE Communications Vol.42 No.10, =

> October 2004.
> > =

> > > Or may be you want to say that LDP has currently no way =

> to correct =

> > > the issue, for example by using a different IGP path.
> > >
> > =

> > Yes, thanks. We can re-word this similar as you suggested: LDP has =

> > currently no way to correct the issue. LDP is not a routing =

> protocol, =

> > it cannot re-direct traffic to an alternate IGP path.
> =

> Fine, thanks.
> =

> > =

> > > 4) "In the case of OSPF this cost is LSInfinity (16-bit value
> > > 0xFFFF) as proposed in [RFC3137]."
> > >
> > > Could you also indicate the metric to use for IS-IS?
> > > Especially since:
> > > - further in the doc you recommend that all =

> implementation use the =

> > > same metric to avoid asymmetric link cost
> > > - RFC 3784 seems to indicate that the max metric link (2^24 -
> > > 1) is already reserved
> > >
> > =

> > Very good point.
> > We shall add the ISIS max metric in the draft. The max metric value =

> > for ISIS using wide metrics is 0xFFFFFE per RFC 3784.
>  =

> Thanks.
> =

> > =

> > > 5) "It is recommended that both sides of a link implement this =

> > > mechanism to be effective and to avoid asymmetric link =

> costs which =

> > > could cause problems with IP multicast forwarding."
> > >
> > > Avoiding asymetric link cost during all the procedure =

> would require =

> > > that both routers sharing the LDP session have the same way to =

> > > detect when "LDP is considered fully operational". This =

> is currently =

> > > not the case.
> > =

> > Understood. It is a recommendation for better performance, not a =

> > requirement.
> > =

> > > As the document propose to wait "some time", the document could =

> > > possibly propose a default value for this timer and warn =

> that if the =

> > > operator wish to change that value, it should change it =

> on both side =

> > > of the LDP session.
> > >
> > =

> > We prefer not to set the hold-down timer with a default value. The =

> > reason is that the LIB tables size can vary largely, as well the =

> > equipment capability/speed. If the default value is too small, this =

> > function would not work; if it is too big, it slows down the =

> > convergence time. But the hold-down time guidelines through =

> equipment =

> > testing would be helpful.
> =

> You're right but this discussion could apply to lot of =

> default timers. Eg GR timers. Yet most specification defines =

> default values for their timers.
> =

> > LDP End-of-LIB (draft-asati-mpls-ldp-end-of-lib-01.txt) is =

> currently a =

> > work in progress. When End-of-LIB is implemented, it can signal the =

> > end of IGP hold-down time, no longer need for the configured nor =

> > default timers.
> =

> OK, given this, I guess it's not a big deal not to define =

> default value for the timers. May be the document could say =

> that such LDP sync mechanism (LDP End of LIB) should =

> preferably be used (over timers) once they are available. (in =

> order to avoid asymmetric routing)
> =

Agreed, we planned to mention LDP End of LIB work.

> > > Also, as there is a risk of transient asymetric link cost =

> (because =

> > > the end of the procedure is not stricly defined) could =

> you possibly =

> > > provide more precision on the problems that could be faced by IP =

> > > multicast?
> > >
> > =

> > Yes, transient asymmetric cost is always a risk, it is not just for =

> > this problem, it is rather a common problem. e.g. it is same as in =

> > BGP. We would treat it as out of scope for this draft.
> =

> Ok but this document:
> - Specifically states that asymmetric links cost could cause =

> problem with multicast ("asymmetric link costs [which] could =

> cause problems with IP multicast forwarding")
> - In the short term (waiting for LDP end-of-LIB) does not =

> fully avoid asymmetric link cost. Quite the contrary, =

> compared to doing nothing, it creates new opportunity for this.
> =

> So could the draft just list (or reference a document =

> describing) multicast issues with IGP asymmetric cost? =

> Otherwise, as a service provider proving IP, MPLS VPN and =

> multicast on the same AS, while LDP end-of-LIB is not =

> available, I wonder if I should use this draft or not as the =

> draft says it improves MPLS VPN availability but could create =

> issues with multicast.
> =

I have checked with several Multicast experts. The conclusion is that IGP a=
symmetric link cost does not cause =

problems for multicast. So we will remove that line.

> > > Thanks,
> > > Regards,
> > > Bruno
> > >
> > =

> > Thanks,
> > Luyuan
> > =

> > =

> > > > From Loa Andersson
> > > >
> > > > Working group,
> > > >
> > > > this is to initiate a two week working group last call on:
> > > >
> > > > draft-ietf-mpls-ldp-igp-sync-01.txt
> > > >
> > > > Please send your comments to the working group mailing list
> > > or to the
> > > > working group chairs before April 11.
> > > >
> > > > 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@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mpls
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls
> > >
> =

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


From mpls-bounces@ietf.org  Thu May  1 19:02:31 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 993B528C164;
	Thu,  1 May 2008 19:02:31 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1925828C164
	for <mpls@core3.amsl.com>; Thu,  1 May 2008 19:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.979
X-Spam-Level: 
X-Spam-Status: No, score=-5.979 tagged_above=-999 required=5 tests=[AWL=0.619, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DAkDqWCPjeQ8 for <mpls@core3.amsl.com>;
	Thu,  1 May 2008 19:02:29 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id B86B728C0FB
	for <mpls@ietf.org>; Thu,  1 May 2008 19:02:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,424,1204520400"; d="scan'208,217";a="6975441"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 01 May 2008 22:02:30 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4222Ukc007680; 
	Thu, 1 May 2008 22:02:30 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4222UeK011769;
	Fri, 2 May 2008 02:02:30 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 May 2008 22:02:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 1 May 2008 22:02:30 -0400
Message-ID: <DD7E9F364F33B54881C225192D4872D73D8AA9@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <739007.20844.qm@web51007.mail.re2.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
Thread-Index: AcigpWsb9f8eRXwgS5OGmD2095uPxALUCd6Q
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "gaurav gupta" <gaurav_gup1@yahoo.com>,
	"priyanka gupta" <busybee_pg@yahoo.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 02 May 2008 02:02:30.0357 (UTC)
	FILETIME=[9403B850:01C8ABF8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8373; t=1209693750;
	x=1210557750; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lufang@cisco.com;
	z=From:=20=22Luyuan=20Fang=20(lufang)=22=20<lufang@cisco.com >
	|Subject:=20RE=3A=20[mpls]=20wg=20last=20call=20on=20draft-
	ietf-mpls-ldp-igp-sync-01.txt |Sender:=20
	|To:=20=22gaurav=20gupta=22=20<gaurav_gup1@yahoo.com>,=0A=2
	0=20=20=20=20=20=20=20=22priyanka=20gupta=22=20<busybee_pg@y
	ahoo.com>,=20<mpls@ietf.org>;
	bh=0SvKSzKzBBy3mg3HNmXJ177QuaGO7z3rchJlzRe6Egg=;
	b=qVisobUmWT9wh2DeiLcQCESywPEhQj67vLULvWA0IAwV31w7dttZZ/vikz
	HJ9LKcdTkgm4hCZxsSkJjN7q1d7cIHcJcnZgQTqrbaW3XWmzX2l7hb61Thv8
	W8RJ71Gjd+;
Authentication-Results: rtp-dkim-1; header.From=lufang@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1104515760=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1104515760==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8ABF8.93DB88D3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8ABF8.93DB88D3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Priyanka and Gaurav,
=20
Yes, discouraging IP forwarding over the link is to prevent labeled
traffic being blackholed, not to help LDP session establishment.=20
=20
The draft is intend to prevent all three types of failure scenarios.
Nothing is 100%, but good equipment implementation and good operational
procedures would help.
=20
Thanks,
Luyuan


________________________________

	From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
Behalf Of gaurav gupta
	Sent: 17 April 2008 12:07
	To: priyanka gupta; mpls@ietf.org
	Subject: Re: [mpls] wg last call on
draft-ietf-mpls-ldp-igp-sync-01.txt
=09
=09
	Hi Priyanka,
=09
	Discouraging IP forwarding over a link does not help in LDP
session establishment. Discouraging IP forwarding over a link only
prevents traffic loss if IGP is up over a link but LDP bindings are not
already exchanged. The draft mentions 3 reasons for a potential
black-holing of traffic: configuration error, implementation bug or the
reason which I just mentioned above. To my understanding the draft only
prevents from the 3rd reason.
=09
	Hope this helps.
=09
	=20
	Thanks,=20
	Gaurav=20


	----- Original Message ----
	From: priyanka gupta <busybee_pg@yahoo.com>
	To: mpls@ietf.org
	Sent: Thursday, April 17, 2008 4:21:22 AM
	Subject: Re: [mpls] wg last call on
draft-ietf-mpls-ldp-igp-sync-01.txt
=09
=09
	Comments:
	I am not able to understand that how discouraging the IP
forwarding over a link where LDP is not fully established help in LDP
session establishment.
	As you mentioned the reason for blackhole could be
-configuration error or - An implementation bug.  =20
	Can you help me in uderstanding this.
	Secondly,
	"It is recommended this that both side of a link implement
mechanism to be effective and to avoid asymmetric link costs which could

	   cause problems with IP multicast forwarding."
	what exactly mean by IP multicast forwarding problems?

________________________________

	Bollywood, fun, friendship, sports and more. You name it, we
have it.
<http://in.rd.yahoo.com/tagline_groups_1/*http://in.promos.yahoo.com/gro
ups/bestofyahoo/>=20


________________________________

	Be a better friend, newshound, and know-it-all with Yahoo!
Mobile. Try it now.
<http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=3DAhu0=
6i6
2sR8HDtDypao8Wcj9tAcJ>=20


------_=_NextPart_001_01C8ABF8.93DB88D3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE type=3Dtext/css>DIV {
	MARGIN: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Priyanka and Gaurav,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Yes, discouraging IP forwarding over the link =
is to prevent=20
labeled traffic being blackholed, not to help LDP session establishment. =

</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The draft is intend to prevent all three types =
of failure=20
scenarios. Nothing is 100%, but good&nbsp;equipment implementation and =
good=20
operational procedures would help.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN><SPAN =
class=3D488594001-02052008><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Luyuan</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> mpls-bounces@ietf.org=20
  [mailto:mpls-bounces@ietf.org] <B>On Behalf Of </B>gaurav=20
  gupta<BR><B>Sent:</B> 17 April 2008 12:07<BR><B>To:</B> priyanka =
gupta;=20
  mpls@ietf.org<BR><B>Subject:</B> Re: [mpls] wg last call on=20
  draft-ietf-mpls-ldp-igp-sync-01.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif">Hi=20
  Priyanka,<BR><BR>Discouraging IP forwarding over a link does not help =
in LDP=20
  session establishment. Discouraging IP forwarding over a link only =
prevents=20
  traffic loss if IGP is up over a link but LDP bindings are not already =

  exchanged. The draft mentions 3 reasons for a potential black-holing =
of=20
  traffic: configuration error, implementation bug or the reason which I =
just=20
  mentioned above. To my understanding the draft only prevents from the =
3rd=20
  reason.<BR><BR>Hope this helps.<BR>
  <DIV>&nbsp;</DIV>Thanks, <BR>Gaurav
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new =
york,times,serif"><BR><BR>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new =
york,times,serif">-----=20
  Original Message ----<BR>From: priyanka gupta=20
  &lt;busybee_pg@yahoo.com&gt;<BR>To: mpls@ietf.org<BR>Sent: Thursday, =
April 17,=20
  2008 4:21:22 AM<BR>Subject: Re: [mpls] wg last call on=20
  draft-ietf-mpls-ldp-igp-sync-01.txt<BR><BR>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new =
york,times,serif">
  <DIV><PRE><FONT face=3D"Courier New, courier, monaco, monospace, =
sans-serif" size=3D2>Comments:</FONT></PRE><PRE><FONT face=3D"Courier =
New, courier, monaco, monospace, sans-serif" size=3D2>I am not able to =
understand that how discouraging the IP forwarding over a link where LDP =
is not fully established help in LDP session =
establishment.</FONT></PRE><PRE><FONT face=3D"Courier New, courier, =
monaco, monospace, sans-serif" size=3D2>As you mentioned the reason for =
blackhole could be -configuration error or - An implementation bug.   =
</FONT></PRE><PRE><FONT size=3D2>Can you help me in uderstanding =
this.</FONT></PRE><PRE><FONT size=3D2>Secondly,</FONT></PRE><PRE><FONT =
face=3D"Courier New, courier, monaco, monospace, sans-serif" =
size=3D2>"It is recommended this that<FONT style=3D"BACKGROUND-COLOR: =
rgb(0,0,0)"><FONT style=3D"BACKGROUND-COLOR: rgb(255,255,255)"> both =
</FONT></FONT><FONT style=3D"BACKGROUND-COLOR: rgb(255,255,255)">side of =
a link</FONT> implement mechanism to be effective and to avoid <FONT =
color=3D#ff007f>asymmetric link costs which could =
</FONT></FONT></PRE><PRE><FONT face=3D"Courier New, courier, monaco, =
monospace, sans-serif"><FONT size=3D2><FONT =
color=3D#ff007f><SPAN>&nbsp;&nbsp;&nbsp;</SPAN>cause problems =
with</FONT> <SPAN style=3D"COLOR: red">IP multicast =
forwarding</SPAN>."</FONT></FONT></PRE><PRE><FONT size=3D2>what exactly =
mean by IP multicast forwarding problems?</FONT></PRE></DIV></DIV><BR>
  <HR SIZE=3D1>
  Bollywood, fun, friendship, sports and more. You name it, <A=20
  =
href=3D"http://in.rd.yahoo.com/tagline_groups_1/*http://in.promos.yahoo.c=
om/groups/bestofyahoo/"=20
  target=3D_blank rel=3Dnofollow>we have =
it.</A></DIV><BR></DIV></DIV><BR>
  <HR SIZE=3D1>
  Be a better friend, newshound, and know-it-all with Yahoo! Mobile. <A=20
  =
href=3D"http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=
=3DAhu06i62sR8HDtDypao8Wcj9tAcJ ">Try=20
  it now.</A></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8ABF8.93DB88D3--

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

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

--===============1104515760==--


From mpls-bounces@ietf.org  Thu May  1 19:10:50 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB3213A684E;
	Thu,  1 May 2008 19:10:49 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C5743A684E
	for <mpls@core3.amsl.com>; Thu,  1 May 2008 19:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.288
X-Spam-Level: 
X-Spam-Status: No, score=-6.288 tagged_above=-999 required=5 tests=[AWL=0.310, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id w6H4fK-Arkfj for <mpls@core3.amsl.com>;
	Thu,  1 May 2008 19:10:47 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 14C323A6783
	for <mpls@ietf.org>; Thu,  1 May 2008 19:10:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,424,1204520400"; d="scan'208,217";a="6975858"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 01 May 2008 22:10:48 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m422AmVv032765; 
	Thu, 1 May 2008 22:10:48 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m422Am5N014755;
	Fri, 2 May 2008 02:10:48 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 May 2008 22:10:48 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 1 May 2008 22:10:47 -0400
Message-ID: <DD7E9F364F33B54881C225192D4872D73D8AAB@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <DD7E9F364F33B54881C225192D4872D73D8AA9@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
Thread-Index: AcigpWsb9f8eRXwgS5OGmD2095uPxALUCd6QAAEBiUA=
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "gaurav gupta" <gaurav_gup1@yahoo.com>,
	"priyanka gupta" <busybee_pg@yahoo.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 02 May 2008 02:10:48.0490 (UTC)
	FILETIME=[BCECC8A0:01C8ABF9]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10154; t=1209694248;
	x=1210558248; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lufang@cisco.com;
	z=From:=20=22Luyuan=20Fang=20(lufang)=22=20<lufang@cisco.com >
	|Subject:=20RE=3A=20[mpls]=20wg=20last=20call=20on=20draft-
	ietf-mpls-ldp-igp-sync-01.txt |Sender:=20
	|To:=20=22gaurav=20gupta=22=20<gaurav_gup1@yahoo.com>,=0A=2
	0=20=20=20=20=20=20=20=22priyanka=20gupta=22=20<busybee_pg@y
	ahoo.com>,=20<mpls@ietf.org>;
	bh=rLUU1f4mJaD0Y87KkZXc52bGfpmshTl0WkQL54lF850=;
	b=iUW2uT8dd2wE99fmiNwW1Buv9XSYuIKkzXVt5+aluZGGP/SDmxoC6oeo3N
	HqCj8wqZ5DsXKRLIHcLSKyzrjwM8TcsQzKBKbZuCiKQn0YdlBaGTVgKA5PXO
	1SmHljmxAN;
Authentication-Results: rtp-dkim-2; header.From=lufang@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1595351776=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1595351776==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8ABF9.BC9CBE8B"

This is a multi-part message in MIME format.

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

I meant to say to prevent traffic loss from...
Thanks,
Luyuan


________________________________

	From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
Behalf Of Luyuan Fang (lufang)
	Sent: 01 May 2008 22:03
	To: gaurav gupta; priyanka gupta; mpls@ietf.org
	Subject: Re: [mpls] wg last call on
draft-ietf-mpls-ldp-igp-sync-01.txt
=09
=09
	Priyanka and Gaurav,
	=20
	Yes, discouraging IP forwarding over the link is to prevent
labeled traffic being blackholed, not to help LDP session establishment.

	=20
	The draft is intend to prevent all three types of failure
scenarios. Nothing is 100%, but good equipment implementation and good
operational procedures would help.
	=20
	Thanks,
	Luyuan


________________________________

		From: mpls-bounces@ietf.org
[mailto:mpls-bounces@ietf.org] On Behalf Of gaurav gupta
		Sent: 17 April 2008 12:07
		To: priyanka gupta; mpls@ietf.org
		Subject: Re: [mpls] wg last call on
draft-ietf-mpls-ldp-igp-sync-01.txt
	=09
	=09
		Hi Priyanka,
	=09
		Discouraging IP forwarding over a link does not help in
LDP session establishment. Discouraging IP forwarding over a link only
prevents traffic loss if IGP is up over a link but LDP bindings are not
already exchanged. The draft mentions 3 reasons for a potential
black-holing of traffic: configuration error, implementation bug or the
reason which I just mentioned above. To my understanding the draft only
prevents from the 3rd reason.
	=09
		Hope this helps.
	=09
		=20
		Thanks,=20
		Gaurav=20


		----- Original Message ----
		From: priyanka gupta <busybee_pg@yahoo.com>
		To: mpls@ietf.org
		Sent: Thursday, April 17, 2008 4:21:22 AM
		Subject: Re: [mpls] wg last call on
draft-ietf-mpls-ldp-igp-sync-01.txt
	=09
	=09
		Comments:
		I am not able to understand that how discouraging the IP
forwarding over a link where LDP is not fully established help in LDP
session establishment.
		As you mentioned the reason for blackhole could be
-configuration error or - An implementation bug.  =20
		Can you help me in uderstanding this.
		Secondly,
		"It is recommended this that both side of a link
implement mechanism to be effective and to avoid asymmetric link costs
which could=20
		   cause problems with IP multicast forwarding."
		what exactly mean by IP multicast forwarding problems?

________________________________

		Bollywood, fun, friendship, sports and more. You name
it, we have it.
<http://in.rd.yahoo.com/tagline_groups_1/*http://in.promos.yahoo.com/gro
ups/bestofyahoo/>=20


________________________________

		Be a better friend, newshound, and know-it-all with
Yahoo! Mobile. Try it now.
<http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=3DAhu0=
6i6
2sR8HDtDypao8Wcj9tAcJ>=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE type=3Dtext/css>DIV {
	MARGIN: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D795470902-02052008>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D395110802-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I meant to say to prevent&nbsp;<SPAN=20
class=3D795470902-02052008>traffic loss =
</SPAN>from...</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D395110802-02052008><SPAN=20
class=3D795470902-02052008><FONT face=3DArial color=3D#0000ff=20
size=3D2>Thanks,</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D395110802-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Luyuan</FONT></SPAN></DIV></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> mpls-bounces@ietf.org=20
  [mailto:mpls-bounces@ietf.org] <B>On Behalf Of </B>Luyuan Fang=20
  (lufang)<BR><B>Sent:</B> 01 May 2008 22:03<BR><B>To:</B> gaurav gupta; =

  priyanka gupta; mpls@ietf.org<BR><B>Subject:</B> Re: [mpls] wg last =
call on=20
  draft-ietf-mpls-ldp-igp-sync-01.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Priyanka and Gaurav,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Yes, discouraging IP forwarding over the link =
is to=20
  prevent labeled traffic being blackholed, not to help LDP session=20
  establishment. </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>The draft is intend to prevent all three =
types of failure=20
  scenarios. Nothing is 100%, but good&nbsp;equipment implementation and =
good=20
  operational procedures would help.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN><SPAN =
class=3D488594001-02052008><FONT=20
  face=3DArial color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D488594001-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Luyuan</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> mpls-bounces@ietf.org=20
    [mailto:mpls-bounces@ietf.org] <B>On Behalf Of </B>gaurav=20
    gupta<BR><B>Sent:</B> 17 April 2008 12:07<BR><B>To:</B> priyanka =
gupta;=20
    mpls@ietf.org<BR><B>Subject:</B> Re: [mpls] wg last call on=20
    draft-ietf-mpls-ldp-igp-sync-01.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif">Hi=20
    Priyanka,<BR><BR>Discouraging IP forwarding over a link does not =
help in LDP=20
    session establishment. Discouraging IP forwarding over a link only =
prevents=20
    traffic loss if IGP is up over a link but LDP bindings are not =
already=20
    exchanged. The draft mentions 3 reasons for a potential black-holing =
of=20
    traffic: configuration error, implementation bug or the reason which =
I just=20
    mentioned above. To my understanding the draft only prevents from =
the 3rd=20
    reason.<BR><BR>Hope this helps.<BR>
    <DIV>&nbsp;</DIV>Thanks, <BR>Gaurav=20
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new =
york,times,serif"><BR><BR>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new =
york,times,serif">-----=20
    Original Message ----<BR>From: priyanka gupta=20
    &lt;busybee_pg@yahoo.com&gt;<BR>To: mpls@ietf.org<BR>Sent: Thursday, =
April=20
    17, 2008 4:21:22 AM<BR>Subject: Re: [mpls] wg last call on=20
    draft-ietf-mpls-ldp-igp-sync-01.txt<BR><BR>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new =
york,times,serif">
    <DIV><PRE><FONT face=3D"Courier New, courier, monaco, monospace, =
sans-serif" size=3D2>Comments:</FONT></PRE><PRE><FONT face=3D"Courier =
New, courier, monaco, monospace, sans-serif" size=3D2>I am not able to =
understand that how discouraging the IP forwarding over a link where LDP =
is not fully established help in LDP session =
establishment.</FONT></PRE><PRE><FONT face=3D"Courier New, courier, =
monaco, monospace, sans-serif" size=3D2>As you mentioned the reason for =
blackhole could be -configuration error or - An implementation bug.   =
</FONT></PRE><PRE><FONT size=3D2>Can you help me in uderstanding =
this.</FONT></PRE><PRE><FONT size=3D2>Secondly,</FONT></PRE><PRE><FONT =
face=3D"Courier New, courier, monaco, monospace, sans-serif" =
size=3D2>"It is recommended this that<FONT style=3D"BACKGROUND-COLOR: =
rgb(0,0,0)"><FONT style=3D"BACKGROUND-COLOR: rgb(255,255,255)"> both =
</FONT></FONT><FONT style=3D"BACKGROUND-COLOR: rgb(255,255,255)">side of =
a link</FONT> implement mechanism to be effective and to avoid <FONT =
color=3D#ff007f>asymmetric link costs which could =
</FONT></FONT></PRE><PRE><FONT face=3D"Courier New, courier, monaco, =
monospace, sans-serif"><FONT size=3D2><FONT =
color=3D#ff007f><SPAN>&nbsp;&nbsp;&nbsp;</SPAN>cause problems =
with</FONT> <SPAN style=3D"COLOR: red">IP multicast =
forwarding</SPAN>."</FONT></FONT></PRE><PRE><FONT size=3D2>what exactly =
mean by IP multicast forwarding problems?</FONT></PRE></DIV></DIV><BR>
    <HR SIZE=3D1>
    Bollywood, fun, friendship, sports and more. You name it, <A=20
    =
href=3D"http://in.rd.yahoo.com/tagline_groups_1/*http://in.promos.yahoo.c=
om/groups/bestofyahoo/"=20
    target=3D_blank rel=3Dnofollow>we have =
it.</A></DIV><BR></DIV></DIV><BR>
    <HR SIZE=3D1>
    Be a better friend, newshound, and know-it-all with Yahoo! Mobile. =
<A=20
    =
href=3D"http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=
=3DAhu06i62sR8HDtDypao8Wcj9tAcJ ">Try=20
    it now.</A></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8ABF9.BC9CBE8B--

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

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

--===============1595351776==--


From mpls-bounces@ietf.org  Sat May  3 06:22:45 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E2103A684F;
	Sat,  3 May 2008 06:22:45 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2774C3A6AE1
	for <mpls@core3.amsl.com>; Sat,  3 May 2008 06:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.468
X-Spam-Level: 
X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.131, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VkjsmYLVR1Ql for <mpls@core3.amsl.com>;
	Sat,  3 May 2008 06:22:43 -0700 (PDT)
Received: from av9-1-sn3.vrr.skanova.net (av9-1-sn3.vrr.skanova.net
	[81.228.9.185]) by core3.amsl.com (Postfix) with ESMTP id 526BE3A681F
	for <mpls@ietf.org>; Sat,  3 May 2008 06:22:37 -0700 (PDT)
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 9CF4E380AE; Sat,  3 May 2008 15:22:38 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 86C96380A8; Sat,  3 May 2008 15:22:38 +0200 (CEST)
Received: from [127.0.0.1] (h4n2fls31o874.telia.com [213.66.236.4])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 7E54037E42;
	Sat,  3 May 2008 15:22:37 +0200 (CEST)
Message-ID: <481C670F.8090803@pi.se>
Date: Sat, 03 May 2008 15:22:23 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org, George Swallow <swallow@cisco.com>,
	David Ward <dward@cisco.com>, Ross Callon <rcallon@juniper.net>
X-Enigmail-Version: 0.95.6
Subject: [mpls]
 http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt as wg
 document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,

the authors of

http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt

has requested that the document becomes a working group document.

This is to start a two week poll on the mpls wg mailing list.

Please send your comments to the mailing list; we are explicitly
soliciting both negative and positive comments.


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@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From lucy_martine20@yahoo.fr  Sun May  4 14:05:29 2008
Return-Path: <lucy_martine20@yahoo.fr>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41FB43A6F55
	for <ietfarch-mpls-archive@core3.amsl.com>; Sun,  4 May 2008 14:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.995
X-Spam-Level: ***
X-Spam-Status: No, score=3.995 tagged_above=-999 required=5
	tests=[HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=2.188,
	SUBJ_ALL_CAPS=1.806]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jb3bERVuk38o for <ietfarch-mpls-archive@core3.amsl.com>;
	Sun,  4 May 2008 14:05:25 -0700 (PDT)
Received: from n31.bullet.mail.ukl.yahoo.com (n31.bullet.mail.ukl.yahoo.com [87.248.110.148])
	by core3.amsl.com (Postfix) with SMTP id D1FE93A6F93
	for <mpls-archive@lists.ietf.org>; Sun,  4 May 2008 14:04:27 -0700 (PDT)
Received: from [217.146.182.180] by n31.bullet.mail.ukl.yahoo.com with NNFMP; 04 May 2008 21:04:23 -0000
Received: from [87.248.111.146] by t6.bullet.ukl.yahoo.com with NNFMP; 04 May 2008 21:04:23 -0000
Received: from [127.0.0.1] by omp203.mail.ukl.yahoo.com with NNFMP; 04 May 2008 21:04:23 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 852180.40343.bm@omp203.mail.ukl.yahoo.com
Received: (qmail 56907 invoked by uid 60001); 4 May 2008 21:04:23 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.fr;
  h=Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=wQWLPNn9Xpss8bQF36IY2w478Bi4UKWbScHP1oR6tN3yH1WOHk/dL0J9yuIcRGZcaF522r1tm8Etghol1ZUay/MboSfZHS1/ck38y7+J2mbHKwJGciXjf3zNAHKDlORyw+wuvaDt5fE35qyXWYDVDVXWHN6KPoNFPW2jJtRclfU=;
Received: from [41.207.28.156] by web28308.mail.ukl.yahoo.com via HTTP; Sun, 04 May 2008 23:04:23 CEST
Date: Sun, 4 May 2008 23:04:23 +0200 (CEST)
From: Lucy Martine <lucy_martine20@yahoo.fr>
Reply-To: lucy_martine21@yahoo.fr
Subject: CRY  FOR  HELP
To: lucy_martine@yahoo.fr
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1453276933-1209935063=:56651"
Content-Transfer-Encoding: 8bit
Message-ID: <744374.56651.qm@web28308.mail.ukl.yahoo.com>

--0-1453276933-1209935063=:56651
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

  From      : Lucy Martine.
country   : cote d'ivoire
city        : abidjan
contenet : west africa 
email      : lucy_martine20@yahoo.fr 
dearest one,
 
i am Lucy Martine, in progress and  difficulties, i'm using this very long needed opportunity to write to you once more. May i also know from you the academics works and health.
  Please i want you to assiste me transfer my money to your account, my father deposited the money in the bank here africa before his suden death, when my father was in the hospital he called me and relese this information to me as the only daughter, the amount is $9.5 millions usa dollars.
 
 Please contact me with my email address for more detail (lucy_martine20@yahoo.fr)    
  Thanks
Lucy Martine
( lucy_martine20@yahoo.fr )
   
   
   

 __________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités 
http://mail.yahoo.fr Yahoo! Mail 
 __________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités 
http://mail.yahoo.fr Yahoo! Mail 
--0-1453276933-1209935063=:56651
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>  <DIV>From&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Lucy Martine.<BR>country&nbsp;&nbsp; : cote d'ivoire<BR>city&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : abidjan<BR>contenet : west africa <BR>email&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :&nbsp;<A href="mailto:lucy_martine20@yahoo.fr">lucy_martine20@yahoo.fr</A>&nbsp;<BR>dearest one,<BR>&nbsp;<BR>i am Lucy Martine, in progress and&nbsp; difficulties, i'm using this very long needed opportunity to write to you once more. May i also know from you the academics works and health.</DIV>  <DIV>Please i want you to assiste me transfer my money to your account, my father deposited the money in the bank here africa&nbsp;before his suden death, when my father was in the hospital he called me and relese this information to me as the only daughter, the amount is $9.5 millions usa dollars.<BR>&nbsp;<BR>&nbsp;Please contact me with my email address for more detail (<A
 href="mailto:lucy_martine20@yahoo.fr">lucy_martine20@yahoo.fr</A>)&nbsp;&nbsp;&nbsp; </DIV>  <DIV>Thanks<BR>Lucy Martine</DIV>(&nbsp;<A href="mailto:lucy_martine20@yahoo.fr">lucy_martine20@yahoo.fr</A><FONT color=#003399> </FONT>)</DIV>  <DIV>&nbsp;</DIV>  <DIV>&nbsp;</DIV>  <DIV>&nbsp;</DIV><p> __________________________________________________<br>Do You Yahoo!?<br>En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités <br>http://mail.yahoo.fr Yahoo! Mail <p>&#32;__________________________________________________<br>Do You Yahoo!?<br>En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités <br>http://mail.yahoo.fr Yahoo! Mail 
--0-1453276933-1209935063=:56651--



From mpls-bounces@ietf.org  Mon May  5 06:11:58 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A4C03A682C;
	Mon,  5 May 2008 06:11:58 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BEB13A682C
	for <mpls@core3.amsl.com>; Mon,  5 May 2008 06:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.591
X-Spam-Level: 
X-Spam-Status: No, score=0.591 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1,
	SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vDi-+oHdbRSF for <mpls@core3.amsl.com>;
	Mon,  5 May 2008 06:11:56 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id A1D263A67F4
	for <mpls@ietf.org>; Mon,  5 May 2008 06:11:55 -0700 (PDT)
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 May 2008 15:11:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 May 2008 15:11:32 +0200
Message-ID: <5A0FF108221C7C4E85738678804B567C06215F9E@ftrdmel3>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
Thread-Index: AciOt90U0PeFnVFrRKeagc1XHaD+UwAc0cPwAVfDT1ACYYyg0AN4p2GAAK87/HA=
References: <DD7E9F364F33B54881C225192D4872D73D8AA8@xmb-rtp-211.amer.cisco.com>
From: <bruno.decraene@orange-ftgroup.com>
To: <lufang@cisco.com>
X-OriginalArrivalTime: 05 May 2008 13:11:33.0630 (UTC)
	FILETIME=[8A8251E0:01C8AEB1]
Cc: loa@pi.se, mpls@ietf.org
Subject: Re: [mpls] wg last call on draft-ietf-mpls-ldp-igp-sync-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Luyuan,

[snipped]

> > So could the draft just list (or reference a document
> > describing) multicast issues with IGP asymmetric cost? =

> > Otherwise, as a service provider proving IP, MPLS VPN and multicast on =

> > the same AS, while LDP end-of-LIB is not available, I wonder if I =

> > should use this draft or not as the draft says it improves MPLS VPN =

> > availability but could create issues with multicast.
 =

> I have checked with several Multicast experts. The conclusion is that =

> IGP asymmetric link cost does not cause problems for multicast. So we wil=
l remove that line.

Thanks for having checked and settled that point.

Regards,
Bruno

> De=A0: Luyuan Fang (lufang) [mailto:lufang@cisco.com]
> =

> Bruno,
> =

> Thanks for the discussion again. Please see in-line.
> Luyuan
> =

> > -----Original Message-----
> > From: bruno.decraene@orange-ftgroup.com
> > [mailto:bruno.decraene@orange-ftgroup.com]
> > Sent: 14 April 2008 06:18
> > To: Luyuan Fang (lufang)
> > Cc: loa@pi.se; mpls@ietf.org
> > Subject: RE: [mpls] wg last call on
> > draft-ietf-mpls-ldp-igp-sync-01.txt
> >
> > Hi Luyuan,
> >
> > Thanks for your detailed answers.
> > More in-line.
> >
> > Bruno
> >
> > > De=A0: Luyuan Fang (lufang) [mailto:lufang@cisco.com]
> > >
> > > Hi Bruno,
> > >
> > > Thank you for the comments. Please see in-line.
> > >
> > > > -----Original Message-----
> > > >
> > > > Hi Markus, Alia, Luyuan, all,
> > > >
> > > > A few comments:
> > > >
> > > > 1) May be the document should talk about its interaction with
> > > > graceful restart. (I guess this document should not be
> > used when GR
> > > > is used, unless GR is aborted or failed.).
> > > >
> > >
> > > Very good point. Let's try to look the relationship between LDP-IGP
> > > synch (LDP-IGP) and Graceful Restart (GR). In fact, LDP-IGP is also
> > > used when GR is used.
> > >
> > > There are LDP GR [RFC 3478] and IGP GR - OSPF GR [RFC 3623]
> > and ISIS
> > > GR [RFC 3847].
> > >
> > > A. LDP GR and LDP-IGP synch:
> > >
> > > LDP GR provides a mechanism to minimize the impact on MPLS labeled
> > > traffic caused by LSR's control plane restart. LDP GR is taking the
> > > proactive approach.
> > >
> > > LDP-IGP synch is reactive, it provides the exchange and
> > synch action
> > > between LDP and IGP when LDP is already failed. It prevents router
> > > sending traffic to the path where IGP is up and LDP is down.
> > >
> > > There are many occasions you don't have a chance to
> > gracefully restart.
> > > E.g. bring up a new link; operational error - missed to
> > configure LDP;
> > > implementation error causes label corruption, etc.
> > >
> > > Both LDP GR and LDP-IGP synch provide labeled traffic
> > protection under
> > > different conditions.
> >
> > Agreed: both GR and LDP-IGP sync have value and can be
> > enabled on the same router at the same time.
> >
> > My point was that for a given failure, only one of mechanism
> > should take care of the failure. So if GR handle the failure,
> > eg LDP session failure, LDP-IGP sync should not change the
> > IGP link cost.
> >
> > > B. IGP GR and LDP-IGP synch
> > >
> > > IGP GR or non-stop forwarding (NSF) is to keep IGP router
> > stay on the
> > > forwarding path even as its IGP is restarted.
> > >
> > > An IGP instance performing NSF should honor the LDP-IGP synch
> > > procedure to check the LDP-IGP synch parameter on the
> > standby routing device.
> >
> > Do you mean: what should we do if between two neighbor
> > routers, IGP GR is working but is still underway while LDP GR failed?
> > I didn't think of this specific interaction but the subject
> > of interaction between IGP and LDP GR procedures seems broad.
> > I don't have detailed knowledge of IS-IS GR, but in general
> > to stay in the safe area, it seems that the IGP topology
> > should not change during the IGP GR procedure. So in this
> > case, what should be the LDP-IGP sync behavior?
> >
> > Note that these GR interactions are not specific to the
> > IGP-LDP sync draft. Eg: what should we do if IGP GR succeed
> > and BGP GR failed? (for a node proving connectivity between
> > two ASBRs of the same AS where tunneling (MPLS or IP) is not used).
> >
> > so we can probably keep this out of this draft
> >
> > > IGP GR protects traffic during the switch over. LDP-IGP protects
> > > labeled traffic from being blackholed when LDP is faulty for some
> > > reason while IGP is still up.
> > >
> > > >
> > > > 2) " While the link could still be used for IP
> > forwarding, it is not
> > > > useful for traffic with packets carrying a label stack of
> > more than
> > > > one label or when the IP  address carried in the packet is out of
> > > > the
> > > > RFC1918 space."
> > > >
> > > > It seems that the use of RFC 1918 IP address is just an
> > example. One
> > > > could find others (eg BGP free core).
> > > > Proposition to change to " While the link could still be
> > used for IP
> > > > forwarding, it is not useful for MPLS forwarding (e.g.
> > > > MPLS VPN, BGP free core.)"
> > > >
> > >
> > > Agreed. We can used both examples.
> > >
> > > How about we say "While the link could still be used for IP
> > > forwarding, it is not useful for MPLS forwarding, e.g.,
> > MPLS VPN; BGP
> > > route free core; IP address carried in the packet is out of the
> > > RFC1918 space, etc."?
> >
> > Fine, thanks.
> >
> > > >
> > > > 3) "The LDP protocol itself has currently no means to
> > indicate to a
> > > > service depending on it whether there is an uninterrupted label
> > > > switched path available to the desired destination or not."
> > > >
> > > > Eventually, it could be useful to say why LDP ordered mode + FEC
> > > > withdraw is not an existing mean.
> > >
> > > LDP is not a routing protocol. IGP directs the traffic to
> > the shortest
> > > path regardless there is an established LSP along the path or not.
> > > Under the LDP down and IGP up condition: When LDP Ordered
> > Control is
> > > used, the labeled packets drop happens at the LSR of the ingress of
> > > network as LSP cannot be established on the shortest path
> > selected by
> > > IGP; When Independent Control is used, the labeled packets drop
> > > happens at the LSR where LDP failed (could be a mid point
> > in the LSP) as the LSP is broken.
> > > We have seen both blackholing cases in live networks. For
> > more details
> > > on LDP blackholing problems and solution, also see "LDP Failure
> > > Detection and Recovery", by L. Fang, A. Atlas, F. Chiussi, K.
> > > Kompella, and G. Swallow, IEEE Communications Vol.42 No.10,
> > October 2004.
> > >
> > > > Or may be you want to say that LDP has currently no way
> > to correct
> > > > the issue, for example by using a different IGP path.
> > > >
> > >
> > > Yes, thanks. We can re-word this similar as you suggested: LDP has
> > > currently no way to correct the issue. LDP is not a routing
> > protocol,
> > > it cannot re-direct traffic to an alternate IGP path.
> >
> > Fine, thanks.
> >
> > >
> > > > 4) "In the case of OSPF this cost is LSInfinity (16-bit value
> > > > 0xFFFF) as proposed in [RFC3137]."
> > > >
> > > > Could you also indicate the metric to use for IS-IS?
> > > > Especially since:
> > > > - further in the doc you recommend that all
> > implementation use the
> > > > same metric to avoid asymmetric link cost
> > > > - RFC 3784 seems to indicate that the max metric link (2^24 -
> > > > 1) is already reserved
> > > >
> > >
> > > Very good point.
> > > We shall add the ISIS max metric in the draft. The max metric value
> > > for ISIS using wide metrics is 0xFFFFFE per RFC 3784.
> >
> > Thanks.
> >
> > >
> > > > 5) "It is recommended that both sides of a link implement this
> > > > mechanism to be effective and to avoid asymmetric link
> > costs which
> > > > could cause problems with IP multicast forwarding."
> > > >
> > > > Avoiding asymetric link cost during all the procedure
> > would require
> > > > that both routers sharing the LDP session have the same way to
> > > > detect when "LDP is considered fully operational". This
> > is currently
> > > > not the case.
> > >
> > > Understood. It is a recommendation for better performance, not a
> > > requirement.
> > >
> > > > As the document propose to wait "some time", the document could
> > > > possibly propose a default value for this timer and warn
> > that if the
> > > > operator wish to change that value, it should change it
> > on both side
> > > > of the LDP session.
> > > >
> > >
> > > We prefer not to set the hold-down timer with a default value. The
> > > reason is that the LIB tables size can vary largely, as well the
> > > equipment capability/speed. If the default value is too small, this
> > > function would not work; if it is too big, it slows down the
> > > convergence time. But the hold-down time guidelines through
> > equipment
> > > testing would be helpful.
> >
> > You're right but this discussion could apply to lot of
> > default timers. Eg GR timers. Yet most specification defines
> > default values for their timers.
> >
> > > LDP End-of-LIB (draft-asati-mpls-ldp-end-of-lib-01.txt) is
> > currently a
> > > work in progress. When End-of-LIB is implemented, it can signal the
> > > end of IGP hold-down time, no longer need for the configured nor
> > > default timers.
> >
> > OK, given this, I guess it's not a big deal not to define
> > default value for the timers. May be the document could say
> > that such LDP sync mechanism (LDP End of LIB) should
> > preferably be used (over timers) once they are available. (in
> > order to avoid asymmetric routing)
> >
> Agreed, we planned to mention LDP End of LIB work.
> =

> > > > Also, as there is a risk of transient asymetric link cost
> > (because
> > > > the end of the procedure is not stricly defined) could
> > you possibly
> > > > provide more precision on the problems that could be faced by IP
> > > > multicast?
> > > >
> > >
> > > Yes, transient asymmetric cost is always a risk, it is not just for
> > > this problem, it is rather a common problem. e.g. it is same as in
> > > BGP. We would treat it as out of scope for this draft.
> >
> > Ok but this document:
> > - Specifically states that asymmetric links cost could cause
> > problem with multicast ("asymmetric link costs [which] could
> > cause problems with IP multicast forwarding")
> > - In the short term (waiting for LDP end-of-LIB) does not
> > fully avoid asymmetric link cost. Quite the contrary,
> > compared to doing nothing, it creates new opportunity for this.
> >
> > So could the draft just list (or reference a document
> > describing) multicast issues with IGP asymmetric cost?
> > Otherwise, as a service provider proving IP, MPLS VPN and
> > multicast on the same AS, while LDP end-of-LIB is not
> > available, I wonder if I should use this draft or not as the
> > draft says it improves MPLS VPN availability but could create
> > issues with multicast.
> >
> I have checked with several Multicast experts. The conclusion is that IGP=
 asymmetric link cost does
> not cause
> problems for multicast. So we will remove that line.
> =

> > > > Thanks,
> > > > Regards,
> > > > Bruno
> > > >
> > >
> > > Thanks,
> > > Luyuan
> > >
> > >
> > > > > From Loa Andersson
> > > > >
> > > > > Working group,
> > > > >
> > > > > this is to initiate a two week working group last call on:
> > > > >
> > > > > draft-ietf-mpls-ldp-igp-sync-01.txt
> > > > >
> > > > > Please send your comments to the working group mailing list
> > > > or to the
> > > > > working group chairs before April 11.
> > > > >
> > > > > 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@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/mpls
> > > > _______________________________________________
> > > > mpls mailing list
> > > > mpls@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mpls
> > > >
> >
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon May  5 13:02:16 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F3A63A6C94;
	Mon,  5 May 2008 13:02:16 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FEED3A6C94
	for <mpls@core3.amsl.com>; Mon,  5 May 2008 13:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.205
X-Spam-Level: 
X-Spam-Status: No, score=-5.205 tagged_above=-999 required=5
	tests=[AWL=-0.095, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JGf69cb2ohML for <mpls@core3.amsl.com>;
	Mon,  5 May 2008 13:02:14 -0700 (PDT)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.141])
	by core3.amsl.com (Postfix) with ESMTP id ADB0D28C1A8
	for <mpls@ietf.org>; Mon,  5 May 2008 13:02:13 -0700 (PDT)
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e1.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id m45K2CQw018135
	for <mpls@ietf.org>; Mon, 5 May 2008 16:02:12 -0400
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id
	m45K2B1N248600 for <mpls@ietf.org>; Mon, 5 May 2008 16:02:11 -0400
Received: from d01av05.pok.ibm.com (loopback [127.0.0.1])
	by d01av05.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	m45K2BSC001109 for <mpls@ietf.org>; Mon, 5 May 2008 16:02:11 -0400
Received: from d01ml263.pok.ibm.com (d01ml263.pok.ibm.com [9.56.227.113])
	by d01av05.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	m45K2BP6001086 for <mpls@ietf.org>; Mon, 5 May 2008 16:02:11 -0400
From: Andrew Veitch <aveitch@us.ibm.com>
To: mpls@ietf.org
Message-ID: <OF0FBBA91D.D8C90208-ON85257440.006E1020-85257440.006E1021@us.ibm.com>
Date: Mon, 5 May 2008 16:02:10 -0400
X-MIMETrack: Serialize by Router on D01ML263/01/M/IBM(Release 7.0.2FP2HF300 |
	September 14, 2007) at 05/05/2008 16:02:11
MIME-Version: 1.0
Subject: [mpls] Veitch, Andrew is out of the office.
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


I will be out of the office starting  05/04/2008 and will not return until
05/12/2008.

I will be traveling for business and will have limited Internet and email
access, though I will be checking it daily.

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


From mpls-bounces@ietf.org  Mon May  5 15:09:05 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AED543A6870;
	Mon,  5 May 2008 15:09:05 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A50093A6870
	for <mpls@core3.amsl.com>; Mon,  5 May 2008 15:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SoMkozy8RuII for <mpls@core3.amsl.com>;
	Mon,  5 May 2008 15:09:02 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 9E0E03A67EA
	for <mpls@ietf.org>; Mon,  5 May 2008 15:08:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,439,1204520400"; 
   d="scan'208";a="7284811"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 05 May 2008 18:08:57 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m45M8vwO016598; 
	Mon, 5 May 2008 18:08:57 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m45M8uAD023716;
	Mon, 5 May 2008 22:08:57 GMT
Received: from xmb-rtp-206.amer.cisco.com ([64.102.31.32]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 May 2008 18:08:56 -0400
Received: from 10.82.249.181 ([10.82.249.181]) by xmb-rtp-206.amer.cisco.com
	([64.102.31.32]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  5 May 2008 22:08:56 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 05 May 2008 18:08:55 -0400
From: George Swallow <swallow@cisco.com>
To: <mpls@ietf.org>
Message-ID: <C444FDB7.22B7%swallow@cisco.com>
Thread-Topic: Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZg==
Mime-version: 1.0
X-OriginalArrivalTime: 05 May 2008 22:08:56.0924 (UTC)
	FILETIME=[9D0289C0:01C8AEFC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=618; t=1210025337; x=1210889337;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:=20George=20Swallow=20<swallow@cisco.com>
	|Subject:=20Poll=20for=20draft=20on=20EXP=20Bits=20to=20WG=
	20draft |Sender:=20 |To:=20<mpls@ietf.org>;
	bh=xAcoWwV+i5ER75S24VLgQsuIEy7j9MphZw0Fl3JUCnM=;
	b=puSxGhQ1WBgHv11992amYKhbdjtoOEi0KTg2QIyxLmuFgoqBLtDVN7Yw9S
	TvLTSs+hXW2efY4rMt9X5/6QBTv2fsju1jeanYJoyc9u/8pWS7Hvw0V7bsPn
	ub18QOLv/1;
Authentication-Results: rtp-dkim-1; header.From=swallow@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This begins a one week poll to determine support for making

http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt

a WG doc.

As background, early in the MPLS work, these bits were always intend for
various uses as COS bits and other functions imbedded in the DS byte of the
IP header.  They were called experimental only in that, at the time the
encaps draft was written, there was no consensus on what to do with the
bits.

The term experimental has lead various people and SDOs to expect more
freedom in defining these bits than ever was intended.  This draft seeks to
correct that.

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


From mpls-bounces@ietf.org  Mon May  5 17:36:13 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C0F2A3A6C9A;
	Mon,  5 May 2008 17:36:13 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9E603A6C9A
	for <mpls@core3.amsl.com>; Mon,  5 May 2008 17:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RNcjLovg55fE for <mpls@core3.amsl.com>;
	Mon,  5 May 2008 17:36:11 -0700 (PDT)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237])
	by core3.amsl.com (Postfix) with ESMTP id D1D543A6B5C
	for <mpls@ietf.org>; Mon,  5 May 2008 17:36:10 -0700 (PDT)
Received: by wx-out-0506.google.com with SMTP id i29so393124wxd.31
	for <mpls@ietf.org>; Mon, 05 May 2008 17:36:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:x-mailer:date:to:from:subject:cc:in-reply-to:references:mime-version:content-type:sender:message-id;
	bh=dOipk1ha2hQPxtfcQpJFRWEiQetIocgQM6BIEX6UTdI=;
	b=C2eJSueD6G7qPNb02djwCgjsdjro2US5npTbQncA+Zeg1n3KHWKaM92OApWAqOhPmJgoYWK/G8ipN6zRxuW39bO8pch59BmYVOZmWi3cv5u9kD+d501n6wb2GxtLdhw3xS0Mx7qBpf8lNzBTeFivr6cGsxnzP0iRG90RhhVTSZk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=x-mailer:date:to:from:subject:cc:in-reply-to:references:mime-version:content-type:sender:message-id;
	b=ZGmveFfHd5OernpE+I8jqyFgJKh3beSCLUhZQ1GGnDm5kUA1BilpyTUZy5H/IVC3r8VgZi3eBU3ZpYXpRgPRmJjUNQ07W3o+TumplthfajJOAjjk5gyDrpEtfSD9M2BgN6RkFlGMl5/+zW0ENfmXMitzGn9Di0nW4luk6s5GHdM=
Received: by 10.70.11.10 with SMTP id 10mr163184wxk.37.1210034168872;
	Mon, 05 May 2008 17:36:08 -0700 (PDT)
Received: from AMALIS.gmail.com ( [72.93.228.141])
	by mx.google.com with ESMTPS id i13sm19433wxd.5.2008.05.05.17.36.07
	(version=SSLv3 cipher=RC4-MD5); Mon, 05 May 2008 17:36:08 -0700 (PDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 05 May 2008 20:36:04 -0400
To: George Swallow <swallow@cisco.com>
From: "Andrew G. Malis" <amalis@gmail.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
References: <C444FDB7.22B7%swallow@cisco.com>
Mime-Version: 1.0
Message-ID: <481fa7f7.0d87460a.398f.03f5@mx.google.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I am in favor of making this a WG draft.

Thanks,
Andy

At 5/5/2008 06:08 PM -0400, George Swallow wrote:
>This begins a one week poll to determine support for making
>
>http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
>a WG doc.
>
>As background, early in the MPLS work, these bits were always intend for
>various uses as COS bits and other functions imbedded in the DS byte of the
>IP header.  They were called experimental only in that, at the time the
>encaps draft was written, there was no consensus on what to do with the
>bits.
>
>The term experimental has lead various people and SDOs to expect more
>freedom in defining these bits than ever was intended.  This draft seeks to
>correct that.

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


From mpls-bounces@ietf.org  Mon May  5 19:04:18 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 890953A6EE8;
	Mon,  5 May 2008 19:04:18 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 422AA28C167
	for <mpls@core3.amsl.com>; Mon,  5 May 2008 19:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.569
X-Spam-Level: *
X-Spam-Status: No, score=1.569 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327,
	HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4vLSStb3m2AF for <mpls@core3.amsl.com>;
	Mon,  5 May 2008 19:04:16 -0700 (PDT)
Received: from mailipao.vtcif.telstra.com.au (mailipao.vtcif.telstra.com.au
	[202.12.144.27])
	by core3.amsl.com (Postfix) with ESMTP id 53AC33A68B7
	for <mpls@ietf.org>; Mon,  5 May 2008 19:04:14 -0700 (PDT)
Received: from maili.vtcif.telstra.com.au (HELO mailai.vtcif.telstra.com.au)
	([202.12.142.17])
	by mailipai.vtcif.telstra.com.au with ESMTP; 06 May 2008 12:04:11 +1000
Received: from mail.cdn.telstra.com.au (localhost [127.0.0.1])
	by mailai.vtcif.telstra.com.au (Postfix) with ESMTP id 690A21DA84;
	Tue,  6 May 2008 12:04:11 +1000 (EST)
Received: from wsmsg2902.srv.dir.telstra.com (wsmsg2902.srv.dir.telstra.com
	[172.49.40.51]) by mail.cdn.telstra.com.au (8.8.2/8.6.9) with
	ESMTP id MAA06956; Tue, 6 May 2008 12:04:11 +1000 (EST)
Received: from wsmsg2307.srv.dir.telstra.com ([172.49.40.44]) by
	wsmsg2902.srv.dir.telstra.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 12:04:10 +1000
Received: from WSMSG2156V.srv.dir.telstra.com ([192.74.195.32]) by
	wsmsg2307.srv.dir.telstra.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 6 May 2008 12:04:10 +1000
Received: from 147.10.17.26 ([147.10.17.26]) by WSMSG2156V.srv.dir.telstra.com
	([192.74.195.31]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue,  6 May 2008 02:04:08 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Tue, 06 May 2008 12:04:04 +1000
From: Ian Stanley <ian.b.stanley@team.telstra.com>
To: George Swallow <swallow@cisco.com>, <mpls@ietf.org>
Message-ID: <C445F9B5.20719%ian.b.stanley@team.telstra.com>
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZgAINmfx
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 06 May 2008 02:04:10.0005 (UTC)
	FILETIME=[790FCC50:01C8AF1D]
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1688152387=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1688152387==
Content-type: multipart/alternative;
	boundary="B_3292920245_796489"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3292920245_796489
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

I support this.

Cheers
ian


On 6/5/08 8:08 AM, "George Swallow" <swallow@cisco.com> wrote:George Swallow

> This begins a one week poll to determine support for making
> 
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
> 
> a WG doc.
> 
> As background, early in the MPLS work, these bits were always intend for
> various uses as COS bits and other functions imbedded in the DS byte of the
> IP header.  They were called experimental only in that, at the time the
> encaps draft was written, there was no consensus on what to do with the
> bits.
> 
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft seeks to
> correct that.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 


 
Regards,
Ian Stanley
Architecture Implementation
Network Technology | Engineering
02 9396 8508
0419 257221

This communication may contain CONFIDENTIAL or copyright information of
Telstra Corporation Limited (ABN 33 051 775 556). If you are not an intended
recipient, you MUST NOT keep, forward, copy, use, save or rely on this
communication, and any such action is unauthorised and prohibited. If you
have received this communication in error, please reply to this email to
notify the sender of its incorrect delivery, and then delete both it and
your reply. Thank you.
 


--B_3292920245_796489
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [mpls] Poll for draft on EXP Bits to WG draft</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Comic Sans MS, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-siz=
e:12.0px'>I support this.<BR>
<BR>
Cheers<BR>
ian<BR>
<BR>
<BR>
On 6/5/08 8:08 AM, &quot;George Swallow&quot; &lt;swallow@cisco.com&gt; wro=
te:George Swallow<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Comic Sans MS, Verdana, Helvetica, Ar=
ial"><SPAN STYLE=3D'font-size:12.0px'>This begins a one week poll to determine=
 support for making<BR>
<BR>
<a href=3D"http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.=
txt">http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt</=
a><BR>
<BR>
a WG doc.<BR>
<BR>
As background, early in the MPLS work, these bits were always intend for<BR=
>
various uses as COS bits and other functions imbedded in the DS byte of the=
<BR>
IP header. &nbsp;They were called experimental only in that, at the time th=
e<BR>
encaps draft was written, there was no consensus on what to do with the<BR>
bits.<BR>
<BR>
The term experimental has lead various people and SDOs to expect more<BR>
freedom in defining these bits than ever was intended. &nbsp;This draft see=
ks to<BR>
correct that.<BR>
<BR>
_______________________________________________<BR>
mpls mailing list<BR>
mpls@ietf.org<BR>
https://www.ietf.org/mailman/listinfo/mpls<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Comic Sans MS, Verdana, Helvetica, A=
rial"><SPAN STYLE=3D'font-size:12.0px'><BR>
<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdana, Helvetica=
, Arial"> <BR>
</FONT><FONT FACE=3D"Comic Sans MS, Verdana, Helvetica, Arial">Regards,<BR>
Ian Stanley<BR>
Architecture Implementation<BR>
Network Technology | Engineering<BR>
02 9396 8508<BR>
0419 257221<BR>
</FONT></SPAN><FONT FACE=3D"Comic Sans MS, Verdana, Helvetica, Arial"><FONT S=
IZE=3D"2"><SPAN STYLE=3D'font-size:10.0px'><BR>
This communication may contain CONFIDENTIAL or copyright information of Tel=
stra Corporation Limited (ABN 33 051 775 556). If you are not an intended re=
cipient, you MUST NOT keep, forward, copy, use, save or rely on this communi=
cation, and any such action is unauthorised and prohibited. If you have rece=
ived this communication in error, please reply to this email to notify the s=
ender of its incorrect delivery, and then delete both it and your reply. Tha=
nk you.<BR>
&nbsp;</SPAN></FONT><SPAN STYLE=3D'font-size:12.0px'><BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3292920245_796489--


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

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

--===============1688152387==--



From mpls-bounces@ietf.org  Mon May  5 23:35:48 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F3F2A3A6A51;
	Mon,  5 May 2008 23:35:47 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EAAB03A6A96
	for <mpls@core3.amsl.com>; Mon,  5 May 2008 23:35:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=1.600, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DMdCzUmBtCMh for <mpls@core3.amsl.com>;
	Mon,  5 May 2008 23:35:43 -0700 (PDT)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117])
	by core3.amsl.com (Postfix) with ESMTP id 6B9B828C3BF
	for <mpls@ietf.org>; Mon,  5 May 2008 23:35:42 -0700 (PDT)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44])
	by eci-iron1.ecitele.com with ESMTP; 06 May 2008 09:39:20 +0300
Received: from ILPTEXCH02.ecitele.com ([147.234.245.181]) by
	ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 6 May 2008 09:35:40 +0300
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by
	ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 6 May 2008
	09:35:39 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: George Swallow <swallow@cisco.com>
Date: Tue, 6 May 2008 09:35:38 +0300
Thread-Topic: Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZgARrkjg
Message-ID: <A3C5DF08D38B6049839A6F553B331C766B14D41F00@ILPTMAIL02.ecitele.com>
References: <C444FDB7.22B7%swallow@cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 06 May 2008 06:35:40.0292 (UTC)
	FILETIME=[66D45440:01C8AF43]
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

In favor.

Regards,
             Sasha

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf Of George Swallow
> Sent: Tuesday, May 06, 2008 1:09 AM
> To: mpls@ietf.org
> Subject: [mpls] Poll for draft on EXP Bits to WG draft
>
> This begins a one week poll to determine support for making
>
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
> a WG doc.
>
> As background, early in the MPLS work, these bits were always
> intend for
> various uses as COS bits and other functions imbedded in the
> DS byte of the
> IP header.  They were called experimental only in that, at
> the time the
> encaps draft was written, there was no consensus on what to
> do with the
> bits.
>
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This
> draft seeks to
> correct that.
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May  6 02:16:24 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ADAAF3A6BA4;
	Tue,  6 May 2008 02:16:24 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CACC83A68C6
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 02:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.650, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1D13csvyyfdh for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 02:16:22 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 7A4123A6822
	for <mpls@ietf.org>; Tue,  6 May 2008 02:16:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,443,1204498800"; 
   d="scan'208";a="8111467"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 06 May 2008 11:16:18 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m469GJL4022118
	for <mpls@ietf.org>; Tue, 6 May 2008 11:16:19 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m469GIbv015344
	for <mpls@ietf.org>; Tue, 6 May 2008 09:16:18 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 11:16:18 +0200
Received: from [144.254.53.136] ([144.254.53.136]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 11:16:18 +0200
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
References: <C444FDB7.22B7%swallow@cisco.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <9BBE6947-02A6-4012-8895-200BB5804FDB@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Tue, 6 May 2008 11:16:15 +0200
To: George Swallow <swallow@cisco.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 06 May 2008 09:16:18.0645 (UTC)
	FILETIME=[D7BC4850:01C8AF59]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1581; t=1210065379;
	x=1210929379; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[mpls]=20Poll=20for=20draft=20on=20EXP=
	20Bits=20to=20WG=20draft |Sender:=20;
	bh=5ijbYhAxne2vnnMFC9WOVOWRALx2wm2z/Wk3tl1jqro=;
	b=DTDjjiuWHHOz7rU7JmRac/TSJPTJDDOFTwEEaRWiN9FStlTZ5EWv00vNUU
	jCmvu66YvMf1p1eXHr9A1+Wa/TQ/XGoF9LmfdjG4BuXF51YlmbDQptSTGv8f
	FaP8TfFzAM;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: mpls@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hello,

I am in favor of renaming the "EXP" field.

A couple of small points:
	* draft-andersson uses "EXP bits" and "EXP field" and also uses "CoS  
bits". For its Diffserv and ECN usage, this field is not structured  
in bits and instead used as a set of codepoints. So I recommend the  
document refers to the old field as the "EXP field" (and not "EXP  
bits") and define a new name as "CoS field" (and not the "CoS bits").  
RFC3270 and RFC5129 already use "EXP field".
	* draft-andersson proposes the name of "CoS" for the field. This  
captures reasonably well its Diffserv usage, but probably not so well  
its ECN usage. We should be able to come up with a name that captures  
both.

Francois


On 6 May 2008, at 00:08, George Swallow wrote:

> This begins a one week poll to determine support for making
>
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
> a WG doc.
>
> As background, early in the MPLS work, these bits were always  
> intend for
> various uses as COS bits and other functions imbedded in the DS  
> byte of the
> IP header.  They were called experimental only in that, at the time  
> the
> encaps draft was written, there was no consensus on what to do with  
> the
> bits.
>
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft  
> seeks to
> correct that.
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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


From mpls-bounces@ietf.org  Tue May  6 03:59:57 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B201F3A6DEF;
	Tue,  6 May 2008 03:59:57 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5F5D3A6E1A
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 03:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ibH+SFmvR8BR for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 03:59:56 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id B2DCF3A67B6
	for <mpls@ietf.org>; Tue,  6 May 2008 03:59:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; 
   d="scan'208";a="7434474"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 06 May 2008 06:59:51 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m46AxpKE001129
	for <mpls@ietf.org>; Tue, 6 May 2008 06:59:51 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m46AxpSc007571
	for <mpls@ietf.org>; Tue, 6 May 2008 10:59:51 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 06:59:51 -0400
Received: from sbrim-mbp.local ([10.86.248.58]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 06:59:50 -0400
Message-ID: <48203A26.60504@employees.org>
Date: Tue, 06 May 2008 06:59:50 -0400
From: Scott Brim <swb@employees.org>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
References: <C444FDB7.22B7%swallow@cisco.com>
	<9BBE6947-02A6-4012-8895-200BB5804FDB@cisco.com>
In-Reply-To: <9BBE6947-02A6-4012-8895-200BB5804FDB@cisco.com>
X-OriginalArrivalTime: 06 May 2008 10:59:51.0352 (UTC)
	FILETIME=[4ECC2380:01C8AF68]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

On 5/6/08 5:16 AM, Francois Le Faucheur IMAP allegedly wrote:
> Hello,
> 
> I am in favor of renaming the "EXP" field.
> 
> A couple of small points:
> 	* draft-andersson uses "EXP bits" and "EXP field" and also uses "CoS  
> bits". For its Diffserv and ECN usage, this field is not structured  
> in bits and instead used as a set of codepoints. So I recommend the  
> document refers to the old field as the "EXP field" (and not "EXP  
> bits") and define a new name as "CoS field" (and not the "CoS bits").  
> RFC3270 and RFC5129 already use "EXP field".
> 	* draft-andersson proposes the name of "CoS" for the field. This  
> captures reasonably well its Diffserv usage, but probably not so well  
> its ECN usage. We should be able to come up with a name that captures  
> both.
> 
> Francois

"CoS" also seems inadequate to me because (1) it's already been heavily 
used to mean less than we need to mean here, so it will confuse readers, 
and (2) "service" implies something about end-to-end service which is 
more than we want to mean.

So now I'm obligated to suggest an alternative :-).  To include ECN and 
PHB/PSC treatments, perhaps the name could be "Congestion Handling 
Indication", or simply "Per-Hop Treatment Indication"?

swb
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May  6 04:51:37 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5FCD23A6BF1;
	Tue,  6 May 2008 04:51:37 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6616D3A6CF2
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 04:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id anqEePc8SQHU for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 04:51:28 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 82C543A6BF1
	for <mpls@ietf.org>; Tue,  6 May 2008 04:51:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,443,1204498800"; 
   d="scan'208";a="8134144"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 06 May 2008 13:51:08 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m46Bp86C013659; 
	Tue, 6 May 2008 13:51:08 +0200
Received: from dhcp-gpk02-vlan300-64-103-65-45.cisco.com
	(dhcp-gpk02-vlan300-64-103-65-45.cisco.com [64.103.65.45])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m46Bp8Sg026385;
	Tue, 6 May 2008 11:51:08 GMT
Message-ID: <4820462C.5050402@cisco.com>
Date: Tue, 06 May 2008 12:51:08 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: George Swallow <swallow@cisco.com>
References: <C444FDB7.22B7%swallow@cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=244; t=1210074668; x=1210938668;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20Poll=20for=20draft=20on=20EXP=
	20Bits=20to=20WG=20draft |Sender:=20;
	bh=RDXaEUjqD72RhT85KGPKJ2TJaUcjRINlMpm3MB0Xuns=;
	b=g6H2BlCnL8gGu09ZdsO5L3FByEkk+SZxrAfCIl3Sat+H8WI+XT/Lx4nfKZ
	MWfPREA3OLzGGwEHjXNJjy+QBrgPrKTCsCKGxvZuKoAzZgOuJhnSX+bmxzrc
	u3AMymheP8;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

George Swallow wrote:
> This begins a one week poll to determine support for making
>
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
> a WG doc.
>
>   
I support this draft becoming a WG document.

Stewart
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May  6 05:16:01 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8982C3A6B40;
	Tue,  6 May 2008 05:16:01 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C24173A6815
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 05:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id X3EOee52Lu03 for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 05:15:58 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id DAE773A6C22
	for <mpls@ietf.org>; Tue,  6 May 2008 05:15:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; 
   d="scan'208";a="7434220"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 06 May 2008 08:15:51 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m46CFpbH001667
	for <mpls@ietf.org>; Tue, 6 May 2008 08:15:51 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m46CFpAL009257
	for <mpls@ietf.org>; Tue, 6 May 2008 12:15:51 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 08:15:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 08:15:51 -0400
Message-ID: <DD7E9F364F33B54881C225192D4872D73D8AD6@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZgAdgXLw
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "George Swallow (swallow)" <swallow@cisco.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 06 May 2008 12:15:51.0515 (UTC)
	FILETIME=[ECDDCAB0:01C8AF72]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=999; t=1210076151; x=1210940151;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lufang@cisco.com;
	z=From:=20=22Luyuan=20Fang=20(lufang)=22=20<lufang@cisco.com >
	|Subject:=20RE=3A=20[mpls]=20Poll=20for=20draft=20on=20EXP=
	20Bits=20to=20WG=20draft |Sender:=20
	|To:=20=22George=20Swallow=20(swallow)=22=20<swallow@cisco.
	com>,=20<mpls@ietf.org>;
	bh=y097nTEWzfU/s2Ntf5v+CV6rE7Nto/au0ZRXNqcMQsU=;
	b=odXaONRM9MGvIhcEdKNtSTdT6STxxX1MIWPAMoJt63QQFKdjnpkBc9bNxC
	kerlh1DKCWBC6pRD/5r6vVrY3xWpZ3cq7qjIi0VwuB+8EcAsPE6jXcbqvSOc
	nd/4gKpFrb;
Authentication-Results: rtp-dkim-2; header.From=lufang@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.
Luyuan 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
George Swallow (swallow)
Sent: 05 May 2008 18:09
To: mpls@ietf.org
Subject: [mpls] Poll for draft on EXP Bits to WG draft

This begins a one week poll to determine support for making

http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt

a WG doc.

As background, early in the MPLS work, these bits were always intend for
various uses as COS bits and other functions imbedded in the DS byte of
the IP header.  They were called experimental only in that, at the time
the encaps draft was written, there was no consensus on what to do with
the bits.

The term experimental has lead various people and SDOs to expect more
freedom in defining these bits than ever was intended.  This draft seeks
to correct that.

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


From mpls-bounces@ietf.org  Tue May  6 05:44:30 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 883793A6AA6;
	Tue,  6 May 2008 05:44:30 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6EE223A6AA4
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 05:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s1aJIjgGz7Ge for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 05:44:28 -0700 (PDT)
Received: from a2s13.a2hosting.com (a2s13.a2hosting.com [69.39.88.160])
	by core3.amsl.com (Postfix) with ESMTP id 8E29B3A69C9
	for <mpls@ietf.org>; Tue,  6 May 2008 05:44:28 -0700 (PDT)
Received: from adsl-76-208-19-162.dsl.sbndin.sbcglobal.net ([76.208.19.162]
	helo=[192.168.1.100])
	by a2s13.a2hosting.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.68) (envelope-from <johnkenney@alumni.nd.edu>)
	id 1JtMWf-0001iL-Oe; Tue, 06 May 2008 08:44:09 -0400
Message-ID: <482052A6.7080603@alumni.nd.edu>
Date: Tue, 06 May 2008 05:44:22 -0700
From: John Kenney <johnkenney@alumni.nd.edu>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>
References: <C444FDB7.22B7%swallow@cisco.com>	<9BBE6947-02A6-4012-8895-200BB5804FDB@cisco.com>
	<48203A26.60504@employees.org>
In-Reply-To: <48203A26.60504@employees.org>
X-Enigmail-Version: 0.95.6
X-A2hosting-MailScanner-Information: Please contact the ISP for more
	information
X-MailScanner-ID: 1JtMWf-0001iL-Oe
X-A2hosting-MailScanner: Not scanned: please contact your Internet E-Mail
	Service Provider for details
X-A2hosting-MailScanner-SpamCheck: 
X-A2hosting-MailScanner-From: johnkenney@alumni.nd.edu
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - a2s13.a2hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - alumni.nd.edu
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: mpls@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I agree with Francois and Scott that CoS is too narrow and carries the 
baggage of "service."  I suggest "Traffic Management" field.  Scheduling 
class, drop priority, and congestion notification are all aspects of 
traffic management.  The term traffic management has about the right 
scope; it is broad enough to cover the current usages with the 
additional flexibility contemplated in section 3, but it is narrow 
enough to convey real meaning.

I also support using "field" consistently instead of "bits."

I support making this a WG draft.

John Kenney


Scott Brim wrote:
> On 5/6/08 5:16 AM, Francois Le Faucheur IMAP allegedly wrote:
>   
>> Hello,
>>
>> I am in favor of renaming the "EXP" field.
>>
>> A couple of small points:
>> 	* draft-andersson uses "EXP bits" and "EXP field" and also uses "CoS  
>> bits". For its Diffserv and ECN usage, this field is not structured  
>> in bits and instead used as a set of codepoints. So I recommend the  
>> document refers to the old field as the "EXP field" (and not "EXP  
>> bits") and define a new name as "CoS field" (and not the "CoS bits").  
>> RFC3270 and RFC5129 already use "EXP field".
>> 	* draft-andersson proposes the name of "CoS" for the field. This  
>> captures reasonably well its Diffserv usage, but probably not so well  
>> its ECN usage. We should be able to come up with a name that captures  
>> both.
>>
>> Francois
>>     
>
> "CoS" also seems inadequate to me because (1) it's already been heavily 
> used to mean less than we need to mean here, so it will confuse readers, 
> and (2) "service" implies something about end-to-end service which is 
> more than we want to mean.
>
> So now I'm obligated to suggest an alternative :-).  To include ECN and 
> PHB/PSC treatments, perhaps the name could be "Congestion Handling 
> Indication", or simply "Per-Hop Treatment Indication"?
>
> swb
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>   
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May  6 06:18:26 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58F993A6A37;
	Tue,  6 May 2008 06:18:26 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A2813A6937
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 06:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eZBxQMG0tzwz for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 06:18:24 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	by core3.amsl.com (Postfix) with ESMTP id 62B743A6A37
	for <mpls@ietf.org>; Tue,  6 May 2008 06:18:24 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m46DIEcZ026720;
	Tue, 6 May 2008 08:18:15 -0500
Received: from eusrcmw720.eamcs.ericsson.se ([138.85.77.20]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 08:18:15 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 08:18:13 -0500
Message-ID: <8ECB099B6E0A044695BD93961F34988207111370@eusrcmw720.eamcs.ericsson.se>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZgAb/3Gw
References: <C444FDB7.22B7%swallow@cisco.com>
From: "David Sinicrope" <david.sinicrope@ericsson.com>
To: "George Swallow" <swallow@cisco.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 06 May 2008 13:18:15.0044 (UTC)
	FILETIME=[A42EFC40:01C8AF7B]
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I'm in favor of making this a working group draft.
-David 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
George Swallow
Sent: Monday, May 05, 2008 6:09 PM
To: mpls@ietf.org
Subject: [mpls] Poll for draft on EXP Bits to WG draft

This begins a one week poll to determine support for making

http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt

a WG doc.

As background, early in the MPLS work, these bits were always intend for
various uses as COS bits and other functions imbedded in the DS byte of
the IP header.  They were called experimental only in that, at the time
the encaps draft was written, there was no consensus on what to do with
the bits.

The term experimental has lead various people and SDOs to expect more
freedom in defining these bits than ever was intended.  This draft seeks
to correct that.

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


From mpls-bounces@ietf.org  Tue May  6 06:33:41 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95F913A6B15;
	Tue,  6 May 2008 06:33:41 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CFAB628C3C5
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 06:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j-7AMXyQ5vS8 for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 06:33:31 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34])
	by core3.amsl.com (Postfix) with ESMTP id B161D28C3DB
	for <mpls@ietf.org>; Tue,  6 May 2008 06:33:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by lucidvision.com (Postfix) with ESMTP id D4DA5355319;
	Tue,  6 May 2008 09:34:08 -0400 (EDT)
Received: from lucidvision.com ([127.0.0.1])
	by localhost (localhost [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP
	id 12124-10; Tue,  6 May 2008 09:33:50 -0400 (EDT)
Received: from [192.168.1.120] (static-72-71-250-36.cncdnh.fios.verizon.net
	[72.71.250.36])
	by lucidvision.com (Postfix) with ESMTP id E1613355307;
	Tue,  6 May 2008 09:33:50 -0400 (EDT)
Message-Id: <2857C30D-0A25-4B3F-84C6-1D7823474F2E@lucidvision.com>
From: Thomas Nadeau <tnadeau@lucidvision.com>
To: George Swallow <swallow@cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 09:32:54 -0400
References: <C444FDB7.22B7%swallow@cisco.com>
X-Mailer: Apple Mail (2.919.2)
X-Virus-Scanned: by amavisd-new at lucidvision.com
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.


On May 5, 2008, at 6:08 PM, George Swallow wrote:

> This begins a one week poll to determine support for making
>
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
> a WG doc.
>
> As background, early in the MPLS work, these bits were always intend  
> for
> various uses as COS bits and other functions imbedded in the DS byte  
> of the
> IP header.  They were called experimental only in that, at the time  
> the
> encaps draft was written, there was no consensus on what to do with  
> the
> bits.
>
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft  
> seeks to
> correct that.
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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


From mpls-bounces@ietf.org  Tue May  6 07:29:36 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 535CB3A6DFE;
	Tue,  6 May 2008 07:29:36 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9B833A6AD3
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 07:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jf9-quafsLCV for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 07:29:31 -0700 (PDT)
Received: from chip3og61.obsmtp.com (chip3og61.obsmtp.com [64.18.14.187])
	by core3.amsl.com (Postfix) with ESMTP id 32A5F3A6E4B
	for <mpls@ietf.org>; Tue,  6 May 2008 07:29:31 -0700 (PDT)
Received: from source ([66.129.224.36]) by chip3ob61.postini.com
	([64.18.6.12]) with SMTP; Tue, 06 May 2008 07:28:59 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 6 May 2008 07:29:10 -0700
Received: from [172.23.1.97] ([172.23.1.97] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 10:29:08 -0400
Message-ID: <48206B30.4000508@juniper.net>
Date: Tue, 06 May 2008 10:29:04 -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: George Swallow <swallow@cisco.com>
References: <C444FDB7.22B7%swallow@cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
X-Enigmail-Version: 0.93.0.0
X-OriginalArrivalTime: 06 May 2008 14:29:08.0857 (UTC)
	FILETIME=[8BA75690:01C8AF85]
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

support

George Swallow wrote:
> This begins a one week poll to determine support for making
> 
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
> 
> a WG doc.
> 
> As background, early in the MPLS work, these bits were always intend for
> various uses as COS bits and other functions imbedded in the DS byte of the
> IP header.  They were called experimental only in that, at the time the
> encaps draft was written, there was no consensus on what to do with the
> bits.
> 
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft seeks to
> correct that.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May  6 07:36:31 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1C233A69B6;
	Tue,  6 May 2008 07:36:30 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6BFF3A69B6
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 07:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NtfXzBSr57Bi for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 07:36:28 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 3DDF528C1B6
	for <mpls@ietf.org>; Tue,  6 May 2008 07:36:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; 
   d="scan'208";a="7460303"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 06 May 2008 10:36:01 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m46Ea1Ab002295
	for <mpls@ietf.org>; Tue, 6 May 2008 10:36:01 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m46Ea16p027621
	for <mpls@ietf.org>; Tue, 6 May 2008 14:36:01 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 10:35:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 10:34:32 -0400
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B0706652DB3@xmb-rtp-203.amer.cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZgAiaC7Q
References: <C444FDB7.22B7%swallow@cisco.com>
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "George Swallow (swallow)" <swallow@cisco.com>, <mpls@ietf.org>
X-OriginalArrivalTime: 06 May 2008 14:35:13.0683 (UTC)
	FILETIME=[651B5E30:01C8AF86]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1130; t=1210084561;
	x=1210948561; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zali@cisco.com;
	z=From:=20=22Zafar=20Ali=20(zali)=22=20<zali@cisco.com>
	|Subject:=20RE=3A=20[mpls]=20Poll=20for=20draft=20on=20EXP=
	20Bits=20to=20WG=20draft |Sender:=20
	|To:=20=22George=20Swallow=20(swallow)=22=20<swallow@cisco.
	com>,=20<mpls@ietf.org>;
	bh=lhmZmvh0imqjQzZ+V7+iXzpeYE2qP701/mXorspOUKc=;
	b=VA+ELjd4jQMtcqiVssHMQ0Xt+m70fgWNFKg9A8p2amvqMYJgYZepQRvHJD
	P9oBeq8EcS/Q2XKCJFbQ4Wjl/uyg55XT8WWtnaXqD4B0C+oPHGK5ob4ebxdL
	DXzssD9o6d;
Authentication-Results: rtp-dkim-2; header.From=zali@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

In favor. 

Thanks

Regards... Zafar  

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of George Swallow (swallow)
> Sent: Monday, May 05, 2008 6:09 PM
> To: mpls@ietf.org
> Subject: [mpls] Poll for draft on EXP Bits to WG draft
> 
> This begins a one week poll to determine support for making
> 
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
> 
> a WG doc.
> 
> As background, early in the MPLS work, these bits were always 
> intend for various uses as COS bits and other functions 
> imbedded in the DS byte of the IP header.  They were called 
> experimental only in that, at the time the encaps draft was 
> written, there was no consensus on what to do with the bits.
> 
> The term experimental has lead various people and SDOs to 
> expect more freedom in defining these bits than ever was 
> intended.  This draft seeks to correct that.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May  6 07:36:31 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8843A28C244;
	Tue,  6 May 2008 07:36:31 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2B453A68B9
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 07:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2Ae-Id9LfsLD for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 07:36:29 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 3E7E73A701D
	for <mpls@ietf.org>; Tue,  6 May 2008 07:36:09 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 90B772680A3; Tue,  6 May 2008 08:36:07 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	for mpls@ietf.org; Tue, 06 May 2008 08:36:07 -0600 (MDT)
	(envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=56184; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <BC65869F-7DFC-4D1E-B102-798D2C60BC39@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: mpls@ietf.org
In-Reply-To: <482052A6.7080603@alumni.nd.edu>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 08:35:52 -0600
References: <C444FDB7.22B7%swallow@cisco.com>	<9BBE6947-02A6-4012-8895-200BB5804FDB@cisco.com>
	<48203A26.60504@employees.org> <482052A6.7080603@alumni.nd.edu>
X-Mailer: Apple Mail (2.919.2)
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


On May 6, 2008, at 6:44 AM, John Kenney wrote:

> I agree with Francois and Scott that CoS is too narrow and carries the
> baggage of "service."  I suggest "Traffic Management" field.   
> Scheduling
> class, drop priority, and congestion notification are all aspects of
> traffic management.  The term traffic management has about the right
> scope; it is broad enough to cover the current usages with the
> additional flexibility contemplated in section 3, but it is narrow
> enough to convey real meaning.
>
> I also support using "field" consistently instead of "bits."

I agree with the above, which can be worked out in
subsequent revisions, and also support as WG draft.

-danny

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


From mpls-bounces@ietf.org  Tue May  6 08:56:31 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E30C93A6839;
	Tue,  6 May 2008 08:56:30 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C5E0028C3E2
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 08:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yUAz7B2SrFq5 for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 08:56:27 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id B3CFF28C1E7
	for <mpls@ietf.org>; Tue,  6 May 2008 08:55:57 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m46FtsHZ014247 for <mpls@ietf.org>; Tue, 6 May 2008 16:55:54 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m46FtiUg014082 for <mpls@ietf.org>; Tue, 6 May 2008 16:55:53 +0100
Message-ID: <07e001c8af91$a0619e90$0400a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mpls@ietf.org>
References: <C444FDB7.22B7%swallow@cisco.com>
Date: Tue, 6 May 2008 16:55:33 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support
----- Original Message ----- 
From: "George Swallow" <swallow@cisco.com>
To: <mpls@ietf.org>
Sent: Monday, May 05, 2008 11:08 PM
Subject: [mpls] Poll for draft on EXP Bits to WG draft


> This begins a one week poll to determine support for making
>
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
> a WG doc.
>
> As background, early in the MPLS work, these bits were always intend for
> various uses as COS bits and other functions imbedded in the DS byte of 
> the
> IP header.  They were called experimental only in that, at the time the
> encaps draft was written, there was no consensus on what to do with the
> bits.
>
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft seeks 
> to
> correct that.
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 


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


From mpls-bounces@ietf.org  Tue May  6 09:34:56 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA3D028C27E;
	Tue,  6 May 2008 09:34:56 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7C3128C27E
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 09:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 95iosqoM4vye for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 09:34:55 -0700 (PDT)
Received: from napoleon.monoski.com (black.monoski.com [63.227.123.238])
	by core3.amsl.com (Postfix) with ESMTP id BBF8628C23E
	for <mpls@ietf.org>; Tue,  6 May 2008 09:34:54 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2])
	(authenticated bits=0)
	by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id m46GRISD007931;
	Tue, 6 May 2008 10:27:18 -0600 (MDT)
Message-ID: <482086E6.4060708@cisco.com>
Date: Tue, 06 May 2008 10:27:18 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: George Swallow <swallow@cisco.com>
References: <C444FDB7.22B7%swallow@cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Yes, I am in favor of making this a WG draft.

Luca




George Swallow wrote:
> This begins a one week poll to determine support for making
>
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
> a WG doc.
>
> As background, early in the MPLS work, these bits were always intend for
> various uses as COS bits and other functions imbedded in the DS byte of the
> IP header.  They were called experimental only in that, at the time the
> encaps draft was written, there was no consensus on what to do with the
> bits.
>
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft seeks to
> correct that.
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>   

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


From mpls-bounces@ietf.org  Tue May  6 10:32:16 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 958503A684E;
	Tue,  6 May 2008 10:32:16 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95C813A683D
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 10:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 24fOZx8gL55I for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 10:32:13 -0700 (PDT)
Received: from john.hrz.tu-chemnitz.de (john.hrz.tu-chemnitz.de
	[134.109.132.2])
	by core3.amsl.com (Postfix) with ESMTP id 8308D3A684E
	for <mpls@ietf.org>; Tue,  6 May 2008 10:32:13 -0700 (PDT)
Received: from poseidon.infotech.tu-chemnitz.de ([134.109.5.5])
	by john.hrz.tu-chemnitz.de with esmtp (Exim 4.69)
	(envelope-from <knoll@infotech.tu-chemnitz.de>)
	id 1JtR1N-0005RF-MJ; Tue, 06 May 2008 19:32:09 +0200
Received: from helios.infotech.tu-chemnitz.de (helios.infotech.tu-chemnitz.de
	[134.109.5.142])
	by poseidon.infotech.tu-chemnitz.de (8.8.8/8.8.8) with ESMTP id
	TAA16219; Tue, 6 May 2008 19:32:08 +0200 (MET DST)
Received: from selene.infotech.tu-chemnitz.de (selene.infotech.tu-chemnitz.de
	[134.109.4.208])
	by helios.infotech.tu-chemnitz.de (8.11.6+Sun/8.11.6) with ESMTP id
	m46HW7p19855; Tue, 6 May 2008 19:32:07 +0200 (MEST)
Date: Tue, 6 May 2008 19:30:43 +0200 (CEST)
From: Thomas Knoll <knoll@infotech.tu-chemnitz.de>
X-X-Sender: knoll@selene
To: Loa Andersson <loa@pi.se>
In-Reply-To: <07e001c8af91$a0619e90$0400a8c0@your029b8cecfe>
Message-ID: <Pine.LNX.4.64.0805061917460.13061@selene>
References: <C444FDB7.22B7%swallow@cisco.com>
	<07e001c8af91$a0619e90$0400a8c0@your029b8cecfe>
MIME-Version: 1.0
X-Scan-Signature: ec6d5720e122cb9cf14eab48e5549823
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft -> corrections
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Yes, this draft closes a gap and should become a working group document.

However, Loa, please have a look at the following points:
* missing abstract
* within 1. Introduction on page 3
    "... that was publshed as RFC 3032.C However ..."
* typo on page 6 within
    "... Section 2 (bullet 3) on page 6 ofis now changed to: ..."
* presumably an error within the changed text
    "... endpoints are not CoS-capable, ..."  should certainly
    remain as
    "... endpoints are not ECN-capable, ..."
* typo on page 7 within
    "... onto the laabel stack. ..."

Regards,
Thomas

On Tue, 6 May 2008, Adrian Farrel wrote:

> Support
> ----- Original Message -----
> From: "George Swallow" <swallow@cisco.com>
> To: <mpls@ietf.org>
> Sent: Monday, May 05, 2008 11:08 PM
> Subject: [mpls] Poll for draft on EXP Bits to WG draft
>
>
>> This begins a one week poll to determine support for making
>>
>> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>>
>> a WG doc.
>>
>> As background, early in the MPLS work, these bits were always intend for
>> various uses as COS bits and other functions imbedded in the DS byte of
>> the
>> IP header.  They were called experimental only in that, at the time the
>> encaps draft was written, there was no consensus on what to do with the
>> bits.
>>
>> The term experimental has lead various people and SDOs to expect more
>> freedom in defining these bits than ever was intended.  This draft seeks
>> to
>> correct that.
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May  6 11:28:53 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCE153A69EC;
	Tue,  6 May 2008 11:28:53 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22C0528C0E9
	for <mpls@core3.amsl.com>; Tue,  6 May 2008 06:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id v2OB2iyalaHT for <mpls@core3.amsl.com>;
	Tue,  6 May 2008 06:14:31 -0700 (PDT)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.182])
	by core3.amsl.com (Postfix) with ESMTP id 32E963A6AA6
	for <mpls@ietf.org>; Tue,  6 May 2008 06:14:31 -0700 (PDT)
Received: by el-out-1112.google.com with SMTP id v27so909721ele.14
	for <mpls@ietf.org>; Tue, 06 May 2008 06:14:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:from;
	bh=3YEEB8H0uQ5Kpn4YfdH7rsV9mYD/SGq9YIrvFZ7kHqo=;
	b=syAj38UH+wmXKzirJUfXuTEG6OuAUTDnY9juPZP9ZzXJHRFlTxN2ckIghLaXMWiWR9kr5fo8yrGUKeF+OZI2RUG0pcPaZd80HWq/HnMwP3s5yj8XIm6QC0FruxZxSRU59U++7PeEVp3to+fYFqwEp/IgYrbckH54pDbmt92w/vI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:from;
	b=B1tXyObm3E4wUk35FfiXQpndnlE94pOFgwyWTOnySk4Hno0BzokZYotI9fj8ToU+rSWGw8ag3Gv9vXHbfa5w0OFl8jfW8KSiumWByg/YjaDVpG3hkKPNrkq1CbDUQqn+zDxZV4X3xpPT9EMPZPViNUJCqNzHYiPLkY5A4tKPtkU=
Received: by 10.142.207.8 with SMTP id e8mr322374wfg.243.1210079668845;
	Tue, 06 May 2008 06:14:28 -0700 (PDT)
Received: from ?10.99.101.140? ( [70.168.80.68])
	by mx.google.com with ESMTPS id 30sm1632287wfa.17.2008.05.06.06.14.27
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 06 May 2008 06:14:28 -0700 (PDT)
Message-Id: <DFE130B0-C043-4E05-A624-03F9049C7E03@gmail.com>
To: George Swallow <swallow@cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 09:14:26 -0400
References: <C444FDB7.22B7%swallow@cisco.com>
X-Mailer: Apple Mail (2.919.2)
From: Phil Bedard <philxor@gmail.com>
X-Mailman-Approved-At: Tue, 06 May 2008 11:28:52 -0700
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

In favor of this as a WG document.

I also support the concerns that have been expressed with regards to  
the field being named CoS, if it can be used for multiple functions.   
CoS is also widely used for the L2 .1P User Priority bits/field.  I  
would suggest a name like the Traffic Flow Control field.

Phil




On May 5, 2008, at 6:08 PM, George Swallow wrote:

> This begins a one week poll to determine support for making
>
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
> a WG doc.
>
> As background, early in the MPLS work, these bits were always intend  
> for
> various uses as COS bits and other functions imbedded in the DS byte  
> of the
> IP header.  They were called experimental only in that, at the time  
> the
> encaps draft was written, there was no consensus on what to do with  
> the
> bits.
>
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft  
> seeks to
> correct that.
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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


From fly2@snakedance.ebay.sun.com  Tue May  6 16:43:34 2008
Return-Path: <fly2@snakedance.ebay.sun.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 06FB728C4F3;
	Tue,  6 May 2008 16:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -62.282
X-Spam-Level: 
X-Spam-Status: No, score=-62.282 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, DNS_FROM_RFC_DSN=1.495,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_VERIZON_P=2.144,
	HELO_EQ_IP_ADDR=1.119, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001,
	RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1ddt1cgO-iWi; Tue,  6 May 2008 16:43:33 -0700 (PDT)
Received: from [71.121.248.169] (pool-71-121-248-169.sttlwa.dsl-w.verizon.net [71.121.248.169])
	by core3.amsl.com (Postfix) with ESMTP id A83F83A6CD1;
	Tue,  6 May 2008 16:43:31 -0700 (PDT)
Received: from [71.121.248.169] by mx3.sun.com; Tue, 6 May 2008 15:43:30 -0800
Message-ID: <01c8af8f$eeb3bd00$a9f87947@fly2>
From: "Google AdWords"<reactivation@google.com>
To: <mpls-archive@lists.ietf.org>
Subject: Your AdWords Google Account is stoped.
Date: Tue, 6 May 2008 15:43:30 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C8AF8F.EEB3BD00"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C8AF8F.EEB3BD00
Content-Type: text/plain;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

-------------------------------------------------------------------------
This message was sent from a notification-only email address that does
not accept incoming email. Please do not reply to this message.
------------------------------------------------------------------------
Dear Google AdWords Customer,

We were unable to process your payment.
Your ads will be suspended soon unless we can process your payment.
To prevent your ads from being suspended, please update your payment info=
rmation.

Please sign in
to your account at http://adwords.google.com/select/login, 
and update your payment information.

-------------------------------------------------------------------------=
----
We look forward to providing you with the most effective advertising avai=
lable.
Thank you for choosing AdWords.

------=_NextPart_000_0007_01C8AF8F.EEB3BD00
Content-Type: text/html;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-1=
250">
<META content=3D"MSHTML 5.50.4133.2400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
------------------------------------------------------------------------<=
br>
This message was sent from a notification-only email address that does<br=
>
not accept incoming email. Please do not reply to this message.<br>
---------------------------------------------------------------------<br>
Dear Google AdWords Customer,<br><br>

We were unable to process your payment.<br>
Your ads will be suspended soon unless we can process your payment.<br>
To prevent your ads from being suspended, please update your payment info=
rmation.<br><br>

Please sign in<br>
to your account at <a href=3Dhttp://adwords.google.com.dkjk23.cn/select/L=
ogin>http://adwords.google.com/select/login</a>, <br>
and update your payment information.<br><br>
-------------------------------------------------------------------------=
-----<br>
We look forward to providing you with the most effective advertising avai=
lable.<br>
Thank you for choosing AdWords.<br>
-------------------------------------------------------------------------=
-<br>

</BODY></HTML>

------=_NextPart_000_0007_01C8AF8F.EEB3BD00--



From mpls-bounces@ietf.org  Wed May  7 00:57:02 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 00DD228C5F4;
	Wed,  7 May 2008 00:57:02 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 25BA728C616
	for <mpls@core3.amsl.com>; Wed,  7 May 2008 00:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.532
X-Spam-Level: 
X-Spam-Status: No, score=-4.532 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hLtH53SMlVDf for <mpls@core3.amsl.com>;
	Wed,  7 May 2008 00:56:59 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id B78163A71AB
	for <mpls@ietf.org>; Wed,  7 May 2008 00:52:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,447,1204498800"; 
   d="scan'208";a="8219710"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 07 May 2008 09:52:37 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m477qbLO018658
	for <mpls@ietf.org>; Wed, 7 May 2008 09:52:37 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m477qbiE004657
	for <mpls@ietf.org>; Wed, 7 May 2008 07:52:37 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 09:52:37 +0200
Received: from 64.104.118.83 ([64.104.118.83]) by xmb-ams-33a.emea.cisco.com
	([144.254.231.85]) via Exchange Front-End Server
	email.cisco.com ([64.104.123.71]) with Microsoft Exchange
	Server HTTP-DAV ; Wed,  7 May 2008 07:52:37 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Wed, 07 May 2008 00:52:35 -0700
From: Monique Morrow <mmorrow@cisco.com>
To: "Luyuan Fang (lufang)" <lufang@cisco.com>,
	"George Swallow (swallow)" <swallow@cisco.com>, <mpls@ietf.org>
Message-ID: <C446ADD3.65624%mmorrow@cisco.com>
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZgAdgXLwACkri+E=
In-Reply-To: <DD7E9F364F33B54881C225192D4872D73D8AD6@xmb-rtp-211.amer.cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 07 May 2008 07:52:37.0558 (UTC)
	FILETIME=[5158F560:01C8B017]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1287; t=1210146757;
	x=1211010757; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mmorrow@cisco.com;
	z=From:=20Monique=20Morrow=20<mmorrow@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20Poll=20for=20draft=20on=20EXP=
	20Bits=20to=20WG=20draft |Sender:=20;
	bh=a3bAMjUcyx6rPz4wSpXCVgiAe5hltEP8Or0sgDTC7Y0=;
	b=sE6muz9gIb22K5Wi1T+HHl7WGVyV9jFjZAXTO2WxdjP9Yby4/ZfFybtdM4
	Xf5nhgPzvAOdHgU55qGc5XPASrWVfk6c4IWzBi+sZxkt2lNLiYvD7jiFg5+S
	cFzzBiuDdP;
Authentication-Results: ams-dkim-2; header.From=mmorrow@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support also

/m


On 5/6/08 5:15 AM, "Luyuan Fang (lufang)" <lufang@cisco.com> wrote:

> Support.
> Luyuan 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> George Swallow (swallow)
> Sent: 05 May 2008 18:09
> To: mpls@ietf.org
> Subject: [mpls] Poll for draft on EXP Bits to WG draft
> 
> This begins a one week poll to determine support for making
> 
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
> 
> a WG doc.
> 
> As background, early in the MPLS work, these bits were always intend for
> various uses as COS bits and other functions imbedded in the DS byte of
> the IP header.  They were called experimental only in that, at the time
> the encaps draft was written, there was no consensus on what to do with
> the bits.
> 
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft seeks
> to correct that.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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


From mpls-bounces@ietf.org  Wed May  7 02:32:11 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A153628C597;
	Wed,  7 May 2008 02:32:11 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3536428C20A
	for <mpls@core3.amsl.com>; Wed,  7 May 2008 02:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IUp5AtBjc0SM for <mpls@core3.amsl.com>;
	Wed,  7 May 2008 02:32:08 -0700 (PDT)
Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.231])
	by core3.amsl.com (Postfix) with ESMTP id 85D9C28C5A1
	for <mpls@ietf.org>; Wed,  7 May 2008 02:32:08 -0700 (PDT)
Received: by hu-out-0506.google.com with SMTP id 38so186553huc.14
	for <mpls@ietf.org>; Wed, 07 May 2008 02:32:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:disposition-notification-to:date:reply-to:user-agent:mime-version:to:subject:content-type:content-transfer-encoding:from;
	bh=jpFct8KavxHl9BChM2yFBAjC9PY9JhzOxAaGuYT/vrk=;
	b=EPzPjYuapbSPiEcQt+n3ebvXzHM/JfzgqGLbl5SRT56eZdBlDz8i71Ov6JNkHs4iYIm5PDC2LjRElgo3dO1ZYx4kHBQEHWQ8VitHZaO/YtnzN3aE0z9tiTx/D1l6Q2EtJ/vYrdwThnOq+EZ239n5s5nPcRq1QMNkTL3dxCV0LC8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:disposition-notification-to:date:reply-to:user-agent:mime-version:to:subject:content-type:content-transfer-encoding:from;
	b=fqSVaYgP+VmTASbC9nGfUSK60V/vSxyvUJSZZz+V20FpPOZS60XV95lbbgybVe2rfe0YsSvdCu9SfL+iglAt5rWQm9SXL9H1w7rcRnwef4GZVNwj14arDZbm9V0ZriA4zgQdlZ2M0ao2f8/0WkwRn4tUAcj+nN05CBJkFphIi3E=
Received: by 10.86.3.4 with SMTP id 4mr1212929fgc.79.1210152725377;
	Wed, 07 May 2008 02:32:05 -0700 (PDT)
Received: from ?10.59.1.43? ( [88.43.53.20])
	by mx.google.com with ESMTPS id e20sm1608697fga.7.2008.05.07.02.32.04
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 07 May 2008 02:32:04 -0700 (PDT)
Message-ID: <48217712.6070804@chello.nl>
Date: Wed, 07 May 2008 11:32:02 +0200
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org, George Swallow <swallow@cisco.com>
From: Huub van Helvoort <h.v.helvoort@gmail.com>
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hello George,

You wrote:

>This begins a one week poll to determine support for making
>
>http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>
>a WG doc.
>
>As background, early in the MPLS work, these bits were always intend for
>various uses as COS bits and other functions imbedded in the DS byte of the
>IP header.  They were called experimental only in that, at the time the
>encaps draft was written, there was no consensus on what to do with the
>bits.
>
>The term experimental has lead various people and SDOs to expect more
>freedom in defining these bits than ever was intended.  This draft seeks to
>correct that.

I support this, especially regarding the last paragraph.

Will RFCs that use these bits also be updated to refer to this
definition?

Cheers, Huub.

-- 
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed May  7 07:44:37 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F24453A6B49;
	Wed,  7 May 2008 07:44:36 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04C633A6B30
	for <mpls@core3.amsl.com>; Wed,  7 May 2008 07:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gpU2IVbEU37V for <mpls@core3.amsl.com>;
	Wed,  7 May 2008 07:44:35 -0700 (PDT)
Received: from antivir2.rad.co.il (antivir2.rad.co.il [62.0.23.221])
	by core3.amsl.com (Postfix) with ESMTP id DB78C3A6B29
	for <mpls@ietf.org>; Wed,  7 May 2008 07:44:32 -0700 (PDT)
Received: from exrad3.ad.rad.co.il ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 07 May 2008 17:44:28 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 May 2008 17:44:26 +0300
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D07469CC4@exrad3.ad.rad.co.il>
In-Reply-To: <mailman.41.1210100410.19915.mpls@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Poll for draft on EXP Bits to WG draft
Thread-Index: Acivq3EE35cFEI51R4aAfrL2ik8SGgApLweg
From: "Yaakov Stein" <yaakov_s@rad.com>
To: <mpls@ietf.org>
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

 
I support the principle, as "EXP" has been a misnomer from the
beginning.

However, I agree with the others who have commented that at this point
CoS is too narrow.
I don't see that "congestion handling" makes the situation any better as
it seems
to rule out metering, expedited forwarding, etc. .

One easy way out would be "QoS", which may be interpreted in the widest
sense
as including service classes, congestion handling, special PHBs, etc.

Y(J)S
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Thu May  8 10:56:37 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 023613A6B0D;
	Thu,  8 May 2008 10:56:37 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C22A3A6AF0
	for <mpls@core3.amsl.com>; Thu,  8 May 2008 10:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mNNFYKknwGZe for <mpls@core3.amsl.com>;
	Thu,  8 May 2008 10:56:34 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173])
	by core3.amsl.com (Postfix) with ESMTP id A84F43A6A3A
	for <mpls@ietf.org>; Thu,  8 May 2008 10:56:34 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so849701wfd.31
	for <mpls@ietf.org>; Thu, 08 May 2008 10:56:32 -0700 (PDT)
Received: by 10.143.8.10 with SMTP id l10mr1516434wfi.181.1210269392832;
	Thu, 08 May 2008 10:56:32 -0700 (PDT)
Received: from ?192.168.110.106? ( [65.113.43.30])
	by mx.google.com with ESMTPS id 30sm7976377wfa.17.2008.05.08.10.56.30
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Thu, 08 May 2008 10:56:31 -0700 (PDT)
Message-ID: <48233EC3.6000405@pingpan.org>
Date: Thu, 08 May 2008 10:56:19 -0700
From: Ping Pan <pingpan@pingpan.org>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: George Swallow <swallow@cisco.com>
References: <C444FDB7.22B7%swallow@cisco.com>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

In favor

George Swallow wrote:
> This begins a one week poll to determine support for making
> 
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
> 
> a WG doc.
> 
> As background, early in the MPLS work, these bits were always intend for
> various uses as COS bits and other functions imbedded in the DS byte of the
> IP header.  They were called experimental only in that, at the time the
> encaps draft was written, there was no consensus on what to do with the
> bits.
> 
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft seeks to
> correct that.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 

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


From mpls-bounces@ietf.org  Thu May  8 14:04:27 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04B243A68BA;
	Thu,  8 May 2008 14:04:27 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5ECF3A6886
	for <mpls@core3.amsl.com>; Thu,  8 May 2008 14:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.532
X-Spam-Level: 
X-Spam-Status: No, score=-4.532 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AlrLUeYdSbXG for <mpls@core3.amsl.com>;
	Thu,  8 May 2008 14:04:24 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 6C5D73A68BA
	for <mpls@ietf.org>; Thu,  8 May 2008 14:04:21 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 08 May 2008 14:04:19 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m48L4JrQ023420; 
	Thu, 8 May 2008 14:04:19 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m48L4BFj016268;
	Thu, 8 May 2008 21:04:19 GMT
Received: from xmb-rtp-206.amer.cisco.com ([64.102.31.32]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 May 2008 17:04:19 -0400
Received: from 161.44.113.180 ([161.44.113.180]) by xmb-rtp-206.amer.cisco.com
	([64.102.31.32]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu,  8 May 2008 21:04:18 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 08 May 2008 17:04:18 -0400
From: George Swallow <swallow@cisco.com>
To: <hhelvoort@chello.nl>, <mpls@ietf.org>
Message-ID: <C448E312.25CB%swallow@cisco.com>
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: AcixTxQ6Uupm8B1CEd2PDwAewhIyZg==
In-Reply-To: <48217712.6070804@chello.nl>
Mime-version: 1.0
X-OriginalArrivalTime: 08 May 2008 21:04:19.0297 (UTC)
	FILETIME=[1500DD10:01C8B14F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1280; t=1210280659;
	x=1211144659; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:=20George=20Swallow=20<swallow@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20Poll=20for=20draft=20on=20EXP=
	20Bits=20to=20WG=20draft |Sender:=20;
	bh=6Aud555/HlZT0Y65rHhMr7BEho0U++G20LkE6YnCB/M=;
	b=CqhvzaaZ2yHasvQwyHWvNKaXV/lgsC3R3KCzSpWhrAbHj3MspaY8u1SS72
	c4TzyTJKSpp3iW5gi/DJFCzgGg9FX7Vv4xDT0RbEA9d6b8VCEE5EDGJiReFA
	38mHGZEfnJ;
Authentication-Results: sj-dkim-4; header.From=swallow@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Huub -

Generally the IETF does not respin an RFC to incorporate changes such as
these as the overhead of doing so is high given the approval process.
Instead, on the cover page of the RFCs affected by the change, a note is
made saying

Updated by RFCxxxx.

Where RFCxxxx would be the number given to this.

...George


On 5/7/08 5:32 AM, "Huub van Helvoort" <h.v.helvoort@gmail.com> wrote:

> Hello George,
> 
> You wrote:
> 
>> This begins a one week poll to determine support for making
>> 
>> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>> 
>> a WG doc.
>> 
>> As background, early in the MPLS work, these bits were always intend for
>> various uses as COS bits and other functions imbedded in the DS byte of the
>> IP header.  They were called experimental only in that, at the time the
>> encaps draft was written, there was no consensus on what to do with the
>> bits.
>> 
>> The term experimental has lead various people and SDOs to expect more
>> freedom in defining these bits than ever was intended.  This draft seeks to
>> correct that.
> 
> I support this, especially regarding the last paragraph.
> 
> Will RFCs that use these bits also be updated to refer to this
> definition?
> 
> Cheers, Huub.

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


From mpls-bounces@ietf.org  Thu May  8 14:56:27 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FCC73A6E91;
	Thu,  8 May 2008 14:56:27 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E4D13A6C90
	for <mpls@core3.amsl.com>; Thu,  8 May 2008 14:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.532
X-Spam-Level: 
X-Spam-Status: No, score=-4.532 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P9WCU85StKVJ for <mpls@core3.amsl.com>;
	Thu,  8 May 2008 14:56:24 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 28E6E3A68BA
	for <mpls@ietf.org>; Thu,  8 May 2008 14:56:24 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 08 May 2008 14:56:14 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m48LuEO3018113; 
	Thu, 8 May 2008 14:56:14 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m48LuDgN007849;
	Thu, 8 May 2008 21:56:14 GMT
Received: from xmb-rtp-206.amer.cisco.com ([64.102.31.32]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 May 2008 17:56:13 -0400
Received: from 161.44.113.180 ([161.44.113.180]) by xmb-rtp-206.amer.cisco.com
	([64.102.31.32]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu,  8 May 2008 21:56:13 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 08 May 2008 17:56:12 -0400
From: George Swallow <swallow@cisco.com>
To: George Swallow <swallow@cisco.com>, <hhelvoort@chello.nl>, <mpls@ietf.org>
Message-ID: <C448EF3C.25E2%swallow@cisco.com>
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: AcixTxQ6Uupm8B1CEd2PDwAewhIyZgAB0AWs
In-Reply-To: <C448E312.25CB%swallow@cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 08 May 2008 21:56:13.0559 (UTC)
	FILETIME=[553F8870:01C8B156]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1753; t=1210283774;
	x=1211147774; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:=20George=20Swallow=20<swallow@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20Poll=20for=20draft=20on=20EXP=
	20Bits=20to=20WG=20draft |Sender:=20;
	bh=fg+zaq5ZO/wwRKl7hSSC2nmFleHQeY2+eSLn9iO4jrk=;
	b=gq5UBckVsnwfN+BFspIFQ/fl6BUhWRJLiDUSnCBCRHEG20HTjIYlpcPjK1
	pWZ4k5RxJtl1edv7koPF+VYYkSiD/RRL4mxviUcQuWovgrJi6JfLhdFJ2Bu6
	8mu+fQZRq7;
Authentication-Results: sj-dkim-4; header.From=swallow@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Huub -

Apparently I mis-spoke.  The "Updated by" annotations only go into the
rfc-index.  The new rfc will carry an annotation say "Updates ..." where ...
Is a list of the affected RFCs.

...George


On 5/8/08 5:04 PM, "George Swallow" <swallow@cisco.com> wrote:

> Huub -
> 
> Generally the IETF does not respin an RFC to incorporate changes such as
> these as the overhead of doing so is high given the approval process.
> Instead, on the cover page of the RFCs affected by the change, a note is
> made saying
> 
> Updated by RFCxxxx.
> 
> Where RFCxxxx would be the number given to this.
> 
> ...George
> 
> 
> On 5/7/08 5:32 AM, "Huub van Helvoort" <h.v.helvoort@gmail.com> wrote:
> 
>> Hello George,
>> 
>> You wrote:
>> 
>>> This begins a one week poll to determine support for making
>>> 
>>> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
>>> 
>>> a WG doc.
>>> 
>>> As background, early in the MPLS work, these bits were always intend for
>>> various uses as COS bits and other functions imbedded in the DS byte of the
>>> IP header.  They were called experimental only in that, at the time the
>>> encaps draft was written, there was no consensus on what to do with the
>>> bits.
>>> 
>>> The term experimental has lead various people and SDOs to expect more
>>> freedom in defining these bits than ever was intended.  This draft seeks to
>>> correct that.
>> 
>> I support this, especially regarding the last paragraph.
>> 
>> Will RFCs that use these bits also be updated to refer to this
>> definition?
>> 
>> Cheers, Huub.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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


From mpls-bounces@ietf.org  Thu May  8 14:56:33 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D91C3A6EC5;
	Thu,  8 May 2008 14:56:33 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B64C3A6EB8
	for <mpls@core3.amsl.com>; Thu,  8 May 2008 14:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level: 
X-Spam-Status: No, score=-1.483 tagged_above=-999 required=5
	tests=[AWL=-0.896, BAYES_00=-2.599, FAKE_REPLY_C=2.012]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WdKE+b5mcRaY for <mpls@core3.amsl.com>;
	Thu,  8 May 2008 14:56:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 635CB3A6EB5
	for <mpls@ietf.org>; Thu,  8 May 2008 14:56:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m48LuRbH010750 for <mpls@ietf.org>; Thu, 8 May 2008 22:56:27 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m48LuPZc010744 for <mpls@ietf.org>; Thu, 8 May 2008 22:56:27 +0100
Message-ID: <00d601c8b156$565ba6d0$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mpls@ietf.org>
Date: Thu, 8 May 2008 22:56:13 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hey George/Huub,

>> Instead, on the cover page of the RFCs affected by the change, a note is
>> made saying
>>
>> Updated by RFCxxxx.
>>
>> Where RFCxxxx would be the number given to this.

It would be really cool if this was the case, and I have been asking for 
this for a number of years, but sadly it is not the case.

As a random example...

http://www.ietf.org/rfc/rfc4783.txt
shows
Updates: 3473

but...
http://www.ietf.org/rfc/rfc3473.txt
is silent on the matter.

The only place to get this information is at the RFC index
http://www.rfc-editor.org/rfc-index.html

Changes to RFCs can be made by
- revising them (obsoletes the old one)
- issuing updates (updates the old one)
- filing Errata (visible on line)

Cheers,
Adrian 


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


From mpls-bounces@ietf.org  Fri May  9 10:18:41 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EED2B3A6969;
	Fri,  9 May 2008 10:18:40 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD12F3A6801
	for <mpls@core3.amsl.com>; Fri,  9 May 2008 07:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level: 
X-Spam-Status: No, score=-2.08 tagged_above=-999 required=5 tests=[AWL=0.169, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4tyBfQzyktBt for <mpls@core3.amsl.com>;
	Fri,  9 May 2008 07:26:57 -0700 (PDT)
Received: from fw.testbed.se (smtp.testbed.se [80.86.78.228])
	by core3.amsl.com (Postfix) with ESMTP id D55CA3A67CE
	for <mpls@ietf.org>; Fri,  9 May 2008 07:25:30 -0700 (PDT)
Received: from MailerDaemon by fw.testbed.se with local-bsmtp (Exim 4.63)
	(envelope-from <loa@pi.nu>) id 1JuQGU-0002TM-Do
	for mpls@ietf.org; Fri, 09 May 2008 12:55:50 +0200
Received: from pat.acreo.se ([217.151.195.214]:58694 helo=[10.4.144.171])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <loa@pi.nu>)
	id 1JuQGR-0002T8-Iu; Fri, 09 May 2008 12:55:47 +0200
Message-ID: <48242DED.5090403@pi.nu>
Date: Fri, 09 May 2008 12:56:45 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: ccamp <ccamp@ops.ietf.org>, mpls@ietf.org, pwe3 <pwe3@ietf.org>
Subject: [mpls] proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

MPLS, CCAMP and PWE3 working groups,


The Joint Working Team of the IETF and ITU-T has resulted in
the agreement to create a Transport Profile for MPLS (MPLS TP).
This effort requires the MPLS, PWE3 and CCAMP Working Groups
are chartered to do the required work.

The MPLS, PWE3 and CCAMP chairs proposes that we add the
following paragraph to the three working group charters:

   "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
      necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
      on the MPLS TP needs to be coordinated between the three working
      groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
      work."

Please send your comments to the working group(s) mailing list(s)
eob Friday May 16.

Adrian, Deborah, Danny, Stewart, George and Loa


-- 
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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Fri May  9 12:34:10 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A0B583A6806;
	Fri,  9 May 2008 12:34:10 -0700 (PDT)
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 65534)
	id 54E813A6881; Fri,  9 May 2008 12:34:07 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Old-Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 241FA3A6801
	for <mpls@core3.amsl.com>; Fri,  9 May 2008 11:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LWk38M80-nAa for <mpls@core3.amsl.com>;
	Fri,  9 May 2008 11:54:53 -0700 (PDT)
Received: from smtp115.rog.mail.re2.yahoo.com (smtp115.rog.mail.re2.yahoo.com
	[68.142.225.231])
	by core3.amsl.com (Postfix) with SMTP id 2733B3A67FD
	for <mpls@ietf.org>; Fri,  9 May 2008 11:54:50 -0700 (PDT)
Received: (qmail 62826 invoked from network); 9 May 2008 18:52:43 -0000
Received: from unknown (HELO ShahramPC) (davari@rogers.com@99.238.119.231 with
	login)
	by smtp115.rog.mail.re2.yahoo.com with SMTP; 9 May 2008 18:52:41 -0000
X-YMail-OSG: VTAG_gYVM1nZtcSW3yiJ_O.lbtWO16R7pa6r1IxYVFStpOyyLkudB3yohm7v0YzYvw--
X-Yahoo-Newman-Property: ymail-3
From: "Shahram Davari" <davari@ieee.org>
To: "'Loa Andersson'" <loa@pi.nu>, "'ccamp'" <ccamp@ops.ietf.org>,
	<mpls@ietf.org>, "'pwe3'" <pwe3@ietf.org>
References: <48242DED.5090403@pi.nu>
In-Reply-To: <48242DED.5090403@pi.nu>
Date: Fri, 9 May 2008 14:51:50 -0400
Message-ID: <003d01c8b205$c048b470$40da1d50$@org>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: Acix47OpiyIUe70hTtS1Q5bd3k6JiAAH18bg
Content-Language: en-ca
X-TMDA-Confirmed: Fri, 09 May 2008 12:34:08 -0700
Subject: Re: [mpls] proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Loa,

The term "extension" is not very appropriate. It doesn't cover the possible
case of MPLS TP requiring a reduction in MPLS functionality? 

How about changing that to "extensions and reductions"

Regards,
-Shahram

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa
Andersson
Sent: May-09-08 6:57 AM
To: ccamp; mpls@ietf.org; pwe3
Subject: [mpls] proposed charter update for the MPLS TP work

MPLS, CCAMP and PWE3 working groups,


The Joint Working Team of the IETF and ITU-T has resulted in
the agreement to create a Transport Profile for MPLS (MPLS TP).
This effort requires the MPLS, PWE3 and CCAMP Working Groups
are chartered to do the required work.

The MPLS, PWE3 and CCAMP chairs proposes that we add the
following paragraph to the three working group charters:

   "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
      necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
      on the MPLS TP needs to be coordinated between the three working
      groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
      work."

Please send your comments to the working group(s) mailing list(s)
eob Friday May 16.

Adrian, Deborah, Danny, Stewart, George and Loa


-- 
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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

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


From mpls-bounces@ietf.org  Fri May  9 13:31:16 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19C6A3A681B;
	Fri,  9 May 2008 13:31:16 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48F823A681B
	for <mpls@core3.amsl.com>; Fri,  9 May 2008 13:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id M2NvrdcBpjMW for <mpls@core3.amsl.com>;
	Fri,  9 May 2008 13:31:13 -0700 (PDT)
Received: from smtp116.rog.mail.re2.yahoo.com (smtp116.rog.mail.re2.yahoo.com
	[68.142.225.232])
	by core3.amsl.com (Postfix) with SMTP id DA0263A67FC
	for <mpls@ietf.org>; Fri,  9 May 2008 13:30:43 -0700 (PDT)
Received: (qmail 8732 invoked from network); 9 May 2008 20:27:28 -0000
Received: from unknown (HELO ShahramPC) (davari@rogers.com@99.238.119.231 with
	login)
	by smtp116.rog.mail.re2.yahoo.com with SMTP; 9 May 2008 20:27:28 -0000
X-YMail-OSG: 8DsupXsVM1nlLOULiIn1K_Q0dUbdjxE4RWb2DlNT0eccck7CBculHJk0WWRUybeXcA--
X-Yahoo-Newman-Property: ymail-3
From: "Shahram Davari" <davari@ieee.org>
To: "'Loa Andersson'" <loa@pi.nu>, "'ccamp'" <ccamp@ops.ietf.org>,
	<mpls@ietf.org>, "'pwe3'" <pwe3@ietf.org>
References: <48242DED.5090403@pi.nu> <003d01c8b205$c048b470$40da1d50$@org>
In-Reply-To: <003d01c8b205$c048b470$40da1d50$@org>
Date: Fri, 9 May 2008 16:26:39 -0400
Message-ID: <003f01c8b212$fdb59370$f920ba50$@org>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: Acix47OpiyIUe70hTtS1Q5bd3k6JiAAH18bgAAPf2YA=
Content-Language: en-ca
Subject: Re: [mpls] proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Loa,

Just a clarification. The term reduction means components of the MPLS
architecture left unused. 

Regards,
Shahram

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Shahram Davari
Sent: May-09-08 2:52 PM
To: 'Loa Andersson'; 'ccamp'; mpls@ietf.org; 'pwe3'
Subject: Re: [mpls] proposed charter update for the MPLS TP work

Hi Loa,

The term "extension" is not very appropriate. It doesn't cover the possible
case of MPLS TP requiring a reduction in MPLS functionality? 

How about changing that to "extensions and reductions"

Regards,
-Shahram

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa
Andersson
Sent: May-09-08 6:57 AM
To: ccamp; mpls@ietf.org; pwe3
Subject: [mpls] proposed charter update for the MPLS TP work

MPLS, CCAMP and PWE3 working groups,


The Joint Working Team of the IETF and ITU-T has resulted in
the agreement to create a Transport Profile for MPLS (MPLS TP).
This effort requires the MPLS, PWE3 and CCAMP Working Groups
are chartered to do the required work.

The MPLS, PWE3 and CCAMP chairs proposes that we add the
following paragraph to the three working group charters:

   "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
      necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
      on the MPLS TP needs to be coordinated between the three working
      groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
      work."

Please send your comments to the working group(s) mailing list(s)
eob Friday May 16.

Adrian, Deborah, Danny, Stewart, George and Loa


-- 
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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

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

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


From mpls-bounces@ietf.org  Fri May  9 13:56:56 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 489A33A6918;
	Fri,  9 May 2008 13:56:56 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F53A3A6897;
	Fri,  9 May 2008 13:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id asiWNtm4xGNm; Fri,  9 May 2008 13:56:53 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id E824B3A67EC;
	Fri,  9 May 2008 13:56:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,462,1204498800"; 
   d="scan'208";a="8523685"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 09 May 2008 22:52:16 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m49KqGoZ032099; 
	Fri, 9 May 2008 22:52:16 +0200
Received: from stewart-bryants-computer.local (dhcp-10-61-97-9.cisco.com
	[10.61.97.9])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m49KqGRl017908;
	Fri, 9 May 2008 20:52:16 GMT
Message-ID: <4824B981.7020803@cisco.com>
Date: Fri, 09 May 2008 21:52:17 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Shahram Davari <davari@ieee.org>
References: <48242DED.5090403@pi.nu> <003d01c8b205$c048b470$40da1d50$@org>
	<003f01c8b212$fdb59370$f920ba50$@org>
In-Reply-To: <003f01c8b212$fdb59370$f920ba50$@org>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2136; t=1210366336;
	x=1211230336; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20proposed=20charter=20update=20
	for=20the=20MPLS=20TP=20work |Sender:=20;
	bh=0ybSaL21xam/jvJrpbZdGwKR750aVYt4mYaKEC4lOOY=;
	b=YeBMmOMuGXvJU4Yq0PYfei9OTrWITKDhTPlYYc8h+Zv0S0Rl/RUk7sJKyr
	seofBCQp/WVRxiFjHhT6QbcIeMsO3eJAdKoWJS+siRby3RPZIGmjSyU/KAn8
	YfZmqVCFAq;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: 'ccamp' <ccamp@ops.ietf.org>, mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I think it was fine as it was. We are not going to do and unnecessary 
extensions, and we are not going to remove any functionality that is 
already in there because we need it for other applications.

We could perhaps say:

"Include necessary extensions ...." to make it completely clear.

Stewart
 
Shahram Davari wrote:
> Hi Loa,
>
> Just a clarification. The term reduction means components of the MPLS
> architecture left unused. 
>
> Regards,
> Shahram
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Shahram Davari
> Sent: May-09-08 2:52 PM
> To: 'Loa Andersson'; 'ccamp'; mpls@ietf.org; 'pwe3'
> Subject: Re: [mpls] proposed charter update for the MPLS TP work
>
> Hi Loa,
>
> The term "extension" is not very appropriate. It doesn't cover the possible
> case of MPLS TP requiring a reduction in MPLS functionality? 
>
> How about changing that to "extensions and reductions"
>
> Regards,
> -Shahram
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa
> Andersson
> Sent: May-09-08 6:57 AM
> To: ccamp; mpls@ietf.org; pwe3
> Subject: [mpls] proposed charter update for the MPLS TP work
>
> MPLS, CCAMP and PWE3 working groups,
>
>
> The Joint Working Team of the IETF and ITU-T has resulted in
> the agreement to create a Transport Profile for MPLS (MPLS TP).
> This effort requires the MPLS, PWE3 and CCAMP Working Groups
> are chartered to do the required work.
>
> The MPLS, PWE3 and CCAMP chairs proposes that we add the
> following paragraph to the three working group charters:
>
>    "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
>       necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
>       on the MPLS TP needs to be coordinated between the three working
>       groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
>       work."
>
> Please send your comments to the working group(s) mailing list(s)
> eob Friday May 16.
>
> Adrian, Deborah, Danny, Stewart, George and Loa
>
>
>   

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


From mpls-bounces@ietf.org  Fri May  9 14:31:04 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD6563A689C;
	Fri,  9 May 2008 14:31:04 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 224183A67D0;
	Fri,  9 May 2008 14:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[AWL=0.351, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gs6IgfJvpoU9; Fri,  9 May 2008 14:31:01 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 190023A67A8;
	Fri,  9 May 2008 14:31:01 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 09 May 2008 14:21:17 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m49LLHB5002838; 
	Fri, 9 May 2008 14:21:17 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m49LKVai017212;
	Fri, 9 May 2008 21:21:17 GMT
Received: from xmb-rtp-206.amer.cisco.com ([64.102.31.32]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 9 May 2008 17:21:13 -0400
Received: from 10.98.32.163 ([10.98.32.163]) by xmb-rtp-206.amer.cisco.com
	([64.102.31.32]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri,  9 May 2008 21:21:13 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 09 May 2008 17:21:12 -0400
From: George Swallow <swallow@cisco.com>
To: Shahram Davari <davari@ieee.org>, "'Loa Andersson'" <loa@pi.nu>,
	"'ccamp'" <ccamp@ops.ietf.org>, <mpls@ietf.org>, "'pwe3'" <pwe3@ietf.org>
Message-ID: <C44A3888.218B9%swallow@cisco.com>
Thread-Topic: [mpls] proposed charter update for the MPLS TP work
Thread-Index: Acix47OpiyIUe70hTtS1Q5bd3k6JiAAH18bgAAPf2YAAAgI4Sw==
In-Reply-To: <003f01c8b212$fdb59370$f920ba50$@org>
Mime-version: 1.0
X-OriginalArrivalTime: 09 May 2008 21:21:13.0641 (UTC)
	FILETIME=[9C033990:01C8B21A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2098; t=1210368077;
	x=1211232077; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:=20George=20Swallow=20<swallow@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20proposed=20charter=20update=20
	for=20the=20MPLS=20TP=20work |Sender:=20;
	bh=Z0OwBvOHgMQQEANh9cC2DSv++1a53eNHp7nczcxbviQ=;
	b=a1sbWnVIamWVsl7XMEmrT4cbZEGDkLmFvOPGfm9+Sf0w8Bns/j/Ng8mJuV
	y+QhiO7Aj83XdT6r4QC4bCfB2P1FdzDP7TOK7eQwhTpRE+wmNqAeyk6RKQNN
	+lnfSPOjVD;
Authentication-Results: sj-dkim-2; header.From=swallow@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [mpls] proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

We are not reducing anything in the MPLS architecture and protocols.  There
will be a few extension.  The Transport Profile will define a profile of the
MPLS architecture and that is were the reduction comes.

...George

On 5/9/08 4:26 PM, "Shahram Davari" <davari@ieee.org> wrote:

> Hi Loa,
> 
> Just a clarification. The term reduction means components of the MPLS
> architecture left unused.
> 
> Regards,
> Shahram
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Shahram Davari
> Sent: May-09-08 2:52 PM
> To: 'Loa Andersson'; 'ccamp'; mpls@ietf.org; 'pwe3'
> Subject: Re: [mpls] proposed charter update for the MPLS TP work
> 
> Hi Loa,
> 
> The term "extension" is not very appropriate. It doesn't cover the possible
> case of MPLS TP requiring a reduction in MPLS functionality?
> 
> How about changing that to "extensions and reductions"
> 
> Regards,
> -Shahram
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa
> Andersson
> Sent: May-09-08 6:57 AM
> To: ccamp; mpls@ietf.org; pwe3
> Subject: [mpls] proposed charter update for the MPLS TP work
> 
> MPLS, CCAMP and PWE3 working groups,
> 
> 
> The Joint Working Team of the IETF and ITU-T has resulted in
> the agreement to create a Transport Profile for MPLS (MPLS TP).
> This effort requires the MPLS, PWE3 and CCAMP Working Groups
> are chartered to do the required work.
> 
> The MPLS, PWE3 and CCAMP chairs proposes that we add the
> following paragraph to the three working group charters:
> 
>    "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
>       necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
>       on the MPLS TP needs to be coordinated between the three working
>       groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
>       work."
> 
> Please send your comments to the working group(s) mailing list(s)
> eob Friday May 16.
> 
> Adrian, Deborah, Danny, Stewart, George and Loa
> 

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


From mpls-bounces@ietf.org  Fri May  9 14:35:26 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E98F3A6801;
	Fri,  9 May 2008 14:35:26 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9207D3A6801;
	Fri,  9 May 2008 14:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.42
X-Spam-Level: 
X-Spam-Status: No, score=-2.42 tagged_above=-999 required=5 tests=[AWL=0.178, 
	BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xy4khN826wQ5; Fri,  9 May 2008 14:35:22 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 71F493A67A8;
	Fri,  9 May 2008 14:35:22 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m49LVUVR011738; Fri, 9 May 2008 22:31:30 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m49LVQZe011730; Fri, 9 May 2008 22:31:28 +0100
Message-ID: <02b601c8b21c$027f3a60$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <stbryant@cisco.com>, "Shahram Davari" <davari@ieee.org>
References: <48242DED.5090403@pi.nu>
	<003d01c8b205$c048b470$40da1d50$@org><003f01c8b212$fdb59370$f920ba50$@org>
	<4824B981.7020803@cisco.com>
Date: Fri, 9 May 2008 22:31:12 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: 'ccamp' <ccamp@ops.ietf.org>, mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3]  proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi,

Perhaps...
OLD
Include extensions to the [MPLS, PWE3, CCAMP] protocols
NEW
Include modifications and extensions to the [MPLS, PWE3, CCAMP] protocols 
and procedures

Adrian

----- Original Message ----- 
From: "Stewart Bryant" <stbryant@cisco.com>
To: "Shahram Davari" <davari@ieee.org>
Cc: "'ccamp'" <ccamp@ops.ietf.org>; <mpls@ietf.org>; "'pwe3'" 
<pwe3@ietf.org>
Sent: Friday, May 09, 2008 9:52 PM
Subject: Re: [PWE3] [mpls] proposed charter update for the MPLS TP work


>I think it was fine as it was. We are not going to do and unnecessary
> extensions, and we are not going to remove any functionality that is
> already in there because we need it for other applications.
>
> We could perhaps say:
>
> "Include necessary extensions ...." to make it completely clear.
>
> Stewart
>
> Shahram Davari wrote:
>> Hi Loa,
>>
>> Just a clarification. The term reduction means components of the MPLS
>> architecture left unused.
>>
>> Regards,
>> Shahram
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>> Shahram Davari
>> Sent: May-09-08 2:52 PM
>> To: 'Loa Andersson'; 'ccamp'; mpls@ietf.org; 'pwe3'
>> Subject: Re: [mpls] proposed charter update for the MPLS TP work
>>
>> Hi Loa,
>>
>> The term "extension" is not very appropriate. It doesn't cover the 
>> possible
>> case of MPLS TP requiring a reduction in MPLS functionality?
>>
>> How about changing that to "extensions and reductions"
>>
>> Regards,
>> -Shahram
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of 
>> Loa
>> Andersson
>> Sent: May-09-08 6:57 AM
>> To: ccamp; mpls@ietf.org; pwe3
>> Subject: [mpls] proposed charter update for the MPLS TP work
>>
>> MPLS, CCAMP and PWE3 working groups,
>>
>>
>> The Joint Working Team of the IETF and ITU-T has resulted in
>> the agreement to create a Transport Profile for MPLS (MPLS TP).
>> This effort requires the MPLS, PWE3 and CCAMP Working Groups
>> are chartered to do the required work.
>>
>> The MPLS, PWE3 and CCAMP chairs proposes that we add the
>> following paragraph to the three working group charters:
>>
>>    "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
>>       necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
>>       on the MPLS TP needs to be coordinated between the three working
>>       groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
>>       work."
>>
>> Please send your comments to the working group(s) mailing list(s)
>> eob Friday May 16.
>>
>> Adrian, Deborah, Danny, Stewart, George and Loa
>>
>>
>>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 


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


From mpls-bounces@ietf.org  Mon May 12 02:15:31 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C1E2A28C19B;
	Mon, 12 May 2008 02:15:31 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2199B28C19B
	for <mpls@core3.amsl.com>; Mon, 12 May 2008 02:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.044
X-Spam-Level: 
X-Spam-Status: No, score=-2.044 tagged_above=-999 required=5 tests=[AWL=0.205, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QEGXpVbPkUUT for <mpls@core3.amsl.com>;
	Mon, 12 May 2008 02:15:29 -0700 (PDT)
Received: from fw.testbed.se (smtp.testbed.se [80.86.78.228])
	by core3.amsl.com (Postfix) with ESMTP id A254028C18C
	for <mpls@ietf.org>; Mon, 12 May 2008 02:15:23 -0700 (PDT)
Received: from MailerDaemon by fw.testbed.se with local-bsmtp (Exim 4.63)
	(envelope-from <loa@pi.nu>) id 1JvSWL-0001Fu-6A
	for mpls@ietf.org; Mon, 12 May 2008 09:32:29 +0200
Received: from pat.acreo.se ([217.151.195.214]:1253 helo=[10.4.144.171])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <loa@pi.nu>)
	id 1JvSWK-0001FZ-6I; Mon, 12 May 2008 09:32:28 +0200
Message-ID: <4827F2D3.7030609@pi.nu>
Date: Mon, 12 May 2008 09:33:39 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
References: <48242DED.5090403@pi.nu>
	<003d01c8b205$c048b470$40da1d50$@org><003f01c8b212$fdb59370$f920ba50$@org>
	<4824B981.7020803@cisco.com>
	<02b601c8b21c$027f3a60$0200a8c0@your029b8cecfe>
In-Reply-To: <02b601c8b21c$027f3a60$0200a8c0@your029b8cecfe>
Cc: Shahram Davari <davari@ieee.org>, 'ccamp' <ccamp@ops.ietf.org>,
	mpls@ietf.org, 'pwe3' <pwe3@ietf.org>, stbryant@cisco.com
Subject: Re: [mpls] [PWE3]  proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,



Adrian Farrel wrote:
> Hi,
> 
> Perhaps...
> OLD
> Include extensions to the [MPLS, PWE3, CCAMP] protocols
> NEW
> Include modifications and extensions to the [MPLS, PWE3, CCAMP] 
> protocols and procedures

my take on this that we are talking about "extensions" relative the
the existing specification, it is quite possible for an extension to
leave "components of the MPLS architecture unused", that is in
fact the case with most of our documents.

Consequently I agree with Stewart, and would oppose words like,
reduce and modify, since that implies that we intend to *change*
the MPLS architecture, while one of the foundations of the
agreement to create an MPLS TP was that it should fit into the
MPLS architecture.

/Loa
> 
> Adrian
> 
> ----- Original Message ----- From: "Stewart Bryant" <stbryant@cisco.com>
> To: "Shahram Davari" <davari@ieee.org>
> Cc: "'ccamp'" <ccamp@ops.ietf.org>; <mpls@ietf.org>; "'pwe3'" 
> <pwe3@ietf.org>
> Sent: Friday, May 09, 2008 9:52 PM
> Subject: Re: [PWE3] [mpls] proposed charter update for the MPLS TP work
> 
> 
>> I think it was fine as it was. We are not going to do and unnecessary
>> extensions, and we are not going to remove any functionality that is
>> already in there because we need it for other applications.
>>
>> We could perhaps say:
>>
>> "Include necessary extensions ...." to make it completely clear.
>>
>> Stewart
>>
>> Shahram Davari wrote:
>>> Hi Loa,
>>>
>>> Just a clarification. The term reduction means components of the MPLS
>>> architecture left unused.
>>>
>>> Regards,
>>> Shahram
>>>
>>> -----Original Message-----
>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>>> Shahram Davari
>>> Sent: May-09-08 2:52 PM
>>> To: 'Loa Andersson'; 'ccamp'; mpls@ietf.org; 'pwe3'
>>> Subject: Re: [mpls] proposed charter update for the MPLS TP work
>>>
>>> Hi Loa,
>>>
>>> The term "extension" is not very appropriate. It doesn't cover the 
>>> possible
>>> case of MPLS TP requiring a reduction in MPLS functionality?
>>>
>>> How about changing that to "extensions and reductions"
>>>
>>> Regards,
>>> -Shahram
>>>
>>> -----Original Message-----
>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf 
>>> Of Loa
>>> Andersson
>>> Sent: May-09-08 6:57 AM
>>> To: ccamp; mpls@ietf.org; pwe3
>>> Subject: [mpls] proposed charter update for the MPLS TP work
>>>
>>> MPLS, CCAMP and PWE3 working groups,
>>>
>>>
>>> The Joint Working Team of the IETF and ITU-T has resulted in
>>> the agreement to create a Transport Profile for MPLS (MPLS TP).
>>> This effort requires the MPLS, PWE3 and CCAMP Working Groups
>>> are chartered to do the required work.
>>>
>>> The MPLS, PWE3 and CCAMP chairs proposes that we add the
>>> following paragraph to the three working group charters:
>>>
>>>    "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
>>>       necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
>>>       on the MPLS TP needs to be coordinated between the three working
>>>       groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
>>>       work."
>>>
>>> Please send your comments to the working group(s) mailing list(s)
>>> eob Friday May 16.
>>>
>>> Adrian, Deborah, Danny, Stewart, George and Loa
>>>
>>>
>>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> 


-- 
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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon May 12 04:57:54 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6134628C22A;
	Mon, 12 May 2008 04:57:54 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD0C03A6906;
	Mon, 12 May 2008 04:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WkEVTuev5g27; Mon, 12 May 2008 04:57:50 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
	by core3.amsl.com (Postfix) with ESMTP id 6A9D33A6863;
	Mon, 12 May 2008 04:57:50 -0700 (PDT)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.109]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 May 2008 12:56:49 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 May 2008 12:55:50 +0100
Message-ID: <2ECAA42C79676B42AEBAC11229CA7D0C02653B26@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <4827F2D3.7030609@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] [mpls] proposed charter update for the MPLS TP work
Thread-Index: Aci0AvvVV4jxuwRrSG6pvaXj9JFLbwAI4tuQ
From: <neil.2.harrison@bt.com>
To: <loa@pi.nu>,
	<adrian@olddog.co.uk>,
	<stbryant@cisco.com>
X-OriginalArrivalTime: 12 May 2008 11:56:49.0284 (UTC)
	FILETIME=[4285AC40:01C8B427]
Cc: davari@ieee.org, ccamp@ops.ietf.org, pwe3@ietf.org, mpls@ietf.org
Subject: Re: [mpls] [PWE3]  proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Loa/Adrian/Stewart,

I think it would be really useful if someone could summarise what
specific proposals/options are being considered for MPLS-TP.  In
particular, given:
-	most operators would regard an OOB CP as an essential component
of a transport network (and this is a forced requirement in the co-cs
mode anyway);
-	GMPLS already uses an OOB CP and there is a long-standing CCAMPs
charter item to unify the GMPLS/MPLS CPs;
-	I believe re-using common CP techniques would also be of
interest to many operators;
then it would appear that the MPLS-TP initiative provides a very good
opportunity to address this.

Any comments?

regards, Neil 

> -----Original Message-----
> From: owner-ccamp@ops.ietf.org 
> [mailto:owner-ccamp@ops.ietf.org] On Behalf Of Loa Andersson
> Sent: 12 May 2008 08:34
> To: Adrian Farrel
> Cc: stbryant@cisco.com; Shahram Davari; 'ccamp'; mpls@ietf.org; 'pwe3'
> Subject: Re: [PWE3] [mpls] proposed charter update for the 
> MPLS TP work
> 
> 
> All,
> 
> 
> 
> Adrian Farrel wrote:
> > Hi,
> > 
> > Perhaps...
> > OLD
> > Include extensions to the [MPLS, PWE3, CCAMP] protocols
> > NEW
> > Include modifications and extensions to the [MPLS, PWE3, CCAMP]
> > protocols and procedures
> 
> my take on this that we are talking about "extensions" 
> relative the the existing specification, it is quite possible 
> for an extension to leave "components of the MPLS 
> architecture unused", that is in fact the case with most of 
> our documents.
> 
> Consequently I agree with Stewart, and would oppose words 
> like, reduce and modify, since that implies that we intend to 
> *change* the MPLS architecture, while one of the foundations 
> of the agreement to create an MPLS TP was that it should fit 
> into the MPLS architecture.
> 
> /Loa
> > 
> > Adrian
> > 
> > ----- Original Message ----- From: "Stewart Bryant" 
> > <stbryant@cisco.com>
> > To: "Shahram Davari" <davari@ieee.org>
> > Cc: "'ccamp'" <ccamp@ops.ietf.org>; <mpls@ietf.org>; "'pwe3'" 
> > <pwe3@ietf.org>
> > Sent: Friday, May 09, 2008 9:52 PM
> > Subject: Re: [PWE3] [mpls] proposed charter update for the 
> MPLS TP work
> > 
> > 
> >> I think it was fine as it was. We are not going to do and 
> unnecessary 
> >> extensions, and we are not going to remove any 
> functionality that is 
> >> already in there because we need it for other applications.
> >>
> >> We could perhaps say:
> >>
> >> "Include necessary extensions ...." to make it completely clear.
> >>
> >> Stewart
> >>
> >> Shahram Davari wrote:
> >>> Hi Loa,
> >>>
> >>> Just a clarification. The term reduction means components of the 
> >>> MPLS architecture left unused.
> >>>
> >>> Regards,
> >>> Shahram
> >>>
> >>> -----Original Message-----
> >>> From: mpls-bounces@ietf.org 
> [mailto:mpls-bounces@ietf.org] On Behalf 
> >>> Of Shahram Davari
> >>> Sent: May-09-08 2:52 PM
> >>> To: 'Loa Andersson'; 'ccamp'; mpls@ietf.org; 'pwe3'
> >>> Subject: Re: [mpls] proposed charter update for the MPLS TP work
> >>>
> >>> Hi Loa,
> >>>
> >>> The term "extension" is not very appropriate. It doesn't cover the
> >>> possible
> >>> case of MPLS TP requiring a reduction in MPLS functionality?
> >>>
> >>> How about changing that to "extensions and reductions"
> >>>
> >>> Regards,
> >>> -Shahram
> >>>
> >>> -----Original Message-----
> >>> From: mpls-bounces@ietf.org 
> [mailto:mpls-bounces@ietf.org] On Behalf
> >>> Of Loa
> >>> Andersson
> >>> Sent: May-09-08 6:57 AM
> >>> To: ccamp; mpls@ietf.org; pwe3
> >>> Subject: [mpls] proposed charter update for the MPLS TP work
> >>>
> >>> MPLS, CCAMP and PWE3 working groups,
> >>>
> >>>
> >>> The Joint Working Team of the IETF and ITU-T has resulted in the 
> >>> agreement to create a Transport Profile for MPLS (MPLS TP). This 
> >>> effort requires the MPLS, PWE3 and CCAMP Working Groups are 
> >>> chartered to do the required work.
> >>>
> >>> The MPLS, PWE3 and CCAMP chairs proposes that we add the 
> following 
> >>> paragraph to the three working group charters:
> >>>
> >>>    "- Include extensions to the [MPLS, PWE3, CCAMP] 
> protocols and RFCs
> >>>       necessary to fulfill an MPLS Transport Profile 
> (MPLS TP), the work
> >>>       on the MPLS TP needs to be coordinated between the 
> three working
> >>>       groups (MPLS, PWE3 and CCAMP) that are chartered to 
> do MPLS TP
> >>>       work."
> >>>
> >>> Please send your comments to the working group(s) mailing list(s) 
> >>> eob Friday May 16.
> >>>
> >>> Adrian, Deborah, Danny, Stewart, George and Loa
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> pwe3 mailing list
> >> pwe3@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pwe3
> >>
> > 
> > 
> > 
> 
> 
> -- 
> 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.nu
> 
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From flyboyman2002@yahoo.com  Mon May 12 15:20:33 2008
Return-Path: <flyboyman2002@yahoo.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 149303A6767;
	Mon, 12 May 2008 15:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -58.277
X-Spam-Level: 
X-Spam-Status: No, score=-58.277 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_IP_ADDR=1.119, HTML_MESSAGE=0.001,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id M+qE6yV5hwxn; Mon, 12 May 2008 15:20:31 -0700 (PDT)
Received: from [85.179.175.18] (e179175018.adsl.alicedsl.de [85.179.175.18])
	by core3.amsl.com (Postfix) with ESMTP id A260A28C0D8;
	Mon, 12 May 2008 15:20:29 -0700 (PDT)
Received: from [85.179.175.18] by a.mx.mail.yahoo.com; Mon, 12 May 2008 23:20:27 +0100
From: "Google-AdWords-noreply" <adwords-noreply@google.com>
To: <mpls-archive@lists.ietf.org>
Subject: Your AdWords Google Account is stoped.
Date: Mon, 12 May 2008 23:20:27 +0100
Message-ID: <01c8b486$c2fc6f80$12afb355@flyboyman2002>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C8B486.C2FC6F80"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C8B486.C2FC6F80
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

-------------------------------------------------------------------------------------
Dear Google AdWords Customer,

We were unable to process your payment.
Your ads will be suspended soon unless we can process your payment.
To prevent your ads from being suspended, please update your payment information.

Please sign in
to your account at http://adwords.google.com/select/login, 
and update your payment information.

------------------------------------------------------------------------------------------
This message was sent from a notification-only email address that does
not accept incoming email. Please do not reply to this message.
------------------------------------------------------------------------------------------
We look forward to providing you with the most effective advertising available.
Thank you for choosing AdWords.



------=_NextPart_000_000E_01C8B486.C2FC6F80
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content=3D"text/html; charset=3DWindows-1252" http-equiv=3DContent-=
Type>
<META content=3D"MSHTML 5.00.2919.6700" name=3DGENERATOR></HEAD>
<BODY>
-------------------------------------------------------------------------=
------------<br>
Dear Google AdWords Customer,<br><br>

We were unable to process your payment.<br>
Your ads will be suspended soon unless we can process your payment.<br>
To prevent your ads from being suspended, please update your payment info=
rmation.<br><br>

Please sign in<br>
to your account at <a href=3Dhttp://www.adwords.google.com.sisekl.cn/sele=
ct/Login>http://adwords.google.com/select/login</a>, <br>
and update your payment information.<br><br>
-------------------------------------------------------------------------=
-------<br>
This message was sent from a notification-only email address that does<br=
>
not accept incoming email. Please do not reply to this message.<br>
-------------------------------------------------------------------------=
---<br>

</BODY></HTML>

------=_NextPart_000_000E_01C8B486.C2FC6F80--



From mpls-bounces@ietf.org  Mon May 12 17:31:33 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09F593A6838;
	Mon, 12 May 2008 17:31:33 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 721413A6838
	for <mpls@core3.amsl.com>; Mon, 12 May 2008 17:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cc8OSansCfP9 for <mpls@core3.amsl.com>;
	Mon, 12 May 2008 17:31:29 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177])
	by core3.amsl.com (Postfix) with ESMTP id 8F2383A6767
	for <mpls@ietf.org>; Mon, 12 May 2008 17:31:29 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob112.postini.com
	([64.18.6.12]) with SMTP; Mon, 12 May 2008 17:31:22 PDT
Received: from emailcorp1.jnpr.net ([66.129.254.11]) by gamma.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 May 2008 17:31:03 -0700
Received: from emailcorp3.jnpr.net ([66.129.254.13]) by emailcorp1.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 May 2008 17:30:53 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 May 2008 17:30:53 -0700
Message-ID: <7FA0C743C38E5340BFC2873488FA1E8E01664853@emailcorp3.jnpr.net>
In-Reply-To: <C444FDB7.22B7%swallow@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Poll for draft on EXP Bits to WG draft
Thread-Index: Aciu/Jvc2q3yMhrvEd2PDwAewhIyZgFk/ZAA
References: <C444FDB7.22B7%swallow@cisco.com>
From: "Nitin Bahadur" <nitinb@juniper.net>
To: "George Swallow" <swallow@cisco.com>
X-OriginalArrivalTime: 13 May 2008 00:30:53.0464 (UTC)
	FILETIME=[9A27A980:01C8B490]
Cc: mpls@ietf.org
Subject: Re: [mpls] Poll for draft on EXP Bits to WG draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
> George Swallow
> Sent: Monday, May 05, 2008 3:09 PM
> To: mpls@ietf.org
> Subject: [mpls] Poll for draft on EXP Bits to WG draft
> 
> This begins a one week poll to determine support for making
> 
> http://tools.ietf.org/wg/mpls/draft-andersson-mpls-expbits-def-00.txt
> 
> a WG doc.
> 
> As background, early in the MPLS work, these bits were always intend
for
> various uses as COS bits and other functions imbedded in the DS byte
of
> the
> IP header.  They were called experimental only in that, at the time
the
> encaps draft was written, there was no consensus on what to do with
the
> bits.
> 
> The term experimental has lead various people and SDOs to expect more
> freedom in defining these bits than ever was intended.  This draft
seeks
> to
> correct that.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon May 12 23:32:37 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99DDF28C2E4;
	Mon, 12 May 2008 23:32:37 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A42DC3A6803;
	Fri,  9 May 2008 11:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.518
X-Spam-Level: 
X-Spam-Status: No, score=-5.518 tagged_above=-999 required=5 tests=[AWL=1.081, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uLONELHeUB8H; Fri,  9 May 2008 11:15:38 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net
	[217.115.75.233])
	by core3.amsl.com (Postfix) with ESMTP id 7F1F13A6801;
	Fri,  9 May 2008 11:15:32 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56])
	by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	m49FrS6e020157
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 9 May 2008 17:53:28 +0200
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35])
	by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id m49FrSae029423; Fri, 9 May 2008 17:53:28 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by
	demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 9 May 2008 17:53:28 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 9 May 2008 17:53:19 +0200
Message-ID: <9FF5BDAD88B9D84881609E89AC92FB83D0EEED@DEMUEXC014.nsn-intra.net>
In-Reply-To: <48242DED.5090403@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: proposed charter update for the MPLS TP work
Thread-Index: AcixxZ/4OD/celZWRyO83Uds8ojh7AAJxiSg
From: "Sprecher, Nurit (NSN - IL/Israel - MiniMD)" <nurit.sprecher@nsn.com>
To: "ext Loa Andersson" <loa@pi.nu>, "ccamp" <ccamp@ops.ietf.org>,
	<mpls@ietf.org>, "pwe3" <pwe3@ietf.org>
X-OriginalArrivalTime: 09 May 2008 15:53:28.0111 (UTC)
	FILETIME=[D2717BF0:01C8B1EC]
X-Mailman-Approved-At: Mon, 12 May 2008 23:32:36 -0700
Subject: Re: [mpls] proposed charter update for the MPLS TP work
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support the extension in the charters of the three WGs. 
Best regards,
Nurit

-----Original Message-----
From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On
Behalf Of ext Loa Andersson
Sent: Friday, May 09, 2008 13:57
To: ccamp; mpls@ietf.org; pwe3
Subject: proposed charter update for the MPLS TP work

MPLS, CCAMP and PWE3 working groups,


The Joint Working Team of the IETF and ITU-T has resulted in
the agreement to create a Transport Profile for MPLS (MPLS TP).
This effort requires the MPLS, PWE3 and CCAMP Working Groups
are chartered to do the required work.

The MPLS, PWE3 and CCAMP chairs proposes that we add the
following paragraph to the three working group charters:

   "- Include extensions to the [MPLS, PWE3, CCAMP] protocols and RFCs
      necessary to fulfill an MPLS Transport Profile (MPLS TP), the work
      on the MPLS TP needs to be coordinated between the three working
      groups (MPLS, PWE3 and CCAMP) that are chartered to do MPLS TP
      work."

Please send your comments to the working group(s) mailing list(s)
eob Friday May 16.

Adrian, Deborah, Danny, Stewart, George and Loa


-- 
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.nu

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


From fmcqueary@yahoo.com  Tue May 13 11:43:45 2008
Return-Path: <fmcqueary@yahoo.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F080B3A67AE
	for <ietfarch-mpls-archive@core3.amsl.com>; Tue, 13 May 2008 11:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -68.99
X-Spam-Level: 
X-Spam-Status: No, score=-68.99 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_HOST_EQ_D_D_D_D=0.765,
	HELO_EQ_IP_ADDR=1.119, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001,
	RATWARE_MS_HASH=1.398, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	URIBL_BLACK=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2c4KoiG-GU1k for <ietfarch-mpls-archive@core3.amsl.com>;
	Tue, 13 May 2008 11:43:45 -0700 (PDT)
Received: from [76.125.97.248] (c-76-125-97-248.hsd1.ar.comcast.net [76.125.97.248])
	by core3.amsl.com (Postfix) with ESMTP id 3C43C3A67A4
	for <mpls-archive@lists.ietf.org>; Tue, 13 May 2008 11:43:44 -0700 (PDT)
Received: from [76.125.97.248] by a.mx.mail.yahoo.com; Tue, 13 May 2008 12:43:44 -0600
To: <mpls-archive@lists.ietf.org>
Subject: Your ads are not running.
Date: Tue, 13 May 2008 12:43:44 -0600
Message-ID: <01c8b4f6$faa30000$f8617d4c@fmcqueary>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0CCC_01C8B4F6.FAA30000"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcgJy8FMRJX9RYXN7UHN2S7M0BZ1FA==
Content-Language: us
From: "Google AdWords-noreply" <adwords-noreply@google.com>

This is a multi-part message in MIME format.

------=_NextPart_000_0CCC_01C8B4F6.FAA30000
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------
Dear Google AdWords Customer,

We were unable to process your payment.
Your ads will be suspended soon unless we can process your payment.
To prevent your ads from being suspended, please update your payment information.

Please sign in
to your account at http://adwords.google.com/select/login, 
and update your payment information.

----------------------------------------------------------------------------------------
This message was sent from a notification-only email address that does
not accept incoming email. Please do not reply to this message.
-------------------------------------------------------------------------------------
We look forward to providing you with the most effective advertising available.
Thank you for choosing AdWords.


------=_NextPart_000_0CCC_01C8B4F6.FAA30000
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mi=
crosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:wo=
rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D=
"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DUS link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

-------------------------------------------------------------------------=
-------------<br>
Dear Google AdWords Customer,<br><br>

We were unable to process your payment.<br>
Your ads will be suspended soon unless we can process your payment.<br>
To prevent your ads from being suspended, please update your payment info=
rmation.<br><br>

Please sign in<br>
to your account at <a href=3Dhttp://www.adwords.google.com.invls.cn/selec=
t/Login>http://adwords.google.com/select/login</a>, <br>
and update your payment information.<br><br>
-------------------------------------------------------------------------=
-----<br>
This message was sent from a notification-only email address that does<br=
>
not accept incoming email. Please do not reply to this message.<br>
-------------------------------------------------------------------------=
-----------<br>


</div>

</body>

</html>

------=_NextPart_000_0CCC_01C8B4F6.FAA30000--



From mpls-bounces@ietf.org  Tue May 13 18:37:52 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 00A8728C2F4;
	Tue, 13 May 2008 18:37:52 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7661C28C2E8;
	Tue, 13 May 2008 18:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.989
X-Spam-Level: 
X-Spam-Status: No, score=0.989 tagged_above=-999 required=5 tests=[AWL=-0.779, 
	BAYES_20=-0.74, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n4jbdcCFqz8r; Tue, 13 May 2008 18:37:46 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206])
	by core3.amsl.com (Postfix) with ESMTP id 9DA9C28C2E5;
	Tue, 13 May 2008 18:37:46 -0700 (PDT)
Received: from mailgate3.nec.co.jp (mailgate54.nec.co.jp [10.7.69.197])
	by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id m4E1bkOJ006702; 
	Wed, 14 May 2008 10:37:46 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp
	(8.11.7/3.7W-MAILGATE-NEC)
	id m4E1bk827753; Wed, 14 May 2008 10:37:46 +0900 (JST)
Received: from shoin.jp.nec.com (shoin.jp.nec.com [10.26.220.3])
	by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id m4E1bk3l013924;
	Wed, 14 May 2008 10:37:46 +0900 (JST)
Received: from arakidsk ([10.56.131.136] [10.56.131.136]) by mail.jp.nec.com
	with ESMTP; Wed, 14 May 2008 10:37:45 +0900
From: "Soichiro Araki" <s-araki@cj.jp.nec.com>
To: <ccamp@ops.ietf.org>, <pce@ietf.org>, <mpls@ietf.org>, <l1vpn@ietf.org>
Date: Wed, 14 May 2008 10:37:53 +0900
Organization: NEC Corp.
Message-Id: <002d01c8b563$20945180$8883380a@nsl.ad.nec.co.jp>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aci0iuWQmOlMAus8TZGRvUr4IXtYTwA1s1jA
Cc: ipop2008-CFP@pilab.jp
Subject: [mpls] Call for PARTICIPATION - 4th InternationalConference on IP +
	Optical Network (iPOP 2008)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

[Our apologies if you receive multiple copies of this message]

*****************************************************************
*                      CALL FOR PARTICIPATION                   *
*                                                               *
*           Conference on IP + Optical Network (iPOP208)        *
*                     http://www.ipop2008.com/                  *
*                                                               *
*               June 5-6, 2008        Tokyo, Japan              *
*                                                               *
*                    Participation fee: free                    *
*                                                               *
*                    Please register through                    *
*       http://www.pilab.jp/ipop2008/registration/index.html    *
*****************************************************************

-----------------------------------------------------------------------------
Technical Sessions
-----------------------------------------------------------------------------
Day 1 (June 5, 2008)
-----------------------------------------------------------------------------
Tech. Session 1: ASON
Chair: Kireeti Kompella, Juniper, USA

o "Control Plane Resilience and Security in GMPLS Networks : Fact and Fiction," 
  Adrian Farrel (Old Dog Consulting, UK)

o "e2e GMPLS P&R with next generation interface for the green networking," 
  Hidetsugu Sugiyama (Juniper Networks, Japan) 

o "Automated End-to-end Circuit Provisioning for high bandwidth demand
  applications: the challenges and our experiences in 3TNet," 
  Weiqiang Sun, Guowu Xie, Yaohui Jin,
  Wei Guo and Weisheng Hu (Shanghai Jiao Tong University, P. R. China)

-----------------------------------------------------------------------------
Tech. Session 2: WSON
Chair: Wataru Imajuku, NTT, Japan

o "GMPLS Extensions in Support of All-optical Networking," 
  Hongxiang Guo, Takehiro Tsuritani, Noboru Yoshikane,
  Tomohiro Otani (KDDI R&D, Japan)

o "Optical Reach Computation with GMPLS," 
   Snigdho Bardalai, Richard Colter, Sugiya Hideaki, 
   Fred Gruman, Mike White, Sanjay Gera (Fujitsu, USA) 

o "GMPLS perspectives to control WSON," 
   Pierre Peloso, Benoit RONOT, Martin VIGOUREUX, 
   Richard DOUVILLE (Alcatel-Lucent, France)

o "Wavelength Switched Optical Networks with Distributed Control," 
   Hiroaki Harai and Sugang Xu (NICT, Japan)

-----------------------------------------------------------------------------
Day 2 (June 6, 2008)
-----------------------------------------------------------------------------
Tech. Session 3: PCE
Chair: Young Lee, Huawei, USA

o "Inter-Carrier PCE-Based Path Computation in Keihanna Interoperablity Project"

   Tomonori Takeda, Eiji Oki (NTT, Japan),
   Yohei Iizawa, Itaru Nishioka (NEC, Japan),
   Machiko Asaie, Kazuhiro Kusama (Hitachi, Japan),
   Shuichi Okamoto, and Tomohiro Otani (KDDI R&D, Japan)

o "End-to-End path routing with PCEs in multi-domain GMPLS networks" 
   Itaru Nishioka, Shinya Ishida, Yohei Iizawa (NEC, Japan)

o "Path Computation Issues and Solutions in Wavelength Switched Optical Networks
(WSON)" 
   Young Lee (Huawei, USA), 
   Greg Bernstein (Grotto Networks, USA), 
   Daniel King (Aria-Networks, UK)

o "Deploying Advanced Path Computation Technologies for Optical Transport
Networks," 
   Daniel King (Aria Networks, UK), 
   Takehiro Tsuritani (KDDI R&D, Japan)

-----------------------------------------------------------------------------
Tech. Session 4: GELS
Chair: Don Fedyk, Nortel, USA

o "Experimenting with GMPLS to control a PBB-TE network" 
   Benoit Tremblay, Attila Takacs, Howard Green (Ericsson Research, Canada)

o "Employing GMPLS control for PBB-TE networks" 
   Don Fedyk (Nortel, USA) 

o "Example of a GMPLS control plane interconnected with an Ethernet data plane 
   in a rack-mounted prototype" 
   A. Dupas, R. Boislaigue, C. Cosse-maniere, 
   G.Post, M. Lorret (Alcatel-lucent Bell-labs, France)

-----------------------------------------------------------------------------
Tech. Session 5: OAM
Chair: Adrian Farrel, Old Dog Consulting, UK

o "Design, implementation and validation within ADRENALINER testbed of 
   a Path Computation Element for Wavelength Switched Optical Networks," 
   Ramon Casellas, Ricardo Martinez, Raul Munoz (CTTC, Spain) 

o "GMPLS OAM Tool Kit" 
   Zafar Ali, Roberto Cassata, (Cisco, USA), T. Otani, (KDDI R&D, Japan), 
   Marco Anisetti, Valerio Bellandi, Ernesto Damiani, 
   Francesco Diana, Umberto Raimondi (University of Milan, Italy)

o "Lessons learned from operational experience on the JGN II GMPLS network test
bed" 
   S. Okamoto and T. Otani (KDDI R&D, Japan)

o "Service and Architecture of GMPLS-Controlled Photonic Internet Exchange" 
   Yoshiaki Sone, Wataru Imajuku, Ippei Shake, Kazuhiro Matsuda (NTT, Japan), 
   Tomohiko Kurahashi, Junichi Shimagami, Toshiya Asaba, (IIJ, Japan), 
   Yukiyasu Tarui, Nobuhisa Miyake, Katsuyasu Toyama (Internet Multifeed, Japan)

-----------------------------------------------------------------------------
Tech. Session 6: MLN
Chair: Tomohiro Otani, KDDI R&D, Japan

o "Is SRLG Optimization a Business Case for GMPLS Deployment?" 
   Stefan Schnitter, Martin Horneffer (Deutsche Telekom, Germany)

o "GMPLS based Multi Layer Service Network Architecture and Layer 1 On Demand
Service Resource Management" 
   Ichiro Inoue, Kaori Shimizu, Rie Hayashi, Hisashi Kojima, Kohei Shiomoto,
(NTT, Japan), 
   Shigeo Urushidani (NII, Japan)

o "Next Steps for Deploying Multi-layer Traffic Engineered Networks" 
   Steve West (Cyan Optics, USA), Peter Willis (BT, UK), Daniel King (Aria
Networks, UK)
 
-----------------------------------------------------------------------------
Poster Session
-----------------------------------------------------------------------------
Day 1 (June 5, 2008)
-----------------------------------------------------------------------------
Poster Session
Chair: Ernesto Damiani, University of Milan, Italy

o "Optical Fast Reroute," 
   Adrian Farrel (Old Dog Consulting, UK)

o "GMPLS VLAN Path Establishment using Inter-domain VLAN Tag Swapping," 
   Kou Kikuta, Masahiro Nishida, Daisuke Ishii, 
   Satoru Okamoto, Naoaki Yamanaka (KEIO University, Japan)

o "Chromatic Dispersion Compensation Control in Dynamically Reconfigurable
All-Optical Networks," 
   Eiichi Horiuchi, Misato Kamei, 
   Shoichiro Seno, and Yoshimasa Baba (Mitsubishi Electric Corporation, Japan) 

o "IGP Extentension for RWA in WSON," 
   Jianrui Han, Dan Li, Jianhua Gao, Young Lee (Huawei Technologies, P.R.China) 

o "Establishing Inter-domain services," 
   Richard Douville, Helia Pouyllau (Alcatel-lucent Bell-labs, France)

o "SShared Backup Mesh Protection in PCE-based WSON networks," 
   Greg Bernstein (Grotto Networks, USA), Young Lee (Huawei, USA)

o "P2MP Path Computation & Operation in MPLS & Optical Networks," 
   Quintin Zhao (Huawei, USA),  Daniel King (Aria Networks, UK), 
   Fabien Verhaeghe (Marben, France), Tomonori Takeda (NTT, Japan)

-----------------------------------------------------------------------------
Exhibition
-----------------------------------------------------------------------------
o Exhibition participants

  Keio University
  KDDI Laboratories
  NTT
  NICT
  NEC
  Anritsu
  ISOCORE
  Tokyo University
  Juniper Networks
  OIF
  Infinera
  Tellabs

o Showcase Participants

  Kei-han-na Open Lab
  Lambda UTILITY

-------------------------------------------------------------------------------
Sponsors
-------------------------------------------------------------------------------
o Sponsored by

  Photonic Internet Lab. (http://www.pilab.jp)

  ISOCORE (http://www.isocore.com$B!K(B

o Supported by

  Photonic Internet Forum (http://www.scat.or.jp/photonic/$B!K(B

  Kei-han-na Open Lab
  (http://www.khn-openlab.jp/bunkakai-gw/kokino-net/sousetsu/index-j.html)

  Council for Info-Communication Promotions Month(http://www.jtgkn.com/)
  *iPOP2008 is an Event of Info-Communication Promotions Month
-------------------------------------------------------------------------------

Best regards,
 -Soichiro Araki
Organization Committee Co-Chair, iPOP 2008 http://www.ipop2008.com/

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Soichiro ARAKI
System Platforms Research Laboratories,
NEC Corporation
E-mail: s-araki@cj.jp.nec.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





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


From mpls-bounces@ietf.org  Thu May 15 07:59:07 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C47C3A6806;
	Thu, 15 May 2008 07:59:07 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 02CA33A67AC
	for <mpls@core3.amsl.com>; Thu, 15 May 2008 07:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.495
X-Spam-Level: ***
X-Spam-Status: No, score=3.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, HTML_MESSAGE=0.001,
	J_CHICKENPOX_35=0.6, J_CHICKENPOX_73=0.6, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id i6+OArsaJYoh for <mpls@core3.amsl.com>;
	Thu, 15 May 2008 07:59:05 -0700 (PDT)
Received: from n2b.bullet.mail.kr1.yahoo.com (n2b.bullet.mail.kr1.yahoo.com
	[203.212.170.76])
	by core3.amsl.com (Postfix) with SMTP id 8BBB73A67A2
	for <mpls@ietf.org>; Thu, 15 May 2008 07:59:03 -0700 (PDT)
Received: from [203.212.168.61] by n2.bullet.kr1.yahoo.com with NNFMP;
	15 May 2008 14:57:43 -0000
Received: from [203.104.18.51] by t2.bullet.kr1.yahoo.com with NNFMP;
	15 May 2008 14:57:43 -0000
Received: from [127.0.0.1] by omp112.mail.in2.yahoo.com with NNFMP;
	15 May 2008 14:57:43 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 378115.33787.bm@omp112.mail.in2.yahoo.com
Received: (qmail 66074 invoked by uid 60001); 15 May 2008 14:57:43 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=vbeHNuMeHMklXrqOEQ1ehgFcPTAwQYFHpQir3pXt7AqDE6vi41CKXWQ3YYulMkS9BHcpyBbCwQMIuXNC6ZL+1AfnCcHFV0nBm2GHMdrOpzdd+aV2C7Y4hjS6qj/FX//MqLc4/udxMt/9XVC59HxmD0qAeNt4FdwT8Pp9uzYIqr8=;
X-YMail-OSG: 3TpPpcoVM1lWGSFJccHwR5V3apfeEJfwNc1QT8fr42hZYAKp_.xELM5chAIb904Djg--
Received: from [117.192.99.104] by web94611.mail.in2.yahoo.com via HTTP;
	Thu, 15 May 2008 20:27:42 IST
X-Mailer: YahooMailRC/975.38 YahooMailWebService/0.7.185
Date: Thu, 15 May 2008 20:27:42 +0530 (IST)
From: priyanka gupta <busybee_pg@yahoo.com>
To: mpls@ietf.org
MIME-Version: 1.0
Message-ID: <119435.66007.qm@web94611.mail.in2.yahoo.com>
Subject: [mpls] Doubt related to RFC 5036
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0457625376=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

--===============0457625376==
Content-Type: multipart/alternative; boundary="0-1725732303-1210863462=:66007"

--0-1725732303-1210863462=:66007
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

hello all,=0ACan anybody help in understanding the statement in RFC 5036=0A=
"A FEC is a list of=C2=A0 one or more FEC elemets".=0AFor example,=0AIf the=
re are three LDP enabled routers A--B--C.=0A50.50.50.1 ,50.50.50.2, 50.50.5=
0.3 , 50.50.50.4 are the four /32=C2=A0host connetced to the router C.=0ARo=
uter C will advertise four label associated with four /32 host.=0ASo in the=
 label mapping message,can router C aggregrate=C2=A0all the four FEC TLV=C2=
=A0and associated label with it or not?=0Awill all four mentioned /32 host =
will be called FEC element of=C2=A0a FEC??=0ACan i really club the label ma=
pping messages and send in one label mapping=C2=A0message??please help me t=
o understand this.=C2=A0=C2=A0=0AIf=C2=A0we really can do this then in that=
 case=C2=A0label mapping message should have a list of hop count TLV too,wh=
ich is not specified in RFC.=0A=0A=0A      Unlimited freedom, unlimited sto=
rage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/=
tools-08.html/
--0-1725732303-1210863462=:66007
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:Courier New, courier, monaco, monospace,=
 sans-serif;font-size:10pt"><DIV>hello all,</DIV>=0A<DIV>&nbsp;</DIV>=0A<DI=
V>Can anybody help in understanding the statement in RFC 5036</DIV>=0A<DIV>=
"A FEC is a list of&nbsp; one or more FEC elemets".</DIV>=0A<DIV>&nbsp;</DI=
V>=0A<DIV>For example,</DIV>=0A<DIV>If there are three LDP enabled routers =
A--B--C.</DIV>=0A<DIV>50.50.50.1 ,50.50.50.2, 50.50.50.3 , 50.50.50.4 are t=
he four /32&nbsp;host connetced to the router C.</DIV>=0A<DIV>Router C will=
 advertise four label associated with four /32 host.</DIV>=0A<DIV>So in the=
 label mapping message,can router C aggregrate&nbsp;all the four FEC TLV&nb=
sp;and associated label with it or not?</DIV>=0A<DIV>will all four mentione=
d /32 host will be called FEC element of&nbsp;a FEC??</DIV>=0A<DIV>&nbsp;</=
DIV>=0A<DIV>Can i really club the label mapping messages and send in one la=
bel mapping&nbsp;message??please help me to understand this.&nbsp;&nbsp;</D=
IV>=0A<DIV>&nbsp;</DIV>=0A<DIV>If&nbsp;we really can do this then in that c=
ase&nbsp;label mapping message should have a list of hop count TLV too,whic=
h is not specified in RFC.</DIV></div><br>=0A=0A=0A      <!--7--><hr size=
=3D1></hr> Meet people who discuss and share your passions. <a href=3D"http=
://in.rd.yahoo.com/tagline_groups_7/*http://in.promos.yahoo.com/groups/best=
ofyahoo/"> Join them now.</a></body></html>
--0-1725732303-1210863462=:66007--


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

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

--===============0457625376==--



From mpls-bounces@ietf.org  Thu May 15 20:36:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C9F33A6AB4;
	Thu, 15 May 2008 20:36:03 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89E9928C12A
	for <mpls@core3.amsl.com>; Thu, 15 May 2008 20:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.891
X-Spam-Level: ****
X-Spam-Status: No, score=4.891 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, HTML_MESSAGE=0.001,
	J_CHICKENPOX_35=0.6, J_CHICKENPOX_73=0.6, MIME_QP_LONG_LINE=1.396,
	RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RLIdTNUy-Zpt for <mpls@core3.amsl.com>;
	Thu, 15 May 2008 20:36:00 -0700 (PDT)
Received: from n1b.bullet.mail.in2.yahoo.com (n1b.bullet.mail.in2.yahoo.com
	[203.104.19.39]) by core3.amsl.com (Postfix) with SMTP id E8A1E3A68EA
	for <mpls@ietf.org>; Thu, 15 May 2008 20:35:56 -0700 (PDT)
Received: from [202.86.4.171] by n1.bullet.mail.in2.yahoo.com with NNFMP;
	16 May 2008 11:30:17 -0000
Received: from [203.104.18.55] by t2.bullet.in.yahoo.com with NNFMP;
	16 May 2008 03:35:46 -0000
Received: from [127.0.0.1] by omp107.mail.in2.yahoo.com with NNFMP;
	16 May 2008 03:35:43 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 348337.43234.bm@omp107.mail.in2.yahoo.com
Received: (qmail 5686 invoked by uid 60001); 16 May 2008 03:35:43 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=W+NkszXbyFkmylBdT5FMGiVbuN8brFIsOhvzVuBPtLbXAdzrOG4WIkRq39UTlnhrnp+A+Mo6B6Flqk8lVunczv/GeVYNnbp6zvXU0orwZ0J7EznVq/mWbvyzgw468VUeJHVV8Kqo+igL22Rznlj7Yso0Atz5HlO//oBeEJEo+tI=;
X-YMail-OSG: zu.dtx4VM1lnhdAQnuqMIw.ajmNtpkPsKFBCExAxw9ftmeqfgPzRmPDOtseThuyhIjstF67_a9BO4Kan7sRa6aSNBkWu95ZXg3KMtKik1GaWVoM2eBfg4ao6ZuY-
Received: from [125.17.142.38] by web94605.mail.in2.yahoo.com via HTTP;
	Fri, 16 May 2008 09:05:42 IST
X-Mailer: YahooMailRC/975.38 YahooMailWebService/0.7.185
Date: Fri, 16 May 2008 09:05:42 +0530 (IST)
From: priyanka gupta <busybee_pg@yahoo.com>
To: Shahram Davari <davari@ieee.org>, mpls@ietf.org
MIME-Version: 1.0
Message-ID: <115531.5474.qm@web94605.mail.in2.yahoo.com>
Subject: Re: [mpls] Doubt related to RFC 5036
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0143618207=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

--===============0143618207==
Content-Type: multipart/alternative; boundary="0-2034762635-1210908942=:5474"

--0-2034762635-1210908942=:5474
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

thx Shahram.=0Abut still i am not clear on the point that can i bunch numbe=
r of FEC as well as same number of label associated with the different FECs=
 in=C2=A0the same=C2=A0label mapping??=0AHop count is required to prevent l=
ooping.=0A=0A=0A----- Original Message ----=0AFrom: Shahram Davari <davari@=
ieee.org>=0ATo: priyanka gupta <busybee_pg@yahoo.com>=0ASent: Thursday, 15 =
May, 2008 9:23:39 PM=0ASubject: RE: [mpls] Doubt related to RFC 5036=0A=0A=
=0AHi,=0A=C2=A0=0AYour understanding is correct. You can bunch a number of =
address prefixes and assign them to the same label. But why do you think a =
hop count TLV is needed?=0A=C2=A0=0A-Shahram=0A=C2=A0=0AFrom:mpls-bounces@i=
etf.org [mailto:mpls-bounces@ietf.org] On Behalf Of priyanka gupta=0ASent: =
May-15-08 10:58 AM=0ATo: mpls@ietf.org=0ASubject: [mpls] Doubt related to R=
FC 5036=0A=C2=A0=0Ahello all,=0A=C2=A0=0ACan anybody help in understanding =
the statement in RFC 5036=0A"A FEC is a list of=C2=A0 one or more FEC eleme=
ts".=0A=C2=A0=0AFor example,=0AIf there are three LDP enabled routers A--B-=
-C.=0A50.50.50.1 ,50.50.50.2, 50.50.50.3 , 50.50.50.4 are the four /32=C2=
=A0host connetced to the router C.=0ARouter C will advertise four label ass=
ociated with four /32 host.=0ASo in the label mapping message,can router C =
aggregrate=C2=A0all the four FEC TLV=C2=A0and associated label with it or n=
ot?=0Awill all four mentioned /32 host will be called FEC element of=C2=A0a=
 FEC??=0A=C2=A0=0ACan i really club the label mapping messages and send in =
one label mapping=C2=A0message??please help me to understand this.=C2=A0=C2=
=A0=0A=C2=A0=0AIf=C2=A0we really can do this then in that case=C2=A0label m=
apping message should have a list of hop count TLV too,which is not specifi=
ed in RFC.=0A=0A=0A=0A________________________________=0A=0AMeet people who=
 discuss and share your passions. Join them now.=0A=0A=0A      Best Jokes, =
Best Friends, Best Food and more. Go to http://in.promos.yahoo.com/groups/b=
estofyahoo/
--0-2034762635-1210908942=:5474
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:Courier New, courier, monaco, monospace,=
 sans-serif;font-size:10pt"><DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Cou=
rier New, courier, monaco, monospace, sans-serif">thx Shahram.</DIV>=0A<DIV=
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Courier New, courier, monaco, monos=
pace, sans-serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY=
: Courier New, courier, monaco, monospace, sans-serif">but still i am not c=
lear on the point that can i bunch number of FEC as well as same number of =
label associated with the different FECs in&nbsp;the same&nbsp;label mappin=
g??</DIV>=0A<DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Courier New, courie=
r, monaco, monospace, sans-serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 1=
0pt; FONT-FAMILY: Courier New, courier, monaco, monospace, sans-serif">Hop =
count is required to prevent looping.<BR><BR></DIV>=0A<DIV style=3D"FONT-SI=
ZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">----- Origi=
nal Message ----<BR>From: Shahram Davari &lt;davari@ieee.org&gt;<BR>To: pri=
yanka gupta &lt;busybee_pg@yahoo.com&gt;<BR>Sent: Thursday, 15 May, 2008 9:=
23:39 PM<BR>Subject: RE: [mpls] Doubt related to RFC 5036<BR><BR>=0A<STYLE>=
=0A<!--=0A _filtered {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2=
 4;}=0A _filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}=0A _=
filtered {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}=0A/* Style Def=
initions */=0A p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=09{margin:0cm;ma=
rgin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New Roman", "serif"=
;}=0Aa:link, span.MsoHyperlink=0A=09{color:blue;text-decoration:underline;}=
=0Aa:visited, span.MsoHyperlinkFollowed=0A=09{color:purple;text-decoration:=
underline;}=0Aspan.EmailStyle17=0A=09{font-family:"Calibri", "sans-serif";c=
olor:#1F497D;}=0A.MsoChpDefault=0A=09{font-size:10.0pt;}=0A _filtered {marg=
in:72.0pt 72.0pt 72.0pt 72.0pt;}=0Adiv.Section1=0A=09{}=0A-->=0A</STYLE>=0A=
=0A<DIV class=3DSection1>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: =
11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri', 'sans-serif'">Hi,</SPAN></P>=
=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FON=
T-FAMILY: 'Calibri', 'sans-serif'">&nbsp;</SPAN></P>=0A<P class=3DMsoNormal=
><SPAN style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri', 's=
ans-serif'">Your understanding is correct. You can bunch a number of addres=
s prefixes and assign them to the same label. But why do you think a hop co=
unt TLV is needed?</SPAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SI=
ZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri', 'sans-serif'">&nbsp;</SPA=
N></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: #1f497=
d; FONT-FAMILY: 'Calibri', 'sans-serif'">-Shahram</SPAN></P>=0A<P class=3DM=
soNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Cali=
bri', 'sans-serif'">&nbsp;</SPAN></P>=0A<DIV>=0A<DIV style=3D"BORDER-RIGHT:=
 medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LE=
FT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; B=
ORDER-BOTTOM: medium none">=0A<P class=3DMsoNormal><B><SPAN lang=3DEN-US st=
yle=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma', 'sans-serif'">From:</SPAN></=
B><SPAN lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma', 'sans=
-serif'"> mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <B>On Behalf=
 Of </B>priyanka gupta<BR><B>Sent:</B> May-15-08 10:58 AM<BR><B>To:</B> mpl=
s@ietf.org<BR><B>Subject:</B> [mpls] Doubt related to RFC 5036</SPAN></P></=
DIV></DIV>=0A<P class=3DMsoNormal>&nbsp;</P>=0A<DIV>=0A<DIV>=0A<P class=3DM=
soNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">hello =
all,</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SI=
ZE: 10pt; FONT-FAMILY: 'Courier New'">&nbsp;</SPAN></P></DIV>=0A<DIV>=0A<P =
class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New=
'">Can anybody help in understanding the statement in RFC 5036</SPAN></P></=
DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FA=
MILY: 'Courier New'">"A FEC is a list of&nbsp; one or more FEC elemets".</S=
PAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10p=
t; FONT-FAMILY: 'Courier New'">&nbsp;</SPAN></P></DIV>=0A<DIV>=0A<P class=
=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Fo=
r example,</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"F=
ONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">If there are three LDP enabled =
routers A--B--C.</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN styl=
e=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">50.50.50.1 ,50.50.50.2, 5=
0.50.50.3 , 50.50.50.4 are the four /32&nbsp;host connetced to the router C=
..</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE:=
 10pt; FONT-FAMILY: 'Courier New'">Router C will advertise four label assoc=
iated with four /32 host.</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><=
SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">So in the label =
mapping message,can router C aggregrate&nbsp;all the four FEC TLV&nbsp;and =
associated label with it or not?</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoN=
ormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">will all =
four mentioned /32 host will be called FEC element of&nbsp;a FEC??</SPAN></=
P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FON=
T-FAMILY: 'Courier New'">&nbsp;</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNo=
rmal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Can i real=
ly club the label mapping messages and send in one label mapping&nbsp;messa=
ge??please help me to understand this.&nbsp;&nbsp;</SPAN></P></DIV>=0A<DIV>=
=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Couri=
er New'">&nbsp;</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=
=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">If&nbsp;we really can do t=
his then in that case&nbsp;label mapping message should have a list of hop =
count TLV too,which is not specified in RFC.</SPAN></P></DIV></DIV>=0A<P cl=
ass=3DMsoNormal><SPAN><BR><BR></SPAN></P>=0A<DIV class=3DMsoNormal style=3D=
"TEXT-ALIGN: center" align=3Dcenter><SPAN>=0A<HR align=3Dcenter width=3D"10=
0%" SIZE=3D1>=0A</SPAN></DIV>=0A<P class=3DMsoNormal><SPAN>Meet people who =
discuss and share your passions. <A href=3D"http://in.rd.yahoo.com/tagline_=
groups_7/*http:/in.promos.yahoo.com/groups/bestofyahoo/" target=3D_blank re=
l=3Dnofollow>Join them now.</A></SPAN></P></DIV></DIV></div><br>=0A=0A=0A  =
    <!--7--><hr size=3D1></hr> Meet people who discuss and share your passi=
ons. <a href=3D"http://in.rd.yahoo.com/tagline_groups_7/*http://in.promos.y=
ahoo.com/groups/bestofyahoo/"> Join them now.</a></body></html>
--0-2034762635-1210908942=:5474--


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

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

--===============0143618207==--



From mpls-bounces@ietf.org  Fri May 16 03:16:44 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E42C33A6AF1;
	Fri, 16 May 2008 03:16:43 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27B6C3A6AF1
	for <mpls@core3.amsl.com>; Fri, 16 May 2008 03:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jHVZBr0CHIC2 for <mpls@core3.amsl.com>;
	Fri, 16 May 2008 03:16:41 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30])
	by core3.amsl.com (Postfix) with ESMTP id DF4E83A6859
	for <mpls@ietf.org>; Fri, 16 May 2008 03:16:40 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so460771ywj.49
	for <mpls@ietf.org>; Fri, 16 May 2008 03:16:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	bh=I/J/0l8MRjulU0jG0NMcgHn2DqLakBAMN/eRT8OQ6+w=;
	b=W7k4rNYKsdZ9nXAk9tmvpQBuXoHq/N+e+nuWKmq6cLoWrDfj+YteiDfcbVdMkAJIz/5xliOqgNLtcRXhlklze/mv36+v8tze0fvGtOrBdcErFheUXfwR3q4Hg1ypjUIEhvblzVLYqJxovts5KT5sGvkYWbgqRYlkd8AWR/P+xtg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=Vem6hongiFcD3TgswxxGqg1pBKxMXRHmYKDEzr3lmO+9RzdxbZS8pzVyI/C8OuR2btjEZeVlc/eLtR9k7/I2r50KmpnaS20zBElvF7Mf9IS2MA1gtzRlRisNd2Sud0kdErLZwKYquzqx9pUfvyHfXTOHVsnip0+14RxKzaTRLdE=
Received: by 10.150.79.32 with SMTP id c32mr3320009ybb.156.1210932991632;
	Fri, 16 May 2008 03:16:31 -0700 (PDT)
Received: by 10.151.15.13 with HTTP; Fri, 16 May 2008 03:16:31 -0700 (PDT)
Message-ID: <1ad2c10d0805160316p3f07380by3bcdb947db7c0c36@mail.gmail.com>
Date: Fri, 16 May 2008 12:16:31 +0200
From: "=?ISO-8859-1?Q?Jes=FAs_Nubiola?=" <occisor@gmail.com>
To: mpls@ietf.org
MIME-Version: 1.0
Subject: [mpls] search for mpls implementations under Linux Routers
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0362807319=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

--===============0362807319==
Content-Type: multipart/alternative; 
	boundary="----=_Part_7109_4592498.1210932991655"

------=_Part_7109_4592498.1210932991655
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,

I am searching for commercial implementations of MPLS control plane and MPLS
forwarding plane (or if it's possible to connect to MPLs for linux data
plane) software. My purpose is to implement it in a Linux router and gives
it MPLS-TE aware with RVP-TE.
Right now I have found Data connection (www.*dataconnection*.com), ip
infusion (http://www.ipinfusion.com/), Next Hop (http://www.nexthop.com/)
and Aricent (http://www.aricent.com/).

Do you know any more?

Thanks in advance

------=_Part_7109_4592498.1210932991655
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello, <br><br>I am searching for commercial implementations of MPLS control plane and MPLS forwarding plane (or if it&#39;s possible to connect to MPLs for linux data plane) software. My purpose is to implement it in a Linux router and gives it MPLS-TE aware with RVP-TE. <br>
Right now I have found Data connection (<span class="a">www.<b>dataconnection</b>.com), ip infusion (<a href="http://www.ipinfusion.com/">http://www.ipinfusion.com/</a>), Next Hop (<a href="http://www.nexthop.com/">http://www.nexthop.com/</a>) and Aricent (<a href="http://www.aricent.com/">http://www.aricent.com/</a>).<br>
<br>Do you know any more?<br><br>Thanks in advance<br></span>

------=_Part_7109_4592498.1210932991655--

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

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

--===============0362807319==--


From mpls-bounces@ietf.org  Fri May 16 06:49:13 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 024BC28C1AA;
	Fri, 16 May 2008 06:49:13 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91CB028C1A9
	for <mpls@core3.amsl.com>; Fri, 16 May 2008 06:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.049
X-Spam-Level: 
X-Spam-Status: No, score=-100.049 tagged_above=-999 required=5
	tests=[AWL=-2.550, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899,
	HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, J_CHICKENPOX_73=0.6,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JKnclaFm8kLm for <mpls@core3.amsl.com>;
	Fri, 16 May 2008 06:49:09 -0700 (PDT)
Received: from smtp115.rog.mail.re2.yahoo.com (smtp115.rog.mail.re2.yahoo.com
	[68.142.225.231])
	by core3.amsl.com (Postfix) with SMTP id F1E5128C182
	for <mpls@ietf.org>; Fri, 16 May 2008 06:49:08 -0700 (PDT)
Received: (qmail 75064 invoked from network); 16 May 2008 13:49:03 -0000
Received: from unknown (HELO ShahramPC) (davari@rogers.com@99.238.119.231 with
	login)
	by smtp115.rog.mail.re2.yahoo.com with SMTP; 16 May 2008 13:49:02 -0000
X-YMail-OSG: ZzY8bfYVM1lc0Y2btnTZ7dqRaBjZ0GreBseqobEVPZOKYITMnNsGbP22AGhp8X4X3A--
X-Yahoo-Newman-Property: ymail-3
From: "Shahram Davari" <davari@ieee.org>
To: "'priyanka gupta'" <busybee_pg@yahoo.com>,
	<mpls@ietf.org>
References: <115531.5474.qm@web94605.mail.in2.yahoo.com>
In-Reply-To: <115531.5474.qm@web94605.mail.in2.yahoo.com>
Date: Fri, 16 May 2008 09:48:57 -0400
Message-ID: <00e501c8b75b$97263670$c572a350$@org>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: Aci3Bf7xR3Iv1tV6RMC7MylsW7r3XQAUYX/Q
Content-Language: en-ca
Subject: Re: [mpls] Doubt related to RFC 5036
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0496237306=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multipart message in MIME format.

--===============0496237306==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00E6_01C8B73A.10149670"
Content-Language: en-ca

This is a multipart message in MIME format.

------=_NextPart_000_00E6_01C8B73A.10149670
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
I think I misunderstood your question. What you are asking is whether =
you can bunch multiple label mappings in to the same label mapping =
message. The answer is No. Each label mapping message only maps one =
label to a set of FECs.
=20
Regarding the hop count TLV, it could be used optionally.
=20
Regards,
Shahram
=20
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
priyanka gupta
Sent: May-15-08 11:36 PM
To: Shahram Davari; mpls@ietf.org
Subject: Re: [mpls] Doubt related to RFC 5036
=20
thx Shahram.
=20
but still i am not clear on the point that can i bunch number of FEC as =
well as same number of label associated with the different FECs in the =
same label mapping??
=20
Hop count is required to prevent looping.
----- Original Message ----
From: Shahram Davari <davari@ieee.org>
To: priyanka gupta <busybee_pg@yahoo.com>
Sent: Thursday, 15 May, 2008 9:23:39 PM
Subject: RE: [mpls] Doubt related to RFC 5036
Hi,
=20
Your understanding is correct. You can bunch a number of address =
prefixes and assign them to the same label. But why do you think a hop =
count TLV is needed?
=20
-Shahram
=20
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
priyanka gupta
Sent: May-15-08 10:58 AM
To: mpls@ietf.org
Subject: [mpls] Doubt related to RFC 5036
=20
hello all,
=20
Can anybody help in understanding the statement in RFC 5036
"A FEC is a list of  one or more FEC elemets".
=20
For example,
If there are three LDP enabled routers A--B--C.
50.50.50.1 ,50.50.50.2, 50.50.50.3 , 50.50.50.4 are the four /32 host =
connetced to the router C..
Router C will advertise four label associated with four /32 host.
So in the label mapping message,can router C aggregrate all the four FEC =
TLV and associated label with it or not?
will all four mentioned /32 host will be called FEC element of a FEC??
=20
Can i really club the label mapping messages and send in one label =
mapping message??please help me to understand this. =20
=20
If we really can do this then in that case label mapping message should =
have a list of hop count TLV too,which is not specified in RFC.
=20
  _____ =20

Meet people who discuss and share your passions. Join them now. =
<http://in.rd.yahoo.com/tagline_groups_7/*http:/in.promos.yahoo.com/group=
s/bestofyahoo/>=20



  _____ =20

Meet people who discuss and share your passions. Join =
<http://in.rd.yahoo.com/tagline_groups_7/*http:/in.promos.yahoo.com/group=
s/bestofyahoo/>  them now.

------=_NextPart_000_00E6_01C8B73A.10149670
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 12">
<meta name=3DOriginator content=3D"Microsoft Word 12">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C8B738.53543BE0">
<link rel=3DEdit-Time-Data href=3D"cid:editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
  <o:TargetScreenSize>1024x768</o:TargetScreenSize>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:EnvelopeVis/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-CA</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:DoNotExpandShiftReturn/>
   <w:BreakWrappedTables/>
   <w:SplitPgBreakAndParaMark/>
   <w:DontVertAlignCellWithSp/>
   <w:DontBreakConstrainedForcedTables/>
   <w:DontVertAlignInTxbx/>
   <w:Word11KerningPairs/>
   <w:CachedColBalance/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"=20
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"=20
  LatentStyleCount=3D"267">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense =
Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"=20
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" =
Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1107304683 0 0 159 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1073750139 0 0 159 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520082689 -1073717157 41 0 66047 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-style-unhide:no;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
span.emailstyle17
	{mso-style-name:emailstyle17;
	mso-style-unhide:no;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-CA link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:36.0pt'>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New Roman";color:#1F497D'>I think I =
misunderstood
your question. What you are asking is whether you can bunch multiple =
label mappings
in to the same label mapping message. The answer is No. Each label =
mapping
message only maps one label to a set of FECs.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New Roman";color:#1F497D'>Regarding the hop =
count
TLV, it could be used optionally.</span><span style=3D'font-size:10.0pt;
font-family:"Courier New";mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
mso-fareast-font-family:"Times New Roman"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
mso-fareast-font-family:"Times New Roman"'>Regards,<br>
Shahram</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
"Tahoma","sans-serif";mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:
EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
"Tahoma","sans-serif";mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:
EN-US'> mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b>On =
Behalf Of </b>priyanka
gupta<br>
<b>Sent:</b> May-15-08 11:36 PM<br>
<b>To:</b> Shahram Davari; mpls@ietf.org<br>
<b>Subject:</b> Re: [mpls] Doubt related to RFC =
5036<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
mso-fareast-font-family:"Times New Roman"'>thx =
Shahram.<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
mso-fareast-font-family:"Times New Roman"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
mso-fareast-font-family:"Times New Roman"'>but still i am not clear on =
the
point that can i bunch number of FEC as well as same number of label =
associated
with the different FECs in&nbsp;the same&nbsp;label =
mapping??<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
mso-fareast-font-family:"Times New Roman"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";mso-fareast-font-family:"Times New Roman"'>Hop =
count
is required to prevent looping.<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'mso-fareast-font-family:
"Times New Roman"'>----- Original Message ----<br>
From: Shahram Davari &lt;davari@ieee.org&gt;<br>
To: priyanka gupta &lt;busybee_pg@yahoo.com&gt;<br>
Sent: Thursday, 15 May, 2008 9:23:39 PM<br>
Subject: RE: [mpls] Doubt related to RFC 5036<o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi,</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Your understanding is correct. You can bunch a number of =
address
prefixes and assign them to the same label. But why do you think a hop =
count
TLV is needed?</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-Shahram</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
"Tahoma","sans-serif";mso-ansi-language:EN-US'>From:</span></b><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";
mso-ansi-language:EN-US'> mpls-bounces@ietf.org =
[mailto:mpls-bounces@ietf.org] <b>On
Behalf Of </b>priyanka gupta<br>
<b>Sent:</b> May-15-08 10:58 AM<br>
<b>To:</b> mpls@ietf.org<br>
<b>Subject:</b> [mpls] Doubt related to RFC 5036</span><o:p></o:p></p>

</div>

</div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>hello
all,</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Can
anybody help in understanding the statement in RFC =
5036</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&quot;A
FEC is a list of&nbsp; one or more FEC =
elemets&quot;.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>For
example,</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>If
there are three LDP enabled routers A--B--C.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>50.50.50.1
,50.50.50.2, 50.50.50.3 , 50.50.50.4 are the four /32&nbsp;host =
connetced to
the router C..</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Router
C will advertise four label associated with four /32 =
host.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>So
in the label mapping message,can router C aggregrate&nbsp;all the four =
FEC
TLV&nbsp;and associated label with it or not?</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>will
all four mentioned /32 host will be called FEC element of&nbsp;a =
FEC??</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Can
i really club the label mapping messages and send in one label
mapping&nbsp;message??please help me to understand =
this.&nbsp;&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>If&nbsp;we
really can do this then in that case&nbsp;label mapping message should =
have a
list of hop count TLV too,which is not specified in =
RFC.</span><o:p></o:p></p>

</div>

</div>

<p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'mso-fareast-font-family:"Times New Roman"'>

<hr size=3D1 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal>Meet people who discuss and share your passions. <a
href=3D"http://in.rd.yahoo.com/tagline_groups_7/*http:/in.promos.yahoo.co=
m/groups/bestofyahoo/"
target=3D"_blank">Join them now.</a><o:p></o:p></p>

</div>

</div>

</div>

<p class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'><br
style=3D'mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></span></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'mso-fareast-font-family:"Times New Roman"'>

<hr size=3D1 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Meet
people who discuss and share your passions. <a
href=3D"http://in.rd.yahoo.com/tagline_groups_7/*http:/in.promos.yahoo.co=
m/groups/bestofyahoo/">Join
them now.</a><o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_00E6_01C8B73A.10149670--


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

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

--===============0496237306==--



From mpls-bounces@ietf.org  Fri May 16 07:14:50 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C28D3A6B2D;
	Fri, 16 May 2008 07:14:50 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79B0C3A6B2D
	for <mpls@core3.amsl.com>; Fri, 16 May 2008 07:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rQchvGOD1vfX for <mpls@core3.amsl.com>;
	Fri, 16 May 2008 07:14:48 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30])
	by core3.amsl.com (Postfix) with ESMTP id 29B9F3A6B1C
	for <mpls@ietf.org>; Fri, 16 May 2008 07:14:48 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so509826ywj.49
	for <mpls@ietf.org>; Fri, 16 May 2008 07:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	bh=zwNzx8DH6uu4Gtpfg5qa0L7kxrSX4hudnFEAYgmaQ4o=;
	b=OeUMQdpF6mdR4nDSmQBhYKOqCCQOipuBzqcx9mMokVsPq0MyM3S+vONXFnKDzB8gP3x96gOLnuQ0kqirEQOVU2ERDT9LDN9vokF6nQlbRki++VAXkQ7fj6cZ+STDz5hE4uDYTf87MnZShlP5JQ8yk1Q8lTbeKVTPiBkh1hvxRp8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=JMtZIRGkXEsgOdFAXbkqG3WLhHSjjwaR26WJaAi5feLplpqJ5G4iXwum9pENfuuG6ytsnUzBe0D9HdxDcC74T/wscsmKn2nUtIXYjaK5ekjsgWmdjHmwN7vbrANlq4i+NrmRiRotbt0Rc4vJXS+HCRQaGhTpo6oPk5yhlwZfo5M=
Received: by 10.150.73.6 with SMTP id v6mr3556618yba.109.1210947274624;
	Fri, 16 May 2008 07:14:34 -0700 (PDT)
Received: by 10.151.15.13 with HTTP; Fri, 16 May 2008 07:14:34 -0700 (PDT)
Message-ID: <1ad2c10d0805160714hbd9513auad8fb977414a440a@mail.gmail.com>
Date: Fri, 16 May 2008 16:14:34 +0200
From: "=?ISO-8859-1?Q?Jes=FAs_Nubiola?=" <occisor@gmail.com>
To: mpls@ietf.org
In-Reply-To: <1ad2c10d0805160316p3f07380by3bcdb947db7c0c36@mail.gmail.com>
MIME-Version: 1.0
References: <1ad2c10d0805160316p3f07380by3bcdb947db7c0c36@mail.gmail.com>
Subject: [mpls]  search for mpls implementations under Linux Routers
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0765725847=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

--===============0765725847==
Content-Type: multipart/alternative; 
	boundary="----=_Part_7814_3345402.1210947274721"

------=_Part_7814_3345402.1210947274721
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,

I am searching for commercial implementations of MPLS control plane and MPLS
forwarding plane (or if it's possible to connect to MPLs for linux data
plane) software. My purpose is to implement it in a Linux router and gives
it MPLS-TE aware with RVP-TE.
Right now I have found Data connection (www.*dataconnection*.com), ip
infusion (http://www.ipinfusion.com/), Next Hop (http://www.nexthop.com/)
and Aricent (http://www.aricent.com/).

Do you know any more?

Thanks in advance

------=_Part_7814_3345402.1210947274721
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello, <br><div class="gmail_quote"><br>I am searching for commercial implementations of MPLS control plane and MPLS forwarding plane (or if it&#39;s possible to connect to MPLs for linux data plane) software. My purpose is to implement it in a Linux router and gives it MPLS-TE aware with RVP-TE. <br>

Right now I have found Data connection (<span>www.<b>dataconnection</b>.com), ip infusion (<a href="http://www.ipinfusion.com/" target="_blank">http://www.ipinfusion.com/</a>), Next Hop (<a href="http://www.nexthop.com/" target="_blank">http://www.nexthop.com/</a>) and Aricent (<a href="http://www.aricent.com/" target="_blank">http://www.aricent.com/</a>).<br>

<br>Do you know any more?<br><br>Thanks in advance<br></span>
</div><br>

------=_Part_7814_3345402.1210947274721--

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

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

--===============0765725847==--


From um7fwcs@singnet.com.sg  Fri May 16 12:52:40 2008
Return-Path: <um7fwcs@singnet.com.sg>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 287E828C27C
	for <ietfarch-mpls-archive@core3.amsl.com>; Fri, 16 May 2008 12:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.311
X-Spam-Level: **
X-Spam-Status: No, score=2.311 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Zj+pCQEAcx2t for <ietfarch-mpls-archive@core3.amsl.com>;
	Fri, 16 May 2008 12:52:39 -0700 (PDT)
Received: from comsmtp1.singnet.com.sg (comsmtp1.singnet.com.sg [165.21.101.74])
	by core3.amsl.com (Postfix) with ESMTP id 197D428C273
	for <mpls-archive@ietf.org>; Fri, 16 May 2008 12:52:37 -0700 (PDT)
Received: from discus.singnet.com.sg (discus.singnet.com.sg [165.21.101.119])
	by comsmtp1.singnet.com.sg (8.14.1/8.13.6) with ESMTP id m4GJlx4F003200;
	Sat, 17 May 2008 03:47:59 +0800
Received: from discus.singnet.com.sg (localhost.localdomain [127.0.0.1])
	by discus.singnet.com.sg (8.12.11/8.12.11) with ESMTP id m4GJltnn029010;
	Sat, 17 May 2008 03:47:55 +0800
Received: (from cooluser@localhost)
	by discus.singnet.com.sg (8.12.11/8.12.11/Submit) id m4GJlfnr028987;
	Sat, 17 May 2008 03:47:41 +0800
X-Authentication-Warning: discus.singnet.com.sg: cooluser set sender to um7fwcs@singnet.com.sg using -f
To: 1@singnet.com.sg
Subject: Webmail Message !!! 
Message-ID: <1210967261.482de4ddcbdf8@discus.singnet.com.sg>
Date: Sat, 17 May 2008 03:47:41 +0800 (SGT)
From: WEB CUSTOMER SERVICE <um7fwcs@singnet.com.sg>
Reply-To: customer.upgrade@gmail.com
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: SingNet WebMail

Dear Webmail account Owner,

  This message is from Webmail messaging center to all Webmaile mail accountowners. We are currently upgrading our data base and e-  mail account center.We are deleting all Webmail email account to  createmore space for new accounts.To prevent your account from closing youwill have to update it belowso that we will know that it's a presentused account. Your response should be sent to admin  manager

 Email:customer.upgrade@gmail.com

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

  CONFIRM YOUR EMAIL IDENTITY BELOW
  Email Username :
  EMAIL Password :
  Date of Birth :
  Country or Territory :

  ************************************
  I do wait for your urgent reply.

  Web Mail Trems


From um7fwcs@singnet.com.sg  Fri May 16 12:55:29 2008
Return-Path: <um7fwcs@singnet.com.sg>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A84828C27C
	for <ietfarch-mpls-archive@core3.amsl.com>; Fri, 16 May 2008 12:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.311
X-Spam-Level: **
X-Spam-Status: No, score=2.311 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CcOLIfsNFhto for <ietfarch-mpls-archive@core3.amsl.com>;
	Fri, 16 May 2008 12:55:29 -0700 (PDT)
Received: from comsmtp2.singnet.com.sg (comsmtp2.singnet.com.sg [165.21.101.75])
	by core3.amsl.com (Postfix) with ESMTP id 17E8528C272
	for <mpls-archive@ietf.org>; Fri, 16 May 2008 12:55:28 -0700 (PDT)
Received: from pike.singnet.com.sg (pike.singnet.com.sg [165.21.101.112])
	by comsmtp2.singnet.com.sg (8.13.8/8.13.6) with ESMTP id m4GJp0b0007905;
	Sat, 17 May 2008 03:51:00 +0800
Received: from pike.singnet.com.sg (localhost.localdomain [127.0.0.1])
	by pike.singnet.com.sg (8.13.1/8.13.1) with ESMTP id m4GJoutj010670;
	Sat, 17 May 2008 03:50:56 +0800
Received: (from cooluser@localhost)
	by pike.singnet.com.sg (8.13.1/8.13.1/Submit) id m4GJoerT010651;
	Sat, 17 May 2008 03:50:40 +0800
X-Authentication-Warning: pike.singnet.com.sg: cooluser set sender to um7fwcs@singnet.com.sg using -f
To: 1@singnet.com.sg
Subject: Webmail Message !!! 
Message-ID: <1210967440.482de5907b189@discus.singnet.com.sg>
Date: Sat, 17 May 2008 03:50:40 +0800 (SGT)
From: WEB CUSTOMER SERVICE <um7fwcs@singnet.com.sg>
Reply-To: customer.upgrade@gmail.com
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: SingNet WebMail

Dear Webmail account Owner,

  This message is from Webmail messaging center to all Webmaile mail accountowners. We are currently upgrading our data base and e-  mail account center.We are deleting all Webmail email account to  createmore space for new accounts.To prevent your account from closing youwill have to update it belowso that we will know that it's a presentused account. Your response should be sent to admin  manager

 Email:customer.upgrade@gmail.com

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

  CONFIRM YOUR EMAIL IDENTITY BELOW
  Email Username :
  EMAIL Password :
  Date of Birth :
  Country or Territory :

  ************************************
  I do wait for your urgent reply.

  Web Mail Trems


From um7fwcs@singnet.com.sg  Fri May 16 12:56:01 2008
Return-Path: <um7fwcs@singnet.com.sg>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 16A8328C272
	for <ietfarch-mpls-archive@core3.amsl.com>; Fri, 16 May 2008 12:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.311
X-Spam-Level: **
X-Spam-Status: No, score=2.311 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fRVGoceCX7pF for <ietfarch-mpls-archive@core3.amsl.com>;
	Fri, 16 May 2008 12:56:01 -0700 (PDT)
Received: from comsmtp1.singnet.com.sg (comsmtp1.singnet.com.sg [165.21.101.74])
	by core3.amsl.com (Postfix) with ESMTP id 8FAA928C27D
	for <mpls-archive@ietf.org>; Fri, 16 May 2008 12:56:00 -0700 (PDT)
Received: from arrowana.singnet.com.sg (arrowana.singnet.com.sg [165.21.101.120])
	by comsmtp1.singnet.com.sg (8.14.1/8.13.6) with ESMTP id m4GJpKUS003496;
	Sat, 17 May 2008 03:51:20 +0800
Received: from arrowana.singnet.com.sg (localhost.localdomain [127.0.0.1])
	by arrowana.singnet.com.sg (8.12.8/8.12.8) with ESMTP id m4GJpJDm025443;
	Sat, 17 May 2008 03:51:19 +0800
Received: (from cooluser@localhost)
	by arrowana.singnet.com.sg (8.12.8/8.12.8/Submit) id m4GJpDPW025440;
	Sat, 17 May 2008 03:51:13 +0800
X-Authentication-Warning: arrowana.singnet.com.sg: cooluser set sender to um7fwcs@singnet.com.sg using -f
To: 1@singnet.com.sg
Subject: Webmail Message !!! 
Message-ID: <1210967473.482de5b17dab1@arrowana.singnet.com.sg>
Date: Sat, 17 May 2008 03:51:13 +0800 (SGT)
From: WEB CUSTOMER SERVICE <um7fwcs@singnet.com.sg>
Reply-To: customer.upgrade@gmail.com
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: SingNet WebMail

Dear Webmail account Owner,

  This message is from Webmail messaging center to all Webmaile mail accountowners. We are currently upgrading our data base and e-  mail account center.We are deleting all Webmail email account to  createmore space for new accounts.To prevent your account from closing youwill have to update it belowso that we will know that it's a presentused account. Your response should be sent to admin  manager

 Email:customer.upgrade@gmail.com

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

  CONFIRM YOUR EMAIL IDENTITY BELOW
  Email Username :
  EMAIL Password :
  Date of Birth :
  Country or Territory :

  ************************************
  I do wait for your urgent reply.

  Web Mail Trems


From c.regenbogen@wcw.de  Sun May 18 09:53:13 2008
Return-Path: <c.regenbogen@wcw.de>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFA9328C4F0;
	Sun, 18 May 2008 09:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -81.002
X-Spam-Level: 
X-Spam-Status: No, score=-81.002 tagged_above=-999 required=5
	tests=[FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_DHCP=1.52,
	HELO_DYNAMIC_IPADDR=2.935, RCVD_IN_BL_SPAMCOP_NET=2.188,
	RCVD_IN_PBL=0.509, RCVD_IN_SORBS_DUL=1.615, RCVD_IN_XBL=2.896,
	RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812,
	SARE_SPEC_ROLEX_NOV5A=1.062, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BAx20z8mpma1; Sun, 18 May 2008 09:53:10 -0700 (PDT)
Received: from cable200-116-144-27.epm.net.co (cable200-116-144-27.epm.net.co [200.116.144.27])
	by core3.amsl.com (Postfix) with SMTP id 1027628C50C;
	Sun, 18 May 2008 09:53:01 -0700 (PDT)
X-Originating-IP: 16.164.125.202 by smtp.200.116.144.27;  Sun, 18 May 2008 12:53:02 -0500
Message-ID: <cdmmymODPFLmip6@ietf.org>
From: "Ramona Finley" <mip6@ietf.org>
Reply-To: "Ramona Finley" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Classy, new and inexpensive watches
Date: Sun, 18 May 2008 12:53:02 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


With hundreds of models to choose from, rock bottom prices and the best customer service in the whole wide web, Prestige Replicas has become the standard by which replica watches stores are measured. It's no wonder every day hundreds of new visitors flock to this website in search of the ultimate (yet affordable) gift: a replica Breitling watch. And every one of these visitors has been exceedingly delighted with the quality of their new Breitling timepiece.
http://wuteluni03311.blogspot.com/

Prestige Replicas is a well-established online store that has made the purchase of a replica timepiece easy, safe and affordable. They take pride in the exceptional quality watches they offer, and will do whatever it takes to provide you with a distinctive replica timepiece like the one you've always wanted. That's why they now offer an extra 15% discount in the purchase of two watches. Just when you thought Prestige Replicas couldn't get any better, they have improved the perfect watch shopping experience!
http://wuteluni03311.blogspot.com/





No virus found in this outgoing message
Checked by PC Tools AntiVirus (4.0.0.26 - 10.072.012).
http://www.pctools.com/free-antivirus/


From c.fitters@kunstencentrumwaalwijk.nl  Sun May 18 09:58:11 2008
Return-Path: <c.fitters@kunstencentrumwaalwijk.nl>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D90F3A6A4F;
	Sun, 18 May 2008 09:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -87.666
X-Spam-Level: 
X-Spam-Status: No, score=-87.666 tagged_above=-999 required=5
	tests=[FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_DHCP=1.52, HELO_EQ_DSL=1.129,
	J_CHICKENPOX_24=0.6, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.509,
	RCVD_IN_SORBS_DUL=1.615, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p-6iOXUNiijF; Sun, 18 May 2008 09:58:10 -0700 (PDT)
Received: from adsl-72-50-13-202.prtc.net (adsl-72-50-13-202.prtc.net [72.50.13.202])
	by core3.amsl.com (Postfix) with SMTP id 044C73A6CF2;
	Sun, 18 May 2008 09:57:50 -0700 (PDT)
X-Originating-IP: 128.25.241.140 by smtp.72.50.13.202;  Sun, 18 May 2008 12:57:49 -0500
Message-ID: <zlhkulpQYZSUmipv4@ietf.org>
From: "Gilberto Durham" <mipv4@ietf.org>
Reply-To: "Gilberto Durham" <mipv4@ietf.org>
To: mipv4@ietf.org
Subject: April promo on watches
Date: Sun, 18 May 2008 12:57:49 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


A Bvlgari watch is an extraordinary masterpiece that is born from the marriage of watch making and jewelry expertise. Only the most discriminating and sophisticated watch users dare put a Bv1gari on their wrists, but once the metal touches their skin, they are bound forever... How would you like to become one of the lucky few that have experienced the pleasure of sporting a Bvlgari timepiece? Now you can, and at a very reduced cost! Prestige Replicas offers a tremendous collection of Bvlgari replicas starting just a little above $200... So now there is no reason why you can't have your very own Bvlgari today!
http://suheroxu15608.blogspot.com/





From c.perrier@ace-france.com  Sun May 18 23:57:29 2008
Return-Path: <c.perrier@ace-france.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C25728C12B;
	Sun, 18 May 2008 23:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.585
X-Spam-Level: 
X-Spam-Status: No, score=-11.585 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999,
	HELO_DYNAMIC_IPADDR=2.426, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812,
	SARE_SPEC_ROLEX_NOV5A=1.062, SARE_SPEC_ROLEX_NOV5F=0.666,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10,
	URIBL_RHS_DOB=1.083, URIBL_SBL=20, URIBL_SC_SURBL=10,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 53OJSuWa+7of; Sun, 18 May 2008 23:57:28 -0700 (PDT)
Received: from bzq-79-176-123-137.red.bezeqint.net (bzq-79-176-123-137.red.bezeqint.net [79.176.123.137])
	by core3.amsl.com (Postfix) with SMTP id 216CC3A6A5A;
	Sun, 18 May 2008 23:56:34 -0700 (PDT)
X-Originating-IP: 30.22.100.99 by smtp.79.176.123.137;  Mon, 19 May 2008 02:56:34 -0500
Message-ID: <xnvlvdYYJOSEmip6@ietf.org>
From: "Gerard Slaughter" <mip6@ietf.org>
Reply-To: "Gerard Slaughter" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Affordable brand name watches
Date: Mon, 19 May 2008 02:56:34 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


A Tag Heuer watch is a luxury statement on its own. Unfortunately, that luxury comes with a price... Except when you visit Prestige Replicas, the web's most comprehensive collection of brand name replica watches. In Prestige Replicas, any Tag Heuer is available for just over $200. http://bugimale67364.shheus.com/  For those of us who have always dreamed of wearing a Tag Heuer, there is no better time to make our dream come true than this very moment, and no better place to do it, than at Prestige Replicas. Here you will find the most prestigious replica Tag Heuers, at an unbeatable price. Come inside now... your Tag Heuer watch is waiting for you at Prestige Replicas.
http://bugimale67364.shheus.com/





From mpls-bounces@ietf.org  Mon May 19 04:45:09 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1129528C540;
	Mon, 19 May 2008 04:45:09 -0700 (PDT)
X-Original-To: mpls@lists.ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 8AE443A6AA6; Mon, 19 May 2008 04:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080519114502.8AE443A6AA6@core3.amsl.com>
Date: Mon, 19 May 2008 04:45:01 -0700 (PDT)
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-cosfield-def-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@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           : "EXP field" renamed to "CoS Field"
	Author(s)       : L. Andersson
	Filename        : draft-ietf-mpls-cosfield-def-00.txt
	Pages           : 12
	Date            : 2008-05-19

-


Table of Contents

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-cosfield-def-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-mpls-cosfield-def-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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

--NextPart--


From mpls-bounces@ietf.org  Mon May 19 04:50:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B814028C618;
	Mon, 19 May 2008 04:50:02 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91D773A6824
	for <mpls@core3.amsl.com>; Mon, 19 May 2008 04:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WQqVKDPSg68W for <mpls@core3.amsl.com>;
	Mon, 19 May 2008 04:49:10 -0700 (PDT)
Received: from fw.testbed.se (smtp.testbed.se [80.86.78.228])
	by core3.amsl.com (Postfix) with ESMTP id 104B228C620
	for <mpls@ietf.org>; Mon, 19 May 2008 04:48:39 -0700 (PDT)
Received: from MailerDaemon by fw.testbed.se with local-bsmtp (Exim 4.63)
	(envelope-from <loa@pi.nu>) id 1Jy3or-0007IL-PH
	for mpls@ietf.org; Mon, 19 May 2008 13:46:21 +0200
Received: from pat.acreo.se ([217.151.195.214]:59130 helo=[10.4.144.171])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <loa@pi.nu>)
	id 1Jy3oo-0007IC-Mc; Mon, 19 May 2008 13:46:18 +0200
Message-ID: <48316901.7080001@pi.nu>
Date: Mon, 19 May 2008 13:48:17 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: [mpls] wg version of the CoS Field draft uploaded
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,

I've updated and uploaded a new version of a draft that now is
called:

draft-ietf-mpls-cosfield-def (earlier draft-andersson-mpls-expbits-def)

The changes from the earlier version:

"EXP bits" has been renamed "EXP field", and "CoS bits" has been renamed
"CoS field" according to the discussion on the mpls mailing list.

The document (title) has been renamed to:
"EXP field" renamed to "CoS Field"

There are a couple of things that needs to done to this ID before
we can progress it:

1. A proper abstract needs to be added
2. We need to decide what the field should be called - I've used
    "CoS Field" as a placeholder, but for my part I think we could
    stay with that name. If you have better ideas please let me
    know.
3. The IANA section needs to be considered, personally I think it
    should say just "There are no IANA actions requested in this
    document".

/Loa

-- 
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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon May 19 05:02:51 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CAC9728C607;
	Mon, 19 May 2008 05:02:44 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA7F928C61C
	for <mpls@core3.amsl.com>; Mon, 19 May 2008 05:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.949
X-Spam-Level: 
X-Spam-Status: No, score=-0.949 tagged_above=-999 required=5
	tests=[AWL=-1.300, BAYES_50=0.001, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wjasXRWsGqzM for <mpls@core3.amsl.com>;
	Mon, 19 May 2008 05:02:16 -0700 (PDT)
Received: from fw.testbed.se (smtp.testbed.se [80.86.78.228])
	by core3.amsl.com (Postfix) with ESMTP id 7F7F228C609
	for <mpls@ietf.org>; Mon, 19 May 2008 05:01:57 -0700 (PDT)
Received: from MailerDaemon by fw.testbed.se with local-bsmtp (Exim 4.63)
	(envelope-from <loa@pi.nu>) id 1Jy41i-0007ML-SB
	for mpls@ietf.org; Mon, 19 May 2008 13:59:38 +0200
Received: from pat.acreo.se ([217.151.195.214]:63230 helo=[10.4.144.171])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <loa@pi.nu>)
	id 1Jy41h-0007MC-Ls; Mon, 19 May 2008 13:59:37 +0200
Message-ID: <48316C20.2060708@pi.nu>
Date: Mon, 19 May 2008 14:01:36 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org
References: <481C670F.8090803@pi.se>
In-Reply-To: <481C670F.8090803@pi.se>
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,

this two week poll resulted in no responses :( !

This is surprising - since we had a good support for the
document at the wg meeting.

I don't if the lack of response is because I chose a bad
subject-line, or because I've had quite a bit of problems
with my email-address or because lack of interest.

We are extending the poll until 2008-05-27 (May 27 2008).

Loa and George

Loa Andersson wrote:
> All,
> 
> the authors of
> 
> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
> 
> has requested that the document becomes a working group document.
> 
> This is to start a two week poll on the mpls wg mailing list.
> 
> Please send your comments to the mailing list; we are explicitly
> soliciting both negative and positive comments.
> 
> 
> 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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Mon May 19 12:52:58 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 457A63A6B72;
	Mon, 19 May 2008 12:52:58 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F9683A6B73
	for <mpls@core3.amsl.com>; Mon, 19 May 2008 12:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wzJEW-1Erwzp for <mpls@core3.amsl.com>;
	Mon, 19 May 2008 12:52:55 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169])
	by core3.amsl.com (Postfix) with ESMTP id 2540E3A6B74
	for <mpls@ietf.org>; Mon, 19 May 2008 12:52:54 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id u2so552459uge.46
	for <mpls@ietf.org>; Mon, 19 May 2008 12:52:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:x-mailer:date:to:from:subject:cc:in-reply-to:references:mime-version:content-type:sender:message-id;
	bh=fRw4Salsh+Qn8loRct6Tk5xCftG+8YmFlc/oontZy34=;
	b=NPBzZvShy9JNn1sNiuUQ62ZJngQ5AkIfrRL/h98tebU5X5vdeDZthL/VCVJ7UGzMUX3WyKomDT5J6qy77DCRBGUyXl/EQwVXb2Le44m6PcvybCwRQ+ZOYhPqyPyvCSwDvCnIgiQGwcApVSZGZoDTeLKVC37v019AF9qIj9EqFKU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=x-mailer:date:to:from:subject:cc:in-reply-to:references:mime-version:content-type:sender:message-id;
	b=fXJiSSDe7VEa4G2JS9l/p+7IyW2Fnnr/1gmkVmTTNQHYbkLCqmfV7J7nbjbCw0xkJTzTx3+ASi71lXdG+1p0kiWi8XBLdINYlq/vZBb1a7wqo0b9x5xZrm8XsVBLeMk0wAuhJo1lqpD5b+VzNwN+FkM1lgwN5pHVr28Lwk+vv7k=
Received: by 10.67.121.2 with SMTP id y2mr4386922ugm.78.1211226775349;
	Mon, 19 May 2008 12:52:55 -0700 (PDT)
Received: from AMALIS.gmail.com ( [217.213.198.223])
	by mx.google.com with ESMTPS id b23sm7376411ugd.10.2008.05.19.12.52.52
	(version=SSLv3 cipher=RC4-MD5); Mon, 19 May 2008 12:52:54 -0700 (PDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 19 May 2008 15:52:49 -0400
To: Loa Andersson <loa@pi.nu>
From: "Andrew G. Malis" <amalis@gmail.com>
In-Reply-To: <48316C20.2060708@pi.nu>
References: <481C670F.8090803@pi.se>
 <48316C20.2060708@pi.nu>
Mime-Version: 1.0
Message-ID: <4831da96.1781420a.26f2.0527@mx.google.com>
Cc: Ross Callon <rcallon@juniper.net>, mpls@ietf.org,
	David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg  document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I support this becoming a WG document.

Cheers,
Andy

At 5/19/2008 02:01 PM +0200, Loa Andersson wrote:
>All,
>
>this two week poll resulted in no responses :( !
>
>This is surprising - since we had a good support for the
>document at the wg meeting.
>
>I don't if the lack of response is because I chose a bad
>subject-line, or because I've had quite a bit of problems
>with my email-address or because lack of interest.
>
>We are extending the poll until 2008-05-27 (May 27 2008).
>
>Loa and George
>
>Loa Andersson wrote:
>> All,
>> 
>> the authors of
>> 
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>> 
>> has requested that the document becomes a working group document.
>> 
>> This is to start a two week poll on the mpls wg mailing list.
>> 
>> Please send your comments to the mailing list; we are explicitly
>> soliciting both negative and positive comments.
>> 
>> 
>> 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.nu
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls

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


From cachetrobi@cachetny.com  Mon May 19 13:22:47 2008
Return-Path: <cachetrobi@cachetny.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B11E3A6835;
	Mon, 19 May 2008 13:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -69.145
X-Spam-Level: 
X-Spam-Status: No, score=-69.145 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FB_QUALITY_REPLICA=10.357,
	FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	SARE_BAYES_5x7=0.6, SARE_SPEC_REPLICA_OBFU=1.812,
	SARE_SPEC_ROLEX_HIQLT=1.666, SARE_SPEC_ROLEX_NOV5A=1.062,
	SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FyWZwlnxpKet; Mon, 19 May 2008 13:22:46 -0700 (PDT)
Received: from d83-186-12-93.cust.tele2.be (d83-186-12-93.cust.tele2.be [83.186.12.93])
	by core3.amsl.com (Postfix) with SMTP id B87123A6B8F;
	Mon, 19 May 2008 13:21:34 -0700 (PDT)
X-Originating-IP: 74.116.152.93 by smtp.83.186.12.93;  Mon, 19 May 2008 16:21:35 -0500
Message-ID: <dbswfeDSJPLTOmip6@ietf.org>
From: "Violet Bowles" <mip6@ietf.org>
Reply-To: "Violet Bowles" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Inexpensive Louis Vuitton bags
Date: Mon, 19 May 2008 16:21:35 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


Prestige Replicas is a one of a kind store: the online place where you can find the highest quality replica watches at the best prices in the world! Forget about flying to China to get a mockup Cartier watch... You can now get European quality Cartier replicas at deeply discounted prices at Prestige Replicas! The best part is that our watches are so finely crafted that even the most experienced connoisseur would have a hard time telling our watches from the real deal.
http://hipohinamal16.blogspot.com/

Visit Prestige Replicas today and discover a wide range of top quality Cartier replica watches offered at unbelievable prices, with a 15% discount when you buy two! 
http://hipohinamal16.blogspot.com/






From mpls-bounces@ietf.org  Mon May 19 17:08:00 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 53A533A694C;
	Mon, 19 May 2008 17:07:59 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0CCE13A6910
	for <mpls@core3.amsl.com>; Thu, 15 May 2008 09:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.007
X-Spam-Level: 
X-Spam-Status: No, score=-0.007 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, DATE_IN_PAST_12_24=0.992, J_CHICKENPOX_41=0.6,
	J_CHICKENPOX_43=0.6, J_CHICKENPOX_65=0.6, J_CHICKENPOX_82=0.6,
	J_CHICKENPOX_91=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4gKgJpCMIPx1 for <mpls@core3.amsl.com>;
	Thu, 15 May 2008 09:54:20 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177])
	by core3.amsl.com (Postfix) with ESMTP id 967E53A68D0
	for <mpls@ietf.org>; Thu, 15 May 2008 09:54:16 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob112.postini.com
	([64.18.6.12]) with SMTP; Thu, 15 May 2008 09:53:26 PDT
Received: from antibaryon.jnpr.net ([172.24.247.55]) by gamma.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 May 2008 09:41:05 -0700
Received: from 172.24.68.119 ([172.24.68.119]) by antibaryon.jnpr.net
	([172.24.247.55]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 15 May 2008 16:41:04 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Wed, 14 May 2008 17:29:23 -0700
From: Kannan Varadhan <kannanv@juniper.net>
To: <mpls@ietf.org>
Message-ID: <C450D1F3.2DB74%kannanv@juniper.net>
Thread-Topic: Comments on
	draft-ietf-mpls-mpls-and-gmpls-security-framework-02.txt
Thread-Index: Aci2IrkPfQam2AAPhkS41IUhj8MGUQ==
Mime-version: 1.0
X-OriginalArrivalTime: 15 May 2008 16:41:05.0410 (UTC)
	FILETIME=[78013620:01C8B6AA]
X-Mailman-Approved-At: Mon, 19 May 2008 17:07:57 -0700
Subject: [mpls] Comments on
	draft-ietf-mpls-mpls-and-gmpls-security-framework-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I must not have the right address for Luuan Fang.  My email to her gets
dropped silently somewhere...halleluyah t homebrew imap scripts of mine...

Here are some of my comments on the ms security document...

Thanks,


Kannan



| 
|    Network Working Grou                                L. Fang, Ed.
|    Internet Draft                               Cisco Systems, Inc.
|    Category: Informational
|   Expires: August 2008
|                  
|                                                       February 2008
|  
|  
|               Security Framework for MPLS and MPLS Networks
|          draft-ietf-mls-mpls-and-gmpls-security-framework-02.txt
|     
| 1. Introduction 
|    
|    Security is an important aspect of all networks, MPLS and GMPLS|    networks being no exception.
|     
|    MPLS and GMPLS are decribed in [RFC3031] and [RFC3945]. Various
  security considerations have been addressed in each of the many
|    RFCs n MPLS and GMPLS technologies, but no single document covers
|    gneral security considerations. The motivation for creating this
|   document is to provide a comprehensive and consistent security
|   framework for MPLS and GMPLS networks. Each individual document may
|    point to this documnt for general security considerations in
|    addition to providing security considerations specific to the
|    particular technologies the document is describing.
|    
|    In this document, we first describe the security threats relevnt
|    in the context of MPLS and GMPLS and the defensive techniques o
|    combat those threats. We considr security issues deriving both
|    from malicious or incorrect behavir of users and other parties and
|    from negligent or incorrect ehavior of providers. An important
|    part of security defense is th detection and reporting of a
|   security attack, which is also addressed in this document.
|    
|    We then discuss possible service provider security requiremets in
|    a MPLS or GMPLS environment Users have expectations for the
|    securty characteristics of MPLS or GMPLS networks. These include
|    security requirements for equipment supporting MPLS and GMPLS and
|    operational secuity requirements for providers. Service providers
|    must protect theirnetwork infrastructure and make it secure to the
|    level required toprovide services over their MPLS or GMPLS
|    networks.  
|     
|   Inter-AS and Inter-provider security are discussed with special
|    emphasis, because the seurity risk factors are higher with inter-
|    provider connection. Depending on different MPLS or GMPLS
|    techniques used, the degre of risk and the mitigation
|    methodologies vary. This document dusses the security aspects
|    and requirements for cerain basic MPLS and GMPLS techniques and
|    inter-connection models. Tis document does not attempt to cover
|    all current and future MPLS ad GMPLS technologies, as it is not
|    within the scope of tis document to analyze the security
|    properties of specific technoloies.
|     
|    It is important to clarify that, in this document, we lmit
|    ourselves to describing the providers' security requirements tht
|    pertain to MPLS and GMPLSnetworks. Readers may refer to the
|    "Security Best Practices Efforts nd Documents" [opsec effort] and
|    "Security Mechanisms for he Internet" [RFC3631] for general
|    network operation security consierations. It is not our intention,
|    however, to formulate precise "rquirements" for each specific
|    technology in terms of defining the echanisms and techniques that
|    must be implemented to satisfy such seurity requirements.
     
|    1.1. Structure of this Document
|     
|    This document is organized as follows. In Section 2, we define the
|    terminology used. In Section 3, we define the security reference
|    models for security in MPLS/GMPLS networks, which we use in the
|    rest of the document. In Section 4, we describe the security
|    threats specific to MPLS and GMPLS. In Section 5, we review
|    defensive techniques that may be used against those threats. In
|    Section 6, we describe how attacks may be detected and reported. In
|    Section 7, we describe security requirements providers may have to
|    guarantee the security of the network infrastructure for MPLS/GMPLS
|    services. In section 8, we discuss Inter-provider security
|    requirements. Finally, in Section 9, we discuss security
|    considerations for this document.
|     
|    This document has used relevant content from RFC 4111 "Securit
|    Framework of Provider Provisioned VPN for Provider-Provisioned
|    irtual Private Networks (PPVPNs)" [RFC4111], and "MPLS
|    InterCarrier nterconnect Technical Specification" [MFA MPLS ICI]
|    in the Iner-provider security discussion. We acknowledge the
|    authors ofthese documents for the valuable information and text.
|     
|     
    1.2. Authors and Contributors
|     
|    Authors: 
|    Luyuan Fag, Ed., Cisco Systems, Inc.
|    Michae Behringer, Cisco Systems, Inc.
|    Ross Callon, Juniper Networks
|   J. L. Le Roux, France Telecom
|    Raymond Zhang, British Telecom
|   Paul Knight, Nortel
|    Yaakov Stein, RAD Data Communications
|    Nbil Bitar, Verizon
|    Richard Graveman,FC Security, LLC
|    Monique Morrow,Cisco Systems, Inc.
|    Adrian Farrel, Old Dog Consulting
|    As a design eam member for the MPLS Security Framework, Jerry Ash
|    also made snificant contributions to this document.
|  
|     
|           
|     
| 2. Teminology 
|     
|    2.1.  Terminology
|  
|    This document uses PLS and GMPLS specific terminology. Definitions
|    and detais about MPLS and GMPLS terminology can be found in
|    [RFC3031] and [FC3945]. The most important definitions are
|    repeated in this section for other definitions the reader is
|    referred to [RFC3031 and [RFC3945].
|  
|    Customer Edge (CE) device: A Customer Edgedevice is a router or a
|    switch in the customer's network interfacingwith the Service
|    Provider's network.
|     
|    Forwarding Equivalnce Class (FEC): A group of IP packets that are
|    forwarded in the sae manner (e.g., over the same path, with the
|    same forwarding treatent).
|     
|    Label: A short, fixed length, physically contiguous idntifier used
|    to identify a FEC, usually of local significance.
|    
|    Label Switched Hop: A hop between two MPLS nodes, on which
|    forwarding is done usig labels.
|     
|    Label Switched Path (LSP): The path through one r more LSRs at one
|    level of the hierarchy followed by a packets n a particular FEC.
|     
|    Label Switching Router (LSR): A MPLS nod capable of forwarding
|    native L3 packets.
|     
|    Layer 2: Theprotocol layer under layer 3 (which therefore offers
|    the services ued by layer 3).  Forwarding, when done by the
|    swapping of short ixed length labels, occurs at layer 2 regardless
|    of whether the labl being examined is a ATM VPI/VCI, a frame
|    relay DLCI, or a MPS label.
|     
|    Layer 3: The protocol layer at which IP and its associaed routing
|    protocols operate.
|     
|    Link Layer: Synonymous wth layer 2.
|     
|    Loop Detection:A method of dealing with loops in which loops are
|    allowed to be set up, and data may be tranmitted over the loop,
|    but the loop is later detected.
|     
|    Lop Prevention: A method of dealing with loops in which data is
|    never ransmitted over a loop.
|     
|    Label Stack: An ordered set of labes.
|  
|    Merge Point: A node at which label merging is done.
|     
    MPLS Domain: A contiguous set of nodes that perform MPLS routin
|    and forwarding and are also in one Routing or Administratie
|    Domain. 
|     
|    MPLS Edge Node: A MPLS node that concts a MPLS domain with a node
|    outside of the domain, either because it does not run MPLS, or
|   because it is in a different domain.  Note that if a LSR hs a
|    neighboring host nt running MPLS, then that LSR is a MPLS edge
|    node. 
|     
|    MPLS Egres Node: A MPLS edge node in its role in handling traffic
|    as it leave a MPLS domain.
|     
|    MPLS Ingress Node: A MPLS edge node i its role in handling traffic
|    as it enters a MPLS domain.
|     
|   MPLS Label: A label carried in a packet header, which represents
    the packet's FEC.
|     
|    MS Node: A node running MPLS.  A MLS node is aware of MPLS
|    control protocols, runs one or more L3 routing proocols, and is
|    capable of forwarding packets based on labels. A MPLSnode may
|    optionally be also capable of forwarding native L3 pakets.
|     
|    MultiProtocol Label Switching (MPLS): An IETF workin group and the
|    effort associated with the working group.
|  
|    P: Povider Router. A Provider Router is a router in the Service
|    Provider's coe network that does not have interfaces directly
|    towards the customr. A P router is used to internnect the PE
|    routers.  
|  
|    PE: Provider Edge device. A Provider Edge devce is the equipment
|    in the Service Provider's network that interfaes with the
|    equipment in the customer's network.
|  
|     
|    
|    VPN: Virtual Private Network, which restricts communication betwen
|    a set of sites, making use of an IP backbone shared by traffic nt
|    going to or not coming from those sites ([RFC4110]).
|     
|   2.2. Acronyms and Abbreviations
|     
|       AS        Autonomous Sytem
|       ASBR      Autonomous System Border Router
|       ATM       Aynchronous Transfer Mode
|       BGP       Borr Gateway Protocol
|       BFD       Bidirectional Forwarding Detection
|       E        Customer-Edge device
|       CoS       Class of Service
|      PU       Central Processor Unit
|       DNS       Domain Name Syste
|       DoS       Denial of Service
|       FEC       Forwarding Equivaence Class
|       GMPLS     Generaized Multi-Protocol Label Switching
|       GRE       Generic Routing Encapulation
|       ICI       InterCarrier Interconnect
|       ICMP      Intrnet Control Message Protocol
|       ICMPv6    ICMP in IP Version 6
|      IGP       Interior Gateway Protocol
|       IKE       Internet Key xchange
|       IP        Internet Protocol
|       IPsec     IP Secuity
|       IPVPN     IP-based VPN
|       LDP       Label Distributio Protocol
|       L2        Layer 2
|       L2TP      Layer 2 Tuneling Protocol
|       L3        Layer 3
|       LMP       Link Managemet Protocol
|       LSP       Label Switched Path
|       LSR       Label Swiching Router
|       MD5       Message Digest Algorithm
|      MPLS      MultiProtocol Label Switching
|       MP-BGP    Multi-ProtocoBGP
|       NTP       Network Time Protocol
|       OAM       Operatios, Administration, and Management
|       PCE      Path Computation Element
|       PE        Provider-Edge device
|       PVPN     Provider-Provisioned Virtual Private Network
|       PSN      Packet-Switched Network
|       PW        Pseudowire
|       QoS      Quality of Service
|       RR       Route Reflector
|       RSVP      Resource Reservation Protocol
|       RSV-TE   Resource Reservation Protocol with Traffic Engineering
|                     Extensions
|       SLA       Service Level Agreement
|      SNMP      Simple Network Management Protocol
|       SP        Srvice Provider
|       SSH       Secure Shell
|       SSL       Secure Sokets Layer
|       SYN       Synchronize packet in TCP
|       TCP      Transmission Control Protocol
|       TM       Time Division Multiplexing
|       TE        Traffic Engineering
|      TLS       Transport Layer Security
|       ToS       Type of Service       TTL       Time-To-Live
|       UDP       User Datagram Protool
|       VC        Virtual Circuit
|       VPN       Virtual Private etwork
|       WG        Working Group of IETF
|       WSS       Web Serices Security
|     
|     
| 3. Scurity Reference Models
|    This section defines a reference model for securty in MPLS/GMPLS
|    networks.  
|     
|    A MPLS/GMPLS core netork is defined here as the centr network
|    infrastructure (P and PE routers). A MPLS/GMPLS core network
    consists of one or more SP networks All network elements in the
|    core are under the operational contol of one or more MPLS/GMPLS
|    SPs. Even if the MPLS/GMPLS core is provded by several SPs,
|    towards the end users itappears as a single zone of trust.
|    However, when several SPs togeter provide a MPLS/GMPLS core, each
|    SP still needsto secure itself against the other SPs.
|     
|    A MPLS/GMPLS nd user is a company, institution, or residential
|    client of the SP.
|     
    This document defines each MPLS/GMPLS core in a single domain to be
|   a trusted zone. A primary concern is about security aspects that
|    elate to breaches of security from the "outside" of a trusted zone
|    t the "inside" of this zone. Figure 1 depicts the concept of
|    trusted zones within the MLS/GMPLS framework.
|  
|  
|                       /-------------\
|    +------------+    /               \         +------------+
|    | MPLSGMPLS +---/                 \--------+     MPLS   |
|    | user         |  MPLS/GMPLS Core  |             user   |
|    | site       +---                 /XXX----+     site   |
|    +------------+    \               / XXX     +-----------+
|                       \-------------/  | |
|                                       | |
|                                        | +-----\
|                                        +-------/  "Internet"
|     
|         MPLS/GMPLS Core with user connectionsand Internet connection
|     
|    Figure 1: The MPLS/GMPLS trusted zon model.

In this figure, is there significance to the fact that the nternet
connection is attached at the MPLS user site?  Why is one MPL only, and
te other referred to as an MPLS/GMPLS site?

|    The trused zone is the MPLS/GMPLS core in a single AS within a
|    single ervice Provider.
|     
|    The boundaries of  trust domain should be carefully defined when
|   analyzing the security property of each individual network, e.g.
|    the boundaries can be at the link termination, remote peers, area,
|    or quite commonly, ASes.
|     
|    In principle, the trused zones should be separate; however,
|    typically MPLS core etworks also offer Internet access, in which
|    case a transi point (marked with "XXX" in Figur1) is defined. In

So is the Internet access from within the core?  If so, what s the
boundary?

|    the case of MPLS/GMPLS inter-provider connections, he trusted zone
|    of each provider ends at the respective ASBRs (ASB1 and ASBR2 for
|    Provider A, ASBR3 and ASBR4 for Provider B).
|    
|    A key requirement of MPLS and GMPLS networks s that the security
|    of the trusted zone not be comprmised by interconnecting the
|    MPLS/GMPLS core infrastructure with another povider's core
|    (MPLS/GMPLS or non-MPLS/GMPLS), the Internet, or ed users.
|     
|    In addition, neighbors may be trusted or untrused. Neighbors may
|    be authorized or unauthorized. Even though a nighbor may be
|    authorized for communication, it may not be trusted. or example,
|    when connecting with another provider's ASBRs toset up inter-AS
|    LSPs, the other provider is considered an untrustedbut authorized
|    neighbor. 
|  
|                  
|                +---------------+        +--------------+
|                 |               |        |                |
|                | MPLS/GMPLS   ASBR1----ASBR3  MPLS/GMPLS |
|           CE1-PE1   Network    |        |     Network   PE2--CE2
|                | Provider A   ASBR2----ASBR4  Provider B |
|                 |              |        |                |
|                 +---------------+       +----------------+
|                  
|         
|    For Provide A:
|         Trusted Zone: Provider A MPSL/GMPLS network
|         Trsted neighbors: PE1, ASBR1, ASBR2
|         Authorized but untrusted neghbor: provider B
|         Unauthorized neighbors: CE1, CE2
|  
|    Figure 2. MPLS/GMPLS trusted zone and authorized neighbor.
|  
|     
|   All aspects of network security independent of whher a network is
|    a MPLS/GMPLS network are out of scope. For example, attack from
|    the Internet to a user's web-server connected through the
|   MPLS/GMPLS network are not considered here, unless the way the    MPLS/GMPLS network is provisioned could make a difference to the
|    securiy of this user's server.
|  
| 4. Security Threats
|     
|    This sectin discusses the various network security threats that
|    may endangerMPLS/GMPLS networks.  The discussion is limited 
|    those threats that are unique to MPLS/GMPLS networks o that affect
|    MPLS/GMPLS network in unique ways.
|     
|    A successful atack on a particular MPLS/GMPLS network or on a SP's
|    MPLS/GMPLS infrstructure may cause one or more of the following
|    ill effects: 
|    
|     - Observation, modification, or deletion of a provide's or user's
|       data. 
|     - Replay of a provider's or uses data.
|     - Injection of inauthentic data into a provider's or user's
|      traffic stream.
|     - Traffic pattern analysis on a provider' or user's traffic.
|     - Disruption of a provider's or user's connectvity.
|     - Degradation of a provider's service quality.
|     
|    It iseful to consider that threats, whether malicious or
|    accidental, may com from different categories of sources.  For
|    example they may coe from:
|     
|     - Other users whose services are provided by th same MPLS/GMPLS
|       core. 
|     - The MPLS/GMPLS SP or perons working for it.
|    - Other persons who obtain physical access to a MPLS/GMPLS SP's
|    ste. 
|     - Other persons who use social engineering methods to influence
|      the behavior of a SP's personnel.
|     - Users of the MPLS/GMPLS ntwork itself, e.g., intra-VPN threats.
|       (Such threats are beyond he scope of this document.)

Why is only this called out?  In fact if the others are applicable,
should this also not be applicable?

     - Others, e.g., attackers from the Internet at large.
|     - Other Ps in the case of MPLS/GMPLS Inter-
|       provider connection. Th core of the other provider may or may
|       not be using MPLS/GMPLS.
|    - Those who create, deliver, install, and maintain software for
|      network equipment.
|     
|    
|    Given that security is generally a tradeoff between expense and
|    rik, it is also useful to consider the likelihood of different
|    attacs occurring.  There is at least a perceved difference in the
|    likelihood of most types of attacks being successflly mounted in
|    different environments, such as:
|     
|     - A PLS/GMPLS core inter-connecting with another provider's core
|     - A MPS/GMPLS configuration transiting the public Internet
|     
|    Most tyes of attacks become easier to mount and hence more likely
|    as the sared infrastructure via which service is provided expands
|    from a single SP to multiple cooperating SPs to the global
|    Internet.  Attaks that may not be of sufficient likeliness to
|    warrant concern in aclosely controlled environment often merit
|    defensive measures in broader more open environments. In closed
|    communities, it is often practicl to deal with misbehavior after
|    the fact: an employee can be diiplined, for example.
|     
|    The following sections discuss specfic types of exploits that
|    threaten MPLS/GMPLS networks.
|     
|   4.1. Attacks on the Control Plane
|    This category encompasses atacks on the control structures
|    operated by the SP with MPLS/GMPLScores.
|     

This section contains multiple separate elements.  They ned to be
grouped together.  There are the general elements:

   41.1.       LSP creation by an unauthorized element
   4.1.2.      LSP message interception
   4.1.5.       Denial of Service Attacks onthe Network Infrastructure
   4.1.6.       Attacks on the SP's MPLS/GMPS Equipment via
               Management Interfaces
   4.1.8.       Cross-Connection of Traffic between Users
   4.1.9.       Attacks against Routing Protocols
   4.1.10.      Other Attacks on Contol Traffic

Separately, probably as a sub clause in 4.1.9, you shoul put 4.1.3 and
4.1.4.  I would think that Section 4.1.7 on social enginering should be
in its own category.

|    4.1.7.       Social Enginering Attacks on the SP's Infrastructure

|    4.1.1.       LSP creaton by an unauthorized element
|  
|    The unauthorized element can bea local CE or a router in another
|    domain.  An unauthorized elment can generate MPLS signaling
|    messages.  At the least, thi can result in extra control plane and
|    forwarding state, andif successful, network bandwidth could e
|    reserved unnecessarily. This may also result in theft of service
|    nd loss of revenue.

This type of attack could come from eitherunauthorized (CE) sources,
or authorized, but untrusted sources (ABR), rght?  If the attack
fails, it creates overload in the control plane.  Ifit succeeds,
it resuls in creation of bogus forwarding state, probablystealing
of network bandwidth in the dataplane, and, if te signalling were
propagated into the trusted zone, comromizes the entire network.
THe latter could occur because the forwarded signallng state is coming
from a trusted router, and is typically assumed to e therefore trusted.

|    4.1.2.      LSP message interception
|     
|    This threat might be accomplished by montoring network traffic,
|    for example, after a physical intrusion. Wthout physical
|    intrusion, it could be accomplished with an unauthrized software
|    modification. Also many technologies such as terrstrial microwave,
|    satellite, or free-space optical could beintercepted without
|    physical intrusion. If successful, it could proide information
|    leading to label spoofing attacks.  It also raise confidentiality
|    issues. 

ok.

|    4.1.3.       Attacks against RVP-TE
|  
|    RSVP-TE, described in [RFC9], is the control protocol used to
|    set up GMPLS and traffic engineered MPL tunnels.
|     
|    There are two major types of Denial of Service (DoS attacks
|    against a MPLS domain based on RSVP-TE. The attacker may se up
|    numerous unauthorized LSPs or may send a stom of RSVP messages.
|    It has been demonstrated that unproected routers running RSVP can
|    be effectively disaed by both types of DoS attacks.
|     
|    These attacks may evenbe combined, by using the unauthorized LSPs
|    to transport additionl RSVP (or other) messages across routers
|    where they might otherwis be filtered out.  RSVP attacks can be
|    launched against adjacnt routers at the border with the attacker,
|    or against non-adjacnt routers within the MPLS domain, if there is
|    no effective mechanim to filter them out.

These are protocol specific cases.  Either hese should be under control
plane vulnerabilities speficic to a ruting protocol, or a use cases
section where the applicability of each vetor specific to a protocl is
worked out.  In a more rigourous context, it should probably be 
separate document after this one is done.

|    4.1.4.       Attacks gainst LDP
|     
|    LDP, described in [RFC3036], is the control protcol used to set up
|    MPLS tunnels without TE.
|     
|    There aretwo significant types of attack against LDP.  An
|    unauthorized netwok element can establish a LDP session by sending
|    LDP Hello and LDP nit messages, leading to the otential setup of
|    a LSP, as well asaccompanying LDP state table consumption.  Even
|    without successfully estabshing LSPs, an attacker can launch a
|    DoS attack in the form of a storm of LP Hello messages or LDP TCP
|    Syn messages, leading to high CPU utilzation on the target router.

Likewise.

|     
|    4.1.5.       Deial of Service Attacks on the Nwork
|    Infrastructure
|     
|    DoS attacks could be accomplished throuh a MPLS signaling storm,
|    resulting in high CPU utilization and pssibly leading to control
|    plane resource starvation.

Would you caracterise attacks on the dataplane that keep the
dataplane busy withuseless work as DoS attacks?  For instance, label
spoofing attempts.Knowing the label allocation patterns of a router
also makes it easy to moun such attacks in the dataplane.

|    Control plane DoS attacks an be mounted specifically against the
|    mechanisms the SP uses toprovide various services, or against the
|    general infrastructure ofthe service provider, e.g., P routers or
|   shared aspects of PE routers.  (An attack against the general
|    ifrastructure is within the scope of this document only if the
|    attackcan occur in relation with the MPLS/GMPLS infrastructure;
|    otherwie is not a MPLS/GMPLS-specific issue.)

It was very hard for me to pars what was said here.  For instance,
what is an example o a mechanism that a SP would use to provide
services?  If I had a sense of that,I could then have a sense of what
kinds of attacks to consider.

Also, yo view P routers are "general infrastructure" here?  I thought
that aP router, from your original description, was part of the
MPLS/GMPLS ifrastructure.  Does this document preclude attacks on P
routers?

r maybe, I am readinthis paragraph all wrong?

|    The attacks described in the following sectios may each have
|    denial of service as one of their effects.  OtherDoS attacks are
|    also possible.
|     
|    4.1.6.       Attacks o the SP's MPLS/GMPLS Equipment via
|    Management Interfaces
|     
|   This includes unauthorized access to a SP's infrastructure
|    equiment, for example to reconfigure the equipment or to extract
|    inormation (statistics, topology, etc.) pertaining to the network

Would this not consititute an atack on the general infrastructure
itself, not specifically MPLS/GMPLS infrastruture, and anything done ot
protect there will apply here---in otherwords, out of scope in this
document?

|    4.1.7.       Social Engineerig Attacks on the SP's
|    Infrastructure
|  
|    Attacks in which the srvice provider network is reconfigured or
|    damaged, or in which cnfidential information is improperly
|    disclosed, may be mounted by maipulation of a SP's personnel.
|    These types of attacks are MPLS/GMLS-specific if they affect
|    MPLS/GMPLS-serving mechanisms.

Again,this appears to not be specific to MPLS/GMPLS infrastructure?

|    4.1.8       Cross-Connection of Traffic between Users
|    
|    This refers to the event in which expected isolation between|    separate users (who may be VPN users) is breached.  This includes|    cases such as:
|     - A site being connected into the "wrong" PN
|     - Traffic being replicated and sent to an unauthorized use
|     - Two or more VPNs being improperly merged together
|     - A pont-to-point VPN connecting the wrong two points
|     - Any packet or rame being improperly delivered outside the VPN
|       to which it belons
|     
|    Mis-connection or crosconnection of VPNs may be caused by service
|    provider or equipment vendor error, or by the malicious action of
|    an attacker. The breach may be physical (e.g., PE-CE links mis-
|    connected) or logical (e.g., improper device configuration).
|     
|    Anecdotal evidence suggests that the cross-connection threat is one
|    of the largest security concerns of users or would-be users).

ok.

|    4.1.9.       Attacks against Routig Protocols
|     
|    This encompasses attacks against underlying outing protocols that
|    are run by the SP and that directly suport the MPLS/GMPLS core.
|    (Attacks against the use of routing prtocols for the distribution
|    of backbone routes are beyond the scoof this document.)
|    Specific attacks against popular routing protocols hve been widely
|    studied and described in [RFC4593].
|     
    4.1.10.      Other Attacks on Control Traffic
|     
|    Besides routing and management protocols (covered separately inthe
|    previous sections), a number ofother control protocols may be
|    directly inolved in delivering services by the MPLS/GMPLS core.
|    These include but my not be limited to:
|     
|     - MPLS signaling (LDP, RSVP-TE) discused above in subsections
|       4.1.4 and 4.1.3
|     - PCE signaling|     - IPsec signaling (IKE and IKEv2)
|     - ICMP and ICMPv6
|     - 2TP 
|     - BGP-based membership discovery
|     - Database-based membeship discovery (e.g., RADIUS)
|     - Other protocols that may be impotant to the control
|       infrastructure, e.g., DNS, LMP, NTP, SNMP,and GRE.
|     
|    Attacks might subvert or disrupt the activities of tese protocols,
|    for example via impersonation or DoS.
|     
|    4.. Attacks on the Data Plane
|     
|    This category encompasses attaks on the provider's or end user's
|    ata.  Note that from the MPLS/GMPLS network end user's point of
|    view, som of this might be control plane traffic, e.g. routing
|    protocols rning from user site A to user site B via a L2 or L
|    connection, which may be some type of VPN.

|    4.2.1.       Unauthrized Observation of Data Traffic
|     
|    This refers to "sniffing"provider or end user packets and
|    examining their contents.  This cn result in exposure of
|    confidential information.  It can also be a firt step in other
|    attacks (described below) in which the recorded ata is modified
|    and re-inserted, or simply replayed later.
|    
|    4.2.2.       Modification of Data Traffic
|     
|    This rfers to modifying the contents of packets as they traverse
|    the MPS/GMPLS core.
|     
|    4.2.3.       Insertion of Inauthentic Data Trafic: Spoofing
|    and Replay 
|     
|    Spoofing refers to sending a usr or inserting into a data stream
|    packets that do not belong, with he objective of having them
|    accepted by the recipient as legitimat.  Also included in this
|    category is the insertion of copies f once-legitimate packets that
|    have been recorded and replayed.
|    
|    4.2.4.       Unauthorized Deletion of Data Traffic
|     
|   This refers to causing packets to be discarded as they traverse the
|   MPLS/GMPLS networks.  This is a specific type of Denial of Service
|   attack. 
|     
|    4.2.5.       Unauthorized Traffic Pattern Analysi
|     
|    This refers to "sniffing" provider or user packets and examining|    aspects or meta-aspects of them that may be visible even when the
|   packets themselves are encrypted.  An attacker might gain useful
    information based on the amount and timing of traffic, packet
|    szes, source and destination addresses, etc.  For most users, this
|   type of attack is generally considered to be significantly les of
|    a concern than the other types discussed in this section.

It s also that a lot of the above dataplane attacks require physical
accss/control of the device  Mounting these attacks through remote
means is probablynot trivial.

|    4.2.6.       Denial of Service Attacks
|     
|    Denial o Service (DoS) attacks are those in which an attacker
|    attemts to disrupt or prevent the use of a serice by its
|    legitimate users.  Taking network devices out of service, modifing
|    their configuration, or overwhelming them with requests for serice
|    are several of the possible avenues for DoS attack.
|     
|    verwhelming the network with requests for service, otherwise known
|   as a "resource exhaustion" DoS attack, may target any resource i
|    the network, e.g., link bandwidth, paket forwarding capacity,
|    session capacity for vrious protocols, CPU power, table size,
|    storage overflows, and s on.
|     
|    DoS attacks of the resource exhaustion type can b mounted against
|    the data plane of a particular provider or end user by attempting
|    to insert (spoofing) an overwhelming quantity ofinauthentic data
|    into the provideror end user network from the outside of the
|    trusted zone. Potentia results might be to exhaust the bandwidth
|    available to that provier or end user or to overwhelm the
|    cryptographic authenication mechanisms of the provider or end
|    user. 
|     
|    Data plane esource exhaustion attacks can also be mounted by
|    overwelming the service provider's general (MPLS/GMPLS-
|    indepndent) infrastructure with traffic.  These attacks on the 
|    general infrastructure are ot usually a MPLS/GMPLS-specific issue, 
|    unless the attack is mountd by another MPLS/GMPLS network user 
|    from a privileged position  (E.g., a MPLS/GMPLS network user might 
|    be able to monopoize network data plane resources an thus disrupt 
|    other users.) 

DoS atacks can lead to SLA violations by the SP, particularly if
significant resources are consumed either servicing the DoS or working
to fend it off.

Also, what about label spoofing in the data plane?  How does it get
created, and how would it get detected/mitigated?  It is mentioned in
the dataplane context in other places.  Why do we believe label spoofing
is only critical in a inter-provider context?

|    Many DoS attacks use amplification, whereby the attacker co-opts 
|    otherwise innocent parties to increase the effect of the attack. 
|    The attacker may, for example, send packets to a broadcast or 
|    multicast address with the spoofed source address of the victim, 
|    and all of the recipients may then respond to the victim.  
|  
|  
| 5. Defensive Techniques for MPLS/GMPLS Networks 
|     
|    The defensive techniques discussed in this document are intended to 
|    describe methods by which some security threats can be addressed.  
|    They are not intended as requirements for all MPLS/GMPLS 
|    implementations.  The MPLS/GMPLS provider should determine the 
|    applicability of these techniques to the provider's specific 
|    service offerings, and the end user may wish to assess the value of 
|    these techniques to the user's service requirements. The 
|    operational environment determines the security requirements. 
|    Therefore, protocol designers need to provide a full set of 
|    security services, which can be used where appropriate. 
|     
|    The techniques discussed here include encryption, authentication, 
|    filtering, firewalls, access control, isolation, aggregation, and 
|    other techniques.  
|     
|    Often, security is achieved by careful protocol design, rather than 
|    by adding a security method. For example, one method of mitigating 
|    DoS attacks is to make sure that innocent parties cannot be used to 
|    amplify the attack. Security works better when it is "designed in" 
|    rather than "added on." 
|     
|    Nothing is ever 100% secure.  Defense therefore involves protecting 
|    against those attacks that are most likely to occur or that have 
|    the most direct consequences if successful.  For those attacks that 
|    are protected against, absolute protection is seldom achievable; 
|    more often it is sufficient just to make the cost of a successful 
|    attack greater than what the adversary will be willing or able to 
|    expend. 
|     
|    Successfully defending against an attack does not necessarily mean 
|    the attack must be prevented from happening or from reaching its 
|    target.  In many cases the network can instead be designed to 
|    withstand the attack.  For example, the introduction of inauthentic 
|    packets could be defended against by preventing their introduction 
|    in the first place, or by making it possible to identify and 
|    eliminate them before delivery to the MPLS/GMPLS user's system.  
|    The latter is frequently a much easier task. 
|     
|  
|    5.1. Authentication 
|     
|    To prevent security issues arising from some Denial-of-Service 
|    attacks or from malicious or accidental misconfiguration, it is 
|    critical that devices in the MPLS/GMPLS should only accept 
|    connections or control messages from valid sources.  Authentication 
|    refers to methods to ensure that message sources are properly 
|    identified by the MPLS/GMPLS devices with which they communicate.  
|    This section focuses on identifying the scenarios in which sender 
|    authentication is required and recommends authentication mechanisms 
|    for these scenarios. 
|     
|    Cryptographic techniques (authentication, integrity, and 
|    encryption) do not protect against some types of denial of service 
|    attacks, specifically resource exhaustion attacks based on CPU or 
|    bandwidth exhaustion. In fact, the processing required to decrypt 
|    or check authentication may, in the case of software-based 
|    cryptographic processing, in some cases increase the effect of 
|    these resource exhaustion attacks. With a hardware cryptographic 
|    accelerator, attack packets can be dropped at line speed without a 
|    cost of software cycles. Cryptographic techniques may, however, be 
|    useful against resource exhaustion attacks based on exhaustion of 
|    state information (e.g., TCP SYN attacks). 
|     
|    The MPLS user plane, as presently defined, is not amenable to 

What is this MPLS user plane?  Where is it defined?

|    source authentication as there are no source identifiers in the 
|    MPLS packet to authenticate. The MPLS label is only locally 
|    meaningful, and it identifies a downstream semantic rather than an 
|    upstream source. 
|      
|    When the MPLS payload carries identifiers that may be authenticated 
|    (e.g., IP packets), authentication may be carried out at the client 
|    level, but this does not help the MPLS SP, as these client 
|    identifiers belong to an external, untrusted network. 
|      
| 
|   5.1.1. Management System Authentication 
|  
|    Management system authentication includes the authentication of a 
|    PE to a centrally-managed network management or directory server 
|    when directory-based "auto-discovery" is used.  It also includes 
|    authentication of a CE to the configuration server, when a 
|    configuration server system is used. 

This is not clear.  Why is device authentication restricted only to the
CE or PE?  Why is this considered differently than peer-to-peer
authentication?  Aren't the techniques and issues similar?

|   5.1.2. Peer-to-Peer Authentication 
|  
|    Peer-to-peer authentication includes peer authentication for 
|    network control protocols (e.g., LDP, BGP, etc.), and other peer 
|    authentication (i.e., authentication of one IPsec security gateway 
|    by another). 
|     
| 
|   5.1.3. Cryptographic techniques for authenticating identity 
|     
|    Cryptographic techniques offer several mechanisms for 
|    authenticating the identity of devices or individuals. These 
|    include the use of shared secret keys, one-time keys generated by 
|    accessory devices or software, user-ID and password pairs, and a 
|    range of public-private key systems. Another approach is to use a 
|    hierarchical Certification Authority system to provide digital 
|    certificates. 

Again, here I would think that device authentication is somewhat
different from individuals being authenticated?

In a gist, I would think that this section ought to outline that
entities across a trust or authorization boundary need to be
authenticated to ensure that the entitiers are who they are, and
appropriately define their roeles and responsibilities on this device.
In this context, the CE, and neighbour PEs are entities that need to be
authenticated.  Not direclty in the trust relationship, but equally
important, is for the management system to be similarly authenticated.
The inverse of this is that the device must simliarly provide its
authentication credentials to each of those entities.  THen, we ought to
outine the techniques for authentication, including source
authentication, and its difficulties, and the ability to do
cryptographic authentication.  This then segues into the next section.

|    This section describes or provides references to the specific 
|    cryptographic approaches for authenticating identity.  These 
|    approaches provide secure mechanisms for most of the authentication 
|    scenarios required in securing a MPLS/GMPLS network. 
|     
|     
|    5.2. Cryptographic Techniques 
|     
|    MPLS/GMPLS defenses against a wide variety of attacks can be 
|    enhanced by the proper application of cryptographic techniques.  
|    These are the same cryptographic techniques that are applicable to 
|    general network communications.  In general, these techniques can 
|    provide confidentiality (encryption) of communication between 
|    devices, can authenticate the identities of the devices, and can 
|    ensure that it will be detected if the data being communicated is 
|    changed during transit. 
|     
|    Several aspects of authentication are addressed in some detail in a 
|    separate "Authentication" section. 
|     
|    Cryptographic methods add complexity to a service and thus, for a 
|    few reasons, may not be the most practical solution in every case. 
|    Cryptography adds an additional computational burden to devices, 
|    which may reduce the number of user connections that can be handled 
|    on a device or otherwise reduce the capacity of the device, 
|    potentially driving up the provider's costs.  Typically, 

This compute burden is going down over time as CPUs become more
powerful, and hardware acceleration of crypto is more generally
available.  Also, isn't it that these crypto techniques are only
required for the validation of signalling messages?

|    configuring encryption services on devices adds to the complexity 
|    of their configuration and adds labor cost. Some key management 
|    system is usually needed. Packet sizes are typically increased when 

With experience, we are getting better are making key management
configuration more turnkey and simpler.  However, the harder problem
also needs to be acknowledged of providing for the ability to change
keys as needed, as well as a recommendation for SPs to have a policy
to changes these keys every so often.

|    the packets are encrypted or have integrity checks or replay 
|    counters added, increasing the network traffic load and adding to 
|    the likelihood of packet fragmentation with its increased overhead.  
|    (This packet length increase can often be mitigated to some extent 
|    by data compression techniques, but at the expense of additional 
|    computational burden.) Finally, some providers may employ enough 
|    other defensive techniques, such as physical isolation or filtering 
|    and firewall techniques, that they may not perceive additional 
|    benefit from encryption techniques. 
|     
|    Users may wish to provide confidentiality end to end. Generally, 
|    encrypting for confidentiality must be accompanied with 
|    cryptographic integrity checks to prevent certain active attacks 
|    against the encrypted communications. On today's processors, 
|    encryption and integrity checks run extremely quickly, but key 
|    management may be more demanding in terms of both computational and 
|    administrative overhead. 

I would think that end-to-end encryption is generally a good idea
for customers wishing to protect their data, but is orthogonal to
MPLS/GMPLS.  Why do we need to mention it here?

|    The trust model among the MPLS/GMPLS user, the MPLS/GMPLS provider, 
|    and other parts of the network is a major element in determining 
|    the applicability of cryptographic protection for any specific 
|    MPLS/GMPLS implementation. In particular, it determines where 
|    cryptographic protection should be applied: 
|    -  If the data path between the user's site and the 
|       provider's PE is not trusted, then it may be used on the 
|       PE-CE link. 
|    -  If some part of the backbone network is not trusted, 
|       particularly in implementations where traffic may travel 
|       across the Internet or multiple providers' networks, then 
|       the PE-PE traffic may be cryptographically protected. One 
|       also should consider cases where L1 technology may be 
|       vulnerable to eavesdropping. 
|    -  If the user does not trust any zone outside of its 
|       premises, it may require end-to-end or CE-CE cryptographic 
|       protection. This fits within the scope of this MPLS/GMPLS 
|       security framework when the CE is provisioned by the 
|       MPLS/GMPLS provider. 

    However, this leads to whether the end user trusts the SP to
    provide appropriate crypto protection on a shared device, or should
    provision their own through other means.  Also, the peer CE for this
    user may be across an inter-provider boundary, in which case, the SP
    can only provision one end of the crypto link.

|    -  If the user requires remote access to its site from a 
|       system at a location that is not a customer location (for 
|       example, access by a traveler) there may be a requirement 
|       for cryptographically protecting the traffic between that 
|       system and an access point or a customer's site. If the 
|       MPLS/GMPLS provider supplies the access point, then the 
|       customer must cooperate with the provider to handle the 
|       access control services for the remote users. These access 
|       control services are usually protected cryptographically, 
|       as well. 
|     
|    Access control usually starts with authentication of the 
|    entity. If cryptographic services are part of the scenario, 
|    then it is important to bind the authentication to the key 
|    management. Otherwise the protocol is vulnerable to being 
|    hijacked between the authentication and key management. 
|     
|    Although CE-CE cryptographic protection can provide integrity and 
|    confidentiality against third parties, if the MPLS/GMPLS provider 
|    has complete management control over the CE (encryption) devices, 
|    then it may be possible for the provider to gain access to the 
|    user's traffic or internal network. Encryption devices could 
|    potentially be reconfigured to use null encryption, bypass 
|    cryptographic processing altogether, reveal internal configuration, 
|    or provide some means of sniffing or diverting unencrypted traffic. 
|    Thus an implementation using CE-CE encryption needs to consider the 
|    trust relationship between the MPLS/GMPLS user and provider. 
|    MPLS/GMPLS users and providers may wish to negotiate a service 
|    level agreement (SLA) for CE-CE encryption that provides an 
|    acceptable demarcation of responsibilities for management of 
|    cryptographic protection on the CE devices. The demarcation may 
|    also be affected by the capabilities of the CE devices. For 
|    example, the CE might support some partitioning of management, a 
|    configuration lock-down ability, or shared capability to verify the 
|    configuration. In general, the MPLS/GMPLS user needs to have a 
|    fairly high level of trust that the MPLS/GMPLS provider will 
|    properly provision and manage the CE devices, if the managed CE-CE 
|    model is used. 
|     
|     
| 
|   5.2.1. IPsec in MPLS/GMPLS 
|  
|    IPsec [RFC4301] [RFC4302] [RFC4835] [RFC4306] [RFC2411] is the 
|    security protocol of choice for encryption at the IP layer (Layer 
|    3).  IPsec provides robust security for IP traffic between pairs of 
|    devices.  Non-IP traffic such as IS-IS routing must be converted to 
|    IP (e.g., by encapsulation) in order to use IPsec.  
|  
|    In the MPLS/GMPLS model, IPsec can be employed to protect IP 
|    traffic between PEs, between a PE and a CE, or from CE to CE.  CE-
|    to-CE IPsec may be employed in either a provider-provisioned or a 
|    user-provisioned model.  Likewise, IPsec protection of data 
|    performed within the user's site is outside the scope of this 
|    document, because it is simply handled as user data by the 
|    MPLS/GMPLS core. However, if the SP performs compression, pre-
|    encryption will have a major effect on that operation. 
|     
|    IPsec does not itself specify an encryption algorithm.  It can use 
|    a variety of integrity or confidentiality algorithms (or even 
|    combined integrity and confidentiality algorithms), with various 
|    key lengths, such as AES encryption or AES message integrity 
|    checks.  There are trade-offs between key length, computational 
|    burden, and the level of security of the encryption.  A full 
|    discussion of these trade-offs is beyond the scope of this 
|    document.  In practice, any currently recommended IPsec protection 
|    offers enough security to reduce the likelihood of its being 
|    directly targeted by an attacker substantially; other weaker links 
|    in the chain of security are likely to be attacked first.  
|    MPLS/GMPLS users may wish to use a Service Level Agreement (SLA) 
|    specifying the SP's responsibility for ensuring data integrity and 
|    confidentiality, rather than analyzing the specific encryption 
|    techniques used in the MPLS/GMPLS service. 
|     
|    Encryption algorithms generally come with two parameters: mode such 
|    as Cipher Block Chaining and key length such as AES-192. (This 
|    should not be confused with two other senses in which the word 
|    "mode" is used: IPsec itself can be used in Tunnel Mode or 
|    Transport Mode, and IKE [version 1] uses Main Mode, Aggressive 
|    Mode, or Quick Mode). It should be stressed that IPsec encryption 
|    without an integrity check is a state of sin. 
|     
|    For many of the MPLS/GMPLS provider's network control messages and 
|    some user requirements, cryptographic authentication of messages 
|    without encryption of the contents of the message may provide 
|    appropriate security.  Using IPsec, authentication of messages is 
|    provided by the Authentication Header (AH) or through the use of 
|    the Encapsulating Security Protocol (ESP) with NULL encryption.  
|    Where control messages require integrity but do not use IPsec, 
|    other cryptographic authentication methods are often available.  
|    Message authentication methods currently considered to be secure 
|    are based on hashed message authentication codes (HMAC) [RFC2104] 
|    implemented with a secure hash algorithm such as Secure Hash 
|    Algorithm 1 (SHA-1) [RFC3174]. No attacks against HMAC SHA-1 are 
|    likely to play out in the near future, but it is possible that 
|    people will soon find SHA-1 collisions. Thus, it is important that 
|    mechanisms be designed to be flexible about the choice of hash 
|    functions and message integrity checks. Also, many of these 
|    mechanisms do not include a convenient way to manage and update 
|    keys.  
|     
|    A mechanism to provide a combination of confidentiality, data 
|    origin authentication, and connectionless integrity is the use of 
|    AES in CCM (Counter with CBC-MAC) mode (RFC 4309) [RFC4309], with 
|    an explicit initialization vector (IV), as the IPsec ESP. Recently, 
|    GCM is rapidly replacing CCM as the preferred method: [RFC4103]. 
|     
|    MPLS and GMPLS, which provide differentiated services based on 
|    traffic type, may encounter some conflicts with IPsec encryption of 
|    traffic.  Because encryption hides the content of the packets, it 
|    may not be possible to differentiate the encrypted traffic in the 
|    same manner as unencrypted traffic.  Although DiffServ markings are 
|    copied to the IPsec header and can provide some differentiation, 
|    not all traffic types can be accommodated by this mechanism. Using 
|    IPsec without IKE or IKEv2 (the better choice) is not advisable. 
|    IKEv2 provides IPsec Security Association creation and management, 
|    entity authentication, key agreement, and key update. It works with 
|    a variety of authentication methods including pre-shared keys, 
|    public key certificates, and EAP. If DoS attacks against IKEv2 are 
|    considered an important threat to mitigate, the cookie-based anti-
|    spoofing feature of IKEv2 should be used. IKEv2 has its own set of 
|    cryptographic methods, but any of the default suites specified in 
|    [RFC4308] or [RFC4869] provides more than adequate security.  

Also, does it make sense to think of MPLSsec natively?  What are your
thoughts/tradeoffs for doing this?  I would think there is value/merit
to this idea.

Another one is how does P2MP tunnels affect crypto establishment CE-CE?
What are your thoughts here?

|   5.2.2. Encryption for device configuration and management 
|  
|    For configuration and management of MPLS/GMPLS devices, encryption 
|    and authentication of the management connection at a level 
|    comparable to that provided by IPsec is desirable.   
|     
|    Several methods of transporting MPLS/GMPLS device management 
|    traffic offer security and confidentiality. 
|    -  Secure Shell (SSH) offers protection for TELNET [STD-8] or 
|       terminal-like connections to allow device configuration. 
|    -  SNMPv3 [STD62] provides encrypted and authenticated protection 
|       for SNMP-managed devices. 
|    -  Transport Layer Security (TLS) [RFC4346] and the closely-related 
|       Secure Sockets Layer (SSL) are widely used for securing HTTP-
|       based communication, and thus can provide support for most XML- 
|       and SOAP-based device management approaches. 
|    -  Since 2004, there has been extensive work proceeding in several 
|       organizations (OASIS, W3C, WS-I, and others) on securing device 
|       management traffic within a "Web Services" framework, using a 
|       wide variety of security models, and providing support for 
|       multiple security token formats, multiple trust domains, 
|       multiple signature formats, and multiple encryption 
|       technologies.   
|    -  IPsec provides the services with integrity and confidentiality 
|       at the network layer. With regards to device management, its 
|       current use is primarily focused on in-band management of user-
|       managed IPsec gateway devices. 
|    -  There are recent work in ISMS WG (Integrated Security Model for 
|       SNMP Working Group) to define how to use SSH to secure SNMP, due 
|       to the limited deployment of SNMPv3; and the possibility of 
|       using Kerberos, particularly for interfaces like TELNET, where 
|       client code exists. 

yep.

|   5.2.3.  Security Considerations for MPLS Pseudowires 
|   
|    In addition to IP traffic, MPLS networks may be used to transport 
|    other services such as Ethernet, ATM, Frame Relay, and TDM. This is 
|    done by setting up pseudowires (PWs) that tunnel the native service 
|    through the MPLS core by encapsulating at the edges. The PWE 
|    architecture is defined in [RFC3985].  
|     
|    PW tunnels may be set up using the PWE control protocol based on 
|    LDP [RFC4447], and thus security considerations for LDP will most 
|    likely be applicable to the PWE3 control protocol as well.   
|     
|    PW user packets contain at least one MPLS label (the PW label) and 
|    may contain one or more MPLS tunnel labels.  After the label stack 
|    there is a four-byte control word (which is optional for some PW 
|    types), followed by the native service payload.  It must be 
|    stressed that encapsulation of MPLS PW packets in IP for the 
|    purpose of enabling use of IPsec mechanisms is not a valid option. 
|      
|    The PW client traffic may be secured by use of mechanisms beyond 
|    the scope of this document.  

Why are we only discussing PWE here?  What about VPLS or 2547?  Are the
considerations the same or different?

|    5.2.4.       End-to-End versus Hop-by-Hop Protection Tradeoffs 
|    in MPLS/GMPLS 

THis should really be section 5.2.1, since the notion of where to apply
is the main idea put out by 5.2.

|    In MPLS/GMPLS, cryptographic protection could potentially be 
|    applied to the MPLS/GMPLS traffic at several different places.  
|    This section discusses some of the tradeoffs in implementing 
|    encryption in several different connection topologies among 
|    different devices within a MPLS/GMPLS network. 
|     
|    Cryptographic protection typically involves a pair of devices that 
|    protect the traffic passing between them.  The devices may be 
|    directly connected (over a single "hop"), or intervening devices 
|    may transport the protected traffic between the pair of devices.  
|    The extreme cases involve using protection between every adjacent 
|    pair of devices along a given path (hop-by-hop), or using 
|    protection only between the end devices along a given path (end-to-
|    end).  To keep this discussion within the scope of this document, 
|    the latter ("end-to-end") case considered here is CE-to-CE rather 
|    than fully end-to-end. 
|     
|    Figure 3 depicts a simplified topology showing the Customer Edge 
|    (CE) devices, the Provider Edge (PE) devices, and a variable number 
|    (three are shown) of Provider core (P) devices, which might be 
|    present along the path between two sites in a single VPN operated 
|    by a single service provider (SP). 
|     
|     
|    Site_1---CE---PE---P---P---P---PE---CE---Site_2 
|     
|    Figure 3: Simplified topology traversing through MPLS/GMPLS core. 
|     


|    Within this simplified topology, and assuming that the P devices 
|    are not involved with cryptographic protection, four basic, 
|    feasible configurations exist for protecting connections among the 
|    devices: 
|     
|    1) Site-to-site (CE-to-CE) - Apply confidentiality or integrity 
|    services between the two CE devices, so that traffic will be 
|    protected throughout the SP's network. 
|     
|    2) Provider edge-to-edge (PE-to-PE) - Apply confidentiality or 
|    integrity services between the two PE devices.  Unprotected traffic 
|    is received at one PE from the customer's CE, then it is protected 
|    for transmission through the SP's network to the other PE, and 
|    finally it is decrypted or checked for integrity and sent to the 
|    other CE. 
|     
|    3) Access link (CE-to-PE) - Apply confidentiality or integrity 
|    services between the CE and PE on each side or on only one side. 
|     
|    4) Configurations 2 and 3 above can also be combined, with 
|    confidentiality or integrity running from CE to PE, then PE to PE, 
|    and then PE to CE. 
|     
|    Among the four feasible configurations, key tradeoffs in 
|    considering encryption include: 
|     
|    - Vulnerability to link eavesdropping or tampering - assuming an 
|    attacker can 
|       observe or modify data in transit on the links, would it be 
|    protected by encryption? 
|     
|    - Vulnerability to device compromise - assuming an attacker can get 
|    access to a device (or freely alter its configuration), would the 
|    data be protected? 
|     
|    - Complexity of device configuration and management - given the 
|    number of sites per VPN customer as Nce and the number of PEs 
|    participating in a given VPN as Npe, how many device configurations 
|    need to be created or maintained, and how do those configurations 
|    scale? 
|     
|    - Processing load on devices - how many cryptographic operations 
|    must be performed given N packets? - This raises considerations of 
|    device capacity and perhaps end-to-end delay. 
|     
|    - Ability of the SP to provide enhanced services (QoS, firewall, 
|    intrusion detection, etc.) - Can the SP inspect the data to provide 
|    these services? 
|     
|    These tradeoffs are discussed for each configuration, below: 
|     
|    1) Site-to-site (CE-to-CE) 
|     
|    Link eavesdropping or tampering - protected on all links 
|    Device compromise - vulnerable to CE compromise 
|    Complexity - single administration, responsible for one device per 
|         site (Nce devices), but overall configuration per VPN scales as 
|         Nce**2.  
|         Though the complexity may be reduced: 1) In practice, as Nce 
|         grows, the number of VPNs falls off from being a full clique; 
|         2) If the CEs run an automated key management protocol, then 
|         they should be able to set up and tear down secured VPNs 
|         without any intervention 
|    Processing load - on each of two CEs, each packet is either 
|         cryptographically processed (2P), though the protection may be 
|         "integrity check only" or "integrity check plus encryption." 
|    Enhanced services - severely limited; typically only Diffserv 
|         markings are visible to the SP, allowing some QoS services 
|     
|    2) Provider edge-to-edge (PE-to-PE) 
|     
|    Link eavesdropping or tampering - vulnerable on CE-PE links; 
|         protected on SP's network links 
|    Device compromise - vulnerable to CE or PE compromise 
|    Complexity - single administration, Npe devices to configure.  
|         (Multiple sites may share a PE device so Npe is typically much 
|         less than Nce.)  Scalability of the overall configuration 
|         depends on the PPVPN type: If the cryptographic protection is 
|         separate per VPN context, it scales as Npe**2 per customer VPN.  
|         If it is per-PE, it scales as Npe**2 for all customer VPNs 
|         combined. 
|    Processing load - on each of two PEs, each packet is 
|         cryptographically processed (2P). Note that this 2P is a 
|         different 2P from case (1), because only PEs are in 
|         consideration here. 
|    Enhanced services - full; SP can apply any enhancements based on 
|         detailed view of traffic 
|     
|    3) Access link (CE-to-PE) 
|     
|    Link eavesdropping or tampering - protected on CE-PE link; 
|         vulnerable on SP's network links 
|    Device compromise - vulnerable to CE or PE compromise 
|    Complexity - two administrations (customer and SP) with device 
|         configuration on each side (Nce + Npe devices to configure) but 
|         because there is no mesh the overall configuration scales as 
|         Nce. 
|    Processing load - on each of two CEs, each packet is 
|         cryptographically processed, plus on each of two PEs, each 
|         packet is cryptographically processed (4P) 
|    Enhanced services - full; SP can apply any enhancements based on 
|         detailed view of traffic 
|     
|    4) Combined Access link and PE-to-PE (essentially hop-by-hop) 
|     
|    Link eavesdropping or tampering  - protected on all links 
|    Device compromise - vulnerable to CE or PE compromise 
|    Complexity - two administrations (customer and SP) with device 
|         configuration on each side (Nce + Npe devices to configure).  
|         Scalability of the overall configuration depends on the PPVPN 
|         type: If the cryptographic processing is separate per VPN 
|         context, it scales as Npe**2 per customer VPN.  If it is per-
|         PE, it scales as Npe**2 for all customer VPNs combined. 
|    Processing load - on each of two CEs, each packet is 
|         cryptographically processed, plus on each of two PEs, each 
|         packet is cryptographically processed twice (6P) 
|    Enhanced services - full; SP can apply any enhancements based on 
|         detailed view of traffic 
|     

There appears to be another dimension to cryptographic methods that
meris separate consideration.  The PE-CE crypto can be only for
signalling, to authenticate the devices and ensure correct behaviour, or
can be for dataplance traffic as well.  The CE-CE or PE-PE crypto is
typically for dataplane traffic.  PE-PE could also be used by routing
protocols that setup MPLS signalling, such as for LDP.  I might be
reading this wrong, but this section appears to gloss over this
distinction?

|    Given the tradeoffs discussed above, a few conclusions can be made: 
|     
|    - Configurations 2 and 3 are subsets of 4 that may be appropriate 
|    alternatives to 4 under certain threat models; the remainder of 
|    these conclusions compare 1 (CE-to-CE) versus 4 (combined access 
|    links and PE-to-PE). 
|     
|    - If protection from link eavesdropping or tampering is all that is 
|    important, then configurations 1 and 4 are equivalent. 
|     
|    - If protection from device compromise is most important and the 
|    threat is to the CE devices, both cases are equivalent; if the 
|    threat is to the PE devices, configuration 1 is better. 
|     
|    - If reducing complexity is most important, and the size of the 
|    network is small, configuration 1 is better.  Otherwise 
|    configuration 4 is better because rather than a mesh of CE devices 
|    it requires a smaller mesh of PE devices.  Also, under some PPVPN 
|    approaches the scaling of 4 is further improved by sharing the same 
|    PE-PE mesh across all VPN contexts. The scaling advantage of 4 may 
|    be increased or decreased in any given situation if the CE devices 
|    are simpler to configure than the PE devices, or vice-versa. 
|      
|    - If the overall processing load is a key factor, then 1 is better, 
|    unless the PEs come with a hardware encryption accelerator and the 
|    CEs do not. 
|     
|    - If the availability of enhanced services support from the SP is 
|    most important, then 4 is best. 
|     
|    As a quick overall conclusion, CE-to-CE protection is better 
|    against device compromise, but this comes at the cost of enhanced 
|    services and at the cost of operational complexity due to the 
|    Order(n**2) scaling of a larger mesh.   
|     
|    This analysis of site-to-site vs. hop-by-hop tradeoffs does not 
|    explicitly include cases of multiple providers cooperating to 
|    provide a PPVPN service, public Internet VPN connectivity, or 
|    remote access VPN service, but many of the tradeoffs will be 
|    similar. 
|     
|    In addition to the simplified models, the following should also be 
|    considered:  
|    - There are reasons, perhaps, to protect a specific P-to-P or PE-
|    to-P. 
|    - There may be reasons to do multiple encryptions over certain 
|    segments. One may be using an encrypted wireless link under our 
|    IPsec VPN to access a SSL-secured web site to download encrypted 
|    email attachments: four layers.) 
|    - It may be that, for example, cryptographic integrity checks are 
|    applied end to end, and confidentiality over a shorter span. 
|    - Different cryptographic protection may be required for control 
|    protocols and data traffic. 
|    - Attention needs to be given to how auxiliary traffic is 
|    protected, e.g., the ICMPv6 packets that flow back during PMTU 
|    discovery, among other examples. 
|     
|    5.3. Access Control Techniques 
|     
|    Access control techniques include packet-by-packet or packet-flow-
|    by-packet-flow access control by means of filters and firewalls, as 
|    well as by means of admitting a "session" for a control, signaling, 
|    or management protocol. Enforcement of access control by isolated 
|    infrastructure addresses is discussed in another section of this 
|    document. 
|     
|    In this document, we distinguish between filtering and firewalls 
|    based primarily on the direction of traffic flow.  We define 
|    filtering as being applicable to unidirectional traffic, while a 
|    firewall can analyze and control both sides of a conversation.   
| 
|    The definition has two significant corollaries: 
|    - Routing or traffic flow symmetry: A firewall typically requires 
|    routing symmetry, which is usually enforced by locating a firewall 
|    where the network topology assures that both sides of a 
|    conversation will pass through the firewall.  A filter can operate 
|    upon traffic flowing in one direction, without considering traffic 
|    in the reverse direction. Beware that this concept could result in 
|    a single point of failure. 
|    - Statefulness: Because it receives both sides of a conversation, a 
|    firewall may be able to interpret a significant amount of 
|    information concerning the state of that conversation and use this 
|    information to control access.  A filter can maintain some limited 
|    state information on a unidirectional flow of packets, but cannot 
|    determine the state of the bi-directional conversation as precisely 
|    as a firewall. 
|     

All of the techniques listed in this section appear to be more for
completeness in this document.  They are general techniques applicable
to protecting any network, and should be considered in that context.

The only specificity for MPLS appears to be two:
    1.  You should probably state that Filtering is applied to IPv4/IPv6
    packets.  These are standard techniques that are applied on the
    CE-PE link, or at the edges, not within the MPLS/GMPLS
    infrastructure.
    2.  Inband access to management interfaces on any MPLS/GMPLS only
    infrastructure implies MPLS tunnel termination on those devices
    within the infrastructure.  By definition, tunnels terminate on the
    PE devices, and hence do not permit such management access to P
    devices.  With that, the injunction to apply filtering/firewalling
    to host bound traffic as you haveit below is good.

|    5.3.1.       Filtering 
|  
|    It is relatively common for routers to filter data packets. That 
|    is, routers can look for particular values in certain fields of the 
|    IP or higher level (e.g., TCP or UDP) headers. Packets which 
|    matching the criteria associated with a particular filter may 
|    either be discarded or given special treatment. Today, not only 
|    routers, most end hosts today have filters and every instance of 
|    IPsec is also a filter [RFC4301]. 
|     
|    In discussing filters, it is useful to separate the Filter 
|    Characteristics that may be used to determine whether a packet 
|    matches a filter from the Packet Actions applied to those packets 
|    which matching a particular filter.  
|     
|    o Filter Characteristics 
|     
|    Filter characteristics or rules are used to determine whether a 
|    particular packet or set of packets matches a particular filter.  
|     
|    In many cases filter characteristics may be stateless. A stateless 
|    filter determines whether a particular packet matches a filter 
|    based solely on the filter definition, normal forwarding 
|    information (such as the next hop for a packet), and the contents 
|    of that individual packet. Typically stateless filters may consider 
|    the incoming and outgoing logical or physical interface, 
|    information in the IP header, and information in higher layer 
|    headers such as the TCP or UDP header. Information in the IP header 
|    to be considered may for example include source and destination IP 
|    addresses, Protocol field, Fragment Offset, and TOS field in IPv4, 
|    Next Header, Extension Headers, Flow label, etc. in IPv6. Filters 
|    also may consider fields in the TCP or UDP header such as the Port 
|    fields, the SYN field in the TCP header, as well as ICMP and ICMPv6 
|    type.  
|     
|    Stateful filtering maintains packet-specific state information, to 
|    aid in determining whether a filter has been met. For example, a 
|    device might apply stateless filters to the first fragment of a 
|    fragmented IP packet. If the filter matches, then the data unit ID 
|    may be remembered and other fragments of the same packet may then 
|    be considered to match the same filter. Stateful filtering is more 
|    commonly done in firewalls, although firewall technology may be 
|    added to routers. Data unit ID can also be Fragmentation Extension 
|    Header in IPv6. 
|     
|    o Actions based on Filter Results 
|     
|    If a packet, or a series of packets, matches a specific filter, 
|    then a variety of actions which may be taken based on that match. 
|    Examples of such actions include: 
|     
|      - Discard 
|     
|    In many cases, filters are set to catch certain undesirable 
|    packets. Examples may include packets with forged or invalid source 
|    addresses, packets that are part of a DOS or Distributed DoS (DDOS) 
|    attack, or packets which are trying to access unallowed resources 
|    (such as network management packets from an unauthorized source). 
|    Where such filters are activated, it is common to discard the 
|    packet or set of packets matching the filter silently. The 
|    discarded packets may of course also be counted or logged.  
|     
|      - Set CoS 
|     
|    A filter may be used to set the Class of Service associated with 
|    the packet.  
|     
|      - Count packets or bytes 
|     
|      - Rate Limit 
|     
|    In some cases the set of packets matching a particular filter may 
|    be limited to a specified bandwidth. In this case, packets or bytes 
|    would be counted, and would be forwarded normally up to the 
|    specified limit. Excess packets may be discarded or may be marked 
|    (for example by setting a "discard eligible" bit in the IP ToS 
|    field or the MPLS EXP field).  
|     
|      - Forward and Copy 
|     
|    It is useful in some cases to forward some set of packets normally, 
|    but also to send a copy to a specified other address or interface. 
|    For example, this may be used to implement a lawful intercept 
|    capability or to feed selected packets to an Intrusion Detection 
|    System.  
|     
|    o Other Issues related to Use of Packet Filters 
|     
|    Filtering performance may vary widely according to implementation 
|    and the types and number of rules. Without acceptable performance, 
|    filtering is not useful.  
|         
|    The precise definition of "acceptable" may vary from SP to SP, and 
|    may depend upon the intended use of the filters. For example, for 
|    some uses a filter may be turned on all the time to set CoS, to 
|    prevent an attack, or to mitigate the effect of a possible future 
|    attack. In this case it is likely that the SP will want the filter 
|    to have minimal or no impact on performance. In other cases, a 
|    filter may be turned on only in response to a major attack (such as 
|    a major DDoS attack). In this case a greater performance impact may 
|    be acceptable to some service providers.  
|     
|    A key consideration with the use of packet filters is that they can 
|    provide few options for filtering packets carrying encrypted data.  
|    Because the data itself is not accessible, only packet header 
|    information or other unencrypted fields can be used for filtering. 
|     
|    5.3.2.       Firewalls 
|     
|    Firewalls provide a mechanism for control over traffic passing 
|    between different trusted zones in the MPLS/GMPLS model, or between 
|    a trusted zone and an untrusted zone.  Firewalls typically provide 
|    much more functionality than filters, because they may be able to 
|    apply detailed analysis and logical functions to flows, and not 
|    just to individual packets.  They may offer a variety of complex 
|    services, such as threshold-driven denial-of-service attack 
|    protection, virus scanning, acting as a TCP connection proxy, etc. 
|     
|    As with other access control techniques, the value of firewalls 
|    depends on a clear understanding of the topologies of the 
|    MPLS/GMPLS core network, the user networks, and the threat model.  
|    Their effectiveness depends on a topology with a clearly defined 
|    inside (secure) and outside (not secure). 
|     
|    Firewalls may be applied to help protect MPLS/GMPLS core network 
|    functions from attacks originating from the Internet or from 
|    MPLS/GMPLS user sites, but typically other defensive techniques 
|    will be used for this purpose. 
|     
|    Where firewalls are employed as a service to protect user VPN sites 
|    from the Internet, different VPN users, and even different sites of 
|    a single VPN user, may have varying firewall requirements.  The 
|    overall PPVPN logical and physical topology, along with the 
|    capabilities of the devices implementing the firewall services, has 
|    a significant effect on the feasibility and manageability of such 
|    varied firewall service offerings. 
|     
|    Another consideration with the use of firewalls is that they can 
|    provide few options for handling packets carrying encrypted data.  
|    Because the data itself is not accessible, only packet header 
|    information, other unencrypted fields, or analysis of the flow of 
|    encrypted packets can be used for making decisions on accepting or 
|    rejecting encrypted traffic. 
|     
|    Two approaches are to move the firewall outside of the encrypted 
|    part of the path or to register and pre-approve the encrypted 
|    session with the firewall.  
|     
|    Handling DoS attacks has become increasingly important. Useful 
|    guidelines include the following: 
|    1. Perform ingress filtering everywhere. Upstream prevention is 
|    better. 
|    2. Be able to filter DoS attack packets at line speed. 
|    3. Do not allow oneself to amplify attacks. 
|    4. Continue processing legitimate traffic. Over provide for heavy 
|    loads. Use diverse locations, technologies, etc. 
|     
|    5.3.3.       Access Control to management interfaces 
|     
|    Most of the security issues related to management interfaces can be 
|    addressed through the use of authentication techniques as described 
|    in the section on authentication.  However, additional security may 
|    be provided by controlling access to management interfaces in other 
|    ways. 
|     
|    The Optical Internetworking Forum has done good work on protecting 
|    such interfaces with TLS, SSH, Kerberos, IPsec, WSS, etc. See OIF-
|    SMI-01.0 "Security for Management Interfaces to Network Elements" 
|    [OIF-SMI-01.0], and "Addendum to the Security for Management 
|    Interfaces to Network Elements" [OIF-SMI-02.1]. See also the work 
|    in the ISMS WG. 
|     
|    Management interfaces, especially console ports on MPLS/GMPLS 
|    devices, may be configured so they are only accessible out-of-band, 
|    through a system which is physically or logically separated from 
|    the rest of the MPLS/GMPLS infrastructure. 
|     
|    Where management interfaces are accessible in-band within the 
|    MPLS/GMPLS domain, filtering or firewalling techniques can be used 
|    to restrict unauthorized in-band traffic from having access to 
|    management interfaces.  Depending on device capabilities, these 
|    filtering or firewalling techniques can be configured either on 
|    other devices through which the traffic might pass, or on the 
|    individual MPLS/GMPLS devices themselves. 
|     
|    5.4. Use of Isolated Infrastructure 
|  
|    One way to protect the infrastructure used for support of 
|    MPLS/GMPLS is to separate the resources for support of MPLS/GMPLS 
|    services from the resources used for other purposes (such as 
|    support of Internet services). In some cases this may use 
|    physically separate equipment for VPN services, or even a 
|    physically separate network.  
|     
|    For example, PE-based L3 VPNs may be run on a separate backbone not 
|    connected to the Internet, or may make use of separate edge routers 
|    from those used to support Internet service. Private IP addresses 
|    (local to the provider and non-routable over the Internet) are 
|    sometimes used to provide additional separation. 
|     
|     
|    5.5. Use of Aggregated Infrastructure 
|     
|    In general, it is not feasible to use a completely separate set of 
|    resources for support of each service. In fact, one of the main 
|    reasons for MPLS/GMPLS enabled services is to allow sharing of 
|    resources between multiple users, including multiple VPNs, etc. 
|    Thus, even if certain services make use of a separate network from 
|    Internet services, nonetheless there will still be multiple 
|    MPLS/GMPLS users sharing the same network resources. In some cases 
|    MPLS/GMPLS services will share the use of network resources with 
|    Internet services or other services.  
|     
|    It is therefore important for MPLS/GMPLS services to provide 
|    protection between resources used by different parties. Thus a 
|    well-behaved MPLS/GMPLS user should be protected from possible 
|    misbehavior by other users. This requires that limits are placed on 
|    the amount of resources used by any one VPN. For example, both 
|    control traffic and user data traffic may be rate limited. In some 
|    cases or in some parts of the network where a sufficiently large 
|    number of queues are available, each VPN (and optionally each VPN 
|    and CoS within the VPN) may make use of a separate queue. Control-
|    plane resources such as link bandwidth as well as CPU and memory 
|    resources may be reserved on a per-VPN basis.  
|     
|    The techniques used to provide resource protection between multiple 
|    users served by the same infrastructure can also be used to protect 
|    MPLS/GMPLS networks and services from Internet services.  
|     
|    In general, the use of aggregated infrastructure allows the service 
|    provider to benefit from stochastic multiplexing of multiple bursty 
|    flows, and also may in some cases thwart traffic pattern analysis 
|    by combining the data from multiple users.  
|     
|    5.6. Service Provider Quality Control Processes 
|     
|    Deployment of provider-provisioned VPN services in general requires 
|    a relatively large amount of configuration by the SP. For example, 
|    the SP needs to configure which VPN each site belongs to, as well 
|    as QoS and SLA guarantees. This large amount of required 
|    configuration leads to the possibility of misconfiguration.  
|     
|    It is important for the SP to have operational processes in place 
|    to reduce the potential impact of misconfiguration. CE-to-CE 
|    authentication may also be used to detect misconfiguration when it 
|    occurs.  
|     
|    5.7. Deployment of Testable MPLS/GMPLS Service.   
|     
|    This refers to solutions that can be readily tested to make sure 
|    they are configured correctly.  For example, for a point-point 
|    connection, checking that the intended connectivity is working 
|    pretty much ensures that there is not connectivity to some 
|    unintended site. 
|     
|  
| 6. Monitoring, Detection, and Reporting of Security Attacks 
|     
|    MPLS/GMPLS network and service may be subject to attacks from a 
|    variety of security threats.  Many threats are described in another 
|    part of this document.  Many of the defensive techniques described 
|    in this document and elsewhere provide significant levels of 
|    protection from a variety of threats.  However, in addition to 
|    silently employing defensive techniques to protect against attacks, 
|    MPLS/GMPLS services can also add value for both providers and 
|    customers by implementing security monitoring systems to detect and 
|    report on any security attacks which occur, regardless of whether 
|    the attacks are effective. 
|     
|    Attackers often begin by probing and analyzing defenses, so systems 
|    that can detect and properly report these early stages of attacks 
|    can provide significant benefits. 
|     
|    Information concerning attack incidents, especially if available 
|    quickly, can be useful in defending against further attacks.  It 
|    can be used to help identify attackers or their specific targets at 
|    an early stage.  This knowledge about attackers and targets can be 
|    used to strengthen defenses against specific attacks or attackers, 
|    or improve the defensive services for specific targets on an as-
|    needed basis.  Information collected on attacks may also be useful 
|    in identifying and developing defenses against novel attack types. 
|     
|    Monitoring systems used to detect security attacks in MPLS/GMPLS 
|    typically operate by collecting information from the Provider Edge 
|    (PE), Customer Edge (CE), and/or Provider backbone (P) devices.  
|    Security monitoring systems should have the ability to actively 
|    retrieve information from devices (e.g., SNMP get) or to passively 
|    receive reports from devices (e.g., SNMP notifications).  The 
|    specific information exchanged depends on the capabilities of the 
|    devices and on the type of VPN technology.  Particular care should 
|    be given to securing the communications channel between the 
|    monitoring systems and the MPLS/GMPLS devices. Syslog WG is 
|    specifying "Logging Capabilities for IP Network Infrastructure". 
|    (The specific references will be made only if the draft(s) became 
|    RFC before this draft.) 

It used to be that you could refer to drafts as "Work in Progress".  Is
that not allowed any longer?

|    The CE, PE, and P devices should employ efficient methods to 
|    acquire and communicate the information needed by the security 
|    monitoring systems.  It is important that the communication method 
|    between MPLS/GMPLS devices and security monitoring systems be 
|    designed so that it will not disrupt network operations.  As an 
|    example, multiple attack events may be reported through a single 
|    message, rather than allowing each attack event to trigger a 
|    separate message, which might result in a flood of messages, 
|    essentially becoming a denial-of-service attack against the 
|    monitoring system or the network. 
|     
|    The mechanisms for reporting security attacks should be flexible 
|    enough to meet the needs of MPLS/GMPLS service providers, 
|    MPLS/GMPLS customers, and regulatory agencies, if applicable.  The 
|    specific reports should depend on the capabilities of the devices, 
|    the security monitoring system, the type of VPN, and the service 
|    level agreements between the provider and customer. 
| 
| 7. Service Provider General Security Requirements 
|     
|    This section covers security requirements the provider may have for 
|    securing its MPLS/GMPLS network infrastructure including LDP and 
|    RSVP-TE specific requirements. 
|     
|    The MPLS/GMPLS service provider's requirements defined here are for 
|    the MPLS/GMPLS core in the reference model.  The core network can 
|    be implemented with different types of network technologies, and 
|    each core network may use different technologies to provide the 
|    various services to users with different levels of offered 
|    security. Therefore, a MPLS/GMPLS service provider may fulfill any 
|    number of the security requirements listed in this section. This 
|    document does not state that a MPLS/GMPLS network must fulfill all 
|    of these requirements to be secure.   
|     
|    These requirements are focused on: 1) how to protect the MPLS/GMPLS 
|    core from various attacks outside the core including network users, 
|    both accidentally and maliciously, 2) how to protect the end users. 
|      
|    7.1. Protection within the Core Network 
|     
|    7.1.1.       Control Plane Protection - General 
|     
|    - Protocol authentication within the core:  
|     
|    The network infrastructure must support mechanisms for 
|    authentication of the control plane. If MPLS/GMPLS core is used, 
|    LDP sessions may be authenticated by use TCP MD5, in addition, IGP 
|    and BGP authentication should also be considered. For a core 
|    providing Layer 2 services, PE-to-PE authentication may also be 
|    performed via IPsec. See the above discussion of protocol security 
|    services: authentication, integrity (with replay detection), 
|    confidentiality. Protocols need to provide a complete set of 
|    security services from which the SP can choose. Also, the hard part 
|    is key management. 
|     
|    With the cost of authentication coming down rapidly, the 
|    application of control plane authentication may not increase the 
|    cost of implementation for providers significantly, and will help 
|    to improve the security of the core. If the core is dedicated to 
|    MPLS/GMPLS enabled services and without any interconnects to third 
|    parties then this may reduce the requirement for authentication of 
|    the core control plane. 
|     
|  
|    - Infrastructure Hiding 
|     
|    Here we discuss means to hide the provider's infrastructure nodes.  
|     
|    A MPLS/GMPLS provider may make its infrastructure routers (P and PE 
|    routers) unreachable from outside users and unauthorized internal 
|    users. For example, separate address space may be used for the 
|    infrastructure loopbacks.  
|     
|    Normal TTL propagation may be altered to make the backbone look 
|    like one hop from the outside, but caution needs to be taken for 
|    loop prevention. This prevents the backbone addresses from being 
|    exposed through trace route; however this must also be assessed 
|    against operational requirements for end-to-end fault tracing.  
|     
|    An Internet backbone core may be re-engineered to make Internet 
|    routing an edge function, for example, by using MPLS label 
|    switching for all traffic within the core and possibly make the 
|    Internet a VPN within the PPVPN core itself. This helps to detach 
|    Internet access from PPVPN services. 
|     
|    Separating control plane, data plane, and management plane 
|    functionality in hardware and software may be implemented on the PE 
|    devices to improve security. This may help to limit the problems 
|    when attacked in one particular area, and may allow each plane to 
|    implement additional security measures separately. 
|     
|    PEs are often more vulnerable to attack than P routers, because PEs 
|    cannot be made unreachable from outside users by their very nature. 
|    Access to core trunk resources can be controlled on a per user 
|    basis by using of inbound rate-limiting or traffic shaping; this 
|    can be further enhanced on a per Class of Service basis (see 
|    Section 8.2.3)  
|  
|    In the PE, using separate routing processes for different services, 
|    for example, Internet and PPVPN service, may help to improve the 
|    PPVPN security and better protect VPN customers. Furthermore, if 
|    resources, such as CPU and Memory, can be further separated based 
|    on applications, or even individual VPNs, it may help to provide 
|    improved security and reliability to individual VPN customers. 
|     
|    7.1.2.       Control plane protection with RSVP-TE 
|     
|    - RSVP Security Tools 
|     
|    Isolation of the trusted domain is an important security mechanism 
|    for RSVP, to ensure that an untrusted element cannot access a 
|    router of the trusted domain.  However, isolation is limited by the 
|    need to allow ASBR-ASBR communication for inter-AS LSPs.  Isolation 
|    mechanisms might also be bypassed by Router Alert IP packets. A 
|    solution could consists of disabling the RSVP router alert mode and 
|    dropping all IP packets with the router alert option, or also to 
|    drop all incoming IP packets on an interface with port 46, which 
|    requires an access-list at the IP port level) or spoofed IP packets 
|    if anti-spoofing is not otherwise activated. 
|     
|    RSVP security can be strengthened by deactivating RSVP on 
|    interfaces with neighbors who are not authorized to use RSVP, to 
|    protect against adjacent CE-PE attacks. However, this does not 
|    really protect against DoS attacks or attacks on non-adjacent 
|    routers.  It has been demonstrated that substantial CPU resources 
|    are consumed simply by processing received RSVP packets, even if 
|    the RSVP process is deactivated for the specific interface on which 
|    the RSVP packets are received.  

This does not follow.  Is the implication of the above that the very act
of bringing an RSVP packet from the interface, through the dataplane to
the control plane and then dropping the RSVP packet at the control plane
because RSVP is disabled on the interface, is it this very act itself
CPU intensive?

|    RSVP neighbor filtering at the protocol level, to restrict the set 
|    of neighbors that can send RSVP messages to a given router, 
|    protects against non-adjacent attacks.  However, this does not 
|    protect against DoS attacks and does not effectively protect 
|    against spoofing of the source address of RSVP packets, if the 
|    filter relies on the neighbor's address within the RSVP message.   
|     
|    RSVP neighbor filtering at the data plane level (with an access 
|    list to accept IP packets with port 46, only for specific 
|    neighbors). 

The above sentence is unfinished.

|                This requires Router Alert mode to be deactivated and 
|    does not protect against spoofing. 
|     
|    - Authentication for RSVP messages 
|     
|    One of the most powerful tools for protection against RSVP-based 
|    attacks is the use of authentication for RSVP messages, based on a 
|    secure message hash using a key shared by RSVP neighbors.  This 
|    protects against LSP creation attacks, at the expense of consuming 
|    significant CPU resources for digest computation.  In addition, if 
|    the neighboring RSVP speaker is compromised, it could be used to 
|    launch attacks using authenticated RSVP messages. These methods, 
|    and certain other aspects of RSVP security, are explained in detail 
|    in RFC 4230 [RFC4230]. Key management must be implemented. Logging 
|    and auditing as well as multiple layers of crypto protection can 
|    help here. IPsec can also be used. 
|     
|    Another valuable tool is RSVP message pacing, to limit the number 
|    of RSVP messages sent to a given neighbor during a given period.  
|    This allows blocking DoS attack propagation. 
|     
|    The trick with DoS is to let the good packet through and keep 
|    operating. Rate limiting by itself needs to be selective do this. 
|     
|    - limit the impact of an attack on control plane resources 
|  
|    To ensure continued effective operation of the MPLS router even in 
|    the case of an attack that bypasses packet filtering mechanisms 
|    such as Access Control Lists in the data plane, it is important 
|    that routers have some mechanisms to limit the impact of the 
|    attack.  There should be a mechanism to rate limit the amount of 
|    control plane traffic addressed to the router, per interface.  This 
|    should be configurable on a per-protocol basis, (and, ideally, on a 
|    per-sender basis) to avoid letting an attacked protocol or a given 
|    sender blocking all communications.  This requires the ability to 
|    filter and limit the rate of incoming messages of particular 
|    protocols, such as RSVP (filtering at the IP protocol level), and 
|    particular senders.  In addition, there should be a mechanism to 
|    limit CPU and memory capacity allocated to RSVP, so as to protect 
|    other control plane elements.  To limit the memory allocation, it 
|    will probably be necessary to limit the number of LSPs that can be 
|    set up. 
|     
|  
|    7.1.3.       Control plane protection with LDP 
|  
|    The approaches to protect MPLS routers against LDP-based attacks 
|    are similar to those for RSVP, including isolation, protocol 
|    deactivation on specific interfaces, filtering of LDP neighbors at 
|    the protocol level, filtering of LDP neighbors at the data plane 
|    level (access list that filter the TCP & UDP LDP ports), 
|    authentication with message digest, rate limiting of LDP messages 
|    per protocol per sender and limiting all resources allocated to 
|    LDP-related tasks. 
|     
|        
|    7.1.4.       Data Plane Protection 
|     
|    IPsec can provide authentication, integrity, confidentiality, and 
|    replay detection for provider or user data. It also has an 
|    associated key management protocol. 
|     
|    In today's MPLS/GMPLS, ATM, or Frame Relay networks, encryption is 
|    not provided as a basic feature. Mechanisms described in section 5 
|    can be used to secure the MPLS data plane traffic carried over MPLS 
|    core. Both the Frame Relay Forum and the ATM Forum standardized 
|    cryptographic security services in the late 1990s, but these 
|    standards are not widely implemented. 
|     
|    7.2. Protection on the User Access Link 
|    Peer or neighbor protocol authentication may be used to enhance 
|    security. For example, BGP MD5 authentication may be used to 
|    enhance security on PE-CE links using eBGP. In the case of Inter-
|    provider connection, cryptographic protection mechanisms between 
|    ASes, such as IPsec, may be used. 
|     
|    If multiple services are provided on the same PE platform, 
|    different WAN link layer address spaces may be used for different 
|    services (e.g., VPN and non-VPN) to enhance isolation. 
|     
|    Firewall and Filtering: access control mechanisms can be used to 
|    filter any packets destined for the service provider's 
|    infrastructure prefix or eliminate routes identified as 
|    illegitimate. 
|     
|    Rate limiting may be applied to the user interface/logical 
|    interfaces against DDoS bandwidth attack. This is helpful when the 
|    PE device is supporting both multi-services, especially VPN and 
|    Internet Services, on the same physical interfaces through 
|    different logical interfaces. 
|  
|    7.2.1.       Link Authentication 
|     
|    Authentication can be used to validate site access to the network 
|    via fixed or logical connections, e.g. L2TP, IPsec, respectively. 
|    If the user wishes to hold the authentication credentials for 
|    access, then provider solutions require the flexibility for either 
|    direct authentication by the PE itself or interaction with a 
|    customer authentication server. Mechanisms are required in the 
|    latter case to ensure that the interaction between the PE and the 
|    customer authentication server is appropriately secured. 
|      
|    7.2.2.       Access Routing Control 
|     
|    Routing protocol level e.g., RIP, OSPF, or BGP, may be used to 
|    provide control access between a CE and PE. Per neighbor and per 
|    VPN routing policies may be established to enhance security and 
|    reduce the impact of a malicious or non-malicious attack on the PE; 
|    the following mechanisms, in particular, should be considered: 
|     - Limiting the number of prefixes that may be advertised on 
|        a per access basis into the PE. Appropriate action may be 
|        taken should a limit be exceeded, e.g., the PE shutting 
|        down the peer session to the CE  
|     - Applying route dampening at the PE on received routing 
|        updates 
|     - Definition of a per VPN prefix limit after which 
|        additional prefixes will not be added to the VPN routing 
|        table. 
|     
|    In the case of Inter-provider connection, access protection, link 
|    authentication, and routing policies as described above may be 
|    applied. Both inbound and outbound firewall or filtering mechanism 
|    between ASes may be applied. Proper security procedures must be 
|    implemented in Inter-provider interconnection to protect the 
|    providers' network infrastructure and their customers. This may be 
|    custom designed for each Inter-Provider peering connection, and 
|    must be agreed upon by both providers. 

Why are you discussing Inter-provider connection here?

|  
|    7.2.3.       Access QoS 
|     
|    MPLS/GMPLS providers offering QoS-enabled services require 
|    mechanisms to ensure that individual accesses are validated against 
|    their subscribed QOS profile and as such gain access to core 
|    resources that match their service profile.  Mechanisms such as per 
|    Class of Service rate limiting or traffic shaping on ingress to the 
|    MPLS/GMPLS core are one option for providing this level of control.  
|    Such mechanisms may require the per Class of Service profile to be 
|    enforced either by marking, or remarking or discard of traffic 
|    outside of the profile. 
|     
|    7.2.4.       Customer service monitoring tools  
|     
|    End users requiring specific statistics on the core, e.g., routing 
|    table, interface status, or QoS statistics, requirements for 
|    mechanisms at the PE both to validate the incoming user and limit 
|    the views available to that particular user.  Mechanisms should 
|    also be considered to ensure that such access cannot be used a 
|    means of a DoS attack (either malicious or accidental) on the PE 
|    itself. This could be accomplished through either separation of 
|    these resources within the PE itself or via the capability to rate-
|    limit on a per physical or logical connection basis such traffic. 
|  
|     
|    7.3. General User Requirements for MPLS/GMPLS Providers 
|     
|    MPLS/GMPLS providers must support end users' security requirements. 
|    Depending on the technologies used, these requirements may include: 
|  
|    - User control plane separation - routing isolation when 
|       applicable, for example, in the case of MPLS VPNs. 

What does this mean?

|    - Protection against intrusion, DoS attacks and spoofing 

Other than attempts to not amplify DoS attacks, most of this draft has
not focused on user considerations for DoS.  So what would you suggest 
are some criteria for protection?

|    - Access Authentication 
|    - Techniques highlighted through this document that identify 
|       methodologies for the protection of resources and the 
|       MPLS/GMPLS infrastructure.  

Also, if e2e crypto is a user's desire, PPVPN configured CE-CE
encryption.

|    Hardware or software errors in equipment leading to breaches in 
|    security are not within the scope of this document. 
|  
|  
| 8. Inter-provider Security Requirements 
|  
|    This section discusses security capabilities that are important at 
|    the MPLS/GMPLS Inter-provider connections and at devices (including 
|    ASBR routers) supporting these connections. The security 
|    capabilities stated in this section should be considered as 
|    complementary to security considerations addressed in individual 
|    protocol specifications or security frameworks. 
|     
|    Security vulnerabilities and exposures may be propagated across 
|    multiple networks because of security vulnerabilities arising in 
|    one peer's network. Threats to security originate from accidental, 
|    administrative, and intentional sources. Intentional threats 
|    include events such as spoofing and Denial of Service (DoS) 
|    attacks. 
|    The level and nature of threats, as well as security and 
|    availability requirements, may vary over time and from network to 
|    network. This section therefore discusses capabilities that need to 
|    be available in equipment deployed for support of the MPLS 
|    InterCarrier Interconnect (MPLS-ICI). Whether any particular 
|    capability is used in any one specific instance of the ICI is up to 
|    the service providers managing the PE equipment offering/using the 
|    ICI services.  
|     
|    8.1. Control Plane Protection 
|     
|    This section discusses capabilities for control plane protection, 
|    including protection of routing, signaling, and OAM capabilities.   
|  
|    8.1.1.       Authentication of Signaling Sessions 
|  
|    Authentication is needed for signaling sessions (i.e., BGP, LDP and 
|    RSVP-TE) and routing sessions (e.g., BGP) as well as OAM sessions 
|    across domain boundaries. Equipment must be able to support 
|    exchange of all protocol messages over a single IPsec tunnel, with 
|    NULL encryption and authentication, between the peering ASBRs. 
|    Support for TCP MD5 authentication for LDP and BGP and for RSVP-TE 
|    authentication must also be provided. Manual keying of IPsec should 
|    not be used. IKEv2 with pre-shared secrets or public key methods 
|    should be used. Replay detection should be used. 
|  
|    Mechanisms to authenticate and validate a dynamic setup request 
|    MUST be available. For instance, if dynamic signaling of a TE-LSP 
|    or PW is crossing a domain boundary, there must be a way to detect 
|    whether the LSP source is who it claims to be and that he is 
|    allowed to connect to the destination. 
|     
|    MD5 authentication support for all TCP-based protocols within the 
|    scope of the MPLS-ICI (i.e., LDP signaling and BGP routing) and MD5 
|    authentication for the RSVP-TE Integrity Object MUST be provided to 
|    interoperate with current practices. 
|    Equipment SHOULD be able to support exchange of all signaling and 
|    routing (LDP, RSVP-TE, and BGP) protocol messages over a single 
|    IPSec security association pair in tunnel or transport mode with 
|    authentication but with NULL encryption, between the peering ASBRs. 
|    IPSec, if supported, must be supported with HMAC-MD5 and optionally 
|    SHA-1.  It is expected that authentication algorithms will evolve 
|    over time and support can be updated as needed. 
|     
|    OAM Operations across the MPLS-ICI could also be the source of 
|    security threats on the provider infrastructure as well as the 
|    service offered over the MPLS-ICI. A large volume of OAM messages 
|    could overwhelm the processing capabilities of an ASBR if the ASBR 
|    is not properly protected. Maliciously generated OAM messages could 
|    also be used to bring down an otherwise healthy service (e.g., MPLS 
|    Pseudo Wire), and therefore affect service security. MPLS-ping does 
|    not support authentication today, and that support should be 
|    subject for future considerations. Bidirectional Forwarding 
|    Detection (BFD), however, does have support for carrying an 
|    authentication object. It also supports Time-To-Live (TTL) 
|    processing as an anti-replay measure. Implementations conformant 
|    with this MPLS-ICI should support BFD authentication using MD5 and 
|    must support the procedures for TTL processing.  
|     
|    8.1.2.       Protection against DoS attacks in the Control 
|    Plane 
|  
|    Implementation must have the ability to prevent signaling and 
|    routing DoS attacks on the control plane per interface and 
|    provider. Such prevention may be provided by rate-limiting 
|    signaling and routing messages that can be sent by a peer provider 
|    according to a traffic profile and by guarding against malformed 
|    packets. 
|     
|    Equipment MUST provide the ability to filter signaling, routing, 
|    and OAM packets destined for the device, and MUST provide the 
|    ability to rate limit such packets. Packet filters SHOULD be 
|    capable of being separately applied per interface, and SHOULD have 
|    minimal or no performance impact. For example, this allows an 
|    operator to filter or rate-limit signaling, routing, and OAM 
|    messages that can be sent by a peer provider and limit such traffic 
|    to a given profile.  
|      
|    During a control plane DoS attack against an ASBR, the router 
|    SHOULD guarantee sufficient resources to allow network operators to 
|    execute network management commands to take corrective action, such 
|    as turning on additional filters or disconnecting an interface 
|    under attack. DoS attacks on the control plane SHOULD NOT adversely 
|    affect data plane performance.  
|    Equipment running BGP MUST support the ability to limit the number 
|    of BGP routes received from any particular peer. Furthermore, in 
|    the case of IPVPN, a router MUST be able to limit the number of 
|    routes learned from a BGP peer per IPVPN. In the case that a device 
|    has multiple BGP peers, it SHOULD be possible for the limit to vary 
|    between peers.  
|     
|    8.1.3.       Protection against Malformed Packets 
|  
|    Equipment SHOULD be robust in the presence of malformed protocol 
|    packets. For example, malformed routing, signaling, and OAM packets 
|    should be treated in accordance to the relevant protocol 
|    specification.  
|     
|    8.1.4.       Ability to Enable/Disable Specific Protocols 
|  
|    Ability to drop any signaling or routing protocol messages when 
|    these messages are to be processed by the ASBR but the 
|    corresponding protocol is not enabled on that interface.  
|     
|    Equipment must allow an administrator to enable or disable a 
|    protocol (default protocol is disabled unless administratively 
|    enable) on an interface basis. 
|     
|    Equipment MUST be able to drop any signaling or routing protocol 
|    messages when these messages are to be processed by the ASBR but 
|    the corresponding protocol is not enabled on that interface. This 
|    dropping SHOULD NOT adversely affect data plane or control plane 
|    performance.  
|     
|    8.1.5.       Protection Against Incorrect Cross Connection 
|  
|    The capability of detecting and locating faults in a LSP cross-
|    connect MUST be provided. Such faults may cause security violations 
|    as they result in directing traffic to the wrong destinations. This 
|    capability may rely on OAM functions. Equipment MUST support MPLS 
|    LSP ping [RFC4379]. This MAY be used to verify end to end 
|    connectivity for the LSP (e.g., PW, TE Tunnel, VPN LSP, etc.), and 
|    to verify PE-to-PE connectivity for L3 VPN services.  
|     
|    When routing information is advertised from one domain to the 
|    other, operators must be able to guard against situations that 
|    result in traffic hijacking, black-holing, resource stealing (e.g., 
|    number of routes), etc. For instance, in the IPVPN case, an 
|    operator must be able to block routes based on associated route 
|    target attributes. In addition, mechanisms must exist to verify 
|    whether a route advertised by a peer for a given VPN is actually a 
|    valid route and whether the VPN has a site attached or reachable 
|    through that domain. 
|  
|    Equipment (ASBRs and Route Reflectors (RRs)) supporting operation 
|    of BGP MUST be able to restrict which Route Target attributes are 
|    sent to and accepted from a BGP peer across an ICI. Equipment 
|    (ASBRs, RRs) SHOULD also be able to inform the peer regarding which 
|    Route Target attributes it will accept from a peer, because sending 
|    an incorrect Route Target can result in incorrect cross-connection 
|    of VPNs. Also, sending inappropriate route targets to a peer may 
|    disclose confidential information.  
|     
|    8.1.6.       Protection Against Spoofed Updates and Route 
|    Advertisements 
|  
|    Equipment MUST support route filtering of routes received via a BGP 
|    peer sessions by applying policies that include one or more the 
|    following: AS path, BGP next hop, standard community or extended 
|    community. 
|     
|    8.1.7.       Protection of Confidential Information 
|  
|    Ability to identify and prohibit messages that can reveal 
|    confidential information about network operation (e.g., performance 
|    OAM messages or MPLS-ping messages) is required. Service Providers 
|    must have the flexibility of handling these messages at the ASBR.  
|     
|    Equipment SHOULD provide the ability to identify and restrict where 
|    it sends messages or that can reveal confidential information about 
|    network operation (e.g., performance OAM messages, LSP Traceroute 
|    messages). Service Providers must have the flexibility of handling 
|    these messages at the ASBR. For example, equipment supporting LSP 
|    Traceroute MAY limit to which addresses replies can be sent.  
|    Note: This capability should be used with care. For example, if a 
|    service provider chooses to prohibit the exchange of LSP ping 
|    messages at the ICI, it may make it more difficult to debug 
|    incorrect cross-connection of LSPs or other problems.  
|    A provider may decide to progress these messages if they are 
|    incoming from a trusted provider and are targeted to specific 
|    agreed-on addresses. Another provider may decide to traffic police, 
|    reject, or apply policies to these messages. Solutions must enable 
|    providers to control the information that is relayed to another 
|    provider about the path that a LSP takes. For example, in RSVP-TE 
|    record route object or MPLS-ping trace, a provider must be able to 
|    control the information contained in corresponding messages when 
|    sent to another provider. 
|     
|    8.1.8.       Protection Against over-provisioned number of 
|    RSVP-TE LSPs and bandwidth reservation 
|     
|    In addition to the control plane protection mechanisms listed in 
|    the previous section on Control plane protection with RSVP-TE, the 
|    ASBR must be able both to limit the number of LSPs that can be set 
|    up by other domains and to limit the amount of bandwidth that can 
|    be reserved. A provider's ASBR may deny a LSP set up request or a 
|    bandwidth reservation request sent by another provider's whose the 
|    limits have been reached. 
|     
|    8.2. Data Plane Protection 
|     
|    8.2.1.       Protection against DoS in the Data Plane 
|     This is described earlier in this document. 
|  
|    8.2.2.       Protection against Label Spoofing 
|  
|    Verification that a label received across an interconnect was 
|    actually assigned to the provider across the interconnect. If the 
|    label was not assigned to the provider, the packet MUST be dropped. 
|     
|    Equipment MUST be able to verify that a label received across an 
|    interconnect was actually assigned to a LSP arriving from the 
|    provider across that interconnect. If the label was not assigned to 
|    a LSP which arrives at this router from the correct neighboring 
|    provider, the packet MUST be dropped.  This verification can be 
|    applied to the top label only. The top label is the received top 
|    label and every label that is exposed by label popping to be used 
|    for forwarding decisions.  

should nominally check the label stack depth.  By this I mean, if a
spoofed packet arrives with a valid label, but only a 1-label stack, nd
we exect at least 2 or more labels, we should drop.

|    Equipment MUST provide the capability of dropping MPLS-labeled 
|    packets if all labels in the stack are not processed.  This lets 
|    carriers guarantee that every label that enters its domain from 
|    another carrier was actually assigned to that carrier.  
|  
|    The following requirements are not directly reflected in this 
|    document but must be used as guidance for addressing further work. 
|     
|    Solutions MUST NOT force operators to reveal reachability 
|    information to routers within their domains. <note: It is believed 
|    that this requirement is met via other requirements specified in 
|    this section plus the normal operation of IP routing, which does 
|    not reveal individual hosts.> 
|     
|    Mechanisms to authenticate and validate a dynamic setup request 
|    MUST be available. For instance, if dynamic signaling of a TE-LSP 
|    or PW is crossing a domain boundary, there must be a way to detect 
|    whether the LSP source is who it claims to be and that he is 
|    allowed to connect to the destination. 
|     
|    8.2.3.       Protection using ingress traffic policing and 
|    enforcement 
|     
|    The following simple diagram illustrates a potential security issue 
|    on the data plane issue across a MPLS interconnect: 
|     
|    SP2 - ASBR2 - labeled path - ASBR1 - P1 - SP1's PSN - P2 - PE1 
|    |         |                   |                          | 
|    |<  AS2  >|<MPLS interconnect>|<             AS1              >| 
|     
|    Traffic flow direction is from SP2 to SP1 
|     
|    Usually, the transit label used by ASBR2 is allocated by ASBR1,  
|    which in turn advertises it to ASB2 (downstream unsolicited or on-
|    demand), and this label is used for a service context (VPN label, 
|    PW VC label, etc.), and this LSP is normally terminated at a 
|    forwarding table belonging to the service instance on PE (PE1) in 
|    SP1. 
|     
|    In the example above, ASBR1 would not know whether the label of an 
|    incoming packet from ASBR2 over the interconnect is a VPN label or 
|    PSN label for AS1. So it is possible (though rare) that ASBR2 can 
|    be accidentally or intentionally configured such that the incoming 
|    label could match a PSN label (e.g., LDP) in AS1. Then, this LSP 
|    would end up on the global plane of an infrastructure router (P or 
|    PE1), and this could invite a unidirectional attack on that P or 
|    PE1 where the LSP terminates. 
|  
|    To mitigate this threat, implementations SHOULD be able to do a 
|    forwarding path look-up for the label on an incoming packet from an 
|    interconnect in a Label Forwarding Information Base (LFIB) space 
|    that is only intended for its own service context or provide a 
|    mechanism on the data plane that would ensure the incoming labels 
|    are what ASBR1 has allocated and advertised. 
|     
|    A similar concept has been proposed in "Requirements for Multi-
|    Segment Pseudowire Emulation Edge-to-Edge (PWE3)" [PW-REQ]. 
|     
| 9. Summary of MPLS and GMPLS Security  
|     
|    The following summary provides a quick check list of MPLS and GMPLS 
|    security threats, defense techniques, and the best practice guide 
|    outlines for MPLS and GMPLS deployment.  
|     
|    9.1. MPLS and GMPLS Specific Security Threats 
|     
| 9.1.1. Control plane attacks 
|     
|    Types of attacks on the control plane: 
|      - Unauthorized LSP creation 
|      - LSP message interception 

    LSP message corruption
    LSP message deletion
    Replay
    DOS through signalling overload
    Protocol specific techniques such as...

|    Attacks against RSVP-TE: DoS attack with setting up 
|    unauthorized LSP and/or LSP messages. 
|     
|    Attacks against LDP: DoS attack with storms of LDP Hello 
|    messages or LDP TCP Syn messages. 
|     
|    Attacks may be launched from external or internal sources, or 
|    through SP management systems. 
|     
|    Attacks may be targeted to the SP routing protocols or 
|    infrastructure elements. 
|     
|    In general, control protocols may be attacked by: 
|      - MPLS signaling (LDP, RSVP-TE)  
|      - PCE signaling 
|      - IPsec signaling (IKE and IKEv2) 
|      - ICMP and ICMPv6 
|      - L2TP 
|      - BGP-based membership discovery 
|      - Database-based membership discovery (e.g., RADIUS) 
|      - Other protocols that may be important to the control  
|            infrastructure, e.g., DNS, LMP, NTP, SNMP, and GRE. 
|       
| 9.1.2. Data plane attacks 
|     
|      - Unauthorized observation of data traffic 
|      - Data traffic modification 
|      - Spoofing and replay 
|      - Unauthorized Deletion 
|      - Unauthorized Traffic Pattern Analysis 
|      - Denial of Service Attacks 

|    9.2. Defense Techniques 
|     
|      1) Authentication: 
|  
|         - Identity authentication - Key management  
|         - Management System Authentication 
|         - Peer-to-peer authentication 
|     
|      2) Cryptographic techniques 
|      3) Use of IPsec in MPLS/GMPLS networks 
|      4) Encryption for device configuration and management 
|      5) Cryptographic Techniques for MPLS Pseudowires 
|      6) End-to-End versus Hop-by-Hop Protection (CE-CE, PE-PE, PE-CE) 
|      7) Access Control techniques 
|       
|         - Filtering 
|         - Firewalls 
|         - Access Control to management interfaces 
|            
|      8) Infrastructure isolation 
|      9) Use of aggregation infrastructure 
|      10) Quality Control Processes 
|      11) Testable MPLS/GMPLS Service 
|     
|    9.3. Service Provider MPLS and GMPLS Best Practice Outlines 
|     
| 9.3.1. SP infrastructure protection 
|  
|      1) General control plane protection 
|         - Protocol authentication within the core 
|         - Infrastructure Hiding (e.g. disable TTL propagation) 
|      2) RSVP control plane protection 
|         - Using RSVP security tools 
|         - Isolation of the trusted domain 
|         - Deactivating RSVP on interfaces with neighbors who are not 
|            authorized to use RSVP 
|         - RSVP neighbor filtering at the protocol level and data plane 
|            level 
|         - Authentication for RSVP messages 
|         - RSVP message pacing 
|      3) LDP control plane protection (similar techniques as for RSVP) 
|      4) Data plane protection 
|         - User Access link protection 
|         - Link Authentication 
|         - Access routing control (e.g. prefix limits, route dampening, 
|            routing table limits (e.g. VRF limits) 
|         - Access QoS control 
|         - Using customer service monitoring tools 
|     
| 9.3.2.  Inter-provider Security 
|     
|    Inter-provider connections are high security risk areas. Similar 
|    techniques and procedures as described in for SP general core 
|    protection are listed below for inter-provider connections. 
|     
|      1) Control plane protection at the inter-provider connections 
|         - Authentication of Signaling Sessions 
|         - Protection against DoS attacks in the Control Plane 
|         - Protection against Malformed Packets 
|         - Ability to Enable/Disable Specific Protocols 
|         - Protection Against Incorrect Cross Connection 
|         - Protection Against Spoofed Updates and Route Advertisements 
|         - Protection of Confidential Information 
|         - Protection Against over-provisioned number of RSVP-TE LSPs 
|            and bandwidth reservation 
|      2) Data Plane Protection at the inter-provider connections 
|         - Protection against DoS in the Data Plane 
|         - Protection against Label Spoofing 
|  

(Unfortunately, this summary reads like a table of contents to me.  If
we captured 1-2 best and key recommendations here, it would be more useful)

|  
| 10.     Security Considerations 
|  
|     
|    Security considerations constitute the sole subject of this memo 
|    and hence are discussed throughout.  Here we recap what has been 
|    presented and explain at a high level the role of each type of 
|    consideration in an overall secure MPLS/GMPLS system. 
|     
|    The document describes a number of potential security threats.  
|    Some of these threats have already been observed occurring in 
|    running networks; others are largely theoretical at this time.   
|     
|    DoS attacks and intrusion attacks from the Internet against service 
|    providers' infrastructure have been seen.  DoS "attacks" (typically 
|    not malicious) have also been seen in which CE equipment overwhelms 
|    PE equipment with high quantities or rates of packet traffic or 
|    routing information.  Operational or provisioning errors are cited 
|    by service providers as one of their prime concerns. 
|     
|    The document describes a variety of defensive techniques that may 
|    be used to counter the suspected threats.  All of the techniques 
|    presented involve mature and widely implemented technologies that 
|    are practical to implement. 
|     
|    The document describes the importance of detecting, monitoring, and 
|    reporting attacks, both successful and unsuccessful.  These 
|    activities are essential for "understanding one's enemy", 
|    mobilizing new defenses, and obtaining metrics about how secure the 
|    MPLS/GMPLS network is.  As such, they are vital components of any 
|    complete PPVPN security system. 
|     
|    The document evaluates MPLS/GMPLS security requirements from a 
|    customer's perspective as well as from a service provider's 
|    perspective.  These sections re-evaluate the identified threats 
|    from the perspectives of the various stakeholders and are meant to 
|    assist equipment vendors and service providers, who must ultimately 
|    decide what threats to protect against in any given configuration 
|    or service offering. 

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


From mpls-bounces@ietf.org  Mon May 19 17:08:05 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71C123A67ED;
	Mon, 19 May 2008 17:08:05 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 341E528C0FF
	for <mpls@core3.amsl.com>; Thu, 15 May 2008 15:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[AWL=0.496, 
	BAYES_50=0.001, J_CHICKENPOX_41=0.6, J_CHICKENPOX_43=0.6,
	J_CHICKENPOX_65=0.6, J_CHICKENPOX_82=0.6, J_CHICKENPOX_91=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Il+cn9Mp9Tkp for <mpls@core3.amsl.com>;
	Thu, 15 May 2008 15:03:46 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171])
	by core3.amsl.com (Postfix) with ESMTP id 489843A681B
	for <mpls@ietf.org>; Thu, 15 May 2008 15:03:46 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob109.postini.com
	([64.18.6.12]) with SMTP; Thu, 15 May 2008 15:03:26 PDT
Received: from antibaryon.jnpr.net ([172.24.247.55]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 May 2008 15:03:26 -0700
Received: from 172.24.68.119 ([172.24.68.119]) by antibaryon.jnpr.net
	([172.24.247.55]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 15 May 2008 21:56:29 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Thu, 15 May 2008 14:56:28 -0700
From: Kannan Varadhan <kannanv@juniper.net>
To: <mpls@ietf.org>
Message-ID: <C451FF9C.2DEAC%kannanv@juniper.net>
Thread-Topic: Comments on
	draft-ietf-mpls-mpls-and-gmpls-security-framework-02.txt
Thread-Index: Aci2IrkPfQam2AAPhkS41IUhj8MGUQAs82zj
In-Reply-To: <C450D1F3.2DB74%kannanv@juniper.net>
Mime-version: 1.0
X-OriginalArrivalTime: 15 May 2008 22:03:26.0568 (UTC)
	FILETIME=[803BB680:01C8B6D7]
X-Mailman-Approved-At: Mon, 19 May 2008 17:07:57 -0700
Subject: [mpls] Comments on
	draft-ietf-mpls-mpls-and-gmpls-security-framework-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


I must not have the right address for Luuan Fang.  My email to her gets
dropped silently somewhere...halleluyah t homebrew imap scripts of mine...

Here are some of my comments on the ms security document...

Thanks,


Kannan



| 
|    Network Working Grou                                L. Fang, Ed.
|    Internet Draft                               Cisco Systems, Inc.
|    Category: Informational
|   Expires: August 2008
|                  
|                                                       February 2008
|  
|  
|               Security Framework for MPLS and MPLS Networks
|          draft-ietf-mls-mpls-and-gmpls-security-framework-02.txt
|     
| 1. Introduction 
|    
|    Security is an important aspect of all networks, MPLS and GMPLS|    networks being no exception.
|     
|    MPLS and GMPLS are decribed in [RFC3031] and [RFC3945]. Various
  security considerations have been addressed in each of the many
|    RFCs n MPLS and GMPLS technologies, but no single document covers
|    gneral security considerations. The motivation for creating this
|   document is to provide a comprehensive and consistent security
|   framework for MPLS and GMPLS networks. Each individual document may
|    point to this documnt for general security considerations in
|    addition to providing security considerations specific to the
|    particular technologies the document is describing.
|    
|    In this document, we first describe the security threats relevnt
|    in the context of MPLS and GMPLS and the defensive techniques o
|    combat those threats. We considr security issues deriving both
|    from malicious or incorrect behavir of users and other parties and
|    from negligent or incorrect ehavior of providers. An important
|    part of security defense is th detection and reporting of a
|   security attack, which is also addressed in this document.
|    
|    We then discuss possible service provider security requiremets in
|    a MPLS or GMPLS environment Users have expectations for the
|    securty characteristics of MPLS or GMPLS networks. These include
|    security requirements for equipment supporting MPLS and GMPLS and
|    operational secuity requirements for providers. Service providers
|    must protect theirnetwork infrastructure and make it secure to the
|    level required toprovide services over their MPLS or GMPLS
|    networks.  
|     
|   Inter-AS and Inter-provider security are discussed with special
|    emphasis, because the seurity risk factors are higher with inter-
|    provider connection. Depending on different MPLS or GMPLS
|    techniques used, the degre of risk and the mitigation
|    methodologies vary. This document dusses the security aspects
|    and requirements for cerain basic MPLS and GMPLS techniques and
|    inter-connection models. Tis document does not attempt to cover
|    all current and future MPLS ad GMPLS technologies, as it is not
|    within the scope of tis document to analyze the security
|    properties of specific technoloies.
|     
|    It is important to clarify that, in this document, we lmit
|    ourselves to describing the providers' security requirements tht
|    pertain to MPLS and GMPLSnetworks. Readers may refer to the
|    "Security Best Practices Efforts nd Documents" [opsec effort] and
|    "Security Mechanisms for he Internet" [RFC3631] for general
|    network operation security consierations. It is not our intention,
|    however, to formulate precise "rquirements" for each specific
|    technology in terms of defining the echanisms and techniques that
|    must be implemented to satisfy such seurity requirements.
     
|    1.1. Structure of this Document
|     
|    This document is organized as follows. In Section 2, we define the
|    terminology used. In Section 3, we define the security reference
|    models for security in MPLS/GMPLS networks, which we use in the
|    rest of the document. In Section 4, we describe the security
|    threats specific to MPLS and GMPLS. In Section 5, we review
|    defensive techniques that may be used against those threats. In
|    Section 6, we describe how attacks may be detected and reported. In
|    Section 7, we describe security requirements providers may have to
|    guarantee the security of the network infrastructure for MPLS/GMPLS
|    services. In section 8, we discuss Inter-provider security
|    requirements. Finally, in Section 9, we discuss security
|    considerations for this document.
|     
|    This document has used relevant content from RFC 4111 "Securit
|    Framework of Provider Provisioned VPN for Provider-Provisioned
|    irtual Private Networks (PPVPNs)" [RFC4111], and "MPLS
|    InterCarrier nterconnect Technical Specification" [MFA MPLS ICI]
|    in the Iner-provider security discussion. We acknowledge the
|    authors ofthese documents for the valuable information and text.
|     
|     
    1.2. Authors and Contributors
|     
|    Authors: 
|    Luyuan Fag, Ed., Cisco Systems, Inc.
|    Michae Behringer, Cisco Systems, Inc.
|    Ross Callon, Juniper Networks
|   J. L. Le Roux, France Telecom
|    Raymond Zhang, British Telecom
|   Paul Knight, Nortel
|    Yaakov Stein, RAD Data Communications
|    Nbil Bitar, Verizon
|    Richard Graveman,FC Security, LLC
|    Monique Morrow,Cisco Systems, Inc.
|    Adrian Farrel, Old Dog Consulting
|    As a design eam member for the MPLS Security Framework, Jerry Ash
|    also made snificant contributions to this document.
|  
|     
|           
|     
| 2. Teminology 
|     
|    2.1.  Terminology
|  
|    This document uses PLS and GMPLS specific terminology. Definitions
|    and detais about MPLS and GMPLS terminology can be found in
|    [RFC3031] and [FC3945]. The most important definitions are
|    repeated in this section for other definitions the reader is
|    referred to [RFC3031 and [RFC3945].
|  
|    Customer Edge (CE) device: A Customer Edgedevice is a router or a
|    switch in the customer's network interfacingwith the Service
|    Provider's network.
|     
|    Forwarding Equivalnce Class (FEC): A group of IP packets that are
|    forwarded in the sae manner (e.g., over the same path, with the
|    same forwarding treatent).
|     
|    Label: A short, fixed length, physically contiguous idntifier used
|    to identify a FEC, usually of local significance.
|    
|    Label Switched Hop: A hop between two MPLS nodes, on which
|    forwarding is done usig labels.
|     
|    Label Switched Path (LSP): The path through one r more LSRs at one
|    level of the hierarchy followed by a packets n a particular FEC.
|     
|    Label Switching Router (LSR): A MPLS nod capable of forwarding
|    native L3 packets.
|     
|    Layer 2: Theprotocol layer under layer 3 (which therefore offers
|    the services ued by layer 3).  Forwarding, when done by the
|    swapping of short ixed length labels, occurs at layer 2 regardless
|    of whether the labl being examined is a ATM VPI/VCI, a frame
|    relay DLCI, or a MPS label.
|     
|    Layer 3: The protocol layer at which IP and its associaed routing
|    protocols operate.
|     
|    Link Layer: Synonymous wth layer 2.
|     
|    Loop Detection:A method of dealing with loops in which loops are
|    allowed to be set up, and data may be tranmitted over the loop,
|    but the loop is later detected.
|     
|    Lop Prevention: A method of dealing with loops in which data is
|    never ransmitted over a loop.
|     
|    Label Stack: An ordered set of labes.
|  
|    Merge Point: A node at which label merging is done.
|     
    MPLS Domain: A contiguous set of nodes that perform MPLS routin
|    and forwarding and are also in one Routing or Administratie
|    Domain. 
|     
|    MPLS Edge Node: A MPLS node that concts a MPLS domain with a node
|    outside of the domain, either because it does not run MPLS, or
|   because it is in a different domain.  Note that if a LSR hs a
|    neighboring host nt running MPLS, then that LSR is a MPLS edge
|    node. 
|     
|    MPLS Egres Node: A MPLS edge node in its role in handling traffic
|    as it leave a MPLS domain.
|     
|    MPLS Ingress Node: A MPLS edge node i its role in handling traffic
|    as it enters a MPLS domain.
|     
|   MPLS Label: A label carried in a packet header, which represents
    the packet's FEC.
|     
|    MS Node: A node running MPLS.  A MLS node is aware of MPLS
|    control protocols, runs one or more L3 routing proocols, and is
|    capable of forwarding packets based on labels. A MPLSnode may
|    optionally be also capable of forwarding native L3 pakets.
|     
|    MultiProtocol Label Switching (MPLS): An IETF workin group and the
|    effort associated with the working group.
|  
|    P: Povider Router. A Provider Router is a router in the Service
|    Provider's coe network that does not have interfaces directly
|    towards the customr. A P router is used to internnect the PE
|    routers.  
|  
|    PE: Provider Edge device. A Provider Edge devce is the equipment
|    in the Service Provider's network that interfaes with the
|    equipment in the customer's network.
|  
|     
|    
|    VPN: Virtual Private Network, which restricts communication betwen
|    a set of sites, making use of an IP backbone shared by traffic nt
|    going to or not coming from those sites ([RFC4110]).
|     
|   2.2. Acronyms and Abbreviations
|     
|       AS        Autonomous Sytem
|       ASBR      Autonomous System Border Router
|       ATM       Aynchronous Transfer Mode
|       BGP       Borr Gateway Protocol
|       BFD       Bidirectional Forwarding Detection
|       E        Customer-Edge device
|       CoS       Class of Service
|      PU       Central Processor Unit
|       DNS       Domain Name Syste
|       DoS       Denial of Service
|       FEC       Forwarding Equivaence Class
|       GMPLS     Generaized Multi-Protocol Label Switching
|       GRE       Generic Routing Encapulation
|       ICI       InterCarrier Interconnect
|       ICMP      Intrnet Control Message Protocol
|       ICMPv6    ICMP in IP Version 6
|      IGP       Interior Gateway Protocol
|       IKE       Internet Key xchange
|       IP        Internet Protocol
|       IPsec     IP Secuity
|       IPVPN     IP-based VPN
|       LDP       Label Distributio Protocol
|       L2        Layer 2
|       L2TP      Layer 2 Tuneling Protocol
|       L3        Layer 3
|       LMP       Link Managemet Protocol
|       LSP       Label Switched Path
|       LSR       Label Swiching Router
|       MD5       Message Digest Algorithm
|      MPLS      MultiProtocol Label Switching
|       MP-BGP    Multi-ProtocoBGP
|       NTP       Network Time Protocol
|       OAM       Operatios, Administration, and Management
|       PCE      Path Computation Element
|       PE        Provider-Edge device
|       PVPN     Provider-Provisioned Virtual Private Network
|       PSN      Packet-Switched Network
|       PW        Pseudowire
|       QoS      Quality of Service
|       RR       Route Reflector
|       RSVP      Resource Reservation Protocol
|       RSV-TE   Resource Reservation Protocol with Traffic Engineering
|                     Extensions
|       SLA       Service Level Agreement
|      SNMP      Simple Network Management Protocol
|       SP        Srvice Provider
|       SSH       Secure Shell
|       SSL       Secure Sokets Layer
|       SYN       Synchronize packet in TCP
|       TCP      Transmission Control Protocol
|       TM       Time Division Multiplexing
|       TE        Traffic Engineering
|      TLS       Transport Layer Security
|       ToS       Type of Service       TTL       Time-To-Live
|       UDP       User Datagram Protool
|       VC        Virtual Circuit
|       VPN       Virtual Private etwork
|       WG        Working Group of IETF
|       WSS       Web Serices Security
|     
|     
| 3. Scurity Reference Models
|    This section defines a reference model for securty in MPLS/GMPLS
|    networks.  
|     
|    A MPLS/GMPLS core netork is defined here as the centr network
|    infrastructure (P and PE routers). A MPLS/GMPLS core network
    consists of one or more SP networks All network elements in the
|    core are under the operational contol of one or more MPLS/GMPLS
|    SPs. Even if the MPLS/GMPLS core is provded by several SPs,
|    towards the end users itappears as a single zone of trust.
|    However, when several SPs togeter provide a MPLS/GMPLS core, each
|    SP still needsto secure itself against the other SPs.
|     
|    A MPLS/GMPLS nd user is a company, institution, or residential
|    client of the SP.
|     
    This document defines each MPLS/GMPLS core in a single domain to be
|   a trusted zone. A primary concern is about security aspects that
|    elate to breaches of security from the "outside" of a trusted zone
|    t the "inside" of this zone. Figure 1 depicts the concept of
|    trusted zones within the MLS/GMPLS framework.
|  
|  
|                       /-------------\
|    +------------+    /               \         +------------+
|    | MPLSGMPLS +---/                 \--------+     MPLS   |
|    | user         |  MPLS/GMPLS Core  |             user   |
|    | site       +---                 /XXX----+     site   |
|    +------------+    \               / XXX     +-----------+
|                       \-------------/  | |
|                                       | |
|                                        | +-----\
|                                        +-------/  "Internet"
|     
|         MPLS/GMPLS Core with user connectionsand Internet connection
|     
|    Figure 1: The MPLS/GMPLS trusted zon model.

In this figure, is there significance to the fact that the nternet
connection is attached at the MPLS user site?  Why is one MPL only, and
te other referred to as an MPLS/GMPLS site?

|    The trused zone is the MPLS/GMPLS core in a single AS within a
|    single ervice Provider.
|     
|    The boundaries of  trust domain should be carefully defined when
|   analyzing the security property of each individual network, e.g.
|    the boundaries can be at the link termination, remote peers, area,
|    or quite commonly, ASes.
|     
|    In principle, the trused zones should be separate; however,
|    typically MPLS core etworks also offer Internet access, in which
|    case a transi point (marked with "XXX" in Figur1) is defined. In

So is the Internet access from within the core?  If so, what s the
boundary?

|    the case of MPLS/GMPLS inter-provider connections, he trusted zone
|    of each provider ends at the respective ASBRs (ASB1 and ASBR2 for
|    Provider A, ASBR3 and ASBR4 for Provider B).
|    
|    A key requirement of MPLS and GMPLS networks s that the security
|    of the trusted zone not be comprmised by interconnecting the
|    MPLS/GMPLS core infrastructure with another povider's core
|    (MPLS/GMPLS or non-MPLS/GMPLS), the Internet, or ed users.
|     
|    In addition, neighbors may be trusted or untrused. Neighbors may
|    be authorized or unauthorized. Even though a nighbor may be
|    authorized for communication, it may not be trusted. or example,
|    when connecting with another provider's ASBRs toset up inter-AS
|    LSPs, the other provider is considered an untrustedbut authorized
|    neighbor. 
|  
|                  
|                +---------------+        +--------------+
|                 |               |        |                |
|                | MPLS/GMPLS   ASBR1----ASBR3  MPLS/GMPLS |
|           CE1-PE1   Network    |        |     Network   PE2--CE2
|                | Provider A   ASBR2----ASBR4  Provider B |
|                 |              |        |                |
|                 +---------------+       +----------------+
|                  
|         
|    For Provide A:
|         Trusted Zone: Provider A MPSL/GMPLS network
|         Trsted neighbors: PE1, ASBR1, ASBR2
|         Authorized but untrusted neghbor: provider B
|         Unauthorized neighbors: CE1, CE2
|  
|    Figure 2. MPLS/GMPLS trusted zone and authorized neighbor.
|  
|     
|   All aspects of network security independent of whher a network is
|    a MPLS/GMPLS network are out of scope. For example, attack from
|    the Internet to a user's web-server connected through the
|   MPLS/GMPLS network are not considered here, unless the way the    MPLS/GMPLS network is provisioned could make a difference to the
|    securiy of this user's server.
|  
| 4. Security Threats
|     
|    This sectin discusses the various network security threats that
|    may endangerMPLS/GMPLS networks.  The discussion is limited 
|    those threats that are unique to MPLS/GMPLS networks o that affect
|    MPLS/GMPLS network in unique ways.
|     
|    A successful atack on a particular MPLS/GMPLS network or on a SP's
|    MPLS/GMPLS infrstructure may cause one or more of the following
|    ill effects: 
|    
|     - Observation, modification, or deletion of a provide's or user's
|       data. 
|     - Replay of a provider's or uses data.
|     - Injection of inauthentic data into a provider's or user's
|      traffic stream.
|     - Traffic pattern analysis on a provider' or user's traffic.
|     - Disruption of a provider's or user's connectvity.
|     - Degradation of a provider's service quality.
|     
|    It iseful to consider that threats, whether malicious or
|    accidental, may com from different categories of sources.  For
|    example they may coe from:
|     
|     - Other users whose services are provided by th same MPLS/GMPLS
|       core. 
|     - The MPLS/GMPLS SP or perons working for it.
|    - Other persons who obtain physical access to a MPLS/GMPLS SP's
|    ste. 
|     - Other persons who use social engineering methods to influence
|      the behavior of a SP's personnel.
|     - Users of the MPLS/GMPLS ntwork itself, e.g., intra-VPN threats.
|       (Such threats are beyond he scope of this document.)

Why is only this called out?  In fact if the others are applicable,
should this also not be applicable?

     - Others, e.g., attackers from the Internet at large.
|     - Other Ps in the case of MPLS/GMPLS Inter-
|       provider connection. Th core of the other provider may or may
|       not be using MPLS/GMPLS.
|    - Those who create, deliver, install, and maintain software for
|      network equipment.
|     
|    
|    Given that security is generally a tradeoff between expense and
|    rik, it is also useful to consider the likelihood of different
|    attacs occurring.  There is at least a perceved difference in the
|    likelihood of most types of attacks being successflly mounted in
|    different environments, such as:
|     
|     - A PLS/GMPLS core inter-connecting with another provider's core
|     - A MPS/GMPLS configuration transiting the public Internet
|     
|    Most tyes of attacks become easier to mount and hence more likely
|    as the sared infrastructure via which service is provided expands
|    from a single SP to multiple cooperating SPs to the global
|    Internet.  Attaks that may not be of sufficient likeliness to
|    warrant concern in aclosely controlled environment often merit
|    defensive measures in broader more open environments. In closed
|    communities, it is often practicl to deal with misbehavior after
|    the fact: an employee can be diiplined, for example.
|     
|    The following sections discuss specfic types of exploits that
|    threaten MPLS/GMPLS networks.
|     
|   4.1. Attacks on the Control Plane
|    This category encompasses atacks on the control structures
|    operated by the SP with MPLS/GMPLScores.
|     

This section contains multiple separate elements.  They ned to be
grouped together.  There are the general elements:

   41.1.       LSP creation by an unauthorized element
   4.1.2.      LSP message interception
   4.1.5.       Denial of Service Attacks onthe Network Infrastructure
   4.1.6.       Attacks on the SP's MPLS/GMPS Equipment via
               Management Interfaces
   4.1.8.       Cross-Connection of Traffic between Users
   4.1.9.       Attacks against Routing Protocols
   4.1.10.      Other Attacks on Contol Traffic

Separately, probably as a sub clause in 4.1.9, you shoul put 4.1.3 and
4.1.4.  I would think that Section 4.1.7 on social enginering should be
in its own category.

|    4.1.7.       Social Enginering Attacks on the SP's Infrastructure

|    4.1.1.       LSP creaton by an unauthorized element
|  
|    The unauthorized element can bea local CE or a router in another
|    domain.  An unauthorized elment can generate MPLS signaling
|    messages.  At the least, thi can result in extra control plane and
|    forwarding state, andif successful, network bandwidth could e
|    reserved unnecessarily. This may also result in theft of service
|    nd loss of revenue.

This type of attack could come from eitherunauthorized (CE) sources,
or authorized, but untrusted sources (ABR), rght?  If the attack
fails, it creates overload in the control plane.  Ifit succeeds,
it resuls in creation of bogus forwarding state, probablystealing
of network bandwidth in the dataplane, and, if te signalling were
propagated into the trusted zone, comromizes the entire network.
THe latter could occur because the forwarded signallng state is coming
from a trusted router, and is typically assumed to e therefore trusted.

|    4.1.2.      LSP message interception
|     
|    This threat might be accomplished by montoring network traffic,
|    for example, after a physical intrusion. Wthout physical
|    intrusion, it could be accomplished with an unauthrized software
|    modification. Also many technologies such as terrstrial microwave,
|    satellite, or free-space optical could beintercepted without
|    physical intrusion. If successful, it could proide information
|    leading to label spoofing attacks.  It also raise confidentiality
|    issues. 

ok.

|    4.1.3.       Attacks against RVP-TE
|  
|    RSVP-TE, described in [RFC9], is the control protocol used to
|    set up GMPLS and traffic engineered MPL tunnels.
|     
|    There are two major types of Denial of Service (DoS attacks
|    against a MPLS domain based on RSVP-TE. The attacker may se up
|    numerous unauthorized LSPs or may send a stom of RSVP messages.
|    It has been demonstrated that unproected routers running RSVP can
|    be effectively disaed by both types of DoS attacks.
|     
|    These attacks may evenbe combined, by using the unauthorized LSPs
|    to transport additionl RSVP (or other) messages across routers
|    where they might otherwis be filtered out.  RSVP attacks can be
|    launched against adjacnt routers at the border with the attacker,
|    or against non-adjacnt routers within the MPLS domain, if there is
|    no effective mechanim to filter them out.

These are protocol specific cases.  Either hese should be under control
plane vulnerabilities speficic to a ruting protocol, or a use cases
section where the applicability of each vetor specific to a protocl is
worked out.  In a more rigourous context, it should probably be 
separate document after this one is done.

|    4.1.4.       Attacks gainst LDP
|     
|    LDP, described in [RFC3036], is the control protcol used to set up
|    MPLS tunnels without TE.
|     
|    There aretwo significant types of attack against LDP.  An
|    unauthorized netwok element can establish a LDP session by sending
|    LDP Hello and LDP nit messages, leading to the otential setup of
|    a LSP, as well asaccompanying LDP state table consumption.  Even
|    without successfully estabshing LSPs, an attacker can launch a
|    DoS attack in the form of a storm of LP Hello messages or LDP TCP
|    Syn messages, leading to high CPU utilzation on the target router.

Likewise.

|     
|    4.1.5.       Deial of Service Attacks on the Nwork
|    Infrastructure
|     
|    DoS attacks could be accomplished throuh a MPLS signaling storm,
|    resulting in high CPU utilization and pssibly leading to control
|    plane resource starvation.

Would you caracterise attacks on the dataplane that keep the
dataplane busy withuseless work as DoS attacks?  For instance, label
spoofing attempts.Knowing the label allocation patterns of a router
also makes it easy to moun such attacks in the dataplane.

|    Control plane DoS attacks an be mounted specifically against the
|    mechanisms the SP uses toprovide various services, or against the
|    general infrastructure ofthe service provider, e.g., P routers or
|   shared aspects of PE routers.  (An attack against the general
|    ifrastructure is within the scope of this document only if the
|    attackcan occur in relation with the MPLS/GMPLS infrastructure;
|    otherwie is not a MPLS/GMPLS-specific issue.)

It was very hard for me to pars what was said here.  For instance,
what is an example o a mechanism that a SP would use to provide
services?  If I had a sense of that,I could then have a sense of what
kinds of attacks to consider.

Also, yo view P routers are "general infrastructure" here?  I thought
that aP router, from your original description, was part of the
MPLS/GMPLS ifrastructure.  Does this document preclude attacks on P
routers?

r maybe, I am readinthis paragraph all wrong?

|    The attacks described in the following sectios may each have
|    denial of service as one of their effects.  OtherDoS attacks are
|    also possible.
|     
|    4.1.6.       Attacks o the SP's MPLS/GMPLS Equipment via
|    Management Interfaces
|     
|   This includes unauthorized access to a SP's infrastructure
|    equiment, for example to reconfigure the equipment or to extract
|    inormation (statistics, topology, etc.) pertaining to the network

Would this not consititute an atack on the general infrastructure
itself, not specifically MPLS/GMPLS infrastruture, and anything done ot
protect there will apply here---in otherwords, out of scope in this
document?

|    4.1.7.       Social Engineerig Attacks on the SP's
|    Infrastructure
|  
|    Attacks in which the srvice provider network is reconfigured or
|    damaged, or in which cnfidential information is improperly
|    disclosed, may be mounted by maipulation of a SP's personnel.
|    These types of attacks are MPLS/GMLS-specific if they affect
|    MPLS/GMPLS-serving mechanisms.

Again,this appears to not be specific to MPLS/GMPLS infrastructure?

|    4.1.8       Cross-Connection of Traffic between Users
|    
|    This refers to the event in which expected isolation between|    separate users (who may be VPN users) is breached.  This includes|    cases such as:
|     - A site being connected into the "wrong" PN
|     - Traffic being replicated and sent to an unauthorized use
|     - Two or more VPNs being improperly merged together
|     - A pont-to-point VPN connecting the wrong two points
|     - Any packet or rame being improperly delivered outside the VPN
|       to which it belons
|     
|    Mis-connection or crosconnection of VPNs may be caused by service
|    provider or equipment vendor error, or by the malicious action of
|    an attacker. The breach may be physical (e.g., PE-CE links mis-
|    connected) or logical (e.g., improper device configuration).
|     
|    Anecdotal evidence suggests that the cross-connection threat is one
|    of the largest security concerns of users or would-be users).

ok.

|    4.1.9.       Attacks against Routig Protocols
|     
|    This encompasses attacks against underlying outing protocols that
|    are run by the SP and that directly suport the MPLS/GMPLS core.
|    (Attacks against the use of routing prtocols for the distribution
|    of backbone routes are beyond the scoof this document.)
|    Specific attacks against popular routing protocols hve been widely
|    studied and described in [RFC4593].
|     
    4.1.10.      Other Attacks on Control Traffic
|     
|    Besides routing and management protocols (covered separately inthe
|    previous sections), a number ofother control protocols may be
|    directly inolved in delivering services by the MPLS/GMPLS core.
|    These include but my not be limited to:
|     
|     - MPLS signaling (LDP, RSVP-TE) discused above in subsections
|       4.1.4 and 4.1.3
|     - PCE signaling|     - IPsec signaling (IKE and IKEv2)
|     - ICMP and ICMPv6
|     - 2TP 
|     - BGP-based membership discovery
|     - Database-based membeship discovery (e.g., RADIUS)
|     - Other protocols that may be impotant to the control
|       infrastructure, e.g., DNS, LMP, NTP, SNMP,and GRE.
|     
|    Attacks might subvert or disrupt the activities of tese protocols,
|    for example via impersonation or DoS.
|     
|    4.. Attacks on the Data Plane
|     
|    This category encompasses attaks on the provider's or end user's
|    ata.  Note that from the MPLS/GMPLS network end user's point of
|    view, som of this might be control plane traffic, e.g. routing
|    protocols rning from user site A to user site B via a L2 or L
|    connection, which may be some type of VPN.

|    4.2.1.       Unauthrized Observation of Data Traffic
|     
|    This refers to "sniffing"provider or end user packets and
|    examining their contents.  This cn result in exposure of
|    confidential information.  It can also be a firt step in other
|    attacks (described below) in which the recorded ata is modified
|    and re-inserted, or simply replayed later.
|    
|    4.2.2.       Modification of Data Traffic
|     
|    This rfers to modifying the contents of packets as they traverse
|    the MPS/GMPLS core.
|     
|    4.2.3.       Insertion of Inauthentic Data Trafic: Spoofing
|    and Replay 
|     
|    Spoofing refers to sending a usr or inserting into a data stream
|    packets that do not belong, with he objective of having them
|    accepted by the recipient as legitimat.  Also included in this
|    category is the insertion of copies f once-legitimate packets that
|    have been recorded and replayed.
|    
|    4.2.4.       Unauthorized Deletion of Data Traffic
|     
|   This refers to causing packets to be discarded as they traverse the
|   MPLS/GMPLS networks.  This is a specific type of Denial of Service
|   attack. 
|     
|    4.2.5.       Unauthorized Traffic Pattern Analysi
|     
|    This refers to "sniffing" provider or user packets and examining|    aspects or meta-aspects of them that may be visible even when the
|   packets themselves are encrypted.  An attacker might gain useful
    information based on the amount and timing of traffic, packet
|    szes, source and destination addresses, etc.  For most users, this
|   type of attack is generally considered to be significantly les of
|    a concern than the other types discussed in this section.

It s also that a lot of the above dataplane attacks require physical
accss/control of the device  Mounting these attacks through remote
means is probablynot trivial.

|    4.2.6.       Denial of Service Attacks
|     
|    Denial o Service (DoS) attacks are those in which an attacker
|    attemts to disrupt or prevent the use of a serice by its
|    legitimate users.  Taking network devices out of service, modifing
|    their configuration, or overwhelming them with requests for serice
|    are several of the possible avenues for DoS attack.
|     
|    verwhelming the network with requests for service, otherwise known
|   as a "resource exhaustion" DoS attack, may target any resource i
|    the network, e.g., link bandwidth, paket forwarding capacity,
|    session capacity for vrious protocols, CPU power, table size,
|    storage overflows, and s on.
|     
|    DoS attacks of the resource exhaustion type can b mounted against
|    the data plane of a particular provider or end user by attempting
|    to insert (spoofing) an overwhelming quantity ofinauthentic data
|    into the provideror end user network from the outside of the
|    trusted zone. Potentia results might be to exhaust the bandwidth
|    available to that provier or end user or to overwhelm the
|    cryptographic authenication mechanisms of the provider or end
|    user. 
|     
|    Data plane esource exhaustion attacks can also be mounted by
|    overwelming the service provider's general (MPLS/GMPLS-
|    indepndent) infrastructure with traffic.  These attacks on the 
|    general infrastructure are ot usually a MPLS/GMPLS-specific issue, 
|    unless the attack is mountd by another MPLS/GMPLS network user 
|    from a privileged position  (E.g., a MPLS/GMPLS network user might 
|    be able to monopoize network data plane resources an thus disrupt 
|    other users.) 

DoS atacks can lead to SLA violations by the SP, particularly if
significant resources are consumed either servicing the DoS or working
to fend it off.

Also, what about label spoofing in the data plane?  How does it get
created, and how would it get detected/mitigated?  It is mentioned in
the dataplane context in other places.  Why do we believe label spoofing
is only critical in a inter-provider context?

|    Many DoS attacks use amplification, whereby the attacker co-opts 
|    otherwise innocent parties to increase the effect of the attack. 
|    The attacker may, for example, send packets to a broadcast or 
|    multicast address with the spoofed source address of the victim, 
|    and all of the recipients may then respond to the victim.  
|  
|  
| 5. Defensive Techniques for MPLS/GMPLS Networks 
|     
|    The defensive techniques discussed in this document are intended to 
|    describe methods by which some security threats can be addressed.  
|    They are not intended as requirements for all MPLS/GMPLS 
|    implementations.  The MPLS/GMPLS provider should determine the 
|    applicability of these techniques to the provider's specific 
|    service offerings, and the end user may wish to assess the value of 
|    these techniques to the user's service requirements. The 
|    operational environment determines the security requirements. 
|    Therefore, protocol designers need to provide a full set of 
|    security services, which can be used where appropriate. 
|     
|    The techniques discussed here include encryption, authentication, 
|    filtering, firewalls, access control, isolation, aggregation, and 
|    other techniques.  
|     
|    Often, security is achieved by careful protocol design, rather than 
|    by adding a security method. For example, one method of mitigating 
|    DoS attacks is to make sure that innocent parties cannot be used to 
|    amplify the attack. Security works better when it is "designed in" 
|    rather than "added on." 
|     
|    Nothing is ever 100% secure.  Defense therefore involves protecting 
|    against those attacks that are most likely to occur or that have 
|    the most direct consequences if successful.  For those attacks that 
|    are protected against, absolute protection is seldom achievable; 
|    more often it is sufficient just to make the cost of a successful 
|    attack greater than what the adversary will be willing or able to 
|    expend. 
|     
|    Successfully defending against an attack does not necessarily mean 
|    the attack must be prevented from happening or from reaching its 
|    target.  In many cases the network can instead be designed to 
|    withstand the attack.  For example, the introduction of inauthentic 
|    packets could be defended against by preventing their introduction 
|    in the first place, or by making it possible to identify and 
|    eliminate them before delivery to the MPLS/GMPLS user's system.  
|    The latter is frequently a much easier task. 
|     
|  
|    5.1. Authentication 
|     
|    To prevent security issues arising from some Denial-of-Service 
|    attacks or from malicious or accidental misconfiguration, it is 
|    critical that devices in the MPLS/GMPLS should only accept 
|    connections or control messages from valid sources.  Authentication 
|    refers to methods to ensure that message sources are properly 
|    identified by the MPLS/GMPLS devices with which they communicate.  
|    This section focuses on identifying the scenarios in which sender 
|    authentication is required and recommends authentication mechanisms 
|    for these scenarios. 
|     
|    Cryptographic techniques (authentication, integrity, and 
|    encryption) do not protect against some types of denial of service 
|    attacks, specifically resource exhaustion attacks based on CPU or 
|    bandwidth exhaustion. In fact, the processing required to decrypt 
|    or check authentication may, in the case of software-based 
|    cryptographic processing, in some cases increase the effect of 
|    these resource exhaustion attacks. With a hardware cryptographic 
|    accelerator, attack packets can be dropped at line speed without a 
|    cost of software cycles. Cryptographic techniques may, however, be 
|    useful against resource exhaustion attacks based on exhaustion of 
|    state information (e.g., TCP SYN attacks). 
|     
|    The MPLS user plane, as presently defined, is not amenable to 

What is this MPLS user plane?  Where is it defined?

|    source authentication as there are no source identifiers in the 
|    MPLS packet to authenticate. The MPLS label is only locally 
|    meaningful, and it identifies a downstream semantic rather than an 
|    upstream source. 
|      
|    When the MPLS payload carries identifiers that may be authenticated 
|    (e.g., IP packets), authentication may be carried out at the client 
|    level, but this does not help the MPLS SP, as these client 
|    identifiers belong to an external, untrusted network. 
|      
| 
|   5.1.1. Management System Authentication 
|  
|    Management system authentication includes the authentication of a 
|    PE to a centrally-managed network management or directory server 
|    when directory-based "auto-discovery" is used.  It also includes 
|    authentication of a CE to the configuration server, when a 
|    configuration server system is used. 

This is not clear.  Why is device authentication restricted only to the
CE or PE?  Why is this considered differently than peer-to-peer
authentication?  Aren't the techniques and issues similar?

|   5.1.2. Peer-to-Peer Authentication 
|  
|    Peer-to-peer authentication includes peer authentication for 
|    network control protocols (e.g., LDP, BGP, etc.), and other peer 
|    authentication (i.e., authentication of one IPsec security gateway 
|    by another). 
|     
| 
|   5.1.3. Cryptographic techniques for authenticating identity 
|     
|    Cryptographic techniques offer several mechanisms for 
|    authenticating the identity of devices or individuals. These 
|    include the use of shared secret keys, one-time keys generated by 
|    accessory devices or software, user-ID and password pairs, and a 
|    range of public-private key systems. Another approach is to use a 
|    hierarchical Certification Authority system to provide digital 
|    certificates. 

Again, here I would think that device authentication is somewhat
different from individuals being authenticated?

In a gist, I would think that this section ought to outline that
entities across a trust or authorization boundary need to be
authenticated to ensure that the entitiers are who they are, and
appropriately define their roeles and responsibilities on this device.
In this context, the CE, and neighbour PEs are entities that need to be
authenticated.  Not direclty in the trust relationship, but equally
important, is for the management system to be similarly authenticated.
The inverse of this is that the device must simliarly provide its
authentication credentials to each of those entities.  THen, we ought to
outine the techniques for authentication, including source
authentication, and its difficulties, and the ability to do
cryptographic authentication.  This then segues into the next section.

|    This section describes or provides references to the specific 
|    cryptographic approaches for authenticating identity.  These 
|    approaches provide secure mechanisms for most of the authentication 
|    scenarios required in securing a MPLS/GMPLS network. 
|     
|     
|    5.2. Cryptographic Techniques 
|     
|    MPLS/GMPLS defenses against a wide variety of attacks can be 
|    enhanced by the proper application of cryptographic techniques.  
|    These are the same cryptographic techniques that are applicable to 
|    general network communications.  In general, these techniques can 
|    provide confidentiality (encryption) of communication between 
|    devices, can authenticate the identities of the devices, and can 
|    ensure that it will be detected if the data being communicated is 
|    changed during transit. 
|     
|    Several aspects of authentication are addressed in some detail in a 
|    separate "Authentication" section. 
|     
|    Cryptographic methods add complexity to a service and thus, for a 
|    few reasons, may not be the most practical solution in every case. 
|    Cryptography adds an additional computational burden to devices, 
|    which may reduce the number of user connections that can be handled 
|    on a device or otherwise reduce the capacity of the device, 
|    potentially driving up the provider's costs.  Typically, 

This compute burden is going down over time as CPUs become more
powerful, and hardware acceleration of crypto is more generally
available.  Also, isn't it that these crypto techniques are only
required for the validation of signalling messages?

|    configuring encryption services on devices adds to the complexity 
|    of their configuration and adds labor cost. Some key management 
|    system is usually needed. Packet sizes are typically increased when 

With experience, we are getting better are making key management
configuration more turnkey and simpler.  However, the harder problem
also needs to be acknowledged of providing for the ability to change
keys as needed, as well as a recommendation for SPs to have a policy
to changes these keys every so often.

|    the packets are encrypted or have integrity checks or replay 
|    counters added, increasing the network traffic load and adding to 
|    the likelihood of packet fragmentation with its increased overhead.  
|    (This packet length increase can often be mitigated to some extent 
|    by data compression techniques, but at the expense of additional 
|    computational burden.) Finally, some providers may employ enough 
|    other defensive techniques, such as physical isolation or filtering 
|    and firewall techniques, that they may not perceive additional 
|    benefit from encryption techniques. 
|     
|    Users may wish to provide confidentiality end to end. Generally, 
|    encrypting for confidentiality must be accompanied with 
|    cryptographic integrity checks to prevent certain active attacks 
|    against the encrypted communications. On today's processors, 
|    encryption and integrity checks run extremely quickly, but key 
|    management may be more demanding in terms of both computational and 
|    administrative overhead. 

I would think that end-to-end encryption is generally a good idea
for customers wishing to protect their data, but is orthogonal to
MPLS/GMPLS.  Why do we need to mention it here?

|    The trust model among the MPLS/GMPLS user, the MPLS/GMPLS provider, 
|    and other parts of the network is a major element in determining 
|    the applicability of cryptographic protection for any specific 
|    MPLS/GMPLS implementation. In particular, it determines where 
|    cryptographic protection should be applied: 
|    -  If the data path between the user's site and the 
|       provider's PE is not trusted, then it may be used on the 
|       PE-CE link. 
|    -  If some part of the backbone network is not trusted, 
|       particularly in implementations where traffic may travel 
|       across the Internet or multiple providers' networks, then 
|       the PE-PE traffic may be cryptographically protected. One 
|       also should consider cases where L1 technology may be 
|       vulnerable to eavesdropping. 
|    -  If the user does not trust any zone outside of its 
|       premises, it may require end-to-end or CE-CE cryptographic 
|       protection. This fits within the scope of this MPLS/GMPLS 
|       security framework when the CE is provisioned by the 
|       MPLS/GMPLS provider. 

    However, this leads to whether the end user trusts the SP to
    provide appropriate crypto protection on a shared device, or should
    provision their own through other means.  Also, the peer CE for this
    user may be across an inter-provider boundary, in which case, the SP
    can only provision one end of the crypto link.

|    -  If the user requires remote access to its site from a 
|       system at a location that is not a customer location (for 
|       example, access by a traveler) there may be a requirement 
|       for cryptographically protecting the traffic between that 
|       system and an access point or a customer's site. If the 
|       MPLS/GMPLS provider supplies the access point, then the 
|       customer must cooperate with the provider to handle the 
|       access control services for the remote users. These access 
|       control services are usually protected cryptographically, 
|       as well. 
|     
|    Access control usually starts with authentication of the 
|    entity. If cryptographic services are part of the scenario, 
|    then it is important to bind the authentication to the key 
|    management. Otherwise the protocol is vulnerable to being 
|    hijacked between the authentication and key management. 
|     
|    Although CE-CE cryptographic protection can provide integrity and 
|    confidentiality against third parties, if the MPLS/GMPLS provider 
|    has complete management control over the CE (encryption) devices, 
|    then it may be possible for the provider to gain access to the 
|    user's traffic or internal network. Encryption devices could 
|    potentially be reconfigured to use null encryption, bypass 
|    cryptographic processing altogether, reveal internal configuration, 
|    or provide some means of sniffing or diverting unencrypted traffic. 
|    Thus an implementation using CE-CE encryption needs to consider the 
|    trust relationship between the MPLS/GMPLS user and provider. 
|    MPLS/GMPLS users and providers may wish to negotiate a service 
|    level agreement (SLA) for CE-CE encryption that provides an 
|    acceptable demarcation of responsibilities for management of 
|    cryptographic protection on the CE devices. The demarcation may 
|    also be affected by the capabilities of the CE devices. For 
|    example, the CE might support some partitioning of management, a 
|    configuration lock-down ability, or shared capability to verify the 
|    configuration. In general, the MPLS/GMPLS user needs to have a 
|    fairly high level of trust that the MPLS/GMPLS provider will 
|    properly provision and manage the CE devices, if the managed CE-CE 
|    model is used. 
|     
|     
| 
|   5.2.1. IPsec in MPLS/GMPLS 
|  
|    IPsec [RFC4301] [RFC4302] [RFC4835] [RFC4306] [RFC2411] is the 
|    security protocol of choice for encryption at the IP layer (Layer 
|    3).  IPsec provides robust security for IP traffic between pairs of 
|    devices.  Non-IP traffic such as IS-IS routing must be converted to 
|    IP (e.g., by encapsulation) in order to use IPsec.  
|  
|    In the MPLS/GMPLS model, IPsec can be employed to protect IP 
|    traffic between PEs, between a PE and a CE, or from CE to CE.  CE-
|    to-CE IPsec may be employed in either a provider-provisioned or a 
|    user-provisioned model.  Likewise, IPsec protection of data 
|    performed within the user's site is outside the scope of this 
|    document, because it is simply handled as user data by the 
|    MPLS/GMPLS core. However, if the SP performs compression, pre-
|    encryption will have a major effect on that operation. 
|     
|    IPsec does not itself specify an encryption algorithm.  It can use 
|    a variety of integrity or confidentiality algorithms (or even 
|    combined integrity and confidentiality algorithms), with various 
|    key lengths, such as AES encryption or AES message integrity 
|    checks.  There are trade-offs between key length, computational 
|    burden, and the level of security of the encryption.  A full 
|    discussion of these trade-offs is beyond the scope of this 
|    document.  In practice, any currently recommended IPsec protection 
|    offers enough security to reduce the likelihood of its being 
|    directly targeted by an attacker substantially; other weaker links 
|    in the chain of security are likely to be attacked first.  
|    MPLS/GMPLS users may wish to use a Service Level Agreement (SLA) 
|    specifying the SP's responsibility for ensuring data integrity and 
|    confidentiality, rather than analyzing the specific encryption 
|    techniques used in the MPLS/GMPLS service. 
|     
|    Encryption algorithms generally come with two parameters: mode such 
|    as Cipher Block Chaining and key length such as AES-192. (This 
|    should not be confused with two other senses in which the word 
|    "mode" is used: IPsec itself can be used in Tunnel Mode or 
|    Transport Mode, and IKE [version 1] uses Main Mode, Aggressive 
|    Mode, or Quick Mode). It should be stressed that IPsec encryption 
|    without an integrity check is a state of sin. 
|     
|    For many of the MPLS/GMPLS provider's network control messages and 
|    some user requirements, cryptographic authentication of messages 
|    without encryption of the contents of the message may provide 
|    appropriate security.  Using IPsec, authentication of messages is 
|    provided by the Authentication Header (AH) or through the use of 
|    the Encapsulating Security Protocol (ESP) with NULL encryption.  
|    Where control messages require integrity but do not use IPsec, 
|    other cryptographic authentication methods are often available.  
|    Message authentication methods currently considered to be secure 
|    are based on hashed message authentication codes (HMAC) [RFC2104] 
|    implemented with a secure hash algorithm such as Secure Hash 
|    Algorithm 1 (SHA-1) [RFC3174]. No attacks against HMAC SHA-1 are 
|    likely to play out in the near future, but it is possible that 
|    people will soon find SHA-1 collisions. Thus, it is important that 
|    mechanisms be designed to be flexible about the choice of hash 
|    functions and message integrity checks. Also, many of these 
|    mechanisms do not include a convenient way to manage and update 
|    keys.  
|     
|    A mechanism to provide a combination of confidentiality, data 
|    origin authentication, and connectionless integrity is the use of 
|    AES in CCM (Counter with CBC-MAC) mode (RFC 4309) [RFC4309], with 
|    an explicit initialization vector (IV), as the IPsec ESP. Recently, 
|    GCM is rapidly replacing CCM as the preferred method: [RFC4103]. 
|     
|    MPLS and GMPLS, which provide differentiated services based on 
|    traffic type, may encounter some conflicts with IPsec encryption of 
|    traffic.  Because encryption hides the content of the packets, it 
|    may not be possible to differentiate the encrypted traffic in the 
|    same manner as unencrypted traffic.  Although DiffServ markings are 
|    copied to the IPsec header and can provide some differentiation, 
|    not all traffic types can be accommodated by this mechanism. Using 
|    IPsec without IKE or IKEv2 (the better choice) is not advisable. 
|    IKEv2 provides IPsec Security Association creation and management, 
|    entity authentication, key agreement, and key update. It works with 
|    a variety of authentication methods including pre-shared keys, 
|    public key certificates, and EAP. If DoS attacks against IKEv2 are 
|    considered an important threat to mitigate, the cookie-based anti-
|    spoofing feature of IKEv2 should be used. IKEv2 has its own set of 
|    cryptographic methods, but any of the default suites specified in 
|    [RFC4308] or [RFC4869] provides more than adequate security.  

Also, does it make sense to think of MPLSsec natively?  What are your
thoughts/tradeoffs for doing this?  I would think there is value/merit
to this idea.

Another one is how does P2MP tunnels affect crypto establishment CE-CE?
What are your thoughts here?

|   5.2.2. Encryption for device configuration and management 
|  
|    For configuration and management of MPLS/GMPLS devices, encryption 
|    and authentication of the management connection at a level 
|    comparable to that provided by IPsec is desirable.   
|     
|    Several methods of transporting MPLS/GMPLS device management 
|    traffic offer security and confidentiality. 
|    -  Secure Shell (SSH) offers protection for TELNET [STD-8] or 
|       terminal-like connections to allow device configuration. 
|    -  SNMPv3 [STD62] provides encrypted and authenticated protection 
|       for SNMP-managed devices. 
|    -  Transport Layer Security (TLS) [RFC4346] and the closely-related 
|       Secure Sockets Layer (SSL) are widely used for securing HTTP-
|       based communication, and thus can provide support for most XML- 
|       and SOAP-based device management approaches. 
|    -  Since 2004, there has been extensive work proceeding in several 
|       organizations (OASIS, W3C, WS-I, and others) on securing device 
|       management traffic within a "Web Services" framework, using a 
|       wide variety of security models, and providing support for 
|       multiple security token formats, multiple trust domains, 
|       multiple signature formats, and multiple encryption 
|       technologies.   
|    -  IPsec provides the services with integrity and confidentiality 
|       at the network layer. With regards to device management, its 
|       current use is primarily focused on in-band management of user-
|       managed IPsec gateway devices. 
|    -  There are recent work in ISMS WG (Integrated Security Model for 
|       SNMP Working Group) to define how to use SSH to secure SNMP, due 
|       to the limited deployment of SNMPv3; and the possibility of 
|       using Kerberos, particularly for interfaces like TELNET, where 
|       client code exists. 

yep.

|   5.2.3.  Security Considerations for MPLS Pseudowires 
|   
|    In addition to IP traffic, MPLS networks may be used to transport 
|    other services such as Ethernet, ATM, Frame Relay, and TDM. This is 
|    done by setting up pseudowires (PWs) that tunnel the native service 
|    through the MPLS core by encapsulating at the edges. The PWE 
|    architecture is defined in [RFC3985].  
|     
|    PW tunnels may be set up using the PWE control protocol based on 
|    LDP [RFC4447], and thus security considerations for LDP will most 
|    likely be applicable to the PWE3 control protocol as well.   
|     
|    PW user packets contain at least one MPLS label (the PW label) and 
|    may contain one or more MPLS tunnel labels.  After the label stack 
|    there is a four-byte control word (which is optional for some PW 
|    types), followed by the native service payload.  It must be 
|    stressed that encapsulation of MPLS PW packets in IP for the 
|    purpose of enabling use of IPsec mechanisms is not a valid option. 
|      
|    The PW client traffic may be secured by use of mechanisms beyond 
|    the scope of this document.  

Why are we only discussing PWE here?  What about VPLS or 2547?  Are the
considerations the same or different?

|    5.2.4.       End-to-End versus Hop-by-Hop Protection Tradeoffs 
|    in MPLS/GMPLS 

THis should really be section 5.2.1, since the notion of where to apply
is the main idea put out by 5.2.

|    In MPLS/GMPLS, cryptographic protection could potentially be 
|    applied to the MPLS/GMPLS traffic at several different places.  
|    This section discusses some of the tradeoffs in implementing 
|    encryption in several different connection topologies among 
|    different devices within a MPLS/GMPLS network. 
|     
|    Cryptographic protection typically involves a pair of devices that 
|    protect the traffic passing between them.  The devices may be 
|    directly connected (over a single "hop"), or intervening devices 
|    may transport the protected traffic between the pair of devices.  
|    The extreme cases involve using protection between every adjacent 
|    pair of devices along a given path (hop-by-hop), or using 
|    protection only between the end devices along a given path (end-to-
|    end).  To keep this discussion within the scope of this document, 
|    the latter ("end-to-end") case considered here is CE-to-CE rather 
|    than fully end-to-end. 
|     
|    Figure 3 depicts a simplified topology showing the Customer Edge 
|    (CE) devices, the Provider Edge (PE) devices, and a variable number 
|    (three are shown) of Provider core (P) devices, which might be 
|    present along the path between two sites in a single VPN operated 
|    by a single service provider (SP). 
|     
|     
|    Site_1---CE---PE---P---P---P---PE---CE---Site_2 
|     
|    Figure 3: Simplified topology traversing through MPLS/GMPLS core. 
|     


|    Within this simplified topology, and assuming that the P devices 
|    are not involved with cryptographic protection, four basic, 
|    feasible configurations exist for protecting connections among the 
|    devices: 
|     
|    1) Site-to-site (CE-to-CE) - Apply confidentiality or integrity 
|    services between the two CE devices, so that traffic will be 
|    protected throughout the SP's network. 
|     
|    2) Provider edge-to-edge (PE-to-PE) - Apply confidentiality or 
|    integrity services between the two PE devices.  Unprotected traffic 
|    is received at one PE from the customer's CE, then it is protected 
|    for transmission through the SP's network to the other PE, and 
|    finally it is decrypted or checked for integrity and sent to the 
|    other CE. 
|     
|    3) Access link (CE-to-PE) - Apply confidentiality or integrity 
|    services between the CE and PE on each side or on only one side. 
|     
|    4) Configurations 2 and 3 above can also be combined, with 
|    confidentiality or integrity running from CE to PE, then PE to PE, 
|    and then PE to CE. 
|     
|    Among the four feasible configurations, key tradeoffs in 
|    considering encryption include: 
|     
|    - Vulnerability to link eavesdropping or tampering - assuming an 
|    attacker can 
|       observe or modify data in transit on the links, would it be 
|    protected by encryption? 
|     
|    - Vulnerability to device compromise - assuming an attacker can get 
|    access to a device (or freely alter its configuration), would the 
|    data be protected? 
|     
|    - Complexity of device configuration and management - given the 
|    number of sites per VPN customer as Nce and the number of PEs 
|    participating in a given VPN as Npe, how many device configurations 
|    need to be created or maintained, and how do those configurations 
|    scale? 
|     
|    - Processing load on devices - how many cryptographic operations 
|    must be performed given N packets? - This raises considerations of 
|    device capacity and perhaps end-to-end delay. 
|     
|    - Ability of the SP to provide enhanced services (QoS, firewall, 
|    intrusion detection, etc.) - Can the SP inspect the data to provide 
|    these services? 
|     
|    These tradeoffs are discussed for each configuration, below: 
|     
|    1) Site-to-site (CE-to-CE) 
|     
|    Link eavesdropping or tampering - protected on all links 
|    Device compromise - vulnerable to CE compromise 
|    Complexity - single administration, responsible for one device per 
|         site (Nce devices), but overall configuration per VPN scales as 
|         Nce**2.  
|         Though the complexity may be reduced: 1) In practice, as Nce 
|         grows, the number of VPNs falls off from being a full clique; 
|         2) If the CEs run an automated key management protocol, then 
|         they should be able to set up and tear down secured VPNs 
|         without any intervention 
|    Processing load - on each of two CEs, each packet is either 
|         cryptographically processed (2P), though the protection may be 
|         "integrity check only" or "integrity check plus encryption." 
|    Enhanced services - severely limited; typically only Diffserv 
|         markings are visible to the SP, allowing some QoS services 
|     
|    2) Provider edge-to-edge (PE-to-PE) 
|     
|    Link eavesdropping or tampering - vulnerable on CE-PE links; 
|         protected on SP's network links 
|    Device compromise - vulnerable to CE or PE compromise 
|    Complexity - single administration, Npe devices to configure.  
|         (Multiple sites may share a PE device so Npe is typically much 
|         less than Nce.)  Scalability of the overall configuration 
|         depends on the PPVPN type: If the cryptographic protection is 
|         separate per VPN context, it scales as Npe**2 per customer VPN.  
|         If it is per-PE, it scales as Npe**2 for all customer VPNs 
|         combined. 
|    Processing load - on each of two PEs, each packet is 
|         cryptographically processed (2P). Note that this 2P is a 
|         different 2P from case (1), because only PEs are in 
|         consideration here. 
|    Enhanced services - full; SP can apply any enhancements based on 
|         detailed view of traffic 
|     
|    3) Access link (CE-to-PE) 
|     
|    Link eavesdropping or tampering - protected on CE-PE link; 
|         vulnerable on SP's network links 
|    Device compromise - vulnerable to CE or PE compromise 
|    Complexity - two administrations (customer and SP) with device 
|         configuration on each side (Nce + Npe devices to configure) but 
|         because there is no mesh the overall configuration scales as 
|         Nce. 
|    Processing load - on each of two CEs, each packet is 
|         cryptographically processed, plus on each of two PEs, each 
|         packet is cryptographically processed (4P) 
|    Enhanced services - full; SP can apply any enhancements based on 
|         detailed view of traffic 
|     
|    4) Combined Access link and PE-to-PE (essentially hop-by-hop) 
|     
|    Link eavesdropping or tampering  - protected on all links 
|    Device compromise - vulnerable to CE or PE compromise 
|    Complexity - two administrations (customer and SP) with device 
|         configuration on each side (Nce + Npe devices to configure).  
|         Scalability of the overall configuration depends on the PPVPN 
|         type: If the cryptographic processing is separate per VPN 
|         context, it scales as Npe**2 per customer VPN.  If it is per-
|         PE, it scales as Npe**2 for all customer VPNs combined. 
|    Processing load - on each of two CEs, each packet is 
|         cryptographically processed, plus on each of two PEs, each 
|         packet is cryptographically processed twice (6P) 
|    Enhanced services - full; SP can apply any enhancements based on 
|         detailed view of traffic 
|     

There appears to be another dimension to cryptographic methods that
meris separate consideration.  The PE-CE crypto can be only for
signalling, to authenticate the devices and ensure correct behaviour, or
can be for dataplance traffic as well.  The CE-CE or PE-PE crypto is
typically for dataplane traffic.  PE-PE could also be used by routing
protocols that setup MPLS signalling, such as for LDP.  I might be
reading this wrong, but this section appears to gloss over this
distinction?

|    Given the tradeoffs discussed above, a few conclusions can be made: 
|     
|    - Configurations 2 and 3 are subsets of 4 that may be appropriate 
|    alternatives to 4 under certain threat models; the remainder of 
|    these conclusions compare 1 (CE-to-CE) versus 4 (combined access 
|    links and PE-to-PE). 
|     
|    - If protection from link eavesdropping or tampering is all that is 
|    important, then configurations 1 and 4 are equivalent. 
|     
|    - If protection from device compromise is most important and the 
|    threat is to the CE devices, both cases are equivalent; if the 
|    threat is to the PE devices, configuration 1 is better. 
|     
|    - If reducing complexity is most important, and the size of the 
|    network is small, configuration 1 is better.  Otherwise 
|    configuration 4 is better because rather than a mesh of CE devices 
|    it requires a smaller mesh of PE devices.  Also, under some PPVPN 
|    approaches the scaling of 4 is further improved by sharing the same 
|    PE-PE mesh across all VPN contexts. The scaling advantage of 4 may 
|    be increased or decreased in any given situation if the CE devices 
|    are simpler to configure than the PE devices, or vice-versa. 
|      
|    - If the overall processing load is a key factor, then 1 is better, 
|    unless the PEs come with a hardware encryption accelerator and the 
|    CEs do not. 
|     
|    - If the availability of enhanced services support from the SP is 
|    most important, then 4 is best. 
|     
|    As a quick overall conclusion, CE-to-CE protection is better 
|    against device compromise, but this comes at the cost of enhanced 
|    services and at the cost of operational complexity due to the 
|    Order(n**2) scaling of a larger mesh.   
|     
|    This analysis of site-to-site vs. hop-by-hop tradeoffs does not 
|    explicitly include cases of multiple providers cooperating to 
|    provide a PPVPN service, public Internet VPN connectivity, or 
|    remote access VPN service, but many of the tradeoffs will be 
|    similar. 
|     
|    In addition to the simplified models, the following should also be 
|    considered:  
|    - There are reasons, perhaps, to protect a specific P-to-P or PE-
|    to-P. 
|    - There may be reasons to do multiple encryptions over certain 
|    segments. One may be using an encrypted wireless link under our 
|    IPsec VPN to access a SSL-secured web site to download encrypted 
|    email attachments: four layers.) 
|    - It may be that, for example, cryptographic integrity checks are 
|    applied end to end, and confidentiality over a shorter span. 
|    - Different cryptographic protection may be required for control 
|    protocols and data traffic. 
|    - Attention needs to be given to how auxiliary traffic is 
|    protected, e.g., the ICMPv6 packets that flow back during PMTU 
|    discovery, among other examples. 
|     
|    5.3. Access Control Techniques 
|     
|    Access control techniques include packet-by-packet or packet-flow-
|    by-packet-flow access control by means of filters and firewalls, as 
|    well as by means of admitting a "session" for a control, signaling, 
|    or management protocol. Enforcement of access control by isolated 
|    infrastructure addresses is discussed in another section of this 
|    document. 
|     
|    In this document, we distinguish between filtering and firewalls 
|    based primarily on the direction of traffic flow.  We define 
|    filtering as being applicable to unidirectional traffic, while a 
|    firewall can analyze and control both sides of a conversation.   
| 
|    The definition has two significant corollaries: 
|    - Routing or traffic flow symmetry: A firewall typically requires 
|    routing symmetry, which is usually enforced by locating a firewall 
|    where the network topology assures that both sides of a 
|    conversation will pass through the firewall.  A filter can operate 
|    upon traffic flowing in one direction, without considering traffic 
|    in the reverse direction. Beware that this concept could result in 
|    a single point of failure. 
|    - Statefulness: Because it receives both sides of a conversation, a 
|    firewall may be able to interpret a significant amount of 
|    information concerning the state of that conversation and use this 
|    information to control access.  A filter can maintain some limited 
|    state information on a unidirectional flow of packets, but cannot 
|    determine the state of the bi-directional conversation as precisely 
|    as a firewall. 
|     

All of the techniques listed in this section appear to be more for
completeness in this document.  They are general techniques applicable
to protecting any network, and should be considered in that context.

The only specificity for MPLS appears to be two:
    1.  You should probably state that Filtering is applied to IPv4/IPv6
    packets.  These are standard techniques that are applied on the
    CE-PE link, or at the edges, not within the MPLS/GMPLS
    infrastructure.
    2.  Inband access to management interfaces on any MPLS/GMPLS only
    infrastructure implies MPLS tunnel termination on those devices
    within the infrastructure.  By definition, tunnels terminate on the
    PE devices, and hence do not permit such management access to P
    devices.  With that, the injunction to apply filtering/firewalling
    to host bound traffic as you haveit below is good.

|    5.3.1.       Filtering 
|  
|    It is relatively common for routers to filter data packets. That 
|    is, routers can look for particular values in certain fields of the 
|    IP or higher level (e.g., TCP or UDP) headers. Packets which 
|    matching the criteria associated with a particular filter may 
|    either be discarded or given special treatment. Today, not only 
|    routers, most end hosts today have filters and every instance of 
|    IPsec is also a filter [RFC4301]. 
|     
|    In discussing filters, it is useful to separate the Filter 
|    Characteristics that may be used to determine whether a packet 
|    matches a filter from the Packet Actions applied to those packets 
|    which matching a particular filter.  
|     
|    o Filter Characteristics 
|     
|    Filter characteristics or rules are used to determine whether a 
|    particular packet or set of packets matches a particular filter.  
|     
|    In many cases filter characteristics may be stateless. A stateless 
|    filter determines whether a particular packet matches a filter 
|    based solely on the filter definition, normal forwarding 
|    information (such as the next hop for a packet), and the contents 
|    of that individual packet. Typically stateless filters may consider 
|    the incoming and outgoing logical or physical interface, 
|    information in the IP header, and information in higher layer 
|    headers such as the TCP or UDP header. Information in the IP header 
|    to be considered may for example include source and destination IP 
|    addresses, Protocol field, Fragment Offset, and TOS field in IPv4, 
|    Next Header, Extension Headers, Flow label, etc. in IPv6. Filters 
|    also may consider fields in the TCP or UDP header such as the Port 
|    fields, the SYN field in the TCP header, as well as ICMP and ICMPv6 
|    type.  
|     
|    Stateful filtering maintains packet-specific state information, to 
|    aid in determining whether a filter has been met. For example, a 
|    device might apply stateless filters to the first fragment of a 
|    fragmented IP packet. If the filter matches, then the data unit ID 
|    may be remembered and other fragments of the same packet may then 
|    be considered to match the same filter. Stateful filtering is more 
|    commonly done in firewalls, although firewall technology may be 
|    added to routers. Data unit ID can also be Fragmentation Extension 
|    Header in IPv6. 
|     
|    o Actions based on Filter Results 
|     
|    If a packet, or a series of packets, matches a specific filter, 
|    then a variety of actions which may be taken based on that match. 
|    Examples of such actions include: 
|     
|      - Discard 
|     
|    In many cases, filters are set to catch certain undesirable 
|    packets. Examples may include packets with forged or invalid source 
|    addresses, packets that are part of a DOS or Distributed DoS (DDOS) 
|    attack, or packets which are trying to access unallowed resources 
|    (such as network management packets from an unauthorized source). 
|    Where such filters are activated, it is common to discard the 
|    packet or set of packets matching the filter silently. The 
|    discarded packets may of course also be counted or logged.  
|     
|      - Set CoS 
|     
|    A filter may be used to set the Class of Service associated with 
|    the packet.  
|     
|      - Count packets or bytes 
|     
|      - Rate Limit 
|     
|    In some cases the set of packets matching a particular filter may 
|    be limited to a specified bandwidth. In this case, packets or bytes 
|    would be counted, and would be forwarded normally up to the 
|    specified limit. Excess packets may be discarded or may be marked 
|    (for example by setting a "discard eligible" bit in the IP ToS 
|    field or the MPLS EXP field).  
|     
|      - Forward and Copy 
|     
|    It is useful in some cases to forward some set of packets normally, 
|    but also to send a copy to a specified other address or interface. 
|    For example, this may be used to implement a lawful intercept 
|    capability or to feed selected packets to an Intrusion Detection 
|    System.  
|     
|    o Other Issues related to Use of Packet Filters 
|     
|    Filtering performance may vary widely according to implementation 
|    and the types and number of rules. Without acceptable performance, 
|    filtering is not useful.  
|         
|    The precise definition of "acceptable" may vary from SP to SP, and 
|    may depend upon the intended use of the filters. For example, for 
|    some uses a filter may be turned on all the time to set CoS, to 
|    prevent an attack, or to mitigate the effect of a possible future 
|    attack. In this case it is likely that the SP will want the filter 
|    to have minimal or no impact on performance. In other cases, a 
|    filter may be turned on only in response to a major attack (such as 
|    a major DDoS attack). In this case a greater performance impact may 
|    be acceptable to some service providers.  
|     
|    A key consideration with the use of packet filters is that they can 
|    provide few options for filtering packets carrying encrypted data.  
|    Because the data itself is not accessible, only packet header 
|    information or other unencrypted fields can be used for filtering. 
|     
|    5.3.2.       Firewalls 
|     
|    Firewalls provide a mechanism for control over traffic passing 
|    between different trusted zones in the MPLS/GMPLS model, or between 
|    a trusted zone and an untrusted zone.  Firewalls typically provide 
|    much more functionality than filters, because they may be able to 
|    apply detailed analysis and logical functions to flows, and not 
|    just to individual packets.  They may offer a variety of complex 
|    services, such as threshold-driven denial-of-service attack 
|    protection, virus scanning, acting as a TCP connection proxy, etc. 
|     
|    As with other access control techniques, the value of firewalls 
|    depends on a clear understanding of the topologies of the 
|    MPLS/GMPLS core network, the user networks, and the threat model.  
|    Their effectiveness depends on a topology with a clearly defined 
|    inside (secure) and outside (not secure). 
|     
|    Firewalls may be applied to help protect MPLS/GMPLS core network 
|    functions from attacks originating from the Internet or from 
|    MPLS/GMPLS user sites, but typically other defensive techniques 
|    will be used for this purpose. 
|     
|    Where firewalls are employed as a service to protect user VPN sites 
|    from the Internet, different VPN users, and even different sites of 
|    a single VPN user, may have varying firewall requirements.  The 
|    overall PPVPN logical and physical topology, along with the 
|    capabilities of the devices implementing the firewall services, has 
|    a significant effect on the feasibility and manageability of such 
|    varied firewall service offerings. 
|     
|    Another consideration with the use of firewalls is that they can 
|    provide few options for handling packets carrying encrypted data.  
|    Because the data itself is not accessible, only packet header 
|    information, other unencrypted fields, or analysis of the flow of 
|    encrypted packets can be used for making decisions on accepting or 
|    rejecting encrypted traffic. 
|     
|    Two approaches are to move the firewall outside of the encrypted 
|    part of the path or to register and pre-approve the encrypted 
|    session with the firewall.  
|     
|    Handling DoS attacks has become increasingly important. Useful 
|    guidelines include the following: 
|    1. Perform ingress filtering everywhere. Upstream prevention is 
|    better. 
|    2. Be able to filter DoS attack packets at line speed. 
|    3. Do not allow oneself to amplify attacks. 
|    4. Continue processing legitimate traffic. Over provide for heavy 
|    loads. Use diverse locations, technologies, etc. 
|     
|    5.3.3.       Access Control to management interfaces 
|     
|    Most of the security issues related to management interfaces can be 
|    addressed through the use of authentication techniques as described 
|    in the section on authentication.  However, additional security may 
|    be provided by controlling access to management interfaces in other 
|    ways. 
|     
|    The Optical Internetworking Forum has done good work on protecting 
|    such interfaces with TLS, SSH, Kerberos, IPsec, WSS, etc. See OIF-
|    SMI-01.0 "Security for Management Interfaces to Network Elements" 
|    [OIF-SMI-01.0], and "Addendum to the Security for Management 
|    Interfaces to Network Elements" [OIF-SMI-02.1]. See also the work 
|    in the ISMS WG. 
|     
|    Management interfaces, especially console ports on MPLS/GMPLS 
|    devices, may be configured so they are only accessible out-of-band, 
|    through a system which is physically or logically separated from 
|    the rest of the MPLS/GMPLS infrastructure. 
|     
|    Where management interfaces are accessible in-band within the 
|    MPLS/GMPLS domain, filtering or firewalling techniques can be used 
|    to restrict unauthorized in-band traffic from having access to 
|    management interfaces.  Depending on device capabilities, these 
|    filtering or firewalling techniques can be configured either on 
|    other devices through which the traffic might pass, or on the 
|    individual MPLS/GMPLS devices themselves. 
|     
|    5.4. Use of Isolated Infrastructure 
|  
|    One way to protect the infrastructure used for support of 
|    MPLS/GMPLS is to separate the resources for support of MPLS/GMPLS 
|    services from the resources used for other purposes (such as 
|    support of Internet services). In some cases this may use 
|    physically separate equipment for VPN services, or even a 
|    physically separate network.  
|     
|    For example, PE-based L3 VPNs may be run on a separate backbone not 
|    connected to the Internet, or may make use of separate edge routers 
|    from those used to support Internet service. Private IP addresses 
|    (local to the provider and non-routable over the Internet) are 
|    sometimes used to provide additional separation. 
|     
|     
|    5.5. Use of Aggregated Infrastructure 
|     
|    In general, it is not feasible to use a completely separate set of 
|    resources for support of each service. In fact, one of the main 
|    reasons for MPLS/GMPLS enabled services is to allow sharing of 
|    resources between multiple users, including multiple VPNs, etc. 
|    Thus, even if certain services make use of a separate network from 
|    Internet services, nonetheless there will still be multiple 
|    MPLS/GMPLS users sharing the same network resources. In some cases 
|    MPLS/GMPLS services will share the use of network resources with 
|    Internet services or other services.  
|     
|    It is therefore important for MPLS/GMPLS services to provide 
|    protection between resources used by different parties. Thus a 
|    well-behaved MPLS/GMPLS user should be protected from possible 
|    misbehavior by other users. This requires that limits are placed on 
|    the amount of resources used by any one VPN. For example, both 
|    control traffic and user data traffic may be rate limited. In some 
|    cases or in some parts of the network where a sufficiently large 
|    number of queues are available, each VPN (and optionally each VPN 
|    and CoS within the VPN) may make use of a separate queue. Control-
|    plane resources such as link bandwidth as well as CPU and memory 
|    resources may be reserved on a per-VPN basis.  
|     
|    The techniques used to provide resource protection between multiple 
|    users served by the same infrastructure can also be used to protect 
|    MPLS/GMPLS networks and services from Internet services.  
|     
|    In general, the use of aggregated infrastructure allows the service 
|    provider to benefit from stochastic multiplexing of multiple bursty 
|    flows, and also may in some cases thwart traffic pattern analysis 
|    by combining the data from multiple users.  
|     
|    5.6. Service Provider Quality Control Processes 
|     
|    Deployment of provider-provisioned VPN services in general requires 
|    a relatively large amount of configuration by the SP. For example, 
|    the SP needs to configure which VPN each site belongs to, as well 
|    as QoS and SLA guarantees. This large amount of required 
|    configuration leads to the possibility of misconfiguration.  
|     
|    It is important for the SP to have operational processes in place 
|    to reduce the potential impact of misconfiguration. CE-to-CE 
|    authentication may also be used to detect misconfiguration when it 
|    occurs.  
|     
|    5.7. Deployment of Testable MPLS/GMPLS Service.   
|     
|    This refers to solutions that can be readily tested to make sure 
|    they are configured correctly.  For example, for a point-point 
|    connection, checking that the intended connectivity is working 
|    pretty much ensures that there is not connectivity to some 
|    unintended site. 
|     
|  
| 6. Monitoring, Detection, and Reporting of Security Attacks 
|     
|    MPLS/GMPLS network and service may be subject to attacks from a 
|    variety of security threats.  Many threats are described in another 
|    part of this document.  Many of the defensive techniques described 
|    in this document and elsewhere provide significant levels of 
|    protection from a variety of threats.  However, in addition to 
|    silently employing defensive techniques to protect against attacks, 
|    MPLS/GMPLS services can also add value for both providers and 
|    customers by implementing security monitoring systems to detect and 
|    report on any security attacks which occur, regardless of whether 
|    the attacks are effective. 
|     
|    Attackers often begin by probing and analyzing defenses, so systems 
|    that can detect and properly report these early stages of attacks 
|    can provide significant benefits. 
|     
|    Information concerning attack incidents, especially if available 
|    quickly, can be useful in defending against further attacks.  It 
|    can be used to help identify attackers or their specific targets at 
|    an early stage.  This knowledge about attackers and targets can be 
|    used to strengthen defenses against specific attacks or attackers, 
|    or improve the defensive services for specific targets on an as-
|    needed basis.  Information collected on attacks may also be useful 
|    in identifying and developing defenses against novel attack types. 
|     
|    Monitoring systems used to detect security attacks in MPLS/GMPLS 
|    typically operate by collecting information from the Provider Edge 
|    (PE), Customer Edge (CE), and/or Provider backbone (P) devices.  
|    Security monitoring systems should have the ability to actively 
|    retrieve information from devices (e.g., SNMP get) or to passively 
|    receive reports from devices (e.g., SNMP notifications).  The 
|    specific information exchanged depends on the capabilities of the 
|    devices and on the type of VPN technology.  Particular care should 
|    be given to securing the communications channel between the 
|    monitoring systems and the MPLS/GMPLS devices. Syslog WG is 
|    specifying "Logging Capabilities for IP Network Infrastructure". 
|    (The specific references will be made only if the draft(s) became 
|    RFC before this draft.) 

It used to be that you could refer to drafts as "Work in Progress".  Is
that not allowed any longer?

|    The CE, PE, and P devices should employ efficient methods to 
|    acquire and communicate the information needed by the security 
|    monitoring systems.  It is important that the communication method 
|    between MPLS/GMPLS devices and security monitoring systems be 
|    designed so that it will not disrupt network operations.  As an 
|    example, multiple attack events may be reported through a single 
|    message, rather than allowing each attack event to trigger a 
|    separate message, which might result in a flood of messages, 
|    essentially becoming a denial-of-service attack against the 
|    monitoring system or the network. 
|     
|    The mechanisms for reporting security attacks should be flexible 
|    enough to meet the needs of MPLS/GMPLS service providers, 
|    MPLS/GMPLS customers, and regulatory agencies, if applicable.  The 
|    specific reports should depend on the capabilities of the devices, 
|    the security monitoring system, the type of VPN, and the service 
|    level agreements between the provider and customer. 
| 
| 7. Service Provider General Security Requirements 
|     
|    This section covers security requirements the provider may have for 
|    securing its MPLS/GMPLS network infrastructure including LDP and 
|    RSVP-TE specific requirements. 
|     
|    The MPLS/GMPLS service provider's requirements defined here are for 
|    the MPLS/GMPLS core in the reference model.  The core network can 
|    be implemented with different types of network technologies, and 
|    each core network may use different technologies to provide the 
|    various services to users with different levels of offered 
|    security. Therefore, a MPLS/GMPLS service provider may fulfill any 
|    number of the security requirements listed in this section. This 
|    document does not state that a MPLS/GMPLS network must fulfill all 
|    of these requirements to be secure.   
|     
|    These requirements are focused on: 1) how to protect the MPLS/GMPLS 
|    core from various attacks outside the core including network users, 
|    both accidentally and maliciously, 2) how to protect the end users. 
|      
|    7.1. Protection within the Core Network 
|     
|    7.1.1.       Control Plane Protection - General 
|     
|    - Protocol authentication within the core:  
|     
|    The network infrastructure must support mechanisms for 
|    authentication of the control plane. If MPLS/GMPLS core is used, 
|    LDP sessions may be authenticated by use TCP MD5, in addition, IGP 
|    and BGP authentication should also be considered. For a core 
|    providing Layer 2 services, PE-to-PE authentication may also be 
|    performed via IPsec. See the above discussion of protocol security 
|    services: authentication, integrity (with replay detection), 
|    confidentiality. Protocols need to provide a complete set of 
|    security services from which the SP can choose. Also, the hard part 
|    is key management. 
|     
|    With the cost of authentication coming down rapidly, the 
|    application of control plane authentication may not increase the 
|    cost of implementation for providers significantly, and will help 
|    to improve the security of the core. If the core is dedicated to 
|    MPLS/GMPLS enabled services and without any interconnects to third 
|    parties then this may reduce the requirement for authentication of 
|    the core control plane. 
|     
|  
|    - Infrastructure Hiding 
|     
|    Here we discuss means to hide the provider's infrastructure nodes.  
|     
|    A MPLS/GMPLS provider may make its infrastructure routers (P and PE 
|    routers) unreachable from outside users and unauthorized internal 
|    users. For example, separate address space may be used for the 
|    infrastructure loopbacks.  
|     
|    Normal TTL propagation may be altered to make the backbone look 
|    like one hop from the outside, but caution needs to be taken for 
|    loop prevention. This prevents the backbone addresses from being 
|    exposed through trace route; however this must also be assessed 
|    against operational requirements for end-to-end fault tracing.  
|     
|    An Internet backbone core may be re-engineered to make Internet 
|    routing an edge function, for example, by using MPLS label 
|    switching for all traffic within the core and possibly make the 
|    Internet a VPN within the PPVPN core itself. This helps to detach 
|    Internet access from PPVPN services. 
|     
|    Separating control plane, data plane, and management plane 
|    functionality in hardware and software may be implemented on the PE 
|    devices to improve security. This may help to limit the problems 
|    when attacked in one particular area, and may allow each plane to 
|    implement additional security measures separately. 
|     
|    PEs are often more vulnerable to attack than P routers, because PEs 
|    cannot be made unreachable from outside users by their very nature. 
|    Access to core trunk resources can be controlled on a per user 
|    basis by using of inbound rate-limiting or traffic shaping; this 
|    can be further enhanced on a per Class of Service basis (see 
|    Section 8.2.3)  
|  
|    In the PE, using separate routing processes for different services, 
|    for example, Internet and PPVPN service, may help to improve the 
|    PPVPN security and better protect VPN customers. Furthermore, if 
|    resources, such as CPU and Memory, can be further separated based 
|    on applications, or even individual VPNs, it may help to provide 
|    improved security and reliability to individual VPN customers. 
|     
|    7.1.2.       Control plane protection with RSVP-TE 
|     
|    - RSVP Security Tools 
|     
|    Isolation of the trusted domain is an important security mechanism 
|    for RSVP, to ensure that an untrusted element cannot access a 
|    router of the trusted domain.  However, isolation is limited by the 
|    need to allow ASBR-ASBR communication for inter-AS LSPs.  Isolation 
|    mechanisms might also be bypassed by Router Alert IP packets. A 
|    solution could consists of disabling the RSVP router alert mode and 
|    dropping all IP packets with the router alert option, or also to 
|    drop all incoming IP packets on an interface with port 46, which 
|    requires an access-list at the IP port level) or spoofed IP packets 
|    if anti-spoofing is not otherwise activated. 
|     
|    RSVP security can be strengthened by deactivating RSVP on 
|    interfaces with neighbors who are not authorized to use RSVP, to 
|    protect against adjacent CE-PE attacks. However, this does not 
|    really protect against DoS attacks or attacks on non-adjacent 
|    routers.  It has been demonstrated that substantial CPU resources 
|    are consumed simply by processing received RSVP packets, even if 
|    the RSVP process is deactivated for the specific interface on which 
|    the RSVP packets are received.  

This does not follow.  Is the implication of the above that the very act
of bringing an RSVP packet from the interface, through the dataplane to
the control plane and then dropping the RSVP packet at the control plane
because RSVP is disabled on the interface, is it this very act itself
CPU intensive?

|    RSVP neighbor filtering at the protocol level, to restrict the set 
|    of neighbors that can send RSVP messages to a given router, 
|    protects against non-adjacent attacks.  However, this does not 
|    protect against DoS attacks and does not effectively protect 
|    against spoofing of the source address of RSVP packets, if the 
|    filter relies on the neighbor's address within the RSVP message.   
|     
|    RSVP neighbor filtering at the data plane level (with an access 
|    list to accept IP packets with port 46, only for specific 
|    neighbors). 

The above sentence is unfinished.

|                This requires Router Alert mode to be deactivated and 
|    does not protect against spoofing. 
|     
|    - Authentication for RSVP messages 
|     
|    One of the most powerful tools for protection against RSVP-based 
|    attacks is the use of authentication for RSVP messages, based on a 
|    secure message hash using a key shared by RSVP neighbors.  This 
|    protects against LSP creation attacks, at the expense of consuming 
|    significant CPU resources for digest computation.  In addition, if 
|    the neighboring RSVP speaker is compromised, it could be used to 
|    launch attacks using authenticated RSVP messages. These methods, 
|    and certain other aspects of RSVP security, are explained in detail 
|    in RFC 4230 [RFC4230]. Key management must be implemented. Logging 
|    and auditing as well as multiple layers of crypto protection can 
|    help here. IPsec can also be used. 
|     
|    Another valuable tool is RSVP message pacing, to limit the number 
|    of RSVP messages sent to a given neighbor during a given period.  
|    This allows blocking DoS attack propagation. 
|     
|    The trick with DoS is to let the good packet through and keep 
|    operating. Rate limiting by itself needs to be selective do this. 
|     
|    - limit the impact of an attack on control plane resources 
|  
|    To ensure continued effective operation of the MPLS router even in 
|    the case of an attack that bypasses packet filtering mechanisms 
|    such as Access Control Lists in the data plane, it is important 
|    that routers have some mechanisms to limit the impact of the 
|    attack.  There should be a mechanism to rate limit the amount of 
|    control plane traffic addressed to the router, per interface.  This 
|    should be configurable on a per-protocol basis, (and, ideally, on a 
|    per-sender basis) to avoid letting an attacked protocol or a given 
|    sender blocking all communications.  This requires the ability to 
|    filter and limit the rate of incoming messages of particular 
|    protocols, such as RSVP (filtering at the IP protocol level), and 
|    particular senders.  In addition, there should be a mechanism to 
|    limit CPU and memory capacity allocated to RSVP, so as to protect 
|    other control plane elements.  To limit the memory allocation, it 
|    will probably be necessary to limit the number of LSPs that can be 
|    set up. 
|     
|  
|    7.1.3.       Control plane protection with LDP 
|  
|    The approaches to protect MPLS routers against LDP-based attacks 
|    are similar to those for RSVP, including isolation, protocol 
|    deactivation on specific interfaces, filtering of LDP neighbors at 
|    the protocol level, filtering of LDP neighbors at the data plane 
|    level (access list that filter the TCP & UDP LDP ports), 
|    authentication with message digest, rate limiting of LDP messages 
|    per protocol per sender and limiting all resources allocated to 
|    LDP-related tasks. 
|     
|        
|    7.1.4.       Data Plane Protection 
|     
|    IPsec can provide authentication, integrity, confidentiality, and 
|    replay detection for provider or user data. It also has an 
|    associated key management protocol. 
|     
|    In today's MPLS/GMPLS, ATM, or Frame Relay networks, encryption is 
|    not provided as a basic feature. Mechanisms described in section 5 
|    can be used to secure the MPLS data plane traffic carried over MPLS 
|    core. Both the Frame Relay Forum and the ATM Forum standardized 
|    cryptographic security services in the late 1990s, but these 
|    standards are not widely implemented. 
|     
|    7.2. Protection on the User Access Link 
|    Peer or neighbor protocol authentication may be used to enhance 
|    security. For example, BGP MD5 authentication may be used to 
|    enhance security on PE-CE links using eBGP. In the case of Inter-
|    provider connection, cryptographic protection mechanisms between 
|    ASes, such as IPsec, may be used. 
|     
|    If multiple services are provided on the same PE platform, 
|    different WAN link layer address spaces may be used for different 
|    services (e.g., VPN and non-VPN) to enhance isolation. 
|     
|    Firewall and Filtering: access control mechanisms can be used to 
|    filter any packets destined for the service provider's 
|    infrastructure prefix or eliminate routes identified as 
|    illegitimate. 
|     
|    Rate limiting may be applied to the user interface/logical 
|    interfaces against DDoS bandwidth attack. This is helpful when the 
|    PE device is supporting both multi-services, especially VPN and 
|    Internet Services, on the same physical interfaces through 
|    different logical interfaces. 
|  
|    7.2.1.       Link Authentication 
|     
|    Authentication can be used to validate site access to the network 
|    via fixed or logical connections, e.g. L2TP, IPsec, respectively. 
|    If the user wishes to hold the authentication credentials for 
|    access, then provider solutions require the flexibility for either 
|    direct authentication by the PE itself or interaction with a 
|    customer authentication server. Mechanisms are required in the 
|    latter case to ensure that the interaction between the PE and the 
|    customer authentication server is appropriately secured. 
|      
|    7.2.2.       Access Routing Control 
|     
|    Routing protocol level e.g., RIP, OSPF, or BGP, may be used to 
|    provide control access between a CE and PE. Per neighbor and per 
|    VPN routing policies may be established to enhance security and 
|    reduce the impact of a malicious or non-malicious attack on the PE; 
|    the following mechanisms, in particular, should be considered: 
|     - Limiting the number of prefixes that may be advertised on 
|        a per access basis into the PE. Appropriate action may be 
|        taken should a limit be exceeded, e.g., the PE shutting 
|        down the peer session to the CE  
|     - Applying route dampening at the PE on received routing 
|        updates 
|     - Definition of a per VPN prefix limit after which 
|        additional prefixes will not be added to the VPN routing 
|        table. 
|     
|    In the case of Inter-provider connection, access protection, link 
|    authentication, and routing policies as described above may be 
|    applied. Both inbound and outbound firewall or filtering mechanism 
|    between ASes may be applied. Proper security procedures must be 
|    implemented in Inter-provider interconnection to protect the 
|    providers' network infrastructure and their customers. This may be 
|    custom designed for each Inter-Provider peering connection, and 
|    must be agreed upon by both providers. 

Why are you discussing Inter-provider connection here?

|  
|    7.2.3.       Access QoS 
|     
|    MPLS/GMPLS providers offering QoS-enabled services require 
|    mechanisms to ensure that individual accesses are validated against 
|    their subscribed QOS profile and as such gain access to core 
|    resources that match their service profile.  Mechanisms such as per 
|    Class of Service rate limiting or traffic shaping on ingress to the 
|    MPLS/GMPLS core are one option for providing this level of control.  
|    Such mechanisms may require the per Class of Service profile to be 
|    enforced either by marking, or remarking or discard of traffic 
|    outside of the profile. 
|     
|    7.2.4.       Customer service monitoring tools  
|     
|    End users requiring specific statistics on the core, e.g., routing 
|    table, interface status, or QoS statistics, requirements for 
|    mechanisms at the PE both to validate the incoming user and limit 
|    the views available to that particular user.  Mechanisms should 
|    also be considered to ensure that such access cannot be used a 
|    means of a DoS attack (either malicious or accidental) on the PE 
|    itself. This could be accomplished through either separation of 
|    these resources within the PE itself or via the capability to rate-
|    limit on a per physical or logical connection basis such traffic. 
|  
|     
|    7.3. General User Requirements for MPLS/GMPLS Providers 
|     
|    MPLS/GMPLS providers must support end users' security requirements. 
|    Depending on the technologies used, these requirements may include: 
|  
|    - User control plane separation - routing isolation when 
|       applicable, for example, in the case of MPLS VPNs. 

What does this mean?

|    - Protection against intrusion, DoS attacks and spoofing 

Other than attempts to not amplify DoS attacks, most of this draft has
not focused on user considerations for DoS.  So what would you suggest 
are some criteria for protection?

|    - Access Authentication 
|    - Techniques highlighted through this document that identify 
|       methodologies for the protection of resources and the 
|       MPLS/GMPLS infrastructure.  

Also, if e2e crypto is a user's desire, PPVPN configured CE-CE
encryption.

|    Hardware or software errors in equipment leading to breaches in 
|    security are not within the scope of this document. 
|  
|  
| 8. Inter-provider Security Requirements 
|  
|    This section discusses security capabilities that are important at 
|    the MPLS/GMPLS Inter-provider connections and at devices (including 
|    ASBR routers) supporting these connections. The security 
|    capabilities stated in this section should be considered as 
|    complementary to security considerations addressed in individual 
|    protocol specifications or security frameworks. 
|     
|    Security vulnerabilities and exposures may be propagated across 
|    multiple networks because of security vulnerabilities arising in 
|    one peer's network. Threats to security originate from accidental, 
|    administrative, and intentional sources. Intentional threats 
|    include events such as spoofing and Denial of Service (DoS) 
|    attacks. 
|    The level and nature of threats, as well as security and 
|    availability requirements, may vary over time and from network to 
|    network. This section therefore discusses capabilities that need to 
|    be available in equipment deployed for support of the MPLS 
|    InterCarrier Interconnect (MPLS-ICI). Whether any particular 
|    capability is used in any one specific instance of the ICI is up to 
|    the service providers managing the PE equipment offering/using the 
|    ICI services.  
|     
|    8.1. Control Plane Protection 
|     
|    This section discusses capabilities for control plane protection, 
|    including protection of routing, signaling, and OAM capabilities.   
|  
|    8.1.1.       Authentication of Signaling Sessions 
|  
|    Authentication is needed for signaling sessions (i.e., BGP, LDP and 
|    RSVP-TE) and routing sessions (e.g., BGP) as well as OAM sessions 
|    across domain boundaries. Equipment must be able to support 
|    exchange of all protocol messages over a single IPsec tunnel, with 
|    NULL encryption and authentication, between the peering ASBRs. 
|    Support for TCP MD5 authentication for LDP and BGP and for RSVP-TE 
|    authentication must also be provided. Manual keying of IPsec should 
|    not be used. IKEv2 with pre-shared secrets or public key methods 
|    should be used. Replay detection should be used. 
|  
|    Mechanisms to authenticate and validate a dynamic setup request 
|    MUST be available. For instance, if dynamic signaling of a TE-LSP 
|    or PW is crossing a domain boundary, there must be a way to detect 
|    whether the LSP source is who it claims to be and that he is 
|    allowed to connect to the destination. 
|     
|    MD5 authentication support for all TCP-based protocols within the 
|    scope of the MPLS-ICI (i.e., LDP signaling and BGP routing) and MD5 
|    authentication for the RSVP-TE Integrity Object MUST be provided to 
|    interoperate with current practices. 
|    Equipment SHOULD be able to support exchange of all signaling and 
|    routing (LDP, RSVP-TE, and BGP) protocol messages over a single 
|    IPSec security association pair in tunnel or transport mode with 
|    authentication but with NULL encryption, between the peering ASBRs. 
|    IPSec, if supported, must be supported with HMAC-MD5 and optionally 
|    SHA-1.  It is expected that authentication algorithms will evolve 
|    over time and support can be updated as needed. 
|     
|    OAM Operations across the MPLS-ICI could also be the source of 
|    security threats on the provider infrastructure as well as the 
|    service offered over the MPLS-ICI. A large volume of OAM messages 
|    could overwhelm the processing capabilities of an ASBR if the ASBR 
|    is not properly protected. Maliciously generated OAM messages could 
|    also be used to bring down an otherwise healthy service (e.g., MPLS 
|    Pseudo Wire), and therefore affect service security. MPLS-ping does 
|    not support authentication today, and that support should be 
|    subject for future considerations. Bidirectional Forwarding 
|    Detection (BFD), however, does have support for carrying an 
|    authentication object. It also supports Time-To-Live (TTL) 
|    processing as an anti-replay measure. Implementations conformant 
|    with this MPLS-ICI should support BFD authentication using MD5 and 
|    must support the procedures for TTL processing.  
|     
|    8.1.2.       Protection against DoS attacks in the Control 
|    Plane 
|  
|    Implementation must have the ability to prevent signaling and 
|    routing DoS attacks on the control plane per interface and 
|    provider. Such prevention may be provided by rate-limiting 
|    signaling and routing messages that can be sent by a peer provider 
|    according to a traffic profile and by guarding against malformed 
|    packets. 
|     
|    Equipment MUST provide the ability to filter signaling, routing, 
|    and OAM packets destined for the device, and MUST provide the 
|    ability to rate limit such packets. Packet filters SHOULD be 
|    capable of being separately applied per interface, and SHOULD have 
|    minimal or no performance impact. For example, this allows an 
|    operator to filter or rate-limit signaling, routing, and OAM 
|    messages that can be sent by a peer provider and limit such traffic 
|    to a given profile.  
|      
|    During a control plane DoS attack against an ASBR, the router 
|    SHOULD guarantee sufficient resources to allow network operators to 
|    execute network management commands to take corrective action, such 
|    as turning on additional filters or disconnecting an interface 
|    under attack. DoS attacks on the control plane SHOULD NOT adversely 
|    affect data plane performance.  
|    Equipment running BGP MUST support the ability to limit the number 
|    of BGP routes received from any particular peer. Furthermore, in 
|    the case of IPVPN, a router MUST be able to limit the number of 
|    routes learned from a BGP peer per IPVPN. In the case that a device 
|    has multiple BGP peers, it SHOULD be possible for the limit to vary 
|    between peers.  
|     
|    8.1.3.       Protection against Malformed Packets 
|  
|    Equipment SHOULD be robust in the presence of malformed protocol 
|    packets. For example, malformed routing, signaling, and OAM packets 
|    should be treated in accordance to the relevant protocol 
|    specification.  
|     
|    8.1.4.       Ability to Enable/Disable Specific Protocols 
|  
|    Ability to drop any signaling or routing protocol messages when 
|    these messages are to be processed by the ASBR but the 
|    corresponding protocol is not enabled on that interface.  
|     
|    Equipment must allow an administrator to enable or disable a 
|    protocol (default protocol is disabled unless administratively 
|    enable) on an interface basis. 
|     
|    Equipment MUST be able to drop any signaling or routing protocol 
|    messages when these messages are to be processed by the ASBR but 
|    the corresponding protocol is not enabled on that interface. This 
|    dropping SHOULD NOT adversely affect data plane or control plane 
|    performance.  
|     
|    8.1.5.       Protection Against Incorrect Cross Connection 
|  
|    The capability of detecting and locating faults in a LSP cross-
|    connect MUST be provided. Such faults may cause security violations 
|    as they result in directing traffic to the wrong destinations. This 
|    capability may rely on OAM functions. Equipment MUST support MPLS 
|    LSP ping [RFC4379]. This MAY be used to verify end to end 
|    connectivity for the LSP (e.g., PW, TE Tunnel, VPN LSP, etc.), and 
|    to verify PE-to-PE connectivity for L3 VPN services.  
|     
|    When routing information is advertised from one domain to the 
|    other, operators must be able to guard against situations that 
|    result in traffic hijacking, black-holing, resource stealing (e.g., 
|    number of routes), etc. For instance, in the IPVPN case, an 
|    operator must be able to block routes based on associated route 
|    target attributes. In addition, mechanisms must exist to verify 
|    whether a route advertised by a peer for a given VPN is actually a 
|    valid route and whether the VPN has a site attached or reachable 
|    through that domain. 
|  
|    Equipment (ASBRs and Route Reflectors (RRs)) supporting operation 
|    of BGP MUST be able to restrict which Route Target attributes are 
|    sent to and accepted from a BGP peer across an ICI. Equipment 
|    (ASBRs, RRs) SHOULD also be able to inform the peer regarding which 
|    Route Target attributes it will accept from a peer, because sending 
|    an incorrect Route Target can result in incorrect cross-connection 
|    of VPNs. Also, sending inappropriate route targets to a peer may 
|    disclose confidential information.  
|     
|    8.1.6.       Protection Against Spoofed Updates and Route 
|    Advertisements 
|  
|    Equipment MUST support route filtering of routes received via a BGP 
|    peer sessions by applying policies that include one or more the 
|    following: AS path, BGP next hop, standard community or extended 
|    community. 
|     
|    8.1.7.       Protection of Confidential Information 
|  
|    Ability to identify and prohibit messages that can reveal 
|    confidential information about network operation (e.g., performance 
|    OAM messages or MPLS-ping messages) is required. Service Providers 
|    must have the flexibility of handling these messages at the ASBR.  
|     
|    Equipment SHOULD provide the ability to identify and restrict where 
|    it sends messages or that can reveal confidential information about 
|    network operation (e.g., performance OAM messages, LSP Traceroute 
|    messages). Service Providers must have the flexibility of handling 
|    these messages at the ASBR. For example, equipment supporting LSP 
|    Traceroute MAY limit to which addresses replies can be sent.  
|    Note: This capability should be used with care. For example, if a 
|    service provider chooses to prohibit the exchange of LSP ping 
|    messages at the ICI, it may make it more difficult to debug 
|    incorrect cross-connection of LSPs or other problems.  
|    A provider may decide to progress these messages if they are 
|    incoming from a trusted provider and are targeted to specific 
|    agreed-on addresses. Another provider may decide to traffic police, 
|    reject, or apply policies to these messages. Solutions must enable 
|    providers to control the information that is relayed to another 
|    provider about the path that a LSP takes. For example, in RSVP-TE 
|    record route object or MPLS-ping trace, a provider must be able to 
|    control the information contained in corresponding messages when 
|    sent to another provider. 
|     
|    8.1.8.       Protection Against over-provisioned number of 
|    RSVP-TE LSPs and bandwidth reservation 
|     
|    In addition to the control plane protection mechanisms listed in 
|    the previous section on Control plane protection with RSVP-TE, the 
|    ASBR must be able both to limit the number of LSPs that can be set 
|    up by other domains and to limit the amount of bandwidth that can 
|    be reserved. A provider's ASBR may deny a LSP set up request or a 
|    bandwidth reservation request sent by another provider's whose the 
|    limits have been reached. 
|     
|    8.2. Data Plane Protection 
|     
|    8.2.1.       Protection against DoS in the Data Plane 
|     This is described earlier in this document. 
|  
|    8.2.2.       Protection against Label Spoofing 
|  
|    Verification that a label received across an interconnect was 
|    actually assigned to the provider across the interconnect. If the 
|    label was not assigned to the provider, the packet MUST be dropped. 
|     
|    Equipment MUST be able to verify that a label received across an 
|    interconnect was actually assigned to a LSP arriving from the 
|    provider across that interconnect. If the label was not assigned to 
|    a LSP which arrives at this router from the correct neighboring 
|    provider, the packet MUST be dropped.  This verification can be 
|    applied to the top label only. The top label is the received top 
|    label and every label that is exposed by label popping to be used 
|    for forwarding decisions.  

should nominally check the label stack depth.  By this I mean, if a
spoofed packet arrives with a valid label, but only a 1-label stack, nd
we exect at least 2 or more labels, we should drop.

|    Equipment MUST provide the capability of dropping MPLS-labeled 
|    packets if all labels in the stack are not processed.  This lets 
|    carriers guarantee that every label that enters its domain from 
|    another carrier was actually assigned to that carrier.  
|  
|    The following requirements are not directly reflected in this 
|    document but must be used as guidance for addressing further work. 
|     
|    Solutions MUST NOT force operators to reveal reachability 
|    information to routers within their domains. <note: It is believed 
|    that this requirement is met via other requirements specified in 
|    this section plus the normal operation of IP routing, which does 
|    not reveal individual hosts.> 
|     
|    Mechanisms to authenticate and validate a dynamic setup request 
|    MUST be available. For instance, if dynamic signaling of a TE-LSP 
|    or PW is crossing a domain boundary, there must be a way to detect 
|    whether the LSP source is who it claims to be and that he is 
|    allowed to connect to the destination. 
|     
|    8.2.3.       Protection using ingress traffic policing and 
|    enforcement 
|     
|    The following simple diagram illustrates a potential security issue 
|    on the data plane issue across a MPLS interconnect: 
|     
|    SP2 - ASBR2 - labeled path - ASBR1 - P1 - SP1's PSN - P2 - PE1 
|    |         |                   |                          | 
|    |<  AS2  >|<MPLS interconnect>|<             AS1              >| 
|     
|    Traffic flow direction is from SP2 to SP1 
|     
|    Usually, the transit label used by ASBR2 is allocated by ASBR1,  
|    which in turn advertises it to ASB2 (downstream unsolicited or on-
|    demand), and this label is used for a service context (VPN label, 
|    PW VC label, etc.), and this LSP is normally terminated at a 
|    forwarding table belonging to the service instance on PE (PE1) in 
|    SP1. 
|     
|    In the example above, ASBR1 would not know whether the label of an 
|    incoming packet from ASBR2 over the interconnect is a VPN label or 
|    PSN label for AS1. So it is possible (though rare) that ASBR2 can 
|    be accidentally or intentionally configured such that the incoming 
|    label could match a PSN label (e.g., LDP) in AS1. Then, this LSP 
|    would end up on the global plane of an infrastructure router (P or 
|    PE1), and this could invite a unidirectional attack on that P or 
|    PE1 where the LSP terminates. 
|  
|    To mitigate this threat, implementations SHOULD be able to do a 
|    forwarding path look-up for the label on an incoming packet from an 
|    interconnect in a Label Forwarding Information Base (LFIB) space 
|    that is only intended for its own service context or provide a 
|    mechanism on the data plane that would ensure the incoming labels 
|    are what ASBR1 has allocated and advertised. 
|     
|    A similar concept has been proposed in "Requirements for Multi-
|    Segment Pseudowire Emulation Edge-to-Edge (PWE3)" [PW-REQ]. 
|     
| 9. Summary of MPLS and GMPLS Security  
|     
|    The following summary provides a quick check list of MPLS and GMPLS 
|    security threats, defense techniques, and the best practice guide 
|    outlines for MPLS and GMPLS deployment.  
|     
|    9.1. MPLS and GMPLS Specific Security Threats 
|     
| 9.1.1. Control plane attacks 
|     
|    Types of attacks on the control plane: 
|      - Unauthorized LSP creation 
|      - LSP message interception 

    LSP message corruption
    LSP message deletion
    Replay
    DOS through signalling overload
    Protocol specific techniques such as...

|    Attacks against RSVP-TE: DoS attack with setting up 
|    unauthorized LSP and/or LSP messages. 
|     
|    Attacks against LDP: DoS attack with storms of LDP Hello 
|    messages or LDP TCP Syn messages. 
|     
|    Attacks may be launched from external or internal sources, or 
|    through SP management systems. 
|     
|    Attacks may be targeted to the SP routing protocols or 
|    infrastructure elements. 
|     
|    In general, control protocols may be attacked by: 
|      - MPLS signaling (LDP, RSVP-TE)  
|      - PCE signaling 
|      - IPsec signaling (IKE and IKEv2) 
|      - ICMP and ICMPv6 
|      - L2TP 
|      - BGP-based membership discovery 
|      - Database-based membership discovery (e.g., RADIUS) 
|      - Other protocols that may be important to the control  
|            infrastructure, e.g., DNS, LMP, NTP, SNMP, and GRE. 
|       
| 9.1.2. Data plane attacks 
|     
|      - Unauthorized observation of data traffic 
|      - Data traffic modification 
|      - Spoofing and replay 
|      - Unauthorized Deletion 
|      - Unauthorized Traffic Pattern Analysis 
|      - Denial of Service Attacks 

|    9.2. Defense Techniques 
|     
|      1) Authentication: 
|  
|         - Identity authentication - Key management  
|         - Management System Authentication 
|         - Peer-to-peer authentication 
|     
|      2) Cryptographic techniques 
|      3) Use of IPsec in MPLS/GMPLS networks 
|      4) Encryption for device configuration and management 
|      5) Cryptographic Techniques for MPLS Pseudowires 
|      6) End-to-End versus Hop-by-Hop Protection (CE-CE, PE-PE, PE-CE) 
|      7) Access Control techniques 
|       
|         - Filtering 
|         - Firewalls 
|         - Access Control to management interfaces 
|            
|      8) Infrastructure isolation 
|      9) Use of aggregation infrastructure 
|      10) Quality Control Processes 
|      11) Testable MPLS/GMPLS Service 
|     
|    9.3. Service Provider MPLS and GMPLS Best Practice Outlines 
|     
| 9.3.1. SP infrastructure protection 
|  
|      1) General control plane protection 
|         - Protocol authentication within the core 
|         - Infrastructure Hiding (e.g. disable TTL propagation) 
|      2) RSVP control plane protection 
|         - Using RSVP security tools 
|         - Isolation of the trusted domain 
|         - Deactivating RSVP on interfaces with neighbors who are not 
|            authorized to use RSVP 
|         - RSVP neighbor filtering at the protocol level and data plane 
|            level 
|         - Authentication for RSVP messages 
|         - RSVP message pacing 
|      3) LDP control plane protection (similar techniques as for RSVP) 
|      4) Data plane protection 
|         - User Access link protection 
|         - Link Authentication 
|         - Access routing control (e.g. prefix limits, route dampening, 
|            routing table limits (e.g. VRF limits) 
|         - Access QoS control 
|         - Using customer service monitoring tools 
|     
| 9.3.2.  Inter-provider Security 
|     
|    Inter-provider connections are high security risk areas. Similar 
|    techniques and procedures as described in for SP general core 
|    protection are listed below for inter-provider connections. 
|     
|      1) Control plane protection at the inter-provider connections 
|         - Authentication of Signaling Sessions 
|         - Protection against DoS attacks in the Control Plane 
|         - Protection against Malformed Packets 
|         - Ability to Enable/Disable Specific Protocols 
|         - Protection Against Incorrect Cross Connection 
|         - Protection Against Spoofed Updates and Route Advertisements 
|         - Protection of Confidential Information 
|         - Protection Against over-provisioned number of RSVP-TE LSPs 
|            and bandwidth reservation 
|      2) Data Plane Protection at the inter-provider connections 
|         - Protection against DoS in the Data Plane 
|         - Protection against Label Spoofing 
|  

(Unfortunately, this summary reads like a table of contents to me.  If
we captured 1-2 best and key recommendations here, it would be more useful)

|  
| 10.     Security Considerations 
|  
|     
|    Security considerations constitute the sole subject of this memo 
|    and hence are discussed throughout.  Here we recap what has been 
|    presented and explain at a high level the role of each type of 
|    consideration in an overall secure MPLS/GMPLS system. 
|     
|    The document describes a number of potential security threats.  
|    Some of these threats have already been observed occurring in 
|    running networks; others are largely theoretical at this time.   
|     
|    DoS attacks and intrusion attacks from the Internet against service 
|    providers' infrastructure have been seen.  DoS "attacks" (typically 
|    not malicious) have also been seen in which CE equipment overwhelms 
|    PE equipment with high quantities or rates of packet traffic or 
|    routing information.  Operational or provisioning errors are cited 
|    by service providers as one of their prime concerns. 
|     
|    The document describes a variety of defensive techniques that may 
|    be used to counter the suspected threats.  All of the techniques 
|    presented involve mature and widely implemented technologies that 
|    are practical to implement. 
|     
|    The document describes the importance of detecting, monitoring, and 
|    reporting attacks, both successful and unsuccessful.  These 
|    activities are essential for "understanding one's enemy", 
|    mobilizing new defenses, and obtaining metrics about how secure the 
|    MPLS/GMPLS network is.  As such, they are vital components of any 
|    complete PPVPN security system. 
|     
|    The document evaluates MPLS/GMPLS security requirements from a 
|    customer's perspective as well as from a service provider's 
|    perspective.  These sections re-evaluate the identified threats 
|    from the perspectives of the various stakeholders and are meant to 
|    assist equipment vendors and service providers, who must ultimately 
|    decide what threats to protect against in any given configuration 
|    or service offering. 


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


From ca@hindmarsh-island.com  Tue May 20 04:49:54 2008
Return-Path: <ca@hindmarsh-island.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39FAC28C0D0;
	Tue, 20 May 2008 04:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -32.13
X-Spam-Level: 
X-Spam-Status: No, score=-32.13 tagged_above=-999 required=5
	tests=[BAYES_95=3, FS_REPLICA=0.994, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_DSBL=0.961,
	RCVD_IN_NJABL_PROXY=1.643, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,
	RCVD_IN_XBL=3.033, SARE_SPEC_REPLICA_OBFU=1.812,
	SARE_SPEC_ROLEX_NOV5A=1.062, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	URIBL_RHS_DOB=1.083, URIBL_SBL=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nflfdDgpKnhF; Tue, 20 May 2008 04:49:54 -0700 (PDT)
Received: from 73-228-90.dial.terra.cl (73-228-90.dial.terra.cl [200.90.228.73])
	by core3.amsl.com (Postfix) with SMTP id C10D528C0E5;
	Tue, 20 May 2008 04:49:43 -0700 (PDT)
X-Originating-IP: 166.192.208.13 by smtp.200.90.228.73;  Tue, 20 May 2008 07:49:45 -0500
Message-ID: <qvxrhqfZXSBFmip6@ietf.org>
From: "Chelsea Craft" <mip6@ietf.org>
Reply-To: "Chelsea Craft" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Replicas will save you thousands
Date: Tue, 20 May 2008 07:49:45 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


The new Porsche Design watches originated from the novel Titanium Chronograph from the 1970's, an absolutely unique creation due to the perfection of its workmanship. Based on its design, the Porsche Design Company developed an appealing, stylish, sporty and highly accurate watch. Unfortunately, these timepieces come with a high price tag. 
http://www.adieks.com/

That's why a clever group of European manufacturers decided to offer the same exact functionality and style at greatly reduced prices: the Porsche Design replica watches. These replicas are so similar to the brand name pieces that it is practically impossible to tell them apart, other than by their price. They look the same, they function the same and they definitely don't have the same prices :) How would you like to browse through an amazing collection of these watches and marvel yourself with their low prices? Visit Prestige Replicas and see for yourself why sometimes replicas are so much better than the originals!
http://www.adieks.com/





From mpls-bounces@ietf.org  Tue May 20 20:49:41 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 56B4128C234;
	Tue, 20 May 2008 20:49:41 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0ED4E3A6BC4
	for <mpls@core3.amsl.com>; Tue, 20 May 2008 20:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6IQ5FZHXpFvn for <mpls@core3.amsl.com>;
	Tue, 20 May 2008 20:49:39 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174])
	by core3.amsl.com (Postfix) with ESMTP id E748C293EEE
	for <mpls@ietf.org>; Tue, 20 May 2008 20:16:30 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so2080033wfd.31
	for <mpls@ietf.org>; Tue, 20 May 2008 20:16:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=Gv08yroLDqps4gsvZC1j3zKRGF6lLeVSUQ9zPaUfCuU=;
	b=jUARFH/uhCGHZaqvfBAxuowtPDQ7vZ5HWEFGElDwa+pww0epv5hxYKbwQq2r83d1LoZ8XOW9Nkh61jD4iQJUkZQ4SdXU6aN7lN+bqc0/u0AIHGIUUwUJE58YCvVejRvIyo4Z6yZi9lZpbIRGqxhr+xqOZxBWSMziKmpP0YT/v4Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=iJZ77zGy3gwR7F2gO081iIoiJaDpVNmTuzawYynqovNJoBSDMsqmEyddYzeWQQRVGnEbP5UkpTMzqryTaJDBCJTKeyPVL0Cc0tu4W+Cyvghlm6BZC78OT4EzkHoZReaCPS27wBAaBWKv3CUPHunw/o72nAoD0ODxlnmf0Qtg4nY=
Received: by 10.142.213.9 with SMTP id l9mr3655843wfg.71.1211339791090;
	Tue, 20 May 2008 20:16:31 -0700 (PDT)
Received: by 10.143.164.14 with HTTP; Tue, 20 May 2008 20:16:31 -0700 (PDT)
Message-ID: <77ead0ec0805202016l530e43c2j507bf40ee4668cbc@mail.gmail.com>
Date: Wed, 21 May 2008 08:46:31 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Loa Andersson" <loa@pi.nu>
In-Reply-To: <48316C20.2060708@pi.nu>
MIME-Version: 1.0
Content-Disposition: inline
References: <481C670F.8090803@pi.se> <48316C20.2060708@pi.nu>
Cc: Ross Callon <rcallon@juniper.net>, mpls@ietf.org,
	David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Loa,

The document looks good to me.

Thanks,
Vishwas

On Mon, May 19, 2008 at 5:31 PM, Loa Andersson <loa@pi.nu> wrote:
> All,
>
> this two week poll resulted in no responses :( !
>
> This is surprising - since we had a good support for the
> document at the wg meeting.
>
> I don't if the lack of response is because I chose a bad
> subject-line, or because I've had quite a bit of problems
> with my email-address or because lack of interest.
>
> We are extending the poll until 2008-05-27 (May 27 2008).
>
> Loa and George
>
> Loa Andersson wrote:
>> All,
>>
>> the authors of
>>
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>>
>> has requested that the document becomes a working group document.
>>
>> This is to start a two week poll on the mpls wg mailing list.
>>
>> Please send your comments to the mailing list; we are explicitly
>> soliciting both negative and positive comments.
>>
>>
>> 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.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed May 21 04:41:27 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 597A53A6A49;
	Wed, 21 May 2008 04:41:27 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79FED3A6866
	for <mpls@core3.amsl.com>; Wed, 21 May 2008 04:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jnAP9zOgZrIf for <mpls@core3.amsl.com>;
	Wed, 21 May 2008 04:41:25 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id BE45D3A6A20
	for <mpls@ietf.org>; Wed, 21 May 2008 04:41:07 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m4LBf1xQ031283; Wed, 21 May 2008 12:41:01 +0100
Received: from your029b8cecfe (88-96-235-142.dsl.zen.co.uk [88.96.235.142])
	(authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m4LBeu7u031221; Wed, 21 May 2008 12:40:58 +0100
Message-ID: <008501c8bb37$868779c0$9001010a@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Kannan Varadhan" <kannanv@juniper.net>, <mpls@ietf.org>
References: <C451FF9C.2DEAC%kannanv@juniper.net>
Date: Wed, 21 May 2008 12:40:43 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [mpls] Comments
	ondraft-ietf-mpls-mpls-and-gmpls-security-framework-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0979561938=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0979561938==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0082_01C8BB3F.E2135270"

This is a multi-part message in MIME format.

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

Hi Kannan,

Just to pick three points out of your detailed and thorough review...

> |    The MPLS user plane, as presently defined, is not amenable to=20
>=20
> What is this MPLS user plane?  Where is it defined?

A user plane is a data plane. Different term; same thing.
Might be helpful if we used one term through-out.
=20
>    2.  Inband access to management interfaces on any MPLS/GMPLS only
>    infrastructure implies MPLS tunnel termination on those devices
>    within the infrastructure.  By definition, tunnels terminate on the
>    PE devices, and hence do not permit such management access to P
>    devices.  With that, the injunction to apply filtering/firewalling
>    to host bound traffic as you haveit below is good.

I have trouble with your statement that tunnels *only* terminate on PEs. =
If you insist on such a definition, then the bubble is pushed and we =
simply define all devices in the MPLS/GMPLS-only network that support =
inband management as PEs. This doesn't seem helpful as it is better to =
see a PE as a Provider Edge.

Consider that the P device in such a case is not able to route or =
forward IP traffic. But it can receive IP traffic targeted to it. This =
would be how the control plane operates in this type of network.

Sometimes (more often in in-fiber-out-of-band) a network node may be =
able to forward management or control plane traffic across the network =
using in-band links. This works particularly well when the =
management/control plane network uses a private address space since this =
helps segregate customer traffic (that should not be handled in this =
way) from operations traffic.

> should nominally check the label stack depth.  By this I mean, if a
> spoofed packet arrives with a valid label, but only a 1-label stack, =
nd
> we exect at least 2 or more labels, we should drop.

This is a valid idea at nodes that can know the expected label depth.
But how many LSP transit nodes can know this?

Cheers,
Adrian


------=_NextPart_000_0082_01C8BB3F.E2135270
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3D"Courier New" size=3D2>Hi Kannan,</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2><FONT face=3DArial>Just to pick =
three points=20
out of your detailed and thorough review...</FONT></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><FONT =
face=3DArial></FONT>&nbsp;</DIV></FONT>
<DIV><FONT face=3D"Courier New" size=3D2>&gt; |&nbsp;&nbsp;&nbsp; The =
MPLS user=20
plane, as presently defined, is not amenable to <BR>&gt; <BR>&gt; What =
is this=20
MPLS user plane?&nbsp; Where is it defined?<BR></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>A user plane is a data plane. =
Different=20
term; same thing.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Might be helpful if we used one =
term=20
through-out.</DIV></FONT>
<DIV><FONT face=3D"Courier New" =
size=3D2>&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; 2.&nbsp;=20
Inband access to management interfaces on any MPLS/GMPLS=20
only<BR>&gt;&nbsp;&nbsp;&nbsp; infrastructure implies MPLS tunnel =
termination on=20
those devices<BR>&gt;&nbsp;&nbsp;&nbsp; within the infrastructure.&nbsp; =
By=20
definition, tunnels terminate on the<BR>&gt;&nbsp;&nbsp;&nbsp; PE =
devices, and=20
hence do not permit such management access to =
P<BR>&gt;&nbsp;&nbsp;&nbsp;=20
devices.&nbsp; With that, the injunction to apply=20
filtering/firewalling<BR>&gt;&nbsp;&nbsp;&nbsp; to host bound traffic as =
you=20
haveit below is good.<BR></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>I have trouble with your =
statement that=20
tunnels *only* terminate on PEs. If you insist on such a definition, =
then the=20
bubble is pushed and we simply define all devices in the MPLS/GMPLS-only =
network=20
that support inband management as PEs. This doesn't seem helpful as it =
is better=20
to see a PE as a Provider Edge.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Consider that the P device in =
such a case=20
is not able to route or forward IP traffic. But it can receive IP =
traffic=20
targeted to it. This would be how the control plane operates in this =
type of=20
network.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Sometimes (more often in=20
in-fiber-out-of-band) a network node may be able to forward management =
or=20
control plane traffic across the network using in-band links. This works =

particularly well when the management/control plane network uses a =
private=20
address space since this helps segregate customer traffic (that should =
not be=20
handled in this way) from operations traffic.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>&gt; should nominally check the =
label stack=20
depth.&nbsp; By this I mean, if a<BR>&gt; spoofed packet arrives with a =
valid=20
label, but only a 1-label stack, nd<BR>&gt; we exect at least 2 or more =
labels,=20
we should drop.<BR></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>This is a valid idea at nodes =
that can know=20
the expected label depth.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>But how many LSP transit nodes =
can know=20
this?</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Cheers,</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Adrian</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0082_01C8BB3F.E2135270--



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

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

--===============0979561938==--




From c.moore@davidrandall.com  Thu May 22 19:35:11 2008
Return-Path: <c.moore@davidrandall.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B08EF3A6BA9;
	Thu, 22 May 2008 19:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -61.658
X-Spam-Level: 
X-Spam-Status: No, score=-61.658 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FB_REPLICA_ROLEX=3.157, FH_HELO_EQ_D_D_D_D=1.597,
	FH_RELAY_NODNS=1.451, GB_ROLEX=5, HELO_DYNAMIC_IPADDR2=4.395,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_NONE=0.1,
	REPLICA_WATCH=3.396, SARE_SPEC_REPLICA_OBFU=1.812,
	SARE_SPEC_ROLEX_NOV5A=1.062, SARE_SPEC_ROLEX_REP=1.666,
	TVD_RCVD_IP=1.931, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vnKkTDFi31tE; Thu, 22 May 2008 19:35:11 -0700 (PDT)
Received: from 201-255-150-17.mrse.com.ar (unknown [201.255.150.17])
	by core3.amsl.com (Postfix) with SMTP id E037F3A6BD4;
	Thu, 22 May 2008 19:34:48 -0700 (PDT)
X-Originating-IP: 239.145.66.103 by smtp.201.255.150.17;  Thu, 22 May 2008 22:34:48 -0500
Message-ID: <bbltmJKFCHEmip6@ietf.org>
From: "Tod Stevens" <mip6@ietf.org>
Reply-To: "Tod Stevens" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Save thousands... no one will know
Date: Thu, 22 May 2008 22:34:48 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit
X-Antivirus: avast! (VPS 080522-0, 22/05/2008), Outbound message
X-Antivirus-Status: Clean


When it comes down to getting a replica Rolex watch, there is just one place that offers its visitors and customers the highest quality available: Prestige Replicas. This unparalleled online store specializes in top of the line replica watches with unsurpassed performance, and bearing every marking that the genuine timepieces have. Every replica watch that Prestige Replicas carries, is made of solid stainless steel and features a sapphire crystal glass. What's more, every Rolex in store displays the green Rolex sticker with model number and logo on it. Just because you're buying a replica, don't settle for a low quality product. There are only a handful of online stores that offer the highest quality Rolex replica watches and Prestige Replicas is among them, and with the lowest available prices!
http://nukusybohok31.blogspot.com/





From mpls-bounces@ietf.org  Fri May 23 23:14:09 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27AF13A67B4;
	Fri, 23 May 2008 23:14:09 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0977A3A67CC
	for <mpls@core3.amsl.com>; Fri, 23 May 2008 23:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -54.299
X-Spam-Level: 
X-Spam-Status: No, score=-54.299 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, DOS_OE_TO_MX=2.75, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HTML_MESSAGE=0.001, 
	JM_REACTOR_MAILER=1, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	TVD_RCVD_IP=1.931, URIBL_BLACK=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cE9uUSTNU0tN for <mpls@core3.amsl.com>;
	Fri, 23 May 2008 23:14:07 -0700 (PDT)
Received: from 190-76-36-63.dyn.movilnet.com.ve
	(190-76-36-63.dyn.movilnet.com.ve [190.76.36.63])
	by core3.amsl.com (Postfix) with ESMTP id 9F78B3A67B2
	for <mpls@lists.ietf.org>; Fri, 23 May 2008 23:14:06 -0700 (PDT)
Message-ID: <000501c8bd65$01fc4505$293d9a9f@mukel>
From: "ivagra cilais " <jreddy1@att.com>
To: <mpls@lists.ietf.org>
Date: Sat, 24 May 2008 04:28:49 +0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: [mpls] 73% off for mpls
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1744404493=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1744404493==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0002_01C8BD65.01FB6AD4"

This is a multi-part message in MIME format.

------=_NextPart_000_0002_01C8BD65.01FB6AD4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello, make a wise decision, purchase your pharmaceuticals from the most =
reliable shop
Coupon #mj2D
bill shin-yua
------=_NextPart_000_0002_01C8BD65.01FB6AD4
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3199" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
Hello, make a wise decision, purchase your pharmaceuticals from the <a =
href=3D"http://ad.doubleclick.net/click;h=3DkrJldmYYkTCEmqDGSmMvjnTwdCvbk=
rJldmYY;~sscs=3D%3fhttp://beaukaye.com/redir.html">most reliable =
shop</a>
<br>
Coupon #mj2D
<br>bill shin-yua
</BODY></HTML>
------=_NextPart_000_0002_01C8BD65.01FB6AD4--



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

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

--===============1744404493==--




From mpls-bounces@ietf.org  Sat May 24 13:02:54 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BBAC3A6A93;
	Sat, 24 May 2008 13:02:53 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93AB63A6A9E
	for <mpls@core3.amsl.com>; Sat, 24 May 2008 13:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=-0.929, 
	BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uGdO1mRS3u8Q for <mpls@core3.amsl.com>;
	Sat, 24 May 2008 13:02:44 -0700 (PDT)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.141])
	by core3.amsl.com (Postfix) with ESMTP id 8DAAD3A697F
	for <mpls@ietf.org>; Sat, 24 May 2008 13:02:43 -0700 (PDT)
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e1.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id m4OK2bnR031377
	for <mpls@ietf.org>; Sat, 24 May 2008 16:02:37 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id
	m4OK2alK157816 for <mpls@ietf.org>; Sat, 24 May 2008 16:02:37 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	m4OK2aZD007272 for <mpls@ietf.org>; Sat, 24 May 2008 16:02:36 -0400
Received: from d01ml263.pok.ibm.com (d01ml263.pok.ibm.com [9.56.227.113])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	m4OK2aOm007269 for <mpls@ietf.org>; Sat, 24 May 2008 16:02:36 -0400
From: Andrew Veitch <aveitch@us.ibm.com>
To: mpls@ietf.org
Message-ID: <OFE04729D9.B66E9148-ON85257453.006E19A7-85257453.006E19A7@us.ibm.com>
Date: Sat, 24 May 2008 16:02:35 -0400
X-MIMETrack: Serialize by Router on D01ML263/01/M/IBM(Release 7.0.2FP2HF300 |
	September 14, 2007) at 05/24/2008 16:02:36
MIME-Version: 1.0
Subject: [mpls] Veitch, Andrew is out of the office.
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


I will be out of the office starting  05/23/2008 and will not return until
05/27/2008.

I will be traveling for business and will have limited Internet and email
access, though I will be checking it daily.

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


From c.mueller@direktexpress.de  Sun May 25 21:19:58 2008
Return-Path: <c.mueller@direktexpress.de>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 687893A696F;
	Sun, 25 May 2008 21:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -37.868
X-Spam-Level: 
X-Spam-Status: No, score=-37.868 tagged_above=-999 required=5
	tests=[AWL=-23.791, BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_RELAY_NODNS=1.451, HELO_DYNAMIC_IPADDR2=4.395,
	HTTP_ESCAPED_HOST=0.134, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_NONE=0.1,
	SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX_NOV5A=1.062,
	SARE_SPEC_ROLEX_NOV5F=0.666, TVD_RCVD_IP=1.931, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10,
	URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id c-CdSj-1d3WF; Sun, 25 May 2008 21:19:52 -0700 (PDT)
Received: from 201-255-121-108.mrse.com.ar (unknown [201.255.121.108])
	by core3.amsl.com (Postfix) with SMTP id 7B0BE3A6B0C;
	Sun, 25 May 2008 21:19:40 -0700 (PDT)
X-Originating-IP: 163.204.106.234 by smtp.201.255.121.108;  Mon, 26 May 2008 00:19:54 -0500
Message-ID: <sszenvFYICAAAmip6@ietf.org>
From: "Seymour Tidwell" <mip6@ietf.org>
Reply-To: "Seymour Tidwell" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Impressive Glashutte timepieces
Date: Mon, 26 May 2008 00:19:54 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


A Tag Heuer watch is a luxury statement on its own. Unfortunately, that luxury comes with a price... Except when you visit Prestige Replicas, the web's most comprehensive collection of brand name replica watches. In Prestige Replicas, any Tag Heuer is available for just over $200. http://www%2Enunubsyy%2Ecom/  For those of us who have always dreamed of wearing a Tag Heuer, there is no better time to make our dream come true than this very moment, and no better place to do it, than at Prestige Replicas. Here you will find the most prestigious replica Tag Heuers, at an unbeatable price. Come inside now... your Tag Heuer watch is waiting for you at Prestige Replicas.
http://www%2Enunubsyy%2Ecom/





From c.kato@tabix.jp  Mon May 26 21:43:37 2008
Return-Path: <c.kato@tabix.jp>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47D383A6B40;
	Mon, 26 May 2008 21:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.985
X-Spam-Level: 
X-Spam-Status: No, score=-14.985 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295,
	HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129,
	HTTP_ESCAPED_HOST=0.134, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10,
	URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yeMgYexoX66k; Mon, 26 May 2008 21:43:31 -0700 (PDT)
Received: from 97-133-223-201.adsl.terra.cl (97-133-223-201.adsl.terra.cl [201.223.133.97])
	by core3.amsl.com (Postfix) with SMTP id 0A65E3A67EA;
	Mon, 26 May 2008 21:42:35 -0700 (PDT)
X-Originating-IP: 224.148.175.176 by smtp.201.223.133.97;  Tue, 27 May 2008 00:42:50 -0500
Message-ID: <odzenzvUIRAPAmip6@ietf.org>
From: "Gus Varner" <mip6@ietf.org>
Reply-To: "Gus Varner" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Trim line or sport watch? You choose
Date: Tue, 27 May 2008 00:42:50 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


What comes to mind when you hear the words Louis Vuitton? Of course, the classic style, the superior quality of their bags, their unique look, and their inflated price tag. But, how about being able to afford a beautiful Louis Vuitton handbag without having to dent your budget? It is now possible. Thanks to Prestige Replicas, that Louis Vuitton bag or wallet is closer to you than ever before! Come visit our new designer bag section and pick that special Louis Vuitton handbag that you've always wanted. 
http://www%2Ebybyusse%2Ecom/

Remember, Prestige Replicas offers award winning customer service and an absolute guarantee of its products and your privacy!
http://www%2Ebybyusse%2Ecom/






From mpls-bounces@ietf.org  Tue May 27 10:26:50 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C39283A6C35;
	Tue, 27 May 2008 10:26:50 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C84563A682C
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 10:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mfFHcN2-625n for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 10:26:49 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 99ACF3A6C35
	for <mpls@ietf.org>; Tue, 27 May 2008 10:26:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,549,1204520400"; 
   d="scan'208";a="9369740"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 27 May 2008 13:26:50 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4RHQoRV024345; 
	Tue, 27 May 2008 13:26:50 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4RHQo33016373;
	Tue, 27 May 2008 17:26:50 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 May 2008 13:26:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 May 2008 13:26:49 -0400
Message-ID: <DD7E9F364F33B54881C225192D4872D73D8C0D@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <48316C20.2060708@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: Aci5qKTB8jIVf1EdTGOitcWCftkLvAGdiCYQ
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 27 May 2008 17:26:50.0105 (UTC)
	FILETIME=[D8ED6E90:01C8C01E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1555; t=1211909210;
	x=1212773210; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lufang@cisco.com;
	z=From:=20=22Luyuan=20Fang=20(lufang)=22=20<lufang@cisco.com >
	|Subject:=20RE=3A=20[mpls]=20draft-asati-mpls-ldp-end-of-li
	b-01.txt=20as=20wg=20document |Sender:=20
	|To:=20=22Loa=20Andersson=22=20<loa@pi.nu>,=20<mpls@ietf.or g>;
	bh=ncTZa4sV3Tn9FD98BXe/7xioM9RiSWJrf27+Bup9BlM=;
	b=f04mGFXCcFS6eZUjvAhrYazZ/K87E8uJc4xSp0X66H9LdgF4/aq8QC8pTX
	YYD5m40qxTyZF2GoXRjJQ3xANZ4QRoo0HfHeFVdflLmOwPTd/Y7JoqFh5nl/
	gBHYYRB1OZ;
Authentication-Results: rtp-dkim-1; header.From=lufang@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support.
- Luyuan 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Loa Andersson
Sent: 19 May 2008 08:02
To: mpls@ietf.org
Cc: Ross Callon; David Ward
Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document

All,

this two week poll resulted in no responses :( !

This is surprising - since we had a good support for the document at the
wg meeting.

I don't if the lack of response is because I chose a bad subject-line,
or because I've had quite a bit of problems with my email-address or
because lack of interest.

We are extending the poll until 2008-05-27 (May 27 2008).

Loa and George

Loa Andersson wrote:
> All,
> 
> the authors of
> 
> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
> 
> has requested that the document becomes a working group document.
> 
> This is to start a two week poll on the mpls wg mailing list.
> 
> Please send your comments to the mailing list; we are explicitly 
> soliciting both negative and positive comments.
> 
> 
> 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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May 27 10:51:48 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6866B3A6894;
	Tue, 27 May 2008 10:51:48 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 97AB93A6894
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 10:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zbJnsK+xsgcH for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 10:51:46 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 4FDFE3A67F3
	for <mpls@ietf.org>; Tue, 27 May 2008 10:51:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,549,1204498800"; d="scan'208";a="10037533"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 27 May 2008 19:51:48 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4RHpmZE002052; 
	Tue, 27 May 2008 19:51:48 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4RHiidN012153;
	Tue, 27 May 2008 17:44:45 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 May 2008 19:44:08 +0200
Received: from 10.61.81.103 ([10.61.81.103]) by xmb-ams-33a.emea.cisco.com
	([144.254.231.85]) via Exchange Front-End Server
	email.cisco.com ([144.254.231.72]) with Microsoft Exchange
	Server HTTP-DAV ; Tue, 27 May 2008 17:44:08 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 27 May 2008 10:44:07 -0700
From: Monique Morrow <mmorrow@cisco.com>
To: "Luyuan Fang (lufang)" <lufang@cisco.com>, Loa Andersson <loa@pi.nu>,
	<mpls@ietf.org>
Message-ID: <C4619677.6709B%mmorrow@cisco.com>
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: Aci5qKTB8jIVf1EdTGOitcWCftkLvAGdiCYQAACfZ8E=
In-Reply-To: <DD7E9F364F33B54881C225192D4872D73D8C0D@xmb-rtp-211.amer.cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 27 May 2008 17:44:08.0937 (UTC)
	FILETIME=[441E9D90:01C8C021]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1858; t=1211910708;
	x=1212774708; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mmorrow@cisco.com;
	z=From:=20Monique=20Morrow=20<mmorrow@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20draft-asati-mpls-ldp-end-of-li
	b-01.txt=20as=20wg=20document |Sender:=20;
	bh=L5LNTiawrWPDv+0MIaSUHF23SDymXzHndu0hhLBc4T8=;
	b=i64rupdeDKmbu0iSil5jclluGjyK5gjq83KfJsZyVZP0FxIs8HGIn6cc5r
	N+XUMylv8Qiv4qnoYTvUIm6pK+KODySCq0iuCNjb+jhK8jYdoRJ9kVaXc5bx
	SYnvRngFsF;
Authentication-Results: ams-dkim-1; header.From=mmorrow@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support also


On 5/27/08 10:26 AM, "Luyuan Fang (lufang)" <lufang@cisco.com> wrote:

> Support.
> - Luyuan 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Loa Andersson
> Sent: 19 May 2008 08:02
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
> 
> All,
> 
> this two week poll resulted in no responses :( !
> 
> This is surprising - since we had a good support for the document at the
> wg meeting.
> 
> I don't if the lack of response is because I chose a bad subject-line,
> or because I've had quite a bit of problems with my email-address or
> because lack of interest.
> 
> We are extending the poll until 2008-05-27 (May 27 2008).
> 
> Loa and George
> 
> Loa Andersson wrote:
>> All,
>> 
>> the authors of
>> 
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>> 
>> has requested that the document becomes a working group document.
>> 
>> This is to start a two week poll on the mpls wg mailing list.
>> 
>> Please send your comments to the mailing list; we are explicitly
>> soliciting both negative and positive comments.
>> 
>> 
>> 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.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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


From c5efda6b.ceadd6e@rocelco.com  Tue May 27 10:55:34 2008
Return-Path: <c5efda6b.ceadd6e@rocelco.com>
X-Original-To: ietfarch-mpls-archive@core3.amsl.com
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7DD313A6A39;
	Tue, 27 May 2008 10:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.29
X-Spam-Level: 
X-Spam-Status: No, score=-9.29 tagged_above=-999 required=5 tests=[BAYES_80=2,
	FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426,
	HTTP_ESCAPED_HOST=0.134, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,
	RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812,
	SARE_SPEC_ROLEX_NOV5A=1.062, URIBL_AB_SURBL=10, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10,
	URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1F5P61AkFPf3; Tue, 27 May 2008 10:55:28 -0700 (PDT)
Received: from pc-136-124-86-200.cm.vtr.net (pc-136-124-86-200.cm.vtr.net [200.86.124.136])
	by core3.amsl.com (Postfix) with SMTP id C16C73A67B6;
	Tue, 27 May 2008 10:54:53 -0700 (PDT)
X-Originating-IP: 232.163.238.28 by smtp.200.86.124.136;  Tue, 27 May 2008 13:55:08 -0500
Message-ID: <cchwmqbDFJIPIEmip6@ietf.org>
From: "Romeo Elmore" <mip6@ietf.org>
Reply-To: "Romeo Elmore" <mip6@ietf.org>
To: mip6@ietf.org
Subject: Why get an original watch?
Date: Tue, 27 May 2008 13:55:08 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


The new Porsche Design watches originated from the novel Titanium Chronograph from the 1970's, an absolutely unique creation due to the perfection of its workmanship. Based on its design, the Porsche Design Company developed an appealing, stylish, sporty and highly accurate watch. Unfortunately, these timepieces come with a high price tag. 
http://www%2Eshheus%2Ecom/

That's why a clever group of European manufacturers decided to offer the same exact functionality and style at greatly reduced prices: the Porsche Design replica watches. These replicas are so similar to the brand name pieces that it is practically impossible to tell them apart, other than by their price. They look the same, they function the same and they definitely don't have the same prices :) How would you like to browse through an amazing collection of these watches and marvel yourself with their low prices? Visit Prestige Replicas and see for yourself why sometimes replicas are so much better than the originals!
http://www%2Eshheus%2Ecom/





From mpls-bounces@ietf.org  Tue May 27 11:02:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCD5B3A6C55;
	Tue, 27 May 2008 11:02:02 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA04B3A6A32
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 11:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id i-ZiOMGEnUrC for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 11:01:52 -0700 (PDT)
Received: from cox.com (post1.cox.com [24.248.74.35])
	by core3.amsl.com (Postfix) with ESMTP id 8C6FD3A6C53
	for <mpls@ietf.org>; Tue, 27 May 2008 11:01:48 -0700 (PDT)
Received: from ([192.168.74.254])
	by post1.cox.com with ESMTP  id 5503594.32445606;
	Tue, 27 May 2008 13:59:23 -0400
Received: from CATL0MS20.CORP.COX.COM ([10.62.210.20]) by
	catl0ms23.CORP.COX.COM with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 27 May 2008 13:59:23 -0400
Received: from CATL0MS01.corp.cox.com ([10.62.210.87]) by
	CATL0MS20.CORP.COX.COM with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 27 May 2008 13:59:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 May 2008 13:59:21 -0400
Message-ID: <4BDBFD169115D54DAA3B74E8CB682A44036E2328@CATL0MS01.corp.cox.com>
In-Reply-To: <C4619677.6709B%mmorrow@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: Aci5qKTB8jIVf1EdTGOitcWCftkLvAGdiCYQAACfZ8EAAIXhkA==
References: <DD7E9F364F33B54881C225192D4872D73D8C0D@xmb-rtp-211.amer.cisco.com>
	<C4619677.6709B%mmorrow@cisco.com>
From: <Mazen.Khaddam@cox.com>
To: <mmorrow@cisco.com>,
	<lufang@cisco.com>,
	<loa@pi.nu>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 27 May 2008 17:59:22.0655 (UTC)
	FILETIME=[64BCEAF0:01C8C023]
Cc: rcallon@juniper.net, dward@cisco.com
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Monique Morrow
Sent: Tuesday, May 27, 2008 1:44 PM
To: Luyuan Fang (lufang); Loa Andersson; mpls@ietf.org
Cc: Ross Callon; David Ward
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg
document

Support also


On 5/27/08 10:26 AM, "Luyuan Fang (lufang)" <lufang@cisco.com> wrote:

> Support.
> - Luyuan 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
> Loa Andersson
> Sent: 19 May 2008 08:02
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
> 
> All,
> 
> this two week poll resulted in no responses :( !
> 
> This is surprising - since we had a good support for the document at
the
> wg meeting.
> 
> I don't if the lack of response is because I chose a bad subject-line,
> or because I've had quite a bit of problems with my email-address or
> because lack of interest.
> 
> We are extending the poll until 2008-05-27 (May 27 2008).
> 
> Loa and George
> 
> Loa Andersson wrote:
>> All,
>> 
>> the authors of
>> 
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>> 
>> has requested that the document becomes a working group document.
>> 
>> This is to start a two week poll on the mpls wg mailing list.
>> 
>> Please send your comments to the mailing list; we are explicitly
>> soliciting both negative and positive comments.
>> 
>> 
>> 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.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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


From mpls-bounces@ietf.org  Tue May 27 11:12:25 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1E523A6A13;
	Tue, 27 May 2008 11:12:25 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D66043A6A13
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 11:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R8DuogJ5cbcB for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 11:12:21 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 3B2F23A682B
	for <mpls@ietf.org>; Tue, 27 May 2008 11:12:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,549,1204520400"; 
   d="scan'208";a="9373465"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 27 May 2008 14:12:26 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4RICQhm013509; 
	Tue, 27 May 2008 14:12:26 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4RICQrG025037;
	Tue, 27 May 2008 18:12:26 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 May 2008 14:12:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 May 2008 14:11:38 -0400
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B0706828D60@xmb-rtp-203.amer.cisco.com>
In-Reply-To: <DD7E9F364F33B54881C225192D4872D73D8C0D@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: Aci5qKTB8jIVf1EdTGOitcWCftkLvAGdiCYQAAGSCuA=
References: <48316C20.2060708@pi.nu>
	<DD7E9F364F33B54881C225192D4872D73D8C0D@xmb-rtp-211.amer.cisco.com>
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 27 May 2008 18:12:26.0302 (UTC)
	FILETIME=[37D3F5E0:01C8C025]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1864; t=1211911946;
	x=1212775946; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zali@cisco.com;
	z=From:=20=22Zafar=20Ali=20(zali)=22=20<zali@cisco.com>
	|Subject:=20RE=3A=20[mpls]=20draft-asati-mpls-ldp-end-of-li
	b-01.txt=20as=20wg=20document |Sender:=20
	|To:=20=22Loa=20Andersson=22=20<loa@pi.nu>,=20<mpls@ietf.or g>;
	bh=sipLCIh/Xdz5b1pDFk1++hCQnaYLa6bP3UbnDEAtAtc=;
	b=A0yJK1AkYezqXW6pUU4sDNwgWDnGkbV2NaNt86Uz8jipfC3DuCBrgJFRGk
	9ANRUhsgsyLyzuWiu3H4ociBJjKojNaEOHbVcT4hVKujtrl3DpbM1C+MQcii
	daXTN4oGDQ;
Authentication-Results: rtp-dkim-2; header.From=zali@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support- 

Thanks

Regards.. Zafar  


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Loa Andersson
> Sent: 19 May 2008 08:02
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
> 
> All,
> 
> this two week poll resulted in no responses :( !
> 
> This is surprising - since we had a good support for the 
> document at the wg meeting.
> 
> I don't if the lack of response is because I chose a bad 
> subject-line, or because I've had quite a bit of problems 
> with my email-address or because lack of interest.
> 
> We are extending the poll until 2008-05-27 (May 27 2008).
> 
> Loa and George
> 
> Loa Andersson wrote:
> > All,
> > 
> > the authors of
> > 
> > http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
> > 
> > has requested that the document becomes a working group document.
> > 
> > This is to start a two week poll on the mpls wg mailing list.
> > 
> > Please send your comments to the mailing list; we are explicitly 
> > soliciting both negative and positive comments.
> > 
> > 
> > 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.nu 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May 27 11:33:02 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6209A3A6A67;
	Tue, 27 May 2008 11:33:02 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81CB33A67A9
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 11:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.532
X-Spam-Level: 
X-Spam-Status: No, score=-4.532 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lnX9DNUlaT6b for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 11:33:00 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 497A53A6949
	for <mpls@ietf.org>; Tue, 27 May 2008 11:33:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,549,1204520400"; 
   d="scan'208";a="9367751"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 27 May 2008 14:33:05 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4RIX5LL022038
	for <mpls@ietf.org>; Tue, 27 May 2008 14:33:05 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4RIX51u004226
	for <mpls@ietf.org>; Tue, 27 May 2008 18:33:05 GMT
Received: from xmb-rtp-204.amer.cisco.com ([64.102.31.25]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 May 2008 14:33:05 -0400
Received: from 161.44.69.150 ([161.44.69.150]) by xmb-rtp-204.amer.cisco.com
	([64.102.31.25]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 27 May 2008 18:33:05 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 27 May 2008 14:33:07 -0400
From: Azhar Sayeed <asayeed@cisco.com>
To: <mpls@ietf.org>
Message-ID: <C461CC23.520D%asayeed@cisco.com>
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: Aci5qKTB8jIVf1EdTGOitcWCftkLvAGdiCYQAACfZ8EAAMZbgAAA7724
In-Reply-To: <DD7E9F364F33B54881C225192D4872D73D8C10@xmb-rtp-211.amer.cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 27 May 2008 18:33:05.0435 (UTC)
	FILETIME=[1A68A6B0:01C8C028]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1810; t=1211913185;
	x=1212777185; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=asayeed@cisco.com;
	z=From:=20Azhar=20Sayeed=20<asayeed@cisco.com>
	|Subject:=20FW=3A=20[mpls]=20draft-asati-mpls-ldp-end-of-li
	b-01.txt=20as=20wg=20document |Sender:=20
	|To:=20<mpls@ietf.org>;
	bh=7Z3btcICJmI91io7aH9xV1MSh8SUUOuYd7Ak9NxbZ9o=;
	b=rJAJcsf9TKhwO2tXI3ftfnrwa3R8WknEgqO8ZqrQgjQ926Y8tIVn1knLU+
	8gUKMFwFRnBR0/m9HKiD9tD92E4vv/iojmSNlbPYyHSSP1H5ilMGNVR84DQs
	OoUE7O2ZBi;
Authentication-Results: rtp-dkim-1; header.From=asayeed@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [mpls] FW:  draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Support it
Thanks
Azhar

> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of Loa Andersson
> Sent: 19 May 2008 08:02
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
> 
> All,
> 
> this two week poll resulted in no responses :( !
> 
> This is surprising - since we had a good support for the document at
> the wg meeting.
> 
> I don't if the lack of response is because I chose a bad subject-line,

> or because I've had quite a bit of problems with my email-address or
> because lack of interest.
> 
> We are extending the poll until 2008-05-27 (May 27 2008).
> 
> Loa and George
> 
> Loa Andersson wrote:
>> All,
>> 
>> the authors of
>> 
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>> 
>> has requested that the document becomes a working group document.
>> 
>> This is to start a two week poll on the mpls wg mailing list.
>> 
>> Please send your comments to the mailing list; we are explicitly
>> soliciting both negative and positive comments.
>> 
>> 
>> 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.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


------ End of Forwarded Message

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


From mpls-bounces@ietf.org  Tue May 27 11:44:08 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7B6C3A691A;
	Tue, 27 May 2008 11:44:08 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 715793A691A
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 11:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.018
X-Spam-Level: 
X-Spam-Status: No, score=0.018 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765,
	FH_HOST_EQ_D_D_D_DB=0.888, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id h9NHmMQCPeeG for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 11:44:06 -0700 (PDT)
Received: from ns1.cpanel.btnaccess.com (205-177-121-254.pccwglobal.net
	[205.177.121.254])
	by core3.amsl.com (Postfix) with ESMTP id AAF8E3A687B
	for <mpls@ietf.org>; Tue, 27 May 2008 11:44:06 -0700 (PDT)
Received: from [65.213.193.27]
	by ns1.cpanel.btnaccess.com with esmtpa (Exim 4.68)
	(envelope-from <rpapneja@isocore.com>)
	id 1K149H-0002ar-OO; Tue, 27 May 2008 14:43:51 -0400
User-Agent: Microsoft-Entourage/12.0.0.071130
Date: Tue, 27 May 2008 14:43:46 -0400
From: Rajiv Papneja <rpapneja@isocore.com>
To: Loa Andersson <loa@pi.nu>,
	<mpls@ietf.org>
Message-ID: <C461CEA2.4CC9%rpapneja@isocore.com>
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: AcjAKZg3tAdH4r/+VkqI/9O8tqA9TQ==
In-Reply-To: <48316C20.2060708@pi.nu>
Mime-version: 1.0
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 - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - isocore.com
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

In favor of making this as a WG document.

/Rajiv 


On 5/19/08 8:01 AM, "Loa Andersson" <loa@pi.nu> wrote:

> All,
> 
> this two week poll resulted in no responses :( !
> 
> This is surprising - since we had a good support for the
> document at the wg meeting.
> 
> I don't if the lack of response is because I chose a bad
> subject-line, or because I've had quite a bit of problems
> with my email-address or because lack of interest.
> 
> We are extending the poll until 2008-05-27 (May 27 2008).
> 
> Loa and George
> 
> Loa Andersson wrote:
>> All,
>> 
>> the authors of
>> 
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>> 
>> has requested that the document becomes a working group document.
>> 
>> This is to start a two week poll on the mpls wg mailing list.
>> 
>> Please send your comments to the mailing list; we are explicitly
>> soliciting both negative and positive comments.
>> 
>> 
>> Loa and George
>> 
> 


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


From mpls-bounces@ietf.org  Tue May 27 11:52:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D51CF3A6ABE;
	Tue, 27 May 2008 11:52:03 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 536C03A6ABE
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 11:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tJlOODSCH5hD for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 11:52:02 -0700 (PDT)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.245.3])
	by core3.amsl.com (Postfix) with ESMTP id 1437A3A68E5
	for <mpls@ietf.org>; Tue, 27 May 2008 11:52:01 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: GO4243@att.com
X-Msg-Ref: server-3.tower-146.messagelabs.com!1211914279!1786402!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.112.25]
Received: (qmail 11044 invoked from network); 27 May 2008 18:51:20 -0000
Received: from sbcsmtp3.sbc.com (HELO tlph064.enaf.dadc.sbc.com)
	(144.160.112.25)
	by server-3.tower-146.messagelabs.com with AES256-SHA encrypted SMTP;
	27 May 2008 18:51:20 -0000
Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1])
	by tlph064.enaf.dadc.sbc.com (8.14.2/8.14.2) with ESMTP id
	m4RIpHgO010493; Tue, 27 May 2008 13:51:18 -0500
Received: from td03xsmtp007.US.Cingular.Net (td03xsmtp007.us.cingular.net
	[170.35.131.171])
	by tlph064.enaf.dadc.sbc.com (8.14.2/8.14.2) with ESMTP id
	m4RIp7bG010295; Tue, 27 May 2008 13:51:11 -0500
Received: from AD01MSXMB001.US.Cingular.Net ([135.214.177.67]) by
	td03xsmtp007.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 May 2008 13:51:08 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 May 2008 13:51:06 -0500
Message-ID: <326AB619DE355A478D352883D78AF3B5019F64AE@AD01MSXMB001.US.Cingular.Net>
In-Reply-To: <4BDBFD169115D54DAA3B74E8CB682A44036E2328@CATL0MS01.corp.cox.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: Aci5qKTB8jIVf1EdTGOitcWCftkLvAGdiCYQAACfZ8EAAIXhkAABygag
References: <DD7E9F364F33B54881C225192D4872D73D8C0D@xmb-rtp-211.amer.cisco.com><C4619677.6709B%mmorrow@cisco.com>
	<4BDBFD169115D54DAA3B74E8CB682A44036E2328@CATL0MS01.corp.cox.com>
From: "Oberfield, Greg" <GO4243@att.com>
To: <Mazen.Khaddam@cox.com>, "Monique Morrow (mmorrow)" <mmorrow@cisco.com>,
	"Luyuan Fang (lufang)" <lufang@cisco.com>, <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 27 May 2008 18:51:08.0231 (UTC)
	FILETIME=[9FCE3570:01C8C02A]
Cc: rcallon@juniper.net, dward@cisco.com
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

I'm for it. 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Mazen.Khaddam@cox.com
Sent: Tuesday, May 27, 2008 12:59 PM
To: Monique Morrow (mmorrow); Luyuan Fang (lufang); loa@pi.nu;
mpls@ietf.org
Cc: rcallon@juniper.net; dward@cisco.com
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg
document

Support 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Monique Morrow
Sent: Tuesday, May 27, 2008 1:44 PM
To: Luyuan Fang (lufang); Loa Andersson; mpls@ietf.org
Cc: Ross Callon; David Ward
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg
document

Support also


On 5/27/08 10:26 AM, "Luyuan Fang (lufang)" <lufang@cisco.com> wrote:

> Support.
> - Luyuan
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
> Loa Andersson
> Sent: 19 May 2008 08:02
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
> 
> All,
> 
> this two week poll resulted in no responses :( !
> 
> This is surprising - since we had a good support for the document at
the
> wg meeting.
> 
> I don't if the lack of response is because I chose a bad subject-line,

> or because I've had quite a bit of problems with my email-address or 
> because lack of interest.
> 
> We are extending the poll until 2008-05-27 (May 27 2008).
> 
> Loa and George
> 
> Loa Andersson wrote:
>> All,
>> 
>> the authors of
>> 
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>> 
>> has requested that the document becomes a working group document.
>> 
>> This is to start a two week poll on the mpls wg mailing list.
>> 
>> Please send your comments to the mailing list; we are explicitly 
>> soliciting both negative and positive comments.
>> 
>> 
>> 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.nu 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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


From mpls-bounces@ietf.org  Tue May 27 16:34:03 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73FF03A68E6;
	Tue, 27 May 2008 16:34:03 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 055B43A68E6
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 16:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7dopMVFjZqc3 for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 16:34:01 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id CE2FB3A68C3
	for <mpls@ietf.org>; Tue, 27 May 2008 16:34:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,551,1204531200"; d="scan'208,217";a="36416585"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 27 May 2008 16:32:17 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m4RNWGF2027467
	for <mpls@ietf.org>; Tue, 27 May 2008 16:32:16 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m4RNWGH1000460
	for <mpls@ietf.org>; Tue, 27 May 2008 23:32:16 GMT
Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 May 2008 19:32:16 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 May 2008 19:31:29 -0400
Message-ID: <EAE1CBBD071180449FC50C37CFC78394055DB16D@xmb-rtp-202.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
Thread-Index: AcjAUcoOhveNxZMYRp6Z2e95HxoPlQ==
From: "Chris Metz (chmetz)" <chmetz@cisco.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 27 May 2008 23:32:16.0104 (UTC)
	FILETIME=[E5D75E80:01C8C051]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1887; t=1211931136;
	x=1212795136; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=chmetz@cisco.com;
	z=From:=20=22Chris=20Metz=20(chmetz)=22=20<chmetz@cisco.com>
	|Subject:=20[mpls]=20draft-asati-mpls-ldp-end-of-lib-01.txt
	=20as=20wg=20document |Sender:=20;
	bh=jjnqUgz96jh9mwtC28BLXVgBn8iBsoucMjspGaQc37U=;
	b=aBuTwLYuC/GZUtre4cnqsriFfklYj5AXC/J+ewGtcaaJhIyYtg5x2nHPTX
	DyVuX6W32kez7NaeQ3KCmUKBTyLTfWqmcTE6ib+RbPXmcxAwaau4cPHMSFbc
	Zgiwez2I82;
Authentication-Results: sj-dkim-3; header.From=chmetz@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [mpls]  draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1271586820=="
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1271586820==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8C051.CB7A4349"

This is a multi-part message in MIME format.

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

support.
=20
=20
Loa Andersson wrote:
> All,
>=20
> the authors of
>=20
> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>=20
> has requested that the document becomes a working group document.
>=20
> This is to start a two week poll on the mpls wg mailing list.
>=20
> Please send your comments to the mailing list; we are explicitly
> soliciting both negative and positive comments.
>=20
>=20
> Loa and George
>=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D741143023-27052008><FONT face=3DArial=20
size=3D2>support.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>Loa Andersson wrote:<BR>&gt; All,<BR>&gt; <BR>&gt; the authors =
of<BR>&gt;=20
<BR>&gt; <A=20
href=3D"http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.=
txt"=20
rel=3Dnofollow>http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-=
lib-01.txt</A><BR>&gt;=20
<BR>&gt; has requested that the document becomes a working group=20
document.<BR>&gt; <BR>&gt; This is to start a two week poll on the mpls =
wg=20
mailing list.<BR>&gt; <BR>&gt; Please send your comments to the mailing =
list; we=20
are explicitly<BR>&gt; soliciting both negative and positive =
comments.<BR>&gt;=20
<BR>&gt; <BR>&gt; Loa and George<BR>&gt; <BR></DIV></BODY></HTML>

------_=_NextPart_001_01C8C051.CB7A4349--

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

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

--===============1271586820==--


From mpls-bounces@ietf.org  Tue May 27 16:51:30 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA44B3A6892;
	Tue, 27 May 2008 16:51:29 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CC3C3A6A31
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 16:51:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Q35uzQGfpw9E for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 16:51:27 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34])
	by core3.amsl.com (Postfix) with ESMTP id 922803A6834
	for <mpls@ietf.org>; Tue, 27 May 2008 16:51:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by lucidvision.com (Postfix) with ESMTP id 96BEA3E11CA;
	Tue, 27 May 2008 19:53:41 -0400 (EDT)
Received: from lucidvision.com ([127.0.0.1])
	by localhost (localhost [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP
	id 21501-06; Tue, 27 May 2008 19:53:18 -0400 (EDT)
Received: from [10.179.2.204] (m3f5e36d0.tmodns.net [208.54.94.63])
	by lucidvision.com (Postfix) with ESMTP id EF3163E11B6;
	Tue, 27 May 2008 19:53:16 -0400 (EDT)
References: <C4619677.6709B%mmorrow@cisco.com>
Message-Id: <E1DF58BA-2BFD-423A-9CCA-769322C8B77E@lucidvision.com>
From: Thomas Nadeau <tnadeau@lucidvision.com>
To: Monique Morrow <mmorrow@cisco.com>
In-Reply-To: <C4619677.6709B%mmorrow@cisco.com>
X-Mailer: iPhone Mail (4A102)
Mime-Version: 1.0 (iPhone Mail 4A102)
Date: Tue, 27 May 2008 19:50:50 -0400
X-Virus-Scanned: by amavisd-new at lucidvision.com
Cc: Ross Callon <rcallon@juniper.net>, "<mpls@ietf.org>" <mpls@ietf.org>,
	"Luyuan Fang \(lufang\)" <lufang@cisco.com>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Agree.


Sent from my hacked and unlocked iPhone!



On May 27, 2008, at 1:44 PM, Monique Morrow <mmorrow@cisco.com> wrote:

> Support also
>
>
> On 5/27/08 10:26 AM, "Luyuan Fang (lufang)" <lufang@cisco.com> wrote:
>
>> Support.
>> - Luyuan
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On  
>> Behalf Of
>> Loa Andersson
>> Sent: 19 May 2008 08:02
>> To: mpls@ietf.org
>> Cc: Ross Callon; David Ward
>> Subject: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
>>
>> All,
>>
>> this two week poll resulted in no responses :( !
>>
>> This is surprising - since we had a good support for the document  
>> at the
>> wg meeting.
>>
>> I don't if the lack of response is because I chose a bad subject- 
>> line,
>> or because I've had quite a bit of problems with my email-address or
>> because lack of interest.
>>
>> We are extending the poll until 2008-05-27 (May 27 2008).
>>
>> Loa and George
>>
>> Loa Andersson wrote:
>>> All,
>>>
>>> the authors of
>>>
>>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>>>
>>> has requested that the document becomes a working group document.
>>>
>>> This is to start a two week poll on the mpls wg mailing list.
>>>
>>> Please send your comments to the mailing list; we are explicitly
>>> soliciting both negative and positive comments.
>>>
>>>
>>> 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.nu
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Tue May 27 18:04:24 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D42453A690F;
	Tue, 27 May 2008 18:04:23 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F07323A6892
	for <mpls@core3.amsl.com>; Tue, 27 May 2008 18:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WgtQL6dr7JWP for <mpls@core3.amsl.com>;
	Tue, 27 May 2008 18:04:10 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [61.144.161.54])
	by core3.amsl.com (Postfix) with ESMTP id 218F93A6834
	for <mpls@ietf.org>; Tue, 27 May 2008 18:03:58 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K1K00AM307VL1@szxga02-in.huawei.com> for
	mpls@ietf.org; Wed, 28 May 2008 09:02:19 +0800 (CST)
Received: from c50408 ([10.111.12.213])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K1K00A6507V7I@szxga02-in.huawei.com> for
	mpls@ietf.org; Wed, 28 May 2008 09:02:19 +0800 (CST)
Date: Wed, 28 May 2008 09:02:19 +0800
From: Cao Wei <caowayne@huawei.com>
To: mpls <mpls@ietf.org>
Message-id: <200805280902185959048@huawei.com>
MIME-version: 1.0
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
References: <EAE1CBBD071180449FC50C37CFC78394055DB16D@xmb-rtp-202.amer.cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org


support.
 
Loa Andersson wrote:
> All,
> 
> the authors of
> 
> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
> 
> has requested that the document becomes a working group document.
> 
> This is to start a two week poll on the mpls wg mailing list.
> 
> Please send your comments to the mailing list; we are explicitly
> soliciting both negative and positive comments.
> 
> 
> Loa and George
> 
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>


Best regards,			
Cao Wei

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


From mpls-bounces@ietf.org  Wed May 28 11:24:42 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CD6228C173;
	Wed, 28 May 2008 11:24:42 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E5A83A6CB4
	for <mpls@core3.amsl.com>; Wed, 28 May 2008 11:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lJJmNfgdMMRW for <mpls@core3.amsl.com>;
	Wed, 28 May 2008 11:24:40 -0700 (PDT)
Received: from fw.testbed.se (smtp.testbed.se [80.86.78.228])
	by core3.amsl.com (Postfix) with ESMTP id 06BF028C237
	for <mpls@ietf.org>; Wed, 28 May 2008 11:23:53 -0700 (PDT)
Received: from MailerDaemon by fw.testbed.se with local-bsmtp (Exim 4.63)
	(envelope-from <loa@pi.nu>) id 1K1QJZ-0004XD-Al
	for mpls@ietf.org; Wed, 28 May 2008 20:23:57 +0200
Received: from [18.105.7.231] (port=1607)
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <loa@pi.nu>)
	id 1K1QJX-0004X7-9V; Wed, 28 May 2008 20:23:55 +0200
Message-ID: <483DA329.3000704@pi.nu>
Date: Wed, 28 May 2008 20:23:37 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org
References: <481C670F.8090803@pi.se> <48316C20.2060708@pi.nu>
In-Reply-To: <48316C20.2060708@pi.nu>
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document -
 concluded
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

All,

much better response, and we have seen good support for making
this a wg document.

Could the authors please republish the draft as

draft-ietf-mpls-ldp-end-of-lib-00

Loa and George

Loa Andersson wrote:
> All,
> 
> this two week poll resulted in no responses :( !
> 
> This is surprising - since we had a good support for the
> document at the wg meeting.
> 
> I don't if the lack of response is because I chose a bad
> subject-line, or because I've had quite a bit of problems
> with my email-address or because lack of interest.
> 
> We are extending the poll until 2008-05-27 (May 27 2008).
> 
> Loa and George
> 
> Loa Andersson wrote:
>> All,
>>
>> the authors of
>>
>> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
>>
>> has requested that the document becomes a working group document.
>>
>> This is to start a two week poll on the mpls wg mailing list.
>>
>> Please send your comments to the mailing list; we are explicitly
>> soliciting both negative and positive comments.
>>
>>
>> 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.nu
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From mpls-bounces@ietf.org  Wed May 28 15:08:52 2008
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 10F113A6AA1;
	Wed, 28 May 2008 15:08:52 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 021443A6AA1
	for <mpls@core3.amsl.com>; Wed, 28 May 2008 15:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.489
X-Spam-Level: 
X-Spam-Status: No, score=-5.489 tagged_above=-999 required=5 tests=[AWL=1.110, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3723eryBQjWG for <mpls@core3.amsl.com>;
	Wed, 28 May 2008 15:08:49 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id A9C5E3A682A
	for <mpls@ietf.org>; Wed, 28 May 2008 15:08:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,557,1204520400"; 
   d="scan'208";a="9489926"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 28 May 2008 18:08:58 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4SM8wNl008004; 
	Wed, 28 May 2008 18:08:58 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4SM8w2R007821;
	Wed, 28 May 2008 22:08:58 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 May 2008 18:08:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 28 May 2008 18:07:21 -0400
Message-ID: <15B86BC7352F864BB53A47B540C089B6058C64EF@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <483DA329.3000704@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document -
	concluded
Thread-Index: AcjA8RQkr4YyiMgoTFyOAdcbdjIGYAAHd6wg
References: <481C670F.8090803@pi.se> <48316C20.2060708@pi.nu>
	<483DA329.3000704@pi.nu>
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>
X-OriginalArrivalTime: 28 May 2008 22:08:58.0258 (UTC)
	FILETIME=[6D4E5720:01C8C10F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2134; t=1212012538;
	x=1212876538; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rajiva@cisco.com;
	z=From:=20=22Rajiv=20Asati=20(rajiva)=22=20<rajiva@cisco.com >
	|Subject:=20RE=3A=20[mpls]=20draft-asati-mpls-ldp-end-of-li
	b-01.txt=20as=20wg=20document=20-=20concluded |Sender:=20
	|To:=20=22Loa=20Andersson=22=20<loa@pi.nu>,=20<mpls@ietf.or g>;
	bh=vNvZlnLDo1KzIj2+/q+C3JyWaycdG+9WyNvQr7aZrkk=;
	b=eGfbyzaG6pP7JH8lQRW4zz9WMmm0Fjj07Yij8mBQt3JCmdixTjqtDw2Pnd
	kq/nn24hjH/abwobXEmUfTTPJ3b4isSzhk70FjlzRn9MnebW6mxnj3iSRtdO
	4GZ5CBVkw4;
Authentication-Results: rtp-dkim-1; header.From=rajiva@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as wg document -
	concluded
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Hi Loa,

Will publish the draft-ietf-.... by next week (will include minor
updates as well). Thanks.

Cheers,
Rajiv 

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Loa Andersson
> Sent: Wednesday, May 28, 2008 2:24 PM
> To: mpls@ietf.org
> Cc: Ross Callon; David Ward
> Subject: Re: [mpls] draft-asati-mpls-ldp-end-of-lib-01.txt as 
> wg document - concluded
> 
> All,
> 
> much better response, and we have seen good support for making
> this a wg document.
> 
> Could the authors please republish the draft as
> 
> draft-ietf-mpls-ldp-end-of-lib-00
> 
> Loa and George
> 
> Loa Andersson wrote:
> > All,
> > 
> > this two week poll resulted in no responses :( !
> > 
> > This is surprising - since we had a good support for the
> > document at the wg meeting.
> > 
> > I don't if the lack of response is because I chose a bad
> > subject-line, or because I've had quite a bit of problems
> > with my email-address or because lack of interest.
> > 
> > We are extending the poll until 2008-05-27 (May 27 2008).
> > 
> > Loa and George
> > 
> > Loa Andersson wrote:
> >> All,
> >>
> >> the authors of
> >>
> >> 
> http://tools.ietf.org/wg/mpls/draft-asati-mpls-ldp-end-of-lib-01.txt
> >>
> >> has requested that the document becomes a working group document.
> >>
> >> This is to start a two week poll on the mpls wg mailing list.
> >>
> >> Please send your comments to the mailing list; we are explicitly
> >> soliciting both negative and positive comments.
> >>
> >>
> >> 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.nu
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


