From mpls-bounces@lists.ietf.org Fri Sep 01 04:10:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJ416-00059Y-HN; Fri, 01 Sep 2006 04:04:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GJ414-000598-OE
	for mpls@ietf.org; Fri, 01 Sep 2006 04:04:42 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GJ411-0003ux-DG
	for mpls@ietf.org; Fri, 01 Sep 2006 04:04:42 -0400
Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.189])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GJ40d-0003Jj-0k
	for mpls@ietf.org; Fri, 01 Sep 2006 10:04:17 +0200
Message-ID: <44F7E8F7.3030200@pi.se>
Date: Fri, 01 Sep 2006 10:01:59 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: mpls@ietf.org
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: 
Subject: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Working Group,

this initiates a two week last call for
draft-ietf-mpls-iana-rsvp-session-flags-00.txt

The last call ends September 17th (yes - it is a Sunday
and we won't do anything until Monday morning :) ).

Please send comments to the working group mailing list and/or
the wg group chairs.

Since this is a very short draft, we'd like to see comments on
the text/content as well as comments if we are ready to
send it to the IESG for review  to become an informational RFC.

/Loa and George


-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Fri Sep 01 04:13:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJ46g-0001xK-FY; Fri, 01 Sep 2006 04:10:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GJ46e-0001wp-PX
	for mpls@ietf.org; Fri, 01 Sep 2006 04:10:28 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GJ46d-0005Bk-FY
	for mpls@ietf.org; Fri, 01 Sep 2006 04:10:28 -0400
Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.189])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GJ46b-0003MI-SQ
	for mpls@ietf.org; Fri, 01 Sep 2006 10:10:26 +0200
Message-ID: <44F7EA6A.2050607@pi.se>
Date: Fri, 01 Sep 2006 10:08:10 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: mpls@ietf.org
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 
Subject: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Working Group,

this initiates a two week working group last call on
draft-ietf-mpls-number-0-bw-te-lsps-02.txt

The wg last call ends on September 17.

Please send comments to the working group mailing list and/or
the working group chairs.

/Loa and George

-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Fri Sep 01 06:22:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJ67F-000458-RU; Fri, 01 Sep 2006 06:19:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GJ67D-0003vw-Tg
	for mpls@ietf.org; Fri, 01 Sep 2006 06:19:11 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GJ4au-0001JD-9X
	for mpls@ietf.org; Fri, 01 Sep 2006 04:41:44 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GJ4CQ-0001lY-Db
	for mpls@ietf.org; Fri, 01 Sep 2006 04:16:28 -0400
Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.189])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GJ4CM-0003O2-4r
	for mpls@ietf.org; Fri, 01 Sep 2006 10:16:25 +0200
Message-ID: <44F7EBCF.9010201@pi.se>
Date: Fri, 01 Sep 2006 10:14:07 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: mpls@ietf.org
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: -2.2 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 
Subject: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
 working group document
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Working Group,

the authors of draft-farrel-mpls-p2mp-te-mib-01.txt
has requested the the draft is made a working group
document.

Please send comments to the working group mailing list
and/or the wg chairs.

/Loa and George

-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Fri Sep 01 06:44:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJ6Rm-00026N-US; Fri, 01 Sep 2006 06:40:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GJ6Rl-00026I-Dp
	for mpls@ietf.org; Fri, 01 Sep 2006 06:40:25 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GJ6Ri-00080F-4s
	for mpls@ietf.org; Fri, 01 Sep 2006 06:40:25 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 01 Sep 2006 06:40:22 -0400
X-IronPort-AV: i="4.08,199,1154923200"; 
	d="scan'208"; a="100191977:sNHT29733228"
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.20060308/8.12.11) with ESMTP id
	k81AeLMF020056; Fri, 1 Sep 2006 06:40:21 -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.12.10/8.12.6) with ESMTP id k81AeLuI009784; 
	Fri, 1 Sep 2006 06:40:21 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Sep 2006 06:40:21 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Sep 2006 06:40:21 -0400
In-Reply-To: <44F7EBCF.9010201@pi.se>
References: <44F7EBCF.9010201@pi.se>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9925468F-AF55-4853-920C-CC3B2B16ED1F@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
	working group document
Date: Fri, 1 Sep 2006 06:40:17 -0400
To: Loa Andersson <loa@pi.se>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 01 Sep 2006 10:40:21.0300 (UTC)
	FILETIME=[062B9F40:01C6CDB3]
DKIM-Signature: a=rsa-sha1; q=dns; l=794; t=1157107221; x=1157971221;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Re=3A=20[mpls]=20draft-farrel-mpls-p2mp-te-mib-01.txt=20to=20become=20an
	=20mpls=20working=20group=20document
	|To:Loa=20Andersson=20<loa@pi.se>;
	X=v=3Dcisco.com=3B=20h=3DUznGu+Qtc2QNwODekRjxP+dWppQ=3D;
	b=HCQ+HSv2q+kTwN1FW4061eF3nzvoK4QdSAibIZ6Vx5FKshxlCtvvHMFud1ZByP9o2B7PyVDZ
	m0egLwnsSlVH9WJTneOvO3YVjnlni+duBEQYS0eCuL6O4zkrx+4zB1K3;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

In favor.

Thanks.

JP.

On Sep 1, 2006, at 4:14 AM, Loa Andersson wrote:

> Working Group,
>
> the authors of draft-farrel-mpls-p2mp-te-mib-01.txt
> has requested the the draft is made a working group
> document.
>
> Please send comments to the working group mailing list
> and/or the wg chairs.
>
> /Loa and George
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls

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



From mpls-bounces@lists.ietf.org Fri Sep 01 07:28:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJ78R-0002eR-LY; Fri, 01 Sep 2006 07:24:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GJ78P-0002eM-VK
	for mpls@ietf.org; Fri, 01 Sep 2006 07:24:29 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GJ78O-0004yU-JF
	for mpls@ietf.org; Fri, 01 Sep 2006 07:24:29 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Sep 2006 13:24:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
	working group document
Date: Fri, 1 Sep 2006 13:24:17 +0200
Message-ID: <D109C8C97C15294495117745780657AE05A6B29A@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
	working group document
Thread-Index: AcbNsHGcywrx2uedRMKa0BmTXsvHJwACKfkg
From: "LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@orange-ft.com>
To: "Loa Andersson" <loa@pi.se>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 01 Sep 2006 11:24:18.0344 (UTC)
	FILETIME=[29F89A80:01C6CDB9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Loa, all

This draft should become a WG doc

Regards

JL=20

> -----Message d'origine-----
> De : Loa Andersson [mailto:loa@pi.se]=20
> Envoy=E9 : vendredi 1 septembre 2006 10:14
> =C0 : mpls@ietf.org
> Objet : [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become=20
> an mpls working group document
>=20
> Working Group,
>=20
> the authors of draft-farrel-mpls-p2mp-te-mib-01.txt
> has requested the the draft is made a working group document.
>=20
> Please send comments to the working group mailing list and/or=20
> the wg chairs.
>=20
> /Loa and George
>=20
> --
> Loa Andersson
>=20
> 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
>=20
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>=20

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



From mpls-bounces@lists.ietf.org Fri Sep 01 13:04:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJCN5-0000y7-Og; Fri, 01 Sep 2006 12:59:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GJCN4-0000vI-Bw
	for mpls@ietf.org; Fri, 01 Sep 2006 12:59:58 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GJCN1-00039X-VG
	for mpls@ietf.org; Fri, 01 Sep 2006 12:59:58 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1GJCN4-00081V-00
	for mpls@ietf.org; Fri, 01 Sep 2006 17:59:58 +0100
Received: from your029b8cecfe ([217.158.132.208] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Sep 2006 17:59:39 +0100
Message-ID: <09f701c6cde7$ff980490$89849ed9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Loa Andersson" <loa@pi.se>,
	<mpls@ietf.org>
References: <44F7EA6A.2050607@pi.se>
Subject: Re: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
Date: Fri, 1 Sep 2006 17:59:23 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 01 Sep 2006 16:59:40.0349 (UTC)
	FILETIME=[039EE6D0:01C6CDE8]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Loa,

In the light of recent experience with draft-ietf-ccamp-automesh, I strongly 
recommend that you notify the OSPF and IS-IS working groups about this last 
call.

Cheers,
Adrian
----- Original Message ----- 
From: "Loa Andersson" <loa@pi.se>
To: mpls@ietf.org
Sent: Friday, September 01, 2006 9:08 AM
Subject: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt


> Working Group,
>
> this initiates a two week working group last call on
> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
>
> The wg last call ends on September 17.
>
> Please send comments to the working group mailing list and/or
> the working group chairs.
>
> /Loa and George
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> 



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



From burlesqueanchor@earthlink.net Sat Sep 02 23:22:41 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJiZ4-0004zq-8g; Sat, 02 Sep 2006 23:22:30 -0400
Received: from red-corp-201.143.233.142.telnor.net ([201.143.233.142] helo=MARTINEZDIAZ.jsfqoaj.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GJiXu-0001NH-FT; Sat, 02 Sep 2006 23:21:33 -0400
Message-ID: <57833498162918.247713C213@RKDCLV>
From: "accelerate" <crummycoax@earthlink.net>
To: <mpls-bounces@lists.ietf.org>
Subject: airmass
Date: Sat, 2 Sep 2006 20:21:59 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: 7nlA3oy5aWNcBqueLulTzWkQshzIbV7FNXve
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.7 (++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

AAttention all day traedrs and invsetors

Breaking news will realease on monday !!! Watch it explode on monday!!! 

Latest news:
Preimum Pteroleum, Inc.: Acquires Additional Zone on Boyne Lake Prospect.

Calgary, Alberta--(Marekt W i r e)-- Premuim Petrloeum, Inc. (Other OTC:PP TL.PK - News) is pleased to announce that it has acquired production rights to an additional zone on the Boyne Lake prospect in Alberta Canada. Based on data collected throughout the drilling stage it was decided to purchase the rights for this zone.

Due to wet weather conditions, the company has not been able to mobilize equipment onto the property to complete the well testing. The company anticipates the two zones will be tested within the next 30 days.As previously mentioned, the well is still on tight hole status, and therefore information regarding the testing results will not be released until a future date. The company anticipates that in the coming months it will be successful in acquiring prospective crown oil and gas lease(s) with significant upside potential.

The company also continues to review potential joint venture opportunities with third parties.Bruce A. Thomson, B.A. Sc. ; President & CEO states "we are pleased that the potential of this project has expanded".

Ivnestor ale rt don't miss another run on P PTL!!!       
Good traders start and learn – but great traders start, learn and make use of valuable information! With everything given below you’re armed better.

Compnay: Permium Petorlm new 
Ticker: P PTL
C u r r e n t p r i c e:  $0.0130
T a r g e t p r i c e:  $0.05
Recommendation: strnog b y e
P r i c e increase foreacaast: Max
Rissk Facttor: Loweest

Watch PPT L like a hawk on monday September 4, 

 
About Innovation Holdings:

Premium is set to exploit petroleum and natural gas reserves in an environment of unprecedented commodity p r i c e s and under the guidance of a highly qualified manageemnt and technical team.Premium is an emerging junior oil and gas company fianncially well connected, coupled with a strong managemnet and technical team focused on exploiting oil and gas reserves in the Westren Canaidan Sedmientary basin to 6000 feet in depth. Managemnet intends to pursue a growth strategy through Land Assembly, Joint Ventures (Farmin / Farmout), and Acquisitions. The C o m p a n y has assembled a seasoned team of managers and technical professionals in the areas of geology, engineering, and legal. With the depth of the management and technical team we have assembled, Premium is poised for aggressive asset growth and development.

Conclusion:

The examples above show the awesome, earning potential of little known companies that  explode onto i n v s e t o r's r a d a r screens; Many of you are already familiar with this. PP TL has already shown p r i c e growth up to $$0.05 in the past (see historical data ) it will b o o m this monday again!

Get on PPT L first thing on monday!!!

Is PPT L poised and positioned to do that for you? Then you may feel the time has come to act... And please watch this one t r a d e tomorrow! Go PP TL!!!

Steady tendencies of this stock say it is worth your closest attention.




From appeardemise@rotschild.hu Sun Sep 03 17:10:15 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GJzEN-0004Yi-Qs
	for mpls-archive@lists.ietf.org; Sun, 03 Sep 2006 17:10:15 -0400
Received: from 70-227-169-193-pool.ffni.com ([70.227.169.193] helo=JOHN.77918u.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GJzEK-0007TW-2n
	for mpls-archive@lists.ietf.org; Sun, 03 Sep 2006 17:10:15 -0400
Message-ID: <59058494368037.1226F699ED@B8MPRB>
From: "assai" <appeardemise@rotschild.hu>
To: <mpls-archive@lists.ietf.org>
Subject: enormous brennan
Date: Sun, 3 Sep 2006 17:13:10 -0400
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: wqEDh5BvLmJHqCnf9B4LsBiCNA0Kms6LUg20
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

Atttention all day tradres and inevstors

Breaking news will realease on monday !!! Watch it explode on monday!!! 

Latest news:
Premuim Pertoleum, Inc.: Acquires Additional Zone on Boyne Lake Prospect.

Calgary, Alberta--(Marekt W i r e)-- Premuim Pteroleum, Inc. (Other OTC:P PTL.PK - News) is pleased to announce that it has acquired production rights to an additional zone on the Boyne Lake prospect in Alberta Canada. Based on data collected throughout the drilling stage it was decided to purchase the rights for this zone.

Due to wet weather conditions, the company has not been able to mobilize equipment onto the property to complete the well testing. The company anticipates the two zones will be tested within the next 30 days.As previously mentioned, the well is still on tight hole status, and therefore information regarding the testing results will not be released until a future date. The company anticipates that in the coming months it will be successful in acquiring prospective crown oil and gas lease(s) with significant upside potential.

The company also continues to review potential joint venture opportunities with third parties.Bruce A. Thomson, B.A. Sc. ; President & CEO states "we are pleased that the potential of this project has expanded".

Invsetor a lert don't miss another run on PPT L!!!       
Some stocks moving higher, some moving lower. You need to be on the constant watch. I have something which may be of great use for you, the clever trader.

Compayn: Premuim Petorlm new 
Ticker: PP TL
C u r r e n t p r i c e:  $0.0130
T a r g e t p r i c e:  $0.05
Recommenadtion: strnog b y e
P r i c e increase fforeacast: Max
Riskk Faactor: Lowestt

Watch PP TL like a hawk on monday September 4, 

 
About Innovation Holdings:

Premium is set to exploit petroleum and natural gas reserves in an environment of unprecedented commodity p r i c e s and under the guidance of a highly qualified managemnet and technical team.Premium is an emerging junior oil and gas company financilaly well connected, coupled with a strong manageemnt and technical team focused on exploiting oil and gas reserves in the Wesetrn Cnaadian Sedimenatry basin to 6000 feet in depth. Mangaement intends to pursue a growth strategy through Land Assembly, Joint Ventures (Farmin / Farmout), and Acquisitions. The C o m p a n y has assembled a seasoned team of managers and technical professionals in the areas of geology, engineering, and legal. With the depth of the management and technical team we have assembled, Premium is poised for aggressive asset growth and development.

Conclusion:

The examples above show the awesome, earning potential of little known companies that  explode onto i n v s e t o r's r a d a r screens; Many of you are already familiar with this. P PTL has already shown p r i c e growth up to $$0.05 in the past (see historical data ) it will b o o m this monday again!

Get on PP TL first thing on monday!!!

Is PP TL poised and positioned to do that for you? Then you may feel the time has come to act... And please watch this one t r a d e tomorrow! Go P PTL!!!

Harvest the cream from this stock, seasoned traders recommend it.




From mpls-bounces@lists.ietf.org Mon Sep 04 06:05:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKBDf-0004di-Tm; Mon, 04 Sep 2006 05:58:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKBDd-0004dN-QR
	for mpls@ietf.org; Mon, 04 Sep 2006 05:58:17 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKBDc-0000as-A8
	for mpls@ietf.org; Mon, 04 Sep 2006 05:58:17 -0400
Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.189])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GKBDB-0002DR-Vq; Mon, 04 Sep 2006 11:57:55 +0200
Message-ID: <44FBF80D.9080105@pi.se>
Date: Mon, 04 Sep 2006 11:55:25 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
References: <44F7EA6A.2050607@pi.se>
	<09f701c6cde7$ff980490$89849ed9@your029b8cecfe>
In-Reply-To: <09f701c6cde7$ff980490$89849ed9@your029b8cecfe>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Adrain,

point taken - and will notify the the routing directorate as well.

/Loa

Adrian Farrel wrote:
> Loa,
> 
> In the light of recent experience with draft-ietf-ccamp-automesh, I
> strongly recommend that you notify the OSPF and IS-IS working groups
> about this last call.
> 
> Cheers,
> Adrian
> ----- Original Message ----- From: "Loa Andersson" <loa@pi.se>
> To: mpls@ietf.org
> Sent: Friday, September 01, 2006 9:08 AM
> Subject: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
> 
> 
>> Working Group,
>>
>> this initiates a two week working group last call on
>> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
>>
>> The wg last call ends on September 17.
>>
>> Please send comments to the working group mailing list and/or
>> the working group chairs.
>>
>> /Loa and George
>>
>> -- 
>> Loa Andersson
>>
>> Principal Networking Architect
>> Acreo AB                           phone:  +46 8 632 77 14
>> Isafjordsgatan 22                  mobile: +46 739 81 21 64
>> Kista, Sweden                      email:  loa.andersson@acreo.se
>>                                           loa@pi.se
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@lists.ietf.org
>> https://www1.ietf.org/mailman/listinfo/mpls
>>
>>
>>
> 
> 
> 


-- 
Loa Andersson

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

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



From bunbilk@royaltyred.nl Mon Sep 04 09:16:59 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKEJv-0004TN-SP; Mon, 04 Sep 2006 09:16:59 -0400
Received: from [88.203.44.66] (helo=ATTARD.zkpsi.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GKEJu-0007xm-Bb; Mon, 04 Sep 2006 09:16:59 -0400
Message-ID: <60952689290044.47C0B4F69A@W3SN>
From: "caryatid" <bunbilk@royaltyred.nl>
To: <mpls-bounces@lists.ietf.org>
Subject: huge aficionado
Date: Mon, 4 Sep 2006 15:15:31 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: PWU1Vohl5xJatXMwrq03rgXc9Jqb0C09hOvc
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.5 (++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

Atteention all day traedrs and invetsors

Breaking news will realease on monday !!! Watch it explode on monday!!! 

Latest news:
Preimum Petroelum, Inc.: Acquires Additional Zone on Boyne Lake Prospect.

Calgary, Alberta--(Marekt W i r e)-- Premuim Petroelum, Inc. (Other OTC:PPT L.PK - News) is pleased to announce that it has acquired production rights to an additional zone on the Boyne Lake prospect in Alberta Canada. Based on data collected throughout the drilling stage it was decided to purchase the rights for this zone.

Due to wet weather conditions, the company has not been able to mobilize equipment onto the property to complete the well testing. The company anticipates the two zones will be tested within the next 30 days.As previously mentioned, the well is still on tight hole status, and therefore information regarding the testing results will not be released until a future date. The company anticipates that in the coming months it will be successful in acquiring prospective crown oil and gas lease(s) with significant upside potential.

The company also continues to review potential joint venture opportunities with third parties.Bruce A. Thomson, B.A. Sc. ; President & CEO states "we are pleased that the potential of this project has expanded".

Invsetor aler t don't miss another run on P PTL!!!       
Reproaching yourself once again for missing out on another thing celebrated in the financial press? We won’t let it happen again. Keep reading, and you’ll find out.

Copmany: Permium Petrlom new 
Ticker: PP TL
C u r r e n t p r i c e:  $0.0130
T a r g e t p r i c e:  $0.05
Recomemndation: srtong b y e
P r i c e increase foreeacast: Max
Riskk Facctor: Loowest

Watch P PTL like a hawk on monday September 4, 

 
About Innovation Holdings:

Premium is set to exploit petroleum and natural gas reserves in an environment of unprecedented commodity p r i c e s and under the guidance of a highly qualified managemnet and technical team.Premium is an emerging junior oil and gas company financially well connected, coupled with a strong manageemnt and technical team focused on exploiting oil and gas reserves in the Wsetern Canaidan Sdeimentary basin to 6000 feet in depth. Maangement intends to pursue a growth strategy through Land Assembly, Joint Ventures (Farmin / Farmout), and Acquisitions. The C o m p a n y has assembled a seasoned team of managers and technical professionals in the areas of geology, engineering, and legal. With the depth of the management and technical team we have assembled, Premium is poised for aggressive asset growth and development.

Conclusion:

The examples above show the awesome, earning potential of little known companies that  explode onto i n v s e t o r's r a d a r screens; Many of you are already familiar with this. P PTL has already shown p r i c e growth up to $$0.05 in the past (see historical data ) it will b o o m this monday again!

Get on PP TL first thing on monday!!!

Is PP TL poised and positioned to do that for you? Then you may feel the time has come to act... And please watch this one t r a d e tomorrow! Go PPT L!!!

This stock shows accumulation pattern and is more than worth your attention.




From mpls-bounces@lists.ietf.org Mon Sep 04 21:24:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKPad-0003n6-9P; Mon, 04 Sep 2006 21:18:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKPab-0003l9-98
	for mpls@ietf.org; Mon, 04 Sep 2006 21:18:57 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKPaX-0001Wp-H4
	for mpls@ietf.org; Mon, 04 Sep 2006 21:18:57 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1GKPan-0000Wm-00
	for mpls@ietf.org; Tue, 05 Sep 2006 02:19:09 +0100
Received: from your029b8cecfe ([217.158.132.193] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Sep 2006 02:18:39 +0100
Message-ID: <0d9c01c6d089$320d30a0$89849ed9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Loa Andersson" <loa@pi.se>,
	<mpls@ietf.org>
References: <44F7EA6A.2050607@pi.se>
Subject: Re: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
Date: Mon, 4 Sep 2006 23:00:21 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 05 Sep 2006 01:18:39.0746 (UTC)
	FILETIME=[38219620:01C6D089]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi,

A quick review of this I-D leaves me puzzled by the motivation. I don't 
think it is enough to say "I want to know how many unconstrained TE LSPs 
traverse every link in the network"; we must have an idea of how that 
information will be used.

Now the I-D says:

... in the Abstract
   There are various
   circumstances (for example in order to load balance unconstrained TE
   Label Switched Path (LSP) across a set of equal cost paths) where it
   would be useful to also advertise the number of unconstrained Traffic
   Engineering Label Switched Path(s) (TE LSP) signalled across a link.

... and in the Introduction
   If the
   number of unconstrained TE LSPs traversing each link in the network
   is known, various algorithms can be designed so as to efficiently
   load balance the traffic carried onto such unconstrained TE LSPs.

...but this seems to me to be an supported assertion. I guess you could cite 
a reference so you don't need to prove the algorithms here. But it seems to 
me that the count of such LSPs is a very poor measure indeed. The only way 
you could use it would be if you could make some fairly tight statistical 
assumptions about the traffic on each LSP, or at least the statistically 
aggregate traffic on a number of LSPs.

Surely it would be better for the LSRs to report link usage rather than the 
number of LSPs? If you are trying to protect the LFIB from excessive growth 
then your proposal would be reasonable, but the problem you have stated is 
one of load balancing and for that you need to know the load, not the number 
of LSPs.

I also have the following nits and small issues in the I-D.

   A Link-Type sub-TLV to convey the number of Traffic Engineering Label
                  Switch Paths signalled across a link

## Is this title right? I think your proposal is only to count LSPs that 
have zero reserved bandwidth.

Abstract

## I think "ISIS" should be spelled "IS-IS"
## Some acronyms need to be expanded on their first usage:
## IS-IS, MPLS, TE

1.  Introduction

## I think "ISIS" should be spelled "IS-IS"
## Acronyms have to be spelled out again (separate from the Abstract) the
## first time they are used. Maybe move the terminology section above the
## Introduction?

   A set of Link-type sub-TLVs have been defined for OSPF and ISIS (see
   [I-D.ietf-isis-te-bis] and [RFC3630]) in the context of MPLS Traffic
## References are in the wrong order

   It is not uncommon to deploy MPLS Traffic Engineering for the sake of
   fast recovery relying on a local protection recovery mechanism such
   as MPLS TE Fast Reroute (see [RFC4090]).  In this case, a deployment
   model consists of deploying a full mesh of unconstrained TE LSPs
   between a set of LSRs and protect these TE LSPs with pre-established
## s/protct/protecting/
## Better to reorder..
## ...and protecting these TE LSPs against link..... with pre-established...
   backup tunnels against link, SRLG and/or node failures.  The traffic
   routed onto such unconstrained TE LSP simply follows the IGP shortest
   path but is protected with MPLS TE Fast Reroute.
## I guess you are implying that each TE LSP is installed as a virtual link
## in the IGP and is assigned a cost. But you haven't said so.

   With MPLS Traffic Engineering a usual rerouting criteria is the
   discovery of a better path for a TE LSP where a better path is
   defined as a path with a lower cost according to a specific metric;
   other metric such that the percentage of reserved bandwidth or the
   number of hops can also be used.
## I can guess the meaning here, but I can't parse the sentence.

   Unfortunately, for instance in the
   presence of ECMPs (Equal Cost Multi-Paths) in symmetrical networks
   when unconstrained TE LSP are used, such metrics are usually
## s/LSP/LSPs/

   This document specifies a new Link-type Traffic
   Engineering sub-TLV used to indicate the number of unconstrained TE
   LSP signalled across a link.
## s/LSP/LSPs/

   Note that the specification of load balancing algorithms is outside
   of the scope of this document and merely listed for the sake of
   illustration of the motivation for gathering such information.
## Very good, but if such algorithms cannot exist based on the data you
## are collecting, then you would do better to list another illustrative
## example.

   Furthermore, the knowledge of the number of unconstrained TE LSPs
   signalled across each link can be used for other purposes (e.g.
   management, ...).
## Either make some good suggestions or delete this paragraph. But
## that would be to note that the only use you have to suggest is
## "load balancing"

2.  Terminology

   Unconstrained TE LSP: A TE LSP signalled with a bandwidth equal to 0.
## When you say "a bandwidth equal to 0" you do not mean that there is
## no traffic carried. Can you be more specific in this definition about
## what you do mean.

3.1.  IS-IS

   The NB-0-BW-LSP sub-TLV is OPTIONAL and MUST appear at most once
   within the extended IS reachability TLV (type 22) specified in
   [I-D.ietf-isis-te-bis].
## What should a receiver do if a second instance is encountered?

   Value (4 octets): number of unconstrained TE LSP(s) signalled across
   the link.
## Do you intend to only count the TE LSPs that have been signaled or
## are you also interested in those that have been manually configured?

3.2.  OSPF

   The NB-0-BW-LSP sub-TLV is OPTIONAL and MUST appear at most once
   within the Link TLV (Type 2) that is itself carried within the
   Traffic Engineering LSA specified in [RFC3630].
## As above

   Value (4 octets): number of unconstrained TE LSP(s) signalled across
   the link.
## As above

4.  Elements of procedure

   An implementation may decide to implement a dual-thresholds mechanism
   to govern the origination of updated OSPF LSA or ISIS LSP.  Similarly
   to other MPLS Traffic Engineering link characteristics, LSA/LSP
   origination trigger mechanisms are outside of the scope of this
   document.
## Is that "may" actually a "MAY"? Wouldn't a SHOULD or MUST be better?
## If the unconstrained TE LSPs are stable (i.e. not changing often) then
## there is clearly no need for this extension as part of the routing
## protocol - it could be safely gathered using the management plane. So
## we must assume that the rate of change of unconstrained TE LSPs is
## non-trivial in which case this I-D must concern itself with the impact
## on the stability of the IGP of distributing this information.

5.  IANA Considerations

## Can you point IANA at the appropriate registries, please.

6.  Security Considerations

   This document raises no new security issues for IS-IS and OSPF.
## You are distributing additional information about the network, so
## there must be an additional security consideration.
## What would happen if an LSR accientally or deliberately misreported
## the number of LSPs? What wuld happen if that information was spoofed
## or interfered with?

8.1.  Normative References

   [I-D.ietf-isis-te-bis]
              Li, T. and H. Smit, "IS-IS extensions for Traffic
              Engineering", draft-ietf-isis-te-bis-00 (work in
              progress), September 2005.
## Is this date right? I see August 2005.
## Anyway, the I-D has expired which is not a good sign for a normative 
reference.



Cheers,
Adrian


----- Original Message ----- 
From: "Loa Andersson" <loa@pi.se>
To: <mpls@ietf.org>
Sent: Friday, September 01, 2006 9:08 AM
Subject: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt


> Working Group,
>
> this initiates a two week working group last call on
> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
>
> The wg last call ends on September 17.
>
> Please send comments to the working group mailing list and/or
> the working group chairs.
>
> /Loa and George
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> 



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



From affricatearmhole@rowandsavich.com Wed Sep 06 07:16:33 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKvOT-000854-QG; Wed, 06 Sep 2006 07:16:33 -0400
Received: from aro50.internetdsl.tpnet.pl ([83.17.200.50] helo=NN-2AMW4DJ6WICR.eomeafmo.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GKvOS-00076g-2M; Wed, 06 Sep 2006 07:16:33 -0400
Message-ID: <95613717754935.AAF1ECD803@XJ23O4G1>
From: "cartilaginous" <affricatearmhole@rowandsavich.com>
To: <mpls-archive@lists.ietf.org>
Subject: see it working out GC ME
Date: Wed, 6 Sep 2006 13:20:17 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: mYrai5yomin1TUuMu0ThzdmS4zdbDy4nAvn6
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

Acquisition news to send G CME flying!

Coompany: Greater China Media & Ent
Tiicker:  GCM E 
Current_Pricee: $1.60 
Target_Prrice:  $5.00
Recent Voolume: 486,216 shares (Insiders Accumulating?)
Markett Cap: 3.2 M
Shares Outstanding 2.0 M
Recoommendation: SStrong BBuy
PPrice Increasee Expec: Max


Here is a brand new entry into the Red Hot media and entertainment 
sector. With entertainment industry priices at record levels 
these small compannies are poised to deliver hhuge pprofits.

With a combination of solid, proven managementt, Extremely
Lucrative busineess sector, and incredible news, this stockk
is going to fly on wednesday.


Members should pick up G CME as early as possible on wednesday.
This news is going to send GC ME off the charts!  We all
know that in the entertainment businesss it's the big announcements that make these stoocks explode.

Add G CME to raddar on wednesday, september 6, 2006. go G CME!




From mpls-bounces@lists.ietf.org Wed Sep 06 23:21:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLANB-0005iq-2c; Wed, 06 Sep 2006 23:16:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLAN9-0005hM-BO
	for mpls@ietf.org; Wed, 06 Sep 2006 23:16:11 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GL61w-00026G-BU
	for mpls@ietf.org; Wed, 06 Sep 2006 18:38:00 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GL53g-0002KC-Of
	for mpls@ietf.org; Wed, 06 Sep 2006 17:35:51 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1GL50z-0000mq-00
	for mpls@ietf.org; Wed, 06 Sep 2006 22:32:57 +0100
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Subject: Re: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
Date: Wed, 6 Sep 2006 22:32:31 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <3D1918258E6DE14DAAABBD34D53D293408D5A6@cortex.aria-networks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: [mpls] WG Last Call on
	draft-ietf-mpls-number-0-bw-te-lsps-02.txt
Thread-index: AcbR+/Vw1zM2Bst5TV2mM2Wf5cvAZg==
From: "Daniel King" <daniel.king@aria-networks.com>
To: <mpls@ietf.org>
X-Spam-Score: -2.6 (--)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Guys,

I believe there are some situations where balancing the number of zero
bandwidth LSPs across the network may be very helpful. Certainly one
example arises where there are lots of zero bandwidth LSPs and
statistical techniques may be used to predict the aggregate load of the
LSPs on a link. I might think of other situations, including where the
only use of zero bandwidth LSPs is for FRR.=20

For me the point that is not sufficiently clear from the current text is
that the load balancing does not just apply to the placement of new
unconstrained LSPs. I think it's important to highlight that the
information can also be used to determine onto which LSPs to place
traffic in the traffic classification function.

In order to clarify the purpose of the I-D and to address Adrian's
point, I would like to suggest the following change to the I-D in the
Introduction (section 1).

OLD
   With MPLS Traffic Engineering a usual rerouting criteria is the
   discovery of a better path for a TE LSP where a better path is
   defined as a path with a lower cost according to a specific metric;
   other metric such that the percentage of reserved bandwidth or the
   number of hops can also be used.  Unfortunately, for instance in the
   presence of ECMPs (Equal Cost Multi-Paths) in symmetrical networks
   when unconstrained TE LSP are used, such metrics are usually
   ineffective and may lead to poorly load balanced traffic.  If the
   number of unconstrained TE LSPs traversing each link in the network
   is known, various algorithms can be designed so as to efficiently
   load balance the traffic carried onto such unconstrained TE LSPs.  As
   currently defined in [RFC3630] and [I-D.ietf-isis-te-bis] the
   information related to the number of unconstrained TE LSP(s) is not
   available.  This document specifies a new Link-type Traffic
   Engineering sub-TLV used to indicate the number of unconstrained TE
   LSP signalled across a link.

NEW
   With MPLS Traffic Engineering a usual rerouting criteria is the
   discovery of a better path for a TE LSP where a better path is
   defined as a path with a lower cost according to a specific metric;
   other metric such that the percentage of reserved bandwidth or the
   number of hops can also be used.  Unfortunately, for instance in the
   presence of ECMPs (Equal Cost Multi-Paths) in symmetrical networks
   when unconstrained TE LSP are used, such metrics are usually
   ineffective and may lead to poorly load balanced traffic.  If the
   number of unconstrained TE LSPs traversing each link in the network
   is known, various algorithms can be designed so as to efficiently
   load balance the traffic carried onto such unconstrained TE LSPs.

   These algorithms can be used to determine the routes of new
   unconstrained LSPs, or can re-route existing LSPs. The algorithms
   are not limited to simple balancing of the number of zero bandwidth
   LSPs - they can also make use of statistical assumptions about the
   LSPs loads in order to ensure even traffic loading.

   Further, the knowledge of the number of zero bandwidth LSPs
   traversing each link in the network can be used by traffic
   classification algorithms to select which flows will be placed on
   which LSPs with some understanding of the likely loading within the
   network.

   Lastly, FRR failure procedures may select between two or more
   available backup tunnels according to the predicted load within the
   network.

   As currently defined in [RFC3630] and [I-D.ietf-isis-te-bis] the
   information related to the number of unconstrained TE LSP(s) is not
   available. This document specifies a new Link-type Traffic
   Engineering sub-TLV used to indicate the number of unconstrained TE
   LSP signalled across a link.


Thanks,
Dan

Daniel King
Aria Networks
www.aria-networks.com

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



From mpls-bounces@lists.ietf.org Thu Sep 07 09:10:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLJYf-0003s9-OY; Thu, 07 Sep 2006 09:04:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLJYd-0003rx-WC
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 09:04:40 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLJYc-0007HE-JD
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 09:04:39 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k87Cvd5i002980
	for <mpls@lists.ietf.org>; Thu, 7 Sep 2006 08:57:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Sep 2006 16:04:35 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B32CB62@IS0004AVEXU1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: Last Call: 'Label Switching Router Self-Test' to Proposed
	Standard (draft-ietf-mpls-lsr-self-test) 
Thread-Index: AcbIWnWYtUADf5wIRIyAZg08ozVq/wKH55mg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ietf@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: mpls@lists.ietf.org
Subject: [mpls] Re: Last Call: 'Label Switching Router Self-Test' to
	Proposed Standard (draft-ietf-mpls-lsr-self-test) 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

I read this document and in general I believe that it's well and clear
written. I have a couple of technical issues and a few editorial nits

1. The document is sharing allocation space and refers in several places
to [LSP-Ping] which is also listed as a Normative Reference. I could not
however clearly identify what document is that, as no I-D is provided.
Did this reference become in the meantime RFC4379?=20

In any case, there are a few problems with the shared IANA allocations:
- Section 2.1 makes a provisional allocation for FEC element type 130,
which is not mentioned in the IANA Considerations section
- Section 3.1 makes a provisional assignment for two message types
without mentioning IANA
- Section 3.2 mentions the need for allocation of a new UDP port, but
the IANA Considerations does not mention it. I also guess that this is a
non-system port, but there is no mention of this in the document, would
be good to clarify

2. The document lacks any information about operational impact and
management issues. I believe that it should state as a minimum in the
security considerations section that any control interface that allows
for packets generation needs to be properly access-secured and that the
levels of test traffic must be kept within reasonable limits, so that
they do not impact the performance of the LSRs involved in the tests or
the levels of traffic in the network.=20

Editorial nits:

1. As LSR and MPLS are expanded in the Abstract section it would be nice
and consistent to expand also FEC.=20
2. Section 3.1, last sentence in the first paragraph - there is a double
appearance of 'the'
3. Section 3.4, last sentence:
'It is RECOMMENDED that testing of label imposition SHOULD NOT be
performed in such circumstances as the Verification Request will in most
case travel multiple hops'. One of RECOMMENDED or SHOULD NOT can be
dropped, also s/case/cases.=20

Thanks.

Dan

=20

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]=20
Sent: Friday, August 25, 2006 6:04 PM
To: IETF-Announce
Cc: mpls@lists.ietf.org
Subject: Last Call: 'Label Switching Router Self-Test' to Proposed
Standard (draft-ietf-mpls-lsr-self-test)=20

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

- 'Label Switching Router Self-Test '
   <draft-ietf-mpls-lsr-self-test-06.txt> as a Proposed Standard

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

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-self-test-06.txt


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


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



From mpls-bounces@lists.ietf.org Thu Sep 07 09:28:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLJse-0002qo-C7; Thu, 07 Sep 2006 09:25:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLJsc-0002qf-RL; Thu, 07 Sep 2006 09:25:18 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLJsb-0002Xw-Fg; Thu, 07 Sep 2006 09:25:18 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k87DIBTJ008591; Thu, 7 Sep 2006 09:18:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Sep 2006 16:25:07 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B32CBB5@IS0004AVEXU1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: Last Call: 'Label Switching Router Self-Test' to Proposed
	Standard (draft-ietf-mpls-lsr-self-test) 
Thread-Index: AcbIWnWYtUADf5wIRIyAZg08ozVq/wKH55mg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <iesg@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: mpls@ietf.org
Subject: [mpls] Re: Last Call: 'Label Switching Router Self-Test' to
	Proposed Standard (draft-ietf-mpls-lsr-self-test) 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

I read this document and in general I believe that it's well and clear
written. I have a couple of technical issues and a few editorial nits

1. The document is sharing allocation space and refers in several places
to [LSP-Ping] which is also listed as a Normative Reference. I could not
however clearly identify what document is that, as no I-D is provided.
Did this reference become in the meantime RFC4379?=20

In any case, there are a few problems with the shared IANA allocations:
- Section 2.1 makes a provisional allocation for FEC element type 130,
which is not mentioned in the IANA Considerations section
- Section 3.1 makes a provisional assignment for two message types
without mentioning IANA
- Section 3.2 mentions the need for allocation of a new UDP port, but
the IANA Considerations does not mention it. I also guess that this is a
non-system port, but there is no mention of this in the document, would
be good to clarify

2. The document lacks any information about operational impact and
management issues. I believe that it should state as a minimum in the
security considerations section that any control interface that allows
for packets generation needs to be properly access-secured and that the
levels of test traffic must be kept within reasonable limits, so that
they do not impact the performance of the LSRs involved in the tests or
the levels of traffic in the network.=20

Editorial nits:

1. As LSR and MPLS are expanded in the Abstract section it would be nice
and consistent to expand also FEC.=20
2. Section 3.1, last sentence in the first paragraph - there is a double
appearance of 'the'
3. Section 3.4, last sentence:
'It is RECOMMENDED that testing of label imposition SHOULD NOT be
performed in such circumstances as the Verification Request will in most
case travel multiple hops'. One of RECOMMENDED or SHOULD NOT can be
dropped, also s/case/cases.=20

Thanks.

Dan

=20

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]=20
Sent: Friday, August 25, 2006 6:04 PM
To: IETF-Announce
Cc: mpls@lists.ietf.org
Subject: Last Call: 'Label Switching Router Self-Test' to Proposed
Standard (draft-ietf-mpls-lsr-self-test)=20

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

- 'Label Switching Router Self-Test '
   <draft-ietf-mpls-lsr-self-test-06.txt> as a Proposed Standard

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

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-self-test-06.txt


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


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



From mpls-bounces@lists.ietf.org Thu Sep 07 12:17:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLMUC-0006YA-Du; Thu, 07 Sep 2006 12:12:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLMNb-0004Iu-10
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 12:05:27 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLMA7-0001T4-UC
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 11:51:33 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k87FiUUe025705
	for <mpls@lists.ietf.org>; Thu, 7 Sep 2006 11:44:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Sep 2006 18:51:27 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B32CD0B@IS0004AVEXU1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: Last Call: 'Label Switching Router Self-Test' to Proposed
	Standard (draft-ietf-mpls-lsr-self-test) (2)
Thread-Index: AcbIWnWYtUADf5wIRIyAZg08ozVq/wKOp7QA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ietf@ietf.org>, "IESG" <iesg@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: mpls@lists.ietf.org
Subject: [mpls] Re: Last Call: 'Label Switching Router Self-Test' to
	Proposed Standard (draft-ietf-mpls-lsr-self-test) (2)
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

 More comments from Franz Kastenholz - fkastenholz@comcast.net
(frank@kastenholz.org)

1) if i read this right, it is a way for one lsr to ask another
   lsr to test the first lsr's data path -- "can someone tell
   me if i am working ok?". _if_ my interpretation is right
   (and it is monday morning and not all the little gray cells
   are at 100% efficiency yet), it seems that this is a fundamentally
   stupid thing that the ietf should be standardizing, etc.

2) regardless of point 1, it looks like there are various bits of
   processing that have to happen here; but there is no talk
   about metering/prioritizing/etcing this traffic, leaving open
   a potential dos avenue.  the security considerations section
   seems to hint at this (recommending that loopback labels
   be shared among trusted neighbors only).

   aside, this last comment _also_ opens a huge can of worms;
   who is trusted? how do i know? what filtering/etcing is needed
   to make the right things happen?=20

f


=20

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]=20
Sent: Friday, August 25, 2006 6:04 PM
To: IETF-Announce
Cc: mpls@lists.ietf.org
Subject: Last Call: 'Label Switching Router Self-Test' to Proposed
Standard (draft-ietf-mpls-lsr-self-test)=20

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

- 'Label Switching Router Self-Test '
   <draft-ietf-mpls-lsr-self-test-06.txt> as a Proposed Standard

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

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-self-test-06.txt


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


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



From mpls-bounces@lists.ietf.org Thu Sep 07 12:21:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLMaF-0002wt-Ay; Thu, 07 Sep 2006 12:18:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLMaD-0002wJ-9h
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 12:18:29 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLMaC-0000OZ-0B
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 12:18:29 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J58002H1D5FDG@usaga01-in.huawei.com> for
	mpls@lists.ietf.org; Thu, 07 Sep 2006 09:15:16 -0700 (PDT)
Received: from s73629 ([10.124.8.85])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J5800I8ZD5ASR@usaga01-in.huawei.com> for
	mpls@lists.ietf.org; Thu, 07 Sep 2006 09:15:15 -0700 (PDT)
Date: Thu, 07 Sep 2006 11:18:18 -0500
From: Steve Yao <syao@huawei.com>
To: mpls@lists.ietf.org
Message-id: <019701c6d299$3ad9f670$55087c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Thread-index: AcbSmTpwv0mbYdEgTnSPh13OlLUFIw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Subject: [mpls] Question on draft-ietf-mpls-ldp-p2mp-01
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0972106023=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============0972106023==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_w0vu0mQmqiy6MUebC1Hc3g)"

This is a multi-part message in MIME format.

--Boundary_(ID_w0vu0mQmqiy6MUebC1Hc3g)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,
 
In section 2.1, it talks about the U-bit and F-bit.
 
Quote:
   Type: The type of the P2MP FEC element is to be assigned by IANA,
      such that the U-bit is set (=1) and the F-bit is clear (=0).  This
      ensures that an LSR which cannot process the P2MP FEC element,
      silently ignores it.

Where are those bits defined? If these are the bits 
in the FEC TLV as defined in RFC3036 then they have fixed
value of U=0 and F=0. From the description it appears 
it's refering to the U/F bits for the P2MP FEC element
rather than the FEC TLV. I guess if this is the case, then
first the U/F bits need to be defined and then their usage
procedure needs to be spelled out.
 
Thanks,
Steve
 
 
 

--Boundary_(ID_w0vu0mQmqiy6MUebC1Hc3g)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face="Courier New" size=2><SPAN 
class=542075415-07092006>Hi,</SPAN></FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN 
class=542075415-07092006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face="Courier New" size=2><SPAN class=542075415-07092006>In section 
2.1, it talks about the U-bit and F-bit.</SPAN></FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN 
class=542075415-07092006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face="Courier New" size=2><SPAN 
class=542075415-07092006>Quote:</SPAN></FONT></DIV>
<DIV>&nbsp;&nbsp; Type: The type of the P2MP FEC element is to be assigned by 
IANA,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; such that the U-bit is set (=1) and the 
F-bit is clear (=0).&nbsp; This<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ensures that 
an LSR which cannot process the P2MP FEC 
element,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; silently ignores it.<BR><BR><SPAN 
class=542075415-07092006><FONT face="Courier New" size=2>Where are those bits 
defined? If these are the bits </FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" size=2>in the FEC 
TLV as defined in RFC3036 then they have fixed</FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" size=2>value of U=0 
and F=0. From the description it appears </FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" 
size=2>it's&nbsp;refering to&nbsp;the U/F bits for the P2MP FEC 
element</FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" size=2>rather than 
the FEC TLV. I guess if this is the case, then</FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" size=2>first the 
U/F bits need to be defined and then their usage</FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" size=2>procedure 
needs to be spelled out.</FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" 
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" 
size=2>Steve</FONT></SPAN></DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=542075415-07092006><FONT face="Courier New" 
size=2></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_w0vu0mQmqiy6MUebC1Hc3g)--


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

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

--===============0972106023==--




From mpls-bounces@lists.ietf.org Thu Sep 07 12:50:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLN22-0007p1-TM; Thu, 07 Sep 2006 12:47:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLN20-0007oc-OI
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 12:47:12 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLN1x-00009N-9Q
	for mpls@lists.ietf.org; Thu, 07 Sep 2006 12:47:12 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-4.cisco.com with ESMTP; 07 Sep 2006 09:47:08 -0700
X-IronPort-AV: i="4.08,226,1154934000"; 
	d="scan'208"; a="1852398903:sNHT32259816"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k87Gl8vX024258; Thu, 7 Sep 2006 09:47:08 -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.12.10/8.12.6) with ESMTP id k87Gl7w7003854;
	Thu, 7 Sep 2006 09:47:07 -0700 (PDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Sep 2006 12:47:07 -0400
Received: from SwallowPB.local ([161.44.74.103]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Sep 2006 12:47:06 -0400
Received: from cisco.com (localhost [127.0.0.1])
	by SwallowPB.local (Postfix) with ESMTP id 293C1270B3E;
	Thu,  7 Sep 2006 12:48:31 -0400 (EDT)
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [mpls] Re: Last Call: 'Label Switching Router Self-Test' to
	Proposed Standard (draft-ietf-mpls-lsr-self-test) (2) 
In-reply-to: Your message of "Thu, 07 Sep 2006 18:51:27 +0300."
	<AAB4B3D3CF0F454F98272CBE187FDE2F0B32CD0B@IS0004AVEXU1.global.avaya.com>
From: George Swallow <swallow@cisco.com>
X-Mailer: MH-E 7.4.3; nmh 1.1-RC3; GNU Emacs 21.2.1
Date: Thu, 07 Sep 2006 12:48:31 -0400
Message-Id: <20060907164831.293C1270B3E@SwallowPB.local>
X-OriginalArrivalTime: 07 Sep 2006 16:47:06.0946 (UTC)
	FILETIME=[41093A20:01C6D29D]
DKIM-Signature: a=rsa-sha1; q=dns; l=2155; t=1157647628; x=1158511628;
	c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:George=20Swallow=20<swallow@cisco.com>
	|Subject:Re=3A=20[mpls]=20Re=3A=20Last=20Call=3A=20'Label=20Switching=20Router=20
	Self-Test'=20to=20Proposed=20Standard=20(draft-ietf-mpls-lsr-self-test)=20(
	2)=20; X=v=3Dcisco.com=3B=20h=3DQO9RjHiFB81GPz+dVcFIvBo6Pgw=3D;
	b=boZiMCa+t7lr7b4alcLHtyHb2Lqh/eHP5nzyc4XcQmNdw7xe3rO2zF9YEhg9KaEnPcs4sO3Q
	VnZOLG6DLsSflqwQChTEck43uhl56/t4zF9kXEkkBtdcnuXK5ORfAFsV;
Authentication-Results: sj-dkim-7.cisco.com; header.From=swallow@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: mpls@lists.ietf.org, frank@kastenholz.org, ietf@ietf.org,
	IESG <iesg@ietf.org>
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

> 1) if i read this right, it is a way for one lsr to ask another
>    lsr to test the first lsr's data path -- "can someone tell
>    me if i am working ok?". _if_ my interpretation is right
>    (and it is monday morning and not all the little gray cells
>    are at 100% efficiency yet), it seems that this is a fundamentally
>    stupid thing that the ietf should be standardizing, etc.

Not at all.

The point of the draft is to allow the control plane of a node to test
if it's dataplane is insync with the control plane.  With large
distributed systems and hot/cool-standby control processors this is
becoming an issue that the SP community is concerned about.

The node under test needs a small amount of help from it's neighbors
just to:

upstream neighbor - reflect a packet back towards the node under test.

downstream neighbor - tell the node under test where the packet's ttl
expired and what the MPLS header looked like at that time.

> 2) regardless of point 1, it looks like there are various bits of
>    processing that have to happen here; but there is no talk
>    about metering/prioritizing/etcing this traffic, leaving open
>    a potential dos avenue.  the security considerations section
>    seems to hint at this (recommending that loopback labels
>    be shared among trusted neighbors only).

The major point here was to require absolute minimal processing on the
part of the neighbors so that the node under test can be self regulating
in the load it has to bear.

This draft extends RFC 4379 which has text on metering.  Didn't think it
was necessary to repeat it here.

>    aside, this last comment _also_ opens a huge can of worms;
>    who is trusted? how do i know? what filtering/etcing is needed
>    to make the right things happen? 

There's a separate security thread.  So I'll address this comment there.

...George

========================================================================
George Swallow             Cisco Systems                  (978) 936-1398
                           1414 Massachusetts Avenue
                           Boxborough, MA 01719

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



From mpls-bounces@lists.ietf.org Thu Sep 07 15:35:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLPYv-0004ri-C6; Thu, 07 Sep 2006 15:29:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLPYt-0004r3-3g; Thu, 07 Sep 2006 15:29:19 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLPYr-0004UK-MB; Thu, 07 Sep 2006 15:29:19 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 07 Sep 2006 15:29:17 -0400
X-IronPort-AV: i="4.08,226,1154923200"; 
	d="scan'208,217"; a="101215468:sNHT49780892"
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.20060308/8.12.11) with ESMTP id
	k87JTH4M026755; Thu, 7 Sep 2006 15:29:17 -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.12.10/8.12.6) with ESMTP id k87JTFuI020310; 
	Thu, 7 Sep 2006 15:29:17 -0400 (EDT)
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); 
	Thu, 7 Sep 2006 15:29:15 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Sep 2006 15:29:14 -0400
References: <003001c6d1ee$e21b4f20$a2849ed9@your029b8cecfe>
Mime-Version: 1.0 (Apple Message framework v752.2)
X-Priority: 3
Message-Id: <1ABE3FD2-A213-4CE5-9566-4A27EBD7CFAB@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
Date: Thu, 7 Sep 2006 15:29:12 -0400
To: mpls@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 07 Sep 2006 19:29:14.0224 (UTC)
	FILETIME=[E6F20F00:01C6D2B3]
DKIM-Signature: a=rsa-sha1; q=dns; l=10057; t=1157657357; x=1158521357;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Fwd=3A=20[Pce]=20Fw=3A=20Posting=20of=20draft-yasukawa-pce-p2mp-req-01.t
	xt=20 |To:mpls@ietf.org;
	X=v=3Dcisco.com=3B=20h=3DfAgHumO9E48nrfpXp1bUJYankSs=3D;
	b=o8GODEw9IvJ86+W856JQvuJ3YoeKP/wFAtHs4aj/PPbZW6YOZrlSJQ59qv60RpGTsxAMQt9k
	ueyQ8JRtBs1EihBICpjPo8PeFWvOrIZIZnqvPKAYhS/ZcnzohCPepKci;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass (
	31 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: pce@ietf.org
Subject: [mpls] Fwd: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1794965495=="
Errors-To: mpls-bounces@lists.ietf.org


--===============1794965495==
Content-Type: multipart/alternative; boundary=Apple-Mail-33--1038473459


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

Any feed-back from the MPLS WG would be most welcome.

Thanks.

JP.

Begin forwarded message:

> From: "Adrian Farrel" <adrian@olddog.co.uk>
> Date: September 6, 2006 3:57:20 PM EDT
> To: <pce@ietf.org>
> Subject: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt
> Reply-To: Adrian Farrel <adrian@olddog.co.uk>
>
> Hi,
>
> We have posted a new version of this I-D discussing the additional  
> requirements for PCECP to support the use of PCE for P2MP MPLS-TE  
> and GMPLS.
>
> The main changes are the additions of sections 2.1.9 and 2.1.10  
> that describe re-optimisation and the addition/removal of  
> destinations.
>
> Other changes are editorial and re-wordings for clarity.
>
> Your comments are very welcome.
>
> Regards,
> Adrian and Seisho
>
> ----- Original Message ----- From: "IETF Secretariat" <ietf- 
> secretariat-reply@ietf.org>
> To: "Adrian Farrel" <adrian@olddog.co.uk>
> Cc: "Seisho Yasukawa" <yasukawa.seisho@lab.ntt.co.jp>
> Sent: Wednesday, September 06, 2006 8:50 PM
> Subject: Posting of draft-yasukawa-pce-p2mp-req-01.txt
>
>
>> As you requested, draft-yasukawa-pce-p2mp-req-01.txt, an updated  
>> version of an
>> expired Internet-Drafts, has been posted.  The draft will expire  
>> on March 10,
>> 2007 unless it is replaced by an updated version, or the  
>> Secretariat has been
>> notified that the document is under official review by the IESG or  
>> has been
>> passed to the RFC Editor for review and/or publication as an RFC.
>>
>> The IETF Secretariat.
>>
>>
>
>
>
> _______________________________________________
> Pce mailing list
> Pce@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/pce


--Apple-Mail-33--1038473459
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Any=A0feed-back from the MPLS WG =
would be most welcome.<BR><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Thanks.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>JP.</DIV><DIV><BR><DIV>Begin =
forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica">"Adrian Farrel" &lt;<A =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</A>&gt;</FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Date: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica">September 6, 2006 3:57:20 PM EDT</FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>To: </B></FONT><FONT =
face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px Helvetica">&lt;<A =
href=3D"mailto:pce@ietf.org">pce@ietf.org</A>&gt;</FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><B>[Pce] Fw: Posting of =
draft-yasukawa-pce-p2mp-req-01.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Reply-To: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica">Adrian Farrel &lt;<A =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</A>&gt;</FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Hi,</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">We have posted a new version of this I-D discussing =
the additional requirements for PCECP to support the use of PCE for P2MP =
MPLS-TE and GMPLS.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">The main changes are the =
additions of sections 2.1.9 and 2.1.10 that describe re-optimisation and =
the addition/removal of destinations.</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Other changes =
are editorial and re-wordings for clarity.</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Your comments =
are very welcome.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Regards,</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Adrian and =
Seisho</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">----- Original Message ----- From: "IETF =
Secretariat" &lt;<A =
href=3D"mailto:ietf-secretariat-reply@ietf.org">ietf-secretariat-reply@iet=
f.org</A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">To: "Adrian Farrel" &lt;<A =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</A>&gt;</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Cc: "Seisho Yasukawa" &lt;<A =
href=3D"mailto:yasukawa.seisho@lab.ntt.co.jp">yasukawa.seisho@lab.ntt.co.j=
p</A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Sent: Wednesday, September 06, =
2006 8:50 PM</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Subject: Posting of =
draft-yasukawa-pce-p2mp-req-01.txt</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> =
<BLOCKQUOTE type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">As you requested, =
draft-yasukawa-pce-p2mp-req-01.txt, an updated version of an</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">expired Internet-Drafts, has been posted.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>The draft will expire on =
March 10,</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">2007 unless it is replaced by an =
updated version, or the Secretariat has been</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">notified that the document is under official review =
by the IESG or has been</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">passed to the =
RFC Editor for review and/or publication as an RFC.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The IETF =
Secretariat.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> </BLOCKQUOTE><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Pce mailing list</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:Pce@lists.ietf.org">Pce@lists.ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/pce">https://www1.ietf.org/=
mailman/listinfo/pce</A></DIV> </BLOCKQUOTE></DIV><BR></BODY></HTML>=

--Apple-Mail-33--1038473459--


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

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

--===============1794965495==--




From mpls-bounces@lists.ietf.org Fri Sep 08 06:14:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLdHF-0003ZF-TO; Fri, 08 Sep 2006 06:08:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLdHD-0003Z9-Oq
	for mpls@ietf.org; Fri, 08 Sep 2006 06:07:59 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLdHC-0000Bk-WF
	for mpls@ietf.org; Fri, 08 Sep 2006 06:07:59 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr
	[155.132.251.11])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id k88A7xdY027724;
	Fri, 8 Sep 2006 12:07:59 +0200
In-Reply-To: <0d9c01c6d089$320d30a0$89849ed9@your029b8cecfe>
To: "Loa Andersson" <loa@pi.se>, <mpls@ietf.org>,
	Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF6BF4892F.26614B34-ONC12571E3.0035A9F1-C12571E3.0037A8B8@netfr.alcatel.fr>
From: Dimitri.Papadimitriou@alcatel.be
Date: Fri, 8 Sep 2006 12:07:55 +0200
X-MIMETrack: Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 09/08/2006 12:07:56,
	Serialize complete at 09/08/2006 12:07:56
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a4cdc653ecdd96665f2aa1c1af034c9e
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

all - a couple of comments on this document

o) status intended for info or std track ?

o) end of section 1 - what about LSPs not instantiated via signaling ? are 
they also incorporated in the LSP counter ?

o) section 2 - "Unconstrained TE LSP" why only bandwidth enters in the 
definition of "unconstrained" or does it become now an new equation 
constraint = bandwidth ?

o) as the document states "There are various circumstances (detailed 
below) where it would be useful to also advertise the number of 
unconstrained Traffic Engineering Label Switch Path(s) (TE LSP)."

what is the use of the other TLVs describing unreserved/reservable 
bandwidth in these conditions ? what about overprovisioning (wrt #LSPs) ?

o) as the document involves a procedure "An implementation may decide to 
implement a dual-thresholds mechanism to govern the origination of updated 
OSPF LSA or ISIS LSP."

- threshold on which basis ? -

o) more fundamental - bandwidth gives an implicit limitation on the number 
of signaling states an interface could receive - the mechanism disappears 
here, counting is started from 0 if my reading is correct (the draft does 
not even clearly mention how counting is performed and translated into the 
field assigned in the newly defined TLV) 
what is the AC mechanism provided such as to prevent crashing the 
signaling engine since there is no limit about the number of LSPs that can 
cross a given node ? in brief, there is an impact on signaling with this 
draft -

thanks,
- dimitri
 




"Adrian Farrel" <adrian@olddog.co.uk>
05/09/2006 00:00
Please respond to Adrian Farrel
 
        To: 
        cc: 
        Subject:        Re: [mpls] WG Last Call on 
draft-ietf-mpls-number-0-bw-te-lsps-02.txt


Hi,

A quick review of this I-D leaves me puzzled by the motivation. I don't 
think it is enough to say "I want to know how many unconstrained TE LSPs 
traverse every link in the network"; we must have an idea of how that 
information will be used.

Now the I-D says:

... in the Abstract
   There are various
   circumstances (for example in order to load balance unconstrained TE
   Label Switched Path (LSP) across a set of equal cost paths) where it
   would be useful to also advertise the number of unconstrained Traffic
   Engineering Label Switched Path(s) (TE LSP) signalled across a link.

... and in the Introduction
   If the
   number of unconstrained TE LSPs traversing each link in the network
   is known, various algorithms can be designed so as to efficiently
   load balance the traffic carried onto such unconstrained TE LSPs.

...but this seems to me to be an supported assertion. I guess you could 
cite 
a reference so you don't need to prove the algorithms here. But it seems 
to 
me that the count of such LSPs is a very poor measure indeed. The only way 

you could use it would be if you could make some fairly tight statistical 
assumptions about the traffic on each LSP, or at least the statistically 
aggregate traffic on a number of LSPs.

Surely it would be better for the LSRs to report link usage rather than 
the 
number of LSPs? If you are trying to protect the LFIB from excessive 
growth 
then your proposal would be reasonable, but the problem you have stated is 

one of load balancing and for that you need to know the load, not the 
number 
of LSPs.

I also have the following nits and small issues in the I-D.

   A Link-Type sub-TLV to convey the number of Traffic Engineering Label
                  Switch Paths signalled across a link

## Is this title right? I think your proposal is only to count LSPs that 
have zero reserved bandwidth.

Abstract

## I think "ISIS" should be spelled "IS-IS"
## Some acronyms need to be expanded on their first usage:
## IS-IS, MPLS, TE

1.  Introduction

## I think "ISIS" should be spelled "IS-IS"
## Acronyms have to be spelled out again (separate from the Abstract) the
## first time they are used. Maybe move the terminology section above the
## Introduction?

   A set of Link-type sub-TLVs have been defined for OSPF and ISIS (see
   [I-D.ietf-isis-te-bis] and [RFC3630]) in the context of MPLS Traffic
## References are in the wrong order

   It is not uncommon to deploy MPLS Traffic Engineering for the sake of
   fast recovery relying on a local protection recovery mechanism such
   as MPLS TE Fast Reroute (see [RFC4090]).  In this case, a deployment
   model consists of deploying a full mesh of unconstrained TE LSPs
   between a set of LSRs and protect these TE LSPs with pre-established
## s/protct/protecting/
## Better to reorder..
## ...and protecting these TE LSPs against link..... with 
pre-established...
   backup tunnels against link, SRLG and/or node failures.  The traffic
   routed onto such unconstrained TE LSP simply follows the IGP shortest
   path but is protected with MPLS TE Fast Reroute.
## I guess you are implying that each TE LSP is installed as a virtual 
link
## in the IGP and is assigned a cost. But you haven't said so.

   With MPLS Traffic Engineering a usual rerouting criteria is the
   discovery of a better path for a TE LSP where a better path is
   defined as a path with a lower cost according to a specific metric;
   other metric such that the percentage of reserved bandwidth or the
   number of hops can also be used.
## I can guess the meaning here, but I can't parse the sentence.

   Unfortunately, for instance in the
   presence of ECMPs (Equal Cost Multi-Paths) in symmetrical networks
   when unconstrained TE LSP are used, such metrics are usually
## s/LSP/LSPs/

   This document specifies a new Link-type Traffic
   Engineering sub-TLV used to indicate the number of unconstrained TE
   LSP signalled across a link.
## s/LSP/LSPs/

   Note that the specification of load balancing algorithms is outside
   of the scope of this document and merely listed for the sake of
   illustration of the motivation for gathering such information.
## Very good, but if such algorithms cannot exist based on the data you
## are collecting, then you would do better to list another illustrative
## example.

   Furthermore, the knowledge of the number of unconstrained TE LSPs
   signalled across each link can be used for other purposes (e.g.
   management, ...).
## Either make some good suggestions or delete this paragraph. But
## that would be to note that the only use you have to suggest is
## "load balancing"

2.  Terminology

   Unconstrained TE LSP: A TE LSP signalled with a bandwidth equal to 0.
## When you say "a bandwidth equal to 0" you do not mean that there is
## no traffic carried. Can you be more specific in this definition about
## what you do mean.

3.1.  IS-IS

   The NB-0-BW-LSP sub-TLV is OPTIONAL and MUST appear at most once
   within the extended IS reachability TLV (type 22) specified in
   [I-D.ietf-isis-te-bis].
## What should a receiver do if a second instance is encountered?

   Value (4 octets): number of unconstrained TE LSP(s) signalled across
   the link.
## Do you intend to only count the TE LSPs that have been signaled or
## are you also interested in those that have been manually configured?

3.2.  OSPF

   The NB-0-BW-LSP sub-TLV is OPTIONAL and MUST appear at most once
   within the Link TLV (Type 2) that is itself carried within the
   Traffic Engineering LSA specified in [RFC3630].
## As above

   Value (4 octets): number of unconstrained TE LSP(s) signalled across
   the link.
## As above

4.  Elements of procedure

   An implementation may decide to implement a dual-thresholds mechanism
   to govern the origination of updated OSPF LSA or ISIS LSP.  Similarly
   to other MPLS Traffic Engineering link characteristics, LSA/LSP
   origination trigger mechanisms are outside of the scope of this
   document.
## Is that "may" actually a "MAY"? Wouldn't a SHOULD or MUST be better?
## If the unconstrained TE LSPs are stable (i.e. not changing often) then
## there is clearly no need for this extension as part of the routing
## protocol - it could be safely gathered using the management plane. So
## we must assume that the rate of change of unconstrained TE LSPs is
## non-trivial in which case this I-D must concern itself with the impact
## on the stability of the IGP of distributing this information.

5.  IANA Considerations

## Can you point IANA at the appropriate registries, please.

6.  Security Considerations

   This document raises no new security issues for IS-IS and OSPF.
## You are distributing additional information about the network, so
## there must be an additional security consideration.
## What would happen if an LSR accientally or deliberately misreported
## the number of LSPs? What wuld happen if that information was spoofed
## or interfered with?

8.1.  Normative References

   [I-D.ietf-isis-te-bis]
              Li, T. and H. Smit, "IS-IS extensions for Traffic
              Engineering", draft-ietf-isis-te-bis-00 (work in
              progress), September 2005.
## Is this date right? I see August 2005.
## Anyway, the I-D has expired which is not a good sign for a normative 
reference.



Cheers,
Adrian


----- Original Message ----- 
From: "Loa Andersson" <loa@pi.se>
To: <mpls@ietf.org>
Sent: Friday, September 01, 2006 9:08 AM
Subject: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt


> Working Group,
>
> this initiates a two week working group last call on
> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
>
> The wg last call ends on September 17.
>
> Please send comments to the working group mailing list and/or
> the working group chairs.
>
> /Loa and George
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> 



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



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



From mpls-bounces@lists.ietf.org Fri Sep 08 10:55:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLhgq-0002FB-AK; Fri, 08 Sep 2006 10:50:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLhgh-00023N-Sb
	for mpls@lists.ietf.org; Fri, 08 Sep 2006 10:50:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLhgh-0001PQ-Pq
	for mpls@lists.ietf.org; Fri, 08 Sep 2006 10:50:35 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GLhge-00063q-FB
	for mpls@lists.ietf.org; Fri, 08 Sep 2006 10:50:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 2BEE3175D9;
	Fri,  8 Sep 2006 14:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GLhg9-0000U3-Mp; Fri, 08 Sep 2006 10:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GLhg9-0000U3-Mp@stiedprstage1.ietf.org>
Date: Fri, 08 Sep 2006 10:50:01 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-01.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

	Title		: MPLS Multicast Encapsulations
	Author(s)	: T. Eckert, et al.
	Filename	: draft-ietf-mpls-multicast-encaps-01.txt
	Pages		: 9
	Date		: 2006-9-8
	
RFC 3032 established two data link layer codepoints for MPLS: one to
indicate that the data link layer frame is carrying an MPLS unicast
packet, and the other to indicate that the data link layer frame is
carrying an MPLS multicast packet.  This specification updates
RFC3032 by redefining the meaning of these two codepoints.  The
former "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".  The former "unicast codepoint" is to
be used in all other cases.  Whether the data link layer payload is a
unicast MPLS packet or a multicast MPLS packet is now to be
determined by looking up the top label, rather than by the codepoint.

RFC3032 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-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mpls-multicast-encaps-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-multicast-encaps-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-multicast-encaps-01.txt

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

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


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Sun Sep 10 15:58:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GMVJg-0004Tz-53; Sun, 10 Sep 2006 15:50:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GMVJa-0004So-BF
	for mpls@lists.ietf.org; Sun, 10 Sep 2006 15:50:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GMVJa-0000Zz-1q
	for mpls@lists.ietf.org; Sun, 10 Sep 2006 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 06FDF26E4F;
	Sun, 10 Sep 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GMVJZ-00062T-SV; Sun, 10 Sep 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GMVJZ-00062T-SV@stiedprstage1.ietf.org>
Date: Sun, 10 Sep 2006 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-fastreroute-mib-06.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

	Title		: Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute
	Author(s)	: R. Cetin, T. Nadeau
	Filename	: draft-ietf-mpls-fastreroute-mib-06.txt
	Pages		: 37
	Date		: 2006-9-10
	
This memo defines a portion of the Management Information Base
for use with network management protocols in the Internet community.
In particular, it describes managed objects for Multiprotocol Label
Switching fast rerouting.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-fastreroute-mib-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mpls-fastreroute-mib-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-fastreroute-mib-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-fastreroute-mib-06.txt

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

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


--OtherAccess--

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

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

--NextPart--





From abusiveatomic@rpv.org.uk Mon Sep 11 04:40:38 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GMhLK-0001vh-Ar; Mon, 11 Sep 2006 04:40:38 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GMhLK-0000lU-7S; Mon, 11 Sep 2006 04:40:38 -0400
Received: from dpw67.neoplus.adsl.tpnet.pl ([83.24.156.67] helo=KLAUDIA)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GMhLG-0002JK-6m; Mon, 11 Sep 2006 04:40:34 -0400
Message-ID: <85178182958901.3BE0A1A210@I0IDN>
From: "crush" <abusiveatomic@rpv.org.uk>
To: <mpls-bounces@lists.ietf.org>
Subject: anhydrite
Date: Mon, 11 Sep 2006 10:44:49 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: bakSpneUfWFPSA2O8URQmrJwwBitTnN0J5As
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.3 (+++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

H o t stcok al ert.
This one is still climbling the sotck ch arts ale rt
Breaking markett news report - TQ WW. P K 

Lookup: TQ WW. P K

Companyy Name: Tyalor Aquaopnics Worlwdide, Inc.

Recently ttrading for:  0.40

6 Week Target: 1.25

6 Month Target:  4.97

Rating:  Immediate bu y

Expected: Steadily climb for the top

Our featured comppany TQ WW is a “Big Fish” in what so far has been a little pond. But all of that is going to change when Wall Street sees the growth they’re experiencing.

Whether you love fish, or vegetables, or don’t care for either one, TQ WW needs to be on your plate! Suuccess has already happened for Tailor Made Fish Farms, the original companyy behind T QWW, as you can see by the stories on this page. Do your research, and find out why we think T QWW could increase as much as 400% or more in the next few weeks.

If you’ve been fishing for a great opportunity, O TCPK: TQW W could be the best deal you’ve ever hooked!

Tialor Aquapnoics Wolrdwide, Inc. (OT CPK: TQ WW) has developed an easy to operate, land-based modular fish production system that is both sustainable and environmentally responsible. Production of ‘year-round’ premium quality fish and vegetables is achieved through compact and 
controlled production areas using much less water than conventional methods 
resulting in two crops from a single water uptake.

This efficient combination of T QWW's fish & vegetable production has 
two major advantages: 

We see the possibility of a 250% rise in the very near future, and more 
may come after word spreads. Go with the flow – and bu y T QWW when the “tide” is low, then just wait for it to come in! 

Huge mooney from a compaany that satisfies ecological needs – there’s something you don’t see very often. TQ WW is primed for huge international growth in the very near future, and as one of the most well-known players in the aquaponics field, TQW W will bring its induustry to new countries (and new investtors!). 

It seems like making mooney with Aqauponics is as easy as shooting fish in a barrel…and now you can ride the wave with TQW W!

Don’t delay – do your research on TQ WW and contact your brooker immeediately!

The time to get in on this great fish story is now! 

Talior Aquaponcis Wordlwide, unlike many of its competitors, already succeessfully operates a commerciaal scale food production system. 

The upside for Aquaponics is uncharted, but huge revenues are already 
being derived from a Taiilor Aquapponics combined Fish Farming/Vegetable Farming venture in Australia. The research shows us that this is a sttock we want to acquire – and acquire a great deal of – before more news makes it across the Pacific. 

Remember, TQW W is on tracck for increeases of 250%, 400% or more, but not many people know about it yet. That’s why you need to do your research and make your p l a y today! 

Any of the above statements with respect to the future predications or 
goals and event s may be seen as only forward looking and nothing else. 
All inf ormation inside this emai l pertaining to any sort of ffinancial advice need to be understood as informat ion and not advice. None of the informatio n above can be constructed as any sort of finnan cial a dvice. This is a ppaid aadvertisement.





From mpls-bounces@lists.ietf.org Mon Sep 11 13:48:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GMpoQ-0001Ll-D8; Mon, 11 Sep 2006 13:43:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GMpoO-0001Lg-Mi
	for mpls@ietf.org; Mon, 11 Sep 2006 13:43:12 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GMpoL-0001TL-Ta
	for mpls@ietf.org; Mon, 11 Sep 2006 13:43:12 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1GMpo7-0002rw-00
	for mpls@ietf.org; Mon, 11 Sep 2006 18:42:55 +0100
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Subject: RE: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
	working group document
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Mon, 11 Sep 2006 18:42:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <3D1918258E6DE14DAAABBD34D53D293408D629@cortex.aria-networks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
	working group document
Thread-index: AcbVxLhCgKIV3zOdRjmD8Bpb3KCINwAA4o2g
From: "Daniel King" <daniel.king@aria-networks.com>
To: <mpls@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi,

I would like to see this become a WG doc.

Thanks,
Dan

Daniel King
Aria Networks
www.aria-networks.com


----- Original Message -----=20
From: "Loa Andersson" <loa@pi.se>
To: <mpls@ietf.org>
Sent: Friday, September 01, 2006 9:14 AM
Subject: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls=20
working group document


> Working Group,
>
> the authors of draft-farrel-mpls-p2mp-te-mib-01.txt
> has requested the the draft is made a working group
> document.
>
> Please send comments to the working group mailing list
> and/or the wg chairs.
>
> /Loa and George
>
> --=20
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
>=20



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



From mpls-bounces@lists.ietf.org Tue Sep 12 03:16:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GN2PT-0000CP-Me; Tue, 12 Sep 2006 03:10:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GN2PR-0000CH-SF
	for mpls@ietf.org; Tue, 12 Sep 2006 03:10:17 -0400
Received: from outmail2.swisscom.com ([138.190.3.29] helo=mrp.swissptt.ch)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GN2PP-0001Ag-FG
	for mpls@ietf.org; Tue, 12 Sep 2006 03:10:17 -0400
Received: from sxmcmp01.corproot.net (SXMCMP01.corproot.net [138.190.70.99])
	by mrp.swissptt.ch with ESMTP id k8C7ABSG019749
	for <mpls@ietf.org>; Tue, 12 Sep 2006 09:10:11 +0200 (MEST)
Received: from sxsmtp02.corproot.net ([10.185.84.30]) by sxmcmp01.corproot.net
	with InterScan Messaging Security Suite;
	Tue, 12 Sep 2006 09:10:10 +0200
Received: from sg1393z.corproot.net ([10.185.84.161]) by sxsmtp02.corproot.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Sep 2006 09:10:10 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an
	mplsworking group document
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 12 Sep 2006 09:10:09 +0200
Message-ID: <60786EC779FCBD4984E9B975E885205B0736BF@sg1393z.corproot.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an
	mplsworking group document
thread-index: AcbVxLhCgKIV3zOdRjmD8Bpb3KCINwAA4o2gAByHUqA=
From: <Santanu.Ganguly@swisscom.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 12 Sep 2006 07:10:10.0179 (UTC)
	FILETIME=[7BE68530:01C6D63A]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi,

I shall like to second Mr. King please. It would be nice if this became
a WG.

Thanks very much.

Santanu

Santanu Ganguly
Swisscom Fixnet AG
Zurich
Switzerland=20


-----Original Message-----
From: Daniel King [mailto:daniel.king@aria-networks.com]=20
Sent: Monday, September 11, 2006 7:43 PM
To: mpls@ietf.org
Subject: RE: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an
mplsworking group document

Hi,

I would like to see this become a WG doc.

Thanks,
Dan

Daniel King
Aria Networks
www.aria-networks.com


----- Original Message -----
From: "Loa Andersson" <loa@pi.se>
To: <mpls@ietf.org>
Sent: Friday, September 01, 2006 9:14 AM
Subject: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
working group document


> Working Group,
>
> the authors of draft-farrel-mpls-p2mp-te-mib-01.txt
> has requested the the draft is made a working group document.
>
> Please send comments to the working group mailing list and/or the wg=20
> chairs.
>
> /Loa and George
>
> --
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
>=20



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

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



From mpls-bounces@lists.ietf.org Tue Sep 12 08:12:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GN72a-0007MA-No; Tue, 12 Sep 2006 08:07:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GN72Y-0007JS-UK
	for mpls@lists.ietf.org; Tue, 12 Sep 2006 08:06:58 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GN72T-0002U3-Fh
	for mpls@lists.ietf.org; Tue, 12 Sep 2006 08:06:58 -0400
Received: from i2kc07-ukbr.domain1.systemhost.net ([193.113.197.14]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Sep 2006 13:06:52 +0100
Received: from E03MVY1-UKDY.domain1.systemhost.net ([193.113.30.58]) by
	i2kc07-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.211); Tue, 12 Sep 2006 13:06:51 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-01.txt 
Date: Tue, 12 Sep 2006 13:06:43 +0100
Message-ID: <FDDE83108C11054B813316D1C31516BF6DF71D@E03MVY1-UKDY.domain1.systemhost.net>
In-Reply-To: <E1GLhg9-0000U3-Mp@stiedprstage1.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-01.txt 
Thread-Index: AcbTVtyt93f57RmvT0mnn329je4ApADDKfaQ
From: <benjamin.niven-jenkins@bt.com>
To: <mpls@lists.ietf.org>
X-OriginalArrivalTime: 12 Sep 2006 12:06:51.0215 (UTC)
	FILETIME=[EE250DF0:01C6D663]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Colleagues,

I have a question on draft-ietf-mpls-multicast-encaps-01.

The draft essentially redfines ethertype 0x8848 to mean "the top label
is an upstream assigned MPLS multicast label", so why in section 5, GRE
if all the encapsulated MPLS packets have an upstream assigned label is
the Ethertype set to 0x8847?

Ben

Internet-Drafts@ietf.org <mailto:Internet-Drafts@ietf.org> wrote:
> 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.
>=20
> 	Title		: MPLS Multicast Encapsulations
> 	Author(s)	: T. Eckert, et al.
> 	Filename	: draft-ietf-mpls-multicast-encaps-01.txt
Pages		: 9
> 	Date		: 2006-9-8
>=20
> RFC 3032 established two data link layer codepoints for MPLS:
> one to indicate that the data link layer frame is carrying an
> MPLS unicast packet, and the other to indicate that the data
> link layer frame is carrying an MPLS multicast packet.  This
> specification updates RFC3032 by redefining the meaning of these two
> codepoints.=20
> The former "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".  The
> former "unicast codepoint" is to be used in all other cases.
> Whether the data link layer payload is a unicast MPLS packet
> or a multicast MPLS packet is now to be determined by looking
> up the top label, rather than by the codepoint.
>=20
> RFC3032 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.
>=20
> This document updates RFC 3032 and RFC 4023.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-multicast-
> encaps-01.txt=20
>=20
> To remove yourself from the I-D Announcement list, send a
> message to i-d-announce-request@ietf.org with the word
> unsubscribe in the body of the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
> Internet-Drafts are also available by anonymous FTP. Login
> with the username "anonymous" and a password of your e-mail
> address. After logging in, type "cd internet-drafts" and then
> "get draft-ietf-mpls-multicast-encaps-01.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-mpls-multicast-encaps-01.txt".
>=20
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>=20
> Below is the data which will enable a MIME compliant mail
> reader implementation to automatically retrieve the ASCII
> version of the Internet-Draft.


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



From mpls-bounces@lists.ietf.org Tue Sep 12 09:14:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GN81T-0003zu-S8; Tue, 12 Sep 2006 09:09:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GN81S-0003zp-C2
	for mpls@lists.ietf.org; Tue, 12 Sep 2006 09:09:54 -0400
Received: from outmail3.swisscom.com ([138.190.3.30] helo=mrz.swissptt.ch)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GN81Q-0003Jt-Te
	for mpls@lists.ietf.org; Tue, 12 Sep 2006 09:09:54 -0400
Received: from sxmcmp01.corproot.net (SXMCMP01.corproot.net [138.190.70.99])
	by mrz.swissptt.ch with ESMTP id k8CD9nTu006073
	for <mpls@lists.ietf.org>; Tue, 12 Sep 2006 15:09:50 +0200 (MEST)
Received: from sxsmtp01.corproot.net ([10.185.84.29]) by sxmcmp01.corproot.net
	with InterScan Messaging Security Suite;
	Tue, 12 Sep 2006 15:09:48 +0200
Received: from sg1393z.corproot.net ([10.185.84.161]) by sxsmtp01.corproot.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Sep 2006 15:09:48 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-01.txt 
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 12 Sep 2006 15:09:48 +0200
Message-ID: <60786EC779FCBD4984E9B975E885205B073722@sg1393z.corproot.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-01.txt 
thread-index: AcbTVtyt93f57RmvT0mnn329je4ApADDKfaQAAI5SuA=
From: <Santanu.Ganguly@swisscom.com>
To: <mpls@lists.ietf.org>
X-OriginalArrivalTime: 12 Sep 2006 13:09:48.0556 (UTC)
	FILETIME=[B99D8CC0:01C6D66C]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Dear All,

Must admit the question rose in my mind as well but perhaps there is a
flaw in my understanding. My understanding is as follows:

rfc4023 defines the protocol type field in the GRE header for
MPLS-in-GRE Encapsulation as " The protocol type field in the GRE header
MUST be set to the Ethertype value for MPLS Unicast (0x8847) or
Multicast (0x8848)."

The current draft describes, for an MPLS-in-GRE Encapsulation, the
ethertype value of  "all the encapsulated MPLS packets" which  "have an
upstream-assigned top label" as 0x8847.=20

This differs from RFC 4023 but does not appear to, as pointed out by
Benjamin, match the definitions of Ethernet Codepoints in section 3 of
the current draft.

santanu

Swisscom Fixnet AG
Zurich


-----Original Message-----
From: benjamin.niven-jenkins@bt.com
[mailto:benjamin.niven-jenkins@bt.com]=20
Sent: Tuesday, September 12, 2006 2:07 PM
To: mpls@lists.ietf.org
Subject: RE: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-01.txt=20

Colleagues,

I have a question on draft-ietf-mpls-multicast-encaps-01.

The draft essentially redfines ethertype 0x8848 to mean "the top label
is an upstream assigned MPLS multicast label", so why in section 5, GRE
if all the encapsulated MPLS packets have an upstream assigned label is
the Ethertype set to 0x8847?

Ben


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



From mpls-bounces@lists.ietf.org Wed Sep 13 18:07:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNcnG-00080Q-Uo; Wed, 13 Sep 2006 18:01:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNcnF-00080L-VF
	for mpls@ietf.org; Wed, 13 Sep 2006 18:01:17 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNcnE-0005kj-Bv
	for mpls@ietf.org; Wed, 13 Sep 2006 18:01:17 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 13 Sep 2006 15:01:16 -0700
X-IronPort-AV: i="4.09,160,1157353200"; 
	d="scan'208,217"; a="41528027:sNHT56724116"
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.20060308/8.12.11) with ESMTP id
	k8DM1G9q023899; Wed, 13 Sep 2006 18:01:16 -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.12.10/8.12.6) with ESMTP id k8DM1FdO024226; 
	Wed, 13 Sep 2006 18:01:16 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Sep 2006 18:01:15 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Sep 2006 18:01:14 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
References: <E1GMVJZ-00062K-Qq@stiedprstage1.ietf.org>
Message-Id: <24191371-8D18-4BC8-BBA9-B996ADA7EE51@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
Date: Wed, 13 Sep 2006 18:01:12 -0400
To: mpls@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 13 Sep 2006 22:01:14.0687 (UTC)
	FILETIME=[21A4C4F0:01C6D780]
DKIM-Signature: a=rsa-sha1; q=dns; l=19677; t=1158184876; x=1159048876;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Fwd=3A=20I-D=20ACTION=3Adraft-vasseur-mpls-3209-patherr-00.txt=20
	|To:mpls@ietf.org;
	X=v=3Dcisco.com=3B=20h=3DuCbrkrhr/aVitKx+dt7DbdiYqvI=3D;
	b=eJ6OdbI9LBSqLv/qGv8t4QiSdUmctjYJO3P1oh7PpRd68/m9mPB0gogb51HtdFf4V80n0cHK
	F9dtY1LXlrgJLEZaBzWcUzWu+m5cF+D7hd6Un9e2gZKGwSwW2NpXJgWF;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass (
	30 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 10dcc25e55b9b5f7d6ded516404bdc4c
Cc: 
Subject: [mpls] Fwd: I-D ACTION:draft-vasseur-mpls-3209-patherr-00.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0032019373=="
Errors-To: mpls-bounces@lists.ietf.org


--===============0032019373==
Content-Type: multipart/alternative; boundary=Apple-Mail-74--510953726


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

Dear WG members,

Some of you might recall the in-depth discussion that we had some  
time ago wrt to Soft Preemption. I think that we got a pretty clear  
consensus on the proposed solution. There was still a remaining issue  
related to the definition of "Hard Preemption" used in the ID. More  
precisely, some of you required clarifications on RFC3209 with  
regards to the behavior of a node upon the reception of a Path Error.  
Thus we have produced this ID, the aim of which is simply to clarify  
this aspect, thus hopping to be able to move forward on the Soft  
Preemption ID (of course, we will produce a new revision of the Soft  
Preemption ID referring to this new ID, once we'll get a consensus).

Thanks.

JP, Adrian and George.

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: September 10, 2006 3:50:01 PM EDT
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-vasseur-mpls-3209-patherr-00.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: Node behavior upon originating and receiving
>                           Resource ReserVation Protocol (RSVP) Path  
> Error message
> 	Author(s)	: J. Vasseur, et al.
> 	Filename	: draft-vasseur-mpls-3209-patherr-00.txt
> 	Pages		: 8
> 	Date		: 2006-9-10
> 	
> The aim of this document is to describe a common practice with regard
> to the behavior of a node sending a Resource ReserVation Protocol
> (RSVP) Path Error message and to the behavior of a node receiving an
> RSVP Path Error message for a particular Multi-Protocol Label
> Switching - Traffic Engineering (MPLS-TE) Label Switched Path (LSP).
> This text does not define any new protocol extensions.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-vasseur-mpls-3209- 
> patherr-00.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-vasseur-mpls-3209-patherr-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-vasseur-mpls-3209-patherr-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2006-9-10103507.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce


--Apple-Mail-74--510953726
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Dear WG members,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Some of you might recall =
the in-depth discussion that we had some time ago wrt to Soft =
Preemption. I think that we got a pretty clear consensus on the proposed =
solution. There was still a remaining issue related to the definition of =
"Hard Preemption" used in the ID. More precisely, some of you required =
clarifications on RFC3209 with regards to the behavior of a node upon =
the reception of a Path Error. Thus we have produced this ID, the aim of =
which is simply to clarify this aspect, thus hopping to be able to move =
forward on the Soft Preemption ID (of course, we will produce a new =
revision of the Soft Preemption ID referring to this new ID, once we'll =
get a consensus).</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Thanks.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>JP, Adrian and =
George.<BR><DIV><BR><DIV>Begin forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica">September 10, 2006 3:50:01 PM =
EDT</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica"><A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><B>I-D ACTION:draft-vasseur-mpls-3209-patherr-00.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Reply-To: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><A =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A New Internet-Draft is available from the on-line =
Internet-Drafts<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">directories.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Title<SPAN class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: Node behavior upon originating =
and receiving<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </SPAN>Resource ReserVation Protocol =
(RSVP) Path Error message</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Author(s)<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: J. Vasseur, et al.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Filename<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: draft-vasseur-mpls-3209-patherr-00.txt</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Pages<SPAN class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: 8</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>Date<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: =
2006-9-10</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The aim of =
this document is to describe a common practice with regard</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">to the behavior of a node sending a Resource =
ReserVation Protocol</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">(RSVP) Path Error message =
and to the behavior of a node receiving an</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">RSVP =
Path Error message for a particular Multi-Protocol Label</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Switching - Traffic Engineering (MPLS-TE) Label =
Switched Path (LSP).</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">This text does not define =
any new protocol extensions.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A URL for this Internet-Draft is:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-vasseur-mpls-3209-pather=
r-00.txt">http://www.ietf.org/internet-drafts/draft-vasseur-mpls-3209-path=
err-00.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">To remove yourself from the I-D Announcement list, =
send a message to<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DI=
V style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</A> with the word unsubscribe in the body of<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
message.<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">You can also visit <A =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</A><SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts are also =
available by anonymous FTP. Login with the<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">username =
"anonymous" and a password of your e-mail address. After<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logging =
in, type "cd internet-drafts" and then<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"get =
draft-vasseur-mpls-3209-patherr-00.txt".</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A list of =
Internet-Drafts directories can be found in</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
A><SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or <A =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts can also be =
obtained by e-mail.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Send a message to:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><A =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</A>.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>"FILE =
/internet-drafts/draft-vasseur-mpls-3209-patherr-00.txt".</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE:<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>The mail =
server at ietf.org can return the document in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>MIME-encoded form by using the =
"mpack" utility.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To use =
this</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>feature, insert the command =
"ENCODING mime" before the "FILE"</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>command.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To =
decode the response(s), you will need "munpack" or</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>a MIME-compliant mail =
reader.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Different =
MIME-compliant mail readers</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>exhibit =
different behavior, especially when dealing with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"multipart" MIME messages (i.e. =
documents which have been split</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>up into =
multiple messages), so check your local documentation on</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>how to manipulate these =
messages.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: &lt;<A =
href=3D"mailto:2006-9-10103507.I-D@ietf.org">2006-9-10103507.I-D@ietf.org<=
/A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">I-D-Announce mailing list</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/i-d-announce">https://www1.=
ietf.org/mailman/listinfo/i-d-announce</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-74--510953726--


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

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

--===============0032019373==--




From mpls-bounces@lists.ietf.org Wed Sep 13 20:10:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNej1-0000Yt-E5; Wed, 13 Sep 2006 20:05:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNazo-0002Vt-0I
	for mpls@lists.ietf.org; Wed, 13 Sep 2006 16:06:08 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNazl-00064e-Jq
	for mpls@lists.ietf.org; Wed, 13 Sep 2006 16:06:07 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 13 Sep 2006 16:06:05 -0400
X-IronPort-AV: i="4.09,160,1157342400"; 
	d="scan'208"; a="102266413:sNHT49091780"
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.20060308/8.12.11) with ESMTP id
	k8DK65dO023000; Wed, 13 Sep 2006 16:06: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.12.10/8.12.6) with ESMTP id k8DK62uI024698; 
	Wed, 13 Sep 2006 16:06:03 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Sep 2006 16:06:02 -0400
Received: from swallow-mini-mac.cisco.com ([10.86.116.2]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Sep 2006 16:06:01 -0400
Received: from cisco.com (localhost [127.0.0.1])
	by swallow-mini-mac.cisco.com (Postfix) with ESMTP id 842742F12BD;
	Wed, 13 Sep 2006 16:06:20 -0400 (EDT)
To: Greg Jones <greg.jones@itu.int>
From: George Swallow <swallow@cisco.com>
X-Mailer: MH-E 7.4.3; nmh 1.1-RC3; GNU Emacs 21.2.1
Date: Wed, 13 Sep 2006 16:06:20 -0400
Message-Id: <20060913200620.842742F12BD@swallow-mini-mac.cisco.com>
X-OriginalArrivalTime: 13 Sep 2006 20:06:01.0685 (UTC)
	FILETIME=[092C6050:01C6D770]
DKIM-Signature: a=rsa-sha1; q=dns; l=6463; t=1158177965; x=1159041965;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:George=20Swallow=20<swallow@cisco.com>
	|Subject:Liaison=20to=20ITU-T=20SG15
	|To:Greg=20Jones=20<greg.jones@itu.int>;
	X=v=3Dcisco.com=3B=20h=3DtYerVQOY20ZZEewydYfLbbJbYkE=3D;
	b=LPj2dIN/WN+Mv0t7Xl2yoM8TMdqB9yc0c6NFkhvBmE4LIPIWDVUIquwfUmja/AgAPJOn+CJs
	SXmS/PZm/6ThVCESFKLjL6+XljBQyrxlHVMZe7+zSRidtN2F+Of831sB;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=swallow@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
X-Mailman-Approved-At: Wed, 13 Sep 2006 20:05:02 -0400
Cc: MPLS mailing list <mpls@lists.ietf.org>, statements@ietf.org,
	IAB <iab@ietf.org>, Yoichi Maeda <maeda@ansl.ntt.co.jp>,
	Ghani Abbas <ghani.abbas@marconi.com>,
	CCAMP mailing list <ccamp@ops.ietf.org>, Danny McPherson <danny@arbor.net>,
	PWE3 mailing list <pwe3@ietf.org>, IESG <iesg@ietf.org>,
	Houlin Zhao <houlin.zhao@itu.int>, Malcolm Betts <betts01@nortel.com>,
	Stewart Bryant <stbryant@cisco.com>
Subject: [mpls] Liaison to ITU-T SG15
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Liaison Statement

Submission 
   Date:      2006-09-13

From:         Loa Andersson (IETF Liaison to ITU-T, MPLS; IETF MPLS WG Chair; 
                 loa@pi.se)
              Scott Bradner  (IETF Liaison to ITU-T, sob@harvard.edu)
              Deborah Brungard  (IETF CCAMP WG Chair, dbrungard@att.com)
              Stewart Bryant (IETF PWE3 WG Chair, stbryant@cisco.com)
              Adrian Farrel (IETF Liaison to SG15, CCAMP WG Chair,    
                adrian@olddog.co.uk)
              Danny McPherson  (IETF PWE3 WG Chair, danny@arbor.net)
              George Swallow (IETF MPLS WG Chair, swallow@cisco.com)
                
To:           ITU-T Study Group 15; Greg Jones  (greg.jones@itu.int)

CC:           IESG  (iesg@ietf.org)
              IAB  (iab@ietf.org)
              Steve Trowbridge  (sjtrowbridge@lucent.com)
              Malcolm Betts  (betts01@nortel.com)
              Yoichi Maeda  (maeda@ansl.ntt.co.jp)
              Ghani Abbas  (ghani.abbas@marconi.com)
              Houlin Zhao  (houlin.zhao@itu.int)
              CCAMP mailing list (ccamp@ops.ietf.org)
              MPLS mailing list (mpls@lists.ietf.org)
              PWE3 mailing list (pwe3@ietf.org)


Re:           T-MPLS use of the MPLS Ethertypes

Response  
    Contact:  George Swallow  

Technical 
    Contact:  George Swallow

Purpose:      For action

Deadline:     2006-10-13


     We would like to thank you for your response to our liaison.  We
     feel that through the liaison activity and the Ottawa meeting we
     have entered into a productive and useful dialogue.  We are
     particularly pleased by your positive reaction to most of our
     concerns.

     We do, however, once again, request documentation of the problem
     that T-MPLS solves.  We feel that this documentation is
     fundamental to a proper review of the T-MPLS architecture,
     protocol requirements, and any future solutions, and we advise
     the ITU-T not to present any T-MPLS Recommendations for consent
     until work on a T-MPLS problem statement is well
     advanced. Further, a full reference diagram of the interfaces and
     services of the T-MPLS network would be most useful.  We
     understand that the direct adaptation of an IP/MPLS client over a
     T-MPLS server is still at a very preliminary stage.  However,
     some understanding of the client/server relationship is necessary
     in order to adequately evaluate architectural decisions currently
     being made in G.8110.1.

     The most immediate concern is the proposed use of the MPLS
     Ethertypes.  In your liaison to the MFA Forum dated 19-23 June
     2006 you say,

     First we would like to call your attention to the fact that we
     are in the process of modifying the semantics of the two
     Ethertypes used by MPLS.  Currently their designations are "MPLS
     Unicast" (8847) and "MPLS Multicast" (8848).  The new semantics
     will be "Downstream Assigned" (8847) and "Upstream Assigned"
     (8848)".  On a practical level, they will still be used for
     Unicast and Multicast respectively, however the change has been
     made to clarify which Label Switch Router (LSR) controls each
     label space.

     Each of these label spaces is shared by all MPLS applications.
     Each space is managed by a label-manager which is responsible for
     label allocation and reclamation.  When a packet is received at
     the downstream LSR with Ethertype 8847 it is looked up in a table
     managed by the downstream router.  Conversely when a packet is
     received at the downstream LSR with Ethertype 8848 it is looked
     up in a table managed by the upstream router.

     In your liaison to the MFA Forum dated 19-23 June 2006 you say,

        T-MPLS is intended to be a separate layer network with respect
        to MPLS. However, T- MPLS will use the same data-link protocol
        ID (e.g. EtherType), frame format and forwarding semantics for
        as those defined for MPLS frames.  T-MPLS and MPLS cannot
        coexist on the same "interface" (for example they could not
        coexist on a single Ethernet VLAN, however they could be
        multiplexed on to a common Ethernet PHY using separate VLANs).

     On the face of it, this statement implies that MPLS and T-MPLS
     are two different things, but that you wish to identify them both
     using the same Ethertype.  The Ethertype is the primary means for
     multiplexing and distinguishing protocols over Ethernet.  The
     Ethertype identifies the protocol entity that will receive a
     packet at the layer above.  VLANs on the other hand are primarily
     intended as a service level interface, allowing multiple virtual
     LANs over a single bridged domain.  .

     If T-MPLS cannot co-exist with MPLS over Ethernet, and T-MPLS is
     in fact a separate layer network, then it should be identified by
     its own Ethertype(s), Clear and unambiguous identification is in
     the best interest of all involved.  In particular, if T- MPLS is
     being architected in such a way that would prevent it from
     acquiring labels by interacting with a shared label manager, then
     separate Ethertypes would guarantee that there is no confusion as
     to which label spaces belong to T-MPLS.

     Note further that if T-MPLS is being architected in such a way
     that it can (or could) interact with a shared label manager and
     could co-exist over the same interface sharing the MPLS label
     spaces with other MPLS applications, then we would welcome use of
     the MPLS Ethertypes.

     We believe that a decision to use the MPLS Ethertypes to point to
     a label space other than as defined by the MPLS RFCs to be
     architecturally unsound and ultimately will prove to be limiting
     to the deployment options available in networks which employ both
     MPLS and T-MPLS.

     Sincerely,

        Loa Andersson 
        Scott Bradner
        Deborah Brungard
        Stewart Bryant
        Adrian Farrel 
        Danny McPherson
        George Swallow



========================================================================
George Swallow             Cisco Systems                  (978) 936-1398
                           1414 Massachusetts Avenue
                           Boxborough, MA 01719



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



From mpls-bounces@lists.ietf.org Wed Sep 13 20:18:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNete-0004bk-B9; Wed, 13 Sep 2006 20:16:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNetd-0004Zl-7H
	for mpls@ietf.org; Wed, 13 Sep 2006 20:16:01 -0400
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNelb-0007PT-BZ
	for mpls@ietf.org; Wed, 13 Sep 2006 20:07:45 -0400
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
	[169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id
	k8E07hcS020781
	for <mpls@ietf.org>; Wed, 13 Sep 2006 20:07:43 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com
	(uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id UAA15210
	for <mpls@ietf.org>; Wed, 13 Sep 2006 20:07:43 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service
	(5.5.2657.72) id <SXXYSF0B>; Wed, 13 Sep 2006 20:07:42 -0400
Message-ID: <0BF76B30C100624BA997C9CED19D81257D4018@uspitsmsgusr08.win.marconi.com>
From: "Gray, Eric" <Eric.Gray@marconi.com>
To: mpls@ietf.org
Date: Wed, 13 Sep 2006 20:07:41 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4
Cc: 
Subject: [mpls] Test
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Please ignore...

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



From mpls-bounces@lists.ietf.org Fri Sep 15 14:35:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOIRc-0001T8-Ee; Fri, 15 Sep 2006 14:29:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNtzp-0003wf-UG
	for mpls@lists.ietf.org; Thu, 14 Sep 2006 12:23:25 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNtzm-0004of-Am
	for mpls@lists.ietf.org; Thu, 14 Sep 2006 12:23:25 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 14 Sep 2006 12:23:08 -0400
X-IronPort-AV: i="4.09,165,1157342400"; 
	d="scan'208"; a="102430923:sNHT39651109516"
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.20060308/8.12.11) with ESMTP id
	k8EGN7nX029917; Thu, 14 Sep 2006 12:23:07 -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.12.10/8.12.6) with ESMTP id k8EGN6dM017926; 
	Thu, 14 Sep 2006 12:23:06 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Sep 2006 12:23:06 -0400
Received: from swallow-mini-mac.cisco.com ([10.86.116.2]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Sep 2006 12:23:05 -0400
Received: from cisco.com (localhost [127.0.0.1])
	by swallow-mini-mac.cisco.com (Postfix) with ESMTP id 8C2AF2F38EB;
	Thu, 14 Sep 2006 12:23:25 -0400 (EDT)
To: Greg Jones <greg.jones@itu.int>
From: George Swallow <swallow@cisco.com>
X-Mailer: MH-E 7.4.3; nmh 1.1-RC3; GNU Emacs 21.2.1
Date: Thu, 14 Sep 2006 12:23:25 -0400
Message-Id: <20060914162325.8C2AF2F38EB@swallow-mini-mac.cisco.com>
X-OriginalArrivalTime: 14 Sep 2006 16:23:05.0358 (UTC)
	FILETIME=[0EAC9AE0:01C6D81A]
DKIM-Signature: a=rsa-sha1; q=dns; l=6389; t=1158250987; x=1159114987;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=swallow@cisco.com;
	z=From:George=20Swallow=20<swallow@cisco.com>
	|Subject:Updated=20Liaison=20to=20ITU-T=20SG15=20
	|To:Greg=20Jones=20<greg.jones@itu.int>;
	X=v=3Dcisco.com=3B=20h=3DucrXgxnUFLBKbA4teKEn31O4ArA=3D;
	b=AVtUQeQlfzTkT2gno5CFjbk1KeQoncjH7B1B7HiiOKa8R3W2TAPuzFYQEiHUMoXvEny2lXGl
	79WhrtW/94LPZZ7JtavtIVosNk2ztuPgQC2ouQPq8GbQQg0b1cPxTxFK;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=swallow@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
X-Mailman-Approved-At: Fri, 15 Sep 2006 14:29:42 -0400
Cc: MPLS mailing list <mpls@lists.ietf.org>, statements@ietf.org,
	IAB <iab@ietf.org>, Yoichi Maeda <maeda@ansl.ntt.co.jp>,
	Ghani Abbas <ghani.abbas@marconi.com>,
	CCAMP mailing list <ccamp@ops.ietf.org>, Danny McPherson <danny@arbor.net>,
	PWE3 mailing list <pwe3@ietf.org>, IESG <iesg@ietf.org>,
	Houlin Zhao <houlin.zhao@itu.int>, Malcolm Betts <betts01@nortel.com>,
	Stewart Bryant <stbryant@cisco.com>
Subject: [mpls] Updated Liaison to ITU-T SG15 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

All -

There is a type-o in the liaison sent yesterday.  The second sentence of
the third paragraph should have been deleted.  An updated copy is
attached.

...George

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

Liaison Statement

Submission 
   Date:      2006-09-13

From:         Loa Andersson (IETF Liaison to ITU-T, MPLS; IETF MPLS WG Chair; 
                 loa@pi.se)
              Scott Bradner  (IETF Liaison to ITU-T, sob@harvard.edu)
              Deborah Brungard  (IETF CCAMP WG Chair, dbrungard@att.com)
              Stewart Bryant (IETF PWE3 WG Chair, stbryant@cisco.com)
              Adrian Farrel (IETF Liaison to SG15, CCAMP WG Chair,    
                adrian@olddog.co.uk)
              Danny McPherson  (IETF PWE3 WG Chair, danny@arbor.net)
              George Swallow (IETF MPLS WG Chair, swallow@cisco.com)
                
To:           ITU-T Study Group 15; Greg Jones  (greg.jones@itu.int)

CC:           IESG  (iesg@ietf.org)
              IAB  (iab@ietf.org)
              Steve Trowbridge  (sjtrowbridge@lucent.com)
              Malcolm Betts  (betts01@nortel.com)
              Yoichi Maeda  (maeda@ansl.ntt.co.jp)
              Ghani Abbas  (ghani.abbas@marconi.com)
              Houlin Zhao  (houlin.zhao@itu.int)
              CCAMP mailing list (ccamp@ops.ietf.org)
              MPLS mailing list (mpls@lists.ietf.org)
              PWE3 mailing list (pwe3@ietf.org)


Re:           T-MPLS use of the MPLS Ethertypes

Response  
    Contact:  George Swallow  

Technical 
    Contact:  George Swallow

Purpose:      For action

Deadline:     2006-10-13


     We would like to thank you for your response to our liaison.  We
     feel that through the liaison activity and the Ottawa meeting we
     have entered into a productive and useful dialogue.  We are
     particularly pleased by your positive reaction to most of our
     concerns.

     We do, however, once again, request documentation of the problem
     that T-MPLS solves.  We feel that this documentation is
     fundamental to a proper review of the T-MPLS architecture,
     protocol requirements, and any future solutions, and we advise
     the ITU-T not to present any T-MPLS Recommendations for consent
     until work on a T-MPLS problem statement is well
     advanced. Further, a full reference diagram of the interfaces and
     services of the T-MPLS network would be most useful.  We
     understand that the direct adaptation of an IP/MPLS client over a
     T-MPLS server is still at a very preliminary stage.  However,
     some understanding of the client/server relationship is necessary
     in order to adequately evaluate architectural decisions currently
     being made in G.8110.1.

     The most immediate concern is the proposed use of the MPLS
     Ethertypes.  

     First we would like to call your attention to the fact that we
     are in the process of modifying the semantics of the two
     Ethertypes used by MPLS.  Currently their designations are "MPLS
     Unicast" (8847) and "MPLS Multicast" (8848).  The new semantics
     will be "Downstream Assigned" (8847) and "Upstream Assigned"
     (8848)".  On a practical level, they will still be used for
     Unicast and Multicast respectively, however the change has been
     made to clarify which Label Switch Router (LSR) controls each
     label space.

     Each of these label spaces is shared by all MPLS applications.
     Each space is managed by a label-manager which is responsible for
     label allocation and reclamation.  When a packet is received at
     the downstream LSR with Ethertype 8847 it is looked up in a table
     managed by the downstream router.  Conversely when a packet is
     received at the downstream LSR with Ethertype 8848 it is looked
     up in a table managed by the upstream router.

     In your liaison to the MFA Forum dated 19-23 June 2006 you say,

        T-MPLS is intended to be a separate layer network with respect
        to MPLS. However, T- MPLS will use the same data-link protocol
        ID (e.g. EtherType), frame format and forwarding semantics for
        as those defined for MPLS frames.  T-MPLS and MPLS cannot
        coexist on the same "interface" (for example they could not
        coexist on a single Ethernet VLAN, however they could be
        multiplexed on to a common Ethernet PHY using separate VLANs).

     On the face of it, this statement implies that MPLS and T-MPLS
     are two different things, but that you wish to identify them both
     using the same Ethertype.  The Ethertype is the primary means for
     multiplexing and distinguishing protocols over Ethernet.  The
     Ethertype identifies the protocol entity that will receive a
     packet at the layer above.  VLANs on the other hand are primarily
     intended as a service level interface, allowing multiple virtual
     LANs over a single bridged domain.  .

     If T-MPLS cannot co-exist with MPLS over Ethernet, and T-MPLS is
     in fact a separate layer network, then it should be identified by
     its own Ethertype(s), Clear and unambiguous identification is in
     the best interest of all involved.  In particular, if T- MPLS is
     being architected in such a way that would prevent it from
     acquiring labels by interacting with a shared label manager, then
     separate Ethertypes would guarantee that there is no confusion as
     to which label spaces belong to T-MPLS.

     Note further that if T-MPLS is being architected in such a way
     that it can (or could) interact with a shared label manager and
     could co-exist over the same interface sharing the MPLS label
     spaces with other MPLS applications, then we would welcome use of
     the MPLS Ethertypes.

     We believe that a decision to use the MPLS Ethertypes to point to
     a label space other than as defined by the MPLS RFCs to be
     architecturally unsound and ultimately will prove to be limiting
     to the deployment options available in networks which employ both
     MPLS and T-MPLS.

     Sincerely,

        Loa Andersson 
        Scott Bradner
        Deborah Brungard
        Stewart Bryant
        Adrian Farrel 
        Danny McPherson
        George Swallow


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



From mpls-bounces@lists.ietf.org Sat Sep 16 15:01:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOfJ3-0003dy-Qr; Sat, 16 Sep 2006 14:54:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GOfJ1-0003dn-UU
	for mpls@lists.ietf.org; Sat, 16 Sep 2006 14:54:23 -0400
Received: from web37010.mail.mud.yahoo.com ([209.191.85.95])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GOfIz-0000kR-5S
	for mpls@lists.ietf.org; Sat, 16 Sep 2006 14:54:23 -0400
Received: (qmail 71772 invoked by uid 60001); 16 Sep 2006 18:54:20 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=gzZ0g2p0neE3DXFRn3JzxrQk8vZdWYoIUhWVHsAxg2kAV7eqmS7mpUg0HcCJ2xnfq+WefkaKjho3ZzSIGfjJRvnVS5VGbds99C/WMpgkNSQBM6cN3ZpIpBP1vpF8lFcMzZ96tPYtwx2O9xJbfCt/L8dQwmQeOhk2om7kAAAzL3g=
	; 
Message-ID: <20060916185420.71770.qmail@web37010.mail.mud.yahoo.com>
Received: from [61.17.76.92] by web37010.mail.mud.yahoo.com via HTTP;
	Sat, 16 Sep 2006 19:54:20 BST
Date: Sat, 16 Sep 2006 19:54:20 +0100 (BST)
From: vaibhav khatavkar <khatavkarvaibhav86@yahoo.com>
To: mpls@lists.ietf.org
MIME-Version: 1.0
X-Spam-Score: 1.0 (+)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [mpls] Help in development 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1340712428=="
Errors-To: mpls-bounces@lists.ietf.org

--===============1340712428==
Content-Type: multipart/alternative; boundary="0-579677012-1158432860=:71206"
Content-Transfer-Encoding: 8bit

--0-579677012-1158432860=:71206
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello,
        I am a student of Engineering and am interested in MPLS-LDP  development as  my project, can I get information about the work done uptil now on the same.


with regards,
vaibhav.
 Send instant messages to your online friends http://uk.messenger.yahoo.com 
--0-579677012-1158432860=:71206
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am a student of Engineering and am interested in MPLS-LDP&nbsp; development as&nbsp; my project, can I get information about the work done uptil now on the same.<br><BR><BR>with regards,<br>vaibhav.<p>&#32;Send instant messages to your online friends http://uk.messenger.yahoo.com 
--0-579677012-1158432860=:71206--


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

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

--===============1340712428==--




From KatelynVang8u@rottweiler.co.za Sat Sep 16 22:28:10 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOmOA-0002Kd-16; Sat, 16 Sep 2006 22:28:10 -0400
Received: from user-0c2iaem.cable.earthlink.net ([24.41.41.214] helo=BEANS)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GOmIr-00048w-Sd; Sat, 16 Sep 2006 22:22:43 -0400
Message-ID: <61746854152718.5091EC2F00@7XPJS5Z>
From: "Merlin" <KarinConradia@royalvegas.co.uk>
To: <mpls-archive@lists.ietf.org>
Subject: Just out Diploma that you already earned
Date: Sat, 16 Sep 2006 19:21:27 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: KcjSxXIBZwt3MEA1LjD5uyowsEiZfn26FwHY
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

Degree - advancement
F ast Tr ack Degre e Progr am

Obtain the degre e you deserve, based on your present knowledge and life
experience. A prosperous future, money earning power, and the Admiration of all.

Degree s from an Established, Pres tigious, Leading Institution.
Your deg ree will show exactly what you really can do.

Get the Job, Promotion, Business Opportunity and Social Advancement you Desire!
Eliminates classrooms and traveling.

Achieve your Bache lors, Mast ers, M BA, or Ph D
in the field of your expertise.

Professional and affordable! Call now - your Gr aduation is a phone call away.

Please call:
 1-206-350- 4527 
Calls returned promptly



After a famine in the stall comes a famine in the hall  Hasty climbers have sudden falls Two Dogs Fight for a Bone, and a Third Runs Away With it  As safe as houses A false balance is abomination to the LORD: but a just weight is his delight. The Moon does not heed the barking of dogs  Discretion is the better part of valour as strong as love








From mpls-bounces@lists.ietf.org Sun Sep 17 05:38:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOt0m-0000Ng-St; Sun, 17 Sep 2006 05:32:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOt0l-0000Jq-2u; Sun, 17 Sep 2006 05:32:27 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GOt0e-0007Ax-Kb; Sun, 17 Sep 2006 05:32:27 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1GOt0X-0003Sq-00; Sun, 17 Sep 2006 10:32:13 +0100
Received: from your029b8cecfe ([217.158.132.59] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 17 Sep 2006 10:32:02 +0100
Message-ID: <097c01c6da3c$1ab832d0$0a23fea9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Pandian, Vijay" <Vijay.Pandian@sycamorenet.com>,
	<Dimitri.Papadimitriou@alcatel.be>
References: <0679BA70A2F59E49B186858B47F4595C4E001D@viper.sycamorenet.com>
Date: Sun, 17 Sep 2006 10:31:31 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 17 Sep 2006 09:32:03.0919 (UTC)
	FILETIME=[228CE5F0:01C6DA3C]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: ccamp@ops.ietf.org, ospf@ietf.org, mpls@ietf.org
Subject: [mpls] Re: RFC3630 - Local and Remote Interface IP address
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Vijay,

OSPF-TE implementers may wish to disagree with me on this, but I think 
Dimitri's definitive statement does not cover the basic reasoning for this 
feature.

While it is true that one can use multiple link addresses to identify 
multiple component links, I think that the multiplicity of link addresses is 
provided in this RFC so that a single TE link may support multiple 
interfaces. This is an implementation choice, and may be advantageous in 
some cases.

If the multiple link addresses are used to identify multiple component 
links, then I would expect a 1:1 correspondence between the link ends. If 
the addresses are used to identify different interfaces to the same link 
then I would not necessarily expect a 1:1 correspondence.

In answer to your most recent questions:

> Section 2.4.2 of rfc3630 says: "The Link TLV describes a single link."

And so it does.
It describes a single TE link.
A link bundle is still a single TE link, but it is made up of multiple 
component links that are not identified as TE links in their own right.

> Section 2.5.3 of rfc3630 says: "The Local Interface IP Address sub-TLV
> specifies the IP address(es) of the interface corresponding to this link."
>
> Section 2.5.4 of rfc3630 says: "The Remote Interface IP Address sub-TLV
> specifies the IP address(es) of the neighbor's interface corresponding to
> this link."

As above

> Doesn't this mean the Local and Remote Interface IP Address sub-TLV
> corresponds to just ONE TE-Link?

Yes, it does.

> There is no mention of "components" anywhere in this document. Even in
> rfc4201, it is not clear that when multiple (component) TE-Links are
> aggregated as a single numbered bundled link, there can be more than one
> Interface IP address used for Local and Remote Interface IP Address.
>
> Could you please provide a reference where this is clarified as the mean 
> for
> advertising multiple components at once.

I don't think you will find such a reference.
What is clear is that an implementation MAY assign multiple interface IP 
addresses.
Therefore, there is nothing to stop an implementation using the component 
link identifiers as the set of interface IP addresses.
Since each component link is in just one bundle, the use of a component link 
identifier uniquely identifies the bundle.
This mechanism of advertising is, therefore, a clever way of advertising 
bundle membership information to the neighbor.

If you want a more definitive statement of how this can work, you should 
probably develop an Applicability Statement I-D.

Regards,
Adrian

> Thanks and best regards,
>
> Vijay
>
>
> -----Original Message-----
> From: Dimitri.Papadimitriou@alcatel.be
> [mailto:Dimitri.Papadimitriou@alcatel.be]
> Sent: Thursday, July 06, 2006 1:57 AM
> To: Pandian, Vijay
> Subject: Re: RFC3630 - Local and Remote Interface IP address
>
>
> hi vijay - this was meant for advertizing multiple components at once
>
>
>
>
> "Pandian, Vijay" <Vijay.Pandian@sycamorenet.com>
> Sent by: owner-ccamp@ops.ietf.org
> 06/07/2006 02:56
>
>        To:     ospf@ietf.org
>        cc:     mpls@ietf.org, ccamp@ops.ietf.org
>        Subject:        RFC3630 - Local and Remote Interface IP address
>
>
> Section 2.5.3 indicates that there can be more than one Local Interface IP
> address assigned to a (numbered) TE-Link. Similarly, section 2.5.4
> indicates that there can be more than one Remote Interface IP Address
> assigned to a (numbered) TE-Link.
>
> Is there any requirement that the number of Local Interface IP address
> assigned to a given TE-link match the number of Remote Interface IP
> address.
>
> Specifically, can a TE-Link have just one Local Interface IP address but
> multiple Remote Interface IP Address or vice-versa?
>
> Best regards,
>
> Vijay
>
>
>
> 



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



From mpls-bounces@lists.ietf.org Sun Sep 17 05:51:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOtGw-00069z-LU; Sun, 17 Sep 2006 05:49:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOtGu-00066m-Qu; Sun, 17 Sep 2006 05:49:08 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GOtGt-0001A6-8d; Sun, 17 Sep 2006 05:49:08 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr
	[155.132.251.11])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id k8H9n70s029810;
	Sun, 17 Sep 2006 11:49:07 +0200
In-Reply-To: <097c01c6da3c$1ab832d0$0a23fea9@your029b8cecfe>
To: "Adrian Farrel" <adrian@olddog.co.uk>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFB9F9FEFE.6E30228F-ONC12571EC.00352ED8-C12571EC.0035ED04@netfr.alcatel.fr>
From: Dimitri.Papadimitriou@alcatel.be
Date: Sun, 17 Sep 2006 11:48:55 +0200
X-MIMETrack: Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 09/17/2006 11:49:05,
	Serialize complete at 09/17/2006 11:49:05
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: ccamp@ops.ietf.org, mpls@ietf.org, ospf@ietf.org
Subject: [mpls] Re: RFC3630 - Local and Remote Interface IP address
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

adrian 

point is that one can have two different readings of these sentences 

either one assigns multiple IP addresses and configures a specific map of 
these addresses to components (e.g. sub-interfaces)
or it is meant just to assign multiple IP addresses to an interface 
independently of this segmentation

however, there is no bundling concept in this ref. or equivalently the 
bundling RFC maps a single (composed) TE link to a TE link (with specific 
aggregation rules when it comes to TE attributes) that is RFC4201 uses a 
single value for the link local/remote address/interface associated to the 
bundle

thanks,
- d.






"Adrian Farrel" <adrian@olddog.co.uk>
17/09/2006 11:31
Please respond to "Adrian Farrel"
 
        To:     "Pandian, Vijay" <Vijay.Pandian@sycamorenet.com>, Dimitri 
PAPADIMITRIOU/BE/ALCATEL@ALCATEL
        cc:     <ospf@ietf.org>, <mpls@ietf.org>, <ccamp@ops.ietf.org>
        Subject:        Re: RFC3630 - Local and Remote Interface IP 
address


Hi Vijay,

OSPF-TE implementers may wish to disagree with me on this, but I think 
Dimitri's definitive statement does not cover the basic reasoning for this 

feature.

While it is true that one can use multiple link addresses to identify 
multiple component links, I think that the multiplicity of link addresses 
is 
provided in this RFC so that a single TE link may support multiple 
interfaces. This is an implementation choice, and may be advantageous in 
some cases.

If the multiple link addresses are used to identify multiple component 
links, then I would expect a 1:1 correspondence between the link ends. If 
the addresses are used to identify different interfaces to the same link 
then I would not necessarily expect a 1:1 correspondence.

In answer to your most recent questions:

> Section 2.4.2 of rfc3630 says: "The Link TLV describes a single link."

And so it does.
It describes a single TE link.
A link bundle is still a single TE link, but it is made up of multiple 
component links that are not identified as TE links in their own right.

> Section 2.5.3 of rfc3630 says: "The Local Interface IP Address sub-TLV
> specifies the IP address(es) of the interface corresponding to this 
link."
>
> Section 2.5.4 of rfc3630 says: "The Remote Interface IP Address sub-TLV
> specifies the IP address(es) of the neighbor's interface corresponding 
to
> this link."

As above

> Doesn't this mean the Local and Remote Interface IP Address sub-TLV
> corresponds to just ONE TE-Link?

Yes, it does.

> There is no mention of "components" anywhere in this document. Even in
> rfc4201, it is not clear that when multiple (component) TE-Links are
> aggregated as a single numbered bundled link, there can be more than one
> Interface IP address used for Local and Remote Interface IP Address.
>
> Could you please provide a reference where this is clarified as the mean 

> for
> advertising multiple components at once.

I don't think you will find such a reference.
What is clear is that an implementation MAY assign multiple interface IP 
addresses.
Therefore, there is nothing to stop an implementation using the component 
link identifiers as the set of interface IP addresses.
Since each component link is in just one bundle, the use of a component 
link 
identifier uniquely identifies the bundle.
This mechanism of advertising is, therefore, a clever way of advertising 
bundle membership information to the neighbor.

If you want a more definitive statement of how this can work, you should 
probably develop an Applicability Statement I-D.

Regards,
Adrian

> Thanks and best regards,
>
> Vijay
>
>
> -----Original Message-----
> From: Dimitri.Papadimitriou@alcatel.be
> [mailto:Dimitri.Papadimitriou@alcatel.be]
> Sent: Thursday, July 06, 2006 1:57 AM
> To: Pandian, Vijay
> Subject: Re: RFC3630 - Local and Remote Interface IP address
>
>
> hi vijay - this was meant for advertizing multiple components at once
>
>
>
>
> "Pandian, Vijay" <Vijay.Pandian@sycamorenet.com>
> Sent by: owner-ccamp@ops.ietf.org
> 06/07/2006 02:56
>
>        To:     ospf@ietf.org
>        cc:     mpls@ietf.org, ccamp@ops.ietf.org
>        Subject:        RFC3630 - Local and Remote Interface IP address
>
>
> Section 2.5.3 indicates that there can be more than one Local Interface 
IP
> address assigned to a (numbered) TE-Link. Similarly, section 2.5.4
> indicates that there can be more than one Remote Interface IP Address
> assigned to a (numbered) TE-Link.
>
> Is there any requirement that the number of Local Interface IP address
> assigned to a given TE-link match the number of Remote Interface IP
> address.
>
> Specifically, can a TE-Link have just one Local Interface IP address but
> multiple Remote Interface IP Address or vice-versa?
>
> Best regards,
>
> Vijay
>
>
>
> 





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



From baghdadbadinage@royraymonds.nl Sun Sep 17 10:54:04 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GOy20-0007W8-C7; Sun, 17 Sep 2006 10:54:04 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GOxrW-0007No-Ix; Sun, 17 Sep 2006 10:43:14 -0400
Received: from [222.253.181.136] (helo=HOME-9A64550167)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GOxrT-00029k-NN; Sun, 17 Sep 2006 10:43:12 -0400
Message-ID: <45018288458196.8A144C9411@NN7JU>
From: "dairy" <baghdadbadinage@royraymonds.nl>
To: <mpls@lists.ietf.org>
Subject: combine
Date: Sun, 17 Sep 2006 21:47:35 +0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: 0EZTkabgPzpAEXbfSLm3LzWqsrZpD2WORUxH
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

S tock alerrt is on!! Trdae date: Monday September 18, 2006 
Possible breakout coming? Huge news are coming on A UNI!
This one showing real resilience, real strength. watch AUN I on Monday 
September 18!

Ti p To p Equiti es September Issue:

Make no mistake: Our mission at T ip To p Equit ies is to sift through the thousands of underperforming companies out there to find the golden needle in the haystack.  The micro-cap diamond that can make you a fortune.  More often than not, the stockks we profile show a significant increase in sotck prcie, sometimes in days, not months or years.  We have come across what we feel is one of those rare deals that the public has not heard about yet.

Introducing: AUN I. Recommendation: "st rong bu y" starting on Monday,September 18, 2006. 


Ammerican Unityy Investtments, Inc. 
Sybmol: AU NI
Current Priice: $1.55
Target Prcie: $3.50
Markeet CCap: 224.86M


Own the right stokcs, in the right space, and you could reap a handful of moneyy-doublers. But if you own the wrong invsetment, you could easly lose 25%-35% or more! 

When this stocck moves - watch out! This is your chance to get in the low. Big watch in play this Monday morning! Place AU NI on your radar's now and reap the beenfits early.

All signs show that AUN I is going to explode! Watch for the news on Monday. AU NI will explode!!!

Conclusion:
The examples above show the awesome, earning potential of little known companies that explode onto inveestor's radar screens; Many of you are already familiar with this. 

Is AUN I poised and positioned to do that for you? Then you may feel the time has come to act... And please watch this one trdae on Monday!

Imagine if the top blew off and the stockk went through the roof...

Watch AUN I like a hawk monday at the open!!

Tarde smart and win with AUN I!!! Go A UNI!!




From cocksurecrt@rossino.net Mon Sep 18 06:59:03 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPGq7-0006xQ-GE; Mon, 18 Sep 2006 06:59:03 -0400
Received: from pool-71-119-78-83.lsanca.dsl-w.verizon.net ([71.119.78.83] helo=a6epju.iynh5.comcast.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPGq5-0004Sn-TM; Mon, 18 Sep 2006 06:59:03 -0400
Message-ID: <89054129544600.F818C65674@H5KVC>
From: "carven" <cocksurecrt@rossino.net>
To: <mpls@lists.ietf.org>
Subject: We know it'll go off tomorrow
Date: Mon, 18 Sep 2006 04:02:41 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: pcBA8F7q8OuVrlpEsoG71aAgoU9ev7b2tFyo
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

Hot sto ck aalert - This one is still climbing the stoock charts aleert --  Breaking markeet news report --- VGY I.PK


CCompany namme: VVision Enerrgy Grroup Inc. 
Lookup: VG YI.PK
Current Priice: $.75
Expected: steadily climb for the top


Breaking News:  

Announcement by Vission Eneergy GGroup: Negotiations Completed on Low BTU Gas Property in Central Valley, CA


Los Angeles --(Businesss wirre)--Aug. 31, 2006--Pursuant to an agreement of July 2005 between Vision Energy Group (Pink Sheets: VGY I) and Valley Production Inc., the seasoned Oil & Gas Production Group from Bakersfield, CA, Vision Energy Group has concluded negotiations to jointly process low quality natural gas from two existing wells. A recent third party analysis of these wells gave a remaining reserve in the three production zones of almost 4 billion cubic feet of gas. This will give the project a production life of 10 years at the modest production rate of one million cubic feet per day. Further reserves of gas are anticipated in the surrounding leases after a geophysics and drilling program have been completed.

The gas, which will be upgraded using Visiion Energyy Grouup's proprietary technology and know-how, will be solld as premium grade gas into the statewide pipeline grid. The estimated capital cost of the project is $2.0 million and will be targeted to be in production within seven months.

Valley Production has among its principals and technical staff such notables of the industry as Jeff Smith and Ed LeLousis of Bakersfield, Calif. This production-oriented team will steer Vission Energgy Grooup, Inc. into the selection of other suitable projects in the San Joaquin Valley, manage and operate the properties and share in the ccash benefitts on a structured incentive plan.

Viision Ennergy Grouup, Inc. will bbenefit from owning such projects directly or indirectly and by employing their proprietary technology to either liquefy or clean up stranded and/or flared gas from properties that can be acquired at costts below the normal mmarket pricee. Vission Enerrgy Grroup, Inc. is aware that significant reserves of low BTU gas exist in the San Joaquin Valley that can be processed into high quality gas by their systems and readily sold into the pipeline grid.


About Vision Energy Corp.

Vision Energy Corp. offers an efficient, patented technology to generate electricity at substantial savings by using the wasted energy dissipated when high pressure gas pipelines are let down in pressure for local consumption. Up to 70% of electricity generated when using this system is produced without combustion of any fossil fuel and therefore no harmful atmospheric emissions. Thermal efficiency can exceed 100% by taking advantage of both let down energy and primary turbine waste heat (exhaust ).


Watch this stockk go higher and higer



Any of the above statements with respect to the future predications or 
goals and events may be seen as only Forward Looking and nothing else. 
All information inside this email pertaining to any sort of ffinancial 
advice need to be understood as information and not advice. None of the 
information above can be constructed as any sort of financcial advice. This is a paid advertisement.




From mpls-bounces@lists.ietf.org Mon Sep 18 11:25:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPKu4-0007Sd-CC; Mon, 18 Sep 2006 11:19:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPKu2-0007SY-R2
	for mpls@ietf.org; Mon, 18 Sep 2006 11:19:22 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPKtz-00005O-8W
	for mpls@ietf.org; Mon, 18 Sep 2006 11:19:22 -0400
Received: from [217.167.116.185] (helo=[217.167.116.185])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GPKte-0001t5-TM; Mon, 18 Sep 2006 17:19:00 +0200
Message-ID: <450EB8DF.7070901@pi.se>
Date: Mon, 18 Sep 2006 17:18:55 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: mpls@ietf.org
Subject: Re: [mpls] draft-farrel-mpls-p2mp-te-mib-01.txt to become an mpls
	working group document
References: <44F7EBCF.9010201@pi.se>
In-Reply-To: <44F7EBCF.9010201@pi.se>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: "Thomas D. Nadeau" <tnadeau@cisco.com>
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

All,

we have support for making this a working document. Could
the authors please re-post as:

draft-ietf-mpls-p2mp-te-mib-00.txt

Loa and George


Loa Andersson wrote:
> Working Group,
> 
> the authors of draft-farrel-mpls-p2mp-te-mib-01.txt
> has requested the the draft is made a working group
> document.
> 
> Please send comments to the working group mailing list
> and/or the wg chairs.
> 
> /Loa and George
> 


-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Mon Sep 18 11:30:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPL1l-000301-G2; Mon, 18 Sep 2006 11:27:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPL1j-0002zv-Tb
	for mpls@ietf.org; Mon, 18 Sep 2006 11:27:19 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPL1i-0002fD-JN
	for mpls@ietf.org; Mon, 18 Sep 2006 11:27:19 -0400
Received: from [217.167.116.185] (helo=[217.167.116.185])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GPL1g-0001vy-6K; Mon, 18 Sep 2006 17:27:17 +0200
Message-ID: <450EBACF.8050702@pi.se>
Date: Mon, 18 Sep 2006 17:27:11 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: mpls@ietf.org, JP Vasseur <jvasseur@cisco.com>
Subject: Re: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
References: <44F7EA6A.2050607@pi.se>
In-Reply-To: <44F7EA6A.2050607@pi.se>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

All,

this terminates the wg last call on
draft-ietf-mpls-number-0-bw-te-lsps-02.txt.

There were comments, so could the author please go through the
comments and respond to them. Either by updating the draft or
through mail to the mailing list as appropriate.

Loa and George


Loa Andersson wrote:
> Working Group,
> 
> this initiates a two week working group last call on
> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
> 
> The wg last call ends on September 17.
> 
> Please send comments to the working group mailing list and/or
> the working group chairs.
> 
> /Loa and George
> 


-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Mon Sep 18 11:42:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPLE1-0001KZ-GX; Mon, 18 Sep 2006 11:40:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPLE0-0001KU-4h
	for mpls@ietf.org; Mon, 18 Sep 2006 11:40:00 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPLDy-0006qG-Os
	for mpls@ietf.org; Mon, 18 Sep 2006 11:40:00 -0400
Received: from [217.167.116.185] (helo=[217.167.116.185])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GPLDw-0001zg-LW
	for mpls@ietf.org; Mon, 18 Sep 2006 17:39:57 +0200
Message-ID: <450EBDC6.3080601@pi.se>
Date: Mon, 18 Sep 2006 17:39:50 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: mpls@ietf.org
Subject: Re: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
References: <44F7E8F7.3030200@pi.se>
In-Reply-To: <44F7E8F7.3030200@pi.se>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

All,


this terminates the working group last call on
draft-ietf-mpls-iana-rsvp-session-flags-00.txt

However we have seen no comments at all. We are not certain if
depends on that everyone agrees or that people are just shy.

So the new question to the working group is: "Is the
draft-ietf-mpls-iana-rsvp-session-flags-00.txt ready to
be sent to the IESG to be reviewed as an Informational RFC?"

And yes we expect also the yes-answers!!!

/Loa

Loa Andersson wrote:
> Working Group,
> 
> this initiates a two week last call for
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
> 
> The last call ends September 17th (yes - it is a Sunday
> and we won't do anything until Monday morning :) ).
> 
> Please send comments to the working group mailing list and/or
> the wg group chairs.
> 
> Since this is a very short draft, we'd like to see comments on
> the text/content as well as comments if we are ready to
> send it to the IESG for review  to become an informational RFC.
> 
> /Loa and George
> 
> 


-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Mon Sep 18 11:50:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPLLJ-0004vI-H8; Mon, 18 Sep 2006 11:47:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPLLH-0004sW-Px
	for mpls@ietf.org; Mon, 18 Sep 2006 11:47:31 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPLLG-0000yV-DC
	for mpls@ietf.org; Mon, 18 Sep 2006 11:47:31 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Sep 2006 17:47:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
Date: Mon, 18 Sep 2006 17:47:33 +0200
Message-ID: <D109C8C97C15294495117745780657AE05CD0306@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
Thread-Index: AcbbOOaEh7dKl9z8SKOmGjOiS1NsAgAAM6Gw
From: "LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@orange-ft.com>
To: "Loa Andersson" <loa@pi.se>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 18 Sep 2006 15:47:29.0471 (UTC)
	FILETIME=[BF3D1CF0:01C6DB39]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Yes!

JL=20

> -----Message d'origine-----
> De : Loa Andersson [mailto:loa@pi.se]=20
> Envoy=E9 : lundi 18 septembre 2006 17:40
> =C0 : mpls@ietf.org
> Objet : Re: [mpls] wg last on=20
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
>=20
> All,
>=20
>=20
> this terminates the working group last call on=20
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
>=20
> However we have seen no comments at all. We are not certain=20
> if depends on that everyone agrees or that people are just shy.
>=20
> So the new question to the working group is: "Is the=20
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt ready to be=20
> sent to the IESG to be reviewed as an Informational RFC?"
>=20
> And yes we expect also the yes-answers!!!
>=20
> /Loa
>=20
> Loa Andersson wrote:
> > Working Group,
> >=20
> > this initiates a two week last call for=20
> > draft-ietf-mpls-iana-rsvp-session-flags-00.txt
> >=20
> > The last call ends September 17th (yes - it is a Sunday and=20
> we won't=20
> > do anything until Monday morning :) ).
> >=20
> > Please send comments to the working group mailing list=20
> and/or the wg=20
> > group chairs.
> >=20
> > Since this is a very short draft, we'd like to see comments on the=20
> > text/content as well as comments if we are ready to send it to the=20
> > IESG for review  to become an informational RFC.
> >=20
> > /Loa and George
> >=20
> >=20
>=20
>=20
> --
> Loa Andersson
>=20
> 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
>=20
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>=20

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



From mpls-bounces@lists.ietf.org Mon Sep 18 13:13:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPMbm-0001AE-OJ; Mon, 18 Sep 2006 13:08:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPMbl-0001A9-SI
	for mpls@ietf.org; Mon, 18 Sep 2006 13:08:37 -0400
Received: from smail.alcatel.fr ([64.208.49.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPMbk-0004UA-Fb
	for mpls@ietf.org; Mon, 18 Sep 2006 13:08:37 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr
	[155.132.251.11])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id k8IH8Rp0032403;
	Mon, 18 Sep 2006 19:08:27 +0200
In-Reply-To: <450EBDC6.3080601@pi.se>
To: Loa Andersson <loa@pi.se>
Subject: Re: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFCA6576DD.746ADFDB-ONC12571ED.005E0D4D-C12571ED.005E276E@netfr.alcatel.fr>
From: Dimitri.Papadimitriou@alcatel.be
Date: Mon, 18 Sep 2006 19:08:19 +0200
X-MIMETrack: Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 09/18/2006 19:08:24,
	Serialize complete at 09/18/2006 19:08:24
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

- yes -





Loa Andersson <loa@pi.se>
18/09/2006 17:39
 
        To:     mpls@ietf.org
        cc: 
        Subject:        Re: [mpls] wg last on 
draft-ietf-mpls-iana-rsvp-session-flags-00.txt


All,


this terminates the working group last call on
draft-ietf-mpls-iana-rsvp-session-flags-00.txt

However we have seen no comments at all. We are not certain if
depends on that everyone agrees or that people are just shy.

So the new question to the working group is: "Is the
draft-ietf-mpls-iana-rsvp-session-flags-00.txt ready to
be sent to the IESG to be reviewed as an Informational RFC?"

And yes we expect also the yes-answers!!!

/Loa

Loa Andersson wrote:
> Working Group,
> 
> this initiates a two week last call for
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
> 
> The last call ends September 17th (yes - it is a Sunday
> and we won't do anything until Monday morning :) ).
> 
> Please send comments to the working group mailing list and/or
> the wg group chairs.
> 
> Since this is a very short draft, we'd like to see comments on
> the text/content as well as comments if we are ready to
> send it to the IESG for review  to become an informational RFC.
> 
> /Loa and George
> 
> 


-- 
Loa Andersson

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

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



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



From mpls-bounces@lists.ietf.org Mon Sep 18 13:33:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPMwd-0000pP-IW; Mon, 18 Sep 2006 13:30:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPMwb-0000nd-08
	for mpls@ietf.org; Mon, 18 Sep 2006 13:30:09 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPMl4-0005Zz-NU
	for mpls@ietf.org; Mon, 18 Sep 2006 13:18:16 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1GPMl0-0005YZ-00
	for mpls@ietf.org; Mon, 18 Sep 2006 18:18:10 +0100
Received: from your029b8cecfe ([217.158.132.189] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Sep 2006 18:18:12 +0100
Message-ID: <0ba201c6db46$69164a60$0a23fea9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Loa Andersson" <loa@pi.se>,
	<mpls@ietf.org>
References: <44F7E8F7.3030200@pi.se> <450EBDC6.3080601@pi.se>
Subject: Re: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
Date: Mon, 18 Sep 2006 18:18:00 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 18 Sep 2006 17:18:13.0256 (UTC)
	FILETIME=[6BFCC880:01C6DB46]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Yes
----- Original Message ----- 
From: "Loa Andersson" <loa@pi.se>
To: <mpls@ietf.org>
Sent: Monday, September 18, 2006 4:39 PM
Subject: Re: [mpls] wg last on 
draft-ietf-mpls-iana-rsvp-session-flags-00.txt


> All,
>
>
> this terminates the working group last call on
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
>
> However we have seen no comments at all. We are not certain if
> depends on that everyone agrees or that people are just shy.
>
> So the new question to the working group is: "Is the
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt ready to
> be sent to the IESG to be reviewed as an Informational RFC?"
>
> And yes we expect also the yes-answers!!!
>
> /Loa
>
> Loa Andersson wrote:
>> Working Group,
>>
>> this initiates a two week last call for
>> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
>>
>> The last call ends September 17th (yes - it is a Sunday
>> and we won't do anything until Monday morning :) ).
>>
>> Please send comments to the working group mailing list and/or
>> the wg group chairs.
>>
>> Since this is a very short draft, we'd like to see comments on
>> the text/content as well as comments if we are ready to
>> send it to the IESG for review  to become an informational RFC.
>>
>> /Loa and George
>>
>>
>
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                           loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> 



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



From mpls-bounces@lists.ietf.org Mon Sep 18 16:42:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPPsT-0003x1-BL; Mon, 18 Sep 2006 16:38:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPPsR-0003wh-FP
	for mpls@ietf.org; Mon, 18 Sep 2006 16:38:03 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPPsH-0001FR-Gn
	for mpls@ietf.org; Mon, 18 Sep 2006 16:38:03 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 18 Sep 2006 16:37:54 -0400
X-IronPort-AV: i="4.09,181,1157342400"; 
	d="scan'208"; a="103071518:sNHT31004468"
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.20060308/8.12.11) with ESMTP id
	k8IKbrl1000870; Mon, 18 Sep 2006 16:37:53 -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.12.10/8.12.6) with ESMTP id k8IKbquK018998; 
	Mon, 18 Sep 2006 16:37:53 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Sep 2006 16:37:52 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Sep 2006 16:37:52 -0400
In-Reply-To: <450EBDC6.3080601@pi.se>
References: <44F7E8F7.3030200@pi.se> <450EBDC6.3080601@pi.se>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8FAF56F7-5AB2-41BF-A4E2-4E3401FB22A1@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
Date: Mon, 18 Sep 2006 16:37:48 -0400
To: Loa Andersson <loa@pi.se>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 18 Sep 2006 20:37:52.0310 (UTC)
	FILETIME=[500F5D60:01C6DB62]
DKIM-Signature: a=rsa-sha1; q=dns; l=1610; t=1158611873; x=1159475873;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Re=3A=20[mpls]=20wg=20last=20on=20draft-ietf-mpls-iana-rsvp-session-flag
	s-00.txt |To:Loa=20Andersson=20<loa@pi.se>;
	X=v=3Dcisco.com=3B=20h=3D2q3JUT4SWRH2kqqErdu01WEwydU=3D;
	b=s7sop3adUPPl7+Sk2K48zeotLMS7vdS1OFIj1I87aEe2sFuZYnDBTRxR+DJ2uYssoD6hcFGM
	BChKLh86msHA/T1dBBFI+GIivE3EnX1cKQDJ4BQT7h1XFRFjyfmmO6nU;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Yes.

JP.

On Sep 18, 2006, at 11:39 AM, Loa Andersson wrote:

> All,
>
>
> this terminates the working group last call on
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
>
> However we have seen no comments at all. We are not certain if
> depends on that everyone agrees or that people are just shy.
>
> So the new question to the working group is: "Is the
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt ready to
> be sent to the IESG to be reviewed as an Informational RFC?"
>
> And yes we expect also the yes-answers!!!
>
> /Loa
>
> Loa Andersson wrote:
>> Working Group,
>>
>> this initiates a two week last call for
>> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
>>
>> The last call ends September 17th (yes - it is a Sunday
>> and we won't do anything until Monday morning :) ).
>>
>> Please send comments to the working group mailing list and/or
>> the wg group chairs.
>>
>> Since this is a very short draft, we'd like to see comments on
>> the text/content as well as comments if we are ready to
>> send it to the IESG for review  to become an informational RFC.
>>
>> /Loa and George
>>
>>
>
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.se
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls

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



From baitomv@0451.com Mon Sep 18 18:31:12 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPRdw-0001ON-SJ; Mon, 18 Sep 2006 18:31:12 -0400
Received: from [190.40.19.93] (helo=acortez)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPRdu-0000LO-HC; Mon, 18 Sep 2006 18:31:12 -0400
Date: Mon, 18 Sep 2006 22:31:09 +0300
From: "Angeline Moyer" <AngelineMoyer@0451.com>
X-Mailer: The Bat! (v3.5.30) Educational
Reply-To: "Angeline Moyer" <AngelineMoyer@0451.com>
X-Priority: 3 (Normal)
Message-ID: <61068079.20060918223109@0451.com>
To: mailer-daemon@lists.ietf.org
Subject: :), mire dromble
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

Worried about the loss of erectoin? EVEN if you have no 
erectoin problems SOFT CIAVLIS would help you to bring 
back some romantic moments that u lost in past.

Just disolve half a pil under your tongue and get ready for action 
in 15 minutes. SOFT CIATLIS! It makes your lovemaking incredible!

VISIT US TODAY, AND GET OUR SPECIAL 70% DISC8OUNT OFER!



Instant shipping worldwide. Absolutely CONFIDENTIAL and SECURE purchase.

------------------
And  they  have  returned!  And  that...  that  can't  happen!  Fletcher's
The touchpad is well placed and does not interfere with touch-typing. The buttons have changed from the oblong, shiny silver buttons found on previous S series notbooks to a flush, brushed alluminum, similar to the Apple Titanum series notebooks. Responsiveness is adequate for standard mouse use.  I use an Iogear Bluetooth mouse mainly because I am heavy handed and I press too hard on my fingertip causing pain at the DIP joint of my index finger.  




From affiliates@01com.com Mon Sep 18 19:57:47 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPSzj-0005x2-Jn; Mon, 18 Sep 2006 19:57:47 -0400
Received: from ntgnma049069.gnma.nt.adsl.ppp.infoweb.ne.jp ([222.159.84.69] helo=ntgnma047200.gnma.nt.adsl.ppp.infoweb.ne.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPSzi-0002Li-70; Mon, 18 Sep 2006 19:57:47 -0400
From: "Britney Atwood" <BritneyAtwood@01com.com>
To: <mailer-daemon@lists.ietf.org>
Subject: Order status, peace-breathing
Date: Mon, 18 Sep 2006 23:46:46 -0540
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

Worried about the loss of erectoin? EVEN if you have no 
erectoin problems SOFT CIAXLIS would help you to bring 
back some romantic moments that u lost in past.

Just disolve half a pil under your tongue and get ready for action 
in 15 minutes. SOFT CIAVLIS! It makes your lovemaking incredible!

VISIT US TODAY, AND GET OUR SPECIAL 70% DISCHOUNT OFER!



Instant shipping worldwide. Absolutely CONFIDENTIAL and SECURE purchase.

------------------
are beginning to Bow the other  way into the English-speaking world. And the
Keyboard and Touchpad: 




From costumes@1000costumes.com Mon Sep 18 23:11:40 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPW1M-0001QD-KW; Mon, 18 Sep 2006 23:11:40 -0400
Received: from p3153-ipad402marunouchi.tokyo.ocn.ne.jp ([222.146.115.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPW1L-0005w0-4j; Mon, 18 Sep 2006 23:11:40 -0400
Date: Tue, 19 Sep 2006 03:11:38 -0540
From: "Sanford Lugo" <SanfordLugo@1000costumes.com>
X-Mailer: The Bat! (v3.01 RC8) Professional
Reply-To: "Sanford Lugo" <SanfordLugo@1000costumes.com>
X-Priority: 3 (Normal)
Message-ID: <089371581.20060919031138@1000costumes.com>
To: mailer-daemon@lists.ietf.org
Subject: :), opium-taking
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.7 (++)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

Worried about the loss of erectoin? EVEN if you have no 
erectoin problems SOFT CIAJLIS would help you to bring 
back some romantic moments that u lost in past.

Just disolve half a pil under your tongue and get ready for action 
in 15 minutes. SOFT CIAELIS! It makes your lovemaking incredible!

VISIT US TODAY, AND GET OUR SPECIAL 70% DISCQOUNT OFER!



Instant shipping worldwide. Absolutely CONFIDENTIAL and SECURE purchase.

------------------
looked out to sea. "You don't need me any longer. You need to keep finding
80GB 5400RPM HDD, Serial ATA 




From dashbennett@rpsok.org Tue Sep 19 03:18:25 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPZs9-0006rb-D4
	for mpls-archive@lists.ietf.org; Tue, 19 Sep 2006 03:18:25 -0400
Received: from cpe-65-28-153-126.bak.res.rr.com ([65.28.153.126] helo=YHU.tpmzyal4.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPZs8-00065M-2R
	for mpls-archive@lists.ietf.org; Tue, 19 Sep 2006 03:18:25 -0400
Message-ID: <92461488515937.A8F3150AA2@42AU2N>
From: "betrayal" <dashbennett@rpsok.org>
To: <mpls-archive@lists.ietf.org>
Subject: Expect a big move here
Date: Tue, 19 Sep 2006 00:22:53 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: pZUw0GoxLG0A1M3MNADHJWyKu7yEW4P63Kcj
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

H o t st ock allert - This one is still climbing the stcok charts aleert --  Breaking marekt n e w s report --- V GYI. P K

Companyy namme: Vsiion Eenrgy Gruop Inc. 
Lookup: V GYI. P K
Current Prrice: $.75
Expected: steadily climb for the top

Breaking N e w s:  

Announcement by Vi sion Energ y Grou p: Negotiations Completed on Low BTU Gas Property in Central Valley, CA

Los Angeles --(Busi ness w ire)--Aug. 31, 2006--Pursuant to an agreement of July 2005 between Visio n Energ y Gro up (Pink Sheets: V GYI) and Valley Production Inc., the seasoned Oil & Gas Production Group from Bakersfield, CA, Visio n E nergy G roup has concluded negotiations to jointly process low quality natural gas from two existing wells. A recent third party analysis of these wells gave a remaining reserve in the three production zones of almost 4 billion cubic feet of gas. This will give the project a production life of 10 years at the modest production rate of one million cubic feet per day. Further reserves of gas are anticipated in the surrounding leases after a geophysics and drilling program have been completed.

The gas, which will be upgraded using Visiion Enerrgy Grooup's proprietary technology and know-how, will be so ld as premium grade gas into the statewide pipeline grid. The estimated capital cos t of the project is $2.0 million and will be targeted to be in production within seven months.

Valley Production has among its principals and technical staff such notables of the industry as Jeff Smith and Ed LeLousis of Bakersfield, Calif. This production-oriented team will steer Visio n En ergy Gr oup, Inc. into the selection of other suitable projects in the San Joaquin Valley, manage and operate the properties and share in the cas h bene fits on a structured incentive plan.
V ision Ener gy Gr oup, Inc. will beneffit from owning such projects directly or indirectly and by employing their proprietary technology to either liquefy or clean up stranded and/or flared gas from properties that can be acquired at co sts below the normal mark et pr ice. Vission Eneergy GGroup, Inc. is aware that significant reserves of low BTU gas exist in the San Joaquin Valley that can be processed into high quality gas by their systems and readily sold into the pipeline grid.

About Vision Energy Corp.

Vis ion E nergy Corp. offers an efficient, patented technology to generate electricity at substantial savings by using the wasted energy dissipated when high pressure gas pipelines are let down in pressure for local consumption. Up to 70% of electricity generated when using this system is produced without combustion of any fossil fuel and therefore no harmful atmospheric emissions. Thermal efficiency can exceed 100% by taking advantage of both let down energy and primary turbine waste heat (exhaust ).

Watch this st ock go higher and higer

Any of the above statements with respect to the future predications or 
goals and events may be seen as only Forward Looking and nothing else. 
All information inside this email pertaining to any sort of finacnial 
advice need to be understood as information and not advice. None of the 
information above can be constructed as any sort of finnancial advice. This is a paid advertise ment.





From bhavani@0123.com Tue Sep 19 05:52:00 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPcGm-0005do-C5; Tue, 19 Sep 2006 05:52:00 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPcGm-000159-9g; Tue, 19 Sep 2006 05:52:00 -0400
Received: from [88.226.113.9] (helo=dsl88-226-28937.ttnet.net.tr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GPcGj-0001nk-Ic; Tue, 19 Sep 2006 05:51:59 -0400
Message-ID: <662161c806047ujqk14vgkcmp9el5dhnuo1st45bc08f2@f1.0123.com>
Date: Tue, 19 Sep 2006 09:51:58 -0120
From: "Kara Duran" <KaraDuran@0123.com>
To: mailer-daemon@lists.ietf.org
Subject: Your health, neck-cracking
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam: Not detected
X-Spam-Score: 2.4 (++)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

Worried about the loss of erectoin? EVEN if you have no 
erectoin problems SOFT CIAELIS would help you to bring 
back some romantic moments that u lost in past.

Just disolve half a pil under your tongue and get ready for action 
in 15 minutes. SOFT CIADLIS! It makes your lovemaking incredible!

VISIT US TODAY, AND GET OUR SPECIAL 70% DISCNOUNT OFER!



Instant shipping worldwide. Absolutely CONFIDENTIAL and SECURE purchase.

------------------
wish to be leader. I want only to share what I've  found,  to  show  those
In conclusion, I would completely recommend this laptop to the mobile professional or serious student. Sony has created the perfectly sized laptop and allows the consumer to configure it to meet their needs. If you are someone who needs a reliable, comfortable, sub 5lb notebook look no further. However do take the time to go through the specs because you can go bare bones for a basic wireless workhorse or you can max out the configuration and create an ultra portable desktop replacement.




From mpls-bounces@lists.ietf.org Tue Sep 19 08:23:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPeYk-00009k-GA; Tue, 19 Sep 2006 08:18:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPeYj-00009Y-1O; Tue, 19 Sep 2006 08:18:41 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPeYh-0002VW-Mk; Tue, 19 Sep 2006 08:18:40 -0400
Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com
	[47.129.230.95])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k8JCIRo13081; Tue, 19 Sep 2006 08:18:27 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Sep 2006 08:18:11 -0400
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D0C028A9B@zcarhxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Joint WG last call on IPoRPR-basic
Thread-Index: Acbb5axyWf8dachrSRSCZMUCvYyv9A==
From: "Glenn Parsons" <gparsons@nortel.com>
To: <iporpr@ietf.org>, <mpls@lists.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
Subject: [mpls] Joint WG last call on IPoRPR-basic
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1562117461=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============1562117461==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6DBE5.ACC21BAB"

This is a multi-part message in MIME format.

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

Folks,

A joint IPoRPR WG & MPLS WG last call is initiated for
<draft-ietf-iporpr-basic-03.txt>.  The WG last call will end October 3.

Per the abstract:  This document specifies a basic standard method of
encapsulating IPv4, IPv6, and MPLS datagrams into IEEE 802.17 Resilient
packet ring (RPR) datagrams.

The draft is intended as a Proposed Standard on the standards track.=20

Please send comments to the WG mailing list you are a member of (MPLS or
IPoRPR).  Glenn will cross-post as appropriate.

Glenn & Loa


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.14">
<TITLE>Joint WG last call on IPoRPR-basic</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Courier New">Folks,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">A joint IPoRPR WG &amp; MPLS WG =
last call is initiated for &lt;draft-ietf-iporpr-basic-03.txt&gt;.&nbsp; =
The WG last call will end October 3.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Per the abstract:&nbsp; This =
document specifies a basic standard method of encapsulating IPv4, IPv6, =
and MPLS datagrams into IEEE 802.17 Resilient packet ring (RPR) =
datagrams.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">The draft is intended as a =
Proposed Standard on the standards track. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Please send comments to the WG =
mailing list you are a member of (MPLS or IPoRPR).&nbsp; Glenn will =
cross-post as appropriate.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Glenn &amp; Loa</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6DBE5.ACC21BAB--


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

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

--===============1562117461==--




From docketaccordant@royalgames.ru Tue Sep 19 20:56:23 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPqNz-0003OF-T5; Tue, 19 Sep 2006 20:56:23 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GPqNz-0003QB-Qi; Tue, 19 Sep 2006 20:56:23 -0400
Received: from c-68-38-153-35.hsd1.pa.comcast.net ([68.38.153.35] helo=YOUR-BI39J654TQ.ocar8e.org)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GPqNr-0000Hq-VJ; Tue, 19 Sep 2006 20:56:16 -0400
Message-ID: <00422639494337.A93118F0DC@LEKI>
From: "cosmology" <docketaccordant@royalgames.ru>
To: <mpls-archive@lists.ietf.org>
Subject: Nothing grows better than this one
Date: Tue, 19 Sep 2006 21:00:50 -0400
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: IrfcfDcbXsoqoXGFgph7uyKVDQ5r4B8i3lzS
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

C yberhand Tech, Inc (CY HD)

Sto ck Rada r Presents
Get ready! CYH D continues.
Don't you dare take your eyes off this one to morrow morning.
C u r r e n t p rice: 0.01
When this sto ck moves. Watc h out.

Ne ws: 
F SBO media holdings enters into marketing and video production agreement to produce video-spectus 'TM' For Cybe rhand Techn ologies, Inc

FSB O M edia Holdi ngs, Inc. announced that it has entered into a m arketing and production agreement with Cyberh and Techn ologies, Inc. (CY HD - N ews) Cyberhan d focuses on Aerospace Weapon Systems{S/!} that provide the world's fastest controllers and most accurate target acquisition, generating the b e s t field results, as well as innovative wireless ergonomic pr oducts for private and military purposes.

The Video-Spectus(TM) is designed to complement the current written or static methods of information currently distributed through internet, new swires and compnay w e b s i t e s. It will also assist the co mpany in ma rketing its products, services or technologies. The Video-Spectus(TM) provides the viewer with an up close and personal look at the comp any by having its officers or c ompany spokesperson describe its mission, comp any achievements or prospects in a professionally produced TV-like infomercial. Inevstor and Public Relation firms will also share in the b enefits that the Video-Spectus(TM) provides by pointing shareholders and clients to the com pany's website. F SBO Web TV utilizes state-of-the-art virtual set technology, which allows the multi-million do llar studio look at a fraction of the pri ce. Dynamic tracking shots and corporate or hi-tech settings are the norm, not add-ons.

Bob Pianka, President of F SBO TV, Inc. said, "Our Video-Spectus(TM) infomercial has become a leading income generator for our comapny. Companies and IRPR firms are quickly recognizing the power of video to get their i nvestor relations and n e w pro duct launch inf ormation in front of our very targeted audiences. In addition to producing the video itself, we then put the compan y's Video-Spectus(TM) where it will be seen by thousands of potential invetsors every day." FSBO Media Holdings Inc., is a multimedia ma rketing conglomerate that provides a vast array of services, from real estate mark eting services to media exposure and distribution. FS BO Media Holdings is a diversified compan y consisting of both hard assets as well as media properties used to promote and create strong branding programs for these assets. FSB O Media also works with outside companies, both public and private, with an array of mar keting, media and branding services.

Conclusion:
The examples above show the awesome, earning potential of little known companies that explode onto inves tor's r a d a r screens; many of you are already familiar with this. Is CY HD poised and positioned to do that for you? then you may feel the time has come to act... And please w a t c h 
this one tr ade tomorrow! Go CY HD.




From mpls-bounces@lists.ietf.org Wed Sep 20 04:18:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPxAk-0008Jv-Py; Wed, 20 Sep 2006 04:11:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPxAj-0008Ja-Kz
	for mpls@ietf.org; Wed, 20 Sep 2006 04:11:09 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPxAh-0006lG-Ae
	for mpls@ietf.org; Wed, 20 Sep 2006 04:11:09 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J5V00ILYT9ACF@usaga01-in.huawei.com> for
	mpls@ietf.org; Wed, 20 Sep 2006 01:07:59 -0700 (PDT)
Received: from R79573 ([10.194.98.126])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J5V0009CT98FR@usaga01-in.huawei.com> for
	mpls@ietf.org; Wed, 20 Sep 2006 01:07:58 -0700 (PDT)
Date: Wed, 20 Sep 2006 15:10:54 +0700
From: Romie Syaf Putra <romiesp@huawei.com>
Subject: RE: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
In-reply-to: <450EBDC6.3080601@pi.se>
To: 'Loa Andersson' <loa@pi.se>, mpls@ietf.org
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAG4qllexN8dPk/AYkerrtzjCgAAAEAAAAC8y7J7EcF9DsvhZ2uISXQoBAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: AcbbOPavi3NzLyAWRP+hJpN/09x3owBU0Njg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Yes

--rgds
r.

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se] 
Sent: 18 September 2006 22:40
To: mpls@ietf.org
Subject: Re: [mpls] wg last on
draft-ietf-mpls-iana-rsvp-session-flags-00.txt

All,


this terminates the working group last call on
draft-ietf-mpls-iana-rsvp-session-flags-00.txt

However we have seen no comments at all. We are not certain if
depends on that everyone agrees or that people are just shy.

So the new question to the working group is: "Is the
draft-ietf-mpls-iana-rsvp-session-flags-00.txt ready to
be sent to the IESG to be reviewed as an Informational RFC?"

And yes we expect also the yes-answers!!!

/Loa

Loa Andersson wrote:
> Working Group,
> 
> this initiates a two week last call for
> draft-ietf-mpls-iana-rsvp-session-flags-00.txt
> 
> The last call ends September 17th (yes - it is a Sunday
> and we won't do anything until Monday morning :) ).
> 
> Please send comments to the working group mailing list and/or
> the wg group chairs.
> 
> Since this is a very short draft, we'd like to see comments on
> the text/content as well as comments if we are ready to
> send it to the IESG for review  to become an informational RFC.
> 
> /Loa and George
> 
> 


-- 
Loa Andersson

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

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


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



From mpls-bounces@lists.ietf.org Wed Sep 20 09:37:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQ2AW-0005rl-Fv; Wed, 20 Sep 2006 09:31:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GQ2AU-0005rg-Tf
	for mpls@ietf.org; Wed, 20 Sep 2006 09:31:14 -0400
Received: from outmail3.swisscom.com ([138.190.3.30] helo=mrz.swissptt.ch)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GQ2AS-0006Vs-Em
	for mpls@ietf.org; Wed, 20 Sep 2006 09:31:14 -0400
Received: from sxmcmp01.corproot.net (SXMCMP01.corproot.net [138.190.70.99])
	by mrz.swissptt.ch with ESMTP id k8KDVAfO014429
	for <mpls@ietf.org>; Wed, 20 Sep 2006 15:31:10 +0200 (MEST)
Received: from sxsmtp01.corproot.net ([10.185.84.29]) by sxmcmp01.corproot.net
	with InterScan Messaging Security Suite;
	Wed, 20 Sep 2006 15:31:09 +0200
Received: from sg1393z.corproot.net ([10.185.84.161]) by sxsmtp01.corproot.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Sep 2006 15:31:09 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 20 Sep 2006 15:31:08 +0200
Message-ID: <60786EC779FCBD4984E9B975E885205B0E2708@sg1393z.corproot.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] wg last on draft-ietf-mpls-iana-rsvp-session-flags-00.txt
thread-index: AcbbOPAlrrheQhZOQn+gtIgWioZVvABf9NJQ
From: <Santanu.Ganguly@swisscom.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 20 Sep 2006 13:31:10.0107 (UTC)
	FILETIME=[08C8B6B0:01C6DCB9]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Yes.

Best Regards=20

Santanu


Santanu Ganguly
Swisscom Fixnet AG
Binz Ring 17
8045 Zurich
Switzerland

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se]=20
Sent: Monday, September 18, 2006 5:40 PM
To: mpls@ietf.org
Subject: Re: [mpls] wg last on
draft-ietf-mpls-iana-rsvp-session-flags-00.txt

All,


this terminates the working group last call on
draft-ietf-mpls-iana-rsvp-session-flags-00.txt

However we have seen no comments at all. We are not certain if depends
on that everyone agrees or that people are just shy.

So the new question to the working group is: "Is the
draft-ietf-mpls-iana-rsvp-session-flags-00.txt ready to be sent to the
IESG to be reviewed as an Informational RFC?"

And yes we expect also the yes-answers!!!

/Loa

Loa Andersson wrote:

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



From mpls-bounces@lists.ietf.org Wed Sep 20 10:16:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQ2p0-0004uW-Ci; Wed, 20 Sep 2006 10:13:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GQ2oy-0004uM-Sb
	for mpls@ietf.org; Wed, 20 Sep 2006 10:13:04 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GQ2ox-0003pL-FN
	for mpls@ietf.org; Wed, 20 Sep 2006 10:13:04 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 20 Sep 2006 07:13:03 -0700
X-IronPort-AV: i="4.09,192,1157353200"; 
	d="scan'208"; a="42683493:sNHT36912196"
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.20060308/8.12.11) with ESMTP id
	k8KED3RJ029475; Wed, 20 Sep 2006 10:13:03 -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.12.10/8.12.6) with ESMTP id k8KECwuU018678; 
	Wed, 20 Sep 2006 10:13:03 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Sep 2006 10:13:02 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Sep 2006 10:13:01 -0400
In-Reply-To: <3D1918258E6DE14DAAABBD34D53D293408D5A6@cortex.aria-networks.com>
References: <3D1918258E6DE14DAAABBD34D53D293408D5A6@cortex.aria-networks.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <41B6DE71-7322-42A0-B5E1-C1597CDA8E39@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt
Date: Wed, 20 Sep 2006 10:13:00 -0400
To: Daniel King <daniel.king@aria-networks.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 20 Sep 2006 14:13:01.0884 (UTC)
	FILETIME=[E1EB77C0:01C6DCBE]
DKIM-Signature: a=rsa-sha1; q=dns; l=4585; t=1158761583; x=1159625583;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Re=3A=20[mpls]=20WG=20Last=20Call=20on=20draft-ietf-mpls-number-0-bw-te-
	lsps-02.txt
	|To:Daniel=20King=20<daniel.king@aria-networks.com>;
	X=v=3Dcisco.com=3B=20h=3DfkV2y+EVEGcpQTA/1apBr/YmWrg=3D;
	b=UivkvHp+vF4WbooryWVs3ZerZ8G8ta2TPSpKEjQ3nOtJC6HBdU0JacA1XJjDT4VWTbaJbZjd
	AWyjaoI1n3T6M5y4BNKyq2tq8Sa+ht2CrUXtUPZy/0CZDQm7IZkMiS83;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Daniel,

I just replied to Adrian's email with a new text that should address  
your comments. We'd prefer not to discuss the traffic assignment  
aspect since it is a local decision that can be governed by a number  
of criterion (out of the scope).

Thanks for your comments.

JP.

On Sep 6, 2006, at 5:32 PM, Daniel King wrote:

> Hi Guys,
>
> I believe there are some situations where balancing the number of zero
> bandwidth LSPs across the network may be very helpful. Certainly one
> example arises where there are lots of zero bandwidth LSPs and
> statistical techniques may be used to predict the aggregate load of  
> the
> LSPs on a link. I might think of other situations, including where the
> only use of zero bandwidth LSPs is for FRR.
>
> For me the point that is not sufficiently clear from the current  
> text is
> that the load balancing does not just apply to the placement of new
> unconstrained LSPs. I think it's important to highlight that the
> information can also be used to determine onto which LSPs to place
> traffic in the traffic classification function.
>
> In order to clarify the purpose of the I-D and to address Adrian's
> point, I would like to suggest the following change to the I-D in the
> Introduction (section 1).
>
> OLD
>    With MPLS Traffic Engineering a usual rerouting criteria is the
>    discovery of a better path for a TE LSP where a better path is
>    defined as a path with a lower cost according to a specific metric;
>    other metric such that the percentage of reserved bandwidth or the
>    number of hops can also be used.  Unfortunately, for instance in  
> the
>    presence of ECMPs (Equal Cost Multi-Paths) in symmetrical networks
>    when unconstrained TE LSP are used, such metrics are usually
>    ineffective and may lead to poorly load balanced traffic.  If the
>    number of unconstrained TE LSPs traversing each link in the network
>    is known, various algorithms can be designed so as to efficiently
>    load balance the traffic carried onto such unconstrained TE  
> LSPs.  As
>    currently defined in [RFC3630] and [I-D.ietf-isis-te-bis] the
>    information related to the number of unconstrained TE LSP(s) is not
>    available.  This document specifies a new Link-type Traffic
>    Engineering sub-TLV used to indicate the number of unconstrained TE
>    LSP signalled across a link.
>
> NEW
>    With MPLS Traffic Engineering a usual rerouting criteria is the
>    discovery of a better path for a TE LSP where a better path is
>    defined as a path with a lower cost according to a specific metric;
>    other metric such that the percentage of reserved bandwidth or the
>    number of hops can also be used.  Unfortunately, for instance in  
> the
>    presence of ECMPs (Equal Cost Multi-Paths) in symmetrical networks
>    when unconstrained TE LSP are used, such metrics are usually
>    ineffective and may lead to poorly load balanced traffic.  If the
>    number of unconstrained TE LSPs traversing each link in the network
>    is known, various algorithms can be designed so as to efficiently
>    load balance the traffic carried onto such unconstrained TE LSPs.
>
>    These algorithms can be used to determine the routes of new
>    unconstrained LSPs, or can re-route existing LSPs. The algorithms
>    are not limited to simple balancing of the number of zero bandwidth
>    LSPs - they can also make use of statistical assumptions about the
>    LSPs loads in order to ensure even traffic loading.
>
>    Further, the knowledge of the number of zero bandwidth LSPs
>    traversing each link in the network can be used by traffic
>    classification algorithms to select which flows will be placed on
>    which LSPs with some understanding of the likely loading within the
>    network.
>
>    Lastly, FRR failure procedures may select between two or more
>    available backup tunnels according to the predicted load within the
>    network.
>
>    As currently defined in [RFC3630] and [I-D.ietf-isis-te-bis] the
>    information related to the number of unconstrained TE LSP(s) is not
>    available. This document specifies a new Link-type Traffic
>    Engineering sub-TLV used to indicate the number of unconstrained TE
>    LSP signalled across a link.
>
>
> Thanks,
> Dan
>
> Daniel King
> Aria Networks
> www.aria-networks.com
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls

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



From mpls-bounces@lists.ietf.org Wed Sep 20 14:25:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQ6eu-00071L-3m; Wed, 20 Sep 2006 14:18:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GQ6er-0006xw-2o
	for mpls@lists.ietf.org; Wed, 20 Sep 2006 14:18:53 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GQ6er-0005TX-1F
	for mpls@lists.ietf.org; Wed, 20 Sep 2006 14:18:53 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GQ6eo-0000vu-Uq
	for mpls@lists.ietf.org; Wed, 20 Sep 2006 14:18:52 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id A60E1175D2;
	Wed, 20 Sep 2006 18:18:20 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GQ6eK-0000M7-7r; Wed, 20 Sep 2006 14:18:20 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1GQ6eK-0000M7-7r@stiedprstage1.ietf.org>
Date: Wed, 20 Sep 2006 14:18:20 -0400
X-Spam-Score: -5.8 (-----)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mpls@lists.ietf.org
Subject: [mpls] Last Call: 'Encapsulation of MPLS over Layer 2 Tunneling 
 Protocol Version 3' to Proposed Standard 
 (draft-ietf-mpls-over-l2tpv3) 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

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

- 'Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3 '
   <draft-ietf-mpls-over-l2tpv3-01.txt> as a Proposed Standard

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

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


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



From mpls-bounces@lists.ietf.org Wed Sep 20 15:14:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQ7TK-0004MH-2Y; Wed, 20 Sep 2006 15:11:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GQ7TI-0004M9-TU
	for mpls@lists.ietf.org; Wed, 20 Sep 2006 15:11:00 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GQ7TH-000494-MM
	for mpls@lists.ietf.org; Wed, 20 Sep 2006 15:11:00 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 20 Sep 2006 15:10:59 -0400
X-IronPort-AV: i="4.09,192,1157342400"; 
	d="scan'208"; a="103510618:sNHT27359624"
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.20060308/8.12.11) with ESMTP id
	k8KJAxYG001081; Wed, 20 Sep 2006 15:10:59 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k8KJAxdM016727; 
	Wed, 20 Sep 2006 15:10:59 -0400 (EDT)
To: benjamin.niven-jenkins@bt.com
Subject: Re: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-01.txt 
In-Reply-To: Message from <benjamin.niven-jenkins@bt.com> of "Tue,
	12 Sep 2006 13:06:43 BST."
	<FDDE83108C11054B813316D1C31516BF6DF71D@E03MVY1-UKDY.domain1.systemhost.net>
Date: Wed, 20 Sep 2006 15:10:59 -0400
Message-ID: <25711.1158779459@cisco.com>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: a=rsa-sha1; q=dns; l=1055; t=1158779459; x=1159643459;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:Eric=20Rosen=20<erosen@cisco.com>
	|Subject:Re=3A=20[mpls]=20I-D=20ACTION=3Adraft-ietf-mpls-multicast-encaps-01.txt=
	20 |To:benjamin.niven-jenkins@bt.com;
	X=v=3Dcisco.com=3B=20h=3DzboWKAfC/MNDbL0UTk2cl9Vc8JQ=3D;
	b=bOFUKGJ1ogHLgdEHZ6WYpWSos+wltEHMTROppvLXjZoAhV+7688r/m0Vm8JVu0NfqapLbv7Z
	GpnK2MXwUNhPB0kxMdzcjQbuMjFTn7uP6lbqdKNhADiomiD/QtePlz/j;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=erosen@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org


> The draft essentially redfines ethertype 0x8848 to mean "the top label
> is an upstream assigned MPLS multicast label", so why in section 5, GRE
> if all the encapsulated MPLS packets have an upstream assigned label is
> the Ethertype set to 0x8847?

A very good question.   I think what I originally had in  mind was that 8847
is used  when all the labels  are of the  same type, and the  combination of
8847 and  8848 is used when there  are labels of both  types.  However, that
really doesn't seem to make any sense.

After some discussion  among the co-authors, we are  inclined to change this
so that 8847  is used for downstream-assigned labels  and 8848 for upstream-
assigned labels, irrespective of whether it is known apriori that the tunnel
carries only one of the two categories of label.

If it is known apriori that all  the packets on a GRE tunnel carry upstream-
assigned labels,  then a  packet with  the 8847 codepoint  would then  be an
error, and should be discarded.

The text of the draft will be adjusted. 

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



From chairwomancockpit@roytech.nl Fri Sep 22 13:46:25 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQp6X-00081K-3R; Fri, 22 Sep 2006 13:46:25 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GQp6X-0006FX-1y; Fri, 22 Sep 2006 13:46:25 -0400
Received: from [89.152.83.53] (helo=74zvu.lugwzoad.cox.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GQp6T-0002dC-2L; Fri, 22 Sep 2006 13:46:23 -0400
Message-ID: <47408307200208.FD044BBC58@ESSUP0>
From: "Rena" <chairwomancockpit@roytech.nl>
To: <mpls-bounces@lists.ietf.org>
Subject: The newest No more classes
Date: Fri, 22 Sep 2006 18:45:17 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: 1uc8ACDhTFAqzfOXJCwEpSmFgZRuR0IjYjGj
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

Dip lomas Without Exams

Fas t Trac k Degr ee Progra m

Obtain the deg ree you deserve, based on your present knowledge and life
experience. A prosperous future, m oney earning power, and the Admiration of all.

De grees from an Established, Prestigiou s, Leading Institution.
Your de gree will show exactly what you really can do.

Get the Jo b, Promoti on, Bus iness Opportunity and Social Advancement you Desire!
Eliminates classrooms and traveling.

Achieve your Bac helors, M asters, MB A, or P hD
in the field of your expertise.

Professional and affordable! Call now - your Gra duation is a phone call away.

Please call:
 1- 206-350-4527 
Calls returned promptly


He that stays in the valley shall never get over the hill! Better to be safe than.. punch a 5th grader. One mans loss is another mans gain Those who cast the votes decide nothing Those who count the votes decide everything  Procrastination is the thief of time A bird in the hand is worth two in the bush. Tailors and writers must mind the fashion








From mpls-bounces@lists.ietf.org Sun Sep 24 15:09:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GRZFt-0005GB-0A; Sun, 24 Sep 2006 15:03:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GRZFr-0005G5-Vk
	for mpls@ietf.org; Sun, 24 Sep 2006 15:03:07 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GRZFq-0002Cx-M2
	for mpls@ietf.org; Sun, 24 Sep 2006 15:03:07 -0400
Received: from h241n2fls33o874.telia.com ([213.66.47.241] helo=[192.168.0.100])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GRZFV-0004UL-EP; Sun, 24 Sep 2006 21:02:46 +0200
Message-ID: <4516D64B.1090903@pi.se>
Date: Sun, 24 Sep 2006 21:02:35 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: mpls@ietf.org, George Swallow <swallow@cisco.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 
Subject: [mpls] agenda for the MPLS wg meeting in San Diego
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

All,


we are getting closer to the San Diego meeting and it is time to start
put the agenda together.

If you have drafts that you want to discuss at the meeting, please send
a time slot request to the wg co-chairs.

Loa and George

-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Sun Sep 24 15:53:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GRZzs-0006KL-Da; Sun, 24 Sep 2006 15:50:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GRZzo-0006GW-Ok
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 15:50:36 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GRZzo-0007Ep-M6
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 15:50:36 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GRZzk-0001Ti-A7
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 15:50:36 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 0351D17594;
	Sun, 24 Sep 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GRZzF-0007yw-IT; Sun, 24 Sep 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GRZzF-0007yw-IT@stiedprstage1.ietf.org>
Date: Sun, 24 Sep 2006 15:50:01 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-te-mib-00.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

	Title		: Point-to-Multipoint Multiprotocol Label 
                          Switching (MPLS) Traffic Engineering (TE) 
                          Management Information Base (MIB) module
	Author(s)	: A. Farrel, et al.
	Filename	: draft-ietf-mpls-p2mp-te-mib-00.txt
	Pages		: 42
	Date		: 2006-9-24
	
   This memo defines a portion of the Management Information Base
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for point-to-multipoint
   Multiprotocol Label Switching-based traffic engineering.


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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mpls-p2mp-te-mib-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-p2mp-te-mib-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-p2mp-te-mib-00.txt

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

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


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Sun Sep 24 15:53:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GRZzV-0006Cl-8r; Sun, 24 Sep 2006 15:50:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GRZzI-00062N-04
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 15:50:04 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GRZzF-0007D7-Me
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id A4BF032891;
	Sun, 24 Sep 2006 19:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GRZzF-0007ys-Hp; Sun, 24 Sep 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GRZzF-0007ys-Hp@stiedprstage1.ietf.org>
Date: Sun, 24 Sep 2006 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-lsp-ping-02.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

	Title		: Detecting Data Plane Failures in Point-to-Multipoint Multiprotocol
	Author(s)	: A. Farrel, S. Yasukawa
	Filename	: draft-ietf-mpls-p2mp-lsp-ping-02.txt
	Pages		: 25
	Date		: 2006-9-24
	
Recent proposals have extended the scope of Multiprotocol Label
Switching (MPLS) Label Switched Paths (LSPs) to encompass
point-to-multipoint (P2MP) LSPs.

The requirement for a simple and efficient mechanism that can be
used to detect data plane failures in point-to-point (P2P) MPLS LSPs
has been recognised and has led to the development of techniques
for fault detection and isolation commonly referred to as "LSP Ping".

The scope of this document is fault detection and isolation for P2MP
MPLS LSPs. This documents does not replace any of the mechanism of
LSP Ping, but clarifies their applicability to MPLS P2MP LSPs, and
extends the techniques and mechanisms of LSP Ping to the MPLS P2MP
environment.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-lsp-ping-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mpls-p2mp-lsp-ping-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-p2mp-lsp-ping-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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


--OtherAccess--

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

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

--NextPart--





From mpls-bounces@lists.ietf.org Sun Sep 24 16:22:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GRaRR-0007dI-5S; Sun, 24 Sep 2006 16:19:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GRaRO-0007d9-R2
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 16:19:06 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GRaRL-00035Q-9X
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 16:19:06 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1GRaQw-000508-00
	for mpls@lists.ietf.org; Sun, 24 Sep 2006 21:18:38 +0100
Received: from your029b8cecfe ([217.158.132.45] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 24 Sep 2006 21:18:40 +0100
Message-ID: <125301c6e016$9d9cd040$0a23fea9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mpls@lists.ietf.org>
References: <E1GRZzF-0007ys-Hp@stiedprstage1.ietf.org>
Subject: Re: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-lsp-ping-02.txt 
Date: Sun, 24 Sep 2006 21:18:28 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 24 Sep 2006 20:18:41.0266 (UTC)
	FILETIME=[A0767D20:01C6E016]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi all,

The main change in this document is to incorporate work from 
draft-swallow-mpls-mcast-cv-00.txt as discussed in Montreal.

There is a "changes" section in the I-D to help you identify what we have 
changed.

Thanks,
Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <mpls@lists.ietf.org>
Sent: Sunday, September 24, 2006 8:50 PM
Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-lsp-ping-02.txt


>A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiprotocol Label Switching Working 
> Group of the IETF.
>
> Title : Detecting Data Plane Failures in Point-to-Multipoint Multiprotocol
> Author(s) : A. Farrel, S. Yasukawa
> Filename : draft-ietf-mpls-p2mp-lsp-ping-02.txt
> Pages : 25
> Date : 2006-9-24
>
> Recent proposals have extended the scope of Multiprotocol Label
> Switching (MPLS) Label Switched Paths (LSPs) to encompass
> point-to-multipoint (P2MP) LSPs.
>
> The requirement for a simple and efficient mechanism that can be
> used to detect data plane failures in point-to-point (P2P) MPLS LSPs
> has been recognised and has led to the development of techniques
> for fault detection and isolation commonly referred to as "LSP Ping".
>
> The scope of this document is fault detection and isolation for P2MP
> MPLS LSPs. This documents does not replace any of the mechanism of
> LSP Ping, but clarifies their applicability to MPLS P2MP LSPs, and
> extends the techniques and mechanisms of LSP Ping to the MPLS P2MP
> environment.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-lsp-ping-02.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-ietf-mpls-p2mp-lsp-ping-02.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv@ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-mpls-p2mp-lsp-ping-02.txt".
>
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


--------------------------------------------------------------------------------


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



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



From mpls-bounces@lists.ietf.org Mon Sep 25 10:56:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GRro1-00027I-2T; Mon, 25 Sep 2006 10:51:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GRrnj-0001rD-BX
	for mpls@lists.ietf.org; Mon, 25 Sep 2006 10:51:19 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GRrmU-0002RT-Je
	for mpls@lists.ietf.org; Mon, 25 Sep 2006 10:50:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 8E327328B7;
	Mon, 25 Sep 2006 14:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GRrmU-0005Jh-Dt; Mon, 25 Sep 2006 10:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GRrmU-0005Jh-Dt@stiedprstage1.ietf.org>
Date: Mon, 25 Sep 2006 10:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-rfc3036bis-04.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

	Title		: LDP Specification
	Author(s)	: L. Andersson, et al.
	Filename	: draft-ietf-mpls-rfc3036bis-04.txt
	Pages		: 138
	Date		: 2006-9-25
	
The architecture for Multi Protocol Label Switching (MPLS) is
described in RFC 3031 [RFC3031]. A fundamental concept in MPLS is
that two Label Switching Routers (LSRs) must agree on the meaning of
the labels used to forward traffic between and through them.  This
common understanding is achieved by using a set of procedures, called
a label distribution protocol, by which one LSR informs another of
label bindings it has made.  This document defines a set of such
procedures called LDP (for Label Distribution Protocol) by which LSRs
distribute labels to support MPLS forwarding along normally routed
paths.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mpls-rfc3036bis-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-rfc3036bis-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Mon Sep 25 20:14:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GS0Tw-0000FV-Sk; Mon, 25 Sep 2006 20:07:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GS0RG-00081C-V3
	for mpls@ietf.org; Mon, 25 Sep 2006 20:04:42 -0400
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GS0Fc-0006dm-8V
	for mpls@ietf.org; Mon, 25 Sep 2006 19:52:44 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id k8PNqVX89204; 
	Mon, 25 Sep 2006 16:52:31 -0700 (PDT) (envelope-from ina@juniper.net)
Received: from garnet.juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k8PNpgg02741;
	Mon, 25 Sep 2006 16:51:44 -0700 (PDT) (envelope-from ina@juniper.net)
Date: Mon, 25 Sep 2006 16:51:42 -0700 (PDT)
From: Ina Minei <ina@juniper.net>
To: mpls@ietf.org
Message-ID: <20060925163916.S8419@garnet.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: Bob Thomas <rhthomas@cisco.com>
Subject: [mpls] draft-ietf-mpls-rfc3036bis-04.txt was posted
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org


 	Following the IESG review, draft-ietf-mpls-rfc3036bis-04.txt was 
sent back for more updates. The new version is at.
http://www.ietf.org/internet-drafts/draft-ietf-mpls-rfc3036bis-04.txt

 	The draft will have to go through last call once more after the 
initial review period.

 	Please take a few minutes to review. (a list of changes is at the 
end of this mail).

 			Thank you,

 				Ina


Changes done
=============

Content
-------
- added text regarding disabling sending vendor-private TLVs and messages
(interoperability requirement)
- spelled out the problem that can be caused by spoofed hello messages
(this was a requirement from the security ADs)
- label-mapping procedures - fix the procedures for receipt of a
duplicate label-map for the same fec with a different label.


Editorial
---------
- section 3.5 - added text to say that parameters in a message can end
at odd byte boundaries
- section 2.5.3 - spell out VPI, VCI, DLCI
- section 5.3 - fix should to SHOULD
- section 6 - spell out CoS
- moved RFC2385 (md5) to normative references, as LDP requires support
of it via a MUST statement
- added reference to 4271 and 4278 and text for standards maturity
variance with regards to the MD5 option.
- removed dependency on 3032 as a normative reference by showing
how the label is justified inside a 32 bit field, and stating the
value of the implicit nulllabel.
- removed dependency on 3031 as a normative reference by quoting the
definition of the implicit null label.
- removed the dependency on 3034 as a normative reference  by
including the relevant packet formats from 3034.
- moved refernces to 3031, 3032 and 3034 to informative
- In the definition of LDP Identifier, changed "must" to "MUST" and
"should" to "SHOULD"
- section 3.6 removed should to avoid confusion - "how an LSR should
handle" becomes "how an LSR handles".
- section 2.4.6 - changed must to MUST
- section 2.8 -must to MUST
- a couple of other must/should changes
- added text to say that the document assumes but doesn't require
familiarity with 3031 (to help us move 3031 to informative)
- removed reference to rfc1700 and replaced it with a link to
http://www.iana.org/assignments/address-family-numbers
- removed 1771 and replaced with 4271 in the references
- We had previously removed "MPLS using ATM VP Switching" from the list of
references, but the doc was still referencing it. I removet the 
references.
- I added 2328 to the list of references - somehow it had gotten removed, 
already in version 1 (by mistake), and there was a reference to it in the 
draft.



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



From mpls-bounces@lists.ietf.org Tue Sep 26 04:21:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GS87N-00054Z-74; Tue, 26 Sep 2006 04:16:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GS87L-00054G-Ig; Tue, 26 Sep 2006 04:16:39 -0400
Received: from [69.3.57.5] (helo=mailserver.corp.int.mrv.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GS87L-0003Mu-5u; Tue, 26 Sep 2006 04:16:39 -0400
Received: from chmailsrv.int.mrv.com ([192.168.11.19]) by
	mailserver.corp.int.mrv.com with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id TTHP10M4; Tue, 26 Sep 2006 01:16:37 -0700
Received: from zeus.yok.int.mrv.com ([172.21.9.11]) by chmailsrv.int.mrv.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Sep 2006 01:16:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Sep 2006 11:11:32 +0300
Message-ID: <685D66DF6DB563459D23ECD8B30C73A40CD3F1@zeus.yok.int.mrv.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s 
Thread-Index: AcbhQ2C0b+kGgpGHTcK7Xfpa7iFlsA==
From: "Asaf Henig" <ahenig@mrv.com>
To: <l2vpn@ietf.org>,
	<mpls@lists.ietf.org>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 26 Sep 2006 08:16:37.0522 (UTC)
	FILETIME=[16534720:01C6E144]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
Subject: [mpls] Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0629203724=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============0629203724==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E143.60C5C9D2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It is yet unclear from draft =
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt who =
is responsible to send the MAC Withdrawal message to the secondary PE-rs =
when fail-over occures in an H-VPLS dual homed MTU-s scenario.=20

It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this "secondary" =
PE-rs should flush the relevant previously learned MAC addresses. For =
that to happen we have two options:
  =20
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.=20
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).

Which option is preferred  ?=20


Thanks for any help.  =20
Asaf Henig
MRV communications




------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTFrom mpls-bounces@lists.ietf.org Tue Sep 26 04:21:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GS87N-00054Z-74; Tue, 26 Sep 2006 04:16:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GS87L-00054G-Ig; Tue, 26 Sep 2006 04:16:39 -0400
Received: from [69.3.57.5] (helo=mailserver.corp.int.mrv.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GS87L-0003Mu-5u; Tue, 26 Sep 2006 04:16:39 -0400
Received: from chmailsrv.int.mrv.com ([192.168.11.19]) by
	mailserver.corp.int.mrv.com with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id TTHP10M4; Tue, 26 Sep 2006 01:16:37 -0700
Received: from zeus.yok.int.mrv.com ([172.21.9.11]) by chmailsrv.int.mrv.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Sep 2006 01:16:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Sep 2006 11:11:32 +0300
Message-ID: <685D66DF6DB563459D23ECD8B30C73A40CD3F1@zeus.yok.int.mrv.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s 
Thread-Index: AcbhQ2C0b+kGgpGHTcK7Xfpa7iFlsA==
From: "Asaf Henig" <ahenig@mrv.com>
To: <l2vpn@ietf.org>,
	<mpls@lists.ietf.org>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 26 Sep 2006 08:16:37.0522 (UTC)
	FILETIME=[16534720:01C6E144]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
Subject: [mpls] Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0629203724=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============0629203724==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E143.60C5C9D2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It is yet unclear from draft =
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt who =
is responsible to send the MAC Withdrawal message to the secondary PE-rs =
when fail-over occures in an H-VPLS dual homed MTU-s scenario.=20

It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this "secondary" =
PE-rs should flush the relevant previously learned MAC addresses. For =
that to happen we have two options:
  =20
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.=20
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).

Which option is preferred  ?=20


Thanks for any help.  =20
Asaf Henig
MRV communications




------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s =
</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>It is yet unclear from draft <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.=
txt">http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt=
</A> who is responsible to send the MAC Withdrawal message to the =
secondary PE-rs when fail-over occures in an H-VPLS dual homed MTU-s =
scenario.<BR>
<BR>
It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this =
&quot;secondary&quot; PE-rs should flush the relevant previously learned =
MAC addresses. For that to happen we have two options:<BR>
&nbsp;&nbsp;<BR>
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.<BR>
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).<BR>
<BR>
Which option is preferred&nbsp; ?<BR>
<BR>
<BR>
Thanks for any help.&nbsp;&nbsp;<BR>
Asaf Henig<BR>
MRV communications<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6E143.60C5C9D2--


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

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

--===============0629203724==--


From mpls-bounces@lists.ietf.org Tue Sep 26 04:21:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GS87Q-00054r-2Q; Tue, 26 Sep 2006 04:16:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GS87M-00054U-G1
	for mpls@lists.ietf.org; Tue, 26 Sep 2006 04:16:40 -0400
Received: from [69.3.57.5] (helo=mailserver.corp.int.mrv.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GS87L-0003Mt-3D
	for mpls@lists.ietf.org; Tue, 26 Sep 2006 04:16:40 -0400
Received: from chmailsrv.int.mrv.com ([192.168.11.19]) by
	mailserver.corp.int.mrv.com with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id TTHP10M4; Tue, 26 Sep 2006 01:16:37 -0700
Received: from zeus.yok.int.mrv.com ([172.21.9.11]) by chmailsrv.int.mrv.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Sep 2006 01:16:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Sep 2006 11:11:32 +0300
Message-ID: <685D66DF6DB563459D23ECD8B30C73A40CD3F1@zeus.yok.int.mrv.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s 
Thread-Index: AcbhQ2C0b+kGgpGHTcK7Xfpa7iFlsA==
From: "Asaf Henig" <ahenig@mrv.com>
To: <l2vpn@ietf.org>,
	<mpls@lists.ietf.org>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 26 Sep 2006 08:16:37.0522 (UTC)
	FILETIME=[16534720:01C6E144]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
Subject: [mpls] Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subjENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s =
</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>It is yet unclear from draft <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.=
txt">http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt=
</A> who is responsible to send the MAC Withdrawal message to the =
secondary PE-rs when fail-over occures in an H-VPLS dual homed MTU-s =
scenario.<BR>
<BR>
It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this =
&quot;secondary&quot; PE-rs should flush the relevant previously learned =
MAC addresses. For that to happen we have two options:<BR>
&nbsp;&nbsp;<BR>
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.<BR>
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).<BR>
<BR>
Which option is preferred&nbsp; ?<BR>
<BR>
<BR>
Thanks for any help.&nbsp;&nbsp;<BR>
Asaf Henig<BR>
MRV communications<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6E143.60C5C9D2--


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

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

--===============0629203724==--


From mpls-bounces@lists.ietf.org Tue Sep 26 04:21:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GS87Q-00054r-2Q; Tue, 26 Sep 2006 04:16:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GS87M-00054U-G1
	for mpls@lists.ietf.org; Tue, 26 Sep 2006 04:16:40 -0400
Received: from [69.3.57.5] (helo=mailserver.corp.int.mrv.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GS87L-0003Mt-3D
	for mpls@lists.ietf.org; Tue, 26 Sep 2006 04:16:40 -0400
Received: from chmailsrv.int.mrv.com ([192.168.11.19]) by
	mailserver.corp.int.mrv.com with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id TTHP10M4; Tue, 26 Sep 2006 01:16:37 -0700
Received: from zeus.yok.int.mrv.com ([172.21.9.11]) by chmailsrv.int.mrv.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Sep 2006 01:16:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Sep 2006 11:11:32 +0300
Message-ID: <685D66DF6DB563459D23ECD8B30C73A40CD3F1@zeus.yok.int.mrv.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s 
Thread-Index: AcbhQ2C0b+kGgpGHTcK7Xfpa7iFlsA==
From: "Asaf Henig" <ahenig@mrv.com>
To: <l2vpn@ietf.org>,
	<mpls@lists.ietf.org>,
	<mpls@ietf.org>
X-OriginalArrivalTime: 26 Sep 2006 08:16:37.0522 (UTC)
	FILETIME=[16534720:01C6E144]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
Subject: [mpls] Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2131143910=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============2131143910==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E143.60C5C9D2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It is yet unclear from draft =
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt who =
is responsible to send the MAC Withdrawal message to the secondary PE-rs =
when fail-over occures in an H-VPLS dual homed MTU-s scenario.=20

It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this "secondary" =
PE-rs should flush the relevant previously learned MAC addresses. For =
that to happen we have two options:
  =20
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.=20
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).

Which option is preferred  ?=20


Thanks for any help.  =20
Asaf Henig
MRV communications




------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s =
</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>It is yet unclear from draft <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.=
txt">http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt=
</A> who is responsible to send the MAC Withdrawal message to the =
secondary PE-rs when fail-over occures in an H-VPLS dual homed MTU-s =
scenario.<BR>
<BR>
It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this =
&quot;secondary&quot; PE-rs should flush the relevant previously learned =
MAC addresses. For that to happen we have two options:<BR>
&nbsp;&nbsp;<BR>
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.<BR>
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).<BR>
<BR>
Which option is preferred&nbsp; ?<BR>
<BR>
<BR>
Thanks for any help.&nbsp;&nbsp;<BR>
Asaf Henig<BR>
MRV communications<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6E143.60C5C9D2--


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

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

--===============2131143910==--






ect=subscribe>
Content-Type: multipart/mixed; boundary="===============2131143910=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============2131143910==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E143.60C5C9D2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It is yet unclear from draft =
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt who =
is responsible to send the MAC Withdrawal message to the secondary PE-rs =
when fail-over occures in an H-VPLS dual homed MTU-s scenario.=20

It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this "secondary" =
PE-rs should flush the relevant previously learned MAC addresses. For =
that to happen we have two options:
  =20
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.=20
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).

Which option is preferred  ?=20


Thanks for any help.  =20
Asaf Henig
MRV communications




------_=_NextPart_001_01C6E143.60C5C9D2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>Question regarding MAC Withdrawal in H-VPLS Dual-homed MTU-s =
</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>It is yet unclear from draft <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.=
txt">http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-09.txt=
</A> who is responsible to send the MAC Withdrawal message to the =
secondary PE-rs when fail-over occures in an H-VPLS dual homed MTU-s =
scenario.<BR>
<BR>
It is known that when a primary VC fails in a dual-homing scenario the =
PE-rs connected to the secondary VC should relearn the MAC addresses =
behind the MTU-s. In order to make this process faster this =
&quot;secondary&quot; PE-rs should flush the relevant previously learned =
MAC addresses. For that to happen we have two options:<BR>
&nbsp;&nbsp;<BR>
A) The primary PE-rs would send the MAC Withdrawal message to the =
secondary PE-rs (and all other PE-s) the minute it recognizes that its =
VC has failed.<BR>
B) The MTU-s itself would send the MAC Withdrawal to the secondary PE-rs =
the minute it switches from primary to secondary VC. The secondary PE-rs =
would be responsible to propegate this message to all other PEs in the =
VPLS domain (this option is recommended by =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-00.txt).<BR>
<BR>
Which option is preferred&nbsp; ?<BR>
<BR>
<BR>
Thanks for any help.&nbsp;&nbsp;<BR>
Asaf Henig<BR>
MRV communications<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6E143.60C5C9D2--


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

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

--===============2131143910==--






From mpls-bounces@lists.ietf.org Tue Sep 26 11:34:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSErj-0007VI-FD; Tue, 26 Sep 2006 11:28:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSEri-0007V4-8W
	for mpls@ietf.org; Tue, 26 Sep 2006 11:28:58 -0400
Received: from [80.86.78.228] (helo=smtp.testbed.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSErg-0000rn-Uq
	for mpls@ietf.org; Tue, 26 Sep 2006 11:28:58 -0400
Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.31])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43)
	id 1GSEre-0003b1-M3; Tue, 26 Sep 2006 17:28:55 +0200
Message-ID: <45194728.5060008@pi.se>
Date: Tue, 26 Sep 2006 17:28:40 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: mpls@ietf.org, George Swallow <swallow@cisco.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
Subject: [mpls] implementation poll on draft-ietf-mpls-rsvp-te-p2mp-06
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

All,

we are considering sending draft-ietf-mpls-rsvp-te-p2mp-06 to
the IESG to be reviewed to become an RFC on the standards track.
To that end we need to know of existing implementations, could
you please respond to the wg co-chairs if you have an implementation
of the draft.

Loa and George

-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Tue Sep 26 15:17:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSIL8-00085M-2k; Tue, 26 Sep 2006 15:11:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSIL7-00085H-Dm
	for mpls@ietf.org; Tue, 26 Sep 2006 15:11:33 -0400
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSIL5-0006FX-2k
	for mpls@ietf.org; Tue, 26 Sep 2006 15:11:33 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id k8QJBSX11300
	for <mpls@ietf.org>; Tue, 26 Sep 2006 12:11:30 -0700 (PDT)
	(envelope-from dchuang@juniper.net)
Received: from [172.17.58.35] (dchuang-bsd.juniper.net [172.17.58.35])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k8QJBNg12146
	for <mpls@ietf.org>; Tue, 26 Sep 2006 12:11:23 -0700 (PDT)
	(envelope-from dchuang@juniper.net)
Message-ID: <45197B5A.8050401@juniper.net>
Date: Tue, 26 Sep 2006 12:11:22 -0700
From: Daniel Chuang <dchuang@juniper.net>
Organization: Juniper
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050216
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mpls@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 
Subject: [mpls] mplsTunnelInstance in MPLS TE MIB
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi,

   In the rfc3812(TE)/rfc3811(TC) mib, mplsTunnelInstance definition 
mentions:

When the MPLS signaling protocol is
rsvp(2) this value SHOULD be equal to the LSP Id
of the Sender Template object.

This is 'SHOULD',  but  based on rfc2119 definition:

3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

What is the valid reason for not being 'MUST' then any internal/other
value can be used as vendors see fit ?

thanks,
Daniel

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



From mpls-bounces@lists.ietf.org Tue Sep 26 15:59:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSJ2S-0006x3-E8; Tue, 26 Sep 2006 15:56:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSJ2R-0006uC-Nv
	for mpls@ietf.org; Tue, 26 Sep 2006 15:56:19 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSJ2Q-0007Tk-E8
	for mpls@ietf.org; Tue, 26 Sep 2006 15:56:19 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 26 Sep 2006 12:56:18 -0700
X-IronPort-AV: i="4.09,221,1157353200"; 
	d="scan'208"; a="43739663:sNHT32678260"
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.20060308/8.12.11) with ESMTP id
	k8QJuIDK010172; Tue, 26 Sep 2006 15:56:18 -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.12.10/8.12.6) with ESMTP id k8QJuIdM013533; 
	Tue, 26 Sep 2006 15:56:18 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Sep 2006 15:56:17 -0400
Received: from [161.44.71.206] ([161.44.71.206]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Sep 2006 15:56:17 -0400
In-Reply-To: <45197B5A.8050401@juniper.net>
References: <45197B5A.8050401@juniper.net>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <45AF86C3-52EE-4BBF-9984-92E0DCAA8E33@cisco.com>
Content-Transfer-Encoding: 7bit
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: [mpls] mplsTunnelInstance in MPLS TE MIB
Date: Tue, 26 Sep 2006 15:56:30 -0400
To: Daniel Chuang <dchuang@juniper.net>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 26 Sep 2006 19:56:17.0694 (UTC)
	FILETIME=[D4752BE0:01C6E1A5]
DKIM-Signature: a=rsa-sha1; q=dns; l=1518; t=1159300578; x=1160164578;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tnadeau@cisco.com;
	z=From:=22Thomas=20D.=20Nadeau=22=20<tnadeau@cisco.com>
	|Subject:Re=3A=20[mpls]=20mplsTunnelInstance=20in=20MPLS=20TE=20MIB
	|To:Daniel=20Chuang=20<dchuang@juniper.net>;
	X=v=3Dcisco.com=3B=20h=3DFzCBMkIs3BXWjOktg9gTGWruFDY=3D;
	b=ZG2bwTeZGRPfKq41We9dwzno5ACnquVJgRNMRXBOKifsEsRH4bQZOshRCtoJKAQTVRz3ktg5
	zEwb4zPBCJLul31Lp+SvIBDlMzj66gJHpgCEMWrAUCJ5KVI2tImXigw3;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=tnadeau@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org


	I am glad that you guys are finally getting
around to implementing the MPLS-TE-MIB. *)

	To answer your question, the use of SHOULD
in the text is there to denote that "most of the time"
this is the recommended usage. In practice, we also
made this recommendation based on how the implementations
at the time chose the contents of that value. The idea
is that the indexes are most useful when they correlate
as closely as possible to the signaled values. Also,
the SHOULD here denotes the fact that the exceptional
case of mplsTunnelInstance=0 denotes a tunnel head,
and thus in this case does not correlate to any Sender
Template object.

	--Tom



> Hi,
>
>   In the rfc3812(TE)/rfc3811(TC) mib, mplsTunnelInstance definition  
> mentions:
>
> When the MPLS signaling protocol is
> rsvp(2) this value SHOULD be equal to the LSP Id
> of the Sender Template object.
>
> This is 'SHOULD',  but  based on rfc2119 definition:
>
> 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
>   may exist valid reasons in particular circumstances to ignore a
>   particular item, but the full implications must be understood and
>   carefully weighed before choosing a different course.
>
> What is the valid reason for not being 'MUST' then any internal/other
> value can be used as vendors see fit ?
>
> thanks,
> Daniel
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls

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



From mpls-bounces@lists.ietf.org Tue Sep 26 19:18:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSM7u-0004gg-Ft; Tue, 26 Sep 2006 19:14:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSM7s-0004gY-Jd; Tue, 26 Sep 2006 19:14:08 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GSM7r-0007vM-7q; Tue, 26 Sep 2006 19:14:08 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k8QNE6Ij024774; 
	Tue, 26 Sep 2006 16:14:06 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k8QNE69b024773;
	Tue, 26 Sep 2006 16:14:06 -0700
Date: Tue, 26 Sep 2006 16:14:06 -0700
Message-Id: <200609262314.k8QNE69b024773@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: mpls@lists.ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 4687 on Operations and Management (OAM) Requirements for
	Point-to-Multipoint MPLS Networks
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org


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

        
        RFC 4687

        Title:      Operations and Management (OAM) Requirements 
                    for Point-to-Multipoint MPLS Networks 
        Author:     S. Yasukawa, A. Farrel,
                    D. King, T. Nadeau
        Status:     Informational
        Date:       September 2006
        Mailbox:    s.yasukawa@hco.ntt.co.jp, 
                    adrian@olddog.co.uk, 
                    daniel.king@aria-networks.com,  tnadeau@cisco.com
        Pages:      14
        Characters: 30486
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-p2mp-oam-reqs-01.txt

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

Multi-Protocol Label Switching (MPLS) has been extended to encompass
point-to-multipoint (P2MP) Label Switched Paths (LSPs).  As with
point-to-point MPLS LSPs, the requirement to detect, handle, and
diagnose control and data plane defects is critical.

For operators deploying services based on P2MP MPLS LSPs, the
detection and specification of how to handle those defects are
important because such defects not only may affect the fundamentals
of an MPLS network, but also may impact service level
specification commitments for customers of their network.

This document describes requirements for data plane operations and
management for P2MP MPLS LSPs.  These requirements apply to all forms
of P2MP MPLS LSPs, and include P2MP Traffic Engineered (TE) LSPs and
multicast LSPs.  This memo provides information for the Internet 
community.

This document is a product of the Multiprotocol Label Switching
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



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



From mpls-bounces@lists.ietf.org Wed Sep 27 02:22:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSSic-0007VA-Hv; Wed, 27 Sep 2006 02:16:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSSia-0007UF-JG
	for mpls@ietf.org; Wed, 27 Sep 2006 02:16:28 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSSiZ-00087a-4J
	for mpls@ietf.org; Wed, 27 Sep 2006 02:16:28 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Sep 2006 08:16:14 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 27 Sep 2006 08:16:33 +0200
Message-ID: <D109C8C97C15294495117745780657AE05E49086@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-leroux-mpls-p2mp-te-bypass-00.txt
Thread-Index: Acbh/Hqlp6t3u/GTSEWExddnH+tZnw==
From: "LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@orange-ft.com>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 27 Sep 2006 06:16:14.0936 (UTC)
	FILETIME=[6FBDDD80:01C6E1FC]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
Subject: [mpls] draft-leroux-mpls-p2mp-te-bypass-00.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1473541307=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============1473541307==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E1FC.6F723D22"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E1FC.6F723D22
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

The below draft defines procedures for P2MP RSVP-TE Fast Reroute with
P2MP Bypass LSPs.
http://www.ietf.org/internet-drafts/draft-leroux-mpls-p2mp-te-bypass-00.
txt

Your comments are welcomed.

Regards,

JL




------_=_NextPart_001_01C6E1FC.6F723D22
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>draft-leroux-mpls-p2mp-te-bypass-00.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D4 FACE=3D"Arial">Hi all,</FONT>
</P>

<P><FONT SIZE=3D4 FACE=3D"Arial">The below draft defines procedures for =
P2MP RSVP-TE Fast Reroute with P2MP Bypass LSPs.</FONT>

<BR><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-leroux-mpls-p2mp-te-byp=
ass-00.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D4 =
FACE=3D"Arial">http://www.ietf.org/internet-drafts/draft-leroux-mpls-p2mp=
-te-bypass-00.txt</FONT></U></A>
</P>

<P><FONT SIZE=3D4 FACE=3D"Arial">Your comments are welcomed.</FONT>
</P>

<P><FONT SIZE=3D4 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT SIZE=3D4 FACE=3D"Arial">JL</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C6E1FC.6F723D22--


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

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

--===============1473541307==--




From betwixtakin@rpm-mortgage.com Wed Sep 27 05:03:17 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSVK1-0005Mu-Cc; Wed, 27 Sep 2006 05:03:17 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GSVK1-0003E4-5i; Wed, 27 Sep 2006 05:03:17 -0400
Received: from [59.54.62.94] (helo=JJ-4DFCB2B54186.1c2rzrdm.org)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GSVJy-0006h8-6i; Wed, 27 Sep 2006 05:03:16 -0400
Message-ID: <01418621808608.8C69B26FA4@OFZQ>
From: "brushwork" <betwixtakin@royalbuying.com>
To: <mpls@lists.ietf.org>
Subject: come and see Low-risk opportunity for tomorrow
Date: Wed, 27 Sep 2006 17:07:50 +0800
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: 8imO6S1chC1LIVopVehKtEfXeVhyaBRNY2JO
Content-type: multipart/related;
        boundary="----=_NextPart_000_0009_AA4C18C6.156A7092"
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 681e62a2ce9b0804b459fe780d892beb

------=_NextPart_000_0009_AA4C18C6.156A7092
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit

<HTML><HEAD>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<div align="left"><IMG alt="" hspace=0 
src="cid:T8KDS4X5BC2F28J20LEM" align=baseline 
border=0></div>
<div align="left"><FONT face=Arial size=2></FONT><FONT face=Arial =
size=2>after Rooney's red card have come to define another England exit.</FONT><FONT face=Arial =
size=2>U.S. Support for Afghanistan's Counternarcotics Campaign</FONT><br><br>
  <FONT face=Arial =
size=2>Thank goodness then for Italians Fabio Grosso and Alessandro del Piero, scorers of</FONT><br><br><FONT face=Arial =
size=2>embroiled in a corruption scandal similar to 1982 when they last won the World Cup.</FONT><FONT face=Arial =
size=2>Beckham almost won a penalty with his last contribution of the game - and probably</FONT><br><FONT face=Arial =
size=2>E, before tamely exiting the competition 3-0 at the hands of Brazil in the second</FONT><FONT face=Arial =
size=2>Text of resolution -- UN Security Council Resolution 1706 (2006)</FONT><br><FONT face=Arial =
size=2>Cannavaro won the World Cup on his 100th appearance for Italy</FONT><FONT face=Arial =
size=2>and service to this position.</FONT><br><FONT face=Arial =
size=2>and service to this position.</FONT><FONT face=Arial =
size=2>Hugo Viana and Armando Petit had missed to give Eriksson's side brief hope, but</FONT><br><FONT face=Arial =
size=2>A deflected John Terry shot just looped over the bar after some brilliant work from an</FONT><FONT face=Arial =
size=2>that was settled in extra-time by Rodriguez's thunderbolt from the blue.</FONT><br><FONT face=Arial =
size=2>McClaren should also send 17-year-old Theo Walcott back to school with Arsenal.</FONT><FONT face=Arial =
size=2>And, once identified, we must move quickly to disburse funds in order that our good</FONT><br><br><FONT face=Arial =
size=2>they all had major tournament experience.</FONT><FONT face=Arial =
size=2>This time round, classic encounters have been hard to find.</FONT><br><FONT face=Arial =
size=2>Argentina lit up Group C with some great efforts, most notably Esteban Cambiasso's</FONT><FONT face=Arial =
size=2>The U.S. Department of Energy's (DOE) Energy Sciences Network (ESnet) and</FONT><br><FONT face=Arial =
size=2>He looked a spent force for much of his time in Germany, and England have talent in</FONT></div>
</BODY></HTML>

------=_NextPart_000_0009_AA4C18C6.156A7092
Content-Type: image/gif;
        name="breton.gif"
Content-Transfer-Encoding: base64
Content-ID: <T8KDS4X5BC2F28J20LEM>

R0lGODlhkgEVAvcAAAAAAIAAAACAAICAAAAAgIAAgACAgICAgMDAwP8AAAD/AP//AAAA//8A/wD/
/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMwAAZgAAmQAAzAAA/wAzAAAzMwAzZgAzmQAzzAAz/wBm
AABmMwBmZgBmmQBmzABm/wCZAACZMwCZZgCZmQCZzACZ/wDMAADMMwDMZgDMmQDMzADM/wD/AAD/
MwD/ZgD/mQD/zAD//zMAADMAMzMAZjMAmTMAzDMA/zMzADMzMzMzZjMzmTMzzDMz/zNmADNmMzNm
ZjNmmTNmzDNm/zOZADOZMzOZZjOZmTOZzDOZ/zPMADPMMzPMZjPMmTPMzDPM/zP/ADP/MzP/ZjP/
mTP/zDP//2YAAGYAM2YAZmYAmWYAzGYA/2YzAGYzM2YzZmYzmWYzzGYz/2ZmAGZmM2ZmZmZmmWZm
zGZm/2aZAGaZM2aZZmaZmWaZzGaZ/2bMAGbMM2bMZmbMmWbMzGbM/2b/AGb/M2b/Zmb/mWb/zGb/
/5kAAJkAM5kAZpkAmZkAzJkA/5kzAJkzM5kzZpkzmZkzzJkz/5lmAJlmM5lmZplmmZlmzJlm/5mZ
AJmZM5mZZpmZmZmZzJmZ/5nMAJnMM5nMZpnMmZnMzJnM/5n/AJn/M5n/Zpn/mZn/zJn//8wAAMwA
M8wAZswAmcwAzMwA/8wzAMwzM8wzZswzmcwzzMwz/8xmAMxmM8xmZsxmmcxmzMxm/8yZAMyZM8yZ
ZsyZmcyZzMyZ/8zMAMzMM8zMZszMmczMzMzM/8z/AMz/M8z/Zsz/mcz/zMz///8AAP8AM/8AZv8A
mf8AzP8A//8zAP8zM/8zZv8zmf8zzP8z//9mAP9mM/9mZv9mmf9mzP9m//+ZAP+ZM/+ZZv+Zmf+Z
zP+Z///MAP/MM//MZv/Mmf/MzP/M////AP//M///Zv//mf//zP///yH5BAEAABAALAAAAACSARUC
AAj/AP8JHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuX
MGPKnEmzps2bOHPq3Mmzp8+fQCty4zZw6EB1Q+PhEzi0KVGC8ZByi8fU6dN/UpUOxBcvadWB49Qt
Jdi06NWqTv9Z1Wr17EGjQ8fCTTt1YFeyTqmqvRp2bNC/gFMa/fpvnF51Ys0a7LoUHzd1isEeTuyY
auW9AhH7Feg4LuHIoB+DVjgXMubBAhn/uxz58mDNgWPLHonaqOrVdT+b3Qz69uW7BY0i5f2vq3Hd
mPGGdotwLrelcwl23ru5NlHhz2dr377ROtaz3MaN/06dlDdqpGTFj2OeFDXB4aKTj6+tVz7p648h
R4fatP7nuV0xx92ABDbUFn7KIZdZU6b9Bx6CwbXnH1PqPeXeXnTl5deFzeHHmHPWsfeUaxIWaOKJ
CXmHXlHiKchZVqCtSKF9VS21nkF1AXfhjkQ51iCNHWIW1n529RdhU3JldyOKTDLpnW+5ASmdd+SN
9ZuInGVXZF408phlfRyWpZhRnUGYJX7VYYkbcU22ORuVhmX2I4fD4QbmWXFilZhaltVV24/A8dml
W+ddxeFbEEpln2okAvmnm5BuR2Vx5SVYUIDq+HdhgFpx1lWmn9VZI274ZZjhVrkdiiOE07kX5V1E
xv+oZaS01mrrrbjmquuuvPbq66/ABivssMQWa+yxyCar7LLM0jYpWmWtBa2q9xmJoVfXhpgkWPqh
GSq2Zo0oJoZJMvhZWNmWOi51X7Ul47iiRQXutGxZla1/nIZbaVsTzbWtva8+aC1q6N5a5raWEubj
eA8NtrDDonF4MGGwlUZYXayh1ZiYEyf38FMVCxhmfLE6Vu6XdS4cWrcRfrkaYqm1+KiLDll82lmM
RumxnyDvaWtlWnpp6bMQeWc0c8alStRtzkG39KwRgirvU0nrdTSlCLd8pNP2XenZh1APbaaDlKJK
1aTUMtT0zS0LzfZtt8Jnmtv/NZj2fUVxzRTLlz7/R/JUR8OMXYpTQZbpYB/OLW63ATLsaH5sk2U4
4FTdJZXPrfGstZDg8Z3x3XgPJfjYlM4rH4CgO1khcvxK67iBXN47rYWTo3XczSbvt25c102nVu2y
Y3g7vwry3qq96EUXn1Q63+v0qWvaB+JUGwpYM5p+q2voyFk+f/vPOWZHN2Yq06z24uT/XdDCqnm2
ZHRDEvXug0BPx774PSpto4UiYxk/jVX7zvfwcTnlqIxH1lrS3tI3J+vBTkiK2pS19KW/wjiwSQEy
0vggdqdVlQpRYxLX2dxSJs9AjGtkKgvTHmRB8aTQKXoz2c70tjnFlIlGE+sYqlhop0Et5iqN6mHx
/5yDIeW8kHT+SpjCwgapnI2whvIRVepAyJQnLsh3R8nOx7LEstcMBmOuetoTUxaxqyQPfYfi3ndI
l0MkfWdjDcwiFhVEQMgQUGZmDNoFF7KfCOJMi5pTY/lodTRTRQuISqOI61ADNIBtTz5g21keqWdA
/J3OTI0sUgmJJsl0CWQ9DVIUeR4zIUYCzpEIyddnWDNFEEJsbAGLnKXg1qxa2vKWuMylLnfJy176
8pfADKYwh0nMYhrzmMhMpjKXycxmOvOZ0IymNKdJzWpa85rYzKY2t8nNbnrzm+AMpzjHSc5ymvOc
6EynOtfJzna6853wjKc850nPetrznvjMpz73yf/PfvrznwANqEAHStCCGvSgCE2oQhfK0IY69KEQ
jWhKUEDRlaCAIBfVSEYPctGNTsSj/wApQkSKEZJK1CIbNalIKioQlUrEpC59CEhj2lKP0PSkMuUo
SztK0YzydCA9bWlQQwpUjBL1qEPlKUtDutOCKNWnFX0qUJtaU6NWlalQjWpUi9pRoaZ0qU7F6ldv
itOrFrWmWyVqU1N6VLWeFa1wRWtX3WpWrp7Vp22dK1Lb+la8xpWubKUqXflq17+SFaciDWxV9ZpV
xv51sUgNql+fSlLH7jWwPWUrR/Oa2bzu1bCdZWpCHHvYstbVs5NFbWEvG1a3Kpa1CrEsXl/bWoP/
WLavnx0sTEeqWtNChLZzne1sherZ0341sp+9rVE1O1zDPtaqVyXtYm+r3NVW17cjXWpSIftT4lLX
tlbdamqxWlfZOpe8xa2tV6MrWtHqFb3w9ahstYtdjpT2rbm8b31t+tJe6ne/AA6wgAdM4AIb2Fb3
/e9q1dpZ+WJ0u/g98K8SjNL2Dvautb2uhHuVWO1SVbqChWtzw5vh3G4YWDO1LmC56tewBlesDwav
iBV8Yial2Ln0Pa+LRaxT2yb1vTXmcIkV22INvxjIJiasZoMsZOiCeLrtrSxnCZvkG1OZybjKbFan
Ol7xRnnHC+briM1KYywTq8xmziaa08zmNrv5/81wjrOc2zRUjTq1zhGWKVidvOc5z2bJJS1xoJEs
2DX7OSaJtWtXtwxjPBM5smMt75VffOgBJVquxO3thVE7Yg3Dt7ChrbRsLq1bLqd106GlrVf7vODx
XlnUPyH1d52s5CGrd7RibnCeYQ2U1556ydKFLnuBu1kk59bQvG5Jnb1M5kJbuNbTjTSVl81nZCe7
lta+tra3ze1ue/vb4A63TbScEZpWVtfC3kiZS5vt/nbEygtptzPbbW5cn/bPLpG3jBmib2ZaedHS
Ju+Pj2tszEbbx43lcmvx7N31MtjDnGV0jBftcGDfWakXB/N2P/ze4GpV4uIkN2A73Vtfq/S4rv/F
L7EBrVyoqtbkJCazd4sMWwc/l+U0Xytypzps9o5TysNG912FfnLcutzWcnV0pmn9aB0fm+m4TXmH
T21qYRO91CqX7Kr7TUyga1rS0H51ejuO9E2rvOwUdzrNjR51iv877DbXdNrFzHaxfzPRRw/2iuPK
ap+nXOY4PjvLG85jvtt88O6NenqHDm2wMre7aXc849ce8qt3N747lTizBT3yqfuc4SAn/MYnH+NP
N1y+kr+3eGdKdp4DHMpxT3zmAZ1Orvf6oxSxfUV0/07e5yTUDQF+8Bk+E9+L+/jIT77yl8/85jv/
+dCPvvSnT/3qW//62M++9rfP/e57//vgD7//+MdP/vKb//zoT7/618/+9rv//fCPv/znT//62//+
+M+//vfP//77//8AGIACOIAEWIAGeIAImIAKuIAM2IAOGE1Ft263xlvvtnsKt3UXKHIiB14ORm4d
yFuR91t9BxJzt2v2pm7p1iS7FWgpuFkViHt+R3eP1XoupmqQZVyFd1i0t1JJFhH01oIoIlUCB2MV
F2HANnsY13TL1ndCaHqK53ekdmFAFoKXFnuYtXoXuGsbt4UZCGF/J4Og92WYF3BLGHEO92AJR4To
dYVkOIIWyFyBx137lnOgxmI9p3py54Jwl2daRllSdmSOBm9Ap3OAx3SAGIdYp14tN1wrp2JH/3eD
MlhqjYiInvaGGCaJobZbY/VrT7eJj8iBYTaHnBeFNLhchXdniuiCbBh7d0hyjYZhKwhltqaBP2Zq
LReDr0iJech6xHcR5iWJeghme0iH9/ZqekeBe4iDrVZsp3iJhRhzZqeMe6d35hWLkdhzb+eMMUh5
u+iI3giE5VZcJAeH1jiJLmdxOwiMePiEcUd2rAha0/aMg6hiUMd3mDZyY3eCifhlwcaJMOeMh0eN
JSeQ6VhhcIh1Xuh1RXiPmzeGgjd0iJeF5YWEjdViMxh2i3du4shqS9hlDOZ6+YiMkFaDByd6HkZw
pUd8mzdfKPl4AZcshmZ89rVvKvFf1shvZf+FbDIZjsGIEvp1kzj5gEI5lERZlEFYjEaIkTTJX5OG
lME3Ej+4lDBogpAYb8IXispkkT3plBMVWzyJb774W1x5dlLpb6+3XoGYemEofJkIcVumdQKXVgP3
kgOHcFm4kn+nkkhYgx9XhJrXlyzmeFh4hoA3ei75XLuUd1+HahnZmHHoj4/ZjYVJluoImc5Wd3Tn
a3YomfQoi4toeer4kcC0dkJ3c0vXmZwGl5W5arCFkFVohKp5h1+4gaw5eCanmrSYlIi3ilb3cqBF
db5EjIwpiMLYjsNYh5pJbEnpmIwZeAWpnJFJa6pYnNBobJmpaPaImLxEjMA5hY0Zkf3Yj8j/NY6o
yY3nCGoel4gB+Z11qGPHuI/CaYW++XnWqUucKHsdGJApBp5nKJeZN56Jt4YQiYpO6J8oKXu51mHw
yWkL2Z//WZ4seXEnqXYlGFA7SYIKeJWAcaFG2aEe+qEgik0aaoFe6W4l6oMjmlP6SJUiaYug2JSj
xYQqyqIZF5b8Vpqx1YskWnw0KpYn6qM/6oNfuZV2R6TvaHdFt45POZVopoM9iosVRhNKuFbSJlW7
OaFoOXsgiYasSZMJ6aAjGV4cl4YBmooAZ6D3qIWE6FpcGKZlOZd36XEuZXCEOZ9tKqBXp2ybSaek
5WofqIvcaZw7aHF7h4+2iZ2PeW4N1lx9//qM2GiHwnWKCimb4bl4GeaKQZepmAiJHIqGlNenuBlm
75mLHkiZ1+WJWXefwPeICQedvamZFhaRbAer4cmROqWqoaqGoph0gnmZmJir0eiTo7iY6Eidb6eV
/DmoWoiZtwiL3wij0cmpKdh00zif0MqsnJmki7mcnAmFRUoS2SiaAsmHkimX6FmP8fh5yZWen/hk
ZZqeXlpyeYiukUdpkIePesiu53qezzasspqPa9qs+aaIVJqBPKeMHQmSWkp4BiuNAgp7JgmGHOea
JqaBkNqgnreQzMaIk0VpXHp6pBeg5jqspieIBYuxBYkTCtapbsKyJeGyJ7Gyt2eiwQSzUP/ZslMZ
ojq7szwrgJPqELwokfH2rUs6tFHaomN5tHX6ey+Ye8jyk2gHtCgIrkH6stK5E1HptJaGpW3ZsRhX
oAu7lEELsg5ZcZIleammhqP3sA1rmAlbo21pjHAbpuiol3m5l3VZo2t4towmp1u6HZMIjLAaiVrJ
Z0iHl4E7hUe2i8Jpra+HqeVajnuKnGo3c5T6dNg6uPdqeJYWtbG6dCgnnUDJi7WquKF6Y4wYmFRX
mqirdV2mqON6a+GauubZaqd7sOlWqoaHm3kKuJ5blcgqaD9LuI6rlDaYWu9ZrLqJqBZ5rKjpsCHp
dtvYmckru4fLeVAaG4lbvLVblYW4nuf/ya+h6Z2stb1laqchuKDvunPL6p6Kd6UbKa/fW67Uy76A
y7UDSrehF18Sur/+aagOmnOHJ6kNiqAfG77JtbR4eb60ybafRqhKVoKI67/4y5AhVoY22ywZHJxY
tsH2qaM9G8IiPMIkrLIzOoFvCsJYabQ6Cm9Iq7T6WLgvPJPcamc32ostrMIznGU7fJpPCo4UOKgu
3MNCarTaWLU0XMNDGsPY+4S9drL32rfY2bV7C7mEBoJr+7btK6ozlnre6pCgF7auS5cLW7d9lrfv
u5dm65ZLK49BebeBSppueLRRHKnieFmLm52zKZVsubixe63DKXpkmcehqa5iWrnyasVH/3zHgLqv
arqqb7y5gvus/Qaa7tuK0San5jq8g8xjuTmBqEugCSxp9VqLYFdlQad0d5y+xNuUqIerkJnJwXik
EhpdaUuesvgR2wvBtCq/zlqWnSx1LTrEtGmvuCi9cpuMoaydmIvM/OnKmUvJlurGRgylhCywL6hV
DBm9Nce58Ym0u+nJ5QnE+3mDyuqtx3vE3wyQ72uqxQi+juzNPuyo6Ti70by+uux2dvzKj7qu4uqr
qViycviX/5a2y2nM0sjPZqu3rLeRDf3A7fyxyaywpPd4AJqgOca/NazKboqmVgvEwsqjIeHBwULS
44bCNXnSurxNJl3CLv3SML185VyfJv/80TRNpG98ojdNxDwqw0HKybryhxtqEj5dzRi6oz1R1DxN
tJDiZdLbhKvLj2BayrwqtJf3pWBbZK6rtmws0W17psLlt2v8tbsbp3RI0P46xna5XB3LprtyjrQ7
kCkphoYqwK2Jeo08v8kZuVeLvvJLkKL6zSu3znJ4t/N7sPVK17fSiHMnsN+laujW1sKbxZAcmaB6
n1VXeuObwFNXvRj4ubroqTPdzRPpxY09zbTC2JuNraFdrdxaje/8jacdrqiNy9XqvKYZ29mK0sJc
qMY5q89bK+L71OeK2ADLsPyqyJz7xa3ox7K9nsC9vsgbz82528Md3MoLv9GN2Vk223v/zMCKjcG5
5tphCLHNlrH4+d3iPXFza8DkzcZ0et5mTdHzvasfSXtRLc8pq8EgvdRndkwtPWrlPXxzPCwpmpg6
HNMKvuAMXoD1xtRIvKInV+BeqW83KcFGndIQTrVTO2E5DcMfHos0xnVAKYUZ3pUbfrMd7hNvS8Vj
PYRv6dFXicYm2daTCtVnTNUPV6XrTdHInKYQppdV2tFYipaxume0SKZrmaVP5uLn64QyscvSrJj2
6KoHGbKGLbbzCrEGZ9vwCnupa9zUKqiT29o7Z2SXi3OYvM2J2tcifc8uOrikuuWMHM31bKyV3XnG
bL5pTrxE1sfd2XZ4vXCqK2uOmOe6/wudlGWpB66n9Gq87ZnI4+y9qq2kiDiL7QnYeo2ofS7iyXiN
jbfC6LzC+H25ud3KNSHleW3RXi66C+euMiqt8Kuvdy3XWI7hzjnIsfvHhL3piPzXj13cuZzqFUzk
do3XPyXFpc2HYp3ca+3QPgbAryvHETzJgu610a7sAWzVESraGFunCv2fs9bjDDtvDT5RCX7u6r7u
7N7uEFi0YoreVQvUJAqzCVbkVv1RNjmCxCxW5+ypN3osZPWah33iwAziPGHlfbXvJnrh1uvDZ6xn
LavGWb3tHP2cbO3FO17FZW3xMi7k9c22YP231Nl200aRXQqnuauxpVjYp57tXXqUZv8u61xszQ1d
u5pL15rO61Pujf/4ohGczr6u8KL45ZAe2EieaTsNlr8a8d0akvGKuYkamycZ6Kud2YIJ8Cvmquxc
d/Yc6Y5tmZR5ykX920s/as+qsWkP9QGN85GOsA/P8/Ssrq1Osqls2g9J5+VMwGNvyy3s6gHetH9M
86f+zOac97593JY96bGMr3zdmwWvzDHH9Vee2H2fruwoyHR2mThc3xpPbQIt9ZvqwFpci9p+89uO
3PS4uqmWYwPehXBZxswe7uX+joYOto4/mk2b2ieMYByOTNYW+CqeoxSugvlc/O6e/Mq//GkGwnvP
/JE8zEm7/K1r4z+c/F5n+SnO7pH/NubX7+7Pf9rTr/yV7/jCn4Bpad49CP0syP5M6f7wH//yP//0
X//2f//4n//6v//83//+DxD/BA4kWNDgQYQJFS5k2NDhQ4gRJU6kWNHiRYwZNW7k2NHjR5AhRY4k
WdLkSZQpVa5k2dLlS5gxZc6kWdPmzZgodOq8iKKgT4s+gXYc+tOo0H9FORZVahCpU4dNMz4NShCo
1IM7eWZNihFrRKoCv8oc+7CsxLMVsUoN65HpwrZio35My1Dp1bkD2Wqs2/AuTr2Br27VqpdwUryF
xcZd3HVw4p2GHw/leRfpZceOIze2PNlwV8F45T6lTHgrYqGnF5eGfNg16tKgJa+e/516tlXcqEfL
frzbKmnXrG8rHi2c9srYvJVTRryb+WCuzanaTizYevPA0qtj9q36+XXv1Z3Llrv8evbMxUHbzjx9
/dvyf7G7lxz5u/vn8iuH9p2+/U/x/OtrKfS0ws+o8frbqzv74jNPwdwE/O+78up7kDwK22tqMugq
/MxC0Q480EPmyFsvtM1INC/AwjZEcT8IsfOvQs9kVKlEEzOkUUIcI+QuPRYvhI/H/2LcMcMhRczR
w9zWOtLB+4T0kUnRZoyQSPF0fHLKHgPcEkOWcERSyhFVy24/6EIks7EzlSwTPhiBZCpLzPQ7ry0K
YYRsvDyTpPLLIbEskDOopOOPyP8EB00TPZS6PCy+R4t878Tf5AQS0ioXrdRN5QzdtNM4NfuMuzmP
083GUw1Vk70fNb0tR/pSXO20zegjlC3g9jS1VhtL1NNMwPhiMli7iCVqogGNjU5ZZolL1ibimPXK
LFmlBctabLPVdltuu/X2W3DDFXdccss191x001V3XXbPLetZZeE1MSHGnpWXXoVcJPAsfdvF6V1z
5a2rXrSOxXckxq4c1t9pewOV1kdTDFWx+yR+7VRfgeUVYuFq5XjLjXHrrUGHMcbUKdMghjW1OmEb
9bhc+4M5PFI/ZtiuTNdMFDgu+Qsy0hHBVA/RSyGMcuhleV4zZ0XB87PDN5djulD/SpvMucebk6b4
PY/RbJHRMVf9GlA2AVR07AIb7Nnld32tz7PwslJbwkodNPrFsICdct5MW4w2a6pdrPJJ+YRG1MtO
6V64ajwR1PJoKxFS889EKSd6wavvXBLBpIedenHAORezaVWdXlvPu0G2VerUi46TZ9jzBY90NHds
80HvZk/99cSdtLtJ0ucNncTcX6091YlvJ+1kDFUueTgZLYY65lurz9e05mNbPtWXM16Z0Bh/Hbxa
ALGuGnm9h1f/4PVburd9+MOMv1Hy57f/fvzz139//vv3/38ABlCAAySgtgonvKkcBXTLMtb7/AKt
8qUPIguaWddeNcG3mcpywTpg/0goiMF4ITCBDnQL50SYl7oljnEq9Iu+xNRB91HPVZrRWMtMFpxZ
cQ1lukKflwxUQeNwDypz+ovN4pI3m/UQes5KGcuu5DD23FBWqwPeBn9TRKqdKXtAzKEG1QK+IuWu
S5y5mq5IpcL8tC6KjtPcmCTXu7rhZy+jC1sbl1fHKwJtPqwTHmv8ZEXbKcwy5/ld0KiIrDaiUZEy
Q5uSIvchqXUtYXTEW9k6Z8kjoW1vvfJjh8omtrk1jjeNlFLgBhVIEf5tcwrcHB5pKEGzJHKMYzSS
IS8FsAt9SXSJZGAEO/g4uVXLTr2cnCit5La1KW6T4zvlJZ/4xh9qUY0nLJinwv/4FlryTjt3C1Lw
ovZBVx5ySY5qHaMupzPXodN2aTynKX8HKtmhynCLlOY5zYcsGYJRmaXr3h6dQ70rrtN5fKOYHpWo
IqsV0Tj9Yt5BD1pMPRaPeVHkFSa3SKUmDs6aYCufCecT0TaR0KMEiuf/RNqtkwrrZqr0Sv1Gur+U
bium0ypgTW16U5zmVKc75WlPffpToPYUYDNVWC+vRc0McuWkCTNqVYrVVKQyVHpF9ZxQ4YLUL5aU
IhplXx9LiMIEPjWLVC0qrTQnT1TBkoCsso5Gp/rKoT1PN/mMFsmCiNCQZcyHHxUjbUKpoSSGinsW
tOD3BgtHkfENTBuy4cbeutL/nx3Tjid6Ddag5jO8dnNWvGsVHz/0Izbl6VB4lCicdDcjZO6SRoF6
pn7Yqh7N+quOeqPZ9kT0t6nZtoqvDJQjpzO3phXuh5nL5F/zuNvfJu+dzRTuG5ero7GFiKjNkiUC
iRvZr+SWUqaVWWvb2h1CEk619bSVMf9YyBX+kYKWNWfapnjWdLaXXRerXXM1ZcZ9andy6KUlN08p
2D2aV3faPBycuOu6vNVzmYgdaytjpdt7qouije2o9bYjXRcGdLufauhmlwg20Ma1VxrGXnl3hSck
zsx6xmPgYw3H0BXzE8NBfSnDpmvTG1tVfTkOIEtp/GMgB1nIQyZykY18ZCQn/xmAA4JhKrHaYGHx
GMrbc+py6eVjpsLFpVu9Kk21+uUQglC+vuMyXWiyVDY+cMxVTqmUF/hmaxX2ZSbb6Iv86jKYOU2h
w7EYYLVXYfQVGG5crPBUJ3xAKNItZMHNsxHZxlEhRto+x5t0yShdwxpFeiOphdSKLKroaaIWxNNc
VJ+SGbud3RK+8LSakWDDWXvat4xG2y82If3iSeHOdKsLJ0g4vbQ1I1OOEkOZKYdbXVc/+tS5VrWr
f13G9yI7uUesKJlI2V1PHjeF41PbsSu37Gh+9XzAXlisyinfVQoYcrwOryspG+p1pvmRi/1u0SLX
3HNT8pmbrKK+7WtdXork2f9grJlSpWlLUROP1CtWWqdNXep6IzzeyKWnoASq2AVfTJmCg3RpV+ip
h9NT4m4xq9kSDfLE2u3BnxNm9AxaX+WZ/MSToms+MWrZlfvywwo/ogkdC71PFop8gvVY80QVaIAC
XYc5iTPCynxTgXEwXD4GzHSpLlYcIxJaW1Zy173+dbCHXexjJ3vZzX4TrtYYyiNcXNqv7GayltvL
C3T7WAXG9WrqtO5w5ntWfdeXCJv5qFVWM+DRreYnIz6nXqtN+ioqyTkHkmWXIeLRhYir1vAQ8rgz
0+QxRt+PvbeujPdi7wyK65ov0bhrDW0ue0Za026n9bfbuLHvGNlaclS0Is7/9yI1znGQnY+dw+fj
5wTINE1G0J7mpDDLiytR2oXPuCgeop5fV1Dm+76SWYymDS0Ex/ysPsv9I+68113K72ap4+Ft7+5t
6bYPHm688na2LltcfWNK3vX6LuB1J8lwznMnezswKiItEXMV9lKR3VOcoKk/9Ns3Bsu+TIK3xMsf
bSK9QbI5mhNA6hg1vQomoLuwfkIlL5KjPDMe7Fm1C3Q8QGOhVZIipSu5voM6ksIWeIE7G3u6Cqwp
Ero6qRs8nrpBtTs7IixCIzxCJExCJVxCJkTCEMuqw5s3g9vBrnIuMNO6KjyY+IslKuS+GWwqHIyn
GwtD9lOpKxRDM8zCIRQz/yvssjZkQ8Ibt6lzOoPxNGyiE/9buu/Tv6/BND6rjEtzq5RpwRPUkMaD
okpbujtUPfHpIhILPZdTqOCYxD8bLUWMxOJoxNLbvDoLqztCLfzyL2uyNeCRPX8iG1PLpYFDKB7B
PQOErp9ZFRVUsFzjtU88v2zDoeLbxXZCxU9rGFV7mv96t0zsKwX6xIrTGf5jNW2DJDeSQVLCsAQL
tZFbxfArHlOUFHbLvWs0t+7DvJHbtDBKOAYELy1hv+ZDpX8DL11aRa96wFrTNegKONzDtVYqww1z
pNrjxnbTIjLzxS8UM8gJMObaNd1zJioTxt0JHmbsNNphK/crkw38rFKqRv9aLD/u6qyooUg6qkeP
bLVUFLeBfC0N8h65WiM+LEBHgy0SAzTGMqzSMSKIY0l+Qppq00Scw7mHGSaNfJjF4jbNAxqAGrrO
6kTkaEIoBBzWOsPhIUOvc8qcaDmwQkqqrEqrvEqszEqt3EquBJdw08EpA8LDGz83jDs1jEJ8ZKW8
aLKuxMI4fKlk2cKAhEPFWzuztEstVLKhdLSc28QmarGXG6jLO0FOBDC4mis8o7OfBEREFMwpGsSA
8rxGe7WSxMDSEyqM5MVefED9G8CJpLdUC8mUy8ezapwF/Kb1o5z3E5psykaolK2k4pjk4RCLciMf
cZbj0isDC6lwDB9aIzb/tcwVWHNIiitF3mTAulIdIIswt0q5f+RMFwS/WfRHepxC0uyuqlpAspHA
BFzN0YmOeaQx/mtA6WTFQ/pO20I1Y7ymAKw+lavIcTot1MQr7gxAKtO+VAuqyjux5kRBxjK+izJJ
8FGuxytK1ClN6XO+4QtMPQwtjZG+CSmoDNSztqxQC71QDM1QDd1QDu1QD/1QEA3Rk5ijLxyYucS6
N/RBtFxDEQ0Yt0TDOkzRuyzRFv2XwOrJz8PJljs9u7ogQqszOesjHCosyTw07KxRgeMlWDuaaoyt
y+qvjZy4FNrFWcMvdkLSEQUuZRQt24SnYeKtPLJIK3PQv6JNWSxGssTS/xpUN0JSvy6FP3n7v2Ub
RnxZR57cPzUdUYKbyOMZxzcF0Mz0JmZrSNA8uoTMx3rMU5LQRJCrmT05uZ8sq75sSYdzyR1aqI8i
zH9Sui5U1BhNidesQU9dl1ANVVEdVVRNVVVdVVZtVVd9VViNVVmdVVqtVVu9VVzNVV3dVV7tVV/9
VWANVmEdVmItVmM9VmRNVi3jFyxzQ37ZrWVVq7JMsGO7Q+BircmjVk3KVg9LTEby0eyTS61S0a8M
CrwjprpcVLRcSmraO9UEq3tZRGyLHoz7JVgpyDZ9QXn9OLP5xR08rzYUqcCbyjekQzvbt59rtM6D
TMRMoszC1Bk6IyxCHP85HDjtyle29FOcmbOEfSiE7byE8k8rdNQQlKFENAksIp5odEXVci1n87ZW
JE4/zSs0haS9qdbOrFnKRCuJLZaWIT53I8XsAalkm0ByG04pFLzprFndHDdr3D4FPM7vNMf4lJQp
HU07mVrPlBtWekL8s9qd5Nbe2ln0klmW2ppuNatudD2DdcB5XcibjVOAq06tvcWuvTe5684INLeu
stur+tldAqaDvKRsWjN+M863TVqldT66HdCWldv+KjCfvBPTjDxavLXVaiZQg0ABAVDShD1VJK+4
3Z34G09LcTeUhcYwjUEL2yHmm9RuRTqjE1rJslbl8rltBbFIAVNvJUf/4HxPSL2v3R09RONPjhUk
DaMznDwUZcUpU23eIIRe6Z1e6q1e671e7M1e7d1e7u1e7/1e8A1f8R1f8i1f8z1f9E1f9V1f9m1f
931f+I1f+Z1f+q1f+71f/M1f/d1f/u1f//1fAA5gAR5gAi5gAz5gBE5gBV5gBm5gB+5VdeCGgeAG
Cp5gdRAICpZgDM7gCv4HfIgHCo6HDZ5gDd5gDv6HDkZhCe5gfBiHEMaHgoiHCOYGEVbhExYIEKZh
GBaIDw7hERaIcVCHHR6IGa5hHH7hgkjhCmbhHK5hJV5hDobiDI6HISZhbthhCsZiKeYGIU7iEl5i
De5hGv5hFbbhDDZj/x0uOxCGYXzIYDYe4zb2YRIeiDYW4Ta+4Cc2iDwe4QoGYR7mYoKI4De+YDL+
h3GoYXXo4jr2YEDu4ESuYhS24zE2ZETu4jnmYwle5DsuY0z2YgsuiDi+4g0mZDA+4irO4wrW5Eb+
Yij2ZAwm5LFr4zfOYkZ+4zUmiBT2Y1fmZFxm5TkGY0gm4WDm5VvGYBHW5V7+h2IeiGU25Qk2Yl4u
ZWS+5DJOYTK2ZmWm4Ul242r+YmhGZQme5mtu5WQu5LDb5AgG4QsW5H8QZECmZhfWY1/eZXDO5ncu
iCKG5BSOYFweB0MuYRLOYUjmZ3wGaG7wZ2ou5XimZ3K+5EUO5Ct+Z/8KDuJupuZobuWFLueKLueH
JjsXjuNqRuiD/meNxmY0NuknjuIyxocZnmSIluNxTmaUDmGX/uEztmacjuJW7uCb1umTRmMqTuJ1
1uAsjuiGzmmVLmUbPuktBuMpHuavA2GpzuapXuRl3uOSBuiY7mQeLmKDYGkKhuV9Nmh/nmkYzmiB
IOgyVmsURuiYruCMVuqNnuNNJohNvuUKVgcXPmqD9mW49mvA9uS6LrtQnmVRzuEppmZxvmh5TuiG
/mOtpmOsvupjjmwWFmVmxuw+xmwUPuXAbuNfDmyOrulQpuVU7ukJ9uzQZuTV5mqHrumxO2MTduaO
TmFVxuN5zurVZuf/jm5nUR5saz5kGH5kRpZk3P5jWDZmRtZg4W5nS37rTB7jHGZsbB7rIebtVU5r
pW7merZquZZrMmbnsotgWJ7hreZlD1ZnJ85tx15tMR6HYM5hdfhmrW7iIe7h+SbjZvbtND7i/m5v
JkZicD5h23bpel5uM35u6OZh+6bupC7h3n5gCZ9wCq9wC79wDM9wDd9wDu9wD/9wEA+WEuAGMFgG
bVCBOCgHbyADGYiEJVgAWmiHaqgGMEgALaCHGGCCXdgEEJiAdfiFb9CEItiAZACBEbADDTACVkCB
LciFdtiGEIAAFniEe8AHPAiHTHCEQmCEMWCAW4ABBECFPpCCQ8gF/3AghS3gAC44BHmwBnd4hjDQ
BzcwBitwhg+YAydIgULgAAT4ADtIgBwABzpYhEDwBh3oAU9wgUpQBHCIgTp4A26YAyIQhDKYBjsg
YBrAhXIQgym4B0qAgmnIBgaYhmb4hGvIAmRQgiIAABxYAAlYBSLYhyGwAmZggCgwhVX4gUQghhzA
gFlgAwqAAnkIghBIhnUgg2Y4hhQggkzgAmDAhWoggRhYglWYAUewBjBggm+ogmuYgmGYhysogC04
g0Y4hzEYhGrgA1FQgFrYhUIYBlUAhgNYBhQQhml4AW4oglbQBRqIBAdggBAQAwdgBw4Ih0MAhzOY
BjzQh0og4Ag4Bf96YAIcWARAUIJQQINsMAVK4AVPwAJc0AZw4AdnqAY9mIZP+ARQWIAZkINdAAIi
eAM6EAJ5MIQHyIBcqIR9MIJPoIZTYAJZgINLeINYsANb4AUFmAd3SAIC0AJ78AUfKIE1oAAs+IUR
6AR4EAVfKAJo4IU+uIAywAAsGAA60AUl8AYEWAZ4UIVXsAcpwIByiIAAWIJoAAAx+IYXsIYkUAFH
8IFkCIZd0IAl8IE+IOA08IYgEAQ3cIZa0IQHwIMqGIE94AI3IIYHoANz+II9KIY+AAIQmIEp2IRe
yIRVqIElyAB3CIMSiIV5cAE2eIA++AZVOIUC2IRaEABdMINTPwb/KFgBMaAGdlACNXgGAjgBUmCH
RcCBYFCHabgGYMiEADgHBMiEXtAFWiADF5ABF3CEEjiBf2ACTEiAcqCBKTgGExgCdXiHEiABebCA
GXgFONCDU4gFSTCHGFiHTrAGAl6DLjgBbogFYgAIQ0JmhEEUDwm/MpEMpIgn74EyC6taVRMUQMSV
Tgpy5PIlIYQQTz32eGvgRpaHcWgW/dExo987bcKENKonzUWsChWAsZAC6V40ZEHM0UBiYEEsJ7q6
wZoRihQKUgYaiZkiwh8AdkBO9FjyQZsddpg4qRsFiJ+vRtBGEDEyoNW/uHLn0q1r9y7evHr38u3r
9y/gwIIHEy5s/xgvHy7Abm0jkCsHEwbTLtWJcEjODnmIiCEiZIrFEkTyDAXTNuIXvXU4zgWC8wVR
Jy4WbmhhAAnNCWFaDlmq4oPImBNocFo5NsjSDVtGtAHgNokfMSgw7JQKQEZIESsMOvWJsG6BlDxC
NpHABYpNCkH84Gi4FwAOi2Wpoggh1aBSmGF8Shzu7/8/gAEKOCCBBZJxjjJNxOOGOgis4ssvfqQy
DgzLoJDHHgLw0cwycTTxAwMn/LOOP7TIgQgiMLDzCBR/TAEKItKAMsICcUCyAiq5cPJJL2CwsAkC
ASBAwS7UPLCLM7ysQEImnaEgihz0IEILO7xIE0MndSSCiilJAP+iSgpiHKINA6MkQYQ+ltQBzyqm
cGCLGY9sMQUxEuTQiy3tFLgnn336+SegBUpDSzIK2KJJKvcwQgg5luwTSTwWKLNHHCEUsQYtV4wj
wR/8nFBPA+0Qg8AU2RDwRyKtqBFOOVBc4oUqkaghRhherKGGGTaoccEp4IwBSCpelNIMMx3MIMAz
bqyBgSU6lCPFCvB44gwBw1ixBSET2KDIMCjYgoAkJviigi49LKBMISFUIwUgurxigR8cuHIOOLk0
Eyi++eq7L78CkkNBNZBQwsUO6MgQzQtXIHHKKFQAIosr8diSQg67RLEKP+JQ80cqmsACghnAdJFP
IMGg0sYXuDz9oYEt1izzBT8HtLEBCNKwgssdgfiSRj6DlPFKKw4wIIIYCUjgBigomMGJN1lQMUk9
X3jiTTW8PPPKHdUwQ8IEUbCijCTCJAOGEYdc0E028dRCyyCkCGMFIEDI0S/dddt9N7/4CBNEGJeM
Q8IJOnTBDAt49DOCLzlUQgAYwciTRRnqNACIL7AUQk8E8zSRwgJ5iHKLPTMEsYsjwVijBwQ33IJE
JSJIk4onxpRTCzyqtBOMKFeAswMdXHhijRiVlHBOHq0U8IA64lSwQRcIjIHCIdHEscA/S3gCTxOq
iAMEEUj4kswk6syRgSVFzKGCHMFUUAQYfOD9Pvzxyz9YQAA7

------=_NextPart_000_0009_AA4C18C6.156A7092--




From mpls-bounces@lists.ietf.org Wed Sep 27 11:35:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSbNF-0000Us-61; Wed, 27 Sep 2006 11:31:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSbND-0000UH-1G
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 11:30:59 -0400
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSbEF-00080J-PM
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 11:21:50 -0400
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 27 Sep 2006 17:21:30 +0200
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 27 Sep 2006 17:21:30 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Priority: normal
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Sep 2006 17:21:29 +0200
Message-ID: <9E577E61D0108D4F8CD482029B613F5CBF3FAD@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question regarding LDP session setup
thread-index: AcbiSJsgUwqsBJ/vTJ6ScGdaz27uWA==
From: "Tempia Bonda Alberto" <alberto.tempiabonda@telecomitalia.it>
To: <mpls@lists.ietf.org>
X-OriginalArrivalTime: 27 Sep 2006 15:21:30.0146 (UTC)
	FILETIME=[9B86C020:01C6E248]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Fantolino Luca <luca.fantolino@telecomitalia.it>
Subject: [mpls] Question regarding LDP session setup
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hello,

I have a question about LDP session establishment between two LSRs
connected by multiple links.
A problem has occurred in the network during LDP session set up between
two routers linked by two Ethernet LANs. Below I describe the behavior.

 1. Router A sends a LDP HELLO message on each Ethernet link at the same
time; the two messages are identical, including the router ID and the
source IP address (IP address assigned to an internal interface).

 2. Router B tries to open two TCP connections with router A on port
646: it sends two TCP SYN packets (using two different local ports).

 3. Router A accepts both connections (TCP SYN ACK) and router B
completes the TCP connections set up (TCP ACK): two TCP connections are
now available for LDP message exchange.

 4. Router B (active role) sends two copies of the same LDP
INITIALIZATION message to router A through the two TCP connections.

 5. Router A sends a LDP INITIALIZATION message on the first TCP
connection and clears the second TCP connection (TCP FIN).

 6. Router A sends a LDP NOTIFICATION message with E-bit set and then
resets the second TCP connection.

What happens is that two TCP connections are created and Router B tries
to open two separate LDP sessions. It tries to open a second LDP session
when the first one is not yet established with the result that router A
closes both TCP connections and no LDP session is set up.

It is not clear to me whether this behavior is correct according to RFC
3036. In particular, is it correct that two TCP sessions are created and
a router tries to open two LDP sessions (it sends two LDP INITIALIZATION
messages) with the same peer?

Thanks,
Alberto and Luca
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From mpls-bounces@lists.ietf.org Wed Sep 27 12:46:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GScUi-0002T0-WC; Wed, 27 Sep 2006 12:42:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GScUh-0002Su-Nl
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 12:42:47 -0400
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GScUg-00033d-A0
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 12:42:47 -0400
Received: from tiruveedhulapc (tiruveedhula-pc.avici.com [10.2.20.229])
	by mailhost.avici.com (8.12.8/8.12.8) with SMTP id k8RGgHE5013488;
	Wed, 27 Sep 2006 12:42:35 -0400
From: "Kishore Tiruveedhula" <tiruveedhula@avici.com>
To: "Tempia Bonda Alberto" <alberto.tempiabonda@telecomitalia.it>,
	<mpls@lists.ietf.org>
Subject: RE: [mpls] Question regarding LDP session setup
Date: Wed, 27 Sep 2006 12:42:16 -0400
Message-ID: <BOEJJJAOLEDABPBFHOJAEEOMCAAA.tiruveedhula@avici.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Importance: Normal
In-Reply-To: <9E577E61D0108D4F8CD482029B613F5CBF3FAD@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Fantolino Luca <luca.fantolino@telecomitalia.it>
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

If the both links uses the same local LDP ID (LSR Id:label space id), then
it should create single LDP session (single TCP connection).

I guess your case might be something like below:

If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is Ra:La2
and
Router B (assuming Active) LDP ID on both links is same Rb:Lb.


Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is Rb:Lb)
Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is Rb:Lb)


In this case, Router B opens two TCP connections and Router B accepts both
connections,
but it may be accepted the TCP connections
      link1 of Router A to link2 of Router B  and
      link2 of Router A to link1 of Router B.

In this case, the session initialization fails when it verifies the
Initialization message with its Hello adjacency ( by using Receiver LDP
Identifier in CommonSession Parameter TLV).


Thanks,
Kishore

-----Original Message-----
From: Tempia Bonda Alberto [mailto:alberto.tempiabonda@telecomitalia.it]
Sent: Wednesday, September 27, 2006 11:21 AM
To: mpls@lists.ietf.org
Cc: Fantolino Luca
Subject: [mpls] Question regarding LDP session setup


Hello,

I have a question about LDP session establishment between two LSRs
connected by multiple links.
A problem has occurred in the network during LDP session set up between
two routers linked by two Ethernet LANs. Below I describe the behavior.

 1. Router A sends a LDP HELLO message on each Ethernet link at the same
time; the two messages are identical, including the router ID and the
source IP address (IP address assigned to an internal interface).

 2. Router B tries to open two TCP connections with router A on port
646: it sends two TCP SYN packets (using two different local ports).

 3. Router A accepts both connections (TCP SYN ACK) and router B
completes the TCP connections set up (TCP ACK): two TCP connections are
now available for LDP message exchange.

 4. Router B (active role) sends two copies of the same LDP
INITIALIZATION message to router A through the two TCP connections.

 5. Router A sends a LDP INITIALIZATION message on the first TCP
connection and clears the second TCP connection (TCP FIN).

 6. Router A sends a LDP NOTIFICATION message with E-bit set and then
resets the second TCP connection.

What happens is that two TCP connections are created and Router B tries
to open two separate LDP sessions. It tries to open a second LDP session
when the first one is not yet established with the result that router A
closes both TCP connections and no LDP session is set up.

It is not clear to me whether this behavior is correct according to RFC
3036. In particular, is it correct that two TCP sessions are created and
a router tries to open two LDP sessions (it sends two LDP INITIALIZATION
messages) with the same peer?

Thanks,
Alberto and Luca
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons above
and may contain confidential information. If you have received the message
in error, be informed that any use of the content hereof is prohibited.
Please return it immediately to the sender and delete the message. Should
you have any questions, please contact us by replying to
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------


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



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



From mpls-bounces@lists.ietf.org Wed Sep 27 13:09:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GScrx-0001kr-J1; Wed, 27 Sep 2006 13:06:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSbSY-0004u9-9m
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 11:36:30 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSbSY-0002KZ-85
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 11:36:30 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GSbSV-0004Gw-IS
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 11:36:30 -0400
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42])
	by ns4.neustar.com (Postfix) with ESMTP id 597DE2AC73;
	Wed, 27 Sep 2006 15:35:57 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43)
	id 1GSbS1-00082H-4I; Wed, 27 Sep 2006 11:35:57 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: loa@pi.se, sob@harvard.edu, stbryant@cisco.com,
	adrian@olddog.co.uk, danny@arbor.net, swallow@cisco.com
From: Greg Jones (ITU-T SG 15) <tsbsg15@itu.int>
Message-Id: <E1GSbS1-00082H-4I@ietf.org>
Date: Wed, 27 Sep 2006 11:35:57 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-Mailman-Approved-At: Wed, 27 Sep 2006 13:06:46 -0400
Cc: mpls@lists.ietf.org, greg.jones@itu.int, iab@ietf.org, maeda@ansl.ntt.co.jp,
	ghani.abbas@marconi.com, ccamp@ops.ietf.org, pwe3@ietf.org,
	iesg@ietf.org, tsbsg15@itu.int, houlin.zhao@itu.int, betts01@nortel.com
Subject: [mpls] New Liaison Statement, "Response to liaisons on G.8110.1" 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tsbsg15@itu.int, greg.jones@itu.int
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org


Title: Response to liaisons on G.8110.1
Submission Date: 2006-09-27
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=265 
Please reply by 2006-10-30

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF(loa@pi.se, sob@harvard.edu, stbryant@cisco.com, adrian@olddog.co.uk, danny@arbor.net, swallow@cisco.com)
Cc: iesg@ietf.org
iab@ietf.org
sjtrowbridge@lucent.com
betts01@nortel.com
maeda@ansl.ntt.co.jp
ghani.abbas@marconi.com
houlin.zhao@itu.int
ccamp@ops.ietf.org
mpls@lists.ietf.org
pwe3@ietf.org
Reponse Contact: tsbsg15@itu.int
greg.jones@itu.int
Technical Contact: betts01@nortel.com
Purpose: For comment 
Body: 
Attachment(s):
     Response to liaisons on G.8110.1 - body text (https://datatracker.ietf.org/documents/LIAISON/file367.doc)




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



From mpls-bounces@lists.ietf.org Wed Sep 27 16:17:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSfmN-0006In-8W; Wed, 27 Sep 2006 16:13:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSfmK-0006Gm-1X
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 16:13:12 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSfmJ-0002Z2-1n
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 16:13:11 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GSfmG-0000JH-GO
	for mpls@lists.ietf.org; Wed, 27 Sep 2006 16:13:10 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 20283175CB;
	Wed, 27 Sep 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GSfPt-00038V-Kj; Wed, 27 Sep 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GSfPt-00038V-Kj@stiedprstage1.ietf.org>
Date: Wed, 27 Sep 2006 15:50:01 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-02.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

	Title		: MPLS Multicast Encapsulations
	Author(s)	: T. Eckert, et al.
	Filename	: draft-ietf-mpls-multicast-encaps-02.txt
	Pages		: 9
	Date		: 2006-9-27
	
RFC 3032 established two data link layer codepoints for MPLS: one to
indicate that the data link layer frame is carrying an MPLS unicast
packet, and the other to indicate that the data link layer frame is
carrying an MPLS multicast packet.  This specification updates
RFC3032 by redefining the meaning of these two codepoints.  The
former "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".  The former "unicast codepoint" is to
be used in all other cases.  Whether the data link layer payload is a
unicast MPLS packet or a multicast MPLS packet is now to be
determined by looking up the top label, rather than by the codepoint.

RFC3032 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-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mpls-multicast-encaps-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-multicast-encaps-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-multicast-encaps-02.txt

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

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


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Thu Sep 28 07:35:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSu51-0008GK-R4; Thu, 28 Sep 2006 07:29:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSu4z-0008G9-Ud
	for mpls@ietf.org; Thu, 28 Sep 2006 07:29:25 -0400
Received: from gw.imc.kth.se ([193.10.152.67] helo=oberon.imc.kth.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSu4y-000579-Fg
	for mpls@ietf.org; Thu, 28 Sep 2006 07:29:25 -0400
Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140])
	by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id k8SBRF7f005443
	for <mpls@ietf.org>; Thu, 28 Sep 2006 13:27:16 +0200
Received: from [127.0.0.1] ([172.16.2.31])
	by mail1.imc.kth.se with ESMTP; Thu, 28 Sep 2006 13:28:42 +0200
Message-ID: <451BB1E2.10007@pi.se>
Date: Thu, 28 Sep 2006 13:28:34 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: mpls@ietf.org
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: 
Subject: [mpls] new liaison statement from SG
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Working group,

we have received a new liaison statement from SG 15 of ITU-T.

It is a response to our request on requirements for T-MPLS.

Please find it in the liaison tracker:

https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=265

The liaison is for comments and addressed to IETF and the pwe3,
ccamp and mpls working groups. Working group chairs will compile
the response and comments in the liaison are welcome on this list.

Loa and George

-- 
Loa Andersson

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

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



From mpls-bounces@lists.ietf.org Thu Sep 28 11:55:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSy9K-0007MG-FU; Thu, 28 Sep 2006 11:50:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSy9J-0007MB-0m
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 11:50:09 -0400
Received: from [208.246.215.5] (helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSy9E-0006Hl-SS
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 11:50:08 -0400
Received: from tiruveedhulapc (tiruveedhula-pc.avici.com [10.2.20.229])
	by mailhost.avici.com (8.12.8/8.12.8) with SMTP id k8SFnME5028236;
	Thu, 28 Sep 2006 11:49:48 -0400
From: "Kishore Tiruveedhula" <tiruveedhula@avici.com>
To: "Fantolino Luca" <luca.fantolino@telecomitalia.it>
Subject: RE: [mpls] Question regarding LDP session setup
Date: Thu, 28 Sep 2006 11:49:22 -0400
Message-ID: <BOEJJJAOLEDABPBFHOJAGEOOCAAA.tiruveedhula@avici.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C57874567@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.avici.com id
	k8SFnME5028236
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Luca,
   Yes. I expect single TCP connection.

Thanks,
Kishore

-----Original Message-----
From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]
Sent: Thursday, September 28, 2006 10:18 AM
To: Kishore Tiruveedhula
Cc: mpls@lists.ietf.org; Tempia Bonda Alberto
Subject: RE: [mpls] Question regarding LDP session setup


Thanks for your reply.

I verified again the content of the LDP messages: both report the same LD=
P
ID (the loopback address) and same Label Space ID (0).

In this case I understand you expect a single TCP connection be created.

bye
Luca

-----Original Message-----
From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]
Sent: mercoled=EC 27 settembre 2006 18:42
To: Tempia Bonda Alberto; mpls@lists.ietf.org
Cc: Fantolino Luca
Subject: RE: [mpls] Question regarding LDP session setup

If the both links uses the same local LDP ID (LSR Id:label space id), the=
n
it should create single LDP session (single TCP connection).

I guess your case might be something like below:

If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is Ra:=
La2
and
Router B (assuming Active) LDP ID on both links is same Rb:Lb.


Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is Rb:Lb)
Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is Rb:Lb)


In this case, Router B opens two TCP connections and Router B accepts bot=
h
connections,
but it may be accepted the TCP connections
      link1 of Router A to link2 of Router B  and
      link2 of Router A to link1 of Router B.

In this case, the session initialization fails when it verifies the
Initialization message with its Hello adjacency ( by using Receiver LDP
Identifier in CommonSession Parameter TLV).


Thanks,
Kishore

-----Original Message-----
From: Tempia Bonda Alberto [mailto:alberto.tempiabonda@telecomitalia.it]
Sent: Wednesday, September 27, 2006 11:21 AM
To: mpls@lists.ietf.org
Cc: Fantolino Luca
Subject: [mpls] Question regarding LDP session setup


Hello,

I have a question about LDP session establishment between two LSRs
connected by multiple links.
A problem has occurred in the network during LDP session set up between
two routers linked by two Ethernet LANs. Below I describe the behavior.

 1. Router A sends a LDP HELLO message on each Ethernet link at the same
time; the two messages are identical, including the router ID and the
source IP address (IP address assigned to an internal interface).

 2. Router B tries to open two TCP connections with router A on port
646: it sends two TCP SYN packets (using two different local ports).

 3. Router A accepts both connections (TCP SYN ACK) and router B
completes the TCP connections set up (TCP ACK): two TCP connections are
now available for LDP message exchange.

 4. Router B (active role) sends two copies of the same LDP
INITIALIZATION message to router A through the two TCP connections.

 5. Router A sends a LDP INITIALIZATION message on the first TCP
connection and clears the second TCP connection (TCP FIN).

 6. Router A sends a LDP NOTIFICATION message with E-bit set and then
resets the second TCP connection.

What happens is that two TCP connections are created and Router B tries
to open two separate LDP sessions. It tries to open a second LDP session
when the first one is not yet established with the result that router A
closes both TCP connections and no LDP session is set up.

It is not clear to me whether this behavior is correct according to RFC
3036. In particular, is it correct that two TCP sessions are created and
a router tries to open two LDP sessions (it sends two LDP INITIALIZATION
messages) with the same peer?

Thanks,
Alberto and Luca
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons abov=
e
and may contain confidential information. If you have received the messag=
e
in error, be informed that any use of the content hereof is prohibited.
Please return it immediately to the sender and delete the message. Should
you have any questions, please contact us by replying to
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------


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


--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons abov=
e
and may contain confidential information. If you have received the messag=
e
in error, be informed that any use of the content hereof is prohibited.
Please return it immediately to the sender and delete the message. Should
you have any questions, please contact us by replying to
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------




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



From mpls-bounces@lists.ietf.org Thu Sep 28 14:37:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GT0hA-0000kD-HS; Thu, 28 Sep 2006 14:33:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSwiC-00069p-L6
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 10:18:04 -0400
Received: from maile.telecomitalia.it ([156.54.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSwi6-0005Oo-5K
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 10:18:04 -0400
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by
	maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Thu, 28 Sep 2006 16:17:48 +0200
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 28 Sep 2006 16:17:47 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Priority: normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] Question regarding LDP session setup
Date: Thu, 28 Sep 2006 16:17:46 +0200
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C57874567@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <BOEJJJAOLEDABPBFHOJAEEOMCAAA.tiruveedhula@avici.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Question regarding LDP session setup
thread-index: AcbiU/pOU406xnf/Te6gOKInp0itvQAtDZqg
From: "Fantolino Luca" <luca.fantolino@telecomitalia.it>
To: "Kishore Tiruveedhula" <tiruveedhula@avici.com>
X-OriginalArrivalTime: 28 Sep 2006 14:17:47.0751 (UTC)
	FILETIME=[DF9D4F70:01C6E308]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
X-Mailman-Approved-At: Thu, 28 Sep 2006 14:33:14 -0400
Cc: mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Thanks for your reply.

I verified again the content of the LDP messages: both report the same =
LDP ID (the loopback address) and same Label Space ID (0).

In this case I understand you expect a single TCP connection be created.

bye
Luca

-----Original Message-----
From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=20
Sent: mercoled=EC 27 settembre 2006 18:42
To: Tempia Bonda Alberto; mpls@lists.ietf.org
Cc: Fantolino Luca
Subject: RE: [mpls] Question regarding LDP session setup

If the both links uses the same local LDP ID (LSR Id:label space id), =
then
it should create single LDP session (single TCP connection).

I guess your case might be something like below:

If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is =
Ra:La2
and
Router B (assuming Active) LDP ID on both links is same Rb:Lb.


Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is Rb:Lb)
Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is Rb:Lb)


In this case, Router B opens two TCP connections and Router B accepts =
both
connections,
but it may be accepted the TCP connections
      link1 of Router A to link2 of Router B  and
      link2 of Router A to link1 of Router B.

In this case, the session initialization fails when it verifies the
Initialization message with its Hello adjacency ( by using Receiver LDP
Identifier in CommonSession Parameter TLV).


Thanks,
Kishore

-----Original Message-----
From: Tempia Bonda Alberto [mailto:alberto.tempiabonda@telecomitalia.it]
Sent: Wednesday, September 27, 2006 11:21 AM
To: mpls@lists.ietf.org
Cc: Fantolino Luca
Subject: [mpls] Question regarding LDP session setup


Hello,

I have a question about LDP session establishment between two LSRs
connected by multiple links.
A problem has occurred in the network during LDP session set up between
two routers linked by two Ethernet LANs. Below I describe the behavior.

 1. Router A sends a LDP HELLO message on each Ethernet link at the same
time; the two messages are identical, including the router ID and the
source IP address (IP address assigned to an internal interface).

 2. Router B tries to open two TCP connections with router A on port
646: it sends two TCP SYN packets (using two different local ports).

 3. Router A accepts both connections (TCP SYN ACK) and router B
completes the TCP connections set up (TCP ACK): two TCP connections are
now available for LDP message exchange.

 4. Router B (active role) sends two copies of the same LDP
INITIALIZATION message to router A through the two TCP connections.

 5. Router A sends a LDP INITIALIZATION message on the first TCP
connection and clears the second TCP connection (TCP FIN).

 6. Router A sends a LDP NOTIFICATION message with E-bit set and then
resets the second TCP connection.

What happens is that two TCP connections are created and Router B tries
to open two separate LDP sessions. It tries to open a second LDP session
when the first one is not yet established with the result that router A
closes both TCP connections and no LDP session is set up.

It is not clear to me whether this behavior is correct according to RFC
3036. In particular, is it correct that two TCP sessions are created and
a router tries to open two LDP sessions (it sends two LDP INITIALIZATION
messages) with the same peer?

Thanks,
Alberto and Luca
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above
and may contain confidential information. If you have received the =
message
in error, be informed that any use of the content hereof is prohibited.
Please return it immediately to the sender and delete the message. =
Should
you have any questions, please contact us by replying to
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------


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


--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From mpls-bounces@lists.ietf.org Thu Sep 28 15:55:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GT1uA-0006cO-1b; Thu, 28 Sep 2006 15:50:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GT1u0-0006V9-Rr
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 15:50:36 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GT1u0-0003sN-Lr
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 15:50:36 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GT1tx-0002VW-3K
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 15:50:36 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id ACDC6175BE;
	Thu, 28 Sep 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GT1tS-000086-8t; Thu, 28 Sep 2006 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GT1tS-000086-8t@stiedprstage1.ietf.org>
Date: Thu, 28 Sep 2006 15:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: mpls@lists.ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-icmp-06.txt 
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

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

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mpls-icmp-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-icmp-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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


--OtherAccess--

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

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

--NextPart--




From mpls-bounces@lists.ietf.org Thu Sep 28 18:44:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GT4Xz-0005yy-Ui; Thu, 28 Sep 2006 18:40:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GT4Xy-0005ys-37
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 18:40:02 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GT4Xw-00069e-LL
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 18:40:02 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 28 Sep 2006 18:40:01 -0400
X-IronPort-AV: i="4.09,231,1157342400"; 
	d="scan'208"; a="104930485:sNHT58286220"
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.20060308/8.12.11) with ESMTP id
	k8SMe0ZF017189; Thu, 28 Sep 2006 18:40:00 -0400
Received: from cisco.com (rhthomas-u10.cisco.com [161.44.71.42])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k8SMdvuI024737; 
	Thu, 28 Sep 2006 18:39:59 -0400 (EDT)
Message-Id: <200609282239.k8SMdvuI024737@rtp-core-2.cisco.com>
To: "Kishore Tiruveedhula" <tiruveedhula@avici.com>
Subject: Re: [mpls] Question regarding LDP session setup 
In-Reply-To: Message from "Fantolino Luca" <luca.fantolino@telecomitalia.it> 
	of "Thu, 28 Sep 2006 16:17:46 +0200."
	<E9D1028EC5C22B418B5D54CA6EA27C57874567@PTPEVS108BA020.idc.cww.telecomitalia.it>
Date: Thu, 28 Sep 2006 18:39:57 -0400
From: Bob Thomas <rhthomas@cisco.com>
DKIM-Signature: a=rsa-sha1; q=dns; l=6244; t=1159483200; x=1160347200;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rhthomas@cisco.com;
	z=From:Bob=20Thomas=20<rhthomas@cisco.com>
	|Subject:Re=3A=20[mpls]=20Question=20regarding=20LDP=20session=20setup=20
	|To:=22Kishore=20Tiruveedhula=22=20<tiruveedhula@avici.com>;
	X=v=3Dcisco.com=3B=20h=3DameA71Tycs4MEmKlmhlSM5gVTKM=3D;
	b=rrzXZerHrVMDhZ5qhXw6TIMNS+yQQ9v63AZuUTzZF1/cI4Wb3Vyox0ouBzPzP6LaSbYwihae
	Ne7qh6QlCGyuZY3ZhfOaC4/rzD+6W7mdY4FzqnrhUOOYltO2EIJCVuIp;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=rhthomas@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Cc: Fantolino Luca <luca.fantolino@telecomitalia.it>, mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Kishore,

> Subject: RE: [mpls] Question regarding LDP session setup
> Date: Thu, 28 Sep 2006 11:49:22 -0400 
> Cc: mpls@lists.ietf.org 
> 
> Luca,
>    Yes. I expect single TCP connection.

RFC3036 is silent on this point.

RFC3036 specifies a single session between the 2 routers in this
situation but places no limit on the number of connections the active
router may attempt to open in order to establish the single session.

This leaves the router playing the passive role with the job of
selecting one connection for the session and closing the other(s).

Bob


> Thanks,
> Kishore
> 
> 
> -----Original Message-----
> From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]
> Sent: Thursday, September 28, 2006 10:18 AM
> To: Kishore Tiruveedhula
> Cc: mpls@lists.ietf.org; Tempia Bonda Alberto
> Subject: RE: [mpls] Question regarding LDP session setup
> 
> 
> Thanks for your reply.
> 
> I verified again the content of the LDP messages: both report the same =
> LDP ID (the loopback address) and same Label Space ID (0).
> 
> In this case I understand you expect a single TCP connection be created.
> 
> bye
> Luca
> 
> -----Original Message-----
> From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=20
> Sent: mercoled=EC 27 settembre 2006 18:42
> To: Tempia Bonda Alberto; mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: RE: [mpls] Question regarding LDP session setup
> 
> If the both links uses the same local LDP ID (LSR Id:label space id), =
> then
> it should create single LDP session (single TCP connection).
> 
> I guess your case might be something like below:
> 
> If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is =
> Ra:La2
> and
> Router B (assuming Active) LDP ID on both links is same Rb:Lb.
> 
> 
> Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is Rb:Lb)
> Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is Rb:Lb)
> 
> 
> In this case, Router B opens two TCP connections and Router B accepts =
> both
> connections,
> but it may be accepted the TCP connections
>       link1 of Router A to link2 of Router B  and
>       link2 of Router A to link1 of Router B.
> 
> In this case, the session initialization fails when it verifies the
> Initialization message with its Hello adjacency ( by using Receiver LDP
> Identifier in CommonSession Parameter TLV).
> 
> 
> Thanks,
> Kishore
> 
> -----Original Message-----
> From: Tempia Bonda Alberto [mailto:alberto.tempiabonda@telecomitalia.it]
> Sent: Wednesday, September 27, 2006 11:21 AM
> To: mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: [mpls] Question regarding LDP session setup
> 
> 
> Hello,
> 
> I have a question about LDP session establishment between two LSRs
> connected by multiple links.
> A problem has occurred in the network during LDP session set up between
> two routers linked by two Ethernet LANs. Below I describe the behavior.
> 
>  1. Router A sends a LDP HELLO message on each Ethernet link at the same
> time; the two messages are identical, including the router ID and the
> source IP address (IP address assigned to an internal interface).
> 
>  2. Router B tries to open two TCP connections with router A on port
> 646: it sends two TCP SYN packets (using two different local ports).
> 
>  3. Router A accepts both connections (TCP SYN ACK) and router B
> completes the TCP connections set up (TCP ACK): two TCP connections are
> now available for LDP message exchange.
> 
>  4. Router B (active role) sends two copies of the same LDP
> INITIALIZATION message to router A through the two TCP connections.
> 
>  5. Router A sends a LDP INITIALIZATION message on the first TCP
> connection and clears the second TCP connection (TCP FIN).
> 
>  6. Router A sends a LDP NOTIFICATION message with E-bit set and then
> resets the second TCP connection.
> 
> What happens is that two TCP connections are created and Router B tries
> to open two separate LDP sessions. It tries to open a second LDP session
> when the first one is not yet established with the result that router A
> closes both TCP connections and no LDP session is set up.
> 
> It is not clear to me whether this behavior is correct according to RFC
> 3036. In particular, is it correct that two TCP sessions are created and
> a router tries to open two LDP sessions (it sends two LDP INITIALIZATION
> messages) with the same peer?
> 
> Thanks,
> Alberto and Luca
> --------------------------------------------------------------------
> 
> CONFIDENTIALITY NOTICE
> 
> This message and its attachments are addressed solely to the persons =
> above
> and may contain confidential information. If you have received the =
> message
> in error, be informed that any use of the content hereof is prohibited.
> Please return it immediately to the sender and delete the message. =
> Should
> you have any questions, please contact us by replying to
> webmaster@telecomitalia.it.
> 
>         Thank you
> 
>                                         www.telecomitalia.it
> 
> --------------------------------------------------------------------
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
> 
> 
> --------------------------------------------------------------------
> 
> CONFIDENTIALITY NOTICE
> 
> This message and its attachments are addressed solely to the persons =
> above and may contain confidential information. If you have received the =
> message in error, be informed that any use of the content hereof is =
> prohibited. Please return it immediately to the sender and delete the =
> message. Should you have any questions, please contact us by replying to =
> webmaster@telecomitalia.it.
> 
>         Thank you
> 
>                                         www.telecomitalia.it
> 
> --------------------------------------------------------------------
>                        =20
> 
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
> 

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



From mpls-bounces@lists.ietf.org Thu Sep 28 23:32:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GT91j-0000Gc-37; Thu, 28 Sep 2006 23:27:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GT91i-0000GW-8v
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 23:27:02 -0400
Received: from [63.113.148.10] (helo=riverstonenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GT91f-0000QH-Ne
	for mpls@lists.ietf.org; Thu, 28 Sep 2006 23:27:02 -0400
Received: from gondor.rs.riverstonenet.com by riverstonenet.com
	(8.9.3+Sun/SMI-SVR4-Yago)
	id UAA21504; Thu, 28 Sep 2006 20:26:25 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] Question regarding LDP session setup 
Date: Fri, 29 Sep 2006 08:56:23 +0530
Message-ID: <FCAF0E8A270B6E4781D91431E853F6F303582F71@GONDOR.rs.riverstonenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Question regarding LDP session setup 
Thread-Index: AcbjT4a7QhVoQAL4Tz2/zt+zCqZihwAJs8yA
From: "Dutta, Pranjal" <pdutta@riverstonenet.com>
To: "Bob Thomas" <rhthomas@cisco.com>,
	"Kishore Tiruveedhula" <tiruveedhula@avici.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1924de3f9fb68e58c31920136007eb1
Cc: Fantolino Luca <luca.fantolino@telecomitalia.it>, mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Bob,
        It is well understood that the passive router has to close the
second or subsequent TCP connection requests for the same LDP session.
But=20
If the passive router advertises one LDPID (single label space) from it
then I don't see any reason for the active one to trigger up multiple
TCP connections.  The active router has to initiate only one TCP
connection for remote LDPID, although multiple hello adjacencies may
exist for the same LDPID.    =20

Thanks,
Pranjal

-----Original Message-----
From: Bob Thomas [mailto:rhthomas@cisco.com]=20
Sent: Friday, 29 September, 2006 4:10 AM
To: Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: Re: [mpls] Question regarding LDP session setup=20

Hi Kishore,

> Subject: RE: [mpls] Question regarding LDP session setup
> Date: Thu, 28 Sep 2006 11:49:22 -0400=20
> Cc: mpls@lists.ietf.org=20
>=20
> Luca,
>    Yes. I expect single TCP connection.

RFC3036 is silent on this point.

RFC3036 specifies a single session between the 2 routers in this
situation but places no limit on the number of connections the active
router may attempt to open in order to establish the single session.

This leaves the router playing the passive role with the job of
selecting one connection for the session and closing the other(s).

Bob


> Thanks,
> Kishore
>=20
>=20
> -----Original Message-----
> From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]
> Sent: Thursday, September 28, 2006 10:18 AM
> To: Kishore Tiruveedhula
> Cc: mpls@lists.ietf.org; Tempia Bonda Alberto
> Subject: RE: [mpls] Question regarding LDP session setup
>=20
>=20
> Thanks for your reply.
>=20
> I verified again the content of the LDP messages: both report the same
=3D
> LDP ID (the loopback address) and same Label Space ID (0).
>=20
> In this case I understand you expect a single TCP connection be
created.
>=20
> bye
> Luca
>=20
> -----Original Message-----
> From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=3D20
> Sent: mercoled=3DEC 27 settembre 2006 18:42
> To: Tempia Bonda Alberto; mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: RE: [mpls] Question regarding LDP session setup
>=20
> If the both links uses the same local LDP ID (LSR Id:label space id),
=3D
> then
> it should create single LDP session (single TCP connection).
>=20
> I guess your case might be something like below:
>=20
> If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is
=3D
> Ra:La2
> and
> Router B (assuming Active) LDP ID on both links is same Rb:Lb.
>=20
>=20
> Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is
Rb:Lb)
> Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is
Rb:Lb)
>=20
>=20
> In this case, Router B opens two TCP connections and Router B accepts
=3D
> both
> connections,
> but it may be accepted the TCP connections
>       link1 of Router A to link2 of Router B  and
>       link2 of Router A to link1 of Router B.
>=20
> In this case, the session initialization fails when it verifies the
> Initialization message with its Hello adjacency ( by using Receiver
LDP
> Identifier in CommonSession Parameter TLV).
>=20
>=20
> Thanks,
> Kishore
>=20
> -----Original Message-----
> From: Tempia Bonda Alberto
[mailto:alberto.tempiabonda@telecomitalia.it]
> Sent: Wednesday, September 27, 2006 11:21 AM
> To: mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: [mpls] Question regarding LDP session setup
>=20
>=20
> Hello,
>=20
> I have a question about LDP session establishment between two LSRs
> connected by multiple links.
> A problem has occurred in the network during LDP session set up
between
> two routers linked by two Ethernet LANs. Below I describe the
behavior.
>=20
>  1. Router A sends a LDP HELLO message on each Ethernet link at the
same
> time; the two messages are identical, including the router ID and the
> source IP address (IP address assigned to an internal interface).
>=20
>  2. Router B tries to open two TCP connections with router A on port
> 646: it sends two TCP SYN packets (using two different local ports).
>=20
>  3. Router A accepts both connections (TCP SYN ACK) and router B
> completes the TCP connections set up (TCP ACK): two TCP connections
are
> now available for LDP message exchange.
>=20
>  4. Router B (active role) sends two copies of the same LDP
> INITIALIZATION message to router A through the two TCP connections.
>=20
>  5. Router A sends a LDP INITIALIZATION message on the first TCP
> connection and clears the second TCP connection (TCP FIN).
>=20
>  6. Router A sends a LDP NOTIFICATION message with E-bit set and then
> resets the second TCP connection.
>=20
> What happens is that two TCP connections are created and Router B
tries
> to open two separate LDP sessions. It tries to open a second LDP
session
> when the first one is not yet established with the result that router
A
> closes both TCP connections and no LDP session is set up.
>=20
> It is not clear to me whether this behavior is correct according to
RFC
> 3036. In particular, is it correct that two TCP sessions are created
and
> a router tries to open two LDP sessions (it sends two LDP
INITIALIZATION
> messages) with the same peer?
>=20
> Thanks,
> Alberto and Luca
> --------------------------------------------------------------------
>=20
> CONFIDENTIALITY NOTICE
>=20
> This message and its attachments are addressed solely to the persons =
=3D
> above
> and may contain confidential information. If you have received the =3D
> message
> in error, be informed that any use of the content hereof is
prohibited.
> Please return it immediately to the sender and delete the message. =3D
> Should
> you have any questions, please contact us by replying to
> webmaster@telecomitalia.it.
>=20
>         Thank you
>=20
>                                         www.telecomitalia.it
>=20
> --------------------------------------------------------------------
>=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>=20
>=20
> --------------------------------------------------------------------
>=20
> CONFIDENTIALITY NOTICE
>=20
> This message and its attachments are addressed solely to the persons =
=3D
> above and may contain confidential information. If you have received
the =3D
> message in error, be informed that any use of the content hereof is =
=3D
> prohibited. Please return it immediately to the sender and delete the
=3D
> message. Should you have any questions, please contact us by replying
to =3D
> webmaster@telecomitalia.it.
>=20
>         Thank you
>=20
>                                         www.telecomitalia.it
>=20
> --------------------------------------------------------------------
>                        =3D20
>=20
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>=20

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

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



From mpls-bounces@lists.ietf.org Fri Sep 29 09:47:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GTIbw-0006x3-Aq; Fri, 29 Sep 2006 09:41:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GTIbu-0006wq-LT
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 09:41:02 -0400
Received: from outmail3.swisscom.com ([138.190.3.30] helo=mrz.swissptt.ch)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GTIbs-00087s-0q
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 09:41:02 -0400
Received: from sxmcmp02.corproot.net (SXMCMP02.corproot.net [138.190.70.98])
	by mrz.swissptt.ch with ESMTP id k8TDeti4003897
	for <mpls@lists.ietf.org>; Fri, 29 Sep 2006 15:40:55 +0200 (MEST)
Received: from sxsmtp01.corproot.net ([10.185.84.29]) by sxmcmp02.corproot.net
	with InterScan Messaging Security Suite;
	Fri, 29 Sep 2006 15:40:54 +0200
Received: from sg1393z.corproot.net ([10.185.84.161]) by sxsmtp01.corproot.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Sep 2006 15:40:54 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] Question regarding LDP session setup
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 29 Sep 2006 15:40:53 +0200
Message-ID: <60786EC779FCBD4984E9B975E885205B1B207D@sg1393z.corproot.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Question regarding LDP session setup
thread-index: AcbiU/pOU406xnf/Te6gOKInp0itvQAtDZqgADEmP6A=
From: <Santanu.Ganguly@swisscom.com>
To: <luca.fantolino@telecomitalia.it>
X-OriginalArrivalTime: 29 Sep 2006 13:40:54.0380 (UTC)
	FILETIME=[E2C172C0:01C6E3CC]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Cc: mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Luca,

Just a small observation which may or may not be relevant: If both links =
are connected to the same two routers via ethernet and are operating in =
raw mode, then its likely that the LDP Identifiers will be identical as =
you say. The first 4 octets will probably  be the router ID ( Loopback =
address in this case) and the Label Space ID, in accordance to RFC 3036, =
will be zero for per platform labels for ethernet. Hence 1 TCP =
connection.

Cheers

santanu

Santanu Ganguly
Swisscom Fixnet Wholesale AG
Binz-Ring 17
Zurich
Switzerland=20

-----Original Message-----
From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]=20
Sent: Thursday, September 28, 2006 4:18 PM
To: Kishore Tiruveedhula
Cc: mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup

Thanks for your reply.

I verified again the content of the LDP messages: both report the same =
LDP ID (the loopback address) and same Label Space ID (0).

In this case I understand you expect a single TCP connection be created.

bye
Luca

-----Original Message-----
From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]
Sent: mercoled=EC 27 settembre 2006 18:42
To: Tempia Bonda Alberto; mpls@lists.ietf.org
Cc: Fantolino Luca
Subject: RE: [mpls] Question regarding LDP session setup

If the both links uses the same local LDP ID (LSR Id:label space id), =
then it should create single LDP session (single TCP connection).

I guess your case might be something like below:

If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is =
Ra:La2 and Router B (assuming Active) LDP ID on both links is same =
Rb:Lb.


Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is Rb:Lb) =
Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is Rb:Lb)


In this case, Router B opens two TCP connections and Router B accepts =
both connections, but it may be accepted the TCP connections
      link1 of Router A to link2 of Router B  and
      link2 of Router A to link1 of Router B.

In this case, the session initialization fails when it verifies the =
Initialization message with its Hello adjacency ( by using Receiver LDP =
Identifier in CommonSession Parameter TLV).


Thanks,
Kishore

-----Original Message-----
From: Tempia Bonda Alberto [mailto:alberto.tempiabonda@telecomitalia.it]
Sent: Wednesday, September 27, 2006 11:21 AM
To: mpls@lists.ietf.org
Cc: Fantolino Luca
Subject: [mpls] Question regarding LDP session setup


Hello,

I have a question about LDP session establishment between two LSRs =
connected by multiple links.
A problem has occurred in the network during LDP session set up between =
two routers linked by two Ethernet LANs. Below I describe the behavior.

 1. Router A sends a LDP HELLO message on each Ethernet link at the same =
time; the two messages are identical, including the router ID and the =
source IP address (IP address assigned to an internal interface).

 2. Router B tries to open two TCP connections with router A on port
646: it sends two TCP SYN packets (using two different local ports).

 3. Router A accepts both connections (TCP SYN ACK) and router B =
completes the TCP connections set up (TCP ACK): two TCP connections are =
now available for LDP message exchange.

 4. Router B (active role) sends two copies of the same LDP =
INITIALIZATION message to router A through the two TCP connections.

 5. Router A sends a LDP INITIALIZATION message on the first TCP =
connection and clears the second TCP connection (TCP FIN).

 6. Router A sends a LDP NOTIFICATION message with E-bit set and then =
resets the second TCP connection.

What happens is that two TCP connections are created and Router B tries =
to open two separate LDP sessions. It tries to open a second LDP session =
when the first one is not yet established with the result that router A =
closes both TCP connections and no LDP session is set up.

It is not clear to me whether this behavior is correct according to RFC =
3036. In particular, is it correct that two TCP sessions are created and =
a router tries to open two LDP sessions (it sends two LDP INITIALIZATION
messages) with the same peer?

Thanks,
Alberto and Luca
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited.
Please return it immediately to the sender and delete the message. =
Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------


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


--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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

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



From mpls-bounces@lists.ietf.org Fri Sep 29 10:07:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GTIyx-0002mL-7f; Fri, 29 Sep 2006 10:04:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GTIyv-0002ko-Oo
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 10:04:49 -0400
Received: from [208.246.215.5] (helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GTIys-0001bS-A2
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 10:04:49 -0400
Received: from tiruveedhulapc (tiruveedhula-pc.avici.com [10.2.20.229])
	by mailhost.avici.com (8.12.8/8.12.8) with SMTP id k8TE42E5009165;
	Fri, 29 Sep 2006 10:04:23 -0400
From: "Kishore Tiruveedhula" <tiruveedhula@avici.com>
To: "Bob Thomas" <rhthomas@cisco.com>
Subject: RE: [mpls] Question regarding LDP session setup 
Date: Fri, 29 Sep 2006 10:03:53 -0400
Message-ID: <BOEJJJAOLEDABPBFHOJAOEPCCAAA.tiruveedhula@avici.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <FCAF0E8A270B6E4781D91431E853F6F303582F71@GONDOR.rs.riverstonenet.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c2e58d9873012c90703822e287241385
Cc: Fantolino Luca <luca.fantolino@telecomitalia.it>, mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi Bob,
    If the transport addresses are same, then active router can attempt
single TCP connection, agree with Pranjal.

If the transport addresses differ, then RFC3036 is not clear which one to
pick for TCP connection or attempt multiple TCP connections.


And there is one more problem that both routers may become Active or both
may become passive if both links advertises the different transport
addresses in such way that first adjacency transport address is higher and
second transport address is lower.

Thanks,
Kishore


-----Original Message-----
From: Dutta, Pranjal [mailto:pdutta@riverstonenet.com]
Sent: Thursday, September 28, 2006 11:26 PM
To: Bob Thomas; Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup


Hi Bob,
        It is well understood that the passive router has to close the
second or subsequent TCP connection requests for the same LDP session.
But
If the passive router advertises one LDPID (single label space) from it
then I don't see any reason for the active one to trigger up multiple
TCP connections.  The active router has to initiate only one TCP
connection for remote LDPID, although multiple hello adjacencies may
exist for the same LDPID.

Thanks,
Pranjal

-----Original Message-----
From: Bob Thomas [mailto:rhthomas@cisco.com]
Sent: Friday, 29 September, 2006 4:10 AM
To: Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: Re: [mpls] Question regarding LDP session setup

Hi Kishore,

> Subject: RE: [mpls] Question regarding LDP session setup
> Date: Thu, 28 Sep 2006 11:49:22 -0400
> Cc: mpls@lists.ietf.org
>
> Luca,
>    Yes. I expect single TCP connection.

RFC3036 is silent on this point.

RFC3036 specifies a single session between the 2 routers in this
situation but places no limit on the number of connections the active
router may attempt to open in order to establish the single session.

This leaves the router playing the passive role with the job of
selecting one connection for the session and closing the other(s).

Bob


> Thanks,
> Kishore
>
>
> -----Original Message-----
> From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]
> Sent: Thursday, September 28, 2006 10:18 AM
> To: Kishore Tiruveedhula
> Cc: mpls@lists.ietf.org; Tempia Bonda Alberto
> Subject: RE: [mpls] Question regarding LDP session setup
>
>
> Thanks for your reply.
>
> I verified again the content of the LDP messages: both report the same
=
> LDP ID (the loopback address) and same Label Space ID (0).
>
> In this case I understand you expect a single TCP connection be
created.
>
> bye
> Luca
>
> -----Original Message-----
> From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=20
> Sent: mercoled=EC 27 settembre 2006 18:42
> To: Tempia Bonda Alberto; mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: RE: [mpls] Question regarding LDP session setup
>
> If the both links uses the same local LDP ID (LSR Id:label space id),
=
> then
> it should create single LDP session (single TCP connection).
>
> I guess your case might be something like below:
>
> If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is
=
> Ra:La2
> and
> Router B (assuming Active) LDP ID on both links is same Rb:Lb.
>
>
> Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is
Rb:Lb)
> Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is
Rb:Lb)
>
>
> In this case, Router B opens two TCP connections and Router B accepts
=
> both
> connections,
> but it may be accepted the TCP connections
>       link1 of Router A to link2 of Router B  and
>       link2 of Router A to link1 of Router B.
>
> In this case, the session initialization fails when it verifies the
> Initialization message with its Hello adjacency ( by using Receiver
LDP
> Identifier in CommonSession Parameter TLV).
>
>
> Thanks,
> Kishore
>
> -----Original Message-----
> From: Tempia Bonda Alberto
[mailto:alberto.tempiabonda@telecomitalia.it]
> Sent: Wednesday, September 27, 2006 11:21 AM
> To: mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: [mpls] Question regarding LDP session setup
>
>
> Hello,
>
> I have a question about LDP session establishment between two LSRs
> connected by multiple links.
> A problem has occurred in the network during LDP session set up
between
> two routers linked by two Ethernet LANs. Below I describe the
behavior.
>
>  1. Router A sends a LDP HELLO message on each Ethernet link at the
same
> time; the two messages are identical, including the router ID and the
> source IP address (IP address assigned to an internal interface).
>
>  2. Router B tries to open two TCP connections with router A on port
> 646: it sends two TCP SYN packets (using two different local ports).
>
>  3. Router A accepts both connections (TCP SYN ACK) and router B
> completes the TCP connections set up (TCP ACK): two TCP connections
are
> now available for LDP message exchange.
>
>  4. Router B (active role) sends two copies of the same LDP
> INITIALIZATION message to router A through the two TCP connections.
>
>  5. Router A sends a LDP INITIALIZATION message on the first TCP
> connection and clears the second TCP connection (TCP FIN).
>
>  6. Router A sends a LDP NOTIFICATION message with E-bit set and then
> resets the second TCP connection.
>
> What happens is that two TCP connections are created and Router B
tries
> to open two separate LDP sessions. It tries to open a second LDP
session
> when the first one is not yet established with the result that router
A
> closes both TCP connections and no LDP session is set up.
>
> It is not clear to me whether this behavior is correct according to
RFC
> 3036. In particular, is it correct that two TCP sessions are created
and
> a router tries to open two LDP sessions (it sends two LDP
INITIALIZATION
> messages) with the same peer?
>
> Thanks,
> Alberto and Luca
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
> above
> and may contain confidential information. If you have received the =
> message
> in error, be informed that any use of the content hereof is
prohibited.
> Please return it immediately to the sender and delete the message. =
> Should
> you have any questions, please contact us by replying to
> webmaster@telecomitalia.it.
>
>         Thank you
>
>                                         www.telecomitalia.it
>
> --------------------------------------------------------------------
>
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
> above and may contain confidential information. If you have received
the =
> message in error, be informed that any use of the content hereof is =
> prohibited. Please return it immediately to the sender and delete the
=
> message. Should you have any questions, please contact us by replying
to =
> webmaster@telecomitalia.it.
>
>         Thank you
>
>                                         www.telecomitalia.it
>
> --------------------------------------------------------------------
>                        =20
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>

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



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



From mpls-bounces@lists.ietf.org Fri Sep 29 10:50:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GTJcV-000411-3U; Fri, 29 Sep 2006 10:45:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GTJcT-00040g-EN
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 10:45:41 -0400
Received: from outmail2.swisscom.com ([138.190.3.29] helo=mrp.swissptt.ch)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GTJcP-0006eE-S4
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 10:45:41 -0400
Received: from sxmcmp01.corproot.net (SXMCMP01.corproot.net [138.190.70.99])
	by mrp.swissptt.ch with ESMTP id k8TEjZTM009635
	for <mpls@lists.ietf.org>; Fri, 29 Sep 2006 16:45:35 +0200 (MEST)
Received: from sxsmtp01.corproot.net ([10.185.84.29]) by sxmcmp01.corproot.net
	with InterScan Messaging Security Suite;
	Fri, 29 Sep 2006 16:45:34 +0200
Received: from sg1393z.corproot.net ([10.185.84.161]) by sxsmtp01.corproot.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Sep 2006 16:45:34 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] Question regarding LDP session setup 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 29 Sep 2006 16:45:33 +0200
Message-ID: <60786EC779FCBD4984E9B975E885205B1B2099@sg1393z.corproot.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Question regarding LDP session setup 
thread-index: Acbj0GnOFBRFr84+SPKTEnjhf9tdmAAA2arw
From: <Santanu.Ganguly@swisscom.com>
To: <tiruveedhula@avici.com>
X-OriginalArrivalTime: 29 Sep 2006 14:45:34.0036 (UTC)
	FILETIME=[EB35F940:01C6E3D5]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
Cc: mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

=20
Hi,

As for different transport addresses, its true that RFC 3036 does not
seem to specify which one to pick for connectivity. However, it does say
the following:


"  Note that when an LSR sends a Hello it selects the transport address
   for its end of the session connection and uses the Hello to advertise
   the address, either explicitly by including it in an optional
   Transport Address TLV or implicitly by omitting the TLV and using it
   as the Hello source address.

   An LSR MUST advertise the same transport address in all Hellos that
   advertise the same label space.  This requirement ensures that two
   LSRs linked by multiple Hello adjacencies using the same label spaces
   play the same connection establishment role for each adjacency."


Thanks

santanu


-----Original Message-----
From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=20
Sent: Friday, September 29, 2006 4:04 PM
To: Bob Thomas
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup=20

Hi Bob,
    If the transport addresses are same, then active router can attempt
single TCP connection, agree with Pranjal.

If the transport addresses differ, then RFC3036 is not clear which one
to pick for TCP connection or attempt multiple TCP connections.


And there is one more problem that both routers may become Active or
both may become passive if both links advertises the different transport
addresses in such way that first adjacency transport address is higher
and second transport address is lower.

Thanks,
Kishore


-----Original Message-----
From: Dutta, Pranjal [mailto:pdutta@riverstonenet.com]
Sent: Thursday, September 28, 2006 11:26 PM
To: Bob Thomas; Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup


Hi Bob,
        It is well understood that the passive router has to close the
second or subsequent TCP connection requests for the same LDP session.
But
If the passive router advertises one LDPID (single label space) from it
then I don't see any reason for the active one to trigger up multiple
TCP connections.  The active router has to initiate only one TCP
connection for remote LDPID, although multiple hello adjacencies may
exist for the same LDPID.

Thanks,
Pranjal

-----Original Message-----
From: Bob Thomas [mailto:rhthomas@cisco.com]
Sent: Friday, 29 September, 2006 4:10 AM
To: Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: Re: [mpls] Question regarding LDP session setup

Hi Kishore,

> Subject: RE: [mpls] Question regarding LDP session setup
> Date: Thu, 28 Sep 2006 11:49:22 -0400
> Cc: mpls@lists.ietf.org
>
> Luca,
>    Yes. I expect single TCP connection.

RFC3036 is silent on this point.

RFC3036 specifies a single session between the 2 routers in this
situation but places no limit on the number of connections the active
router may attempt to open in order to establish the single session.

This leaves the router playing the passive role with the job of
selecting one connection for the session and closing the other(s).

Bob


> Thanks,
> Kishore
>
>
> -----Original Message-----
> From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]
> Sent: Thursday, September 28, 2006 10:18 AM
> To: Kishore Tiruveedhula
> Cc: mpls@lists.ietf.org; Tempia Bonda Alberto
> Subject: RE: [mpls] Question regarding LDP session setup
>
>
> Thanks for your reply.
>
> I verified again the content of the LDP messages: both report the same
=3D
> LDP ID (the loopback address) and same Label Space ID (0).
>
> In this case I understand you expect a single TCP connection be
created.
>
> bye
> Luca
>
> -----Original Message-----
> From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=3D20
> Sent: mercoled=3DEC 27 settembre 2006 18:42
> To: Tempia Bonda Alberto; mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: RE: [mpls] Question regarding LDP session setup
>
> If the both links uses the same local LDP ID (LSR Id:label space id),
=3D
> then
> it should create single LDP session (single TCP connection).
>
> I guess your case might be something like below:
>
> If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is
=3D
> Ra:La2
> and
> Router B (assuming Active) LDP ID on both links is same Rb:Lb.
>
>
> Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is
Rb:Lb)
> Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is
Rb:Lb)
>
>
> In this case, Router B opens two TCP connections and Router B accepts
=3D
> both
> connections,
> but it may be accepted the TCP connections
>       link1 of Router A to link2 of Router B  and
>       link2 of Router A to link1 of Router B.
>
> In this case, the session initialization fails when it verifies the=20
> Initialization message with its Hello adjacency ( by using Receiver
LDP
> Identifier in CommonSession Parameter TLV).
>
>
> Thanks,
> Kishore
>
> -----Original Message-----
> From: Tempia Bonda Alberto
[mailto:alberto.tempiabonda@telecomitalia.it]
> Sent: Wednesday, September 27, 2006 11:21 AM
> To: mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: [mpls] Question regarding LDP session setup
>
>
> Hello,
>
> I have a question about LDP session establishment between two LSRs=20
> connected by multiple links.
> A problem has occurred in the network during LDP session set up
between
> two routers linked by two Ethernet LANs. Below I describe the
behavior.
>
>  1. Router A sends a LDP HELLO message on each Ethernet link at the
same
> time; the two messages are identical, including the router ID and the=20
> source IP address (IP address assigned to an internal interface).
>
>  2. Router B tries to open two TCP connections with router A on port
> 646: it sends two TCP SYN packets (using two different local ports).
>
>  3. Router A accepts both connections (TCP SYN ACK) and router B=20
> completes the TCP connections set up (TCP ACK): two TCP connections
are
> now available for LDP message exchange.
>
>  4. Router B (active role) sends two copies of the same LDP=20
> INITIALIZATION message to router A through the two TCP connections.
>
>  5. Router A sends a LDP INITIALIZATION message on the first TCP=20
> connection and clears the second TCP connection (TCP FIN).
>
>  6. Router A sends a LDP NOTIFICATION message with E-bit set and then=20
> resets the second TCP connection.
>
> What happens is that two TCP connections are created and Router B
tries
> to open two separate LDP sessions. It tries to open a second LDP
session
> when the first one is not yet established with the result that router
A
> closes both TCP connections and no LDP session is set up.
>
> It is not clear to me whether this behavior is correct according to
RFC
> 3036. In particular, is it correct that two TCP sessions are created
and
> a router tries to open two LDP sessions (it sends two LDP
INITIALIZATION
> messages) with the same peer?
>
> Thanks,
> Alberto and Luca
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
=3D

> above and may contain confidential information. If you have received=20
> the =3D message in error, be informed that any use of the content =
hereof

> is
prohibited.
> Please return it immediately to the sender and delete the message. =3D =

> Should you have any questions, please contact us by replying to=20
> webmaster@telecomitalia.it.
>
>         Thank you
>
>                                         www.telecomitalia.it
>
> --------------------------------------------------------------------
>
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
=3D

> above and may contain confidential information. If you have received
the =3D
> message in error, be informed that any use of the content hereof is =
=3D=20
> prohibited. Please return it immediately to the sender and delete the
=3D
> message. Should you have any questions, please contact us by replying
to =3D
> webmaster@telecomitalia.it.
>
>         Thank you
>
>                                         www.telecomitalia.it
>
> --------------------------------------------------------------------
>                        =3D20
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>

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



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

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



From mpls-bounces@lists.ietf.org Fri Sep 29 17:58:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GTQHh-0005Lq-Fg; Fri, 29 Sep 2006 17:52:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GTQHg-0005Kt-1r
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 17:52:40 -0400
Received: from email.corliant.com ([207.7.61.16] helo=cormail2.pa.corliant.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GTQHd-00042B-OB
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 17:52:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 29 Sep 2006 16:50:30 -0500
Message-ID: <E58B6253B0756A4DA193794D71AEB1A301879368@cormail2.pa.corliant.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question regarding LDP session setup
thread-index: AcbkEUgLQ9CQci2HSNiK9gvVc6k1jA==
From: "Swaroop Potdar" <Swaroop.Potdar@Corliant.com>
To: <mpls@lists.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: [mpls] Question regarding LDP session setup
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1797907043=="
Errors-To: mpls-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============1797907043==
Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E411.4810A258"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E411.4810A258
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

QXMgcGVyIHRoZSBSRkMsDQogDQoxKSBUaGVyZSBzaG91bGQgYmUgbm8gcXVlc3Rpb24gb2YgdHdv
IGxhYmVsIHNwYWNlcyBhcyBvbmx5IGluIGNhc2Ugb2YgQVRNL0ZSIHdoaWNoIHVzZXMgSW50ZXJm
YWNlIHNwZWNpZmMgbGFiZWwgc3BhY2Ugd291bGQgdGhlIExTUiBhZHZlcnRpc2UgdHdvIGxhYmVs
IHNwYWNlcy4gd2l0aCBFdGhlcm5ldCBpdCB3b3VsZCBhbHdheXMgdXNlIHBlciBQbGF0Zm9ybSBz
cGVjaWZpYyBsYWJlbC4gU2luY2UgaW4gdGhlIGV4YW1wbGUgaXRzIG11bHRpcGxlIGV0aGVybmV0
IGJldHdlZW4gYm90aCBMU1IncyBpdCB3b3VsZCBiZSBzaW5nbGUgbGFiZWwgc3BhY2UgYWx3YXlz
Lg0KIA0KMikgV2hlbiB0aGUgaGVsbG9zIGFyZSBzZW50IGl0IHdvdWxkIGNhcnJ5IGEgc2luZ2xl
IGxhYmVsIHNwYWNlLCBzbyBJIGRvbnQgYWN0dWFsbHkgdW5kZXJzdGFuZCB0aGUgYWN0aXZlIExT
UiBvcGVuaW5nIHR3byBzaW11bHRhbmVvdXMgVENQIHNlc3Npb25zIHRvIHRoZSBzYW1lIGRlc3Rp
bmF0aW9uPz8gDQogDQpJIGJlbGlldmUgaXQgY291bGQgbm90IGhhcHBlbiwgb3IgaXQgY291bGQg
YmUgYSBwcm9ibGVtIHdpdGggdGhlIHN0YWNrIG9yIHB1cmVseSBoeXBvdGhldGljYWwuDQogDQpU
aGFua3MsDQpTd2Fyb29wDQo=

------_=_NextPart_001_01C6E411.4810A258
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj48SFRNTD48SEVBRD48TUVUQSBIVFRQLUVRVUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+PC9IRUFEPjxCT0RZPjxESVY+QXMgcGVyIHRoZSBS
RkMsPC9ESVY+CjxESVY+Jm5ic3A7PC9ESVY+CjxESVY+MSkgVGhlcmUgc2hvdWxkIGJlIG5vIHF1
ZXN0aW9uIG9mIHR3byBsYWJlbCBzcGFjZXMgYXMgb25seSBpbiBjYXNlIG9mIApBVE0vRlIgd2hp
Y2ggdXNlcyBJbnRlcmZhY2Ugc3BlY2lmYyBsYWJlbCBzcGFjZSB3b3VsZCB0aGUgTFNSIGFkdmVy
dGlzZSB0d28gCmxhYmVsIHNwYWNlcy4gd2l0aCBFdGhlcm5ldCBpdCB3b3VsZCBhbHdheXMmbmJz
cDt1c2UgcGVyJm5ic3A7UGxhdGZvcm0gc3BlY2lmaWMgCmxhYmVsLiBTaW5jZSBpbiB0aGUgZXhh
bXBsZSBpdHMgbXVsdGlwbGUgZXRoZXJuZXQgYmV0d2VlbiBib3RoIExTUidzIGl0IHdvdWxkIGJl
IApzaW5nbGUgbGFiZWwgc3BhY2UgYWx3YXlzLjwvRElWPgo8RElWPiZuYnNwOzwvRElWPgo8RElW
PjIpIFdoZW4gdGhlIGhlbGxvcyBhcmUgc2VudCBpdCB3b3VsZCBjYXJyeSBhIHNpbmdsZSBsYWJl
bCBzcGFjZSwgc28gSSBkb250IAphY3R1YWxseSB1bmRlcnN0YW5kIHRoZSZuYnNwO2FjdGl2ZSZu
YnNwO0xTUiBvcGVuaW5nIHR3byBzaW11bHRhbmVvdXMgVENQIApzZXNzaW9ucyB0byB0aGUgc2Ft
ZSBkZXN0aW5hdGlvbj8/IDwvRElWPgo8RElWPiZuYnNwOzwvRElWPgo8RElWPkkgYmVsaWV2ZSBp
dCBjb3VsZCBub3QgaGFwcGVuLCBvciBpdCBjb3VsZCBiZSBhIHByb2JsZW0gd2l0aCB0aGUgc3Rh
Y2sgb3IgCnB1cmVseSBoeXBvdGhldGljYWwuPC9ESVY+CjxESVY+Jm5ic3A7PC9ESVY+CjxESVY+
VGhhbmtzLDwvRElWPgo8RElWPlN3YXJvb3A8L0RJVj48L0JPRFk+PC9IVE1MPg==

------_=_NextPart_001_01C6E411.4810A258--


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

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

--===============1797907043==--




From mpls-bounces@lists.ietf.org Fri Sep 29 22:16:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GTUIw-0005Gi-Tk; Fri, 29 Sep 2006 22:10:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GTUIv-0005Gd-Qv
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 22:10:13 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GTUIt-0003T7-8g
	for mpls@lists.ietf.org; Fri, 29 Sep 2006 22:10:13 -0400
Received: from zinnhxm0.corp.nortel.com (zinnhxm0.corp.nortel.com
	[47.153.200.77])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k8U2A1d22347; Fri, 29 Sep 2006 22:10:01 -0400 (EDT)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] Question regarding LDP session setup
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Sat, 30 Sep 2006 12:09:57 +1000
Message-ID: <A47C032972CD72498B0B1A2BEACFF01701CB89EE@zinnhxm0.corp.nortel.com>
In-Reply-To: <BOEJJJAOLEDABPBFHOJAOEPCCAAA.tiruveedhula@avici.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Question regarding LDP session setup
Thread-Index: Acbj0HdBlRC0VL4sThmTJtFQuZhhTgAY08EQ
From: "Yu Yi" <yuyi@nortel.com>
To: "Kishore Tiruveedhula" <tiruveedhula@avici.com>,
	"Bob Thomas" <rhthomas@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7
Cc: Fantolino Luca <luca.fantolino@telecomitalia.it>, mpls@lists.ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>,
	<mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Hi,

   The relation between TCP connection and session is one to one. and in =
your case there should be only 1 session. So there should be only 1 tcp =
connect. If there are multiple links between 2 routers and using =
different transport address we should have some method to process this =
case. But unfortunately this is not clearly specified by RFC3036. =20
   Maybe the transport address should be same if mutiple links exist. =
This can avoid much trouble and this can be done by the limitation of =
configuration.
   Or just accept the first hello adjacency for the session if the =
second hello adjacency has different transport address.  Only in case =
the transport address are same for multiple adjacencies the session will =
be maintained by these multiple adjacencies.
=20
Cheers,
Yu Yi

-----Original Message-----
From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=20
Sent: 2006=C4=EA9=D4=C229=C8=D5 10:04 PM
To: Bob Thomas
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup

Hi Bob,
    If the transport addresses are same, then active router can attempt =
single TCP connection, agree with Pranjal.

If the transport addresses differ, then RFC3036 is not clear which one =
to pick for TCP connection or attempt multiple TCP connections.


And there is one more problem that both routers may become Active or =
both may become passive if both links advertises the different transport =
addresses in such way that first adjacency transport address is higher =
and second transport address is lower.

Thanks,
Kishore


-----Original Message-----
From: Dutta, Pranjal [mailto:pdutta@riverstonenet.com]
Sent: Thursday, September 28, 2006 11:26 PM
To: Bob Thomas; Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup


Hi Bob,
        It is well understood that the passive router has to close the =
second or subsequent TCP connection requests for the same LDP session.
But
If the passive router advertises one LDPID (single label space) from it =
then I don't see any reason for the active one to trigger up multiple =
TCP connections.  The active router has to initiate only one TCP =
connection for remote LDPID, although multiple hello adjacencies may =
exist for the same LDPID.

Thanks,
Pranjal

-----Original Message-----
From: Bob Thomas [mailto:rhthomas@cisco.com]
Sent: Friday, 29 September, 2006 4:10 AM
To: Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: Re: [mpls] Question regarding LDP session setup

Hi Kishore,

> Subject: RE: [mpls] Question regarding LDP session setup
> Date: Thu, 28 Sep 2006 11:49:22 -0400
> Cc: mpls@lists.ietf.org
>
> Luca,
>    Yes. I expect single TCP connection.

RFC3036 is silent on this point.

RFC3036 specifies a single session between the 2 routers in this =
situation but places no limit on the number of connections the active =
router may attempt to open in order to establish the single session.

This leaves the router playing the passive role with the job of =
selecting one connection for the session and closing the other(s).

Bob


> Thanks,
> Kishore
>
>
> -----Original Message-----
> From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]
> Sent: Thursday, September 28, 2006 10:18 AM
> To: Kishore Tiruveedhula
> Cc: mpls@lists.ietf.org; Tempia Bonda Alberto
> Subject: RE: [mpls] Question regarding LDP session setup
>
>
> Thanks for your reply.
>
> I verified again the content of the LDP messages: both report the same
=3D
> LDP ID (the loopback address) and same Label Space ID (0).
>
> In this case I understand you expect a single TCP connection be
created.
>
> bye
> Luca
>
> -----Original Message-----
> From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=3D20
> Sent: mercoled=3DEC 27 settembre 2006 18:42
> To: Tempia Bonda Alberto; mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: RE: [mpls] Question regarding LDP session setup
>
> If the both links uses the same local LDP ID (LSR Id:label space id),
=3D
> then
> it should create single LDP session (single TCP connection).
>
> I guess your case might be something like below:
>
> If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is
=3D
> Ra:La2
> and
> Router B (assuming Active) LDP ID on both links is same Rb:Lb.
>
>
> Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is
Rb:Lb)
> Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is
Rb:Lb)
>
>
> In this case, Router B opens two TCP connections and Router B accepts
=3D
> both
> connections,
> but it may be accepted the TCP connections
>       link1 of Router A to link2 of Router B  and
>       link2 of Router A to link1 of Router B.
>
> In this case, the session initialization fails when it verifies the=20
> Initialization message with its Hello adjacency ( by using Receiver
LDP
> Identifier in CommonSession Parameter TLV).
>
>
> Thanks,
> Kishore
>
> -----Original Message-----
> From: Tempia Bonda Alberto
[mailto:alberto.tempiabonda@telecomitalia.it]
> Sent: Wednesday, September 27, 2006 11:21 AM
> To: mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: [mpls] Question regarding LDP session setup
>
>
> Hello,
>
> I have a question about LDP session establishment between two LSRs=20
> connected by multiple links.
> A problem has occurred in the network during LDP session set up
between
> two routers linked by two Ethernet LANs. Below I describe the
behavior.
>
>  1. Router A sends a LDP HELLO message on each Ethernet link at the
same
> time; the two messages are identical, including the router ID and the=20
> source IP address (IP address assigned to an internal interface).
>
>  2. Router B tries to open two TCP connections with router A on port
> 646: it sends two TCP SYN packets (using two different local ports).
>
>  3. Router A accepts both connections (TCP SYN ACK) and router B=20
> completes the TCP connections set up (TCP ACK): two TCP connections
are
> now available for LDP message exchange.
>
>  4. Router B (active role) sends two copies of the same LDP=20
> INITIALIZATION message to router A through the two TCP connections.
>
>  5. Router A sends a LDP INITIALIZATION message on the first TCP=20
> connection and clears the second TCP connection (TCP FIN).
>
>  6. Router A sends a LDP NOTIFICATION message with E-bit set and then=20
> resets the second TCP connection.
>
> What happens is that two TCP connections are created and Router B
tries
> to open two separate LDP sessions. It tries to open a second LDP
session
> when the first one is not yet established with the result that router
A
> closes both TCP connections and no LDP session is set up.
>
> It is not clear to me whether this behavior is correct according to
RFC
> 3036. In particular, is it correct that two TCP sessions are created
and
> a router tries to open two LDP sessions (it sends two LDP
INITIALIZATION
> messages) with the same peer?
>
> Thanks,
> Alberto and Luca
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
=3D=20
> above and may contain confidential information. If you have received=20
> the =3D message in error, be informed that any use of the content =
hereof=20
> is
prohibited.
> Please return it immediately to the sender and delete the message. =3D =

> Should you have any questions, please contact us by replying to=20
> webmaster@telecomitalia.it.
>
>         Thank you
>
>                                         www.telecomitalia.it
>
> --------------------------------------------------------------------
>
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
=3D=20
> above and may contain confidential information. If you have received
the =3D
> message in error, be informed that any use of the content hereof is =
=3D=20
> prohibited. Please return it immediately to the sender and delete the
=3D
> message. Should you have any questions, please contact us by replying
to =3D
> webmaster@telecomitalia.it.
>
>         Thank you
>
>                                         www.telecomitalia.it
>
> --------------------------------------------------------------------
>                        =3D20
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>

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



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

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



